HL7 FHIRDesign reference
FHIR R4 exchange baseline
Health Level Seven Fast Healthcare Interoperability Resources Release 4 is the stated public baseline for approved clinical exchange contracts.
Standards without lock-in
A common language for systems that already exist.
PHX uses governed interfaces, versioned profiles, shared terminology, and conformance evidence to help diverse systems exchange information reliably.
Exchange foundations
Standards are precise commitments—not a logo wall
Legacy integrationRoadmap
Meet existing systems where they are
Approved adapters can support bounded legacy exchange while the country moves toward governed profiles.
ImagingRoadmap
DICOM-aware integration
Digital Imaging and Communications in Medicine is referenced for imaging exchange where implemented and tested.
Open interfacesIn validation
Versioned APIs and events
Public contracts should use bounded, versioned, documented interfaces with acknowledgements and traceability.
Meaning and quality
Exchange is useful only when systems understand the data
Clinical terminology
SNOMED CT references, where appropriately licensed and governed, can support consistent clinical meaning.
Laboratory observations
LOINC references, under applicable licence terms, can support shared laboratory and observation identifiers.
Classification
ICD classifications can support authorized reporting and morbidity use cases under the applicable source and licence rules.
Country code sets
National and local code sets remain important and are governed through approved mapping and version policy.
Conformance
Participation must be testable
Declare
Publish the supported version, use case, profile, and security obligations.
Validate
Check structure, meaning, required fields, and country rules.
Exercise
Test happy paths, rejection, retries, acknowledgements, and recovery.
Monitor
Track exchange health and data quality without exposing sensitive content.
PHX does not claim certification by standards bodies unless a named, valid, independently verifiable certification exists for an exact scope.
Technical engagement
Connect through a governed country context.
Vendors and implementers can begin with a defined use case, supported contract, and conformance-readiness discussion.