Difference between revisions of "Appointment Management"

Revision as of 22:25, 24 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=proposed&location.identifier=<siteid>

e.g.

http://fhir3.healthintersections.com.au/open/Appointment?location.identifier=2E421477117F949B63F565953EE12E6E&_include=Appointment:actor&_format=json

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

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