NATIONWIDE HEALTH INFORMATION NETWORK GOVERNANCE Doug Fridsma Director, Office of Interoperability and Standards.

Slides:

Advertisements

Similar presentations

National HIT Agenda and HIE John W. Loonsk, M.D. Director of Interoperability and Standards Office of the National Coordinator Department of Health.

Advertisements

| Implications for Health Information Exchange – MetroChicago January 2011.

Standards & Interoperability Kickoff HHS – ONC September 20, 2010 Office of Standards and Interoperability 1.

Interoperability Roadmap Comments Package Implementation, Certification, and Testing (ICT) Workgroup February 13, 2015 Liz Johnson, co-chair Cris Ross,

Nick Vennaro, NHIN Team (Contractor), Office of the National Coordinator for Health IT Michael Torppey, CONNECT Health IT Security Specialist (Contractor)

Timeline & Milestones: Certification & Standards NPRM Stage 2 Health IT Standards Committee, March 29, 2011 Doug Fridsma, MD, PhD Director Office of Interoperability.

S&I Framework Provider Directories Initiative esMD Work Group October 19, 2011.

SaMoLo in Government Open Source Projects Lessons from the CONNECT project.

1 HIT STANDARDS COMMITTEE DRAFT: S&I Framework Principles and Processes 1.

Overview of Longitudinal Coordination of Care (LCC) Presentation to HIT Steering Committee May 24, 2012.

1 Overview of Other Global Networks Exchange Network User Group Meeting April 2006.

Interoperability Framework Overview March 24, 2010 Presented by: Douglas Fridsma, MD, PhD Acting Director, Office of Interoperability & Standards ONC HIT.

Connecting Health and Care for the Nation: A Shared Nationwide Interoperability Roadmap – DRAFT Version 1.0 Joint FACA Meeting Chartese February 10, 2015.

S&I Framework Doug Fridsma, MD, PhD Director, Office of Standards and Interoperability, ONC Fall 2011 Face-to-Face.

1 Joyce Sensmeier MS, RN, FHIMSS, HIMSS Glen Marshall, Siemens Healthcare Charles Parisot, GE Healthcare IHE's contribution to standards harmonization.

Georgia Department of Community Health Georgia Health Information Exchange Network HomeTown Health Event September 25, 2012.

Introduction to Standard 2: Partnering with consumers Advice Centre Network Meeting Nicola Dunbar October 2012.

Riki Merrick, APHL Anna Orlova, PhD, PHDSC Lise Stevens, FDA Nikolay Lipskiy, MD, DrPH, MBA – CDC CSTE Conference June 5 th, 2012 The findings and conclusions.

Query Health Business Working Group Kick-Off September 8, 2011.

Achieving Interoperability Doug Fridsma, MD, PhD, FACMI Director, Office of Standards & Interoperability, ONC 1.

Nedra Garrett Director, Division of Informatics Practice, Policy, and Coordination (DIPPC) PHIN Partner Call April 20, 2011 Public Health Information Network.

1 Federal Health IT Ontology Project (HITOP) Group The Vision Toward Testing Ontology Tools in High Priority Health IT Applications October 5, 2005.

S&I Framework Architecture Refinement & Management (ARM) 01/07/2013.

1 NHIN Direct + Interoperability Framework = Focused Collaboration Bottom up use case development within a top-down coordination framework CORE PRINCIPLES.

EHR System (EHR-S) Functional Requirements Implementation Guide: Laboratory Results Interface (LRI) Kickoff March 3 rd,

TUESDAY, 4:00 – 4:20PM WEDNESDAY, 4:00 – 4:20PM Douglas Hill, NHIN Implementation Lead (Contractor), Office of the National Coordinator for Health IT Vanessa.

Public Health Reporting Initiative: Stage 2 Draft Roadmap.

SIM- Data Infrastructure Subcommittee November 14, 2013.

Data Gathering HITPC Workplan HITPC Request for Comments HITSC Committee Recommendations gathered by ONC HITSC Workgroup Chairs ONC Meaningful Use Stage.

Longitudinal Coordination of Care WG Roadmap Discussion 1.

1561 INITIATIVE Lessons Learned and Future Considerations

Standards & Interoperability Framework Overview Doug Fridsma, MD, PhD Director, Office of Interoperability & Standards ONC IHE North American Connectathon.

CONNECT Roadmap Draft version as of February 4 th,

ONCHIT – 3 NHIN Prototype and other Initiatives for Kentucky Kentucky e-Health Network Claudine Beron February 21, 2006.

State HIE Program Chris Muir Program Manager for Western/Mid-western States.

Interoperability Framework Overview Health Information Technology (HIT) Standards Committee June 24, 2010 Presented by: Douglas Fridsma, MD, PhD Acting.

HIT Policy Committee NHIN Workgroup Recommendations Phase 2 David Lansky, Chair Pacific Business Group on Health Danny Weitzner, Co-Chair Department of.

Direct Project Update Arien Malec. First Production Usage Immunization data from Hennepin County Medical Center to Minnesota Department of Health via.

PD Provider Directories Initiative Overview PD January 20, 2012.

Enterprise Architecture, Enterprise Data Management, and Data Standardization Efforts at the U.S. Department of Education May 2006 Joe Rose, Chief Architect.

Public Health Data Standards Consortium

S&I Integration with NIEM (DRAFT) Standards Development Support June 8, 2011.

S&I Provider Directories Initiative Revisions to Initiative Charter July 1, 2011.

Health eDecisions Use Case 2: CDS Guidance Service Strawman of Core Concepts Use Case 2 1.

S&I PUBLIC HEALTH REPORTING INITIATIVE: DEVELOPING OF A TEAMING APPROACH S&I Public Health Reporting Initiative Nikolay Lipskiy, MD, DrPH, Co-Lead September,

Federal Advisory Committees Introducing Future Topics and Adding Workgroups Discussion Document October 2009 ** Pre-decisional Draft Do not Disclose **

Standards and Interoperability Framework Primer of S&I Phases, Procedures, and Functions.

HIT Standards Committee Overview and Progress Report March 17, 2010.

Health Information Exchange Roadmap: The Landscape and a Path Forward Primary and Behavioral Health Care Integration Program Grantee.

Mariann Yeager, NHIN Policy and Governance Lead (Contractor) Office of the National Coordinator for Health IT David Riley, CONNECT Lead (Contractor) Federal.

Health TechNet Presented by: Suniti Ponkshe October 8, 2010.

HIT Policy Committee NHIN Workgroup HIE Trust Framework: HIE Trust Framework: Essential Components for Trust April 21, 2010 David Lansky, Chair Farzad.

Health Management Information Systems Unit 3 Electronic Health Records Component 6/Unit31 Health IT Workforce Curriculum Version 1.0/Fall 2010.

Discussion - HITSC / HITPC Joint Meeting Transport & Security Standards Workgroup October 22, 2014.

Creating an Interoperable Learning Health System for a Healthy Nation Jon White, M.D. Acting Deputy National Coordinator Office of the National Coordinator.

HIT Policy Committee Meeting Nationwide Health Information Network Governance June 25, 2010 Mary Jo Deering, PhD ONC, Office of Policy and Planning NHIN.

S&I FRAMEWORK PROPOSED INITIATIVE SUMMARIES Dr. Douglas Fridsma Office of Interoperability and Standards December 10, 2010.

Lab Results Interfaces S&I Framework Initiative Bi-Weekly Initiative Meeting August 29, 2011.

Proposed S&I Public Health Reporting Initiative 1 Challenge -There is a lack of harmonized activities to enable electronic data exchange between clinical.

Data Gathering HITPC Workplan HITPC Request for Comments HITSC Committee Recommendations gathered by ONC HITSC Workgroup Chairs ONC Meaningful Use Stage.

Lab Results Interface Validation Suite Workgroup and Pilots Workgroup Vision, Charter, NIST Collaboration, July 8,

Health IT Standards Committee Update December 19, 2012 Doug Fridsma, MD, PhD, FACP, FACMI Chief Science Officer & Director, Office of Science & Technology.

Standards and Interoperability Framework esMD Primer of S&I Phases, Procedures, and Functions S&I F2F Thursday, April 12 th, :00 AM.

September, 2005What IHE Delivers 1 Joyce Sensmeier, MS, RN, BC, CPHIMS, FHIMSS Vice President, Informatics, HIMSS Charles Parisot, GE Healthcare IT infrastructure.

Establish the NIEM Health Domain by focusing on high value data exchanges that can be modeled within NIEM in the context of the existing NIEM framework.

Electronic Case Reporting Update

Standards and the National HIT Agenda John W. Loonsk, MD

Health IT Policy Committee Workgroup Evolution

Model Contract for Health

Biosurveillance and the National Health IT Agenda

Presentation transcript:

NATIONWIDE HEALTH INFORMATION NETWORK GOVERNANCE Doug Fridsma Director, Office of Interoperability and Standards

S&I Framework coordination Tools and Services (Use Case Development, Harmonization Tools, Vocabulary Browser, Value Set Repository, Testing Scripts, etc) (Stanley) Tools and Services (Use Case Development, Harmonization Tools, Vocabulary Browser, Value Set Repository, Testing Scripts, etc) (Stanley) Use Case Development and Functional Requirements (Accenture) Use Case Development and Functional Requirements (Accenture) Standards Development (TBD) Standards Development (TBD) Certification and Testing (Stanley/Deloitte) Certification and Testing (Stanley/Deloitte) Harmonization of Core Concepts (Deloitte) Harmonization of Core Concepts (Deloitte) Implementation Specifications (Deloitte) Implementation Specifications (Deloitte) Pilot Demonstration Projects (Lockheed Martin) Pilot Demonstration Projects (Lockheed Martin) Reference Implementation (Lockheed Martin) Reference Implementation (Lockheed Martin) Subject matter experts, priorities setting Stds, operational and technical coordination Versioning, code and dev. coordination Certification criteria, testing NHIN Exchange, other pilot projects

S&I Framework coordination Tools and Services (Use Case Development, Harmonization Tools, Vocabulary Browser, Value Set Repository, Testing Scripts, etc) (Stanley) Tools and Services (Use Case Development, Harmonization Tools, Vocabulary Browser, Value Set Repository, Testing Scripts, etc) (Stanley) Use Case Development and Functional Requirements (Accenture) Use Case Development and Functional Requirements (Accenture) Standards Development (TBD) Standards Development (TBD) Certification and Testing (Stanley/Deloitte) Certification and Testing (Stanley/Deloitte) Harmonization of Core Concepts (Deloitte) Harmonization of Core Concepts (Deloitte) Implementation Specifications (Deloitte) Implementation Specifications (Deloitte) Pilot Demonstration Projects (Lockheed Martin) Pilot Demonstration Projects (Lockheed Martin) Reference Implementation (Lockheed Martin) Reference Implementation (Lockheed Martin) Subject matter experts, priorities setting

Use Case Development and Coordination »Organizing Principles Bottom-up, driven by use cases and need (think NHIN Direct) “use case steward” Focused on stakeholders Inclusive of all stakeholders »Stakeholders Federal advisory committees (HITPC, HITSC) Meaningful use requirements VLER pilots Federal partners Patients, privacy, security experts

Prioritization and Backlog Lists 12/8/2015

S&I Framework coordination Tools and Services (Use Case Development, Harmonization Tools, Vocabulary Browser, Value Set Repository, Testing Scripts, etc) (Stanley) Tools and Services (Use Case Development, Harmonization Tools, Vocabulary Browser, Value Set Repository, Testing Scripts, etc) (Stanley) Use Case Development and Functional Requirements (Accenture) Use Case Development and Functional Requirements (Accenture) Standards Development (TBD) Standards Development (TBD) Certification and Testing (Stanley/Deloitte) Certification and Testing (Stanley/Deloitte) Harmonization of Core Concepts (Deloitte) Harmonization of Core Concepts (Deloitte) Implementation Specifications (Deloitte) Implementation Specifications (Deloitte) Pilot Demonstration Projects (Lockheed Martin) Pilot Demonstration Projects (Lockheed Martin) Reference Implementation (Lockheed Martin) Reference Implementation (Lockheed Martin) Stds, operational and technical coordination

Prioritization and Backlog Lists 12/8/2015 Strategic Priorities Strategic Priorities Operational Priorities “Day to Day” Priorities within each functional team

S& I Overview of Roles and Controls 12/8/2015 Core artifacts are versioned and controlled Artifacts are “packaged” and released Each artifacts has a responsible role Artifacts and releases have prioritization and approval points, or “controls”

S&I Framework coordination Tools and Services (Use Case Development, Harmonization Tools, Vocabulary Browser, Value Set Repository, Testing Scripts, etc) (Stanley) Tools and Services (Use Case Development, Harmonization Tools, Vocabulary Browser, Value Set Repository, Testing Scripts, etc) (Stanley) Use Case Development and Functional Requirements (Accenture) Use Case Development and Functional Requirements (Accenture) Standards Development (TBD) Standards Development (TBD) Certification and Testing (Stanley/Deloitte) Certification and Testing (Stanley/Deloitte) Harmonization of Core Concepts (Deloitte) Harmonization of Core Concepts (Deloitte) Implementation Specifications (Deloitte) Implementation Specifications (Deloitte) Pilot Demonstration Projects (Lockheed Martin) Pilot Demonstration Projects (Lockheed Martin) Reference Implementation (Lockheed Martin) Reference Implementation (Lockheed Martin) Versioning, code and dev. coordination

Versioning and Development Coordination »Principles Leverage knowledge of open-source communities Support rapid, iterative and open development Coordination with both the use-case teams and the certification and testing teams »Highly operational coordination, using software development tools

S&I Framework coordination Tools and Services (Use Case Development, Harmonization Tools, Vocabulary Browser, Value Set Repository, Testing Scripts, etc) (Stanley) Tools and Services (Use Case Development, Harmonization Tools, Vocabulary Browser, Value Set Repository, Testing Scripts, etc) (Stanley) Use Case Development and Functional Requirements (Accenture) Use Case Development and Functional Requirements (Accenture) Standards Development (TBD) Standards Development (TBD) Certification and Testing (Stanley/Deloitte) Certification and Testing (Stanley/Deloitte) Harmonization of Core Concepts (Deloitte) Harmonization of Core Concepts (Deloitte) Implementation Specifications (Deloitte) Implementation Specifications (Deloitte) Pilot Demonstration Projects (Lockheed Martin) Pilot Demonstration Projects (Lockheed Martin) Reference Implementation (Lockheed Martin) Reference Implementation (Lockheed Martin) Certification criteria, testing

S&I Framework coordination Tools and Services (Use Case Development, Harmonization Tools, Vocabulary Browser, Value Set Repository, Testing Scripts, etc) (Stanley) Tools and Services (Use Case Development, Harmonization Tools, Vocabulary Browser, Value Set Repository, Testing Scripts, etc) (Stanley) Use Case Development and Functional Requirements (Accenture) Use Case Development and Functional Requirements (Accenture) Standards Development (TBD) Standards Development (TBD) Certification and Testing (Stanley/Deloitte) Certification and Testing (Stanley/Deloitte) Harmonization of Core Concepts (Deloitte) Harmonization of Core Concepts (Deloitte) Implementation Specifications (Deloitte) Implementation Specifications (Deloitte) Pilot Demonstration Projects (Lockheed Martin) Pilot Demonstration Projects (Lockheed Martin) Reference Implementation (Lockheed Martin) Reference Implementation (Lockheed Martin) NHIN Exchange, other pilot projects

Nationwide Health Information Network »Onboarding requires Conformance testing against standards specifications –Product level conformance for CONNECT (like EHR certification) –Addition conformance testing against specific standards used in the Nationwide Health Information Network (constrained C32, etc) –Certification of “HISPs” may provide coordination mechanism Interoperability testing –“Scripts” about how exchange occurs (send, acknowledge, response) –More challenging that conformance testing, but automatic testing can help Agreement to operate in a particular way –DURSA defines some of the behaviors expected (ie, breach notification, etc) –Uses contracting mechanism for enforcement

S&I Framework coordination Tools and Services (Use Case Development, Harmonization Tools, Vocabulary Browser, Value Set Repository, Testing Scripts, etc) (Stanley) Tools and Services (Use Case Development, Harmonization Tools, Vocabulary Browser, Value Set Repository, Testing Scripts, etc) (Stanley) Use Case Development and Functional Requirements (Accenture) Use Case Development and Functional Requirements (Accenture) Standards Development (TBD) Standards Development (TBD) Certification and Testing (Stanley/Deloitte) Certification and Testing (Stanley/Deloitte) Harmonization of Core Concepts (Deloitte) Harmonization of Core Concepts (Deloitte) Implementation Specifications (Deloitte) Implementation Specifications (Deloitte) Pilot Demonstration Projects (Lockheed Martin) Pilot Demonstration Projects (Lockheed Martin) Reference Implementation (Lockheed Martin) Reference Implementation (Lockheed Martin)

The goal of the S&I Framework 15 LowHigh Low High Focused Collaboration A Thousand Flowers Bloom Command and Control Participation Classic Trade-Off Focus »Consensus Driven Process »Open Collaboration »Established core guiding principles »Driven by business needs and elaborated use cases »Real world pilot implementation »Establish coordination mechanisms across the entire spectrum of the S&I Framework

Final Thoughts »Coordination is not one-size-fits all »Different parts of the S&I framework require different coordination mechanisms Not all aspects of the S&I framework require formal governance established through rule-making. Need to maintain flexibility for those things that require rapid response to changing needs. –Strategic priorities –Certification to standards and implementation specification –Operational coordination for harmonization, code and versioning control –Approval of implementation specifications for specific purposes