How to Choose EMR Software in the UAE: A Step-by-Step Selection Process

Choosing an EMR is not a purchasing decision. It is a change to how every clinician, nurse and receptionist in the facility works, for years. Facilities that treat it as procurement, comparing quotes and picking the cheapest compliant option, end up with a system their doctors resent and their billing team works around. Facilities that treat it as a project, with the same discipline they would apply to opening a new department, end up with a system that fits.

This guide is the project plan. It is written for the UAE, where the exchanges and licensing bodies add requirements that a generic selection guide will miss. If you want to know what to look for in the software itself, read the 2026 EMR buyer's guide first; this article is about how to run the selection.

Step 1: Gather requirements from the people who will use it

Spend two weeks, not two hours. Sit with a doctor from each specialty, a nurse, the front desk, the billing team and the pharmacy if you have one, and ask two questions: what do you do forty times a day, and what goes wrong once a week. Write both down. The forty-times-a-day list is your usability requirement; the once-a-week list is your integration and workflow requirement.

Then add the requirements that come from outside the building:

• Your licensing authority. DHA in Dubai, DoH in Abu Dhabi, MOHAP in the Northern Emirates. Each has its own health information exchange (NABIDH, Malaffi, Riayati) and its own expectations of a licensed facility.
• Your insurers. Which ones, what share of revenue, and how claims currently reach them.
• Your growth plan. A second branch in another emirate changes which approvals you need. A new specialty changes which templates you need.

Sort everything into three lists: must have on day one, must have within a year, nice to have. Be honest about the third list; it is where scope creep lives.

Step 2: Decide what you are actually buying

An EMR is rarely bought on its own. For a clinic, it is usually one module of a clinic management platform that also handles scheduling, billing, insurance and pharmacy. For a hospital, it is the clinical core of a hospital information system. Decide which you are buying, because it changes the vendor list.

Also decide on deployment. Cloud is fastest to start and simplest to run. On-premise gives the facility direct control of its data. Hybrid keeps clinical data on-site with cloud access for the rest. Your governance policy, your IT capacity and your licensing authority's expectations decide this, and the decision should be made before the shortlist, not during the demo.

Step 3: Shortlist three vendors

Three, not seven. Beyond three, the demos blur into each other and the scoring becomes guesswork. Build the shortlist from three sources: platforms with the UAE authority approvals you need, platforms live at facilities like yours, and platforms your clinicians have used elsewhere and did not hate. If a vendor cannot name a reference facility of your type and size in the UAE, move on.

Step 4: Write one demo script and send it to every vendor

This is the step most facilities skip, and it is the one that makes the rest work. A vendor's own demo shows you what the product does well. Your script shows you what it does with your patients. Write it from the requirements in step 1:

1. Register this patient (Emirates ID, this insurer, this plan) and verify eligibility.
2. Book them with this doctor, then move the appointment.
3. Triage: record these vitals and this allergy.
4. Consultation in this specialty: document this complaint, add this diagnosis, order this test, prescribe this medication (which interacts with something on the list).
5. Show the result returning, and the abnormal flag.
6. Generate the claim, submit it, then show a rejection and how it is reworked.
7. Show the data this encounter would send to our health information exchange.
8. Show the audit trail of everything above.
9. Run claim ageing and revenue-by-doctor for last month.

Send it a week ahead. Tell the vendors you will score them on this and nothing else. A vendor who pushes back on running your script is telling you how they will behave after the contract.

Step 5: Score during the demo, with clinicians driving

Put the doctor who will use it most in the driving seat for the clinical section, and the billing lead for the claims section. The vendor talks; your people click. Score each step on a fixed scale as you go, on paper, before discussion. Memory is generous; paper is not. The five-area scorecard works well here.

Watch for three warning signs: "that's on the roadmap" for anything in your day-one list; a feature that works in the demo database but the vendor cannot show at a live reference site; and a workflow that takes more clicks than your current process, however pretty the screen.

Step 6: Check references properly

Ask each remaining vendor for two reference facilities of similar type and size in the UAE. Call them yourself; do not accept a written testimonial. Ask what went wrong during implementation, how long it really took, what the support response is like at 8pm, what they would ask that they did not, and whether they would choose the same vendor again. The last question is the only one that matters, and the pause before the answer tells you more than the answer.

Step 7: Read the proposal and contract for the things that hurt later

By this point you have a preferred vendor. Before you sign, check the proposal for:

• Components, not a headline price. Modules, users, branches, implementation, migration, training, each integration, hosting and support, each priced. If the exchange connection or the insurer integrations are missing, ask why.
• Data ownership and export. The records are yours. The contract should say so, and should describe how you get them out, in what format, at what cost, throughout the term and after it.
• Implementation plan with named responsibilities. Who configures, who migrates, who tests the exchange connection, who trains, and what "done" means at each stage.
• Support commitments. Hours, channels, response and resolution targets, and what happens if they are missed.
• What happens when the authority changes a requirement. Exchange specifications evolve. Ask whether keeping up is included or billed.

MEDAS, for reference, offers E-Clinic and HIMS on a subscription or usage-based model priced from the components above, with data export available throughout the relationship, 24/7 support, and a four-to-eight-week implementation for a typical clinic. Any vendor should be willing to put the equivalent in writing.

Step 8: Plan the first ninety days before go-live

The selection is not finished at signature. The ninety days after go-live decide whether the investment pays back. Before go-live, agree on: super users in each department who get extra training and become the first line of help; a go-live support rota with the vendor on site or on call; a short list of metrics you will watch weekly (consultation time, claim rejection rate, days to payment, appointment no-shows); and a review at thirty, sixty and ninety days to fix what the first weeks reveal. The clinic digitisation guide covers adoption and migration in more depth.

Frequently asked questions

How long should EMR selection take?

Six to ten weeks from the first requirements meeting to a signed contract is realistic for a clinic: two weeks on requirements, two on the shortlist and demo script, two to three on demos and scoring, and the rest on references and contract. Rushing the first two weeks is the most common cause of regret.

Should we issue a formal RFP?

For a hospital or a multi-branch group, yes. For a single clinic, a written requirements list and a demo script sent to three vendors achieve the same discipline with far less paperwork.

Who should be on the selection team?

One doctor per major specialty, the nursing lead, the front-desk lead, the billing or finance lead, whoever manages IT, and the owner or medical director as the decision-maker. Clinicians must be in the demos, not just consulted afterwards.

What is the biggest mistake in choosing an EMR?

Letting the vendor run their demo instead of yours. The second biggest is comparing headline prices instead of five-year component costs.