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

Slides:



Advertisements
Similar presentations
Georgia Department of Community Health
Advertisements

National HIT Agenda and HIE John W. Loonsk, M.D. Director of Interoperability and Standards Office of the National Coordinator Department of Health.
Office of Science & Technology Update April 17, 2013 Doug Fridsma, MD, PhD, FACP, FACMI Chief Science Officer & Director, Office of Science & Technology.
HIT Steering Committee 6/20/2102 Doug Fridsma, MD, PhD, FACMI Chief Science Officer Director, Office of Science & Technology.
Office of Science & Technology
Electronic Submission of Medical Documentation (esMD) Face to Face Informational Session esMD Requirements, Priorities and Potential Workgroups – 2:00pm.
OST Update HIT Standards Committee July 17, 2013 Doug Fridsma, MD, PhD, FACP, FACMI Chief Science Officer & Director, Office of Science & Technology.
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.
Timeline & Milestones: Certification & Standards NPRM Stage 2 Health IT Standards Committee, March 29, 2011 Doug Fridsma, MD, PhD Director Office of Interoperability.
Direct Implementation Perspective 0 Mark Bamberg, Vice President Research & Development MEDfx.
2015 Edition Proposed Rule Modifications to the ONC Health IT Certification Program and 2015 Edition Health IT Certification Criteria.
Texas Approach to Supporting Statewide Health Information Exchange January 2013.
Query Health Technical WG 9/14/2011. Agenda TopicTime Allocation Administrative Stuff and Reminders11:05 – 11:10 am Summer Concert Series Patterns Discussion11:10.
Centers for Disease Control and Prevention Office of the Associate Director for Communication Electronic Health Records/Meaningful Use and Public Health.
A Primer on Healthcare Information Exchange John D. Halamka MD CIO, Harvard Medical School and Beth Israel Deaconess Medical Center.
NextGen Interoperability – Leading the Charge Presenter – David Venier DISCLAIMER: The views and opinions expressed in this presentation are those of the.
S&I Framework Doug Fridsma, MD, PhD Director, Office of Standards and Interoperability, ONC Fall 2011 Face-to-Face.
Electronic Submission of Medical Documentation (esMD) Face to Face Informational Session Charter Discussion – 9:30am – 10:00am October 18, 2011.
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.
S&I Framework Operating Metrics Timing Outputs Participation & Process Framework Launch DateJan 7, 2011 First Initiative Launch DateJan 31, 2011 Elapsed.
Collaborative Direct-- Status Update December 6, 2013 Don Jorgenson Inpriva, Inc.
Achieving Interoperability Doug Fridsma, MD, PhD, FACMI Director, Office of Standards & Interoperability, ONC 1.
Data Gathering HITPC Workplan HITPC Request for Comments HITSC Committee Recommendations gathered by ONC HITSC Workgroup Chairs ONC Meaningful Use Stage.
Transport & Security Standards Workgroup Notice of Proposed Rulemaking Comments Dixie Baker, Chair Lisa Gallagher, Co-Chair May 15, 2015.
Automate Blue Button Initiative Push Workgroup Meeting January 7, 2013.
ONC Program Update Health IT Policy Committee Meeting January 8, 2013 Jodi Daniel, Office of Policy and Planning, ONC Doug Fridsma, Office of Science and.
Automate Blue Button Initiative All Hands Community Meeting August 29, 2012.
HITSC Workplan: April Update April 17, 2013 Doug Fridsma, MD, PhD, FACP, FACMI Chief Science Officer & Director, Office of Science & Technology.
HIT Standards Committee HIT Standards Committee Privacy and Security Workgroup Discussion of NwHIN Power Team Recommendations August 6,
EsMD PPA Use Case 1 Harmonization WG Meeting Wednesday, March 28 th, 2012.
Automate Blue Button Initiative Push Workgroup Meeting December 17, 2012.
Data Access Framework All Hands Community Meeting January 15, 2014.
NCVHS and the Standards, Implementation Specifications and Operating Rules for Claim Attachments Walter G. Suarez, MD, MPH Director, Health IT Strategy.
1 Collaboration and Concept Exploration Nationwide Health Information Organization (NHIO) Gateway March 28, 2007.
Data Gathering HITPC Workplan HITPC Request for Comments HITSC Committee Recommendations gathered by ONC HITSC Workgroup Chairs ONC Meaningful Use Stage.
Automate Blue Button Initiative Content Workgroup Meeting November 19, 2012.
Utilizing the CMS Security Risk Assessment Tool Liz Hansen, PCMH CEC, ICD-10 PMC Special Consultant, GA-HITEC Member Manager, GaHIN
EsMD PPA Use Case 2 WG Meeting Wednesday, March 21 st, 2012.
HIT Policy Committee NHIN Workgroup Recommendations Phase 2 David Lansky, Chair Pacific Business Group on Health Danny Weitzner, Co-Chair Department of.
Automate Blue Button Initiative Pull Workgroup Meeting November 20, 2012.
Direct Project Update Arien Malec. First Production Usage Immunization data from Hennepin County Medical Center to Minnesota Department of Health via.
Blue Button Plus Push Workgroup Meeting April 22, 2013.
The Year of Implementation and Value Creation!Global Gaming Expo 2006 Good Things Happen When We All Pull Together The World of Transport.
Automate Blue Button Initiative Pull Workgroup Meeting September 25, 2012.
HITSC 2013 Workplan Dr. Doug Fridsma Chief Science Officer and Director, Office of Science and Technology Office of the National Coordinator for Health.
Automate Blue Button Initiative Push Workgroup Meeting November 26, 2012.
HIPAA Transactions Testing Update Kepa Zubeldia, M.D. September 13, 2004.
Larry Wolf Certification / Adoption Workgroup May 13th, 2014.
Health eDecisions Use Case 2: CDS Guidance Service Strawman of Core Concepts Use Case 2 1.
S&I Public Health * We will start the meeting 3 min after the hour July 22, 2014.
Health Delivery Services May 29, Eastern Massachusetts Healthcare Initiative Policy Work Group Session 2 May 29, 2009.
HIT Standards Committee Overview and Progress Report March 17, 2010.
OST Update Health IT Policy Committee March 14, 2013 Doug Fridsma, MD, PhD, FACP, FACMI Chief Science Officer & Director, Office of Science & Technology.
The Patient Choice Project Project Kickoff December 14 th, 2015.
Justin Richer The MITRE Corporation October 8, 2014 Overview of OAuth 2.0 and Blue Button + REST.
Electronic Submission of Medical Documentation (esMD)
EsMD PPA Use Case 2 WG Meeting Wednesday, April 4 th, 2012.
Discussion - HITSC / HITPC Joint Meeting Transport & Security Standards Workgroup October 22, 2014.
Automate Blue Button Initiative Push Workgroup Meeting November 19, 2012.
Primary Goal: To support case detection and investigation for the reportable infectious diseases (conditions) using electronic information exchanges between.
Framing Identity Management Recommendations Transport & Security Standards Workgroup November 19, 2014.
Data Gathering HITPC Workplan HITPC Request for Comments HITSC Committee Recommendations gathered by ONC HITSC Workgroup Chairs ONC Meaningful Use Stage.
Automate Blue Button Initiative Push Workgroup Meeting November 12, 2012.
Health IT Standards Committee Update December 19, 2012 Doug Fridsma, MD, PhD, FACP, FACMI Chief Science Officer & Director, Office of Science & Technology.
S&I Framework Update HIT Standards Committee June 10, 2013 Doug Fridsma, MD, PhD, FACP, FACMI Chief Science Officer & Director, Office of Science & Technology.
Automate Blue Button Initiative Pull Workgroup Meeting December 13, 2012.
Pennsylvania Health Information Exchange NJHIMSS - DVHIMSS Enabling Healthcare Transformation Through Information Technology September, 2010.
FHIR BULK DATA API April 2018
Biosurveillance and the National Health IT Agenda
ONC Update for HITSP Board
Presentation transcript:

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

S&I Initiative Portfolio Snapshot Transitions of Care Provider Directories Query Health Pre-DiscoveryUse CaseHarmonizationRI, Test & PilotEvaluation Lab Results Interface Data Segmentation for Privacy esMD Longitudinal Coordination of Care Public Health Reporting Laboratory Orders Interface Direct Project (S&I Archetype) Health eDecisions Automate Blue Button (ABBI)

Automate Blue Button Initiative (ABBI) Status update November 13, 2012

Blue Button Background Two years ago, the VA added a simple, easy to recognize “Blue Button” to their patient portal. Since then, the use of Blue Button has grown into a movement – a commitment by many of the country’s largest data holders, including the Federal government – to get personal health information out of proprietary silos and into the hands of the consumers who want a holistic picture of their health and health care. Several hundreds of thousands of veterans, members of the military, and Medicare beneficiaries have already downloaded their data through Blue Button. VA CMS Department of Defense Aetna United + Many more 4 #ABBI

Today, Blue Button means letting consumers download an ASCII file of their personal health information after they log onto the dataholder’s portal. For example: Blue Button: How It Works Today 5

ABBI Scope Identify, define, and harmonize implementation standards, tools and services that facilitate the automated PUSH and automated PULL of patient information via the Blue Button Identify, define and harmonize content structures and specifications for the Blue Button so that information downloaded is machine readable and human readable Identify, define, and harmonize protocols around identification and credentialing, and protocols around access and authorization, that facilitate the automated PUSH and automated PULL of patient information via the Blue Button 6 #ABBI

PUSH Project Scope 7 Automating transmission of personal health data to a specific location By patient request, a provider can specify in an EHR that a patient be sent an updated copy of his/her personal health information as it becomes available A patient can specify in a dataholder’s system to be sent an updated copy of his/her personal health information as it becomes available. PUSH EXAMPLE USE CASES REQUIREMENTS & ASSUMPTIONS IN SCOPE (TO BE CONSIDERED) OUT OF SCOPE (NOT TO BE CONSIDERED) Patient/Provider is already authenticated in dataholder’s system. Transport must be secure Data sent must be both human-readable and machine-readable Patient/Provider is already authenticated in dataholder’s system. Transport must be secure Data sent must be both human-readable and machine-readable Transport standards, services, and specifications Content standards: whether or not to include in implementation guide(s) Implementation guide(s) to support use case(s), building off existing standards Transport standards, services, and specifications Content standards: whether or not to include in implementation guide(s) Implementation guide(s) to support use case(s), building off existing standards Policy concerns and constraints. This initiative will define the mechanism, – how and where they apply it will be up to state and local laws #ABBI

PULL Project Scope 8 Allowing a third party application to periodically access my personal health data PULL EXAMPLE USE CASE A patient can direct a third party application to periodically have access to his/her personal health information via the internet. The dataholder will ensure this data is made available and follow certain privacy and security standards. REQUIREMENTS & ASSUMPTIONS IN SCOPE (TO BE CONSIDERED) OUT OF SCOPE (NOT TO BE CONSIDERED) Data must be transmitted securely Patient must give application consent to pull health information from data holder Data sent must be both human-readable and machine-readable Data must be transmitted securely Patient must give application consent to pull health information from data holder Data sent must be both human-readable and machine-readable Authentication, transport, and content standards. Leverage REHx project (Oauth and OpenID) Leverage ToC project Leverage lab interface project Authentication, transport, and content standards. Leverage REHx project (Oauth and OpenID) Leverage ToC project Leverage lab interface project Policy concerns and constraints. This initiative will define the mechanism, – how and where they apply it will be up to state and local laws #ABBI

Blue Button v2: Deliverables 1. Reference Implementations V/D/T + Automation Showcase PULL demonstrations Etc. 2. Technical Implementation Guides Direct Pull 3. Workflow Guides Payers Providers 4. Policy FAQ Guidance 5. CCD/ C-CDA Style Sheet Library 6. Blue Button Brand Guidance: V1 vs. V/D/T vs. V2 #1) By March: 5+ Implementations of Blue Button v2 #2) By March: Implementation Guide on Blue Button v2 #3) By June: Developer Response to Blue Button v2 About How ToCommitImplementation Examples Policy Guidance Brand Guidelines ChallengesDatapalooza Theme Examples of New Products #4) By Aug: Pilots of Blue Button v2 ProvidersPayersEHR Vendors Workstreams 9

Questions/Discussion Learn more at: ONC website: S&I Framework wiki: Questions/Discussion 10