201801 Provider Directory
Background for Service Provider Directory
If considering implementing more than a simple client, extensive pre-connectathon work is recommended.
Specification Page(s):
Organization Location Practitioner PractitionerRole EndPoint HealthcareService
Submitting WG/Project/Implementer Group
Patient Administration
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 track will test how FHIR can be used to standardize the exchange of services/provider directory data. Defining how healthcare organizations can participate in a federated healthcare directory will promote interoperability and innovation.
(And hopefully review the Provider Directory created by MiHN, and some mappings on the IHE HPD profile into FHIR)
Proposed Track Lead
(tentative) Coordinator: Brian Postlethwaite(sgtshultzpos)
Expected participants
Provider Directory:
- Telstra Health (HealthConnex)
- Epic
- Sequoia
- Touchstone (AEGIS)
Roles
Provider Directory
Service Provider Directory Server
A Server that has Service/Provider directory data in it (with associated schedule information)
Scenarios
1 Directory Search - Provider, Location, Organization
- Action: Perform a search for Provider Directory related resource.
- See Argonaut Provider Directory Connectathon for 1-6 (which have example queries there also)
- 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
We would also like to test to see if extracts can work using paging over an open search, or history can work in these scenarios.
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/Provider-Directory
