From the Health & Human Services edition of November 10, 2026
Abu Dhabi Department of Health puts an AI physician assistant into its Malaffi health information exchange for all physicians in the emirate
Department of Health - Abu Dhabi, with Abu Dhabi Health Data Services (M42) · Public health authority and health information exchange · Abu Dhabi, United Arab Emirates
- Publisher
- Emirates News Agency (WAM)
- Original publication
- 2026-11-10
- Source retrieved
- 2026-11-11
What happened
The Department of Health - Abu Dhabi and M42's Abu Dhabi Health Data Services integrated an AI physician assistant into Malaffi, the emirate's health information exchange, for all physicians. It retrieves record information, summarizes health histories and answers queries, drawing on records for more than 14 million patients and over four billion clinical records. It runs on M42's Ossi platform on Microsoft Azure in the UAE. Physicians keep clinical decisions, access follows approved permissions, and usage and feedback will be evaluated.
Why it matters
U.S. state-designated HIEs and public health agencies considering AI summarization over exchange data can see a government-run deployment at scale; transferability is limited by UAE governance and a single regulator.
Evidence and measured results
WAM (Nov. 10, 2026) relays the Department of Health announcement with statements from M42 and ADHDS executives.
Limitations and uncertainty
Government announcement relayed by state media; no accuracy, usage or time-savings data; vendor and regulator are closely linked.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-10; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Clinicians spend time searching fragmented exchange records for relevant patient history.
- Stakeholders
- State HIE executives
- Public health informatics leaders
- HIE participant CMIOs
- Discovery questions
- Do your HIE participation agreements allow AI processing?
- How would you log and audit AI queries?
- What accuracy threshold would clinicians accept?
- Value hypothesis
- Summarization over exchange data could cut record-search time if accuracy and audit controls hold.
- Potential engagement
- HIE AI readiness review plus a limited summary-accuracy pilot with a few participant practices.
- Unsupported claims
- Time savings achieved
- Accuracy levels
- Applicability to U.S. HIE governance without changes
Pre-sales engineering
Role takeaway
- Fit
- Read-only summarization and Q&A layer over a health information exchange.
- Architecture and integration
- HIE record retrieval under existing permissions, summarization model in in-country cloud, physician-facing interface.
- Prerequisites
- Participation agreements allowing AI use
- Per-query audit logging
- Accuracy test set
- Constraints
- U.S. HIE governance differs across states
- Data residency and BAA requirements
- No published accuracy data
- Security
- Enforce existing access permissions, log each query, and restrict model training on exchange data.
- Proof of value
- Summary accuracy against source records
- Clinician correction rate
- Time to find key history items
Delivery
Role takeaway
- Work
- Update agreements, configure logging, run an accuracy pilot, gather feedback and expand in phases.
- Dependencies
- HIE participants
- Cloud hosting agreements
- Clinical review panel
- Ownership
- HIE executive director, with participant clinical leads.
- Skills and adoption
- Physicians need guidance on verifying AI summaries against records.
- Governance checkpoints
- Pre-release accuracy review
- Quarterly error review
- Privacy review of logging and retention
- Acceptance criteria
- Summary accuracy meets an agreed threshold (proposed)
- All queries logged and auditable (proposed)
- Feedback loop reviewed monthly (proposed)
- Risks
- Hallucinated or incomplete summaries
- Privacy exposure across a large dataset
- Vendor and regulator conflicts of interest
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
AI assistant layered on a regional HIE, hosted in in-country cloud, using existing access permissions for retrieval.
Governance
Who approves, reviews and stays accountable for outcomes?
Physician accountability retained; permissions and data protection requirements apply; evaluation plan described only generally.
Security and privacy
What data, permissions and controls need testing?
In-country cloud hosting and access permissions are stated; no detail on logging, retention or model data use.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Aims to give physicians more time for patients.
Procurement
What should contracts, pricing and exit terms secure?
Delivered by a state-linked platform company rather than open procurement.
Operating model
Which teams own the service once it runs?
Moves AI capability to the exchange level, serving all physicians at once.
Publication history
- 2026-11-10Health & Human Services · Issue 116 resources
Stable resource ID: abu-dhabi-doh-malaffi-ai-physician-assistant-hie-20261110