Tutorial ID | T-31 |
Section | Reporting & Billing |
Title | Updating the Report When New Documents Arrive |
Subtitle | Bring new documents into an existing report without breaking the chronology, duplicating events, or losing your edits. |
Before You Begin
You have a report already generated for this case, and new documents that need to be added to it.
You know which sections of the report might be affected by the new material.
What You Will Accomplish
By the end of this tutorial, every new document you add will be checked against the existing chronology, screened for duplicates, integrated without overwriting your manual edits, and reflected in a re-validated, clearly versioned report.
Why Does This Tutorial Matter
A case rarely arrives complete, and updating a report is not simply appending new material — it's re-checking whether that material changes anything you already concluded. A new document can confirm, extend, or contradict what's already in the report, and treating it with the same care as the original set is what keeps the report both current and trustworthy.
Treat an update as a simple append, and a contradicting record gets silently overwritten, a duplicate creates a second entry for the same event, a regenerated section discards edits you already made by hand, a new provider name goes unreconciled with an existing one, and a report that's never re-validated or re-versioned leaves no clear account of which documents it actually reflects.
What to Do if Something Goes Wrong
The list below covers the most common problems when updating a report with new documents. Each entry follows the same pattern: what you'll notice, why it likely happened, a real example, and how to fix it.
Problem: A new document gives a different date, mechanism, or history than what's already recorded in the chronology.
Likely cause: The new document was added without being read against the existing chronology first, so the conflict wasn't caught before integration.
Example: A later medical record lists a different injury date than the one already in the chronology, and the new date is added without noting the discrepancy.
Fix:
Read new documents against the existing chronology before integrating them.
Where they conflict, note the discrepancy rather than silently replacing the earlier account.
Re-validate the affected statements and decide, as the professional, how to present the conflict.
Problem: The same event appears twice in the report after new documents are added.
Likely cause: The same record arrived more than once, from different sources, and wasn't recognized as a duplicate before being integrated.
Example: A hospital sends the same discharge summary twice, once directly and once through the attorney, and both copies get processed as separate events.
Fix:
Run duplicate detection when new documents are added.
Confirm whether a new document is genuinely new or a copy of one already in the case.
Merge or discard duplicates so that each event appears once.
Problem: A correction you made by hand is gone after new content is added to the report.
Likely cause: A section was regenerated in full to incorporate new material, and the regeneration discarded the manual edits that were already in place.
Example: A reviewer had corrected a mislabeled provider name in a section, and regenerating that section to add a new document reverts the name to its original, incorrect form.
Fix:
Generate or regenerate only over the new material, not the whole report, where possible.
Confirm that your earlier reviewed edits are preserved after adding new content.
Re-apply any manual corrections that were affected.
Problem: The same provider, facility, or diagnosis appears under two different spellings in the report.
Likely cause: A new document referred to an existing provider or diagnosis using different wording, and it wasn't checked against the names already used in the report.
Example: An existing entry lists “Dr. Jonathan Reyes” while a new document refers to “Dr. J. Reyes,” and the report treats them as two different providers.
Fix:
Check new provider, facility, and diagnosis names against those already in the report.
Standardize to the existing form where they refer to the same entity.
Use Search to apply the standard form consistently.
Problem: A statement's Validation Score doesn't reflect the report as it actually stands after new documents were added.
Likely cause: The report wasn't re-validated after integrating new content, even though the added material can change scores and the relationships between statements.
Example: A new document weakens the support behind an existing statement, but the statement still shows its original, higher Validation Score because validation was never rerun.
Fix:
After integrating new documents, re-run validation over the affected sections.
Review any newly low-scoring statements.
Update the timeline and chronology order to reflect the new material.
Problem: It's unclear which version of the report reflects which set of documents.
Likely cause: An updated report wasn't saved as a clearly identified new version, so there's no traceable record of what changed and when.
Example: Two team members each have a copy of the report open, and neither can tell which one includes the records that arrived last week.
Fix:
Save the updated report as a clearly identified new version.
Note which documents were added, and when.
Keep the relationship between document sets and report versions traceable.
Tip Update in place rather than starting over. Regenerating only the affected sections keeps the time you invested in earlier edits and conclusions, while still letting the new evidence do its work. |
Summary
Every new document is now checked against the existing chronology, screened for duplicates, integrated without overwriting your manual edits, reconciled against existing names, re-validated, and reflected in a clearly versioned report — so each update keeps the report both current and trustworthy.