Validated Healthcare Directory Connect-A-Thon

Slides:



Advertisements
Similar presentations
Microsoft ® System Center Configuration Manager 2007 R3 and Forefront ® Endpoint Protection Infrastructure Planning and Design Published: October 2008.
Advertisements

Open Interconnect Consortium Introduction for oneM2M
Electronic Submission of Medical Documentation (esMD) for Medicare FFS Presentation to HITSC Provenance Workgroup January 16, 2015.
Systems Engineering in a System of Systems Context
Introduction and Overview “the grid” – a proposed distributed computing infrastructure for advanced science and engineering. Purpose: grid concept is motivated.
Note: This is a preliminary discussion
Data Gathering HITPC Workplan HITPC Request for Comments HITSC Committee Recommendations gathered by ONC HITSC Workgroup Chairs ONC Meaningful Use Stage.
Topical Interest Groups as Communities of Practice: Strategies for Building a Community of Practice Facilitated by: PK12 Educational Evaluation TIG Evaluation.
2009 Indiana Election Administrator’s Conference Statewide Voter Registration System (SVRS) Project Update December 2,
FHIM Overview How the FHIM can organize other information modeling efforts.
Cross Domain Patient Identity Management Eric Heflin Dir of Standards and Interoperability/Medicity.
OSIAM4HE Proposed org structure Authored by the strategy and organization team.
Public Health Tiger Team we will start the meeting 3 min after the hour DRAFT Project Charter May 6, 2014.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
1 Collaboration and Concept Exploration Nationwide Health Information Organization (NHIO) Gateway March 28, 2007.
CONNECT Roadmap Draft version as of February 4 th,
Arizona SIM Strategy. SIM Overview CMS established State Innovation Model (SIM) Initiative for multi-payer efforts around payment reform and health system.
EHR-S Functional Requirements IG: Lab Results Interface Laboratory Initiative.
Lab Results Interfaces S&I Framework Initiative Bi-Weekly Initiative Meeting August 15, 2011.
Public Health Tiger Team we will start the meeting 3 min after the hour DRAFT Project Charter April 15, 2014.
Getting it Right for Every Learner in Renfrewshire: A Partnership Approach for Additional Support Needs (Draft Revised Renfrewshire ASL Act Implementation.
A case study: How Sitefinity triggered our business transformation from idea to execution.
Health Delivery Services May 29, Eastern Massachusetts Healthcare Initiative Policy Work Group Session 2 May 29, 2009.
Data Provenance Community Meeting May 15 th, 2014.
Data Access Framework All Hands Community Meeting 1 November 18, 2015.
Discussion - HITSC / HITPC Joint Meeting Transport & Security Standards Workgroup October 22, 2014.
Electronic Clinical Quality Measures – Session #1 ONC Resource Center.
Work Related to Senate Bill 2202 (effective January 1, 2001)
Welcome ONC/IWG/IHE-USA/eHEX HPD Providers Directory Task Group Vendor/Industry Feedback Discussion November 22, 2013.
Longitudinal Coordination of Care (LCC) Workgroup (WG) LTPAC SWG Meeting March 11,
Ian Bird Overview Board; CERN, 8 th March 2013 March 6, 2013
“ Jericho / UT Austin Pilot” Privacy with Dynamic Patient Review April 30, 2013 Presented by: David Staggs, JD, CISSP Jericho Systems Corporation.
1 An Overview of Process and Procedures for Health IT Collaboration GSA Office of Citizen Services and Communications Intergovernmental Solutions Division.
Lab Results Interface Validation Suite Workgroup and Pilots Workgroup Vision, Charter, NIST Collaboration, July 8,
Exercising, Maintaining and Reviewing BCM Arrangements ERMAN TASKIN
Information Sharing for Integrated Care A 5 Step Blueprint.
ISO Datatypes Approved by Enterprise Composite Architecture team (eCAT) on July 7, 2009 Guidelines for use for CBIIT funded projects.
Longitudinal Coordination of Care LCP SWG Thursday, April 25, 2013.
Data Access Framework All Hands Community Meeting 1 March 23, 2016.
Data Provenance Tiger Team April 28 th, 2014 Johnathan Coleman Johnathan Coleman - Initiative Coordinator Bob Yencha Bob Yencha – Subject Matter Expert.
Next Generation PDF and the PDF Association
NCQA’s Approach to the New Quality Measurement Landscape
Laboratory Orders Interface Initiative
Ontario Early Years Child and Family Centres Planning Guidelines
Structured Data Capture (SDC)
Care Coordination and Interoperable Health IT Systems
Creation of a National Health Provider Directory
Workshop Discussion on Day-2
EE Third-Party Solicitation Process Workshop Solicitation Alignment
Electronic Case Reporting Update
IHE Eye Care Process and Timeline
“Next Generation of Connected Health”
Arizona Health-e Connection Leadership from Governor Napolitano
Saturday, January 27 & Sunday, January 28
FHIR BULK DATA API April 2018
ONC P2 FHIR Ecosystem Task Force
Structured Data Capture (SDC)
Clinician-on- Stephen Chu September 2016.
Care Management & Planning track
IFX Forum Overview September 28, 2015 © Copyright IFX Forum, Inc
“Improving physical and mental health outcomes for adults living with severe and chronic mental health in Lismore through the integration of acute, primary.
HL7 FHIR Connectathon Care Planning & Management Track
Touchstone Testing Platform
eLearning Initiative: Introduction to HL7
Kuali Research Organizational Change Management
[2011 Texas Emergency Management Conference]
Jeanie Moore Director, (Acting) Office of External Affairs
James Shaw-Cotterill – STP
US Core Data for Interoperability (USCDI): Data Provenance IG
CMS NPRM for Payer Data Exchange – to Member
Presentation transcript:

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

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

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 http://vhdir-demo.fhir.org

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 2016. 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.

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.

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: http://hl7.org/fhir/uv/vhdir/2018Sep/index.html

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

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.

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.

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.