Tutorial ID | T-15 |
Section | Preparing a Case/Reviewing the case |
Title | Preparing the Case for Analysis and Reporting |
Subtitle | Confirm your case is fully ready before running workflows or assembling a report. |
Before You Begin
You have a case with uploaded documents.
Note The case header — the claimant's name, date of birth, and event date — sets the foundation for every chronology entry and every pre-event versus post-event distinction in the case. If any of these fields are wrong, every downstream calculation that depends on them will be inaccurate, even when every individual document and entry is otherwise correct. |
What You Will Accomplish
By the end of this tutorial, your case will be fully ready before you run workflows or assemble a chronology report. You will know how to confirm every document is processed, and your workflow outputs reflect the current, complete document set.
Why Does this Tutorial Matter
When a case moves into AI analysis before it's actually ready, the consequences go well beyond a few overlooked pages. Incomplete document sets, and outdated workflow outputs all flow directly into the final report — so you receive a report built on a partial or outdated picture of the case. A report generated this way can misrepresent the claimant's medical history, distort the causation argument, or omit critical findings.
What to Do if Something Goes Wrong
The list below covers the most common problems with case preparation. Each entry follows the same pattern: what you'll notice, why it likely happened, and how to fix it.
Tip Add a label, such as "Review finished" or "In progress," to each document as you go, so you and your colleagues can see processing status at a glance.
|
Problem: The case moves into chronology report creation before every document has actually been fully processed.
Likely cause: A case can contain dozens of documents uploaded across multiple sessions, and it's easy to lose track of which ones were fully processed, reviewed, and added to the workspace versus which were uploaded and never followed through to completion.
Example: A case has 20 documents uploaded over several weeks. One of the batches was uploaded but never stapled or reviewed afterward. It sits in Files exactly as it arrived, and nobody notices because the other 19 batches look complete.
Fix:
Open Files and review every document listed for the case, regardless of when it was uploaded.
Confirm that each document shows a fully processed status (all necessary pages are added to a workspace, organized into staples, and include episodes with relevant information).
Add a label, such as "Review finished" or "In progress," to track each document's status.
For any batch that appears incomplete or was never followed up on, determine why — whether it failed processing, was left unstapled, or was simply never reviewed.
Problem: The chronology is incomplete, because episodes were created but their corresponding pages have not been added to the Workspace.
Likely cause: The page's Include page into workspace toggle was switched off — either by mistake or because the page was never revisited after its date and provider were set — so the page shows a fully configured episode (date, time, provider, notes) but does not actually contribute to the timeline.
Example: A page from physiatry visit has its episode fully set up — the date, provider, and relevant notes are all correctly assigned in the panel. But Include page into workspace toggle next to it is switched off. At a glance, everything about the page looks complete — episodes attributed to this page or staple simply never appear in the Timeline among other visits and events.
Fix:
Open a page or a staple in a document set and check the Include page into workspace toggle in the panel on the right.
Confirm the toggle is switched on for every page that should contribute to the chronology of the case.
If the toggle is off, switch it on to add the page into the Workspace.
Problem: The report is assembled from workflow output that no longer reflects the current document set.
Likely cause: Some workflows run early, before all documents are uploaded, while others run later once preparation is complete. It's easy to treat all the output as equally current, when only the later runs actually reflect the finished case.
Example: A causation-analysis workflow runs during the case's first week, before the imaging reports and the independent medical exam have been uploaded. Three weeks later, the case is fully prepared with all records in place, but the report still uses that original workflow output.
Fix:
Before assembling a report from existing workflow outputs, check the date each workflow was run against the date the last document set was uploaded.
Identify any workflow run before the case reached its final prepared state.
For each outdated workflow, determine whether the records added or changes made since it ran are significant enough to require rerunning it.
Rerun any workflow whose output may no longer reflect the current, complete document set, rather than relying on its earlier output by default.
Once all workflow output is confirmed, proceed with assembling the report.
Summary
Your case is now fully ready for analysis and reporting. Every batch is processed, every relevant page has reached the chronology, the case header is accurate, and your workflow outputs reflect the current, complete document set.