This wiki has undergone a migration to Confluence found Here

Difference between revisions of "201605 ServicesDirectoryAndScheduling Track"

From HL7Wiki
Jump to navigation Jump to search
Line 41: Line 41:
 
<!-- What will be the actions performed by participants? -->
 
<!-- What will be the actions performed by participants? -->
  
===Scenario Directory Update===
+
===Scenario Directory Search===
:Action: <!--Who does what?  (Use the role names listed above when referring to the participants -->
+
:Action: Perform a search for either Practitioner or HealthsareService resources
:Precondition: <!-- What setup is required prior to executing this step? -->
+
:Precondition: Directory FHIR Resources should already be on a FHIR server to query
:Success Criteria: <!-- How will the participants know if the test was successful? -->
+
:Success Criteria: The desired resources were found
:Bonus point: <!-- Any additional complexity to make the scenario more challenging -->
+
:Bonus point: The criteria for the resources used several restrictions, possibly Specialty or Location
  
 
<!-- Provide a description of each task -->
 
<!-- Provide a description of each task -->
  
===Scenario Directory Search===
+
===Scenario Directory Update===
 
: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? -->
Line 80: Line 80:
  
 
<!-- Provide a description of each task -->
 
<!-- Provide a description of each task -->
 
  
 
==TestScript(s)==
 
==TestScript(s)==

Revision as of 13:27, 10 February 2016


Services Directory and Scheduling

Submitting WG/Project/Implementer Group

Patient Administration/Implementer Communities

Justification

A key challenge of healthcare is knowing about the resources available in the local, regional, and global healthcare networks. When a patient's care is transitioned from one setting to another, it's critical to know about the doctors, hospitals and clinics available to receive that patient. When a patient is travelling, it improves care when local healthcare facilities can retrieve the patient's up to date medical history from a primary care provider. There are currently no widely adopted standards for exchanging this directory information. Currently, healthcare organizations use a variety of labor intensive processes to gather, normalize, de-duplicate and consume this data. They share custom flat files, scrape web pages, or pay 3rd parties to curate their practitioner data. Organizational data is often isolated in different networks and aren't easily shared. This project will define how FHIR will be used to standardize the exchange of provider directory data. Defining how healthcare organizations can participate in a federated healthcare directory will promote interoperability and innovation. This directory structure can later be extended to support other workflows like electronic scheduling, advanced case management, and automated insurance eligibility checks.

This track will also lead into the creation of Appointments based on schedules found associated with the above services/providers, and also verify the workflow of proceeding from a booked appointment into the creation of the Encounter.

Proposed Track Lead

Brian Postlethwaite (sgtshultzpos)

Expected participants

  • SureScripts
  • Epic
  • HealthConnex

Roles

Service Directory Server

A Server that has Service/Provider directory data in it (with associated schedule information)

Patient Consumer application

An application that should be used by a client to search for where services could be provided, and can book an appointment

Provider Consumer application

An application that should be used by a provider to search for information to support creating a referral, and can book an appointment on a client's behalf


Scenarios

Scenario Directory Search

Action: Perform a search for either Practitioner or HealthsareService resources
Precondition: Directory FHIR Resources should already be on a FHIR server to query
Success Criteria: The desired resources were found
Bonus point: The criteria for the resources used several restrictions, possibly Specialty or Location


Scenario Directory Update

Action:
Precondition:
Success Criteria:
Bonus point:


Check Availability

Action:
Precondition:
Success Criteria:
Bonus point:


Book Appointment

Action:
Precondition:
Success Criteria:
Bonus point:


Progress Appointment into an Encounter

Action:
Precondition:
Success Criteria:
Bonus point:


TestScript(s)