1. Validated Healthcare Directory Connect-A-Thon
Introduction
Daniel Chaput, Office of the National Coordinator for Health IT
Sandra Vance, Aegis.net, Inc.

2. Code-a-thon Logistics
Agenda
Code-a-thon Logistics
Objectives
How to join
Servers
Introductions
Background
Healthcare Directory
Validated Healthcare Directory Standard
Scenarios
Questions and Answers

3. Code-A-Thon Logistics: How to Participate
Messaging: Zullip
To sign up for an account go to: chat.fhir.org
Stream: VHDir - Validated Healthcare Directory
Test Server

4. Background: Healthcare Directory Activities
April 2016: ONC and the Federal Health Architecture (FHA) jointly hosted a Provider Directory Workshop convening public and private stakeholders
Review challenges, share successes, and generate new ideas around provider directory standards and solutions. It was agreed that data quality is a persistent challenge across the industry.
July 2016: ONC and FHA launched a new healthcare directory effort in July The project goals were to:
Define the architecture of a proposed national resource of validated healthcare directory data
Develop an HL7 Fast Healthcare Interoperability Resources (FHIR) Based Implementation Guide describing the exchange of information between a national resource of validated healthcare directory data and local environments (e.g. provider organizations, payers, HIEs)
To address concerns about data quality, reduce administrative burden, and improve consumer satisfaction
ONC/FHA’s Healthcare Directory effort is comprised of the Technology Learning Community (TLC) and four tiger teams.

5. Background: Healthcare Directory Activities (cont’d)
The proposed national resource would include a broad set of provider data that supports a variety of healthcare directory use cases.
Data would be validated against primary sources (e.g. state licensing boards for licensure information) and available to local environments through a national exchange standard.
Providers would only have to attest to much of their information once for the national resource, rather than for each local environment.

6. Background: The Validated Healthcare Directory
Since early 2018, The Office of the National Coordinator for Health Information Technology (ONC) and the Federal Health Architecture (FHA) in collaboration with public and private stakeholders have been defining a standard to exchange data from a Validated Healthcare Directory.
This standard is designed to support the sharing of directory information for individuals and organizations across the healthcare spectrum in order to support interoperability.
It describes the architectural considerations for attesting to, validating, and exchanging data from a central source of validated provider data (i.e. a Validated Healthcare Directory or VHDir), as well as a RESTful FHIR API for accessing data from a VHDir.
The balloted standard can be found at:

7. VHDir - Conceptual Diagram - Draft
Validated Health Care Directory (VHDir)
Attested Information
Primary Source
Primary Source
FHIR
Primary Sources
Attester
Initial Validation
FHI
Core Data
Healthcare Directory
Recurring Validation
FHIR
Local Workflow Environment(1)
Local Workflow Environment(2)
HDir(2)
HDir(1)
Exchange Processes
FHIR
FHIR

8. Code-A-Thon Logistics: Objectives
This virtual Connect-A- Thon seeks to:
Test basic access to a directory based on the VHDir IG,
whether a FHIR server can appropriately represent the information and
whether local systems can access and use the information
Inform planning for future Connect-a-thons in terms of the scope of data, scenarios and use cases, and features such as bulk data access.
Target: Host an in-person Connect-A-Thon at the January HL7 conference in San Antonio
Access Directory information that meets the needs of local use cases, establishing that the server side can represent the information and the ability of local systems across the spectrum of potential local stakeholders to consume the information retrieved.

9. Code-A-Thon Logistics: Use Cases
Scenario 1: Local Data Validation - A Local Workflow Environment needs to verify details on a known individual prior as part of a local use case.
Scenario 2: Request data on a set of practitioners  - A Local Workflow Environment needs to data on a set of practitioners as defined by jurisdictional boundaries, in this case a state.
Scenario 3: Request data on an individual  organization - A Local Workflow Environment needs current data on an individual organization including all locations, and services.
Scenario 4: Request Data on Organizations - A Local Workflow Environment needs current data on an individual organization’s affiliations; including all locations and the services delivered at those locations.

10. Code-A-Thon Logistics: Use Cases (continued)
Scenario 5: Request Organization data for a specific Provider - A Local Workflow environment needs updated information for a specific provider and all organizations the provider is affiliated with.
Scenario 6: Identify data associated with a Network - A Local Workflow needs available data from a Healthcare Directory concerning a Network, including all services, locations, practitioners, and organizations.