Skip to Content
العربيةBook a demo
Solutions
Platform
Integrations
Security & Delivery
Resources
Company
Book a demo

Riayati integration for UAE healthcare facilities

Riayati is the national unified medical record programme of the UAE Ministry of Health and Prevention. This is what is public, what we could not find for software vendors, and how Ventrecs prepares a facility.

What Riayati is

Riayati is the national unified medical record programme run by the UAE Ministry of Health and Prevention. It sits at federal level, next to the emirate-level exchanges: Malaffi in Abu Dhabi and NABIDH in Dubai.

The Ministry has announced an integration between Riayati, Malaffi and NABIDH. For a facility, that does not remove its own obligations: each facility still onboards with the authority that licenses it.

At a glance
Where
UAE, federal level
Run by
The Ministry of Health and Prevention
Programme
National unified medical record
Related platforms
Malaffi in Abu Dhabi and NABIDH in Dubai
Public vendor documentation
None found: no public technical onboarding specification
Riayati

Who this affects

Facilities under the Ministry of Health and Prevention, and groups that operate across emirates.
Facilities in Abu Dhabi and Dubai, which onboard through Malaffi and NABIDH respectively.
Software vendors, who should ask the Ministry whether a technical onboarding path exists.
Riayati

What data is exchanged

Unified medical recordThe programme is a national unified medical record. The public pages do not list the data categories a vendor must send.
What a vendor must sendNot publicly specified. Ask the Ministry which identifiers, messages and code sets apply.
What Ventrecs holdsPatient identity, encounters, orders, results, prescriptions and discharge documents, recorded as events in the patient record.
Riayati

What we could and could not verify

What is public

The programme pages describe the purpose and the operator.

  • A national unified medical record programme
  • Run by the Ministry of Health and Prevention
  • An announced integration with Malaffi and NABIDH

What we did not find

We looked for the documentation a vendor builds against.

  • No public technical onboarding specification
  • No public sandbox or message specification
  • No public list of required message types

Questions for the Ministry

Ask in writing before scoping any work.

  • Which facilities must connect, and when?
  • Is there a system-to-system option, and under which agreement?
  • Which standard, identifiers and code sets apply?
Riayati

How Ventrecs prepares

One identityEnterprise patient identity with duplicate review, so that a record sent to any exchange refers to one person.
Clinical eventsMovements, orders, results, prescriptions and discharge documents recorded as events in the patient record.
Country starter packA UAE starter pack of regional settings exists and must be reviewed against current regulation before use.
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 Riayati, 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

Riayati

Typical rollout steps

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

  1. 1
    DiscoverConfirm with the Ministry of Health and Prevention 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 Ministry of Health and Prevention 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 Ministry of Health and Prevention where the operator requires it.
  8. 8
    HypercareClose monitoring in the first weeks, then hand-over to the agreed support process.
Riayati

Sources

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

Riayati

Questions we are asked

What is Riayati?

The national unified medical record programme of the UAE Ministry of Health and Prevention.

Do we still connect to Malaffi or NABIDH?

Yes. Each facility still onboards with the authority that licenses it, even with an announced integration between the platforms.

Is there a public specification for software vendors?

We found none. Ask the Ministry whether a technical onboarding path exists.

Can Ventrecs connect us to Riayati?

Yes, as a project. Ventrecs Connect carries the messages through an integration layer with retry, a transaction log and a reconciliation queue. Once the Ministry provides the specification and access, we scope, build and test the connection with you.

Talk to us about your setup

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