Difference between revisions of "Appointment Management"
From Hiasobi - FHIR
Brett Esler (Talk | contribs) |
Brett Esler (Talk | contribs) (→Request Appointment) |
||
| Line 21: | Line 21: | ||
Search for requested appointments on the server | Search for requested appointments on the server | ||
| − | GET [base]/Appointment?status= | + | GET [base]/Appointment?status=pending&location.identifier=<siteid> |
e.g. | e.g. | ||
| Line 31: | Line 31: | ||
Appointment | Appointment | ||
| − | status = | + | status = pending |
start | start | ||
end | end | ||
Revision as of 21:59, 30 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 on the server
GET [base]/Appointment?status=pending&location.identifier=<siteid>
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
