HL7 FHIR R4
We support FHIR R4 exchange through Care, with message acknowledgements available for review within the receiving system and transaction scope agreed for your facility.
Set by HL7 International
Subject type: technical format. HL7 FHIR R4 is a standard for exchanging health data as resources, published by HL7 International. This page states what Care builds. Standard support is not national onboarding.
What Care builds
- Care builds FHIR R4 resources including Patient, Encounter, Appointment, ServiceRequest, Condition, Observation, Immunization, AllergyIntolerance, Procedure, DocumentReference, Coverage and CarePlan.
- The exchange to NABIDH sends patient demographics, encounters with diagnoses and vital signs, allergies, medications, laboratory results, radiology reports, referrals and immunisations.
- Procedure and clinical document resources are built but not yet enabled for exchange.
- The operation is creating individual resources, from Care to the exchange. Each exchange keeps the response that came back.
Profiles, authentication and prerequisites
Profiles and authentication are set by each exchange during onboarding. Conformance to an exchange’s implementation guide is confirmed in that testing, so this page makes no profile claim. Until a facility has credentials, a test mode records the message and a placeholder acknowledgement. Each national connection needs its own onboarding. Malaffi and Riayati use HL7 version 2, not FHIR.
Illustrative example: a resource and its response
This example uses synthetic data. Care builds a Patient resource for a synthetic patient, Noor Al Mansoori, and sends it to the exchange endpoint. If the exchange accepts it, Care stores the identifier it returns on the exchange record and shows it as acknowledged. If the exchange answers with an error, the record shows a failed status with the response code and message, and it can be sent again once the cause is fixed. The example shows how Care records the outcome. It does not show a live connection.
Official source
HL7 FHIR R4. No universal FHIR endpoint compatibility, complete resource coverage or national connection is claimed.
What we claim, precisely
The system holds the evidence; the facility's accountable person attests. Nothing here asserts that a facility is compliant.
Common questions
-
Confirm the resources, operations and receiving implementation guide for the proposed connection. FHIR R4 support does not establish universal coverage of every resource or a ready connection to any endpoint.
-
No. FHIR R4 is the format Care uses for NABIDH. Malaffi and Riayati use HL7 version 2. Each connection needs onboarding, credentials and testing with that exchange.
-
Each exchange sets its own authentication and implementation guide profiles during onboarding. Care’s conformance to them is confirmed in that testing, so this page makes no profile claim.
Not answered here? Contact the team
NXH Flow