HIT Policy Committee Information Exchange Workgroup NwHIN Conditions for Trusted Exchange Request For Information (RFI) May 18, 2012 1.

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

ELTSS Alignment to Nationwide Interoperability Roadmap DRAFT: For Stakeholder Consideration in response to public comment.
Information Risk Management Key Component for HIPAA Security Compliance Ann Geyer Tunitas Group
Congress and Contractor Personal Conflicts of Interest May 21, 2008 Jon Etherton Etherton and Associates, Inc.
HITPC Information Exchange Workgroup Discussion of Governance RFI May 16,
Proposed Establishment of Certification Programs for Health Information Technology Notice of Proposed Rulemaking HIT Standards Committee Presentation.
Connecting Health and Care for the Nation: A Shared Nationwide Interoperability Roadmap – DRAFT Version 1.0 Joint FACA Meeting Chartese February 10, 2015.
Privacy and Security Workgroup: Big Data Public Hearing December 8, 2014 Deven McGraw, chair Stan Crosley, co-chair.
Interoperability Standards Advisory Summary of Public Comments and Next Steps June 24, 2015 Chris Muir.
Discussion of 2015 Ed. NPRM Certification/Adoption Workgroup HIT Policy Committee April 2, 2014.
Information Systems Controls for System Reliability -Information Security-
Understanding and Leveraging MU2 Optional Transports Paul M. Tuten, PhD Senior Consultant, ONC Leader, Implementation Geographies Workgroup, Direct Project.
Minnesota Law and Health Information Exchange Oversight Activities James I. Golden, PhD State Government Health IT Coordinator Director, Health Policy.
August 12, Meaningful Use *** UDOH Informatics Brown Bag Robert T Rolfs, MD, MPH.
HIT Policy Committee Nationwide Health Information Network Governance Workgroup Recommendations Accepted by the HITPC on 12/13/10 Nationwide Health Information.
Authentication, Access Control, and Authorization (1 of 2) 0 NPRM Request (for 2017) ONC is requesting comment on two-factor authentication in reference.
SCHC, 9/27/2005 US Implementation of the Globally Harmonized System The GHS Journey Continues…
How Hospitals Protect Your Health Information. Your Health Information Privacy Rights You can ask to see or get a copy of your medical record and other.
Interoperability Updates -National Interoperability Roadmap 8/20/2014 Erica Galvez, ONC Interoperability Portfolio Manager.
Regional Integration Cluster Olivier Hartmann - SSATP.
Nationwide Health Information Network: Conditions for Trusted Exchange Request For Information (RFI) Steven Posnack, MHS, MS, CISSP Director, Federal Policy.
HIT Standards Committee Privacy and Security Workgroup: Initial Reactions Dixie Baker, SAIC Steven Findlay, Consumers Union June 23, 2009.
Draft – discussion only Content Standards WG (Documents and Data) Proposed HITSC Workgroup Evolution 1 Architecture, Services & APIs WG Transport and Security.
Implementation of EU Electronic Communication Directives.
DRAFT – For Discussion Only HHSC IT Governance Executive Briefing Materials DRAFT April 2013.
HIT Policy Committee Information Exchange Workgroup NwHIN Conditions for Trusted Exchange Request For Information (RFI) May 15,
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.
HIT Policy Committee Privacy & Security Workgroup Update Deven McGraw Center for Democracy & Technology Rachel Block Office of Health Information Technology.
1 Meaningful Use Stage 2 The Value of Performance Benchmarking.
Copyright © 2009 by The McGraw-Hill Companies, Inc. All Rights Reserved. McGraw-Hill Chapter 6 The Privacy and Security of Electronic Health Information.
HIT Policy Committee Adoption/Certification Workgroup Comments on NPRM, IFR Paul Egerman, Co-Chair Retired Marc Probst, Co-Chair Intermountain Healthcare.
1 Privacy and Security Tiger Team Meeting Discussion Materials Today’s Topics Governance RFI Prioritized Questions June 4, 2012.
The Culture of Healthcare Privacy, Confidentiality, and Security Lecture d This material (Comp2_Unit9d) was developed by Oregon Health and Science University,
ONC’s Proposed Strategy on Governance for the Nationwide Health Information Network Following Public Comments on RFI HIT Standards Committee Meeting September.
Larry Wolf Certification / Adoption Workgroup May 13th, 2014.
HIT Standards Committee Privacy and Security Workgroup Final Recommendations for NwHIN Governance RFI Assigned Questions Dixie Baker, Chair Walter Suarez,
Health Information Technology EHR Meaningful Use Milestones for HIT Funding Michele Madison
EGovOS Panel Discussion CIO Council Architecture & Infrastructure Committee Subcommittee Co-Chairs March 15, 2004.
HIT Policy Committee NwHIN Governance Workgroup NwHIN Conditions for Trusted Exchange Request For Information (RFI) May 15,
Scalable Trust Community Framework STCF (01/07/2013)
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.
Linking the learning to the National Standards for Safer Better Healthcare Joan Heffernan Inspector Manager Regulation – Healthcare Health Information.
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.
HIT Standards Committee Privacy and Security Workgroup Progress Report on Review of Governance RFI Dixie Baker, Chair Walter Suarez, Co-Chair May 24, 2012.
Certification and Adoption Workgroup HIT Policy Committee April 28, 2014 Discussion on Incremental Rulemakings.
Functioning as a Business Associate Under HIPAA William F. Tulloch Director, PCBA March 9, 2004.
360Exchange (360X) Project 12/06/12. Reminders / announcements 360X Update CEHRT 2014 / MU2 Transition of Care Requirements 1 Agenda.
Governance Workgroup Recommendations on Scope of Nationwide Health Information Network Governance Functions John Lumpkin, MD, MPH, Chair Robert Wood Johnson.
ACWG Charge Make recommendations to the Health IT Policy Committee on how HHS policies and programs can advance the evolution of a health IT infrastructure.
The Health Insurance Portability and Accountability Act of 1996 “HIPAA” Public Law
Organizations of all types and sizes face a range of risks that can affect the achievement of their objectives. Organization's activities Strategic initiatives.
COBIT. The Control Objectives for Information and related Technology (COBIT) A set of best practices (framework) for information technology (IT) management.
Interoperability Measurement for the MACRA Section 106(b) ONC Briefing for HIT Policy and Standards Committee April 19, 2016.
ONC Listening Session June 26, 2009 American Recovery and Reinvestment Act of 2009 Section 3013: State Grant Program.
The Value of Performance Benchmarking
Update from the Faster Payments Task Force
Quality and Qualifications Ireland and its Functions
Accreditation Update Regional Municipality of Durham March 15, 2018.
Health IT Policy Committee Workgroup Evolution
Healthcare Privacy: The Perspective of a Privacy Advocate
Data and Interoperability:
THE 13TH NATIONAL HIPAA SUMMIT HEALTH INFORMATION PRIVACY & SECURITY IN SHARED HEALTH RECORD SYSTEMS SEPTEMBER 26, 2006 Paul T. Smith, Esq. Partner,
HIPAA Compliance Services CTG HealthCare Solutions, Inc.
HIPAA Compliance Services CTG HealthCare Solutions, Inc.
An overview of Internal Controls Structure & Mechanism
Presentation transcript:

HIT Policy Committee Information Exchange Workgroup NwHIN Conditions for Trusted Exchange Request For Information (RFI) May 18,

Our Ten Questions 2 Establishing a Governance Mechanism Question 1: Would these categories [Safeguards, Interoperability, Business Practices] comprehensively reflect the types of CTEs needed to govern the nationwide health information network? If not, what other categories should we consider? Question 2: What kind of governance approach would best produce a trusted, secure, and interoperable electronic exchange nationwide? Question 3: How urgent is the need for a nationwide governance approach for electronic health information exchange? Conversely, please indicate if you believe that it is untimely for a nationwide approach to be developed and why. Question 4: Would a voluntary validation approach as described above sufficiently achieve this goal? If not, why? Question 5: Would establishing a national validation process as described above effectively relieve any burden on the States to regulate local and regional health information exchange markets? Question 6: How could we ensure alignment between the governance mechanism and existing State governance approaches? Question 7: What other approaches to exercising our authority to establish a governance mechanism for the nationwide health information network should we consider? CTE Lifecycle Question 60: What process should we use to update CTEs? Question 61: Should we expressly permit validation bodies to provide for validation to pilot CTEs? Question 62: Should we consider a process outside of our advisory committees through which the identification and development to frame new CTEs could be done?

General Need for Governance QuestionComments Question 3: How urgent is the need for a nationwide governance approach for electronic health information exchange? Conversely, please indicate if you believe that it is untimely for a nationwide approach to be developed and why. 3

Nationwide Health Information Network Governance Conditions of Trusted Exchange Conditions for Trusted Exchange (CTEs) – Three Domains: –Safeguards: focus on the protection of individually identifiable health information (IIHI) to ensure its confidentiality, integrity, and availability and to prevent unauthorized or inappropriate access, use, or disclosure. Example [S-1]: An NVE must comply as if it were a covered entity, and must treat all implementation specifications as “required.” –Interoperability: focus on the technical standards and implementation specifications needed for exchanging electronic health information. Example [I-2]: An NVE must follow required standards for establishing and discovering digital certificates. –Business Practices: focus on the operational and financial practices to which NVEs would need to adhere in support of trusted electronic health information exchange. Example [BP-2]: An NVE must provide open access to the directory services it provides to enable planned electronic exchange. 4

Domains QuestionComments Question 1: Would these categories [Safeguards, Interoperability, Business Practices] comprehensively reflect the types of CTEs needed to govern the nationwide health information network? If not, what other categories should we consider? 5

Governance Approach An important component of the governance mechanism we are considering would be the establishment of a voluntary framework for entities that facilitate electronic exchange to be validated to CTEs adopted for the exchange services or activities they are capable of supporting. Upon successful validation to the CTEs, an entity would be recognized as a NVE and thus would be recognized as an entity that would be accountable for the electronic exchange services or activities it performs in accordance with the CTEs. Given the incremental CTE adoption approach we expect to take, we also anticipate that the recognition of NVEs would incrementally expand along with the diversity of the electronic exchange services or activities they are able to perform. Thus, we could see providing NVEs or new entities with other categorical recognition(s) for the electronic exchange services or activities they are capable of supporting in accordance with subsequently adopted CTEs. Additionally, this validation process would support an evolution, in the U.S. and internationally, towards engaging accountability agents as a supplemental means for ensuring that organizations and providers involved in the management, storage, and transport of IIHI adhere to policies and practices that protect the privacy and security of information 6

Voluntary Nature of Governance It is also our expectation that validation would be voluntary. In other words, the validation process established as part of the governance mechanism would not be mandatory and would only apply in so far as an entity deciding that there would be value (e.g., prestige, competitive advantage) in seeking validation. That said, once the validation process is established, much like other government programs on which subsequent policy objectives could be leveraged, it would be possible for other public and private organizations to specify NVE recognition as a condition in awarding contracts, procurements and/or in other situations where validation would be beneficial. 7

Governance Approach QuestionComments Question 2: What kind of governance approach would best produce a trusted, secure, and interoperable electronic exchange nationwide? Question 4: Would a voluntary validation approach as described above sufficiently achieve this goal? If not, why? Question 7: What other approaches to exercising our authority to establish a governance mechanism for the nationwide health information network should we consider? 8

Governance And States QuestionComments Question 5: Would establishing a national validation process as described above effectively relieve any burden on the States to regulate local and regional health information exchange markets? Question 6: How could we ensure alignment between the governance mechanism and existing State governance approaches? 9

CTE Lifecycle Assuming we were to pursue an approach that includes the adoption of CTEs as part of a governance mechanism for the nationwide health information network, we expect that additional CTEs and revisions to CTEs would be necessary to accommodate policy maturity and technical changes over time. We believe that an inclusive and transparent process to identify, modify, and retire CTEs would be needed to engage stakeholders and would result in more refined and widely accepted CTEs. The purpose of this process would be to identify and assess current electronic exchange needs and to provide a path for determining how best to address them through the CTEs. We envision that rulemaking could be necessary every two years, most likely on years that would alternate with regulations published for EHR Incentive Programs, to keep the CTEs up-to-date and to permit entities to seek validation to new CTEs for other more complex forms of electronic exchange. 10

CTE Lifecycle (2) We believe that an approach to a CTE maturity life cycle could start with the identification of “emerging” CTEs, followed by the identification of “pilot” CTEs, followed by “national” candidate CTEs which we would consider sufficiently mature to propose for adoption. We believe that the “pilot” stage could empower greater stakeholder participation in governance and could permit the direct submission of best practices to ONC or through one of our advisory committees. It could also potentially enable validation bodies to provide for validation to pilot CTEs which would provide further input in terms of the CTEs’ readiness to be identified as national candidate CTEs. We could see using the HIT Policy Committee and HIT Standards Committee to provide a forum to solicit public input on identifying best practices and piloting CTEs in a manner consistent with their statutory authority. We would further envision that this process would follow the procedures and comport with the requirements of section 3004 and other relevant sections of the PHSA, for the development and adoption of standards, implementation specifications, and certification criteria 11

CTE Lifecycle Questions QuestionComments Question 60: What process should we use to update CTEs? Question 61: Should we expressly permit validation bodies to provide for validation to pilot CTEs? Question 62: Should we consider a process outside of our advisory committees through which the identification and development to frame new CTEs could be done? 12