The footprint
Oracle Health, formerly Cerner, is the deeply-entrenched EHR vendor in the Middle East private hospital market. The flagship deployments are well-known. The American Hospital Dubai, the King's College Hospital London Dubai, Emirates Health Services across the federal hospital network — all run on Oracle Cerner Millennium. The vendor has been in the region for more than two decades and the integrator ecosystem around the platform is mature.
The footprint matters because it sets the institutional default. When a hospital group expands, the default is Oracle Cerner. When a regulator publishes a digital health standard, the implementation reference is Oracle Cerner. When a clinician trains in the region, the platform they train on is Oracle Cerner. None of that is wrong on the merits. The platform is mature and the clinical workflows are well-supported. The question worth asking, and the one this piece exists to answer, is what the full operating cost of that default actually looks like at a mid-sized Middle East hospital group, and where the alternative starts to be a sensible conversation.
What the bill actually contains
The licence is a meaningful number but it is rarely the largest number in the operating bill. Industry commentary places mid-size community hospital initial licensing and implementation in the multi-million-dollar range, with annual maintenance running at a substantial percentage of the licence and implementation services adding meaningfully on top. Those numbers compound at a Middle East hospital group with multiple facilities.
Three cost layers sit underneath the licence:
The integrator and consultancy retainer. Operating Cerner Millennium at scale is not a task the hospital's own IT team performs unsupported. The deployment is held together by a system integrator on a long-term services agreement. Major changes — a new department go-live, a new specialty workflow, an integration with a new diagnostic system — are billable at the integrator's standard rate. The retainer is the largest line on the IT department's recurring budget at most Middle East hospitals.
The infrastructure cost on Oracle Cloud. The recent generation of Cerner deployments in the region runs on Oracle Cloud Infrastructure, often in the Oracle Cloud UAE or KSA regions. The OCI commitment is bundled into the Cerner relationship in ways that make the cost difficult to separate. The hospital is buying the EHR licence and the infrastructure as a combined commitment. The flexibility to renegotiate one without the other is structurally limited.
The clinical-workflow extension tax. Every specialty workflow the hospital wants to refine — an oncology pathway, a maternity workflow, a cardiac-rehab protocol — typically requires Cerner configuration or content development that goes through the integrator. The clinical staff who would otherwise own the workflow refinement find themselves dependent on a vendor release cycle that runs at vendor pace, not hospital pace.
Sum those against the licence. The full operating cost of an EHR estate at a mid-sized Middle East hospital group is multiple times the headline licence number. That is the number the CIO is working with when the alternative conversation lands on the table.
What the alternative looks like in practice
We are not arguing that any Middle East hospital should retire Oracle Health overnight. The clinical risk in EHR migration is real. The regulator's posture on EHR continuity at supervised facilities is rigorous. The patient safety considerations override every commercial argument that ignores them. The conversation we have with Middle East hospital CIOs is not about replacement. It is about the workflows where ownership outside the core EHR pays back fastest, and the architectural pattern that lets the hospital own those workflows without disturbing the EHR backbone.
The pattern is the same one that works in retail, banking, and manufacturing. Pick the workflow furthest from the core, build the owned alternative, run it in parallel, retire the dependency on the EHR module that covered the workflow before. The core EHR stays where it is. The licence reduces in proportion to the modules that have moved.
The workflows we have moved successfully:
Patient engagement and the digital front door. The patient portal, the appointment booking, the pre-visit intake forms, the post-visit follow-up. These can run on owned software that integrates back to the EHR through a defined boundary. The patient experience improves materially because the team designing it owns the surface. The EHR continues to hold the clinical record.
Clinical operations dashboards. The bed-management surface, the operating-theatre utilisation view, the emergency-department throughput dashboard, the discharge-planning workspace. These are workflows the operations team owns. The data lives in the EHR. The view does not need to.
Specialty workflow tooling. Pathway tooling for high-volume specialties — chemotherapy scheduling, dialysis scheduling, antenatal pathways. The data contract back to the EHR is well-defined. The specialty workflow is built and refined by the clinical team that runs it, not by a vendor configuration release.
Patient flow optimisation. The workflow that watches the hospital's real-time operational state and surfaces the patient-flow bottlenecks for the operations team. This is the workflow the next article in this series covers in depth. It does not exist as a product in the EHR catalogue.
The regulator's view
The UAE Ministry of Health and Prevention, the Dubai Health Authority, the Department of Health Abu Dhabi, and the Saudi Ministry of Health each have published positions on digital health, data residency, and clinical information system continuity. The positions are detailed and they are reviewed regularly. The hospital that proposes a workflow replacement around an existing EHR finds the regulator's response is rarely opposed, provided the patient safety arguments are addressed and the audit trail is preserved.
What the regulators do not want is a fragmented architecture where the hospital's own teams cannot answer questions about the workflow. The architecture we propose addresses this directly. The hospital's operations and clinical teams own the workflow that has moved. The EHR continues to hold the clinical record. The audit trail is preserved on both sides of the boundary. The supervisory conversation about the move is a substantive conversation, not a defensive one.
The cost arithmetic
A first workflow move — typically the patient engagement layer or the operations dashboard — at a mid-sized Middle East hospital runs from kickoff to first production traffic at one facility inside a single fixed-scope engagement. The cost of the engagement is a fraction of the annual integrator retainer the hospital is paying. The reduction in the integrator's billable work in the year following the move typically funds the next move. The architecture is self-funding by the second workflow.
The total IT operating cost at the end of a 12-month cycle is meaningfully lower than the trajectory the hospital was on. The renewal conversation with the EHR vendor is a different conversation. The hospital that has moved one workflow has not committed to moving the rest. It has bought itself the option, the institutional confidence, and the platform-team capability to make that decision against a future renewal.
The saasinator perspective
Healthcare is the category where we apply the most conservative scope. Patient safety is the first consideration in every engagement and the architecture is designed so that the clinical decision surface remains inside the EHR where it has been validated. The work above is not a critique of Cerner's clinical decision support. It is a recognition that not every workflow in the hospital is a clinical decision workflow, and the workflows that are not have economics that justify ownership.
The hospital CIO who runs the first workflow successfully is in a different conversation with the EHR vendor at the next renewal. The institutional default has shifted. The next move is a smaller decision than the first one.
What to bring to the diagnostic
If you operate a Middle East hospital group on Oracle Health Cerner and the integrator retainer is the line on the IT budget that has grown most in the last three years, the conversation worth having is which non-clinical workflow you would test against in a four-week pilot. Bring the EHR module breakdown, the integrator retainer schedule, and the clinical and operations leadership view on which workflow has the most friction today.
The diagnostic for a healthcare engagement is 15 working days. We work with the hospital's clinical governance, patient safety, and risk leadership alongside the IT leadership. The output is the workflow recommendation, the architecture sketch, and the first-quarter scope that respects every safety consideration the institution operates against.