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

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

Standards & Interoperability Kickoff HHS – ONC September 20, 2010 Office of Standards and Interoperability 1.
Quality Measures Vendor Tiger Team December 13, 2013.
ELTSS Alignment to Nationwide Interoperability Roadmap DRAFT: For Stakeholder Consideration in response to public comment.
Quality Label and Certification Processes Vienna Summit 11 April 2014 Karima Bourquard Director of Interoperability IHE-Europe.
Nick Vennaro, NHIN Team (Contractor), Office of the National Coordinator for Health IT Michael Torppey, CONNECT Health IT Security Specialist (Contractor)
Building the Digital Infrastructure for Vermont’s Learning Health System ONC HIT Policy Committee Testimony September 14, 2011 Hunt Blair, Deputy Commissioner.
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.
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.
S&I Data Provenance Initiative Presentation to the HITSC on Data Provenance September 10, 2014.
Consumer Work Group Presentation Federal Health IT Strategic Plan January 9, 2015 Gretchen Wyatt Office of Planning, Evaluation, and Analysis.
S&I Framework Doug Fridsma, MD, PhD Director, Office of Standards and Interoperability, ONC Fall 2011 Face-to-Face.
EsMD Harmonization WG Meeting Wednesday, June 13 th, 2012.
1 Joyce Sensmeier MS, RN, FHIMSS, HIMSS Glen Marshall, Siemens Healthcare Charles Parisot, GE Healthcare IHE's contribution to standards harmonization.
LEVERAGING THE ENTERPRISE INFORMATION ENVIRONMENT Louise Edmonds Senior Manager Information Management ACT Health.
August 12, Meaningful Use *** UDOH Informatics Brown Bag Robert T Rolfs, MD, MPH.
Electronic Submission of Medical Documentation (esMD) Face to Face Informational Session Charter Discussion – 9:30am – 10:00am October 18, 2011.
Query Health Business Working Group Kick-Off September 8, 2011.
Arlington, VA January 5, 2006 Evaluation of Standards Harmonization Process for HIT Project Overview HITSP 05 N 42 December 29, 2005.
1 Federal Health IT Ontology Project (HITOP) Group The Vision Toward Testing Ontology Tools in High Priority Health IT Applications October 5, 2005.
HITSC Workplan: April Update April 17, 2013 Doug Fridsma, MD, PhD, FACP, FACMI Chief Science Officer & Director, Office of Science & Technology.
HIT Policy Committee Nationwide Health Information Network Governance Workgroup Recommendations Accepted by the HITPC on 12/13/10 Nationwide Health Information.
Interoperability Updates -National Interoperability Roadmap 8/20/2014 Erica Galvez, ONC Interoperability Portfolio Manager.
S&I Framework Architecture Refinement & Management (ARM) 01/07/2013.
Public Health Informatics and Technology Program Office Office of Surveillance, Epidemiology, and Laboratory Services Public Health and Meaningful Use.
NIEM Domain Awareness June 2011 Establishing a Domain within NIEM.
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,
Draft – discussion only Content Standards WG (Documents and Data) Proposed HITSC Workgroup Evolution 1 Architecture, Services & APIs WG Transport and Security.
Data Gathering HITPC Workplan HITPC Request for Comments HITSC Committee Recommendations gathered by ONC HITSC Workgroup Chairs ONC Meaningful Use Stage.
Data Intermediaries and Meaningful Use: Quality Measure Innovation, Calculation and Reporting Recommendations from Data Intermediary Tiger Team.
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.
What is NIEM? 1 NIEM is a national program supported by the federal government to increase information sharing between organizations who share a common.
State HIE Program Chris Muir Program Manager for Western/Mid-western States.
HIT Policy Committee NHIN Workgroup Recommendations Phase 2 David Lansky, Chair Pacific Business Group on Health Danny Weitzner, Co-Chair Department of.
Health Domain Value Proposition Briefing. health SCOPE Support information sharing and promote interoperability between healthcare organizations including.
Public Health Tiger Team we will start the meeting 3 min after the hour DRAFT Project Charter April 15, 2014.
10/27/111 Longitudinal Care Work Group (LCWG) Proposal to Re-Scope and Re-Name the LTPAC WG.
Enterprise Architecture, Enterprise Data Management, and Data Standardization Efforts at the U.S. Department of Education May 2006 Joe Rose, Chief Architect.
0 Connectathon 2009 Registration Bob Yencha Webinar | August 28, 2008 enabling healthcare interoperability.
Public Health Data Standards Consortium
S&I Integration with NIEM (DRAFT) Standards Development Support June 8, 2011.
ONC’s Proposed Strategy on Governance for the Nationwide Health Information Network Following Public Comments on RFI HIT Standards Committee Meeting September.
S&I PUBLIC HEALTH REPORTING INITIATIVE: DEVELOPING OF A TEAMING APPROACH S&I Public Health Reporting Initiative Nikolay Lipskiy, MD, DrPH, Co-Lead September,
Standards and Interoperability Framework Primer of S&I Phases, Procedures, and Functions.
HIT Standards Committee Overview and Progress Report March 17, 2010.
NATIONWIDE HEALTH INFORMATION NETWORK GOVERNANCE Doug Fridsma Director, Office of Interoperability and Standards.
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.
S&I Public Health Education Series: Data Provenance July 9th, 2014 Johnathan Coleman Initiative Coordinator – Data Provenance ONC/OCPO/OST (CTR)
Discussion - HITSC / HITPC Joint Meeting Transport & Security Standards Workgroup October 22, 2014.
S&I FRAMEWORK PROPOSED INITIATIVE SUMMARIES Dr. Douglas Fridsma Office of Interoperability and Standards December 10, 2010.
Data Gathering HITPC Workplan HITPC Request for Comments HITSC Committee Recommendations gathered by ONC HITSC Workgroup Chairs ONC Meaningful Use Stage.
Certification and Adoption Workgroup HIT Policy Committee April 28, 2014 Discussion on Incremental Rulemakings.
Association of Enterprise Architects International Committee on Enterprise Architecture Standards Jan 23, Collaborative Expedition Workshop #57aeajournal.org.
Office of the National Coordinator for Health Information Technology ONC Update for HITSP Board U.S. Department of Health and Human Services John W. Loonsk,
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.
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.
Federal Health IT Ontology Project (HITOP) Group
Health IT Standards Committee Workgroup Evolution Discussion
Health IT Policy Committee Workgroup Evolution
State and Regional Demonstrations of Health IT
ONC Update for HITSP Board
Presentation transcript:

Interoperability Framework Overview Health Information Technology (HIT) Standards Committee June 24, 2010 Presented by: Douglas Fridsma, MD, PhD Acting Director, Office of Interoperability & Standards, Office of the National Coordinator for Health Information Technology (ONC)

Goals of the Standards and Interoperability Framework »Move toward more “computational” implementation specifications (IS) Scalable processes Ability to develop tools to increase the efficiency of IS development and maintenance The importance of developing IS that are explicit and subject to less interpretation »Link use cases and standards from inception to certification Keep the certification processes tightly linked to the standards and IS processes Support tool development for certification testing Develop the testing for compliance at the same time as developing the standards and IS »Integrate multiple SDOs with different expertise across the process Transport packages Vocabulary Value sets Security 10/17/2015

Bottom up use case development within a top- down coordination framework 3 National Health Information Network (NHIN) Direct + Interoperability Framework = Focused Collaboration Focused Collaboration A Thousand Flowers Bloom CORE PRINCIPLES Prioritization Transparency Engagement Rapid Results Command and Control LowHigh Participation Classic Trade-Off Low High Focus

Bottom Up Innovation within a Coordination Framework 4 Tools and Services (Use Case Development, Harmonization Tools, Vocabulary Browser, Value Set Repository, Testing Scripts, etc) Use Case Development and Functional Requirements Standards Development Certification and Testing Harmonization of Core Concepts (NIEM framework) Implementation Specifications Pilot Demonstration Projects Reference Implementation

Use Case Development and Functional Requirements »Example of a use case provider wants to send a referral to a specialist electronically »Use case describes Services Standards (package) Business rules, trust, policies That are necessary to satisfy the use case The process should »Engage a wide community in defining the use cases »Focus on solving a real problem Determines scope Able to “test” if the use case solves the problem Prevents “analysis paralysis” Does not model in the abstract Open, transparent process »Establish a “use case steward” to shepherd the use cases through the entire process »Output is a clear description (in a computable form) that describes the standards, services and policies necessary to describe the use case 5 Use Case Development and Functional Requirements Standards Development Certification and Testing Harmonization of Core Concepts (NIEM framework) Implementation Specifications Pilot Demonstration Projects Reference Implementation Tools and Services (Use Case Development, Harmonization Tools, Vocabulary Browser, Value Set Repository, Testing Scripts, etc)

Harmonization of Core Concepts »Need to have a strong harmonization framework that spans different standards organizations eXtensible Markup Language (XML)/Unified Modeling Language (UML) computational descriptions of the use cases Strong governance and transparent processes Use-case driven (bottom up) with top down coordination »Harmonization processes need to describe Standards Services Policies In standard ways 6 Harmonization of Core Concepts (NIEM framework) »Multiple use cases might have overlapping standards, services or policies E-prescribing and adverse event reporting Clinical care summary and quality reporting Laboratory data exchange and clinical decision support Standards Development Use Case Development and Functional Requirements Certification and Testing Harmonization of Core Concepts (NIEM framework) Implementation Specifications Pilot Demonstration Projects Reference Implementation Tools and Services (Use Case Development, Harmonization Tools, Vocabulary Browser, Value Set Repository, Testing Scripts, etc)

Harmonization of Core Concepts »Standards harmonization Leverage best practices Use the National Information Exchange Model (NIEM) processes Create explicit data exchange package that describe the data elements, vocabularies and value sets »Service harmonization Information model Services description Conformance description Governance (business rules) descriptions »Policy descriptions Harmonization of policies is a challenge 7 Harmonization of Core Concepts (NIEM framework) »Three parts to harmonization Description of the standards (the data that is exchanged) Description of the services (the functions that will be supported in the exchange) Description of the policy (trust, business rules, etc) Use Case Development and Functional Requirements Standards Development Certification and Testing Harmonization of Core Concepts (NIEM framework) Implementation Specifications Pilot Demonstration Projects Reference Implementation Tools and Services (Use Case Development, Harmonization Tools, Vocabulary Browser, Value Set Repository, Testing Scripts, etc)

What is the NIEM process? »National Information Exchange Model »Started as a Department of Justice (DoJ) initiative, but the processes have been generalized Supported data integration and reporting for Recovery.gov Used by Department of Health & Human Services (HHS) to support child and family services Recommended by Office of Management and Budget (OMB) as best practice Used by state and local governments 8 Reference Implementation Harmonization of Core Concepts (NIEM framework) Use Case Development and Functional Requirements Standards Development Certification and Testing Harmonization of Core Concepts (NIEM framework) Implementation Specifications Pilot Demonstration Projects Tools and Services (Use Case Development, Harmonization Tools, Vocabulary Browser, Value Set Repository, Testing Scripts, etc)

What is the NIEM framework? »A common core of concepts, explicitly defined, that are shared across different use cases or domains »Naming and modeling conventions that allow different groups to work independently but harmonize the work together »Based on the ISO metadata standard used by the (NCI), NLM, and standards organizations. 10/17/2015 Patient Discovery Quality reporting Discharge Summary Provider address lookup Future Domains E-prescribingLab data exchange PHR exchange Patient summary Child and Family Services Common Core Harmonization of Core Concepts (NIEM framework)

Standards Development »Gaps in existing standards Data package Value sets Services »Can be identified as part of the use case development and harmonization process »Work with SDOs (NLM, HL7 etc) to fill in gaps »Allows the standards work to proceed in parallel with development of the implementation specifications 10 Standards Development Use Case Development and Functional Requirements Standards Development Certification and Testing Harmonization of Core Concepts (NIEM framework) Implementation Specifications Pilot Demonstration Projects Tools and Services (Use Case Development, Harmonization Tools, Vocabulary Browser, Value Set Repository, Testing Scripts, etc)

Implementation Specifications »If the standards, services and policies are the ingredients, then the implementation specification is the recipe »Packaged together to support use cases »Guides development of reference implementation »Interim Final Rule requires creation of Implementation Specifications where they don’t exist 11 Implementation Specifications »An implementation specification becomes a explicit description of the Standards Services Policies »That conform to adopted standards and have sufficient detail to be implemented Use Case Development and Functional Requirements Standards Development Certification and Testing Harmonization of Core Concepts (NIEM framework) Implementation Specifications Pilot Demonstration Projects Reference Implementation Tools and Services (Use Case Development, Harmonization Tools, Vocabulary Browser, Value Set Repository, Testing Scripts, etc)

Reference Implementation »Specification must be tested to make sure they can be implemented »Can be used by others to help guide their own implementation or find problems with specifications »Encourages feedback to ONC 12 Reference Implementation »Example: CONNECT software could potentially be the reference implementation of NHIN specifications and standards Use Case Development and Functional Requirements Standards Development Certification and Testing Harmonization of Core Concepts (NIEM framework) Implementation Specifications Pilot Demonstration Projects Reference Implementation Tools and Services (Use Case Development, Harmonization Tools, Vocabulary Browser, Value Set Repository, Testing Scripts, etc)

Pilot Demonstration Projects »Reference implementation in use by stakeholders »Confirms use case is being supported »ONC should provide coordination of pilot demonstrations 13 Pilot Demonstration Projects »NHIN Trial Implementations »NHIN Limited Production Exchange »NHIN Direct Project Use Case Development and Functional Requirements Standards Development Certification and Testing Harmonization of Core Concepts (NIEM framework) Implementation Specifications Pilot Demonstration Projects Reference Implementation Tools and Services (Use Case Development, Harmonization Tools, Vocabulary Browser, Value Set Repository, Testing Scripts, etc)

Certification and Testing »Culmination of prior activities »NIST can help create test harnesses to ensure conformance with specifications 14 Certification and Testing National Institute of Standards and Technology (NIST) Conformance tools Tools and resources for certification processes Use Case Development and Functional Requirements Standards Development Certification and Testing Harmonization of Core Concepts (NIEM framework) Implementation Specifications Pilot Demonstration Projects Reference Implementation Tools and Services (Use Case Development, Harmonization Tools, Vocabulary Browser, Value Set Repository, Testing Scripts, etc)

Tools and Services »Make the process as automated and self-serve as possible »Leverage tools & services in future efforts 15 Tools and Services (Use Case Development, Harmonization Tools, Vocabulary Browser, Value Set Repository, Testing Scripts, etc) Use Case Development and Functional Requirements Standards Development Certification and Testing Harmonization of Core Concepts (NIEM framework) Implementation Specifications Pilot Demonstration Projects Reference Implementation

Bottom Up Innovation within a Coordination Framework 16 Tools and Services (Use Case Development, Harmonization Tools, Vocabulary Browser, Value Set Repository, Testing Scripts, etc) Information Model, Services, and Value Sets Harmonized/ Implementation Specification Integration Testing and Implementation Reference Code Set Use Case Development and Functional Requirements Standards Development Certification and Testing Harmonization of Core Concepts (NIEM framework) Implementation Specifications Pilot Demonstration Projects Reference Implementation

S&I and HITSC Activities NHIN Direct Activities J J A S O N D J F M A M J J A S O N Tools and Services (Use Case Development, Harmonization Tools, Vocabulary Browser, Value Set Repository, Testing Scripts, etc) Use Case Development and Functional Requirements Standards Development Certification and Testing Harmonization of Core Concepts (NIEM framework) Implementation Specifications Reference Implementation Implementation Specifications Pilot Demonstration Projects Reference Implementation HITPC Activities HITPC P&S Tiger Team Policy Framework HITPC + HITSC Specification Policy Review HITPC + HITSC Specification Policy Review HIT Standards Committee Review NHIN Inclusion Evaluation Other Standards Governance Evaluations NHIN Direct Example