"Have my results come back yet?" — the single most common inbound call to a clinic front desk. In legacy clinics, the answer is "let me check," followed by a five-minute hunt. In modern clinics, the patient already has the answer on their phone before they reach for it.
Lab result sharing is a workflow problem dressed as an IT problem. Here's the workflow.
Table of Contents
- The problem in shape
- The modern flow
- Lab integrations: API vs PDF
- Critical results: a different track
- Patient-facing delivery
- What to measure
- FAQ
The problem in shape
- Results arrive by fax, email, or portal scrape.
- Staff manually attach to the patient chart.
- Doctor reviews and decides on action.
- Patient is called or messaged manually.
- Whole loop: 1-3 days, sometimes a week.
The modern flow
- Order placed digitally; lab receives instantly.
- Result returns via API to the patient's chart automatically.
- Doctor sees a "new results" inbox the moment they land.
- If normal: auto-message to patient with result + interpretation; copy to chart.
- If abnormal: doctor reviews, decides; patient notified per protocol.
- Critical: instant alert to the doctor on call.
Lab integrations: API vs PDF
| Approach | Pros | Cons |
|---|---|---|
| API (HL7/FHIR) | Structured, fast, searchable | Requires lab and clinic-system support |
| PDF + manual attach | Universal | Slow, no structured data, error-prone |
| Portal scrape | Works without lab API | Fragile, breaks on portal redesigns |
Critical results: a different track
A potassium of 6.8 doesn't wait for tomorrow's review. Critical-result workflows must:
- Alert the on-call doctor immediately (SMS / push + escalation if unacknowledged).
- Bypass normal "doctor reviews tomorrow" queues.
- Log the alert and the response time for compliance.
- Have a documented escalation path if the primary doctor is unreachable.
Patient-facing delivery
- SMS / WhatsApp notification: "Your results are ready. Tap to view." (No PHI in the message itself.)
- Portal view: result + a one-paragraph plain-language interpretation.
- Option to message the clinic with questions.
- Automatic follow-up reminder if the patient doesn't open within 48 hours.
What to measure
- Median time from result-landing to patient-notified.
- Inbound "results?" call volume.
- Critical result acknowledgment time.
- Portal open-rate on result notifications.
- Result-related complaints (target: trending to zero).
FAQ
What if my lab won't do API?
Many won't yet — though the share is growing fast. A PDF-with-auto-attach workflow is the bridge; press your lab on their roadmap.
Can I send results before the doctor reviews?
For routine results, often yes — with appropriate disclaimers. For abnormal or complex results, a doctor pre-review is non-optional.
Are auto-interpretations safe?
For clearly-normal results, with conservative wording, yes. For anything ambiguous, route to the doctor.
How do I handle the patient who doesn't read the result?
Auto-reminders at 48 hours and 7 days. After that, a phone call from staff — at least for clinically important results.
What about lab results from outside labs?
Treat them like internal labs: structured intake, attached to chart, delivered via the same workflow. The patient doesn't care who ran the test.
Is this HIPAA / GDPR compliant?
If the notification itself contains no PHI and the portal access is properly authenticated, yes. Standard cloud-clinic-platform configuration handles it.
The summary
Lab result sharing is one of the easiest patient-experience wins available, and yet most clinics still treat it as a manual chore. Modern integrations, structured workflows, and patient-facing delivery turn a multi-day cycle into hours. Pair with our patient portal piece for the patient-side architecture.