Every DHA-licensed facility in Dubai is required to exchange patient data with NABIDH, the Dubai Health Authority’s health information exchange. For most clinics this is the hardest part of going live: the licence depends on it, and it cannot be solved with a spreadsheet or a manual upload.
MedInsight handles it for you. Clinical events are transmitted to NABIDH automatically as your team works, using the DHA's required HL7 message formats and code sets. There is no separate integration engine to buy, no middleware for your staff to babysit, and no extra step at the end of a consultation. Your clinicians document care the way they normally would, and the NABIDH submission happens in the background.
NABIDH requirements scale with facility type. A single-specialty clinic sends a different set of events than a hospital with inpatient wards.
MedInsight covers the full NABIDH requirement set for outpatient facilities, up to and including polyclinics. That means single-specialty clinics, specialty clinics, medical centres and multi-specialty polyclinics licensed by the DHA.
Inpatient, day surgery and emergency department event sets sit outside our current certified scope. If your facility operates at that tier, talk to us about your roadmap before you commit.
| Event | HL7 message | What is transmitted |
|---|---|---|
| Add person record | ADT^A28 | Creation of a patient record ahead of any visit: demographics, Emirates ID, nationality, contact details, MRN |
| Update person record | ADT^A31 | Corrections and additions to person-level demographic data |
| Update patient and visit information | ADT^A08 | Changes to an existing patient or an existing encounter |
| Register patient / start of visit | ADT^A04 | Outpatient registration with full encounter context: visit number, attending and referring clinician, insurance, allergies, diagnoses, procedures and recorded observations |
| Cancel registration | ADT^A11 | Reversal of a visit registered in error |
| End of visit | ADT^A03 | Closure of the outpatient encounter, with final diagnoses and procedures |
| Merge patient identifiers | ADT^A40 | Consolidation of duplicate patient records |
| Problem list | PPR^PC1 | Active and resolved problems with onset, status and coded problem detail |
| Clinical document | MDM^T02 | Original document and its content: consultation notes, procedure notes, history and physical, reports |
| Clinical document revision | MDM^T08 | Edited or replaced version of a previously submitted document |
| Prescription / medication order | OMP^O09 | Drug (Dubai Drug Code), dose, route, frequency, duration, prescriber and order status |
| Segment | Carries |
|---|---|
| MSH | Message header, including the sending facility's Sheryan unique ID |
| EVN | Event type and event facility |
| PID | Patient identification: Emirates ID, with passport and GCC number as fallbacks, plus MRN and demographics |
| PV1 | Encounter details: visit number, patient class, attending, referring and consulting clinician (Sheryan IDs) |
| IN1 | Insurance and coverage details |
| AL1 | Allergies and intolerances, with reaction and severity |
| DG1 | Diagnoses, ICD-10-CM coded, admitting, working and final |
| PRB | Problem detail for problem list messages |
| PR1 | Procedures, CPT-4 coded, and CDT coded for dental |
| OBX | Observations and measurements: vitals, height, weight, and structured document content |
| ORC | Common order control for medication orders |
| RXO | Pharmacy and treatment order detail, Dubai Drug Code |
| TXA | Document metadata: type, availability, completion and authentication status |
| MRG | Merge information for patient record consolidation |
| ZSC, ZSH, ZFH | NABIDH extension segments |
| Event set | Reason |
|---|---|
| Inpatient admission and transfer (ADT^A01, A02) | Hospital tier |
| DRG and bed management | Hospital tier |
| Emergency department reporting | Hospital tier |
| Standalone laboratory and radiology result messages (ORU) | Not part of the polyclinic scope certified to date |
| Immunisation messages (VXU) | Not part of the polyclinic scope certified to date |
| Pharmacy dispensing messages (RDE, RXE) | MedInsight submits the prescription order, not the dispensing event |
| C-CDA document exchange (ITI-41, ITI-44) | MedInsight submits via HL7 v2.5 messaging |
MedInsight is built as a multi-specialty platform, so a polyclinic running six departments submits to NABIDH from a single patient record rather than six disconnected systems.
| Field of medicine | Coding applied | Notes |
|---|---|---|
| General practice and family medicine | ICD-10-CM, CPT-4, DDC | Full consultation, prescription and referral flow |
| Dental | ICD-10-CM, CDT (ADA) | Dental procedures are coded to CDT as required by DHA, including tooth and surface level charting |
| Dermatology and aesthetics | ICD-10-CM, CPT-4 | Procedure records and treatment notes submitted as clinical documents |
| Obstetrics and gynaecology | ICD-10-CM, CPT-4 | Encounter, diagnosis and procedure reporting, with reports submitted as documents |
| Paediatrics | ICD-10-CM, CPT-4, DDC | Growth measurements and observations submitted with the encounter |
| Internal medicine | ICD-10-CM, CPT-4, DDC | Chronic disease follow-up with an ongoing coded problem list |
| Cardiology (outpatient) | ICD-10-CM, CPT-4 | Diagnostic findings submitted as clinical documents |
| Orthopaedics | ICD-10-CM, CPT-4 | Procedures and follow-up encounters |
| ENT | ICD-10-CM, CPT-4 | Procedures and consultation notes |
| Ophthalmology | ICD-10-CM, CPT-4 | Procedures and consultation notes |
| Physiotherapy and rehabilitation | ICD-10-CM, CPT-4 | Session records submitted as progress notes |
| Nutrition and dietetics | ICD-10-CM | Measurements and assessments submitted as observations |
| Psychiatry and psychology | ICD-10-CM, CPT-4, DDC | Handled under NABIDH restricted confidentiality coding |
MedInsight submits using the standards the DHA mandates, not a generic international profile:
NABIDH connectivity is a condition of holding and renewing a DHA licence, so it cannot be treated as an optional module. What matters in practice is not only that messages leave your system, but that they are accepted. MedInsight surfaces rejected messages, corrects and resubmits them, rather than letting failures accumulate silently until an audit finds them.
New clinics typically move from onboarding to NABIDH go-live in a matter of weeks, and existing clinics migrating from another system keep their historical records intact.
If you are opening a clinic or polyclinic in Dubai, or you are moving off a system that is causing NABIDH rejections, we can walk you through exactly which events your facility type has to submit and how MedInsight handles each one.
