Hospital Patient App vs Sehhaty: Does Your Hospital Still Need Its Own?
Most multi-branch hospitals still need their own patient channel, but it should complement Sehhaty, not copy it. Sehhaty covers national services such as appointment booking, consultations and health records. A hospital app should own what only the hospital knows: its branches, doctors, programmes, follow-up plans and communication preferences.
Key takeaways
- Sehhaty and a hospital app solve different problems. Treat the decision as "what should each own", not "which one wins".
- Do not rebuild national features. Vaccination records, sick-leave and report access and generic vital-sign tracking already sit in Sehhaty.
- A hospital channel earns its place on branch-specific journeys, between-visit follow-up, programme enrolment with consent, and one inbox for patient communication.
- Confirm any integration or deep-link pathway with the Ministry of Health before promising it to your board. [VERIFY WITH BRAND]
On this page
What Sehhaty already does
The Ministry of Health describes Sehhaty as a platform where users reach services "provided by various entities in the health sector in Saudi Arabia". Its published service list includes instant consultations, appointment booking and review, remote appointments, medication search, a digital health wallet, sick-leave and medical-report review, women's health and dependents' services, a designated family doctor, children's vaccination records, vital-sign tracking ("Know Your Numbers"), step counting, a saved medicine list, educational content, and vaccination and screening appointments. The page we reviewed does not list private-sector providers specifically and gives no user numbers, so we make no claim about either.
The platform is also still evolving. On 15 September 2026 the Ministry announced the results of a public consultation on Sehhaty enhancements and said two services were approved for rollout: Appointment Attendance Confirmation and a Pediatric Autism Screening Questionnaire. The announcement gave no participation figures. The direction is clear: more of the generic patient journey will live in the national app over time.
Why the question matters to a hospital group
Search results for this topic today are dominated by app-development vendors writing "cost to build an app like Sehhaty". That framing misses the buyer's real question. A hospital group is not trying to build a second national app. It is deciding where its own patient relationship lives when the front door belongs to the Ministry.
Four jobs a hospital-owned channel should do
1. Branch-specific journeys
Sehhaty can show a patient an appointment. It does not know that your Jeddah branch runs a diabetes clinic on Tuesdays, that the Riyadh branch has a dedicated cardiology pathway, or that a patient prefers a female clinician at a particular site. A hospital channel carries that operational context.
2. Between-visit follow-up
Most of a chronic patient's life happens between visits. Reminders, questionnaires, home readings and nurse check-ins belong to the treating team's plan, and the plan belongs to the hospital. This is where a branded channel creates continuity.
3. Programme enrolment and consent
Patient support programmes, loyalty and wellness programmes, and pharma-sponsored initiatives need explicit enrolment, purpose-specific consent and an audit trail. Those flows belong in a channel your hospital controls, with consent text you can govern in Arabic and English. See our guide to PDPL-compliant patient support programmes.
4. One communication inbox
Patients reach hospitals through calls, WhatsApp, the web, the app and walk-ins. A hospital-owned channel can give your contact centre a single thread per patient. That is operational value no national app can provide for you.
What not to rebuild
Resist the urge to replicate national functions. A generic vaccination record, sick-leave certificate access or step counter in your app adds maintenance cost and no differentiation, and with Sehhaty's roadmap moving, you would be racing the Ministry on its own ground. If a patient wants those, point them to Sehhaty.
A simple split: who owns what
Use Sehhaty for
National health record access, Ministry-led services, vaccination and screening appointments, sick-leave and report access, and national consultation services.
Use your hospital channel for
Branch and clinician context, chronic-care follow-up plans, programme enrolment and consent, post-visit and post-discharge check-ins, billing and service questions, and a unified communication thread.
Design for coexistence
Keep patient identity and data flows clean so your channel can complement Sehhaty today and connect to it later if an official integration pathway is available to your facility. Do not promise an integration your hospital has not confirmed with the Ministry.
An illustrative scenario: a four-branch group with a chronic-care cohort
Illustrative scenario, not a client case. A four-branch private hospital group has 3,000 patients in its diabetes and hypertension clinics. Booking mostly happens through national channels and the call centre. The clinical leadership's gap is not booking; it is that nobody systematically contacts patients between quarterly visits, and the contact centre cannot see which patient is in which programme. The group does not build a booking app. It deploys a branded channel limited to three jobs: enrolment with consent, scheduled check-ins by the care team, and a single patient thread for the contact centre. Booking remains wherever the patient already books. The group measures operational indicators only: contact rate, response rate, and whether scheduled follow-up visits are kept. No clinical outcome claim is made. HOLD — expert review before any outcome claim is published.
Questions to ask before you buy or build
Which journeys are unique to our hospital and cannot live in a national app? Which flows need our own consent text and audit trail? What integration pathways are open to our facility, confirmed with the Ministry? Who owns the patient communication thread when a patient writes in through three channels? And what does it cost to maintain a feature the Ministry may deliver itself within a year? For the economics, read our build-vs-buy guide for hospital patient apps and our note on EHR integration.
How CareSync fits
CareSync Network is a white-label omnichannel platform for multi-branch hospitals, with the hospital's own branding, Arabic and English journeys, and programme and follow-up tooling. [VERIFY WITH BRAND] Confirm current capabilities (branch-level journeys, consent flows, contact-centre thread, and any Sehhaty or national-platform connectivity) before this section is promoted.
Frequently asked questions
Q1: Do private hospitals in Saudi Arabia need their own patient app if Sehhaty exists?
A1: Many multi-branch groups still benefit from their own channel, but for different jobs: branch-specific journeys, between-visit follow-up, programme enrolment with consent and unified communication. They generally should not rebuild national functions such as vaccination records or sick-leave access.
Q2: What services does Sehhaty offer?
A2: According to the Ministry of Health, Sehhaty includes instant and remote consultations, appointment booking, medication search, a digital health wallet, sick-leave and report review, family doctor and vaccination records for children, vital-sign tracking and educational content, among others.
Q3: What is the Sehhaty Appointment Attendance Confirmation service?
A3: On 15 September 2026 the Ministry of Health announced it as one of two enhancements approved for rollout after a public consultation. The announcement we reviewed gave no further detail on how it works for providers, so check the Ministry's channels for specifics.
Q4: Can a hospital integrate its app with Sehhaty?
A4: We did not find a published public integration pathway for private hospitals on the Ministry pages we reviewed. Confirm directly with the Ministry of Health and your integration partners before planning around it. [VERIFY WITH BRAND]
Q5: Should a hospital group build or buy its patient app?
A5: Scope drives the answer. A narrow, branded channel for follow-up, consent and communication is usually faster to buy as white-label than to build; see our build-vs-buy guide for the cost and risk trade-offs.