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

Slides:



Advertisements
Similar presentations
H = P = A = HIPAA DEFINED HIPAA … A Federal Law Created in 1996 Health
Advertisements

Reliability Provisions of EPAct of 2005 & FERC’s Final Rule
Presented by Elena Chan, UCSF Pharm.D. Candidate Tiffany Jew, USC Pharm.D. Candidate March 14, 2007 P HARMACEUTICAL C ONSULTANTS, I NC. P RO P HARMA HIPAA.
HIPAA Privacy Rule Training
Information Risk Management Key Component for HIPAA Security Compliance Ann Geyer Tunitas Group
Connecticut Ave NW, Washington, DC Understanding Patient Engagement in Stage 2 MU: Direct, HIPAA, VDT, and Patient Engagement.
Health Insurance Portability Accountability Act of 1996 HIPAA for Researchers: IRB Related Issues HSC USC IRB.
Recommendations on Certification of EHR Modules HIT Standards Committee Privacy and Security Workgroup April 11, 2014.
Health IT Privacy and Security Policy Jodi Daniel, J.D., M.P.H. Director, Office of Policy and Research, Office of the National Coordinator for Health.
Electronic Submission of Medical Documentation (esMD) for Medicare FFS Presentation to HITSC Provenance Workgroup January 16, 2015.
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.
Chapter 9 Information Systems Controls for System Reliability— Part 2: Confidentiality and Privacy Copyright © 2012 Pearson Education, Inc. publishing.
Discussion of 2015 Ed. NPRM Certification/Adoption Workgroup HIT Policy Committee April 2, 2014.
Understanding and Leveraging MU2 Optional Transports Paul M. Tuten, PhD Senior Consultant, ONC Leader, Implementation Geographies Workgroup, Direct Project.
Per Anders Eriksson
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.
1 HIPAA Security Overview Centers for Medicare & Medicaid Services (CMS)
HIT Policy Committee Privacy and Security Tiger Team Deven McGraw, Chair Paul Egerman, Co-Chair Provider Authentication Recommendations November 19, 2010.
Secure Electronic Transaction (SET)
HIPAA PRIVACY AND SECURITY AWARENESS.
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.
Update on Federal HIT Legislation Kirsten Beronio Mental Health America.
Computerized Networking of HIV Providers Workshop Data Security, Privacy and HIPAA: Focus on Privacy Joy L. Pritts, J.D. Assistant Research Professor Health.
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.
TFTM Interim Trust Mark/Listing Approach Paper Analysis of Current Industry Trustmark Programs and GTRI PILOT Approach Discussion Deck TFTM Committee.
Nationwide Health Information Network: Conditions for Trusted Exchange Request For Information (RFI) Steven Posnack, MHS, MS, CISSP Director, Federal Policy.
Patient Protection and Affordable Care Act March 23, 2010.
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
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.
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.
Practice Management Quality Control
Copyright © 2009 by The McGraw-Hill Companies, Inc. All Rights Reserved. McGraw-Hill Chapter 6 The Privacy and Security of Electronic Health Information.
© 2013 The McGraw-Hill Companies, Inc. All rights reserved. Ch 8 Privacy Law and HIPAA.
The right item, right place, right time. DLA Privacy Act Code of Fair Information Principles.
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.
HIT Policy Committee Information Exchange Workgroup NwHIN Conditions for Trusted Exchange Request For Information (RFI) May 18,
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.
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
HIT Policy Committee NwHIN Governance Workgroup NwHIN Conditions for Trusted Exchange Request For Information (RFI) May 15,
PROTECTION OF PERSONAL DATA. OECD GUIDELINES: BASIC PRINCIPLES OF NATIONAL APPLICATION Collection Limitation Principle There should be limits to the collection.
A Road Map to Research at Jefferson: HIPAA Privacy and Security Rules for Researchers Presented By: Privacy Officer/Office of Legal Counsel October 2015.
HIT Policy Committee NHIN Workgroup HIE Trust Framework: HIE Trust Framework: Essential Components for Trust April 21, 2010 David Lansky, Chair Farzad.
Overview of ONC Report to Congress on Health Information Blocking Presented to the Health IT Policy Committee, Task Force on Clinical, Technical, Organizational,
HIT Policy Committee Meeting Nationwide Health Information Network Governance June 25, 2010 Mary Jo Deering, PhD ONC, Office of Policy and Planning NHIN.
HIT Standards Committee Privacy and Security Workgroup Progress Report on Review of Governance RFI Dixie Baker, Chair Walter Suarez, Co-Chair May 24, 2012.
VETERANS HEALTH ADMINISTRATION SLIDE 0 New Requirements for VA ORD Investigators: Implementation of Data Management and Access Plans.
Clinical Quality Workgroup April 10, 2014 Commenting on the ONC Voluntary 2015 Edition Proposed Rule Marjorie Rallins– co-chair Danny Rosenthal –co-chair.
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.
HIT Policy Committee Privacy & Security Workgroup Update Deven McGraw Center for Democracy & Technology Rachel Block Office of Health Information Technology.
The Health Insurance Portability and Accountability Act of 1996 “HIPAA” Public Law
New Hire HIPAA Orientation. HIPAA Overview HIPAA is an acronym that stands for the Health Insurance Portability and Accountability Act of HIPAA.
Interoperability Measurement for the MACRA Section 106(b) ONC Briefing for HIT Policy and Standards Committee April 19, 2016.
The Value of Performance Benchmarking
Overview nate-trust.org Who (describe your organization)
What is HIPAA? HIPAA stands for “Health Insurance Portability & Accountability Act” It was an Act of Congress passed into law in HEALTH INSURANCE.
HIPAA Administrative Simplification
Disability Services Agencies Briefing On HIPAA
THE 13TH NATIONAL HIPAA SUMMIT HEALTH INFORMATION PRIVACY & SECURITY IN SHARED HEALTH RECORD SYSTEMS SEPTEMBER 26, 2006 Paul T. Smith, Esq. Partner,
Government Data Practices & Open Meeting Law Overview
Presentation transcript:

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

Our Eight Questions 2 Actors, Accreditation and Validation Bodies, and Validation Entity Eligibility 1. Question 8: We solicit feedback on the appropriateness of ONC’s role in coordinating the governance mechanism and whether certain responsibilities might be better delegated to, and/or fulfilled by, the private sector. Question 9: Would a voluntary validation process be effective for ensuring that entities engaged in facilitating electronic exchange continue to comply with adopted CTEs? If not, what other validation processes could be leveraged for validating conformance with adopted CTEs? If you identify existing processes, please explain the focus of each and its scope. Question 10:Should the validation method vary by CTE? Which methods would be most effective for ensuring compliance with the CTEs? (Before answering this question it may be useful to first review the CTEs we are considering to adopt, see section “VI. Conditions for Trusted Exchange.” Question 11:What successful validation models or approaches exist in other industries that could be used as a model for our purposes in this context? Question 13:Should there be an eligibility criterion that requires an entity to have a valid purpose (e.g., treatment) for exchanging health information? If so, what would constitute a “valid” purpose for exchange? Question 14:Should there be an eligibility criterion that requires an entity to have prior electronic exchange experience or a certain number of participants it serves? Question 15:Are there other eligibility criteria that we should also consider? Question 16:Should eligibility be limited to entities that are tax-exempt under section 501(c)(3) of the IRC? If yes, please explain why.

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

Accreditation and Validation Process Overview 4  Similar to the permanent certification program for HIT, the National Coordinator would approve a single body to accredit and oversee validation bodies.  Validation bodies would evaluate an entity’s conformance to adopted CTEs as opposed to a particular product’s (e.g., EHR technology) certification to certification criteria.  Certified HIT could be used by an entity as a way to demonstrate conformance with certain adopted CTEs  Accreditation body would be expected to conform to internationally accepted standards for accreditation bodies  Validation bodies - upon accreditation by the accreditation body and authorization from the National Coordinator - would subsequently perform the validation of entities‘ conformance to adopted CTEs.  Validation could use different methodologies (self-attestation, laboratory testing for conformance, certification, accreditation) and could vary depending on CTE type and potential methodology burden.

Actors and Associated Responsibilities 8. ONC’s roles & delegation of responsibilities to the private sector. 5 Proposed Role Suggested Lead Existing Authorities and/or Alternatives to Consider 1. Endorsing and adopting CTEs, publishing guidance ONCIn accordance with the National Coordinator‘s authority at section 3001(c)(1)(A) and processes identified at section 3004 under the PHSA, and publishing interpretative guidance 2. Facilitating the receipt of input from the HIT Policy and Standards Committees and other interested parties on: revisions to CTEs, new CTEs, and the appropriate retirement of CTEs ONCIn accordance with processes identified at sections 3002(b)(3) and 3003(b)(2) of the PHSA 3. Selection and oversight processes for an accreditation body ONCONC would approve a single body to accredit and oversee “validation bodies”. 4. Authorizing and overseeing validation bodies responsible for validating that eligible entities have met adopted CTEs ONC 5. Administering a process to classify the readiness for nationwide adoption and use of technical standards and implementation specifications to support interoperability related CTEs ONC[ONC would have to adopt specific certification criteria that could be used to certify other types of HIT through established certification program. 6. Overall oversight of all entities and processes established as part of the governance mechanism. ONC

ONC Role 8. Voluntary Nature of Process 6 RoleComments We solicit feedback on the appropriateness of ONC’s role in coordinating the governance mechanism and whether certain responsibilities might be better delegated to, and/or fulfilled by, the private sector.

Validation Process 9. Voluntary Nature of Process 7 RoleComments 9(a) Would a voluntary validation process be effective for ensuring that entities engaged in facilitating electronic exchange continue to comply with adopted CTEs? 9(b) What other validation processes could be leveraged for validating conformance with adopted CTEs?

Conditions for Trusted Exchange Safeguards 8 [S-1]: An NVE must comply as if it were a covered entity, and must treat all implementation specifications as “required.” [S-2]: An NVE must only facilitate electronic health information exchange for parties it has authenticated and authorized, either directly or indirectly. [S-3]: An NVE must ensure that individuals are provided with a meaningful choice regarding whether their IIHI may be exchanged by the NVE. [S-4]: An NVE must only exchange encrypted IIHI. [S-5]: An NVE must make publicly available a notice of its data practices describing why IIHI is collected, how it is used, and to whom and for what reason it is disclosed. [S-6]: An NVE must not use or disclose de-identified health information to which it has access for any commercial purpose. [S-7]: An NVE must operate its services with high availability. [S-8]: If an NVE assembles or aggregates health information that results in a unique set of IIHI, then it must provide individuals with electronic access to their unique set of IIHI. [S-9]: If an NVE assembles or aggregates health information which results in a unique set of IIHI, then it must provide individuals with the right to request a correction and/or annotation to this unique set of IIHI. [S-10]: An NVE must have the means to verify that a provider requesting an individual’s health information through a query and response model has or is in the process of establishing a treatment relationship with that individual.

Conditions for Trusted Exchange Interoperability 9 [I-1]: An NVE must be able to facilitate secure electronic health information exchange in two circumstances: 1) when the sender and receiver are known; and 2) when the exchange occurs at the patient’s direction. [I-2]: An NVE must follow required standards for establishing and discovering digital certificates. [I-3]: An NVE must have the ability to verify and match the subject of a message, including the ability to locate a potential source of available information for a specific subject.

Conditions for Trusted Exchange Business Practices 10 [BP-1]: An NVE must send and receive any planned electronic exchange message from another NVE without imposing financial preconditions on any other NVE. [BP-2]: An NVE must provide open access to the directory services it provides to enable planned electronic exchange. [BP-3]: An NVE must report on users and transaction volume for validated services.

Validation Process 10. Validation Method 11 RoleComments 10 (a) Should the validation method vary by CTE? 10 (b) Which methods would be most effective for ensuring compliance with CTEs? Examples of validation methods from RFI: self-attestation, laboratory testing for conformance, certification, accreditation

Validation Process 11. Comparative Models 12 RoleComments 11. What successful validation models or approaches exist in other industries that could be used as a model for our purposes in this context?

NwHIN Validated Entity (NVE) Eligibility Criteria Overview 13 The RFI considers the following criteria that NVEs must meet to be eligible:  Meet all solvency and financial responsibility requirements imposed by the statutes and regulatory authorities of the State or States in which it, or any subcontractor performing some or all of its functions, would serve.  Make some type of financial disclosure filing  Provide evidence that it has a surety bond or some other form of financial security  Have the overall resources and experience to fulfill its responsibilities in accordance with the CTEs when performing health information exchange services  Have at least one year of experience  Serve a sufficient number of providers to permit a finding of effective and efficient administration; however, no prospective NVE would be deemed ineligible if it only served providers located in a single State  Have to be a valid business or governmental entity operating in the United States.  Have not had civil monetary penalties, criminal penalties, or damages imposed, or have been enjoined for a HIPAA violation within two years prior to seeking validation  Not be listed on the Excluded Parties List System maintained by the General Services Administration  Not be listed on the List of Excluded Individuals and Entities maintained by the Office of Inspector General  Would not be appropriate to limited to tax-exempt 501(c)(3) organizations.  Some of the eligibility criteria being considered may be inapplicable to fed/State governmental entities.

Eligibility Criteria 13. Organizational Purpose 14 RoleComments 13 (a) Should there be an eligibility criterion that requires an entity to have a valid purpose (e.g., treatment) for exchanging health information? 13 (b) If so, what would constitute a valid purpose for exchange?

Eligibility Criteria 14. Prior Experience 15 RoleComments 14. Should there be an eligibility criterion that requires an entity to have prior electronic exchange experience or a certain number of participants it serves?

Eligibility Criteria 15. Other Criteria to Consider 16 RoleComments 15. Are there other eligibility criteria that we should also consider?

Eligibility Criteria 16. Tax Exempt Status 17 RoleComments 16. Should eligibility be limited to entities that are tax- exempt under section 501(c)(3) of the IRC? If yes, please explain why.?