HL7 and FHIR integration
End-to-end design and delivery of HL7 and FHIR integration across AU, NZ, and US profile ecosystems — R4/R5, AU Core, NZ Base, US Core, SMART on FHIR, subscription topics, and implementation guide authoring.
Services
What Basal does.
Five service lines, all delivered directly by the principal. Each engagement is sized so the work runs from architecture through to signed-off, in-production systems — not slide decks.
Clinical messaging architecture
Architecture for HL7 v2, FHIR messaging, and CDA across hospital, laboratory, and jurisdictional estates. Middleware reference designs covering Rhapsody, InterSystems, Mirth Connect, Iguana, Corepoint, and cloud-native alternatives.
Cross-agency data sharing
Federated and hub architectures for cross-agency and cross-jurisdiction health data sharing — Commonwealth-to-state exchanges (AU), national data pipelines (NZ), and US HIE/TEFCA connectivity. Information sharing agreements through to execution.
Cloud migration of integration estates
Lift legacy on-premises integration estates to AWS, Azure, or GCP without breaking clinical operations — phased cutovers, NZISM / IRAP alignment where applicable, and target-state architectures that reduce vendor lock-in.
Health IT governance — PIA, SRA, ATO
Privacy Impact Assessments, Security Risk Assessments, and Authority to Operate packages written to pass procurement and assurance review. NZISM, IRAP, HIPAA Security Rule, and jurisdictional privacy alignment.
How engagements work
Basal takes on a small number of engagements at a time. Most fit one of three shapes: a fixed-scope architecture or strategy deliverable (4–8 weeks), a principal-architect retainer on a programme of work (3–12 months), or an on-call advisory arrangement during a critical transition window.
All engagements are delivered directly by the principal. There is no junior team, no offshore practice, and no hand-off. Get in touch to discuss whether the work is a fit.