Australian privacy and sovereignty rules shape the orchestration boundary
Australian health workflows cannot be designed as if location and disclosure do not matter. Cross-border disclosure controls, national assurance expectations, and service-by-service compliance scope directly affect which architecture choices are acceptable.
A practical lesson from current AWS documentation is that teams should validate assurance scope for each chosen service. The AWS services-in-scope list for IRAP is authoritative for current inclusion, while the HealthImaging compliance documentation points teams back to those programmatic scope listings and to HIPAA eligibility guidance.
APP 8 - cross-border disclosure of personal information
OAIC guidance on the Australian Privacy Principles rule governing cross-border disclosure decisions.
Review APP 8 guidanceAWS services in scope by compliance program - IRAP
AWS services-in-scope page used to confirm the current IRAP coverage of the exact services selected in the design.
Check current IRAP scopeAWS HealthImaging compliance validation
HealthImaging documentation describing how to review its compliance posture and where to confirm program coverage.
Review HealthImaging compliance guidanceHealthcare Identifiers are part of the orchestration contract
Australian digital-health exchange depends on national identifiers. For orchestration, the core pattern is that patient, clinician, and organisation identity should be stable and traceable across routing, reporting, and downstream exchange actions.
Identifier types architects usually need to model
| Identifier | Represents | Workflow use |
|---|---|---|
| IHI | Individual receiving care | Matches clinical and imaging artifacts to the right person |
| HPI-I | Individual healthcare provider | Supports routing, authorship, and exchange accountability |
| HPI-O | Healthcare provider organisation | Anchors organisation identity in national exchange and service context |
Healthcare Identifiers Integration Toolkit
ADHA implementation toolkit for Healthcare Identifiers integration, onboarding, and supporting resources.
Review the HI integration toolkitHPI-O namespace guidance
Australian Digital Health Agency namespace reference for HPI-O identifier representation.
Review HPI-O namespace detailsPublication to My Health Record is its own orchestration lane
National publication is not just another outbound interface. The orchestrator has to decide whether the report is eligible for upload, which practitioner and organisation identifiers should be asserted, whether the content is final enough to publish, and what to do if the national-service submission fails after the local report was already signed.
Publication decisions that should be explicit workflow state
| Decision | Why it matters | Typical evidence |
|---|---|---|
| Upload eligibility | Not every locally available result should be published at the same time or in the same way | Final-report status, service rules, and policy configuration |
| Authoring identity | National publication depends on stable provider and organisation identifiers | HPI-I and HPI-O resolution before submission |
| Visibility timing | Consumer visibility may follow rules that are distinct from successful upload | Configured delay, exemptions, or product release behavior |
My Health Record B2B Gateway upload document
ADHA implementer guidance for the upload-document interaction used to publish content into My Health Record.
Review the upload-document interactionMy Health Record upload and visibility rules are separate workflow concerns
As of Thursday, March 12, 2026, ADHA guidance for impacted providers says the share-by-default requirement for written pathology and diagnostic imaging reports starts on July 1, 2026, and that upload requirement does not include images. Separately, My Health Record Release 26.1.0 was deployed to production on March 5, 2026 and documented in vendor release notes published on March 10, 2026. Those release notes changed the consumer delay behavior for diagnostic imaging so limb x-ray reports are available immediately and other diagnostic imaging reports are visible after five days rather than seven.
Architecturally, that means the orchestrator should distinguish “uploaded to My Health Record,” “visible to consumer now,” and “future share-by-default policy obligation.” Those are related, but they are not the same state. Upload state, visibility delay, exemptions, and remediation should all be explicit workflow decisions rather than implied assumptions.
Use exact current guidance for timing rules
National exchange timing rules are time-sensitive. Build the workflow so timing can be configured and updated without rewriting the whole orchestration path.
Better and Faster Access guide for pathology and diagnostic imaging providers
ADHA guide for impacted providers that states the 1 July 2026 commencement date and clarifies that the upload requirement applies to written reports, not images.
Review the impacted providers guideMy Health Record Release 26.1.0 vendor release notes
ADHA vendor release notes for the production release deployed on March 5, 2026, including the March 10, 2026 publication note about diagnostic-imaging delay changes.
Review Release 26.1.0 notesKnowledge Check
Test your understanding with this quiz. You need to answer all questions correctly to mark this section as complete.