Difference between revisions of "Appointment Management"
From Hiasobi - FHIR
Brett Esler (Talk | contribs) (→Information) |
Brett Esler (Talk | contribs) (→Information) |
||
| Line 2: | Line 2: | ||
== Information == | == Information == | ||
| − | See: [http://hl7.org/fhir/STU3/appointment.html Appointment] | + | See: Core FHIR Resources [http://hl7.org/fhir/STU3/appointment.html Appointment], [http://hl7.org/fhir/STU3/schedule.html Schedule], [http://hl7.org/fhir/STU3/schedule.html Slot] |
| + | |||
| + | Todo: Oridashi Profiles for Appointment, Schedule and Slot | ||
== Available Slots == | == Available Slots == | ||
Revision as of 15:07, 13 October 2017
Contents
Information
See: Core FHIR Resources Appointment, Schedule, Slot
Todo: Oridashi Profiles for Appointment, Schedule and Slot
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
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
