Difference between revisions of "Appointment Management"
From Hiasobi - FHIR
(→Appointment Accept/Reject) |
Brett Esler (Talk | contribs) |
||
Line 12: | Line 12: | ||
Extension - nominal period of slots | Extension - nominal period of slots | ||
− | Free/busy slots that represent a | + | Free/busy slots that represent a period for an appointment; these may be already booked or currently free |
Slot | Slot | ||
Line 22: | Line 22: | ||
GET [base]/Appointment?status=proposed&location.identifier=<siteid> | GET [base]/Appointment?status=proposed&location.identifier=<siteid> | ||
+ | |||
+ | e.g. | ||
+ | |||
+ | http://fhir3.healthintersections.com.au/open/Appointment?location.identifier=2E421477117F949B63F565953EE12E6E&_include=Appointment:actor&_format=json | ||
Revision as of 09:57, 23 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 period 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>
e.g.
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