Waiting for the first events
Nothing has been received from the extension yet. Open the clinic HIS, fill a demo claim and submit it — anonymous events appear here within a few seconds.
Just want to see the console populated? Load a synthetic batch (tagged clinic_id: demo-seed; use Reset events to clear).
Submissions vs payer rejections
Per minute of simulation time · rejections include partial and NPHIES errors
Rejections by NPHIES code
Recall = share caught by a rule open at submit
| Rule | NPHIES code | Owner | Tier (pushed live) | Fired@ submit |
Shown | Fixed | Overrides | n labeled |
Precision | Recommendation |
|---|
Precision = among submitted claims with an outcome and the rule open at submit, share denied with the rule's own code (MN-1-1 counts for R08 and R09; R12/R14 count any non-approved outcome). Recommendations follow the pilot gate: n ≥ 5 to judge, precision ≥ 90% with n ≥ 8 to block, ≥ 60% to warn, < 30% to demote. Click a recommendation to apply it.
Anonymous rule events — nothing that identifies a patient
The extension evaluates the claim inside the browser. Only these whitelisted keys are accepted; anything else is dropped on arrival and counted below. Every stored payload is then re-scanned for ID-like numbers, exact dates and exact amounts.
- No names
- No national ID / Iqama / member ID
- No phone, DOB or exact dates
- No free text (HPI, exam)
- No exact amounts — bands only
- No full ICD codes — 3-char category
Key whitelist per event type
Enforced server-side at ingest
Last 20 payloads, exactly as received
Pretty-printed from the database
Activity by role
Role is set once per workstation install — never a person
Why staff override
Reasons chosen on “Submit anyway”