This fragment is not visible to the reader
This publication includes IP covered under the following statements.
| Type | Reference | Content |
|---|---|---|
| web | tel:+436501234567890 | +436501234567890 |
| web | booking.example.com | Appointment Booking URL : https://booking.example.com/slot/297c0007-f8d1-4e47-bddb-a47978607f65 |
| web | github.com | Austrian Appointment Scheduling (R5), published by HL7® Austria, TC FHIR®. This guide is not an authorized publication; it is the continuous build for version 0.2.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7Austria/TC-FHIR-AG-Scheduling-R5/ and changes regularly. See the Directory of published versions |
| web | fhir.hl7.at |
Appointment.participant.actor ( HL7® AT Core Practitioner , Group , CareTeam , Device , HL7® AT Core Patient , HealthcareService , HL7® AT Core PractitionerRole , RelatedPerson , Location ) |
| web | fhir.hl7.at |
Appointment.participant.actor ( HL7® AT Core Practitioner , Group , CareTeam , Device , HL7® AT Core Patient , HealthcareService , HL7® AT Core PractitionerRole , RelatedPerson , Location ) |
| web | fhir.hl7.at |
Appointment.participant.actor ( HL7® AT Core Practitioner , Group , CareTeam , Device , HL7® AT Core Patient , HealthcareService , HL7® AT Core PractitionerRole , RelatedPerson , Location ) |
| web | github.com | Sebastian Altenhuber |
| web | github.com | Armin Berger |
| web | github.com | Samuel Brendler |
| web | github.com | Reinhard Egelkraut |
| web | github.com | Minas Gerges |
| web | github.com | Hans-Jürgen Schiller |
| web | fhir.hl7.at |
This implementation guide is based on FHIR R5 and builds on the HL7® AT Core profiles (R5)
. R5 was chosen because it significantly improves the scheduling-related resources compared to R4, e.g. the Appointment.virtualService
element for virtual appointments and the use of CodeableReference
for linking Schedules, Slots and Appointments to HealthcareServices. As a newly created guide without an existing R4-based installed base, there was also no legacy constraint that would have justified staying on an older FHIR version. Wherever an Austrian core profile exists (Patient, Practitioner, PractitionerRole, Organization, Location), it is referenced instead of the base resource to ensure consistency with other Austrian implementation guides.
|
| web | profiles.ihe.net |
Rather than designing a scheduling workflow from scratch, this guide adapts the concepts of the German ISiK Modul "Terminplanung"
(gematik) and IHE Scheduling
(IHE ITI) implementation guides to the Austrian context. This keeps the Austrian specification aligned with internationally established patterns and lowers the implementation effort for vendors already familiar with those guides. The most important differences concern how the FHIR Resources Slot
and Appointment
are used to discover availability, and which use cases are in scope.
|
| web | profiles.ihe.net |
IHE Scheduling (Appointment-centric discovery).
Availability is exposed as proposed
Appointment
Resources. The Find Potential Appointments
transaction ( ITI-115
) returns a searchset
Bundle of Appointment
Resources, and the subsequent Hold
( ITI-116
) and Book
( ITI-117
) transactions operate on that same Appointment
. Schedule
and Slot
exist conceptually but remain largely server-internal — the client never browses Slots directly. The entire workflow is Appointment-centric.
|
| web | profiles.ihe.net |
IHE Scheduling (Appointment-centric discovery).
Availability is exposed as proposed
Appointment
Resources. The Find Potential Appointments
transaction ( ITI-115
) returns a searchset
Bundle of Appointment
Resources, and the subsequent Hold
( ITI-116
) and Book
( ITI-117
) transactions operate on that same Appointment
. Schedule
and Slot
exist conceptually but remain largely server-internal — the client never browses Slots directly. The entire workflow is Appointment-centric.
|
| web | profiles.ihe.net |
IHE Scheduling (Appointment-centric discovery).
Availability is exposed as proposed
Appointment
Resources. The Find Potential Appointments
transaction ( ITI-115
) returns a searchset
Bundle of Appointment
Resources, and the subsequent Hold
( ITI-116
) and Book
( ITI-117
) transactions operate on that same Appointment
. Schedule
and Slot
exist conceptually but remain largely server-internal — the client never browses Slots directly. The entire workflow is Appointment-centric.
|
| web | developer.mozilla.org |
Scheduling Clients SHALL use the following HTTP request Prefer Header
for requests of standard POST
and PUT
interactions:
|
| web | fhir.hl7.at | A Scheduling Client can create a Patient on a Scheduling Server. This is a prerequisite for booking an Appointment in which this Patient participates. The HL7® AT Core Patient Profile SHALL be used by both the Scheduling Client for the request as well as the Scheduling Server in the response. |
| web | github.com | This implementation guide is developed and maintained on GitHub . |
|
interactions/book-appointment.svg
|
|
interactions/cancel-appointment-client.svg
|
|
interactions/cancel-appointment-server.svg
|
|
interactions/create-patient.svg
|
|
interactions/find-existing-appointments.svg
|
|
interactions/find-healthcareService-Providers.svg
|
|
interactions/find-healthcareServices.svg
|
|
interactions/find-schedules.svg
|
|
interactions/find-slots.svg
|
|
interactions/hold-slot.svg
|
|
interactions/postpone-appointment-client.svg
|
|
interactions/postpone-appointment-server.svg
|
|
interactions/update-appointment-information-client.svg
|
|
interactions/update-appointment-information-server.svg
|
|
scenarios/scheduling-platform.svg
|
|
scenarios/sequence-platform-external.svg
|
|
scenarios/sequence-platform.svg
|
|
scenarios/sequence-simple.svg
|
|
scenarios/simple-booking.svg
|
|
tree-filter.png
|