For attorneys and legal nurse consultants who have both the occurrence report and the chart for the same event.
An incident report and the chart are written by different people, at different times, for different audiences, and they often disagree. Paste the incident or occurrence report on the left and the chart notes about the same event on the right (fall, medication event, pressure injury discovery, elopement, equipment failure, restraint, procedure complication). The tool sets the two accounts side by side and lists each discrepancy by element: time, location, witnesses, sequence, injury, notification, intervention. It calls out late entries and addenda, builds a grid of who was notified and which document records it, raises record-grounded flags and names the audit trails that settle the differences. Every finding is quoted from one of the two texts. It does not decide who is right, whether the report is privileged or what caused the event.
The texts were long and the analysis stopped before the end. Trim the chart to the notes about the event and run again.
Summary
The two accounts
Discrepancies
Late entries and addenda
Notifications
Flags
Gaps in what was pasted
How to use the result
Start with the times. When the report and the chart give different times for the event, its discovery or the physician call, the EHR audit trail and the incident-system metadata tell you when each entry was actually created. Those two logs are the first request.
Treat late entries as questions, not conclusions. A late entry is permitted documentation practice when it is labelled and timed. The issue for review is whether it adds facts that appear nowhere else, changes an earlier account, or was written after the author learned of the report or a complaint.
Notifications claimed in only one document are a common gap. A report that says the physician and family were notified, against a chart that documents neither, is a deposition topic for the author of each document.
Silence is not contradiction. Where one document simply does not address an element the other covers, the grid says so. Ask for the complete chart (flow sheets, assessments, orders after the event) before treating the silence as meaningful.
Discoverability varies by state. Whether the incident report and risk-management file are protected by a peer-review, quality-improvement or work-product privilege depends on the jurisdiction and on how the facility handled the document. That is a legal question for the attorney; this tool only compares the texts it is given.
Verify every quote against the page it came from before it goes into a chronology, expert packet or deposition outline.
What to request next
EHR audit trail for every chart entry about the event: user, creation time, edits and deletions with original values, late-entry flags, access log for the 72 hours after the event
Incident-reporting system metadata: creation and submission times, submitter, every edit and version, routing and review history, attachments, final disposition
Witness statements and staff interview notes taken after the event, with dates and who conducted them
The risk-management, quality or peer-review file on the event, to the extent discoverable in the jurisdiction (or a privilege log identifying what is withheld and the basis)
Policies in force on the date: incident reporting, post-fall or post-event assessment, physician and family notification, late-entry and addendum documentation, root-cause analysis
Staffing and assignment sheet for the shift, including who was assigned to the patient and who was present on the unit
Device, alarm, call-light, bed-alarm and camera or badge-access logs covering the event window, and the retention policy for each
Any root-cause analysis, failure-mode review or corrective action plan the event generated, where discoverable
Need this across the whole chart?
MedLegal AI's Records Analyzer and Timeline Builder read the complete record, pin every finding to a Bates page and build the chronology for the demand or expert packet. Free account to start.