This wiki has undergone a migration to Confluence found Here

Difference between revisions of "201601 Scheduling"

From HL7Wiki
Jump to navigation Jump to search
Line 37: Line 37:
Specification Page: [ Appointment] [ AppointmentResponse] [ Schedule] [ Slot]
Specification Page: [ Appointment] [ AppointmentResponse] [ Schedule] [ Slot]
Pre-requisites: none
<!-- What will be the actions performed by participants? -->
<!-- What will be the actions performed by participants? -->

Revision as of 20:33, 25 November 2015


Submitting WG/Project/Implementer Group

Patient Administration (PA)


This track will extend on the experience that was had at the last connectathon and help improve the experience with these resources, and extend into the Encounter resource.

Proposed Track Lead

Coordinator: Brian Postlethwaite

Expected participants

Brian Postlethwaite - HealthConnex



A Server Role can be either a simple FHIR server that just stores the scheduling resources, or could be smart and perform placing/allocation services on the appointment requests coming in.


A client that creates appointments (as either booked resources, or requests which need a placer to fill)


A placer is a client (or server) that processes appointment requests and allocates either participants, or times to these requests.


If creating a client application, this track should require minimal work in advance of the connectathon, though at least a bit of playing is recommended. If creating a server, advanced preparation will be required, but this scenario should somewhat limit the effort involved.

Specification Page: Appointment AppointmentResponse Schedule Slot

The intro section on the "usual" workflow And once you're working out what statuses mean, and what would be expected, at the bottom of that same page is a collection of examples Which tie together the 4 resources...

Scenario Step 1 Name

Success Criteria:
Bonus point: