Guide · Healthcare

Doctor booking apps for Syria.

Patients see the booking loop. Behind it, a booking app in Syria is a health app that needs a licence, with rules on who can be listed, how people sign up and where patient data lives. Here is how to build version one, and what the licence asks for.

Updated 20 November 2026Sources checked 20 November 2026Reviewed by Eng. Hasan Kassas

The short answer

Version one of a doctor booking app is a short loop: a patient finds a doctor, books a slot that is really free, gets an instant confirmation, then a reminder before the visit. Video calls, payments and medical records can wait. That loop is the one we designed DocDoc around.

Because it is a health app, Syria adds a second track. Most apps here only notify the authorities (see our licence guide), but a health app needs more. Under the Ministry of Health's Decision 24/ت of 2 December 2025, it needs the ministry's approval and then accreditation from the National Authority for Information Technology Services (NAITS). Patient data must sit on servers inside Syria, every doctor needs a ministry licence whose number and date the app shows, listed clinics must be licensed, and sign-up must verify the phone with a code. That is the position on 20 November 2026.

The rules

What Decision 24/ت asks of a booking app

The decision saysSo build
DoctorsLicensed by the ministry; each one's specialty, licence number and licence date recorded and shownRequired licence fields on every profile
ClinicsEvery listed facility licensed by the ministryLicence data and a review for each clinic
Sign-upA code sent to the user's phone; doctor accounts verified by phone numberPhone verification for every account
HostingPatient and health data on servers inside SyriaHosting in Syria, chosen before the backend
ConsultationsDocumented; AI is not a clinical source without review by the medical teamStored notes; any AI text checked by a doctor
PrivacyThe confidentiality of a medical file; no third-party sharing without the user's consentNo health details in third-party analytics
Ministry accessThe ministry may take a copy of the databaseA documented export, ready to hand over
ChangesNo change to the approved version without approvalReleases tracked against that version
PromotionNo before and after photos or patient testimonials as advertisingReviews and marketing built around that ban
The licence

Getting a health app licensed

  1. Owner and two officers

    The owner must be a public body, a company or a person with a commercial register. Name a scientific officer, such as a doctor or pharmacist, who answers for medical content, and a data protection officer with an IT, security or data background.

  2. Prepare the file

    Annex 2 asks for the commercial register; names, qualifications and IDs of the owner, chief executive, developer and both officers; a fully working build; a document on how the app works; and a usage policy covering minors.

  3. Apply online, then on paper

    Submit the Annex 1 form online. It asks where the developer is based and where, and with whom, the app is hosted. Then register a paper copy at the ministry within 15 days.

  4. Fill the gaps within 30 days

    Complete any missing documents within 30 days of the ministry's notice, or the request lapses.

  5. Study and approval

    The study can include an interview with the ministry's committee. Approval lasts two calendar years; NAITS accreditation follows, and the public registry is updated.

  6. Keep it valid

    Changes need the ministry's approval, renewal must be requested from both bodies at least 30 days before it is due, and the ministry may stop an app without paying compensation.

The registry

Applying is not the same as approved

The ministry's FAQ is plain: an app is licensed only after the study, the ministry's approval and NAITS accreditation. Its public register of electronic health apps shows each app's status, owner, classification, approval date and approved services. On 20 November 2026 it listed 23 apps (1 accredited by NAITS, 4 with temporary NAITS approval and 18 with initial ministry approval), several of them for booking doctors. A listing is a regulatory status, not an endorsement.

Still open: Decision 24/ت, which replaced Decision 13/ت of 2023, sorts apps into three classes, but the annex that assigns them is unpublished, so a plain booking app's class is unconfirmed.

The product

The booking loop: find, book, confirm, remind

We designed and built DocDoc as part of its founding team; it was later sold by its owners to a healthcare company in Palestine. Its first version covered four steps: find a doctor by specialty, location and availability, book a real-time slot, get an instant confirmation, and receive a reminder. It was built on Flutter, one codebase for iOS and Android, with a Node services layer and Postgres for the scheduling core, Arabic-first and light on data.

The hard part was trust: a slot taken on one phone had to vanish from every other screen at once. In any booking app, that takes slots generated on the server, a short hold that expires if the patient walks away, a database constraint that allows one booking per doctor and start time, and live updates to every open screen. Put the clinic's phone and walk-in bookings in the same calendar, release cancelled slots at once, and let staff mark no-shows. Reminders are the first defence against missed visits; deposits bring payment rules with them.

Who uses it

Three kinds of user

01
Patients

Search by name, specialty and area, see real open times, book for themselves or a relative, get reminders, cancel or move visits, and see each doctor's licence number and date.

02
Doctors and clinic staff

Set hours, slot lengths and days off, see the day's list, add phone and walk-in bookings, and mark arrivals. Give receptionists their own role if they run the diary.

03
Admins and the two officers

Check licence data before profiles go live, log who opened which patient record, and export data when the ministry asks. The scientific officer reviews medical content; the data protection officer owns access and breaches.

Syria specifics

What changes in Syria

Each point links to a fuller guide.

  • Phone codes. Twilio stopped SMS to Syria on 15 September 2025, and WhatsApp's Business Platform cannot reach users there. Infobip lists Syria, and Google's Identity Platform (behind Firebase phone sign-in) prices SMS to it. Test on real Syriatel and MTN SIMs. See SMS codes and OTP.
  • Reminders. Schedule them on the server, push first and SMS for visits that are close, and keep bookings visible in the app, since a push can arrive late. See push notifications in Syria.
  • Weak internet. Cache doctors and the patient's bookings, mark a booking confirmed only when the server does, and give each request a unique key so a retry cannot book twice. See building for weak internet.
  • Arabic search. Normalise alef and hamza forms, taa marbuta, alif maqsura and diacritics in names and specialties, and map everyday words so that أسنان finds dentists. See Arabic search normalisation.
  • Calendar. The Syrian week starts on Saturday in the CLDR data browsers use, Asia/Damascus has been UTC+3 all year since late 2022, and months read كانون الثاني, not يناير. See dates in Syrian apps and Syriac month names.
  • Clinic location. Syria does not require postcodes, according to the Universal Postal Union. Store a map pin, a Plus Code and a description with the building, floor and a landmark. See addresses and maps.
  • Deposits. Decision 1124 of 18 August 2026 puts collecting payments under Central Bank licensing, and Stripe's policy (updated 22 September 2026) still bars dealings with people located in Syria. Version one can leave payment at the clinic desk. See accepting payments.
Health data

Patient data under Law No. 12 of 2024

The personal data law, dated 28 March 2024 and in force since 1 January 2025, treats health data, including appointments and visit history, as sensitive. Article 13 requires a licence or permit from the Personal Data Protection Authority to process it, plus the person's written, explicit consent. Children's data needs a guardian's consent, which matters as soon as parents can book for children. We could not confirm that the Authority is operating yet, so ask a lawyer how to handle that step today.

The executive instructions, Council of Ministers Decision 29 of 4 July 2024, expect proof of consent: electronic records of name, national number, phone, date and method, with an in-app activation message accepted as a method. Sharing sensitive data needs the Authority's approval. After a breach, Article 8 of the law requires telling the Authority immediately, sending details within 72 hours and telling affected users within three working days of that notice, and Article 37 sets heavier penalties for sensitive data. Build the consent log and the incident plan before launch.

Hosting

Where the servers go

The Ministry of Communications decision of 16 April 2025 lets apps in general be hosted abroad, but health apps answer to stricter texts. The NAITS rulebook (version 3, 2025) keeps health data out of hosting abroad, and Decision 24/ت requires servers inside Syria for every medical and health app. The application form still has an 'outside Syria' box; we would not read it as permission. Nor does Law No. 12's consent exception for transfers made to provide medical care (Article 15(b)(1)) lift the hosting rule.

Inside Syria, the state National Data Center says it offers shared hosting, virtual private servers, colocation and backups to private companies as well as public bodies, and NAITS accredits companies that sell hosting to the private sector. We found no published source naming a private commercial data centre. Decide early: the host is named in your application, and changes to an approved app need approval. See data localization and hosting for users in Syria.

Doctors

Doctors, advertising and video consultations

Legislative Decree 12 of 1970, which the ministry still cites, allows medical practice only with the certificate, ministry registration and a permanent or temporary ministry licence, and both licence types need syndicate registration too. We read the ministry's copy; later amendments were not checked. We found no public online licence lookup, so the check falls on the app: collect the specialty, licence number and date, keep copies, review every profile, and take specialties from the licence, since Decision 24/ت bars advertising specialties a licence does not include.

Article 47 of the decree bars doctors from advertising themselves, beyond a single newspaper notice of up to two weeks in set cases such as starting practice in a town or moving clinic, and from deals with anyone to steer patients to their clinic. It predates the internet, so how it applies online is not stated. Paid featured listings, per-referral fees and public ratings sit close to it; have a lawyer review the business model.

We found no Ministry of Health rule dedicated to telemedicine as of 20 November 2026. In-app consultations fall under Decision 24/ت: documented, and given by ministry-licensed professionals, so a doctor licensed only abroad would need a Syrian licence (temporary ones exist for Arabs and foreigners). The NAITS rulebook allows medical consultations in an app if they are stored for at least six months, and some registry entries include voice or video consultations in their approved services: proof they can be approved, not that anyone may offer them. Ask the ministry and a lawyer first. DocDoc used WebRTC for in-app consultations; a Syrian version one can launch without video.

How to build it

Version one, step by step

  1. Fix the scope you apply with

    The ministry approves a specific version, so settle every version one feature before you file.

  2. Model the schedule first

    Doctors, clinics, hours and days off come before any screen. Store times in UTC, show Damascus time, start weeks on Saturday.

  3. Make booking atomic

    Hold, confirm, commit, with a double-booking constraint and live updates. Test it with two phones tapping one slot.

  4. Onboard with licence data

    No doctor or clinic goes public without a licence number, a licence date and a human review.

  5. Build sign-up and consent together

    A phone code through a provider tested on Syriatel and MTN, a consent record, and a guardian step for children.

  6. Host in Syria, then apply

    Servers inside Syria, access logs, a documented export and a breach plan, then the licence file with a fully working build.

FAQ

Common questions

Yes. Decision 24/ت covers any mobile or web app offering medical or health services, and booking apps already appear on the ministry's register. You need the ministry's approval, valid for two calendar years, then NAITS accreditation.

Sources

Where these facts come from

  1. Regulatory Decision 24/ت on licensing electronic medical and health apps (signed scan)Ministry of Health · 2 Dec 2025
  2. Licensing health apps: procedure, stages and FAQMinistry of Health · read 20 Nov 2026
  3. Annex 1: licence application form (services, platforms, developer, hosting)Ministry of Health · read 20 Nov 2026
  4. Annex 2: required documentsMinistry of Health · read 20 Nov 2026
  5. Circular 19/20449: existing private health apps must apply by 2 December 2026Ministry of Health · Sep 2026
  6. Ministry of Health sets a deadline for licensing private health appsSANA · 21 Sep 2026
  7. Deadline reminder on the ministry's official channelMinistry of Health (Telegram) · 18 Nov 2026
  8. Decision 24/ت and the public registry, explained by the ministry official in chargeSANA · 11 Oct 2026
  9. Register of electronic health appsMinistry of Health · read 20 Nov 2026
  10. Personal Data Protection Law No. 12 of 2024 (PDF)Ministry of Communications and IT · 28 Mar 2024
  11. Law No. 12 of 2024, full text (Articles 8 and 37)Al-Mashhad Online · 28 Mar 2024
  12. Executive instructions of Law No. 12, Decision 29 (signed scan)Council of Ministers, hosted by the Ministry of Communications and IT · 4 Jul 2024
  13. Legislative Decree 12 of 1970 on practising the medical professions (ministry-hosted copy)Ministry of Health · 7 Jan 1970
  14. NAITS rulebook on accrediting electronic applications, version 3 (hosting, in-app consultations)NAITS · 25 May 2025
  15. Ministry decision on electronic apps (notification, hosting abroad)SANA · 16 Apr 2025
  16. How the National Data Center supports digital servicesMinistry of Communications and IT · 21 Sep 2026
  17. NAITS licences and accreditations (incl. private hosting providers)NAITS · accessed 15 Nov 2026
  18. Twilio SMS guidelines for Syria (delivery stopped 15 September 2025)Twilio · accessed 15 Nov 2026
  19. WhatsApp Cloud API country restrictionsMeta for Developers · accessed 15 Nov 2026
  20. SMS coverage and connectivity (Syria row)Infobip · accessed 15 Nov 2026
  21. Identity Platform pricing (SMS price for Syria)Google Cloud · accessed 15 Nov 2026
  22. Decision 1124: the Electronic Payment and Transfer SystemCentral Bank of Syria · 18 Aug 2026
  23. Stripe Restricted Businesses policyStripe · updated 22 Sep 2026

Checked 20 November 2026 (the SMS, payment and hosting provider rows on 15 November 2026). The Ministry of Health is applying Decision 24/ت now, with a deadline on 2 December 2026, so re-check its licensing page before you rely on any of this.

Building a booking app for clinics in Syria?

We designed and built DocDoc as part of its founding team. Tell us about your clinics, and we will help you scope version one with the licence in mind.