Compare
Structured pathology results or PDF reports?
A lab's PDF report is written for a person to read. A structured result is written for software as well. If you store, chart or compare results across labs, the difference matters.
Side by side
| PDF report | Structured result from Eirly Health | |
|---|---|---|
| Made for | A person reading it | Software, and the people using it |
| Layout | Each lab's own | One JSON shape, whichever lab produced the result |
| Biomarker names | As each lab names them | Mapped to one biomarker catalogue, using LOINC codes where a lab sends them |
| Units | As each lab reports them | The lab's own value and unit, plus a canonical value in one agreed unit |
| The lab's words | The whole report | The lab's report text comes through whole, alongside the values |
| Getting it into your product | Read it, or extract the values yourself | Fetch it with one authenticated call when a webhook says it is ready |
When a PDF is enough
If a practitioner only needs to read one report, the PDF does the job. Structured results earn their keep when results are stored, charted, compared across labs or passed to other software.
Why units and names need mapping
Laboratories name the same test differently and report it in different units, so storing each result exactly as received can mix scales in one client's series. The LOINC guide explains how mapping works, and the test catalogue lists the biomarkers each test reports.
Keep reading
- A pathology API or a direct HL7 integration?
What differs between integrating with each lab's HL7 messages and calling one REST API.
- Lab results API
Results normalised across labs, with canonical values and the lab's own report text.
- Pathology API
Referrals, results, webhooks, bundles and collection centres in one REST API.
Build on the Eirly Health API.
Start in the staging environment with its own keys, then talk to us about production access. Pricing is on request.