Difference between revisions of "201601 Scheduling"
| Line 45: | Line 45: | ||
Which tie together the 4 resources... | Which tie together the 4 resources... | ||
| − | === | + | ===Create Appointment=== |
| + | :Action: <!--Who does what? (Use the role names listed above when referring to the participants --> | ||
| + | :Precondition: <!-- What setup is required prior to executing this step? --> | ||
| + | :Success Criteria: <!-- How will the participants know if the test was successful? --> | ||
| + | :Bonus point: <!-- Any additional complexity to make the scenario more challenging --> | ||
| + | |||
| + | <!-- Provide a description of each task --> | ||
| + | |||
| + | ===Check Schedule=== | ||
| + | :Action: <!--Who does what? (Use the role names listed above when referring to the participants --> | ||
| + | :Precondition: <!-- What setup is required prior to executing this step? --> | ||
| + | :Success Criteria: <!-- How will the participants know if the test was successful? --> | ||
| + | :Bonus point: <!-- Any additional complexity to make the scenario more challenging --> | ||
| + | |||
| + | <!-- Provide a description of each task --> | ||
| + | |||
| + | ===Process Appointment (Response)=== | ||
| + | :Action: <!--Who does what? (Use the role names listed above when referring to the participants --> | ||
| + | :Precondition: <!-- What setup is required prior to executing this step? --> | ||
| + | :Success Criteria: <!-- How will the participants know if the test was successful? --> | ||
| + | :Bonus point: <!-- Any additional complexity to make the scenario more challenging --> | ||
| + | |||
| + | <!-- Provide a description of each task --> | ||
| + | |||
| + | ===Cancel Appointment=== | ||
:Action: <!--Who does what? (Use the role names listed above when referring to the participants --> | :Action: <!--Who does what? (Use the role names listed above when referring to the participants --> | ||
:Precondition: <!-- What setup is required prior to executing this step? --> | :Precondition: <!-- What setup is required prior to executing this step? --> | ||
Revision as of 20:35, 25 November 2015
Scheduling
Submitting WG/Project/Implementer Group
Patient Administration (PA)
Justification
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
Roles
Server
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.
Requester
A client that creates appointments (as either booked resources, or requests which need a placer to fill)
Placer
A placer is a client (or server) that processes appointment requests and allocates either participants, or times to these requests.
Scenarios
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 http://hl7.org/fhir/appointment.html#5.27.1.1 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 http://hl7.org/fhir/appointment.html#typical Which tie together the 4 resources...
Create Appointment
- Action:
- Precondition:
- Success Criteria:
- Bonus point:
Check Schedule
- Action:
- Precondition:
- Success Criteria:
- Bonus point:
Process Appointment (Response)
- Action:
- Precondition:
- Success Criteria:
- Bonus point:
Cancel Appointment
- Action:
- Precondition:
- Success Criteria:
- Bonus point:
