EHR Error Pattern Clustering
Group recurring EHR submission failures — distinguish systemic issues from one-offs
Scope — EHR section only: The patterns below come from
If an error message in the Reason column contains a UUID that belongs to a page rather than a document, use Document Journey — it accepts both document IDs and page IDs.
patient_packets.hd_response_reason (documents that reached EHR submission but were rejected).
Errors that happen earlier — such as Azure OpenAI content policy violations or other OCR-stage failures — block the document before a patient_packets row is created,
so they never appear here. Those are listed separately in the OCR / Pre-EHR Errors card below.
If an error message in the Reason column contains a UUID that belongs to a page rather than a document, use Document Journey — it accepts both document IDs and page IDs.
1
Distinct Error Patterns
0
Systemic (3+ days)
6
Total Affected Docs
Error Patterns
1 patterns · 6 docs
| Error Pattern | Sample Reason | Docs | Days appeared |
Top Facilities | First Seen | Last Seen | Type | Action |
|---|---|---|---|---|---|---|---|---|
| No reason provided | No reason provided | 6 | 1 | Outlook Scrapper, East View Healthcare | 06/19 01:20 | 06/19 13:30 | One-off |
Systemic = error appeared on 3+ distinct days (likely a recurring integration or config issue). One-off = appeared on 1–2 days (possibly transient, retry or data issue). Click any row to expand and view affected documents.
OCR / Pre-EHR Error Documents
Error-status docs with no patient_packets — blocked at OCR / Classification stage
No OCR-stage error documents in this date range.