Use case · Patient Platform

Online Appointment Booking

Online appointment booking is the patient-facing surface for scheduling clinical encounters — outpatient consultations, day procedures, follow-ups, and teleconsultations — directly into the institution's calendar of record. In HealthOS, booking is not a separate scheduling product integrated to a clinical system; it is the same record the institution uses, exposed to the patient.

Last reviewed:

What hospitals struggle with

In Fragmentation-Era hospitals, patient-facing booking is a separate scheduling product. The clinician's calendar lives in the EHR; the patient's booking lives in a portal vendor's database; reconciliation is a daily operational task and a recurring source of double-booking and missed appointments.


How HealthOS runs it

The institutional workflow.

  1. 01

    Patient opens the institution's Patient Platform on a device of their choice.

  2. 02

    Available slots are read directly from the same calendar the clinician uses — no synchronization layer.

  3. 03

    Booking confirms instantly; the appointment, prep instructions, and check-in code arrive on the patient's device.

  4. 04

    Clinician's worklist is updated in the same atomic transaction; institutional capacity counters update simultaneously.

  5. 05

    If the appointment is moved or cancelled, the entire chain — patient, clinician, billing, insurance precertification — updates as one event.


Canonical layer

This workflow runs on the Patient Platform.

The Patient Platform is one of the layers of HealthOS. It is not a separate product; it is a property of the substrate. See the Patient Platform layer →


Frequently asked

Is this a separate booking product?

No. Booking is a property of the Patient Platform layer in HealthOS. The patient and the clinician operate on the same calendar.

Can patients book teleconsultations?

Yes. Teleconsultations and in-person appointments are surfaced as the same booking object, with modality declared on the slot.

Is this suitable for a single clinic?

Yes. The same architecture that runs national networks runs a single clinic. See /scale/single-facility.

Position

The booking surface is the operational surface. They are the same object — the patient's view onto the institution's calendar, not a synchronization between two systems. Signed by the Veronara Patient Platform Office.

Dated · Propose a correction to corrections@veronara.com.


Engage Veronara.

Executive briefings are offered to hospital networks, ministries of health, and enterprise healthcare institutions.


Request Executive Briefing

For hospital networks and enterprise healthcare institutions.

Acknowledged within two business days.


Government & National Inquiries

For ministries of health, national digital health programs, and sovereign deployments.

Acknowledged within 72 hours.


Investor Relations

For qualified institutional investors.

Reviewed by institutional engagement.


Online Appointment Booking — Veronara