# Sentinel Event & RCA Record Review > Chart, policy and device-log assembly for root cause analysis and sentinel event review, page-cited and delivered inside the reporting window. Canonical page: https://medrecords.ai/solutions/sentinel-event-rca-record-review/ --- [Home](https://medrecords.ai/) ›[Solutions](https://medrecords.ai/solutions/) ›Sentinel Event & RCA Review SENTINEL EVENT & RCA RECORD REVIEW ## 45 days to a credible RCA. Most of it goes to assembly. Sentinel event record review services assemble everything a root cause analysis runs on: the full chart, the policies in force that day, device logs, and staffing records, ordered into one page-cited timeline. The RCA team spends its window analysing the event rather than collecting the documents that describe it. [Test a file ](https://medrecords.ai/test-a-file/?src=sentinel-event-rca-record-review) [Book a demo](https://medrecords.ai/demo/) Click any row → the source page it cites Event assembly · Case #IME-4812 documented Adams, Timothy · sentinel event file 342 pp / 2 packets received logged 11 duplicate pages removed free p.140 — wrong patient quarantined Pages 342 Documents 27 Cited 100% ### The analysis standard is published. So is the clock. We do not build for a case type until we can name the standard that defines a correct output and the person who grades the file against it. For sentinel event review, both are already published. The standard and the referee The rulebook - The Joint Commission Sentinel Event Policy, which requires a comprehensive systematic analysis and an action plan, generally within 45 days of the event becoming known - The Patient Safety and Quality Improvement Act and 42 CFR Part 3, which set the terms on which work becomes patient safety work product inside a PSES - The hospital's own policies and procedures as they existed on the date of the event, not as they read today - State adverse-event reporting statutes, which run their own clocks and definitions The referee - The Joint Commission, which reviews the thoroughness and credibility of the analysis and the action plan - The state health department, where a reportable adverse event triggers its own review - The patient safety organization, whose PSES defines what is protected and what is not A 45-day window spent chasing device logs and superseded policy versions Flat 10¢/page here, duplicates free Event assembly · Case #IME-4812 cited 100% Packet342 pp / 2 packets · 11 deduplicatedlogged Full chartOrdered to the minute of the eventcited Policies in forceVersion dated to the event, not todaycited Device & system logsAligned to the clinical timelineflagged Assembly delivered · cited 100% · no causation finding How it works ### 3 steps between the event and the analysis. 01 #### Send everything you have Chart, medication administration records, device downloads, staffing sheets, and the policy set in force on the date — in any format, in any order. 02 #### We return the assembly, page-cited One timeline to the minute, with clinical events, device data, and the governing policy version aligned, and every entry citing its source. 03 #### The RCA team analyses Your team runs the systematic analysis and writes the action plan. We never assign cause, name a contributing factor, or draft a corrective action. The boundary, in writing ### An assembled record, not a root cause. We assemble and cite the chart, the logs, and the policy versions in force, aligned on one timeline. We do not determine cause, identify contributing factors, apportion responsibility, or draft the action plan. A root cause analysis is the work of your patient safety team, and it stays there. Whether the assembly becomes patient safety work product depends on your PSES definition and how the engagement sits inside it. That is a question for your patient safety officer and counsel, worth settling before the first event is sent. Audit trail · Case #IME-4812 exportable 08:12Packet received · 342 pp / 2 packetssystem 08:3111 pages deduplicatedsystem 08:44p.140 flagged — wrong patientsystem 08:54Event assembly complete · assembly complete · 1 timeline · cited 100%system 09:20Event assembly reviewed · citations verifiedreviewer 09:26Event assembly exported · RCA workbook drafted off-platformreviewer Every access logged · file deleted 30 days after delivery Why Medrecords AI ### The rules the platform never breaks. EVERY LINE CITED CASE #IME-4812 · ADAMS, T.342 pp 2/14 — ER visit, right knee p.4 4/18 — arthroscopic surgery p.61 p.140 — wrong patient quarantined Medrecords AI Read every page · cite every line #### HIPAA, under a signed BAA Every file is handled under our Business Associate Agreement, from the first byte. #### Never trains a model Your records are never used to train any AI model — ours or anyone else's. #### Every line cited If we can't cite it, we don't say it. Every sentence links to its source page. #### Deleted after delivery Files are deleted 30 days after delivery, with a full audit log of every access. Powered by the platform ### 4 capabilities behind every event assembly. The event assembly is 1 deliverable of the same platform that reads, sorts, and cites the whole record. [ #### Medical Records OCR Every page read in full — chart, device downloads, staffing sheets, superseded policy PDFs — nothing skipped, nothing guessed. IN ACTION · 342 pp / 2 packets → 27 documents, read in full ](https://medrecords.ai/product/ocr/) [ #### Medical Chronology The event timeline builds itself to the minute, so clinical events, device data, and staffing line up on one axis. IN ACTION · admission → event → response, 1 continuous timeline ](https://medrecords.ai/product/chronology/) [ #### Verifiable AI Citations If we can't cite it, we don't say it. Every entry on the timeline links to the page or log line it came from. IN ACTION · every timeline entry → cited 100% ](https://medrecords.ai/product/citations/) [ #### Medical Summary Reports The assembly formats straight into your RCA workbook — your template, your letterhead. IN ACTION · event assembly → RCA-ready timeline ](https://medrecords.ai/product/summaries/) FAQ ### Sentinel event record review, answered. No. We assemble and cite the record the analysis runs on: the chart, the device logs, the staffing records, and the policies in force on the date, aligned to one timeline. Identifying cause, contributing factors, and corrective actions is your patient safety team's work. That depends on your patient safety evaluation system, your PSO relationship, and how the engagement is structured under 42 CFR Part 3. We can work inside a structure your counsel and patient safety officer define; we don't opine on whether protection attaches. Yes, if you send the versions. We cite the policy document you provide and the effective date printed on it, so the analysis reads the rule that was actually in force rather than the current revision. We can't produce a version you no longer hold. No. Medrecords AI does not retrieve records from providers or facilities. You bring the records you already have — review starts in minutes from upload. Retrieval vendors take days; you can keep yours and still cut the review to minutes. ### Send 1 file. We'll tell you what we can read. No obligation. If the case type is buildable we'll scope it; if it isn't, we'll say so. [Test a file ](https://medrecords.ai/test-a-file/?src=sentinel-event-rca-record-review) [Book a demo](https://medrecords.ai/demo/) [See every case type we process →](https://medrecords.ai/solutions/case-types/)