Interoperability and the Australian Digital Health Mandate
The historical architectural isolation of monolithic PACS environments has resulted in deeply fragmented patient histories across the healthcare spectrum. State governments have embarked on massive consolidation projects, but the most sweeping architectural shift is occurring at the federal level.
My Health Record Evolution
The My Health Record system has evolved significantly since its inception, transitioning from an opt-in model to opt-out, and now to mandatory sharing by default for diagnostic imaging reports.
My Health Record Share by Default timeline
| Date | Event | Detail |
|---|---|---|
| July 2012 | My Health Record launched | Initially called Personally Controlled Electronic Health Record (PCEHR) |
| July 2016 | Opt-out trial begins | Transition from opt-in to opt-out model tested |
| July 2019 | National opt-out implementation | All Australians automatically enrolled unless opted out |
| 2023 | Share by Default legislation passed | Health Legislation Amendment Act 2023 |
| 1 July 2026 | Share by Default commences | Mandatory diagnostic imaging report uploads |
| 2027+ | Full image sharing consideration | Potential expansion to include DICOM images |
1 July 2026 Compliance Deadline
Australian imaging providers must ensure their clinical software conforms to ADHA standards and can interface with the MHR B2B gateway by 1 July 2026 to claim Medicare benefits.
FHIR Resources for Medical Imaging
FHIR R4 defines several resource types specifically designed for representing medical imaging data and reports in a standardized, interoperable format.
FHIR resource types for imaging workflows
| Resource | Description | Imaging Relationship |
|---|---|---|
| DiagnosticReport | Radiology report with conclusions and impressions | References associated ImagingStudy |
| ImagingStudy | Metadata about imaging series and instances | References DICOM metadata without pixels |
| Media | Renders images or videos | Can contain rendered key images |
| ServiceRequest | Order for imaging procedure | Links order to performed study |
| Observation | Measurements from imaging (e.g., tumor size) | Structured findings from report |
IHE XDS-I Architecture Flowchart
The following architecture diagram illustrates the IHE Cross-Enterprise Document Sharing for Imaging (XDS-I) profile with Document Registry and Repository:
IHE XDS-I Architecture: Document Registry + Repository
Loading diagram...
XDS-I Profile
IHE XDS-I (Cross-Enterprise Document Sharing for Imaging) enables secure sharing of medical images and reports across healthcare enterprises. The Document Registry maintains metadata indexes while Document Repositories store the actual DICOM objects.
FHIR vs HL7 v2 for Imaging
While HL7 v2 ORU^R01 messages have been the traditional method for transmitting radiology reports, FHIR DiagnosticReport resources offer significant advantages including RESTful API access, JSON formatting, and native web integration.
HL7 FHIR R4 Specification
Fast Healthcare Interoperability Resources R4 standard documentation
Read moreFHIR Imaging Resources
FHIR resources for medical imaging - DiagnosticReport, ImagingStudy, Media
Read moreArchitecting Interoperability: HL7 v2 to FHIR Conversion
To meet aggressive national integration goals, the global healthcare IT industry is transitioning away from legacy HL7 v2.x pipe-delimited messaging toward Fast Healthcare Interoperability Resources (FHIR).
Mirth Connect operates on highly available Amazon EC2 instances, acting as a universal translator. The engine listens continuously for incoming legacy HL7 v2 messages via MLLP or secure VPN/Direct Connect.
Once ingested, Mirth utilizes a JavaScript-based transformation layer to parse pipe-delimited payloads, map clinical data fields, and restructure data into fully compliant FHIR R4 JSON resources.
HL7 v2 to FHIR Conversion Architecture on AWS
Loading diagram...
HL7 Australia FHIR Implementation Guide
Australian FHIR profiling and implementation guides for local healthcare
Read moreConstructing the Multimodal Healthcare Data Lake
By successfully converting siloed HL7 data to FHIR and centralizing it within HealthLake, AWS Solution Architects can construct what is known as a "multimodal data lake".
In a multimodal architecture, rich textual clinical metadata stored in HealthLake is intrinsically linked via unique patient identifiers with massive DICOM pixel data stored in AWS HealthImaging, and complex genomic sequences stored in AWS HealthOmics.
Single Source of Truth
Utilizing AWS Lake Formation and Amazon Athena, researchers can execute complex SQL queries across all three modalities simultaneously without duplicating underlying petabytes of data, establishing a single, highly governed source of truth.
Cross-Enterprise Image Sharing Sequence
The following sequence diagram illustrates the Document Query → Retrieval workflow for cross-enterprise image sharing:
Cross-Enterprise Image Sharing: Document Query → Retrieval
Loading diagram...
Australian Context
The My Health Record Share by Default mandate (1 July 2026) implements a form of cross-enterprise sharing at national scale. Diagnostic imaging reports uploaded to MHR become accessible to any authorized healthcare provider across Australia.
External References
For further reading on healthcare interoperability and FHIR standards:
AWS HealthLake
Fully managed FHIR R4 data store with NLP inference for ICD-10, SNOMED CT, RxNorm
Read moreHL7 Australia FHIR Guides
Australian FHIR implementation guides and local profiling resources used for My Health Record integration.
Visit HL7 Australia FHIRKnowledge Check
Test your understanding with this quiz. You need to answer all questions correctly to mark this section as complete.