Difference between revisions of "201605 ServicesDirectoryAndScheduling Track"
(Created page with "{{subst::Template for FHIR Connectathon Track Proposals}}") |
|||
| Line 2: | Line 2: | ||
[[Category:201605_FHIR_Connectathon_Track_Proposals|May 2016 Proposals]] | [[Category:201605_FHIR_Connectathon_Track_Proposals|May 2016 Proposals]] | ||
__NOTOC__ | __NOTOC__ | ||
| − | = | + | =Services Directory and Scheduling= |
==Submitting WG/Project/Implementer Group== | ==Submitting WG/Project/Implementer Group== | ||
| Line 8: | Line 8: | ||
==Justification== | ==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== | ==Proposed Track Lead== | ||
| − | + | Brian Postlethwaite (sgtshultzpos) | |
| − | |||
==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 --> | ||
| + | * SureScripts | ||
| + | * Epic | ||
| + | * 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 --> | ||
| − | === | + | ===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== | ==Scenarios== | ||
<!-- What will be the actions performed by participants? --> | <!-- What will be the actions performed by participants? --> | ||
| − | ===Scenario | + | ===Scenario Directory Update=== |
| + | :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 --> | ||
| + | |||
| + | ===Scenario Directory Search=== | ||
| + | :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 Availability=== | ||
: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 32: | Line 63: | ||
<!-- Provide a description of each task --> | <!-- Provide a description of each task --> | ||
| + | |||
| + | ===Book 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 --> | ||
| + | |||
| + | ===Progress Appointment into an Encounter=== | ||
| + | :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 --> | ||
| + | |||
==TestScript(s)== | ==TestScript(s)== | ||
Revision as of 13:22, 10 February 2016
Services Directory and Scheduling
Submitting WG/Project/Implementer Group
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 Update
- Action:
- Precondition:
- Success Criteria:
- Bonus point:
Scenario Directory Search
- 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:
