This wiki has undergone a migration to Confluence found Here

Difference between revisions of "201601 Scheduling"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "{{subst::Template for FHIR Connectathon Track Proposals}}")
 
Line 2: Line 2:
 
[[Category:201601_FHIR_Connectathon_Track_Proposals|Jan 2016 Proposals]]
 
[[Category:201601_FHIR_Connectathon_Track_Proposals|Jan 2016 Proposals]]
 
__NOTOC__
 
__NOTOC__
=Track Name=
+
=Scheduling=
  
 
==Submitting WG/Project/Implementer Group==
 
==Submitting WG/Project/Implementer Group==
<!-- Who is asking for this track? -->
+
Patient Administration (PA)
  
 
==Justification==
 
==Justification==
 
<!--Why is this an important track to include in the connectathon - include implementer need, impact on ballot, FMM readiness of the resources, etc. -->
 
<!--Why is this an important track to include in the connectathon - include implementer need, impact on ballot, FMM readiness of the resources, etc. -->
 +
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==
 
==Proposed Track Lead==
<!-- Name, email and Skype id of individual who will coordinate the track at the connectathon -->
+
Coordinator: [mailto:bpostlethwaite@healthconnex.com.au Brian Postlethwaite]
 +
 
  
 
==Expected participants==
 
==Expected participants==
 
<!-- List of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track -->
 
<!-- List of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track -->
 +
Brian Postlethwaite - HealthConnex
  
 
==Roles==
 
==Roles==
 
<!-- Roles are sets of functionality (generally defined by a Conformance resource) that a single system can take on -->
 
<!-- Roles are sets of functionality (generally defined by a Conformance resource) that a single system can take on -->
===Role 1 Name===
+
===Server===
 +
<!-- Provide a description of the capabilities this role will have within the connectathon -->
 +
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===
 +
<!-- Provide a description of the capabilities this role will have within the connectathon -->
 +
A client that creates appointments (as either booked resources, or requests which need a placer to fill)
 +
 
 +
===Placer===
 
<!-- Provide a description of the capabilities this role will have within the connectathon -->
 
<!-- Provide a description of the capabilities this role will have within the connectathon -->
 +
A placer is a client (or server) that processes appointment requests and allocates either participants, or times to these requests.
  
 
==Scenarios==
 
==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: [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]
 +
 +
Pre-requisites: none
 +
 
<!-- What will be the actions performed by participants? -->
 
<!-- What will be the actions performed by participants? -->
 +
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...
  
 
===Scenario Step 1 Name===
 
===Scenario Step 1 Name===

Revision as of 20:32, 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

Pre-requisites: none

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...

Scenario Step 1 Name

Action:
Precondition:
Success Criteria:
Bonus point:


TestScript(s)