Connecting for Health Common Framework for Health Information Exchange

  • Upload
    kasen

  • View
    40

  • Download
    0

Embed Size (px)

DESCRIPTION

Connecting for Health Common Framework for Health Information Exchange Networked Personal Health Information. Carol C Diamond MD MPH Markle Foundation HIPAA Summit August 20, 2008. Establishing TRUST and INNOVATION in HEALTHCARE. Code, HIPAA and Fear - PowerPoint PPT Presentation

Citation preview

  • *Connecting for Health Common FrameworkforHealth Information ExchangeNetworked Personal Health InformationCarol C Diamond MD MPHMarkle Foundation

    HIPAA SummitAugust 20, 2008

  • Establishing TRUST and INNOVATION in HEALTHCARE

    Code, HIPAA and Fear

    21st Century Attributes of Trust

  • The Current Paradigm

    CodeFear HIPAA

  • What do we know from public opinion surveys and focus groups?Fear

  • Overall six out of ten Americans say they would favor the creation of a secure online personal health record service for their own use.

  • Now let's imagine that a new secure online service was made available to you allowing you to locate your medical records and view them through your own secure online "personal health record" account. Now I am going to read you some things this secure online "personal health record" service would allow you to do after I read each item, please tell me, yes or no, whether or not you would use this secure online "personal health record" service for each activity.There is also a strong interest among consumers in using health information technology to more fully participate in their own health care.

    Statement% YesCheck for mistakes in your medical record.Check and fill prescriptions.Get results over the Internet.Conduct secure and private email communication with your doctor or doctors.

  • But California Health Care Foundation (2005)67% of Americans are concerned about the privacyof their personal medical records--recent privacy breaches have raised their level of concern1 in 8 Americans have put their health at riskby engaging in privacy-protective behavior: - Avoiding their regular doctor - Asking a doctor to alter a diagnosis - Paying privately for a test - Avoiding tests altogether

    Harris/Westin poll on EHRs and Privacy (2006)42% of Americans feel that privacy risks outweigh expected benefits from health IT.

  • I am going to read you different attributes that could be part of this exchange or network and I would like you to rate the importance of each. As you respond, please keep in mind that not every attribute can be a top priority.Keeping electronic medical information private and secure remains chief among consumer concerns.

    Statement% Absolute Top PriorityThe identity of anyone using the system would be carefully confirmed to prevent any unauthorized access or any cases of mistaken identity. An individual would be able to review who has had access to their personal health information.Only with an individuals permission could their medical information be shared through this network.Employers would NOT have access to the secure health information exchange networks.

  • Americans recognize the upside and the downsideFear of misuses52% believe employer uses medical info to affect personnel or insurance benefits (CHCF Survey 2005)85% believe if genetic test results known to insurers, would refuse policies or charge more (Genetics and Public Policy Center Survey 2007)Three-quarters of Americans are willing to share their personal information to help public officials look for disease outbreaks and research ways to improve the quality of health care if they have safeguards to protect their identity (Markle Survey 2006).

  • Markle Survey November 2006

    3/4 want the government to set rules to protect the privacy and confidentiality of electronic health information

    2/3 want the government to set rulescontrolling the secondary uses of information

  • Organizational ImpactWhat do we know about variation in compliance?Fear

  • HISPC: Sources of Variations in Business PracticesVariation related to misunderstandings and differing applications of HIPAAVariation related to state privacy laws, scattered and often conflicting and antiquatedLack of trust in applied information securityCultural and business issues, concern about liability for incidental or inappropriate disclosures and general resistance to changeVariations due to uncertainty and doubt

  • Federal efforts have been dominated by standards and certification Technical design choices have profound policy effects (Code is Law, Architecture is Policy)Privacy debates and policy making have been reactive instead of pro-active (guiding technical design)Lack of policy guidance has the potential to undermine trust

    Paradigm Shift: Technology and policy need to be developed togetherCODE

  • HIPAA (Health Insurance Portability and Accountability Act 1996)

    Solving 20th Century Challenges

    Disclosure, consentCovered entity paradigm De-identification (18 identifiers) HIPAA

  • ChallengeDisclosure vs. Collection and Use of Personal Health Information Consent paradigms do not alone provide for protection of the consumer, rather it can burden them unfairly (consent to what? and what are the protections when consented?)What is personally identifiable is blurring, making re-identification easierCovered entity paradigm no longer worksLack of robust enforcement

    Paradigm Shift: Need a 21st Century approachHIPAA

  • How has the privacy landscape been changed by the Web?

    Health 2.0

  • Networks empower businesses and people to share information *TravelGPSOnline shoppingMobile PhoneATM

  • But not so much in health and health care Changes in other sectors rely on a fresh openness toward consumer access to and contribution of information.

    Yet, health care today is not networked.

    Consumers go through the system one data silo at a time.

    And much of the important information remains on paper or in the consumers head.

  • *Consumer Access ServicesHealth PlanDoctors OfficeRetail PharmacyMillie Using PHRConsumer Usinga Different PHR Blood Pressure DeviceHospitalPBMMobile PhoneMillies AppsGlobal Internet BrandsProvidersHealth InsurersEmployers RHIOsOthers21st Century ConsumerHealth Care Institutions

  • The power of networks depend on trust *TravelGPSOnline shoppingMobile PhoneATM

  • Changing the Current ParadigmFocus on a 21st Century Trust paradigm that Integrates policy AND technologyGoes beyond piecemeal approaches (focus on collection, use and information handling)Provides a strategic frame that limits risk

    Through a common framework of attributes in which policies can be focused on preventing misuse, empowering individuals and enabling a virtuous cycle of information to shape policy and innovation

  • 21st Century Trust AttributesA 21st Century health information environment that fosters trust must:

    Protect individual privacy through a set of policies that implement the core principles of fair information practice Incorporate technical tools that facilitate trusted use: audit, access, authorization, authentication and accuracyPromote technological choices that limit the potential for abuse (such as considering distributed architectures and separating demographic from clinical information)Focus on interoperability as to allow for flexible, yet sustainable, platforms of innovation and diversity of applications

  • and trust (particularly in health care) depends on Core Privacy PrinciplesSound Network DesignOversight and AccountabilityConsumerAccess ServicesDoctors OfficeMillies Apps*Health PlanPharmacies & PBMsHospitalHospital System(Aggregator)Claims Warehouse

  • *Core Privacy PrinciplesTrust through sound information policy expectations

    Nine core privacy principles are based on Fair Information Practices in the United States, Canada, and the EU

    The principles speak to:Transparency Specification of purpose and limitations on data collections and uses Consumer access, participation and control Data quality and security safeguards Accountability and remedies

    The principles are fulfilled through policy and technology

    The principles must be taken together as a comprehensive approach to privacy

  • OpennessPurpose SpecificationCollection LimitationUse LimitationIndividual Participation and ControlRemediesAccountabilitySecurity Data IntegrityP1: The Privacy Principles are Interdependent!

  • *Core Privacy PrinciplesSound Network DesignTrust through extensible, practical network design

    The Internet is the network

    The NHIN is not a new network, but rather a way of using the existing Internet for private and secure health information exchange based on a set of common policies and practices

    Open standards should support many applications

    Information need not be centralized in order to be shared

    Data should stay where captured, and shared as needed

  • 21st Century Technical Principles Make it ThinAvoid Rip and ReplaceSeparate Applications from the NetworkDecentralizationFederationFlexibilityPrivacy and SecurityAccuracy

  • *Core Privacy PrinciplesSound Network DesignOversight and AccountabilityTrust through governance and other enforcement mechanismsA policy framework is only effective if subject to mechanisms that enforce it.

    These mechanisms should empower innovations and experimentation within clear policies.

    Some uses of HIT will lend themselves to contractual enforcement within the parameters of existing state and federal laws and others will require a combination of mechanisms to establish adequate oversight and accountability.

    The governance model should anticipate future participants who may collect, transport or otherwise use patient data

  • *Core Privacy PrinciplesSound Network DesignOversight and AccountabilityConnecting for Health: A Public-Private Collaborative

  • *The First Detailed, Consensus-Based Framework for Networking Personal Health Records

    Endorsed by

  • * Consumers should be able to collect, store, manage, and share copies of personal health information.

    The Common Framework is based on fair information practices and focuses on network rules, not application standards.

    The purpose of the Connecting for Health Common Framework is embodied in Millie.

    Her character illustrates the needs of millions of U.S. adults who could benefit from greater connectivity in health and health care.

  • *Millie could manage her health the way she can manage her finances or travel.

    Download and upload critical health information Track her vital numbers Order prescription refills Get lab results Connect to professionals and communities of patients

    Consumers can help transform the health sector, as they have in other sectors.

    Networked PHRs are a vital tool for consumer empowerment.

    But to have an environment of trust, some basic rules should guide the emerging industry.

  • * Obtaining the consumers consent is a critical fair information practice. However, consent by itself does not adequately protect people. A complete framework of protections is necessary, no matter the I agree statement. Specific, independent consent is advisable for practices that would be unexpected by a reasonable consumer.Millie would understand and exercise meaningful choices about her information. She would be asked specifically about uses and disclosures of her personal health information.

  • * Contracts are one mechanism to bind parties to policies. Chain-of-trust agreements should disallow unauthorized uses of information. There are limitations to chain-of-trust agreements, including inconsistent enforcement and scaling difficulties.The organizations that touch Millie's health information would be Contractually bound to handle the information according to specified policies. For example, the policies would disallow business partners from assembling unauthorized profiles about Millie.

  • * There should be policies to notify affected consumers in the event of a potentially harmful breach of information.If Millie's information or identity becomes compromised because of a mistake, data leak, or fraud, Millie would be notified about it in a timely way. She would be told what she can do, and what others will do, to limit any harm.

  • * There should be mechanisms to resolve disputes such as breach or misuse, data quality or matching errors, allegations of unfair or deceptive trade practices, etc.If Millie has a problem with a service, or finds an error about her information, she would be able to easily figure out the process for resolving it.

  • * Some new services will co-mingle information from professionals and consumers. It is important to disallow discrimination based on information in PHRs or similar consumer tools. Participating organizations should take a strong stand against compelled disclosures (i.e., when consumers must allow organizations access to personal information in their PHR as a condition of employment, benefits, or other critical services.)Millie wouldn't lose her job, insurance, or other benefits because of information about her on the network. She also wouldn't be forced to allow insurers or employers to see her information in order to get a job or benefits.

  • *Millie's health information moves many places, in lots of different bits and bytes.

    Each organization touching information about her has different roles and plays by somewhat different rules. Health data streams are enormously complex, resulting in copies of information being held at many different points. Information can be combined to build revealing profiles of individuals. As consumers become network participants, new consumer data streams are being created. Consumers need better tools and assurances that their information will be handled according to fair information practices.

  • *Millie would be able to see who has accessed her accounts and the information in them. It would all be tracked, and accessible to her anytime.PHRs and supporting services should maintain an easy-to-comprehend, user-accessible, and clearly labeled electronic audit trail containing immutable entries that pertain to the consumers account, data, and policy consent.

  • *

    Connecting for Health PrincipleCommon Framework Resource1. Openness and transparency:CP2: Policy Notice to Consumers

    2. Purpose specification:CP2: Policy Notice to ConsumersCP3: Consumer Consent to Collections, Uses, and Disclosures of InformationCT4: Limitations on Identifying Information

    3. Collection limitation and data minimization:CP2: Policy Notice to ConsumersCP3: Consumer Consent to Collections, Uses, and Disclosures of InformationCT4: Limitations on Identifying Information

  • *

    Connecting for Health PrincipleCommon Framework Resource4. Use limitation:CP2:Policy Notice to ConsumersCP3: Consumer Consent to Collections, Uses, and Disclosures of InformationCP7: Discrimination and Compelled DisclosuresCT3: Immutable Audit TrailsCT4: Limitations on Identifying Information

    5. Individual participation and control:CP3:Consumer Consent to Collections, Uses, and Disclosures of InformationCP5: Notification of Misuse or BreachCP7: Discrimination and Compelled DisclosuresCP8: Consumer Obtainment and Control of InformationCT3: Immutable Audit TrailsCT5: Portability of Information

  • *

    Connecting for Health PrincipleCommon Framework Resource6. Data quality and integrity: CP6:Dispute ResolutionCP8: Consumer Obtainment and Control of InformationCT2: Authentication of ConsumersCT3: Immutable Audit Trails

    7. Security safeguards and controls:CP5:Notification of Misuse or BreachCT2: Authentication of ConsumersCT4: Limitations on Identifying InformationCT6: Security and Systems RequirementsCT7: An Architecture for Consumer Participation

  • *

    Connecting for Health PrincipleCommon Framework Resource8. Accountability and oversight:CP4: Chain-of-Trust AgreementsCP5:Notification of Misuse or BreachCP6: Dispute ResolutionCP9: Enforcement of PoliciesCT3: Immutable Audit Trails

    9. Remedies:CP5:Notification of Misuse or BreachCP6: Dispute ResolutionCP9: Enforcement of Policies

  • *When taken together, the practices enhance participation and protect personal health information

  • What Markle Set Out to Explore10%15%14%5%9%Many surveys since 2005 have explored Electronic Health Records (EHR) systems and privacy issues involved

    But major services now unfolding for individuals to create, store, and process their health information online, apart from EHR organizational systems

    These PHRs being offered by major health insurers (e.g. Aetna), employers (Dossia), HMOs, and Internet companies (Microsoft, Google, Revolution Health, WebMD, Intuit, etc.)

    Some under HIPAA (if by covered entity), but others not

  • Survey Methodology10%15%14%5%9%Questionnaire developed by Josh Lemieux and Alan Westin, with Markle staff input

    Sample creation, fieldwork and data production by Knowledge Networks

    1,580 respondents, representative of total adult (18+) population, both on and not on the Net

    Responses collected by special online process, May 13-22, 2008

    Knowledge Networks places error rate at +/- 2.5%

    Estimates of millions represented by results based on Current Population Survey estimate of adult US population at 228M

  • Markle Survey: Key Findings Four in 5 believe that online PHRs would be beneficial in managing their health and health care. Nearly half the public expresses some interest in using one.Among those not interested, concern for privacy is the most frequently cited reason why.Majorities of 87 percent to 92 percent say six key privacy practices are factors in their decision to use an online PHR.More than 90 percent said their express agreement should be required for each use of their online health information.More than 75 percent said each of four possible policy enforcement mechanisms would be effective.

    *

  • *For more information:

    www.connectingforhealth.org

    *I am delighted to be here I like the focus of the meeting and the NSF program on achieving trust, instead of solely privacy Clearly, informational privacy is a foundational component that must be addressed in other to establish trust Yet, and in health care especially, privacy is often defined narrowly meaning opt-in/opt-out I dont believe that revisiting the opt-in debate will contribute toward establishing a trusted environment that will accelerate innovation and subsequently better health Instead of focusing directly on privacy, I would like to engage in answering the question on how we can establish trust AND innovation in health care. In particular, I will argue that the current environment is undermining trust as it is characterized by a prioritization on code (or technological decisions), a struggle to make HIPAA relevant to a 21st Century and fear in the eyes of both new and traditional players not sure on how their business model (if any) will survive (with all kinds of potential impacts on their stance and behavior toward privacy). The absence of trust has been confirmed through numerous surveys However we can establish a trusted environment if we develop a new paradigm based upon a set of attributes that guide both technologists and policy makers on how to design a new health delivery system, using innovative tools. *As indicated, we are currently confronted with an environment where code, HIPAA and fear meet undermining trust among the public and health professionals.******Let me start by the current prioritization of technological design or code to accelerate the use of Health IT. Am sure that you all have heard of the various efforts by the federal, state and local actors, both public and private, to develop some kind of a health information infrastructure that would allow for personal health information to be exchanged. One of the crucial barriers toward such an infrastructure involves interoperability. As such, and for good reason, a drive toward standardization (and often certification) has been orchestrated. Unfortunately, much of these initial efforts toward interoperability have now been replaced by certification efforts to assure certain functionswhile the policy guidance that is necessary to make sure that technology serves protects rights and values has been lacking. For once, given the expertise of this group, I dont have to explain into depth that technical design choices have profound policy effects. Lessigs law is code, and Mitch Kapors Architecture is politics is well known to this group. It is clear that purportedly technologically-neutral decisions have far broader ramifications. Indeed, in an important sense, standards and certifications can be seen as a form of regulation, affecting, among other things, the competitiveness of markets, the usability of software and other technologies, the emergence of dominant industry players, intellectual property rights, and various public interest goals such as access, privacy, usability, and cost. The dilemma is that these various strategic ends may not always be compatible with each other. In particular, public interest values may be at odds with some of the other goals promoted by industry (profitability) or government (public health). The choices made with regard to standards, then, will need to guided by policies that try to balance these competing interests. Unfortunately, current policy making, toward privacy and other public interests, have been reactive instead of pro-active. As such, the absence of any meaningful policy framework is undermining trust, as it fails to inform technological design choices that have profound impact on how personal health information is collected, stored, shared and used. My first axiom toward establishing a new paradigm is therefore that technology and policy need to be developed in sync. ******Refer to P1: The Architecture for Privacy in a Networked Health Information Environment for a full discussion of the privacy principles and their implementation in a networked health information environment.

    *Make it ThinThe it is the Common Framework. It should be as minimal as possibleonly defining those things that must be uniform on a nationwide basis. Leave local systems to handle local questions on their ownthis allows flexibility and innovation at the edges of the network.

    Avoid Rip and Replace Build on the existing healthcare system and the existing Internet. They should evolve, but we dont need to replace them.

    Separate Applications from the Network In the Connecting for Health model, the network (sometimes called the NHIN, the HIN, etc.) is based on the existing Internet. It allows information to flow among authorized parties. The network must be designed to support a wide range of applications, which should receive data from the network in standard formats and display or interpret it.

    Decentralization Clinical data should stay under the control of healthcare providers who have a direct relationship with the patient. This arrangement helps to protect privacy and also enhances the quality of data by assuring that data is associated with its original source.

    Federation The Connecting for Health model assumes that most participants who share health information will be part of communities or, as we call them, Sub Network Organizations/SNOsany group of affiliated organizations, which may or may not be regionally-based (eg the VA, RxHub). Members of a SNO need to have agreements among themselves regarding health information exchange in order to build trust and clarify protocols. This is a federated model (as opposed to a centralized one).

    Flexibility Any hardware or software can be used as long as it conforms to the Common Framework.

    Privacy and Security Health information sharing requires an environment of trusttrust depends in part on the establishment of and conformance with policies that determine who can access a patients private information and under what circumstances. Youll hear more about this in the policy presentation by Janlori Goldman.

    Accuracy Accuracy is important both in identifying patients and finding their medical records. Its better to risk not finding all of the records that pertain to a particular patient than to associate the wrong record with someone.Openness and transparency: Consumers should be able to know what information has been collected about them, the purpose of its use, who can access and use it, and where it resides. They should also be informed about how they may obtain access to information collected about them and how they may control who has access to it.

    2. Purpose specification: The purposes for which personal data are collected should be specified at the time of collection, and the subsequent use should be limited to those purposes, or others that are specified on each occasion of change of purpose.

    3. Collection limitation and data minimization: Personal health information should only be collected for specified purposes and should be obtained by lawful and fair means. The collection and storage of personal health data should be limited to that information necessary to carry out the specified purpose. Where possible, consumers should have the knowledge of or provide consent for collection of their personal health information.

    *4. Use limitation: Personal data should not be disclosed, made available, or otherwise used for purposes other than those specified.

    5. Individual participation and control: Consumers should be able to control access to their personal information. They should know who is storing what information on them, and how that information is being used. They should also be able to review the way their information is being used or stored.

    *Data quality and integrity: All personal data collected should be relevant to the purposes for which they are to be used and should be accurate, complete, and up-to-date.

    7. Security safeguards and controls: Reasonable safeguards should protect personal data against such risks as loss or unauthorized access, use, destruction, modification, or disclosure.

    *8. Accountability and oversight: Entities in control of personal health information must be held accountable for implementing these principles.

    9. Remedies: Remedies must exist to address security breaches or privacy violations.

    *