EirlyEirly
PartnersEirly APIPractitionersCatalogueAboutPricing
Sign inGet started

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.

Pathology APIRead the docs

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 compared with the Eirly Health pathology API
Direct HL7 v2 integrationEirly Health pathology API
What you build againstHL7 v2.4 messages, as specified for Australian pathology by AS 4700.2 and HL7 Australia's localisationREST endpoints that return structured JSON
LabsA separate project for each laboratory, each with its own local codes, units, referral requirements and message habitsOne integration; Eirly Health deals with the lab connections
Biomarker identityEach lab's own local codesOne biomarker catalogue across labs, using LOINC codes where a lab sends them and each lab's own codes
Values and unitsAs each lab reports themThe lab's own value, unit and reference ranges, plus a canonical value in one agreed unit
Report textIn the lab's messageThe lab's report text comes through whole, including reports with no individual biomarkers
New resultsYour system receives and parses each messageA 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.

Book a demoAPI access, pricing on request

EirlyEirly

Pathology and diagnostic infrastructure for practitioners and health brands.

Solutions

  • Partners
  • Telehealth services
  • Health brands and white label
  • Clinics and practitioners
  • Longevity clinics
  • Clinical trials
  • Research
  • At-home collection

Platform

  • Pathology infrastructure
  • Eirly API
  • Medicare pathology
  • Catalogue
  • How-to guides
  • Who can order tests
  • Pricing
  • API pricing

Developers

  • Pathology API
  • Lab results API
  • Pathology booking API
  • Lab testing API
  • Radiology API
  • MCP server
  • Guides

Company

  • About
  • Blog
  • Compliance
  • Contact

Legal

  • Privacy
  • Terms
  • Refunds

Our network

  • Pathology labs
  • Collection centres
  • Healius Pathology
  • Australian Clinical Labs
  • 4Cyte Pathology
  • Sonic Healthcare
  • NutriPATH
  • Microba
  • Fatty Acid Labs

Built in Australia. Global by design, local where it counts.

Eirly Health is a trading name of Bloody Good Tests Pty Ltd. Eirly provides data infrastructure and educational context. It does not provide medical advice, diagnosis or treatment. Pathology is requested by a registered practitioner and analysed by accredited or otherwise appropriately qualified laboratories. Practitioners using the platform are responsible for their own clinical and regulatory obligations.

© 2026 Bloody Good Tests Pty Ltd

Clients: sign in to view your results →