Compare
A pathology API or a direct HL7 integration?
Australian laboratories exchange orders and results as HL7 version 2 messages. A healthtech can integrate with each lab directly, or call one REST API that deals with the lab connections. Here is what differs.
Side by side
The first column describes direct integration as the HL7 guide sets it out. The second describes Eirly Health.
| Direct HL7 v2 integration | Eirly Health pathology API | |
|---|---|---|
| What you build against | HL7 v2.4 messages, as specified for Australian pathology by AS 4700.2 and HL7 Australia's localisation | REST endpoints that return structured JSON |
| Labs | A separate project for each laboratory, each with its own local codes, units, referral requirements and message habits | One integration; Eirly Health deals with the lab connections |
| Biomarker identity | Each lab's own local codes | One biomarker catalogue across labs, using LOINC codes where a lab sends them and each lab's own codes |
| Values and units | As each lab reports them | The lab's own value, unit and reference ranges, plus a canonical value in one agreed unit |
| Report text | In the lab's message | The lab's report text comes through whole, including reports with no individual biomarkers |
| New results | Your system receives and parses each message | A webhook notifies you, and you fetch the result with one authenticated call |
When a direct integration makes sense
If you work with one laboratory and already handle its HL7 messages, a direct integration keeps you closest to that lab. The work grows with each lab you add, because each one brings its own codes and habits.
What the API does not claim
Eirly Health does not claim FHIR support. For the standards themselves, read the HL7 pathology guide and the LOINC guide.
Keep reading
- Structured results or PDF reports?
What a structured result carries that a lab's PDF report does not, and when the PDF is enough.
- Lab results API
Results normalised across labs, with canonical values and the lab's own report text.
- HL7 for pathology in Australia
HL7 v2 messaging, AS 4700.2 and where a REST API fits.
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.