We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byErika Lyons
Modified over 2 years ago
Rationale for Independent Health Record Banks William A. Yasnoff, MD, PhD, FACMI Managing Partner, NHII Advisors William A. Yasnoff, MD, PhD, FACMI Managing Partner, NHII Advisors HIMSS Legislation & Regulation Teleconference October 6, 2006 © 2006 NH I I ADVISORS
2 2 © 2006 NH I I ADVISORS Complete Electronic Patient Information Stakeholder cooperation Financial Sustainability Public Trust Components of a Community Health Information Infrastructure
3 3 © 2006 NH I I ADVISORS Complete Electronic Patient Information n Most information is already electronic: Labs, Medications, Images, Hospital Records n Outpatient records are mostly paper l Only 10-15% of physicians have EHRs l Business case for outpatient EHRs weak n For outpatient information to be electronic, need financial incentives to ensure that physicians acquire and use EHRs n Requirement #1: Financial incentives to create good business case for outpatient EHRs
4 4 © 2006 NH I I ADVISORS Complete Electronic Patient Information n Need single access point for electronic information n Option 1: Gather data when needed (scattered model) l Pro: 1) data stays in current location; 2) no duplication of storage l Con: 1) all systems must be available for query 24/7/365; 2) each system incurs added costs of queries (initial & ongoing); 3) slow response time; 4) searching not practical; 5) huge interoperability challenge (entire U.S.); 6) records only complete if every possible data source is operational
5 5 © 2006 NH I I ADVISORS Complete Electronic Patient Information n Need single access point for electronic information n Option 2: Central repository l Pro: fast response time, no interoperability between communities, easy searching, reliability depends only on central system, security can be controlled in one location, completeness of record assured, low cost l Con: public trust challenging, duplicate storage (but storage is inexpensive)
6 6 © 2006 NH I I ADVISORS Complete Electronic Patient Information n Need single access point for electronic information n Requirement #2: Central repository for storage
7 7 © 2006 NH I I ADVISORS n Voluntary Impractical n Financial incentives l Where find $$$$$? n Mandates l New Impractical l Existing – HIPAA requires information to be provided on patient request n Requirement #3: Patients must request their own information Stakeholder cooperation
8 8 © 2006 NH I I ADVISORS n Funding options l Government – Federal: unlikely – State: unlikely – Startup funds at best l Healthcare Stakeholders – Paid for giving care – New investments or transaction costs difficult l Payers/Purchasers – Skeptical about benefits – Free rider/first mover effects l Consumers – 72% support electronic records – 52% willing to pay >=$5/month n Requirement #4: Solution must appeal to consumers so they will pay Financial Sustainability
9 9 © 2006 NH I I ADVISORS A.Public Trust = Patient Control of Information n Requirement #5: Patients must control all access to their information Public Trust
10 © 2006 NH I I ADVISORS B.Trusted Institution Via regulation (like banks) impractical Self-regulated Community-owned non-profit Board with all key stakeholders Independent privacy oversight Open & transparent Requirement #6: Governing institution must be self-regulating community- owned non-profit Public Trust
11 © 2006 NH I I ADVISORS C.Trustworthy Technical Architecture Prevent large-scale information loss Searchable database offline Carefully screen all employees Prevent inappropriate access to individual records State-of-the-art computer security Strong authentication No searching capability Secure operating system Easier to secure central repository: efforts focus on one place Requirement #7: Technical architecture must prevent information loss and misuse Public Trust
12 © 2006 NH I I ADVISORS Health Record Banking Model n All information for a patient stored in Health Record Bank (HRB) account n Patient (or designee) controls all access to account information [copies of original records held elsewhere] n Each HRB has three interfaces: l Withdrawal window - record access l Deposit window - receives new info l Search window - authorized requests n When care received, new records sent to HRB for deposit in patient’s account n All data sources contribute at patient request (per HIPAA) n All information for a patient stored in Health Record Bank (HRB) account n Patient (or designee) controls all access to account information [copies of original records held elsewhere] n Each HRB has three interfaces: l Withdrawal window - record access l Deposit window - receives new info l Search window - authorized requests n When care received, new records sent to HRB for deposit in patient’s account n All data sources contribute at patient request (per HIPAA)
13 © 2006 NH I I ADVISORS Clinical Encounter Health Record Bank Clinician EHR System Encounter Data Entered in EHR Encounter data sent to Health Record Bank Patient Permission? NO DATA NOT SENT Clinician Inquiry Patient data delivered to Clinician YES Optional payment Clinician’s Bank Secure patient health data files Health Record Banking
14 © 2006 NH I I ADVISORS Questions? William A. Yasnoff, MD, PhD, FACMI firstname.lastname@example.org 703/527-5678 For more information: www.healthbanking.org www.yasnoff.com
Health Information Infrastructure: What, Why, and How William A. Yasnoff, MD, PhD, FACMI Managing Partner, NHII Advisors William A. Yasnoff, MD, PhD, FACMI.
A New Patient-centric and Sustainable Path to Achieving Health Information Infrastructure William A. Yasnoff, MD, PhD, FACMI Managing Partner, NHII Advisors.
Health Record Banks Enable Secondary Data Use with Privacy Protection William A. Yasnoff, MD, PhD, FACMI CEO, Health Record Banking Alliance William A.
A Feasible Path to Sustainable Community Health Information Infrastructure William A. Yasnoff, MD, PhD, FACMI CEO, Health Record Banking Association William.
Health Information Technology: Where are the Opportunities? William A. Yasnoff, MD, PhD, FACMI Managing Partner, NHII Advisors Healthcare in 2009 New York,
How to Develop a Sustainable Community Health Information Infrastructure William A. Yasnoff, MD, PhD, FACMI Managing Partner, NHII Advisors Founder and.
Health Record Banks: A Financially Sustainable Model for Health Information Exchange William A. Yasnoff, MD, PhD, FACMI Managing Partner, NHII Advisors.
Health Record Banks: Sustainable Health Information Infrastructure AND Privacy William A. Yasnoff, MD, PhD, FACMI Managing Partner, NHII Advisors World.
A Paradigm Shift for Sharing Health Information: the Health and Prevention Promotion Initiative (HAPPI) William A. Yasnoff, MD, PhD, FACMI Managing Partner,
Averting the Collision: Privacy Doctrine & Health Information Exchange Katherine L. Ball, MD, MSc William A. Yasnoff, MD, PhD, FACMI e-Health Initiative.
Edward H. Shortliffe, MD, PhD Chairman, Advisory Board Health Record Banking Alliance (HRBA) Panel on Privacy - III Defragmenting.
Introduction to Health Record Banks William A. Yasnoff, MD, PhD, FACMIHarvard University. Cambridge, MA. October 15, 2012.
Developing National Health Information Infrastructure (NHII) in the U.S. William A. Yasnoff, MD, PhD, FACMI Senior Advisor National Health Information.
1 Virtua’s goals for PHR technologies Create tools and processes that: Encourage patients to be engaged with their healthcare Provide tools for caregivers.
Software Certification for Electronic Health Records: The Certification Commission for Healthcare Information Technology (CCHIT) James J. Cimino, M.D.
1 Washington State Health Care Authority Richard Onizuka, PhD, Executive Sponsor Health Record Bank Project Washington State Health Record Bank Pilot Project.
National Health Information Infrastructure (NHII) William A. Yasnoff, MD, PhD, FACMI Senior Advisor National Health Information Infrastructure Department.
Indiana Health Information Exchange 12/16/041 RHIO Case Study J. Marc Overhage, MD, PhD, FACP, FACMI President and CEO, Indiana Health Information Exchange.
Brian E. Dixon, MPA, PhD Candidate Health IT Project Manager Regenstrief Institute, Inc. Bi-Directional Communication Enhancing Situational Awareness in.
10/08/20041 © 2004 Pete Palmer Federated Identity Management and Regional Health Information Organizations Pete Palmer, Principal Security Analyst, Guidant.
The National Perspective: National Health Information Infrastructure (NHII): Key to the Future of Health Care Helga E. Rippen, MD, PhD, MPH Deputy Senior.
The Use of Health Information Technology in Physician Practices
Component 4: Introduction to Information and Computer Science Unit 2: Internet and the World Wide Web 1 Component 4/Unit 2Health IT Workforce Curriculum.
Hurdles and Solutions for the Interoperable EHR John W, Loonsk, MD FACMI Chief Medical Officer CGI.
7927 Jones Branch Drive, Suite 3150 ● McLean, VA P: ● F: ● “The Advocate for Northern Virginia Physicians”
The New Jersey Health Information Technology Act NJ HITC and Office for e-HIT by June 2010 must Deliver Report and make Recommendations to Governor and.
Presented by: Presented by: Tim Cameron CommIT Project Manager, Internet 2 CommIT Project Update.
CHAPTER © 2011 The McGraw-Hill Companies, Inc. All rights reserved. 2 The Use of Health Information Technology in Physician Practices.
IT in Healthcare IT Careers in Healthcare Emerging opportunities for IT professionals Prof. Vance Wilson Arizona State University.
The U. S. Health Care System Challenges, Opportunities and Solutions Fifth National HIPAA Summit Clinical Data Standards and the Creation of an Interconnected,
Copyright © 2011 Delmar, Cengage Learning. ALL RIGHTS RESERVED. Chapter 5 Electronic Health Records.
Missouri Public Service Commission Electronic Filing & Information System a Case Study for Business Process Management Todd Craig, CIO Missouri Public.
West Virginia Information Technology Summit November 4, 2009.
Jeanene Smith MD, MPH Office for Oregon Health Policy and Research SCI Coverage Institute - July, 2009 Albuquerque, NM Building a Healthy Oregon: Delivery.
Santa Barbara County Care Data Exchange June 22, 2004 Sam Karp, Director Health Information Technology California HealthCare Foundation NHII 2004 Cornerstones.
National Health Policy Conference February 4, 2008 Washington State Health Reform Efforts Richard K. Onizuka, PhD Health Policy Director.
Health Information Technology and Puerto Rico Juan Eugenio Rodríguez de Hostos Chief Information Officer, Government of Puerto Rico Dr. José Piovanetti.
AHCCCS/ASU Clinical Data Project March 17 th, 2009 Arizona Health Care Cost Containment Health System Medicaid Transformation Grant Program.
September, 2005Cardio - June 2007 IHE for Regional Health Information Networks Cardiology Uses.
The state of regional health information (RHIOs) : Health data exchange on the Rise Student : Laura Lin Teacher : Mr. Ma Number : M Date : 3 / 12.
Meaningful Use The Catalyst for Connected Health Sameer Bade Strategic Product Planner.
History of Health Information Technology in the U.S. The HITECH Act Lecture b – Meaningful Use, Health Information Exchange and Research This material.
Minnesota Law and Health Information Exchange Oversight Activities James I. Golden, PhD State Government Health IT Coordinator Director, Health Policy.
1 Networked PHR, a framework for personal health applications & services Anne Chapman, Senior Program Manager Personal Health Records, Intel.
Centers for Disease Control and Prevention Office of the Associate Director for Communication Electronic Health Records/Meaningful Use and Public Health.
The Promise and Peril of Electronic Health Records Cari Weishaar Final Project 12/8/11.
© 2016 Chapter 6 Data Management Health Information Management Technology: An Applied Approach.
The University of Kansas Medical Center Shadow Experience Training.
Forms Management: Compliance, Security & Workflow Efficiencies.
© 2017 SlidePlayer.com Inc. All rights reserved.