Difference between revisions of "Appointment Management"
From Hiasobi - FHIR
(→Request Appointment) |
(→Appointment Accept/Reject) |
||
Line 50: | Line 50: | ||
== Appointment Accept/Reject == | == Appointment Accept/Reject == | ||
+ | |||
Update appointment to accept or reject it | Update appointment to accept or reject it | ||
+ | |||
+ | PUT [base]/Appointment/<id> | ||
+ | |||
+ | |||
+ | Structure is like: | ||
Appointment | Appointment |
Revision as of 16:16, 20 November 2016
Information
See: [1]
Available Slots
Practitioner schedule sessions in this implementation these are complete sessions - there may be multiple sessions per day
Schedule Extension - nominal period of slots
Free/busy slots that represent a tperiod for an appointment; these may be already booked or currently free
Slot
Request Appointment
Search for requested appointments
GET [base]/Appointment?status=proposed&location.identifier=<siteid>
Server provides a list of appointments that are requested
Appointment status = proposed 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
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