Clinical Audit Workflow
Once a PCR is selected via Review, you enter the active clinical audit interface.
PCR Header
Section titled “PCR Header”The header displays:
- The PCR ID and incident date
- A session type badge: “Reviewing” (indigo) when in active QA review mode, or “Viewing” (gray) when read-only.
- The current review status and priority badge (e.g., “High Priority”, “Flagged”, “In Progress”)
- A “Compliance” percentage score in the upper right, color-coded (green = high, red = low)
- A spinner and “Analyzing…” label in place of the score if the AI engine is still running
- Navigation arrows for moving to the “Previous PCR (Newer)” and “Next PCR (Older)” in the queue
- A “Provider Receipt” row showing “Viewed:” and “Acknowledged:” timestamps for provider-facing feedback
The Data Review Interface
Section titled “The Data Review Interface”The audit is organized into six functional tabs, in the following order:
- AI Summary — auto-generated clinical insights
- Narrative — provider’s written documentation
- Vitals & Meds — chronological interventions
- Protocol Compliance — rule engine results
- Physical Exam — body diagram and findings
- Notes — internal notes and provider feedback
AI Summary
Section titled “AI Summary”This tab has two columns. The main column shows:
- “Clinical Insights” — LLM-generated narrative summarizing the clinical encounter
- “Protocol Deviations” — a list of failed rules (if any) highlighted for quick review
- An auto-flag alert (if the system flagged the record) listing the specific flag reasons
The right sidebar shows:
- “Patient Profile” card: Age, Sex, Impression, Chief Complaint, Disposition, Destination Type, Transport Mode, Final Acuity
- “Primary Crew Member” card: Provider name and certification level
- “Peer Comparison” card: a bar chart comparing this provider’s compliance to the agency average for the protocol
Protocol Compliance
Section titled “Protocol Compliance”The Protocol Compliance tab header inside the tab reads “Medical Directives Audit” with the subtitle “Automatic verification against system protocols.” A search bar at the top accepts text to filter protocols or rules.
Each applicable protocol appears as an expandable section. The collapsed header shows:
- The protocol name
- A summary of “{N} Passed” (emerald), “{N} Deviations” (rose), “{N} Warnings” (amber)
- An “Applicable” or “Not Applicable” badge
When expanded, each protocol shows:
- A “Protocol Entry Criteria” section with a “MET” or “NOT MET” badge and a trace tree
- Individual rule cards, each with a status badge: “Pass” (green), “Fail” (red), “Warning” (yellow), or “Skip” (amber)
- Expanding a rule card reveals the “Audit Logic Trace” — a hierarchical breakdown of the reasoning steps the rule engine followed
Physical Exam
Section titled “Physical Exam”The Physical Exam tab shows a body silhouette diagram with clickable anatomical regions. Clicking a region scrolls to the corresponding finding card. Findings are organized into anatomical cards: Skin, Head, Face, Neck, Heart, Pelvis/GU, Mental Status, Neurological, Abdomen, Back/Spine, Extremities, Eyes, Lungs, and Chest. If no physical exam was recorded, the tab displays the message: “No Physical Exam Recorded — This PCR does not contain any physical examination findings.”
The Notes tab has two sub-tabs toggled by a switch:
- “Internal Notes” (lock icon) — private QA team notes not visible to providers
- “Provider Feedback” (message icon) — a messaging thread visible to the provider; used for peer-to-peer feedback and requesting documentation corrections
Final Disposition of Audit
Section titled “Final Disposition of Audit”The actual action buttons in the PCR header are:
- “Reprocess” (outline button with refresh icon, visible on large screens only) — re-runs the AI evaluation engine on the PCR, used when source data has changed.
- “Flag” (amber outline button with flag icon) — marks the record for secondary review by a QA Manager.
- “Approve” (emerald filled button with checkmark icon) — finalizes the audit and sets the review status to “Reviewed.”
If the provider’s documentation needs to be returned for editing, this is handled through the “Provider Feedback” sub-tab in the Notes tab, not via a Regress button.