Illustrative Scenarios

Several hospitals run different record systems. Clinicians cannot easily see a patient's history from another site, and the group must exchange data with its health authority's platform.

• One patient index across the hospitals
• An integration layer using HL7 v2 and FHIR
• A planned connection to NABIDH or Malaffi, depending on the emirate
• Hosting inside the UAE, as the law requires

• Time for a clinician to find an outside result
• Duplicate patient records
• Failed or delayed interface messages
• Records successfully shared with the exchange

Baselines are measured in discovery, so results can be compared later.

A growing clinic runs on paper charts and a dated scheduling system. Surgeons re-enter details, and patients call to chase appointments and results.

• An EMR configured with practising surgeons
• A patient record app and portal for appointments and results
• Connections to the laboratory, imaging and billing systems
• Staged data migration, then training before go-live

• Documentation time per case
• Calls about appointments and results
• Late starts in the theatre schedule
• Billing items missed between clinic and finance

Baselines are measured in discovery, so results can be compared later.

After acquisitions, a company runs overlapping applications with unclear owners. Reports are assembled by hand, and major programmes keep overrunning.

• An application inventory with named owners
• A target architecture and a retirement plan for overlapping systems
• Shared integration in place of point-to-point links
• A programme office with one view of status and dependencies

• Number of applications and interfaces
• Annual licence and support cost
• Hours spent assembling reports
• Programme schedule and budget against plan

Baselines are measured in discovery, so results can be compared later.