Move your clinic's appointment book onto the patient's phone

At nine in the morning three call centre lines ring at once, a queue builds at reception, and because one doctor has been signed off sick every appointment in the day has to be moved one by one. As long as the appointment book lives only on the HBYS screen and at the end of a phone line, that load sits on your staff. A mobile app moves booking, rescheduling and reminders onto the patient's phone.

How many separate apps does this need?

  • 01

    Patient mobile app (iOS + Android)

    Specialty and doctor selection, available-slot calendar, one-tap cancellation and rescheduling, appointment reminders, past visit history, test result viewing, and details of contracted insurers.

  • 02

    Doctor and clinic staff app

    The doctor's daily list, patient summary card, consultation duration settings, leave and on-call notifications, plus a quick-entry screen so reception can log phone bookings into the same calendar.

  • 03

    Web admin panel

    Slot rules per outpatient department and doctor, bulk appointment shifting, waiting list management, contracted insurer and pricing setup, no-show rate and utilisation reports, and user permissions.

What the app includes

  • Doctor and fee list filtered by the patient's contracted insurer
  • Patient matching by national ID, merging of duplicate files
  • Booking for children and dependants from one account
  • Digital medical history and consent form before the visit
  • Room and device calendar (ultrasound, echo, endoscopy) conflict check
  • QR self check-in on arrival with queue number
  • Live queue position and estimated waiting time per clinic
  • Automatic follow-up invitation on the date the doctor sets
  • Session plan and absence tracking for course-based therapy
  • e-prescription and report numbers pushed to the patient (Turkey's e-Reçete system)
  • On-call and standby rota reflected in the booking calendar
  • Deposit requirement triggered by a patient's no-show history

State of the sector

Patients now choose a provider partly on whether they can book from their phone; hospital chains and large medical centres have offered that channel for years. A newly opened medical centre or single-site clinic that only takes bookings by phone loses every request that arrives outside office hours and has no way to refill a no-show's slot. When follow-up appointments go unreminded, treatment is left half-finished and the patient goes elsewhere next time. The competitive pressure comes less from price than from accessibility: how many days it takes a patient to find the first available slot, and how easily they can change an appointment, has become the deciding factor.

Metrics that matter here

  • No-show rate — The reminder chain, one-tap cancellation and optional deposit directly reduce the number of empty doctor hours.
  • Share of booking requests reaching the call centre — As cancellations, rescheduling and new bookings move to self-service, phone volume and the queue at reception fall.
  • Time to the first available appointment — Opening a freed slot to the waiting list immediately shortens how many days a patient has to wait.
  • Follow-up appointment return rate — An automatic reminder on the date the doctor set for the follow-up keeps treatment courses from being left unfinished.

Common mistakes in this sector

  • Keeping the app's appointment calendar separate If the app uses its own calendar while reception uses the HBYS calendar, you get double bookings. One source has to be designated as authoritative and the other channel has to read from it. Otherwise someone reconciles the two by hand every day.
  • Making cancellation hard Hiding the cancel option does not lower the no-show rate; it just keeps the slot occupied until the last minute. One-tap cancellation from the notification, with the freed slot opening to the waiting list, protects utilisation far better than friction does.
  • Giving every consultation a fixed duration When first consultations, follow-ups and interventional procedures are squeezed into the same slot length, either patients are kept waiting or the doctor sits idle. Durations must be configurable from the panel per doctor and per procedure type.
  • Cramming test results into the first release Result viewing has to be built together with the doctor approval flow, access logging and retention rules. Trying to ship it at the same time as the appointment flow leaves both half-finished; the results module belongs in phase two.

Regulation and compliance

Under KVKK (Turkey's data protection law, aligned with GDPR), health data is classed as special-category personal data: appointment, diagnosis and test records require explicit consent, separate storage and access authorisation. Turkey's Regulation on Personal Health Data brings access logging and domestic data hosting into scope, and the healthcare provider is responsible for its VERBIS (data controllers' registry) registration. Practical obligations include data reporting to e-Nabız (the Ministry of Health's national health record system), authorisation and invoicing through Medula (the social security institution's health claims system) for SGK-covered treatments, and issuing e-Fatura/e-Arşiv (Turkey's mandatory e-invoicing system) for paid services. Promotional messages require consent via İYS (Turkey's commercial message consent registry); appointment reminders should be kept separate as purely informational messages.

The real challenges in this sector

Required integrations

  • HBYS (hospital information system) integration via HL7 v2 messaging or FHIR services for patient and appointment sync
  • Matching SGK authorisation and invoicing flows through Medula (the social security health claims system) to the appointment record
  • Record transfer that meets reporting obligations to e-Nabız (the Ministry of Health's national health record system)
  • e-Fatura and e-Arşiv (Turkey's mandatory e-invoicing system, via GİB, the Turkish Revenue Administration) for billing paid consultations and packages
  • 3D Secure prepayments and deposits via iyzico, PayTR (Turkish payment providers) or a bank virtual POS
  • Pulling approved result reports from laboratory (LIS) and imaging (PACS) systems

Who this page is for

  • Single-site clinic or private practice

    With a handful of doctors, multi-site resource management and lab integration are unnecessary; start with the calendar, reminders, cancel and reschedule, and a simple patient card.

  • Newly opened multi-specialty medical centre

    Here the real work is per-specialty slot rules, contracted insurers and fee tables, room and device conflicts, and one shared calendar with the hospital system; a waiting list and deposits protect occupancy from day one.

  • Course-based clinic (physiotherapy, dental, aesthetics)

    The unit is not one appointment but a course spread over weeks: package sales, making up missed sessions, remaining-session balance and per-therapist calendars matter most; a results module is often not needed at all.

A phased plan that splits the budget

  1. 1

    Phase 1 — Working booking core for a single clinic 5-7 hafta

    Specialty and doctor selection, the slot engine with short-lived slot locking, the reminder chain, one-tap cancel and reschedule, a fast reception entry screen and doctor calendars in the panel. This alone moves most phone bookings into the app and is usable without any later phase.

  2. 2

    Phase 2 — Occupancy, payment and HBYS connection 4-6 hafta

    Waiting list with released slots offered to the first patient who accepts, deposits and prepayment, contracted-insurer and fee definitions, room and device resources, QR check-in, and integration with the hospital information system. It only makes sense once the calendar has a single source of truth, hence the ordering.

  3. 3

    Phase 3 — Result viewing and institutional reporting 4-6 hafta

    Lab and imaging results shown after physician approval, time-limited links and access audit logs, matching with Medula (Turkey's social-security claim system), reporting to e-Nabız (the Ministry of Health data platform), multi-site setup and no-show reporting. Health data needs its own security design, so it is deliberately left last.

Typical scope and timeline

Typical scope: the patient app (iOS and Android), doctor and reception screens, and a web admin panel; the slot engine, reminders and waiting list, payment infrastructure, HBYS integration and access logging that meets KVKK requirements. UI/UX design, store assets, ASO, QA and the App Store and Google Play release process are included. Result viewing is usually moved to a second phase.

Estimated timeline: 12-18 weeks

Off-the-shelf or custom build?

Topic Off-the-shelf Custom build
Connecting to the hospital information system Off-the-shelf products often ship connectors for the common systems; if your vendor is on the list it works in days, if not you join a roadmap queue. Custom work is written against whatever your system exposes, HL7 v2, FHIR or read access; if nothing is exposed, the app's calendar becomes the source of truth.
Slot rules and procedure durations Fixed slots and a simple doctor calendar are more than enough for most single-specialty practices: quick to set up, easy for staff to learn. Procedure-dependent durations, device and room dependencies, therapy series and on-call rotas can only be modelled in your own slot engine.
Monthly subscription versus one-time ownership A monthly fee keeps the entry cost low and leaves maintenance and updates with the vendor, but it grows with doctor count and booking volume. Custom development front-loads the cost and leaves an annual maintenance line; growing doctor and patient volume adds no per-seat charge.
Ownership and portability of patient data Data sits in the vendor's cloud; most packages allow an export, yet hosting location and retention period are not your decision. Appointment and health records stay on your own servers; the special-category requirements of KVKK (Turkey's data protection law), local hosting and access logs follow your own policy.

Sector glossary

Block booking (quota)
Reserving part of a doctor's day for one purpose only, such as follow-up patients, a contracted insurer or procedures, with that block kept closed to ordinary online booking.
No-show
A patient who neither attends nor cancels. It burns the doctor's hour and blocks the next patient from that slot; clinics track it per doctor, specialty and time of day.
Provizyon (SGK pre-authorisation)
Pre-authorisation obtained through Medula for a procedure covered by SGK, Turkey's social security institution. Without it a claim can be rejected, so the appointment record must carry the matching authorisation number.
HL7 v2 and FHIR
The two ways clinical systems talk to each other. Older hospital systems usually emit HL7 v2 messages, newer ones expose FHIR services; which one your vendor opens dictates how long integration takes.
On-call standby duty
Duty where the doctor is not on site but must come in if called. It should never appear as bookable clinic time, yet it still has to affect availability in planning.

Frequently asked questions

Let us talk about your project

A free 30-minute call to scope it out, then an itemised quote within 48 hours.

Get a Free Quote

This page explains the problems an app must solve in this sector. We share references and comparable projects during the call.

Other sectors

All sectors →