Seha Virtual Hospital: Lessons From Saudi Arabia's Virtual Care Model

Seha Virtual Hospital (SVH), run by Saudi Arabia's Ministry of Health, is the clearest working example of what a "virtual hospital" actually is. It is not an app for video consultations. It is a central team of specialists who deliver care into physical hospitals across the country: running daily ICU rounds remotely, responding to stroke codes, joining tumour boards and reading scans.

It launched in February 2022 with a live network of 130 connected hospitals. Today the Ministry's own page describes support for more than 242 hospitals, 48 main specialties and 68 subspecialties, recognition by Guinness World Records as the world's largest virtual healthcare provider, and Diamond-level accreditation from Accreditation Canada, a first for a virtual hospital (Saudi MoH).

For hospital groups in India and the Gulf, SVH is a useful benchmark because its model works at smaller scale too. A five-hospital group with one strong tertiary centre faces the same problem Saudi Arabia did: specialists concentrated in one place, patients spread everywhere.

What Seha Virtual Hospital actually does

The Ministry groups SVH services into seven pathways:

Notice how much of this is clinician-to-clinician. The patient is usually in a real hospital bed with real nurses. The virtual hospital supplies scarce expertise: an intensivist for a district ICU, a stroke neurologist at 2 a.m., an oncologist for a multidisciplinary meeting.

Why this model works

Three structural reasons explain SVH's growth:

1. It solves a real scarcity problem. Intensivists, stroke neurologists and sub-specialist oncologists are scarce everywhere. Centralising them and sharing their time across many sites uses that scarcity better than spreading them thin.
2. It works inside existing workflows. ICU rounds, stroke codes and tumour boards are established clinical routines. SVH plugs into them rather than inventing new ones.
3. It is accountable like a hospital. Seeking hospital-grade accreditation forces the clinical governance, documentation and quality monitoring a real hospital needs.

The Ministry has also built an Innovation Empowerment Center alongside SVH, with a sandbox for health innovations and a clinical research centre, so new virtual services can be tested before scaling. In September 2025 SVH and that centre won an excellence award for virtual healthcare solutions (MoH news).

Four lessons hospital groups can copy

SVH runs at national scale, but four of its service lines translate well to a private hospital group.

Lesson 1: start with tele-ICU rounds

Of all SVH's pathways, daily virtual ICU rounds are the easiest to copy and have some of the clearest benefits. Many secondary hospitals run ICUs without an intensivist on site around the clock. A remote intensivist doing structured daily rounds, with on-call support for deterioration, raises the standard of care without hiring at every site.

What you need:

• A camera and screen at each ICU bed or a mobile cart, good enough to see the patient, monitors and ventilator settings.
• Live access to vitals, labs, medications and imaging for the remote intensivist, through your hospital system, not over WhatsApp.
• A structured rounding template so every patient gets the same review: lines, ventilation, sedation, nutrition, infection, plan.
• Clear responsibility. Who writes the orders, the remote intensivist or the bedside doctor? Decide and document it.

Our IPD and bed management guide and nursing management system guide cover the inpatient data a remote team needs to see.

Lesson 2: telestroke needs a protocol before technology

Telestroke is listed among SVH's urgent care services because stroke is time-critical and stroke neurologists are scarce. A remote neurologist can examine the patient by video, review the CT scan and advise on thrombolysis.

The technology is the easy part. The hard part is the protocol:

1. A stroke code that triggers at the spoke hospital's emergency department.
2. CT imaging done immediately and pushed to the remote neurologist's screen.
3. A video assessment within minutes, with a nurse or doctor at the bedside.
4. A documented decision, and a transfer pathway if the patient needs thrombectomy at the hub.

Lesson 3: virtual tumour boards scale specialist opinion

SVH runs virtual multidisciplinary teams for cardiac and several cancer types. For hospital groups, virtual tumour boards are a high-value, low-risk starting point: no emergency, structured cases, specialists who already meet weekly.

The software requirement is a case presentation workspace: pathology, imaging, staging and history in one place, with the board's recommendation recorded back into the patient's record. That is a clinical data and workflow problem, which is where most of the build effort goes.

Lesson 4: teleradiology and remote EEG as utility services

Teleradiology and remote EEG are "allied" services in SVH's model. They do not need a patient on video at all, just images or signals and a reporting workflow. Many hospital groups already outsource night radiology. Bringing it inside a group-level virtual service gives control over quality and turnaround.

What to adapt for India and the UAE

Seha is a national programme with a single ministry behind it. Private hospital groups operate differently, and some adaptations matter:

In the UAE, data residency rules mean the virtual hospital's systems must keep health data in the country. In India, consent and record sharing should run through ABDM where patients have ABHA numbers. For both, see our multi-specialty hospital software guide for what a group-wide system needs.

The technology stack, in plain terms

• A shared patient record across sites, or at least a shared patient index and real-time access to each site's records.
• Clinical video that is reliable, secure and launched from inside the patient record.
• Device and monitor data from ICUs, streamed or at least visible in near real time.
• PACS access for imaging across sites.
• Scheduling and rostering for virtual sessions, so specialists' virtual time is planned, not squeezed in.
• Documentation and audit: every virtual consultation recorded in the patient's chart, with who advised what and when.

At Algon we design hospital systems for multi-site groups so that a "virtual" encounter is just another encounter type in the same record, which makes this kind of service much easier to add later. See our hospital management system work for how we approach shared records.

How to start: a 6-month roadmap

1. Month 1: Pick one pathway, usually ICU rounds or tumour boards. Agree clinical governance and responsibilities.
2. Month 2: Make sure the hub team can see spoke data: vitals, labs, medications, imaging.
3. Month 3: Equip spokes with cameras and carts, train nurses, test connectivity and image transfer.
4. Months 4-5: Go live with daily rounds or weekly boards, measure and adjust.
5. Month 6: Review outcomes (transfers avoided, length of stay, protocol adherence) and decide on the next pathway.

Effort and cost drivers

Virtual care budgets are easy to underestimate because the visible items, cameras and software licences, are the cheap part. Indicative drivers for a group-level virtual service:

Integration usually dominates the software effort. If each hospital in the group runs a different system, the remote specialist ends up with five logins and no single view. Solving that, through a shared record or an integration layer that pulls the essentials into one screen, is the real project.

Mistakes to avoid

• Starting with a patient app. Direct-to-patient video is the least differentiated piece. Start where specialist scarcity hurts most.
• Leaving responsibility vague. If the remote specialist and bedside doctor both think the other wrote the order, patients get hurt. Document it per pathway.
• Ignoring nurses. Virtual rounds depend on bedside nurses presenting patients well. Train them and give them a template.
• Measuring activity instead of outcomes. Video minutes say nothing about whether patients did better.

Conclusion

Seha Virtual Hospital shows that a virtual hospital is an operating model, not a gadget: scarce specialists organised centrally, delivering care into physical hospitals through structured pathways, with the governance of a real hospital. Its scale is national, but its building blocks, tele-ICU rounds, telestroke, virtual tumour boards and teleradiology, work for any hospital group with one strong centre and several smaller sites.

Start with one pathway, make the data visible across sites, and measure clinical outcomes. If you are planning a group-level virtual care service, talk to us about building it into your hospital system rather than bolting it on.