Malaffi health information exchange
We support Malaffi connectivity through Care and retain exchange acknowledgements, giving your team a record to review alongside the facility’s agreed connection scope.
Set by Department of Health, Abu Dhabi
What this is
Malaffi is the Abu Dhabi health information exchange, run under the Department of Health Abu Dhabi. A facility connects to it through onboarding with Malaffi; this page describes what Care provides on the facility’s side.
What is built
- Care includes a Malaffi connector for clinical exchange, built on HL7 v2 messaging over MLLP.
- Each outbound message is recorded in an exchange log with its status and the response received.
- Clinical information is drawn from the relevant Care patient and encounter context.
- Until a facility’s live connection is configured, the connector runs in a test mode that records the message and a synthetic acknowledgement without sending anything.
What a technical reviewer can inspect
Your team can review an exchange entry, the patient and encounter information used, and the response recorded against it. This is evidence about the transaction being examined. It does not show that every record was accepted or that the facility is activated, and a test-mode acknowledgement is not evidence of a live connection.
Illustrative example: one exchange message
This example uses synthetic data.
A synthetic patient, Omar Rahman, is seen in an outpatient encounter. Care builds the exchange message from the encounter and records it in the exchange log. When Malaffi answers, Care keeps the response against the same entry. If the response reports a problem, the entry keeps the error text for the team to read, and the facility decides who corrects the record and what happens next.
What the facility arranges
- The health data exchange pack, where licensed.
- Onboarding with Malaffi, including network access and credentials.
- The message profile and clinical content Malaffi requires for the facility’s services.
- Testing with representative records and agreed handling of any response needing attention.
Boundaries
The Malaffi page, the UAE market page and the interoperability page describe the same scope: Care provides the connector, and live activation depends on the facility’s own arrangements. Malaffi is a clinical exchange. It is separate from insurance claim submission and from incident reporting, and it does not demonstrate payer acceptance. No automatic rejection dashboard, escalation timer or guarantee of acceptance is claimed.
Official source: malaffi.ae
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
-
Care includes a Malaffi connector in its health data exchange scope. A facility still needs the health data exchange pack, licensing and onboarding with Malaffi before its deployment can be treated as activated.
-
Care’s Malaffi connector is built on HL7 v2 messaging. The exact message profile and content for a facility are agreed with Malaffi during onboarding, and Care’s general support for other formats does not change that.
-
Care retains acknowledgements in the described exchange workflow. Review the relevant response with the transaction and agree how your team interprets it and handles anything requiring attention.
-
Malaffi connectivity describes clinical information exchange. Insurance claims use their own workflows, plan scope and transaction routes; do not treat a clinical exchange as evidence of a settled or accepted claim.
Not answered here? Contact the team
NXH Flow