How to Choose a Telemedicine App for a Hospital in Saudi Arabia: A Scorecard for HCOs
Choose a telemedicine app by passing it through regulatory gates, then scoring it on nine weighted criteria: consent and documentation, privacy and hosting, EHR integration, patient access, clinician workflow, continuity of care, operations, commercial exit terms and vendor evidence. Confirm your top two in a time-boxed pilot before signing.
Key takeaways
- Licensing, consent and identity checks are pass/fail gates. A product that fails a gate should not be scored.
- The Saudi Ministry of Health (MOH) telehealth regulations and the WHO telemedicine guide give you a defensible checklist; the weights in this article are our editorial proposal, not a standard.
- Ask for evidence, not demos: consent records, audit logs, integration specifications and hosting documents.
- Run an 8–12 week pilot on a small set of services and measure operational results you control.

On this page
Start with the gates, not the features
Saudi telehealth sits inside a licensing framework. The MOH document Legal Regulations for Telehealth Services states that it applies to facilities and professionals providing telehealth under a Ministry licence, and requires Ministry-approved devices and software (Art. 5(3)), signed and verifiable informed consent before the first service (Art. 12), and sufficient evidence of patient identity before and during each service (Art. 11(3)). It also requires physician-led diagnosis and treatment (Art. 6) and complaint and annual reporting to the Telehealth Centre.
Al Tamimi's 2019 summary adds practical points that affect product choice: teleconsultations must include video rather than audio only; an electronic health record (EHR) system is required for telemedicine centres; each telemedicine activity must be recorded in the patient's record (provider, location, activities, date and time, prescriptions or investigations, observations); and services must follow the national health information exchange policy. It was written in November 2019, so treat it as background and check what has changed.
Turn this into five yes/no gates your vendor must pass in writing:
- Can the product operate under your facility's current MOH licence arrangement, and does the vendor know which approvals apply to software?
- Does it support video consultation with documented consent captured before the first session?
- Does it verify patient identity before and during the service, and keep proof?
- Does every consultation write a complete record into your EHR or a record you control?
- If monitoring devices are used, are they SFDA-approved where required (Art. 10(5))?
The scorecard
Score each product 0–5 per criterion and multiply by the weight. Adjust weights to your strategy; keep the criteria.
| Criterion | Weight | Questions to ask | Evidence to request |
|---|---|---|---|
| Consent, identity and documentation | 15 | How is consent captured, versioned and withdrawn? How is identity verified? | Sample consent record, audit export, identity flow |
| Privacy, security and hosting | 15 | Where is data hosted? Who can see recordings and chat? How are roles controlled? | Hosting documents, access matrix, PDPL position |
| EHR and systems integration | 15 | Which standards and interfaces? Is it one-way or two-way? | Integration specification, a reference site, test plan |
| Patient access and accessibility | 12 | Native Arabic with right-to-left layout? Low-bandwidth mode? Support for older adults and caregivers? | Screens in both languages, device and network test results |
| Clinician workflow and usability | 12 | How many clicks from schedule to note and prescription? | Timed walkthrough with your own clinicians |
| Continuity of care | 10 | Does it connect booking, reminders, follow-up and remote monitoring? | Journey map, reminder templates |
| Operations: support, uptime, reporting | 9 | Support hours in Arabic? Incident process? Utilisation reports? | SLA, incident history, sample dashboard |
| Commercials and exit | 7 | Pricing per user, visit or site? Data export on exit? | Price sheet, exit clause, export format |
| Vendor evidence and references | 5 | Who runs it today at a comparable hospital? | Two references you contact yourself |
The WHO Consolidated telemedicine implementation guide (published 9 November 2022) frames telemedicine adoption as planning, implementation and maintenance leading to a costed investment plan, and its page links the 2022 WHO–ITU accessibility standard for telehealth. We could access only the guide's landing page, not the full PDF, so use it as the structure for your plan and read the PDF itself for detail on platform selection and equity. Consolidated telemedicine implementation guide
Red flags in vendor responses
- "Compliant" with no document attached.
- A demo that skips identity verification and consent.
- Integration described as "possible" without a named interface or reference site.
- Arabic limited to translated labels, with English-only notifications.
- No export of consultation records or recordings on exit.
Pilot before you commit
Pilot for 8–12 weeks with one or two services, a named clinical lead and your own baseline. Measure what you control: consult completion rate, no-show rate, time from booking to consultation, documentation completeness, clinician time per consult, patient satisfaction and support tickets. Clinical outcome claims need clinician-designed evaluation.
A worked scenario (illustrative)
A four-branch hospital group shortlists three apps. Two fail gate 4 because notes stay in the vendor's system. The remaining product scores highest on integration and Arabic access but lowest on support hours, so the group negotiates Arabic support coverage into the contract and pilots it for ten weeks in dermatology and diabetes follow-up. This is a hypothetical, not a CareSync customer result.
Where CareSync fits
CareSync positions itself as a white-label platform connecting booking, virtual care, reminders and follow-up for hospitals. Which of the scorecard criteria it meets in your environment should be tested the same way as any vendor.
FAQ
Do we need a Ministry licence before launching telemedicine in Saudi Arabia? The MOH regulations state that telehealth is provided by licensed facilities and professionals under a Ministry licence. Confirm your facility's situation and the current approval route with the MOH.
Can we use audio-only consultations? Al Tamimi's 2019 summary says teleconsultations must include video. Check whether this has changed.
How many apps should we pilot? Pilot one or two. More than two splits clinician attention and weakens the comparison.
What should the contract include? Hosting location, data export on exit, support hours, incident response, audit-log access and who owns consultation records. Have counsel review it.
Does a telemedicine app replace our EHR? No. It should write to your record or integrate with it; the record stays yours.
Sources
- Saudi MOH Legal Regulations for Telehealth Services
- Al Tamimi, The Regulation and Licensing of Telemedicine in Saudi Arabia, Nov 2019
- WHO Consolidated telemedicine implementation guide