This wiki has undergone a migration to Confluence found Here

Difference between revisions of "201609 Provider Directories and Scheduling"

From HL7Wiki
Jump to navigation Jump to search
Line 53: Line 53:
==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 -->
* Telstra Health (HealthConnex)
* SureScripts
* Epic

Revision as of 21:21, 15 June 2016

Background for Service Provider Directory

If considering implementing more than a simple client, extensive pre-connectathon work is recommended.

Specification Page(s):


And we are seeking some feeback on the new Directory Support resources:


Background For Scheduling

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(s):


The introduction section on the "usual" workflow can be found here:

If you're trying to work out what statuses mean, and what would be expected, there is a summary at the bottom of that same page including a collection of examples Which tie together the 4 resources...

Submitting WG/Project/Implementer Group

Patient Administration/Implementer Communities


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)

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

Coordinator: Brian Postlethwaite(sgtshultzpos) See Connectathon_Track_Lead_Responsibilities

Expected participants

  • Telstra Health (HealthConnex)
  • SureScripts
  • Epic


Please include information here regarding how much advance preparation will be required if creating a client and/or server.

Role 1 Name


Scenario Step 1 Name

Success Criteria:
Bonus point: