← Back to Work
Process file · Healthcare Healthcare

What’s inside: monitoring · output checking

In-range results into the EHR, abnormal to a clinician

The question this file answersWho checks that a lab result actually reached the chart, and how fast does an abnormal one reach the doctor?

Fits: clinics and hospital groups where lab results still pass through admin for checking, entry or notification — continuous volume with screening-programme spikes (healthcare playbook), no per-day figure published.

Not for: sites where the lab feed already writes every result to the EHR and abnormal flags already page the clinician — there is nothing administrative left between the lab and the chart.

Typical day

What the desk looks like today

Typical, from the healthcare playbook — not a client's day. Results flow continuously from the lab system — Sunquest, Orchard, PathNet — and spike whenever a screening programme runs. When the feed into the EHR works, admin still checks each result and notifies the ordering physician; when it fails, someone keys the values in. Patients ring asking whether results are in. No per-day count is published, so the audit takes yours. It hurts in screening season, when a week's results arrive in two days and the abnormal value waits behind everything in range.

What changes

What Monday looks like after

The Monday a screening batch lands. Overnight results are already in the chart, the in-range ones filed and the physician notified under your protocol; admin opens the exceptions — a field missing, a faxed result, an unmatched patient record — not the whole day's output. Each abnormal value went to a clinician when it arrived, with the previous result beside it, and the clinician's judgement about it is untouched. The phones are quieter, because routine results reach the portal with a plain note when your protocol allows. Your lab manager sees turnaround per result. Accenture (2023) is the source for the turnaround figure above; it describes distribution, never interpretation.

Typical, not a measured client result. Every figure here comes from the playbook source named below.

~40–60%

faster result distribution — Accenture (2023)

Before: results wait for admin to check, file and notify. After: Accenture (2023) reports 40–60% faster distribution — no model interprets a panic value.

Where this number comes from

Accenture "Digital Health Technology Vision" (2023): automated result distribution reduces turnaround time by 40–60%; the playbook also cites HL7/FHIR interoperability as enabling roughly 70% of lab-result workflows to be automated. Industry figures, not our measurement. Playbook range 50–70%. Interpretation of abnormal results stays with a clinician.

What we install

What we put in front of the systems you already run

No model interprets a result here; the clinician does. We install filing and routing between your lab system — Sunquest, Orchard, Cerner PathNet — and your EHR — Epic, Cerner, MEDITECH or the one you run:

  1. results are imported over HL7/FHIR, PDFs parsed only where a lab still faxes
  2. each value is compared with the reference range and the lab's own flags
  3. in-range results are filed and the ordering physician notified under your protocol
  4. an abnormal or critical value goes to the named clinician at once, with the order and previous result, and nothing about it goes to the patient
  5. for in-range results a plain-language portal note is drafted, released under your clinical lead's protocol.

First scope: one high-volume panel.

What stays human — and what this will not do

Interpreting the abnormal result. Deciding on follow-up. Counselling the patient. Anything that is a clinical act rather than a filing event.

What can go wrong — and what we do about it

A wrong or missing reference range in the feed makes a normal look abnormal or, worse, the reverse — so ranges and flags are the lab's own, reviewed by your clinical lead before go-live; doubt routes to a clinician. Fax and paper results read imperfectly; those go to admin as now. Without HL7/FHIR on both sides the bridge is the vendor's import, slower and dependent on IT; HIPAA logging comes first. The playbook's 50–70% covers filing and distribution; interpreting an abnormal result, deciding follow-up and counselling the patient are outside it, always.

How long it takes, and what we need from you

Audit, about two weeks (€1.5–3K): we trace a month of results from lab to chart, count how many needed a hand and why — failed feed, fax, missing field — and check whether both vendors will switch on HL7/FHIR. Pilot, 3–5 weeks — medium complexity in the healthcare playbook (€10–20K): one panel, filing and notification only, your clinical lead signs the routing protocol first. Production: further panels, then patient-facing notes. From you: interface access, the notification protocol, your privacy officer.

The path: free 60-second estimate → free 20-minute review → paid audit of this one process (€1.5–3K, typically two weeks) → pilot with your people in the loop (€10–20K, weeks, not quarters). No transformation programme. Prices are public, on the services page →

This is about you if…
What does this mean in euros?

That depends on your volumes and wage costs — this page will not invent the number. The free 60-second estimate runs that calculation from your answers, with every multiplier sourced.

Get your free savings estimate 60 seconds · no sales call Or write first → Map a healthcare process like this one — free, 60 seconds →

Not a named Aperanda client. Process file · Healthcare.

Deep-dive process file. Volumes, weeks and sources come from the industry playbook; nothing here is a named client.

All process files