Health Cloud for Gulf hospitals: patient access, referrals and follow-up

10 September 2026
Arcsen

A patient in Riyadh or Dubai who needs a cardiologist might call the contact centre, send a WhatsApp message, fill in a web form or bring a referral letter from a clinic. Each route lands somewhere different: a ticket, a shared inbox, an email address, and a booking in the hospital information system (HIS) made by whoever picks it up. When the patient calls back, the person who answers cannot see the referral or the form, and the follow-up depends on someone remembering it.

Health Cloud is Salesforce’s product for that layer, and Salesforce describes it as extending the value of the electronic health record (EHR). The EHR keeps the clinical record. Health Cloud keeps the relationship, from the first enquiry to the follow-up call. This guide shows how that split works for hospitals and medical groups in the Gulf and Egypt. Our healthcare outlook covers the wider picture.

What Health Cloud gives a provider

Health Cloud is one of the Salesforce industry clouds we implement. Its product page lists a contact centre for healthcare with access to EHR data, Intelligent Appointment Management, referral management, Integrated Care Management for care plans, and provider relationship and network management for referring doctors and clinics. Enquiries and complaints run as cases in Service Cloud.

Referrals. Since Winter ’24, Salesforce has recommended the Clinical Service Request object in its FHIR R4-aligned Clinical Data Model for referrals. The older approach on leads and opportunities gets no future referral enhancements.
Appointments. Intelligent Appointment Management gives schedulers one console over Salesforce Scheduler, the EHR’s scheduling engine, or both, with open slots in real time. Patients can book online as guests and filter by video, phone or in-person visits, gender and the languages a doctor speaks. It sends automated reminders, and a visit type can carry a pre-visit questionnaire.
Agents. In March 2026 Salesforce announced six new agents for healthcare. It said a contact centre agent template for patients and members was generally available that day, and put referral triage, which routes referrals and books follow-ups, at June 2026. Salesforce said some of the features were unreleased, so check your org before building an Agentforce agent on them.

Patient access, stage by stage

This is how we split the work between Health Cloud and the HIS on a typical outpatient path:

Stage	In Health Cloud	Stays in the HIS or EHR	What integration carries
1. Enquiry	An enquiry from phone, WhatsApp, chat or email, tracked as a case with the patient’s preferred language	Nothing until the caller is registered	A lookup by medical record number (MRN) for upcoming appointments
2. Referral	A clinical service request with referrer, priority, documents and status	Registration and the clinical letter	New registrations, and the MRN back to Salesforce
3. Booking	Slot search and confirmation in Intelligent Appointment Management	The schedule, where its engine owns it	Open slots read live, bookings written back
4. Before the visit	Reminders, directions and questionnaires in Arabic or English	Clinical orders	Changes and cancellations from either side
5. The visit	Status only: arrived, seen or no-show	Notes, orders, results and prescriptions	Status events that start follow-up
6. Follow-up	Calls, the next appointment, and care plans with tasks	The clinical plan and results	Due dates and appointments, without clinical detail

Read the third column first. Every field copied from the EHR becomes health information you must protect and keep, so copy only what people need to act on.

Rule of thumb: the EHR owns clinical facts and, where it runs the schedule, the slots. Health Cloud owns the conversation, the request and the follow-up.

How integration carries it

Three decisions settle most of the design.

One patient, two systems. Health Cloud uses identifier records to map its records to the matching records in an external system with scheduling, such as an EHR. Agree which identifier links them, such as the MRN, and what happens to a caller who has none yet. Arabic and English spellings of a name rarely match, so match on MRN, date of birth and mobile number first.
Who owns the schedule. Where the EHR’s engine owns the slots, Intelligent Appointment Management reads availability and pushes bookings back over REST endpoints, with a named credential for authentication. Decide clinic by clinic, and never let two systems own the same slots.
Which events flow back. Arrival, no-show, cancellation and discharge events from the EHR start follow-up work. Health Cloud offers FHIR APIs, and an integration layer such as MuleSoft carries the feeds, retries failures and keeps a log both teams can read. Salesforce’s March 2026 announcement describes an EHR read-write agent for EHRs such as athenahealth through MuleSoft; for any other HIS, plan the interfaces as a project of their own.

Arabic and English on every channel

Store each patient’s preferred language on the record and let it choose the template, the queue and the person who calls back. Then plan for three limits.

Staff screens. Arabic is a supported end-user language, and Lightning Experience switches to right-to-left for it. Salesforce says the layout focuses on standard Sales and Service Cloud objects, reports and dashboards, and the Salesforce mobile app does not support right-to-left. Test every Health Cloud screen your Arabic-speaking staff use.
Messages. Write reminders, confirmations and follow-ups in both languages, approved by your communications and clinical teams, and keep clinical detail out: time, place and preparation are enough. Campaigns from Marketing Cloud follow the same rules.
Agents. Salesforce lists Arabic as Beta for Agentforce and warns of some inconsistencies when retrieving information. Directions, visiting hours and booking status suit an agent. Symptoms, results and medication go to a person.

Health data rules that shape the design

Three texts shape a hospital CRM in the UAE and Saudi Arabia. Confirm the detail with counsel.

The UAE’s health ICT law. Federal Law No. 2 of 2019 covers every use of information and communications technology in health, free zones included. Article 16 requires anyone handling patient information to keep it confidential and use it only for health purposes, with the patient’s written approval for other uses, subject to listed exceptions such as insurers verifying entitlements. Article 20 sets a minimum retention period of 25 years from the last health procedure, one more reason to copy little clinical detail into Salesforce.

The UAE’s data protection law. Federal Decree-Law No. 45 of 2021 treats health data as sensitive, and its Article 2 excludes personal health data that has its own legislation. Where it applies, consent must be easy to withdraw (Article 6) and people can object to direct marketing (Article 17). Ask counsel which data falls under which law.

Saudi Arabia’s Personal Data Protection Law. SDAIA’s guide to the law treats health data as sensitive data, rules out legitimate interests as the legal basis for processing it, and confirms that people can withdraw consent at any time.

In practice: keep clinical detail in the EHR, record consent and its withdrawal by channel and purpose, and build marketing segments from non-clinical data unless the patient has agreed in writing. In Egypt, Qatar and other markets, map the local rules with counsel first.

Our work in healthcare

Arcsen is a Salesforce Summit partner with offices in Dubai, Riyadh, Jeddah, Doha and Cairo, 170+ consultants and 400+ certifications, and we deliver Arabic-first. Our healthcare clients include Almoosa Health, SSMC, AlJazira Healthcare and Kaizmed.

Where to start

Map one patient path. One specialty, from referral to first follow-up: every channel, handover, system and message, in both languages.
Agree the record rules: the identifier that links Salesforce and the HIS, the clinical fields the CRM may hold, and the consent you record.
Choose the scheduling engine for each clinic: the EHR’s schedule or Salesforce Scheduler, never both for the same slots.
List the interfaces (lookup, registration, slots, bookings and status events), each with an owner on both sides and test data in both systems.
Pick a first agent with care. Directions and booking questions make a good start, with written rules for clinical handovers. The free Agentforce Readiness Assessment picks three use cases and costs a pilot.

Planning patient access on Salesforce? See our healthcare work, or, if you already run Salesforce, start with the free Salesforce Health Check: a scored report on the whole org in ten working days, yours to keep. You can also talk to our healthcare team or send us your RFP.

Frequently asked questions

Does Health Cloud replace a hospital information system?

No. It sits beside the HIS or EHR, which keeps the clinical record. Health Cloud keeps enquiries, referrals, appointment requests, follow-up and consent, connected through integration.

Can Health Cloud book appointments into our EHR’s schedule?

Yes. Intelligent Appointment Management can use the EHR’s scheduling engine, Salesforce Scheduler or both, reading open slots from the EHR and writing bookings back through REST endpoints.

Does Health Cloud work in Arabic?

Arabic is a supported end-user language with right-to-left layouts in Lightning Experience, focused on standard objects. The Salesforce mobile app does not support right-to-left, and Salesforce lists Arabic as Beta for Agentforce.

Which laws govern patient data in a hospital CRM in the UAE and Saudi Arabia?

In the UAE, Federal Law No. 2 of 2019 on ICT in health fields, alongside the federal data protection law, which excludes health data that has its own legislation. In Saudi Arabia, the Personal Data Protection Law, which treats health data as sensitive.

Can an AI agent answer patients?

For directions, preparation and booking status, yes, with a quick handover to a person. Salesforce made a contact centre agent template for patients generally available in March 2026. Symptoms, results and medication belong with clinical staff.