Health Data Exchange
Know what reached the exchange, and what needs attention
NextHealth Care
NextHealth Care
Applicable regulatory integration pack; available with any Care plan subject to confirmed scope and onboarding.
NXH Care health data exchange sends clinical information to regional health information exchanges and keeps the response. Adapters are built for Malaffi and Riayati over HL7 v2.5.1 and for NABIDH over FHIR R4. Each exchange is recorded with its status, from queued to sent to acknowledged, and a failed exchange can be retried from the exchange monitor. Whether a facility is connected depends on its regulatory pack, licence, credentials and onboarding with the exchange, agreed before deployment.
Agree the exchange, send it and follow the response
-
Step 1
Agree scope
Confirm the exchange, pack and data types
-
Step 2
Send
Care queues the exchange to the facility’s exchange
-
Step 3
Keep the response
The acknowledgement is stored with the exchange
-
Step 4
Follow up
Review failures and retry them
What your team can do
- Send clinical information to Malaffi and Riayati over HL7 v2.5.1.
- Send clinical information to NABIDH over FHIR R4.
- Choose which data types each facility shares.
- Track each exchange from queued to sent to acknowledged, or failed.
- Retry failed exchanges automatically, then manually from the monitor.
- Inspect the message payload and the response for each exchange.
Agree the exchange before you plan the connection
Supporting a protocol does not connect a facility. Care has adapters for Malaffi in Abu Dhabi (HL7 v2.5.1 over MLLP), NABIDH in Dubai (FHIR R4) and Riayati (HL7 v2.5.1 over MLLP). Each runs against a sandbox by default, which records the exchange and a test acknowledgement. A live connection needs the exchange’s credentials and onboarding for the facility, the matching regulatory pack, and agreement on which data types the facility shares. A facility is not connected to a national exchange until that work is done.
What you can review after an exchange
The exchange monitor lists each exchange by patient, type and status: queued, sent, acknowledged, failed or retrying. It shows the attempts, any error and the message payload. A failed exchange is retried automatically with a delay between attempts. After the last attempt it stays failed until a user with the right permission retries it. Deciding what to do about a rejected message stays with your team.
Illustrative example: an exchange that failed and was retried
This example uses synthetic data.
For a synthetic patient, Lena Sample, Care queues an encounter exchange to the facility’s configured exchange. The monitor shows it as sent, then acknowledged, with the exchange’s message identifier. A second synthetic exchange fails because the exchange cannot be reached. Care retries it after a delay, and when the final attempt fails the monitor keeps it as failed with the error text. An authorised user checks the cause and queues it again from the monitor.
Prerequisites by country
Claims routes are separate from clinical exchanges. See the interoperability scope for how each route is handled, and the market pages for what each country needs.
Related NXH Care modules
2 more modules
Common questions
-
Health data exchange is available through the Care regulatory pack where licensed. Confirm the required exchange and deployment scope for your facility before selecting the pack.
-
Care has adapters for Malaffi and Riayati over HL7 v2.5.1 and for NABIDH over FHIR R4, and keeps the response for each exchange. Confirm the exchange that applies to your facility and the data types to share as part of the technical scope discussion.
-
No. A facility uses the adapter that matches its regulator and licence, through the matching regulatory pack, and it is connected only after onboarding is complete. There is no NPHIES connection for Saudi Arabia.
-
The exchange monitor shows each exchange’s status, attempts, any error, the message payload and the stored response. Ask the technical team to demonstrate a representative exchange and a failed one within the scope proposed for your facility.
Not answered here? Contact the team
NXH Flow