This wiki has undergone a migration to Confluence found Here

Difference between revisions of "201801 Scheduling"

From HL7Wiki
Jump to navigation Jump to search
(Added TestScripts section)
 
(7 intermediate revisions by one other user not shown)
Line 4: Line 4:
 
__NOTOC__
 
__NOTOC__
  
 +
Zulip Chat stream for this Track is [https://chat.fhir.org/#narrow/stream/argonaut here]  and issues can be posted  [https://github.com/argonautproject/scheduling/issues here]
  
 
===Background For Scheduling===
 
===Background For Scheduling===
  
This track is based upon [https://github.com/argonautproject/scheduling/wiki Argonaut Scheduling project] and the  '''[https://argonautproject.github.io/scheduling/ Argonaut Scheduling Implementation Guide CI Build]'''
+
This track is based upon [https://github.com/argonautproject/scheduling/wiki Argonaut Scheduling project] and the  '''[https://argonautproject.github.io/scheduling/ Argonaut Scheduling Implementation Guide CI Build]'''.  It is based upon the FHIR 3.0.1 Standard.
 
 
====This track will focus on these Use Cases:====
 
 
 
*'''Patient based Scheduling Use Cases'''
 
** Use Case 1: Patient Portal Scheduling for existing patients
 
** Use Case 2: Open Scheduling for new patient or existing patient
 
** Use Case 3 Prefetching Open Slots
 
* '''Provider based Scheduling Use Cases'''
 
** Use Case 4: Scheduling across systems
 
** Use Case 5: Scheduling for existing patient across systems
 
 
 
====... and specifically these transactions====
 
 
 
* Appointment Availability Search Operation
 
* Appointment booking Operation
 
* Search for booked Appointment
 
* Cancels or cancel/reschedules
 
* Prefetching and updating Slots
 
  
 
<!-- What will be the actions performed by participants? -->
 
<!-- What will be the actions performed by participants? -->
Line 48: Line 31:
 
<!-- 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 -->
  
Scheduling:
 
  
 
Servers:  
 
Servers:  
Line 145: Line 127:
 
<!-- What will be the actions performed by participants? -->
 
<!-- What will be the actions performed by participants? -->
  
See the  the Argonaut Scheduling Implementation Guide CI Build Use Cases:
+
See the Argonaut Scheduling Implementation Guide CI Build Use Cases:
 +
 
 +
* '''[https://argonautproject.github.io/scheduling/patient-scheduling.html Patient based Scheduling Use Cases]'''
 +
** Use Case 1: Patient Portal Scheduling for existing patients
 +
** Use Case 2: Open Scheduling for new patient or existing patient
 +
** Use Case 3 Prefetching Open Slots
 +
*  '''[https://argonautproject.github.io/scheduling/provider-scheduling.html Provider based Scheduling Use Cases]'''
 +
** Use Case 4: Scheduling across systems
 +
** Use Case 5: Scheduling for existing patient across systems
 +
 
 +
====... and specifically these transactions====
 +
 
 +
* Appointment Availability Search Operation
 +
* Appointment booking Operation
 +
* Search for booked Appointment
 +
* Cancels or cancel/reschedules
 +
* Prefetching and updating Slots
 +
 
 +
==TestScript(s)==
 +
<!-- Optional (for initial proposal): Provide links to the TestScript instance(s) that define the behavior to be tested. 
 +
These should be committed to SVN under trunk/connectathons/[connectathon]
 +
-->
 +
The supporting TestScripts and corresponding fixtures have been committed to the FHIR documents Github repository at: https://github.com/FHIR/documents/tree/master/connectathons/NewOrleansJan2018/Connectathon17/Scheduling
 +
 
 +
Please note that the available TestScripts test the [http://hl7.org/fhir/2018Jan/appointment.html#status-flow Typical (Work)flow of statuses] as described in the FHIR specification Schedule resource type page.
 +
 
 +
==Security and Privacy Considerations==
 +
<!-- Optional (for initial proposal): Address the topic of Privacy and Security.
 +
* What Authentication/Authorization will be used (e.g. SMART on FHIR (OAuth), HEART (UMA/OAuth), IHE IUA (OAuth), generic OAuth, generic SAML, mutual-Auth-TLS), or explicitly indicate that it is out of scope and left to implementations.
 +
* What Privacy Consent management will be used? When the Consent Resource is used, define how.
 +
* What Audit Logging will be used? When the AuditEvent Resource is used, define expectations of what events will be logged and what each AuditEvent will contain.
 +
* How will Provenance be used? Provenance use should be mandated when data is imported from other systems, so as to track that source of that data. Provenance should be used when data is authored by unusual sources, such as the Patient themselves or devices.
 +
* How will security-labels be used? Security-labels are meta tags used to classify the data into various confidentiality, sensitivity, and integrity classifications. These security-labels are then available for use and available for access control decisions.
 +
I am happy to help: JohnMoehrke@gmail.com -- security co-chair
 +
-->
 +
 
  
* [https://argonautproject.github.io/scheduling/patient-scheduling.html Patient based Scheduling Use Cases]
+
See the [https://argonautproject.github.io/scheduling/index.html#security Argonaut Scheduling Implementation Guide CI Build Use Cases Security and Assumptions sections]
* [https://argonautproject.github.io/scheduling/provider-scheduling.html Provider based Scheduling Use Cases]
 

Latest revision as of 21:18, 19 January 2018

Return to Jan 2018 Proposals


Zulip Chat stream for this Track is here and issues can be posted here

Background For Scheduling

This track is based upon Argonaut Scheduling project and the Argonaut Scheduling Implementation Guide CI Build. It is based upon the FHIR 3.0.1 Standard.


For additional background, review the Appointment resource especially the section on the "usual" workflow and a discussion on statuses, and what would be expected.

Submitting WG/Project/Implementer Group

The Argonaut Project

Justification

The Argonaut Scheduling Project is a vendor agnostic specification providing FHIR RESTful APIs and guidance for access to and booking of appointments for patients by both patient and practitioner end users. This specification is based on FHIR Version 3.0.1 and specifically the Scheduling and Appointment resources.

Proposed Track Lead

Eric Haas

Expected participants

Servers:

Name Use Case 1 Use Case 2 Use Case 3 Use Case 4 Use Case 5
Epic X X
Telstra Health (HealthConnex) X
HealthSamuri (tentative) X
Health eData Inc (facade) X


Clients:

Name Use Case 1 Use Case 2 Use Case 3 Use Case 4 Use Case 5
ShareCare
ZocDoc X
Health eData Inc (PostMan Test Client) X X X X X

Roles

Appointments

Provider or 3rd Party consumer application (Client)

An application that should be used by an end user (e.g., patient or practitioner) to search for information to support creating a referral, and can book an appointment on a client's behalf

FHIR Server (EHR)

A Server that that processes appointment availability booking 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. To somewhat limit the effort involved we have provided a simple set Argo Scheduling Sprint Test Data to get you started. The corresponding FHIR resources for the test data has been loaded on the Telstra FHIR test server and can be fetched using the FHIR API. They are also available as FHIR bundles in xml format.

Scenarios

See the Argonaut Scheduling Implementation Guide CI Build Use Cases:

... and specifically these transactions

  • Appointment Availability Search Operation
  • Appointment booking Operation
  • Search for booked Appointment
  • Cancels or cancel/reschedules
  • Prefetching and updating Slots

TestScript(s)

The supporting TestScripts and corresponding fixtures have been committed to the FHIR documents Github repository at: https://github.com/FHIR/documents/tree/master/connectathons/NewOrleansJan2018/Connectathon17/Scheduling

Please note that the available TestScripts test the Typical (Work)flow of statuses as described in the FHIR specification Schedule resource type page.

Security and Privacy Considerations

See the Argonaut Scheduling Implementation Guide CI Build Use Cases Security and Assumptions sections