Health IT Standards Committee Work Product Health IT Standards Committee A Public Advisory Body on Health Information Technology to the National Coordinator.

Slides:



Advertisements
Similar presentations
Quality Measures Vendor Tiger Team January 30, 2014.
Advertisements

ELTSS Alignment to Nationwide Interoperability Roadmap DRAFT: For Stakeholder Consideration in response to public comment.
1 HIT Standards Committee Privacy and Security Workgroup: Recommendations Dixie Baker, SAIC Steven Findlay, Consumers Union August 20, 2009.
Task Force Session Standards & Interoperability Task Force Stan Huff, Co-Chair Arien Malec, Co-Chair February 17, 2015.
Interoperability Roadmap Comments Package Transport & Security Standards Workgroup Dixie Baker, chair Lisa Gallagher, co-chair February 24, 2015.
Cracking the Code on Nationwide Interoperability DISCLAIMER: The views and opinions expressed in this presentation are those of the author and do not necessarily.
Interoperability and Health Information Exchange Workgroup March 10, 2015 Micky Tripathi, chair Chris Lehmann, co-chair.
Health IT Standards Committee Federal Health IT Strategic Plan December 10, 2014 Seth Pazinski Director, Office of Planning, Evaluation, and.
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.
Consumer Work Group Presentation Federal Health IT Strategic Plan January 9, 2015 Gretchen Wyatt Office of Planning, Evaluation, and Analysis.
Kickoff Meeting Precision Medicine Task Force July 17, 2015 Leslie Kelly Hall, Co-Chair Jon White, Co-Chair.
August 12, Meaningful Use *** UDOH Informatics Brown Bag Robert T Rolfs, MD, MPH.
Community Information Technology Engagement (CITE): Program Overview
HIT Policy Committee Accountable Care Workgroup – Kickoff Meeting May 17, :00 – 2:00 PM Eastern.
Strategy and Innovation Workgroup: Recommendations on the Federal Health IT Strategic Plan March 4, 2015 David Lansky, Chair Jennifer Covich,
August 10, 2011 A Leading Provider of Consulting and Systems Engineering Services to Public Health Organizations.
Update on Newborn Screening Use Case Advisory Committee on Heritable Diseases in Newborns and Children - Advisory Committee on Heritable Diseases in Newborns.
Privacy and Security Tiger Team Recommendations Adopted by The Health IT Policy Committee Relevant to Consumer Empowerment May 24, 2013.
HIT Policy Committee Nationwide Health Information Network Governance Workgroup Recommendations Accepted by the HITPC on 12/13/10 Nationwide Health Information.
Presentations from Subject Matter Experts Precision Medicine Task Force July 29, 2015 Leslie Kelly Hall, Co-Chair Jon White, Co-Chair.
Update on Interoperability Roadmap Comments Sections G, F and E Transport & Security Standards Workgroup Dixie Baker, chair Lisa Gallagher, co-chair March.
Interoperability and Health Information Exchange Workgroup April 2, 2015 Micky Tripathi, chair Chris Lehmann, co-chair 1.
1 Collaboration and Concept Exploration Nationwide Health Information Organization (NHIO) Gateway March 28, 2007.
3 June 2010National Academies - BRDI1 Research Data and Information: Recent Developments and Continuing NIH Interests Jerry Sheehan Assistant Director.
Chapter 6 – Data Handling and EPR. Electronic Health Record Systems: Government Initiatives and Public/Private Partnerships EHR is systematic collection.
Data Intermediaries and Meaningful Use: Quality Measure Innovation, Calculation and Reporting Recommendations from Data Intermediary Tiger Team.
Larry Wolf, chair Marc Probst, co-chair Certification / Adoption Workgroup March 19, 2014.
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.
Draft Preliminary Recommendations Precision Medicine Task Force September 18, 2015 Leslie Kelly Hall, Co-Chair Jon White, Co-Chair.
National Institute of Standards and Technology Information Technology Laboratory 1 USG Cloud Computing Technology Roadmap Next Steps NIST Mission: To promote.
Draft – discussion only Advanced Health Models and Meaningful Use Workgroup June 23, 2015 Paul Tang, chair Joe Kimura, co-chair.
0 HIT Standards Committee Consumer/Patient Engagement Power Team Leslie Kelly Hall, Chair Health IT Standards Committee Meeting April 18, 2012.
0 Connectathon 2009 Registration Bob Yencha Webinar | August 28, 2008 enabling healthcare interoperability.
Task Force Discussion Standards & Interoperability Task Force Stan Huff, Co-Chair Arien Malec, Co-Chair January 30, 2015.
Query Health Vendor Advisory Meeting 12/15/2011. Agenda Provide Overview of Query Health Seek Guidance and Feedback on Integration Approaches.
Kickoff Meeting Precision Medicine Task Force July 17, 2017 Leslie Kelly Hall, Co-Chair Jon White, Co-Chair.
Larry Wolf Certification / Adoption Workgroup May 13th, 2014.
(Slide 1 of 22) Response to the National Vaccine Advisory Committee Recommendations on the Immunization Safety Office Scientific Agenda Frank DeStefano,
Preliminary Recommendations to Health IT Standards Committee Precision Medicine Task Force September 22, 2015 Leslie Kelly Hall, Co-Chair Jon White, Co-Chair.
HITSC Update Precision Medicine Task Force August 31, 2015 Leslie Kelly Hall, Co-Chair Jon White, Co-Chair.
HIT Standards Committee Overview and Progress Report March 17, 2010.
Cris Ross, co-chair Anita Somplasky, co-chair December 1, 2015 Certified Technology Comparison (CTC) Task Force.
S&I Public Health Education Series: Data Provenance July 9th, 2014 Johnathan Coleman Initiative Coordinator – Data Provenance ONC/OCPO/OST (CTR)
HIT Policy Committee NHIN Workgroup HIE Trust Framework: HIE Trust Framework: Essential Components for Trust April 21, 2010 David Lansky, Chair Farzad.
Moving the National Health Information Technology Agenda Forward The Fourth Health Information Technology Summit March 28, 2007 Robert M. Kolodner, MD.
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.
Update to HITSC Standards & Interoperability Task Force Stan Huff, Co-Chair Arien Malec, Co-Chair January 27, 2015.
Overview of ONC Report to Congress on Health Information Blocking Presented to the Health IT Policy Committee, Task Force on Clinical, Technical, Organizational,
Virtual Hearing of the Health IT Policy Committee Clinical, Technical, Organizational and Financial Barriers to Interoperability Task Force Friday, August.
Draft Preliminary Recommendations Precision Medicine Task Force September 10, 2015 Leslie Kelly Hall, Co-Chair Jon White, Co-Chair.
EHealth Initiative Business and Clinical Motivator Work Group January 21, :00 p.m. EDT.
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.
Clinical, Technical, Organizational and Financial Barriers to Interoperability Task Force August 14, 2015 Paul Tang, chair.
Task Force Meeting Precision Medicine Task Force March 30, 2016 Leslie Kelly Hall, Co-Chair Andy Wiesenthal, Co-Chair.
Task Force Meeting Precision Medicine Task Force February 26, 2016 Leslie Kelly Hall, Co-Chair Andy Wiesenthal, Co-Chair.
Health IT Standards Committee A Public Advisory Body on Health Information Technology to the National Coordinator for Health IT 2017 Interoperability Standards.
Joint Health IT Committee Meeting Precision Medicine Task Force March 10, 2016 Leslie Kelly Hall, Co-Chair Andy Wiesenthal, Co-Chair.
Uses of the NIH Collaboratory Distributed Research Network Jeffrey Brown, PhD for the DRN Team Harvard Pilgrim Health Care Institute and Harvard Medical.
Task Force Meeting Precision Medicine Task Force April 13, 2016 Leslie Kelly Hall, Co-Chair Andy Wiesenthal, Co-Chair.
Office of the Secretary Office for Civil Rights (OCR) Enforcement and Policy Challenges in Health Information Privacy Linda Sanches HIPAA Summit Special.
DAF Phase 3-Data Access for Research Frequently Asked Questions DRAFT VERSION
Interoperability Measurement for the MACRA Section 106(b) ONC Briefing for HIT Policy and Standards Committee April 19, 2016.
HIT Policy Committee Health Information Exchange Workgroup Comments on Notice of Proposed Rule Making (NPRM) and Interim Final Rule (IFR) Deven McGraw,
Copyright © 2009 by The McGraw-Hill Companies, Inc. All Rights Reserved. McGraw-Hill/Irwin Chapter 2 Clinical Information Standards – Unit 3 seminar Electronic.
Joint Health IT Committee Meeting Precision Medicine Initiative Update March 10, 2016 P. Jon White, MD, Deputy National Coordinator for Health IT.
Open Platforms for Innovation
FDA Sentinel Initiative
Presentation transcript:

Health IT Standards Committee Work Product Health IT Standards Committee A Public Advisory Body on Health Information Technology to the National Coordinator for Health IT Precision Medicine Task Force Leslie Kelly Hall, co-chair Andy Wiesenthal, co-chair May 17, 2016

Health IT Standards Committee Work Product Agenda Welcome, Opening Remarks Task Force Background and Charge Considerations Critical Pathways to Interoperability Recommendations Discussion 2

Health IT Standards Committee Work Product Precision Medicine Task Force Members 3 MemberOrganization Co-ChairsLeslie Kelly HallHealthwise Andrew M. WiesenthalDeloitte Consulting, LLP MembersGil AlterovitzHarvard Medical School Dixie BakerMartin, Blanck, and Associates Mary BartonNational Committee for Quality Assurance (NCQA) Stanley CrosleyMember, Drinker Biddle & Reath LLP Steven KeatingMIT Media Lab and Mechanical Engineering David McCallie, Jr.Cerner Corporation Matthew MightHarvard University Andrey OstrovskyCare at Hand Ketan ParanjapeIntel Eric RoseIntelligent Medical Objects Joyce SensmeierHealthcare Information and Management Systems Society Federal Ex OfficioJames BreelingVeterans Health Administration (VHA) Teresa Zayas CabanONC Christina HeideHHS / Office for Civil Rights Betsy HumphreysNational Library of Medicine (NLM) Terry RauchDepartment of Defense Mitra RoccaFood and Drug Administration (FDA) Jon WhiteONC Maya UppaluruUnited States Digital Services (USDS)

Health IT Standards Committee Work Product ONC Role in Precision Medicine Initiative Accelerate opportunities for innovative collaboration around pilots and testing of standards that support health IT interoperability for research Adopt policies and standards to support privacy and security of cohort participant data Advance standards that support a participant-driven approach to patient data contribution 4

Health IT Standards Committee Work Product Task Force Charge Identify opportunities for ONC to support our federal partners’ PMI efforts and related health IT/interoperability challenges, including National Cancer Institute, Food and Drug Administration, National Institutes of Health, and Department of Veterans Affairs. Identify opportunities for ONC to collaborate with industry and pilot the use of standards to enable data donation and patient access through APIs using standards such as FHIR and OAuth 2.0. Identify standards for uses cases to support interoperability of data types that are critical to PMI-type research and prioritize piloting the exchange of those data types based on a phased approach, that would incorporate most structured/coded data first and add additional data types in subsequent pilot phases. 5

Health IT Standards Committee Work Product Precision Medicine Task Force Workplan 6 MeetingsTask Friday February 12, :00 AM-11:00 AM Progress and status of current initiatives NCI – PMI-Oncology FDA – Precision FDA needs to harmonize data standards Friday February 26, :00 PM - 2:30 PM ONC – Computable Consent NIH – Precision Medicine Initiative Progress & Sync for Science pilots Recap and discussion of issues to explore from other agencies Wednesday March 16, :00 PM-2:30 PM Department of Veterans Affairs (VA) Department of Defense (DoD) Wednesday March 30, :00 PM-2:30 PM Findings and preliminary recommendations Gaps in interoperability use cases - lab data, patient and provider access Wednesday April 13, :00 PM-2:30 PM Discuss draft recommendations Tuesday April 19, :30 AM to 3:00 PM Joint HIT Committee Meeting Draft Recommendations to Joint Committee Thursday April 21, :00 PM-2:30 PM Task Force Meeting to Finalize Recommendations Wednesday, May 11, :00 PM - 2:30 PM Task Force Meeting to Finalize Recommendations  Tuesday, May 17, :30 AM - 3:00 PM Joint HIT Committee Meeting Final Recommendations to Joint Committee

Health IT Standards Committee Work Product Interoperability Pathways Critical to PMI Overarching Questions What data sources are available? What are the known gaps regarding high value data needed for PMI? What efforts could be accelerated to help the work of PMI? Are there areas for which standards could be recommended to promote scalable and repeatable development for PMI? 7

Health IT Standards Committee Work Product Interoperability Pathways Critical to PMI Considerations Volume, complexity and new sources of data will necessitate emphasis on access and query based exchange versus the actual transfer of large datasets »Data volume will be beyond that of current EHR ecosystem »PMI data requires consideration of new data sources which bring complexity –Data for care directly from the patient –Genomic and other data from research platforms (e.g., NIH Cohort), laboratories and disease registries –PCORnet and others device data as well PMI (e.g., genetic) data remain uniquely valid over time, therefore, data validity and availability must be persistent over time 8

Health IT Standards Committee Work Product Interoperability Pathways Critical to PMI Considerations Data standards should be interoperable by design to accelerate timelines »Requires use of existing standards »Acceleration and coordination of some standards initiatives to support PMI »Acceleration of access patient generated health data (PGHD) »Interoperable design should be informed by ONC’s Interoperability Roadmap, NIH guidance, and others development and procurement 9

Health IT Standards Committee Work Product Three Interoperability Pathways Critical to PMI as Discussed by the Task Force 10 HPO’s EHR (labs, meds, etc.) Individual’s EHR Patient Portal (e.g., labs, meds) and PGHD Individual’s App Focus on EHR data first (e.g., labs, meds) 1 NIH PMI Cohort Enable data gathering from other independent non-provider sources NIH PMI Cohort Labs, PBMs, Claims Retail Pharmacies 2 NIH PMI Cohort ProviderPatient Accelerate ability to return an individual participant’s aggregated data from multiple sources, and eventually research results 3 HPO, Patients, Other Sources

Health IT Standards Committee Work Product Recommendations Recommendations fell under three main categories A.Interoperability and Data Reciprocity B.Policy Considerations C.Standards and APIs 11

Health IT Standards Committee Work Product Recommendations A. Interoperability and Data Reciprocity (1 of 3) ONC should consider the following promote PMI: »Provide the ONC Interoperability Roadmap addendum for PMI »Engage stakeholders to accelerate –Definition of minimum data set and standards for PMI, PGHD and phenotypic data –Include vocabulary where gaps exist using existing standards and efforts »Provide ongoing guidance –Use Technical Expert Panel(s) (TEP) to enhance participant understanding of utilizing various data sources (e.g., validity overlap, provenance) –Roadmap of current efforts that support PMI (e.g., ONC Tech Lab) –Inform the research community on interoperability with EHRs and standards in general (non-regulatory is the bias of the Task Force) 12

Health IT Standards Committee Work Product Recommendations A. Interoperability and Data Reciprocity (2 of 3) PMI should consider high value, non-EHR data sources to promote completeness of longitudinal patient information PMI should encourage use of standard APIs (e.g., FHIR) to source data »Meds –History, lack dispensing, adherence data, complete lists of current meds, feedback on efficacy and effectiveness –Potential sources: PBMs, retail pharmacies and physician notes »Labs –Consider challenges in pulling data from commercial and hospital labs –Explore practical differences between lab data in the EHR vs. data directly from the labs to determine which set may have greater fidelity and value »Claims –Determine how claims data enhance understanding of the patient and the sources PMI should consider means of patient mediated data donation to reduce probabilistic matching 13

Health IT Standards Committee Work Product Recommendations A. Interoperability and Data Reciprocity (3 of 3) Individual participant’s access to their aggregated PMI data will promote participation, retention and engagement »Data return should offer dynamic, compelling visualizations to promote its use »Patients should have access to computable, raw genetic testing and sequencing data –These data are among the most potentially useful to patients in the long term »Patients will need provider support on the implications of their genetic data PMI should define near term means of access and accelerate individual access »Recommend that patient-facing portals that enable individuals to access all data types (e.g., labs, meds, genomics) »Portals should allow individuals to use apps and APIs based on existing, and emerging standards (e.g., FHIR) »Draw from stakeholders with relevant strengths and experiences (e.g., Open Humans, PatientsLikeMe, Open Notes) 14

Health IT Standards Committee Work Product Recommendations B. Policy Considerations (1 of 3) NIH should educate patients and providers of data access rights and uses »Access rights should be consistent with protected health information (PHI) access standards »Consider The Framework for Responsible Sharing of Genomic and Health- Related Data* in developing data exchange principles »Enrollment should include notification of the use of the patient NIH ID –To accommodate results return and future use cases based on Sync 4 Science recommendations, notification should be sent back to EHR with patient consent »NIH direct enrollment should include strong assurance and identify proofing –Equivalent to the current patient portals model –Use direct language –Employ Web Content Accessibility Guidelines (WCAG) accessibility and enrollment 15

Health IT Standards Committee Work Product Recommendations B. Policy Considerations (2 of 3) Gathering patient data from a variety of sources will have implications to: »Identity Matching – the Task Force recognizes that significant efforts are underway to support this necessary capability »Consent and Authorization –Inform patients of implications of identifiers used and consent regarding their use –Clarify in consent if it applies to copies of the data –Employ a consent framework that enables new and/or expansive consent as new data needs emerge –HHS Office of Civil Rights (OCR) should confirm if consent is required for a provider to receive access to NIH data when a covered entity enrolls a patient into the cohort »Data access rights –Should apply to genomic and phenotypic information –Use notification to patients and providers when data is harvested 16

Health IT Standards Committee Work Product Recommendations B. Policy Considerations (3 of 3) The Task Force recognizes that efforts are underway to address: »Access –Clarification of related policy that would facilitate patient data access and return of research results (e.g., CLIA, HIPAA) –Privacy and security implications of returning an individual’s aggregated data –Options related to types of data patients would like to access / receive »Liability and Consent –Liability issues of working with genomic data with respect to what a researcher is obligated to disclose back to the patient –Granularity of permissions –Patient notification / consent to ongoing, or further, use of data for research 17

Health IT Standards Committee Work Product Recommendations C. Standards and APIs (1 of 2) Data Formats »Participants should be constrained to using a specified EHR export format(s) »Data recipients may need to anticipate a certain level of effort to translate data »Consensus-based models can facilitate exchange, models to consider: –Data Access Framework (DAF) and Argonaut –PCORnet, Sentinel, NCI Cloud Pilots and Cancer Genomic Data Commons, Observational Health Data Sciences and Informatics (OHDSI) –Veterans Administration mapping to (OHDSI) Individual Data »For data donation and return to patient use consistent FHIR-based APIs (e.g., Sync 4 Science, Argonaut, SMART) »New FHIR resources may not be needed immediately; an extension of existing resources may help (e.g., existing MU CDEs) »FHIR will become more necessary as it continues to evolve 18

Health IT Standards Committee Work Product Recommendations C. Standards and APIs (2 of 2) Data Sources »HPO enrollment on patients’ behalf should include PGHD when possible –Patients will act as an exchange mechanism among their providers and as a data source for data not captured in EHRs –Promote standardization for use of PGHD (e.g., Genetic Alliance) especially in enrollment –Recognize that standards are evolving »EHRs source for: –Episodic and demographic information, labs, meds, histories, etc. –Common Clinical Data Set minimum bar Standards based app and API implementation is recommended to: »Enable patients to connect to EHRs with apps and APIs »Enable patient to mediate exchange of the data (e.g., via CDS) to NIH cohort »Provide ability for reciprocal queries from EHR for patient specific aggregate requests of PGHD 19

Health IT Standards Committee Work Product Appendix: Parking Lot Issues 20

Health IT Standards Committee Work Product Parking Lot Items for Future Potential Task Force Work Demographic data »Recommendations to improve structured data around race, ethnicity, gender, sexual orientation? »What are the highest priority demographic data types for PMI? Define specific activities or pilots ONC could lead to support and advance progress Patient rights and ownership of genomic pattern data Record locator services and identity management »This work will be executed by the Coordinating Center awardee Genomic data (not for short-term consideration) 21