Difference between revisions of "Appointment Management"
From Hiasobi - FHIR
Brett Esler (Talk | contribs) (→Information) |
Brett Esler (Talk | contribs) (→Available Slots) |
||
Line 7: | Line 7: | ||
== Available Slots == | == Available Slots == | ||
− | + | * Schedules (Appointment Book) can be retrieved from FHIR interface (FHIR Schedule) | |
− | Practitioner | + | * Each FHIR Schedule is for a provider (FHIR Practitioner); there may be multiple sessions per day |
− | + | * A FHIR extension defines the nominal slot period length for each Schedule | |
− | + | * Free/Busy slots are available (FHIR Slot) | |
− | + | ||
− | + | ||
− | Free/ | + | |
− | + | ||
− | + | ||
− | + | ||
==Appointments Requiring Action== | ==Appointments Requiring Action== |
Revision as of 15:18, 13 October 2017
Contents
Information
See: Core FHIR Resources Appointment, Schedule, Slot
Todo: Oridashi Profiles for Appointment, Schedule and Slot
Available Slots
- Schedules (Appointment Book) can be retrieved from FHIR interface (FHIR Schedule)
- Each FHIR Schedule is for a provider (FHIR Practitioner); there may be multiple sessions per day
- A FHIR extension defines the nominal slot period length for each Schedule
- Free/Busy slots are available (FHIR Slot)
Appointments Requiring Action
Search for requested/cancelled appointments on the server; include all the participants
GET [base]/Appointment?status=pending&location.identifier=<siteid>&_include=Appointment:actor
e.g.
Server provides a list of appointments that are requested
Appointment status = pending start end slot - optional reference participant [0] type = PPRF actor is Practitioner required = required status = needs-action participant [1] type = null actor is Patient required = required status = accepted participant [2] type = null actor is HealthcareService providedBy = (reference to organization) serviceCategory = (appointments calendar) required = required status = needs-action
Appointment Accept/Reject
Clinic will update appointment to accept or reject it
PUT [base]/Appointment/<id>
Structure is like:
Appointment participant[0] status = accepted | declined participant[2] status = accepted | declined