Schedule a demo
Care coordination

Appointment booking

This scenario models a patient booking a follow-up visit after an earlier encounter. Scheduling systems expose a service calendar, open slots are available at convenient times, and the patient secures a reservation without conflicts or double-booking.

12resources / instance
10FHIR types
10instances
appointment_booking.py
from zato_fhir.test.r4.v1 import Scenarios, TestData

for booking in Scenarios.appointment_booking:
    for name in booking.patient.name:
        print(name.text)

    for name in booking.practitioner.name:
        print(name.text)

    print(booking.organization.name)

    for enc in booking.encounters:
        print(enc.status)

    print(booking.appointment.status)
    print(booking.appointment_response.participantStatus)
    print(booking.schedule.active)
    print(booking.slot.status)
    print(booking.healthcare_service.active)
    print(booking.endpoint.status)

for appt in TestData.Appointment:
    print(appt.status)

About this scenario

This scenario models a patient booking a follow-up visit after an earlier encounter. Scheduling systems expose a service calendar, open slots are available at convenient times, and the patient secures a reservation without conflicts or double-booking.

Both the clinic and the patient affirm the appointment through responses, and the healthcare service definition plus endpoint metadata give integrators enough context to route notifications or telehealth links. The flow completes with everyone aligned on time, place, and service type.

FHIR resources in this scenario

12 resources per instance, 120 total across 10 instances.

FHIR resource typeRole in this scenario
PatientPerson booking the follow-up
PractitionerClinician associated with the visit
OrganizationScheduling organization
EncounterPrior or anchor encounter context
AppointmentProposed or booked appointment
AppointmentResponseParticipant acceptance or tentative reply
ScheduleContainer of availability
SlotBookable time interval
HealthcareServiceService being scheduled
EndpointTechnical address for integrations
FHIR resources per instance12
Total resources (10 instances)120
Distinct resource types10
Scenario identifier`Scenarios.appointment_booking`

At a glance

12
FHIR resources per instance
120
Total resources (10 instances)
10
Distinct resource types
Scenarios.appointment_booking
Scenario identifier

Ready to build integrations?

Get started with Zato and connect your systems in minutes.

Open source In Python