Skip to Content

Malaffi integration for Abu Dhabi clinics, laboratories and hospitals

Malaffi is the health information exchange of Abu Dhabi. This is who has to connect, what it takes to become a connected participant, and how Ventrecs scopes the connection for a facility.

What Malaffi is

Malaffi is the health information exchange of Abu Dhabi. It is operated by Abu Dhabi Health Data Services for the Department of Health, and it lets licensed facilities share clinical information about a patient, so that a clinician in one facility can see what another has recorded.

For a facility, Malaffi is two things at once: a source its EMR sends clinical events to, and a viewer its clinicians open from inside the EMR.

At a glance
Where
Abu Dhabi
Operated by
Abu Dhabi Health Data Services, for the Department of Health
Carries
Clinical information shared between licensed facilities
Connected participant
Malaffi available inside the EMR through single sign-on, and real-time ADT messages
Published
Facilities required to connect, onboarding requirements, connected-status criteria
Malaffi

Who needs to connect

Hospitals, and medical, dental, one-day surgery and primary healthcare centres.
Clinics, imaging and laboratory diagnostic centres, dialysis and IVF centres, pharmacies, home care and telemedicine providers.
Some categories are exempt, such as military, police, aviation and university facilities. Check your facility type against the current list.
Malaffi

What data is exchanged

Patient identityConsistent identifiers, so that the exchange can join records to one person.
EncountersAdmission, discharge and transfer messages sent in real time, when the event is saved.
Clinical contentNot fully public. Ask the onboarding team for the message set and test steps at the start.
Single sign-on linkMalaffi opens inside the EMR, so a clinician reaches it in one click.
Malaffi

What connecting involves

Onboarding requirements

Malaffi describes onboarding as a series of steps that can take several months, depending on technical readiness.

  • The Accession Agreement and the Facility Declaration
  • The Malaffi Security Assessment
  • An EMR that can exchange HL7 messages, and an SD-WAN connection from the telecom provider

Connected participant

Malaffi distinguishes joining from connecting. A facility connects when it meets two criteria.

  • Embedded mode: Malaffi opens inside the EMR through single sign-on
  • Real-time ADT: admission, discharge and transfer HL7 messages sent when the event is saved

What the EMR has to do

The capabilities that decide the effort.

  • Movement events raised the moment they are saved
  • Consistent patient identity and duplicate control
  • Shared codes, and monitoring so that silent failures are caught
Malaffi

How Ventrecs handles it

Patient movementsAdmissions, discharges and transfers are recorded as part of the encounter, which is the source of the events Malaffi needs.
Patient identityEnterprise patient identity with a duplicate-review queue, and clinical records with an audit trail.
Sensitive patientsSensitive patients are marked so that release rules can respect them.
Durable outboxMessages leave through an outbox with retry, a transaction log and a reconciliation queue, so a deferred, rejected or missing response is a visible state with an owner.
How the connection is delivered

Each connection is delivered as a project: scoped with your facility and Malaffi, built as an interface adapter on the Ventrecs integration layer, tested in the operator's environment and signed off before go-live. Where the operator requires approval or certification, it is part of the project plan.

Messages are carried by Ventrecs Connect. See how an integration is delivered, from scoping to monitoring. Ventrecs Connect · The integration lifecycle

Malaffi

Typical rollout steps

The same eight stages as every Ventrecs deployment, applied to this connection. How we deliver

  1. 1
    DiscoverConfirm with the Malaffi onboarding team which of your facility types must connect, and which messages or transactions apply.
  2. 2
    DesignAgree the message set, identifiers and code mappings, and name an owner for each interface.
  3. 3
    ConfigureSet up facilities, users, catalogues and the integration layer, with credentials held outside the clinical records.
  4. 4
    MigrateLoad the master data the exchange needs, such as facilities, clinicians and patient identifiers, and reconcile it.
  5. 5
    TestTest in the environment the Malaffi onboarding team provides, with synthetic data, including rejected and duplicate messages.
  6. 6
    TrainTrain the teams who watch the interface and fix the rejections.
  7. 7
    Go-liveCut over in phases with on-site support, and with sign-off from the Malaffi onboarding team where the operator requires it.
  8. 8
    HypercareClose monitoring in the first weeks, then hand-over to the agreed support process.
Malaffi

Sources

Operator and standards documents these statements rest on. Standards change, so work from the current version.

Malaffi

Questions we are asked

Who has to connect to Malaffi?

Most DOH-licensed facilities, including hospitals, clinics, diagnostic centres, dialysis and IVF centres, pharmacies, home care and telemedicine providers. Some categories are exempt, so check the current list.

What does connected participant mean?

The facility has made Malaffi available inside its EMR through single sign-on, and its EMR exchanges ADT messages with Malaffi in real time.

How long does onboarding take?

Malaffi says it can take up to several months, depending on the technical readiness of the participant.

Can Ventrecs connect us to Malaffi?

Yes. We deliver the connection as a project with your facility and the Malaffi onboarding team: Ventrecs Connect carries the messages through an integration layer with retry, a transaction log and a reconciliation queue. The interface is built and tested before go-live, and the go-live plan is agreed with you.

Talk to us about your setup

Tell us about your facility and current systems. We will reply within one working day.