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 36: Line 36:
 
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.
 
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: [http://hl7.org/fhir/2015Sep/appointment.html Appointment] [http://hl7.org/fhir/2015Sep/appointmentresponse.html AppointmentResponse] [http://hl7.org/fhir/2015Sep/schedule.html Schedule] [http://hl7.org/fhir/2015Sep/slot.html Slot]
+
Specification Page(s): [http://hl7.org/fhir/2015Sep/appointment.html Appointment] [http://hl7.org/fhir/2015Sep/appointmentresponse.html AppointmentResponse] [http://hl7.org/fhir/2015Sep/schedule.html Schedule] [http://hl7.org/fhir/2015Sep/slot.html Slot]
  
 
<!-- What will be the actions performed by participants? -->
 
<!-- What will be the actions performed by participants? -->
The intro section on the "usual" workflow
+
The introduction section on the "usual" workflow can be found here:
 
http://hl7.org/fhir/appointment.html#5.27.1.1
 
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
+
 
 +
If you're trying to work out what statuses mean, and what would be expected, there is a summary at the bottom of that same page including a collection of examples
 
http://hl7.org/fhir/appointment.html#typical
 
http://hl7.org/fhir/appointment.html#typical
 
Which tie together the 4 resources...
 
Which tie together the 4 resources...
  
 
===Create Appointment===
 
===Create Appointment===
:Action: <!--Who does what?  (Use the role names listed above when referring to the participants -->
+
:Action: Create an appointment resource and store on a server (Requester)
:Precondition: <!-- What setup is required prior to executing this step? -->
+
:Precondition: None
:Success Criteria: <!-- How will the participants know if the test was successful? -->
+
:Success Criteria: Appointment passes validation against the Appointment schema and schematron
:Bonus point: <!-- Any additional complexity to make the scenario more challenging -->
+
:Bonus point: Define an Appointment with multiple participants
 +
:Bonus point: Define an appointment with a Location
 +
:Bonus point: Define an Appointment with varied Participant statuses
 +
:Bonus point: Define an Appointment against multiple slots
  
 
<!-- Provide a description of each task -->
 
<!-- Provide a description of each task -->

Revision as of 20:39, 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(s): Appointment AppointmentResponse Schedule Slot

The introduction section on the "usual" workflow can be found here: http://hl7.org/fhir/appointment.html#5.27.1.1

If you're trying to work out what statuses mean, and what would be expected, there is a summary at the bottom of that same page including a collection of examples http://hl7.org/fhir/appointment.html#typical Which tie together the 4 resources...

Create Appointment

Action: Create an appointment resource and store on a server (Requester)
Precondition: None
Success Criteria: Appointment passes validation against the Appointment schema and schematron
Bonus point: Define an Appointment with multiple participants
Bonus point: Define an appointment with a Location
Bonus point: Define an Appointment with varied Participant statuses
Bonus point: Define an Appointment against multiple slots


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:


TestScript(s)