<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Patsy Bailin on Medium]]></title>
        <description><![CDATA[Stories by Patsy Bailin on Medium]]></description>
        <link>https://medium.com/@patsy_10890?source=rss-d17646ee3754------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*okvHnWdE51V5lUGgmsi56Q.jpeg</url>
            <title>Stories by Patsy Bailin on Medium</title>
            <link>https://medium.com/@patsy_10890?source=rss-d17646ee3754------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 21:07:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@patsy_10890/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Datavant’s Comments to CMS on Patient Matching]]></title>
            <link>https://medium.com/datavant/datavants-comments-to-cms-on-patient-matching-53670c5af6d?source=rss-d17646ee3754------2</link>
            <guid isPermaLink="false">https://medium.com/p/53670c5af6d</guid>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[patient-engagement]]></category>
            <category><![CDATA[healthcare]]></category>
            <dc:creator><![CDATA[Patsy Bailin]]></dc:creator>
            <pubDate>Tue, 04 Jun 2019 16:40:28 GMT</pubDate>
            <atom:updated>2019-06-04T16:40:28.879Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Datavant is a health data technology company focused on facilitating the exchange of patient information in a privacy-preserving way. Our software de-identifies patient health data and provides a secure method of linking patient records across disparate datasets without compromising individual privacy. Datavant’s de-identification and linking software is installed at over 120 sites and serves as the foundation for an ethical data exchange network that serves clients across the healthcare industry.</em></p><p>Datavant submitted these comments on patient matching in response to the proposed rule to advance interoperability and patient access to health information (<a href="https://www.cms.gov/Center/Special-Topic/Interoperability/CMS-9115-P.pdf">CMS-9115-P</a>) drafted by the Centers for Medicare &amp; Medicaid Services (CMS).</p><p>***</p><p>Datavant greatly appreciates CMS’s interest in the issue of patient matching. As CMS is aware, research has shown that a large amount of patient information gets unnecessarily misattributed, lost, or disclosed as a result of inaccurate matching of health records. This has significant implications not only for individual patient care and privacy but also for public health research and analytics. Patient matching processes that rely on identifiable information are of course critical for interoperability, portability, and patient access; however, we contend that the challenge of patient matching is even more confounding in a de-identified setting, where record elements are obfuscated or removed altogether. Despite this challenge, patient matching in the de-identified context is necessary to support clinical research, population health studies, and treatment development — all of which serve to improve patient outcomes and advance the quality of our healthcare system.</p><p>Given Datavant’s core competency in privacy-preserving patient matching, we have scoped our response specifically to address CMS’s request for comment on the topic, namely: 1) the privacy and security considerations of patient matching process versus unique patient identifiers (UPIs); 2) recommendations for CMS to promote private sector patient matching strategies; and 3) suggestions for ways in which CMS can leverage its authority to support improvements in patient matching.</p><p>***</p><p><strong>Privacy &amp; Security Considerations for Patient Matching</strong></p><p>It is Datavant’s experience that patient matching processes, if built and managed responsibly, can serve the same purpose as UPIs — accurately linking disparate records for the same patient — at substantially lower risk to the patient’s privacy and the security of the data. This is because a UPI is inherently a fixed state method, meaning the same patient identifier must persist across the healthcare ecosystem, leaving it vulnerable to compromise. A patient matching process, however, can take a myriad of formats ranging from stateless or real-time matching to matching based on de-identified and multiple representations of an individual patient. In other words, patient matching processes optimize for consistently accurate matching, while at the same time mitigating the patient privacy and security risks that would otherwise arise out of persisting a UPI across disparate patient records.</p><p>We would like to note, however, that patient matching processes are more complex than UPIs and will consequently require greater attention to transparency standards, particularly with respect to the information used to generate a match. Also worth noting is that patient matching processes could perpetuate unintentionally incorrect matches, which could pose a risk to patient privacy and security for different reasons than a UPI. Patient matching processes, like UPIs, are also not immune to fraud and should not be considered a replacement or substitute for identity verification services.</p><p><strong>Facilitation of Private Sector Patient Matching Strategies</strong></p><p>Datavant encourages CMS to consider pursuing or continuing its work on the following initiatives:</p><ul><li>Supporting the creation of standards for acceptable patient matching algorithms and solutions</li><li>Supporting the creation of a validation program for evaluating patient matching solutions against the criteria established in those standards</li><li>Ensuring that the records generated by CMS-funded/related programs contain at least all of the minimum demographic elements deemed necessary for patient matching. In addition to ensuring that datasets are “matchable”, this policy would have the added benefit of ensuring that CMS programs are well positioned to make use of patient matching solutions.</li><li>Encouraging through financial support and internal policy the use of patient matching solutions for CMS-funded/related programs</li></ul><p><strong>Leveraging CMS Program Authority to Support Improvements in Patient Matching</strong></p><p>We answer each of CMS’s specific questions on how the agency can use its authority to support improvements in patient matching below.</p><p><em>Should CMS require Medicare FFS, MA Plans, Medicaid FFS, Medicaid managed care plans (MCOs, PIHPs, and PAHPs), CHIP FFS, CHIP managed care entities, and QHP issuers in FFEs (not including SADP issuers), use a patient matching algorithm with a proven success rate of a certain percentage where the algorithm and real world processes associated with the algorithm used are validated by HHS or a 3rd party?</em></p><p>Datavant supports a CMS requirement that any patient algorithms used by its programs be validated against a standard metric. CMS could also assist in various capacities with the development of that standard evaluation metric.</p><p>However, CMS should not mandate that its programs use the same algorithm. It would be most beneficial for the continued improvement of patient matching that experimentation, research, and innovation in matching algorithms be given the space and opportunity to excel.</p><p><em>Should CMS require Medicare FFS, the MA Plans, Medicaid FFS, Medicaid managed care plans, CHIP FFS, CHIP managed care entities, and QHP issuers in FFEs to use a particular patient matching software solution with a proven success rate of a certain percentage validated by HHS or a 3rd party?</em></p><p>CMS runs the risk of supporting market fragmentation and perpetuating propriety barriers to interoperability if it requires its programs to use a particular software solution. Not only should CMS programs be able to use a solution that is best suited to their needs, but a single CMS-mandated solution entrenches a single algorithm and technology provider in the market — to the likely detriment of innovation and data portability. Effective patient matching software solutions should be able to work with each other, and an open market encourages them to do so.</p><p>Datavant does agree, however, that CMS should develop a program to validate patient matching software and should require that its programs only use software solutions that have been validated. This would establish a common framework against which private sector solutions can gauge “success”. It would also ensure both that a standard baseline exists for patient matching and that all CMS programs are using software that meets those standards.</p><p><em>Should CMS expand the recent Medicare ID card efforts by requiring a CMS-wide identifier which is used for all beneficiaries and enrollees in health care programs under CMS administration and authority?</em></p><p>While the extension of a CMS-wide identifier would help improve patient matching for programs under CMS’s administration, it would not support patient matching across the larger healthcare ecosystem. In addition, a CMS-wide identifier is more similar to a UPI than a patient matching process and would increase patient privacy and security risks that might otherwise be mitigated if the alternative — a patient matching process — is used instead.</p><p><em>Should CMS advance more standardized data elements across all appropriate programs for matching purposes?</em></p><p>Datavant encourages CMS to advance a standard set of data elements. One of the primary challenges for successful and accurate patient matching is inconsistency in available patient information. Standardizing the available elements for CMS programs would go a long way toward establishing record consistency for (and improving the accuracy of) patient matching because CMS programs produce the greatest share of patient records and would quickly set a standard for the healthcare ecosystem. Even if particular patient matching solutions chose to rely on different sets of fields for their matching algorithms, a common set of required elements improves the likelihood that data could be portable across solutions.</p><p>We believe patient matching is most effective when multiple elements are available for the matching process, and unsurprisingly, when elements are unique and/or stable. A standard set of elements should optimize for capturing one or more unique values across the standard set, since the combination of elements is likely to increases the probability of achieving a correct match due to its “uniqueness”. Uniqueness notably depends on a variety of factors, including the size of the patient pool (family, small local providers, state/regional providers, US patient population) and the element itself (gender versus email address). The most valuable elements are the ones that do not or are not likely to change, such as a government issued identifier or birthdate.</p><p>A second challenge for patient matching is that fields with the same name may not lead to the same values for the same patient, either because the values are represented in a different metric or the field does not have a standard format. Without consistency in the defined format for a standard field, patient matching could lead to poor quality matches even if the matching algorithm is strong.</p><p>Once CMS has advanced a standard set of elements, Datavant would also like to encourage CMS to mandate that all standard elements be present in a record to the extent they are available for a patient. Standardizing the elements will only be effective if the standard is enforced.</p><p><em>To what extent should patient-generated data complement patient matching efforts?</em></p><p>Patient-generated data can be enormously valuable for patient matching, in large part because patients are best-equipped to provide accurate and comprehensive information. Patients should be encouraged to help identify incorrect records or incorrectly matched records and should be encouraged to provide the information necessary to complete or correct their health records.</p><p>As mentioned previously, patient matching processes can be complex, and every effort should be made to provide patients with transparency into the process. Datavant strongly believes that CMS should support initiatives to facilitate patient access to the information used in a matching process. Such access and awareness would: 1) lead to greater consumer comfort and familiarity with the process that might otherwise be unexpected or unsettling to patients; and 2) impose a social oversight function on businesses to act ethically and responsibly with the patient matching process and the underlying data that feeds it.</p><p>***</p><p>Datavant wholly supports CMS’s interest in patient matching as a method of increasing interoperability and access to health information, and we are in favor of CMS’s effort to promote standardization of demographic data and benchmarking of matching accuracy and scalability.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=53670c5af6d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/datavant/datavants-comments-to-cms-on-patient-matching-53670c5af6d">Datavant’s Comments to CMS on Patient Matching</a> was originally published in <a href="https://medium.com/datavant">Datavant</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Executive Summary: Evolution of Health Data Regulation]]></title>
            <link>https://medium.com/datavant/executive-summary-evolution-of-health-data-regulation-faa5fbb4dc3c?source=rss-d17646ee3754------2</link>
            <guid isPermaLink="false">https://medium.com/p/faa5fbb4dc3c</guid>
            <category><![CDATA[healthcare]]></category>
            <category><![CDATA[data-sharing]]></category>
            <category><![CDATA[hipaa]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[policy]]></category>
            <dc:creator><![CDATA[Patsy Bailin]]></dc:creator>
            <pubDate>Mon, 01 Apr 2019 23:38:39 GMT</pubDate>
            <atom:updated>2019-04-08T18:27:01.568Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*FoupmHvK9pvzD4dTxnS-rA.png" /></figure><p>The news today is full of discussions about data privacy and data protection legislation, with diverse views from policymakers, advocacy groups, and industry. For healthcare leaders, it can be challenging to keep track of what applies to your data, what changes are worth following, and how the final legislation could impact you and your company.</p><p>Here’s what you need to know.</p><h3><strong>How health information is regulated in the United States today</strong></h3><p><strong><em>The sensitivity of health information makes it one of the few categories of information that is already federally protected by law. These are the three laws to know.</em></strong></p><p><strong>Health Insurance Portability &amp; Accountability Act (HIPAA)</strong></p><p>Enacted in 1996, HIPAA is the primary healthcare law in the U.S. It was amended in 1999 to cover the protection of individual health information (or PHI). These rules remain the industry’s “north star” for the collection, use, exchange, and protection of patient information.</p><p>Although HIPAA covers only a small portion of the healthcare industry, it has become the standard for both the right of patients to access their information and the business obligation to protect sensitive health data. Though the laws do place restrictions on the use of PHI, they were written to support the exchange of patient information, outlining how data can be legally and securely exchanged.</p><p>HIPAA is a floor, not a ceiling. It does not preempt laws that create stricter requirements for PHI, and other laws can augment its requirements.</p><p><strong>Health Information Technology for Economic and Clinical Health (HITECH)</strong></p><p>In 2009, Congress enacted the HITECH Act, which widened the scope of HIPAA’s data protection requirements, increased the legal liability for non-compliance, and strengthened the enforcement rights of the Office of Civil Rights (OCR, a division of HHS). The primary goal of HITECH was to accelerate the adoption of electronic health records (EHRs) and other health technologies, which were expected to improve individual patient care and public health outcomes. Broadening the data protection requirements in HIPAA was a way to mitigate the risks of EHRs and other technologies, which brought significant amounts of new medical information online.</p><p><strong>Genetic Information Nondiscrimination Act (GINA)</strong></p><p>GINA was enacted in 2008, as inexpensive clinical and direct-to-consumer genetic tests were entering the market. GINA prohibits employers from requiring or financially incentivizing employees to disclose their genetic information, their individual health information, or their family medical histories; it prohibits employers from disclosing employee health information or discriminating against an individual for employment or health insurance based on his or her genetic information or medical history. It also prohibits health insurance plans from using or disclosing genetic information for underwriting purposes.</p><p><strong><em>Federal agencies oversee the healthcare industry’s generation, collection, use, and sharing of health information. The Department of Health &amp; Human Services and the Federal Trade Commission are two primary enforcement agencies for the health industry.</em></strong></p><p><strong>The Department of Health &amp; Human Services (HHS)</strong></p><p>HHS has enforcement authority for HIPAA and HITECH. The agency sets the regulatory agenda for the healthcare industry and — among many other things — funds initiatives to improve industry standards, technology, and accountability for the management of patient health information. HHS’s responsibility for patient information was reinforced in 2016 with the passage of the 21st Century Cures Act. Among other things, the Act called on HHS to better define interoperability and prohibit “information blocking”; it also modified the requirements around informed consent for certain types of clinical research and modified the FDA’s drug approval process to permit the use of “real world evidence” in FDA submissions under certain conditions. With respect to health information, the two parts of HHS for health companies to be aware of are:</p><ul><li>The <em>Office of Civil Rights (OCR)</em>, an office within HHS, enforces HIPAA/HITECH; keeps track of breaches of protected health information; and manages investigations and resolutions of complaints or violations of HIPAA’s Privacy &amp; Security Rules.</li><li>The <em>Food &amp; Drug Administration (FDA)</em> oversees clinical research and trials for drugs, biologics, and medical devices. It also enforces industry standards, including the Common Rule (an ethics standard for the protection of human subjects in government-funded research that has become the de facto standard regardless of funding) and Good Clinical, Laboratory, and Manufacturing Practices (together, GxP), which are internationally recognized standards for drug development activities that require proper management of data, including the ethical collection, use, and disclosure of information from human subjects.</li></ul><p><strong>Federal Trade Commission (FTC)</strong></p><p>The FTC regulates the collection and use of consumer data in the private sector. While the FTC does not have enforcement authority over data regulated by HIPAA, it does cover the collection and use of consumer data by healthcare companies. The agency also regulates many companies that consumers would consider “health related” but that fall outside the scope of HHS oversight (e.g., health tracking apps, wearable fitness devices, direct-to-consumer genetic testing companies).</p><p>FTC’s authority to protect health information comes primarily from two sources:</p><ul><li><em>Section 5 of the FTC Act</em>, which gives the FTC the authority to protect consumers from corporate acts and practices that are unfair or deceptive. The agency has developed enforceable guidance around what constitutes “fair” data management practices and “reasonable” security safeguards for consumer information. The rules FTC has promulgated apply to health companies insofar as the types of consumer data they handle or the activities for which they employ it are not already covered by HIPAA.</li><li>The <em>Fair Credit Reporting Act (FCRA)</em> regulates the use of consumer information in credit, employment, and insurance eligibility decisions. Its requirements, which the FTC enforces, are intended to promote information accuracy and accessibility for consumers and to ensure that companies only use consumer data in fair and transparent ways. Health information is subject to the same rules as all other information collected and disclosed in a consumer’s report.</li></ul><p><strong><em>States have passed their own laws protecting health information, contributing to the “patchwork” of data protection laws in the United States.</em></strong></p><p>As previously noted, HIPAA sets a regulatory floor, and only applies to a subset of personal health information. States have stepped in to fill the gaps and, in some cases, establish stricter standards. The relevant state laws fall into three categories:</p><p><strong>Sector-specific state healthcare laws</strong></p><p>Every U.S. state and D.C. has enacted laws specific to the health industry. With varying degrees of specificity and severity, they contain safeguards for the privacy and confidentiality of health information by regulating the collection, use, and disclosure of patient health and biometric information.</p><p><strong>Data Breach Notification &amp; Identity Protection Laws</strong></p><p>All 50 states and D.C. have enacted security breach notification laws. Of those, 16 explicitly include health data or medical history (D.C. might pass an update that would bring the number to 17), and an additional 7 include biometric data or health insurance information. Regardless, every state includes name and social security number (or other government-issued ID number) as personal information subject to data breach notification requirements, which means all medical and insurance records are effectively covered by these laws. In fact, the majority of reported breaches, settlements, and fines at the state level are the result of unauthorized disclosures of healthcare provider records and health insurance information.</p><p><strong>Unfair or Deceptive Practices Statutes</strong></p><p>Every state and D.C. have enacted statutes to protect consumers against unfair or deceptive corporate practices. These laws are similar to the FTC’s Section 5 authority in that they apply to the privacy, security, and confidentiality of personal information, including health information not covered by HIPAA or a state health law. State consumer protection statutes usually grant enforcement authority to the state’s Attorney General, though in some instances consumers have a private right of action.</p><p><strong><em>Health companies self-regulate to varying degrees, creating and voluntarily adhering to standards and codes of conduct regarding the collection, use, and exchange of health information.</em></strong></p><p>There are numerous industry groups developing standards that apply to health data, and a variety of codes of conduct have been developed for the management and protection of health data. Some, like the National Institute of Standards &amp; Technology (NIST) de-identification guidelines and its privacy framework (currently under development), are cross-industry best practices. HITRUST is a private organization that conducts corporate audits to certify that organizations are employing appropriate technical, administrative, and physical safeguards to protect health data in compliance with HIPAA. Meanwhile, groups like the CARIN Alliance and the Future of Privacy Forum develop codes of conduct with member support that codify best practices for specific activities to standardize behavior across the industry.</p><h3><strong>Here’s what’s coming</strong></h3><p><strong><em>The idea of federal privacy regulation for the protection of personal information is hardly new, but the number of proposals currently on the docket in Congress is unprecedented.</em></strong></p><p>To date, 8 federal privacy bills have been introduced in Congress. Each proposal addresses similar legal concepts, but the degree of variation suggests consensus is lacking. This is especially true with respect to higher-stakes questions like preemption.</p><p>Here are the key trends:</p><ul><li>Legislation is moving toward broadly scoping its coverage to capture more data types, including health data</li><li>Proposals use a combination of a consumer rights model (promote consumer control) and a consumer protection model (enforce corporate behavior)</li><li>Rulemaking and enforcement authority is granted to the FTC</li><li>Proposals are encouraging data minimization</li></ul><p>The federal privacy legislation debate has drawn industry and advocacy groups, businesses, and individuals, some of whom have taken the opportunity to draft federal proposals of their own. Intel, for example, released its proposal in January 2019, the “Innovative &amp; Ethical Data Use Act”, with tremendous support from its industry peers; the Center for Democracy &amp; Technology published its proposal in December 2018, “Federal Baseline Privacy Legislation”, which has received much attention for its clarity and comprehensiveness.</p><p><strong><em>Numerous federal agencies have stepped into the data privacy debate, but the actions of HHS and FTC will have the greatest impact on the health industry.</em></strong></p><p><strong>Department of Health &amp; Human Services</strong></p><p>HHS has released rules and requested comments about revisions to HIPAA, improvements in coordinating healthcare for patients, and incentivizing interoperability through refreshed guidelines. Two recent examples:</p><ol><li>In December 2018, the Office of Civil Rights requested information on how HIPAA (and the Privacy Rule, in particular) could be modified to promote information sharing for coordinated and value-based care in a privacy-sensitive manner.</li><li>In February 2019, the Center for Medicare/Medicaid Services and the Office of the National Coordinator for Health Information Technology released proposed rules that would promote patient access to and control over their information.</li></ol><ul><li>The CMS proposal requires healthcare companies to implement technology that would support the seamless transition of health records as patients move between providers and plans; it also proposed to publicly report healthcare providers that engaged in “information blocking”.</li><li>ONC’s proposal promotes secure, free, and real-time access to health records through the adoption of standardized APIs, which would give patients the ability to see their information on apps and mobile devices. It also attempts to define activities that do not constitute “information blocking”.</li></ul><p><strong>The Federal Trade Commission</strong></p><p>The FTC has received numerous complaints about the disclosure of health and health-related information for advertising and risk scoring. In a complaint against Facebook, for example, a consumer advocacy association argued that the social media company misled consumers into sharing personal health information because its information use and disclosure policies were unclear.</p><p>Recently, there has been significant media attention on the lack of transparency around the collection of information from wellness and fitness tracking apps; as well as the use of health information in algorithm-based decision-making. All of these activities fall within the FTC’s scope to investigate, should it choose to do so.</p><p><strong><em>States have been more aggressive on privacy legislation than the federal government.</em></strong></p><p>A slew of states have already passed or are preparing to pass data protection laws, many of which will impact the health sector. This growing body of legislation creates inconsistencies across jurisdictions in terms of requirements and scope.</p><p>Broadly speaking, there are three categories of state laws:</p><p><strong>California Consumer Rights Model</strong></p><p>California passed the California Consumer Privacy Act (CCPA) in mid-2018. The law takes effect on January 1, 2020, and is the first consumer privacy law in the country. It establishes consumer rights over the data collected and used about them, and prescribes responsibilities and mechanisms for companies to honor those rights. Though it exempts consumer information protected by HIPAA and the state’s Confidentiality of Medical Information Act (CMIA), it covers other consumer data generated, used, and exchanged by the healthcare industry (e.g., online behavioral and interest data, social determinants of health, and direct-to-consumer health app, testing, and device data). A detailed analysis of the CCPA and its impact on the health industry can be found <a href="https://medium.com/datavant/what-the-ccpas-exemptions-really-mean-for-health-companies-cddc1246c517?source=collection_home---4------2---------------------">here</a>.</p><p>California has started a trend. Hawaii, New York, New Mexico, North Dakota, Maryland, Massachusetts, and Rhode Island have introduced similar consumer privacy legislation, despite the CCPA’s many ambiguities and conflicts, which have to be resolved before the law goes into effect.</p><p><strong>European Data Protection Model</strong></p><p>Washington is poised to pass data privacy legislation modeled after Europe’s General Data Protection Regulation (GDPR). The law would provide more comprehensive data rights to consumers than the CCPA and would enforce those rights through the regulation of corporate behavior.</p><p>The bill requires that companies provide consumers with notice about these rights and mechanisms to exercise them (the consumer rights model). But it also requires that companies be transparent about their data collection and use practices; that they conduct risk assessments of their data processing; that they monitor and pass on their compliance and contractual obligations, including with respect to de-identified data; and it places limits on the use of facial recognition technology (the corporate behavior model).</p><p>While the bill defines personal information broadly (“any information that is linked or linkable to an identified or identifiable natural person”), it exempts information that is already protected by some federal laws, including HIPAA.</p><p><strong>Sector-specific Model</strong></p><p>As previously noted, the U.S. has historically passed data privacy laws for specific sectors or data types, including the health industry and health data. Some states are continuing this model.</p><ul><li>Florida and New York are the most recent states to propose Biometric Information Privacy Acts (BIPAs), which are designed to protect data about a consumer’s biology, physiology, genetic, and olfactory information. Specific examples include DNA, fingerprints, facial imagery, and retina scans. BIPAs have come under pressure from companies developing or implementing facial-recognition software, voice and fingerprint identification technology, and other biometric-based services, but Florida and New York are following in the footsteps of Illinois (2008), Texas (2009), and Washington (2017). Meanwhile, BIPA proposals in Montana, New Hampshire, Alaska, and Delaware have been in committee for a year or more.</li><li>Oregon’s state legislature is considering the passage of the Health Information Property Act, which proposes that patient’s PHI should be the legal property of the patient. It would require that patients provide affirmative authorization before healthcare providers de-identify and sell their PHI; that consumers should have the option to receive payment in exchange for the authorization to sell their de-identified information; and that healthcare providers cannot discriminate against consumers who do not authorize the sale of their de-identified information. The group behind this bill is currently lobbying for similar laws in other states, including Arizona, California, Georgia, Hawaii, Maryland, Massachusetts, Montana, New Jersey, Pennsylvania, and Washington.</li></ul><h3><strong>Here’s how all of it is likely to shake out</strong></h3><p><strong><em>States will pass legislation quickly over the next year, which will impact companies in the health industry.</em></strong></p><p>Inconsistency in state requirements will lead to heavy operational costs, lower rates of compliance, and/or negative economic impacts as companies either retreat from some states or pass on costs to consumers. An important distinction for the health industry to watch is whether state laws include exemptions for health data covered by HIPAA or other state legislation. Hawaii’s data privacy bill, for example, has been introduced without an exemption for health data covered by other laws. State bills that do not have an exemption could create conflicts with existing state or federal laws.</p><p>As the private sector struggles to comply with various state privacy laws, pressure will mount for Congress to pass federal privacy legislation that includes explicit preemption of other privacy laws.</p><p><strong><em>HHS and the FTC will establish new guidelines with respect to the use of health data over the next two years.</em></strong></p><p>Before Congress manages to pass federal legislation, HHS and FTC will step in to increase protections for health data. HHS will promulgate rules to accelerate interoperability and portability initiatives, as well as data transparency rules to improve patient care and awareness. HHS will also push for revisions to the HIPAA privacy rule that will continue to protect patients while promoting more efficient data sharing.</p><p>Meanwhile, the FTC will increase enforcement of privacy violations through its Section 5 authority. The agency has already expressed concern over biases and discrimination in the use of data for algorithm-based decision-making, which is a new frontier in healthcare and application for health/health-related data and will likely introduce guidelines for the use of data in automated decisions and the permissible use of automated decisions in healthcare settings.</p><p><strong><em>On the back of state legislation, and HHS and FTC action, we will see federal data protection legislation in the next two years, which will set baseline requirements for all data types across all industries.</em></strong></p><p>Federal data protection legislation will take some time and will continue to be a high-visibility issue for the next two years. In whatever form it passes, the final legislation is likely to accomplish four things:</p><ul><li>It will be broader in scope than the traditional sector-specific approach to privacy, covering online data, financial data, social and demographic data, as well as health data.</li><li>The requirements for protected data under the new legislation will likely be equivalent, if not stricter, than the protections for PHI, which would lead to regulatory parity between PHI and other data types.</li><li>It will preempt state law and will provide similar protections to those offered by the strictest state laws.</li><li>The FTC’s enforcement rights will be strengthened.</li></ul><p>Bottom line: data protection requirements are changing quickly, but clear trends are emerging. While the health industry will be subject to the new requirements, the industry’s familiarity with data regulations gives it a head start to designing and implementing the data management operations necessary for compliance.</p><p><em>This piece is intended as a high-level overview. Subsequent pieces will cover pending federal and state legislation in additional detail. Thank you to Travis May and Bob Borek for their thoughts and edits on this piece.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=faa5fbb4dc3c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/datavant/executive-summary-evolution-of-health-data-regulation-faa5fbb4dc3c">Executive Summary: Evolution of Health Data Regulation</a> was originally published in <a href="https://medium.com/datavant">Datavant</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What the CCPA’s exemptions really mean for health companies]]></title>
            <link>https://medium.com/datavant/what-the-ccpas-exemptions-really-mean-for-health-companies-cddc1246c517?source=rss-d17646ee3754------2</link>
            <guid isPermaLink="false">https://medium.com/p/cddc1246c517</guid>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[privacy-law]]></category>
            <category><![CDATA[healthcare]]></category>
            <dc:creator><![CDATA[Patsy Bailin]]></dc:creator>
            <pubDate>Mon, 25 Feb 2019 17:36:13 GMT</pubDate>
            <atom:updated>2019-02-25T17:36:13.686Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Last year, California passed the </em><a href="https://leginfo.legislature.ca.gov/faces/billCompareClient.xhtml?bill_id=201720180AB375"><em>California Consumer Privacy Act (CCPA)</em></a><em>, which will go into effect in 2020. Widely seen as a “GDPR-light,” the law could have many implications on the healthcare industry, even though the law excludes certain types of health data. This article is an overview of some of the impacts.</em></p><p>The CCPA, which goes into effect in January 2020, requires businesses to support consumer’s (new!) information rights when their data is collected, used, and sold. The combination of its many prescriptive requirements with its broad definitions (for example, “personal information,” “collecting”, and “selling”) has significant operational implications for the businesses covered by the CCPA, which is why the question of applicability has been as heavily discussed as the law’s actual requirements.</p><p>Many health companies assume that the presence of health information exceptions in the CCPA are enough to exempt them from compliance. However, most of these companies have at least some data that falls squarely in the purview of the CCPA, and they should be prepared to implement compliance programs to manage it in accordance with the new rights granted to California consumers.</p><p>Specifically, health companies should ask themselves two questions:</p><ol><li>Does my organization meet the definition of a business under the law?</li><li>Does my organization have personal information that is not otherwise captured by the exemptions?</li></ol><p>If the answers to both of these are yes, then the organization will need to implement CCPA compliance mechanisms.</p><p>Here’s how to answer these questions and a few gray areas to watch out for.</p><p><strong>Establishing applicability for health organizations</strong></p><p>An organization under the CCPA is one that is:</p><ul><li>For-profit;</li><li>Operating in California;</li><li>Collecting personal information; and that</li><li>Satisfies one or more of the following: a) has annual gross revenues in excess of $25 million dollars, b) derives 50% or more of its annual revenues from selling personal information, and/or c) handles the personal information of 50,000 or more consumers, households, or devices.</li></ul><p>The definition covers a broad swath of the healthcare industry. Think healthcare providers and insurance companies, their business associates, health analytics companies, aggregators of health information for the secondary market, pharmaceutical companies, direct-to-consumer health resources (genetic testing, wearables, lifestyle apps, personal health record vendors), mental health and assisted living facilities, biotechnology companies. The list goes on. The few who aren’t covered include non-profit organizations, small start-up ventures, and any health organization that does not interact with California consumers.</p><p><strong>What health data is exempt</strong></p><p>CCPA explicitly does not apply to three types of health information:</p><ul><li>“Medical Information” already covered by the state’s Confidentiality of Medical Information Act (CMIA) is exempt from CCPA. Medical information as defined in the CMIA is identifiable information about a patient’s medical history or condition that is held by a healthcare provider, healthcare service plan, pharmaceutical company, or contractor. (Note that the definition of a contractor in the CMIA is narrower than the definition of a “business associate” in HIPAA, and is essentially a health-related organization that is not a service plan or provider.)</li><li>“Protected Health Information” (PHI) already covered by the Health Insurance Portability &amp; Accountability Act (HIPAA) is exempt from CCPA. PHI is defined in HIPAA as individually identifiable health information that is created or received by a HIPAA-covered entity, relates to the physical or mental health of an individual or the provision for or payment of health care to the individual, and either identifies the individual or could reasonably be used to identify the individual.</li><li>Information collected as part of a clinical trial that is already subject to the Common Rule, GCP guidelines, or FDA requirements, is also exempt from CCPA.</li></ul><p>CCPA also does not apply to aggregate consumer information or de-identified information.</p><ul><li>CCPA defines aggregate consumer information as information about a group or category of individuals that does not refer to or identify any specific individual, household, or device.</li><li>De-identified information is “information that cannot reasonably identify, relate to, describe, be capable of being associated with, or be linked, directly or indirectly, to a particular consumer”. In addition to the de-identification processing, the business must do all of the following: a) implement technical safeguards to prohibit re-identification of the consumer; b) implement business processes that prohibit re-identification and prevent inadvertent release of de-identified information; and c) make no attempt to re-identify the information.</li></ul><p>These exemptions create a safe harbor for much of the information health organizations collect, use, and share. This is true even for some unexpected organizations (think patient portals collating health records and pharmaceutical companies receiving clinical trial data). But remember that <em>the CCPA is framed around the protection of specific types of data, not specific types of companies</em>. This means that some information (we’ll call it “non-exempt information”) collected by organizations in the healthcare space is subject to CCPA’s compliance requirements regardless of the organization’s status as a covered or regulated entity under CMIA, HIPAA, or the FDA.</p><p><strong>What is<em> not</em> exempt</strong></p><p>Non-exempt information is a surprising amount of a health organization’s information. It includes marketing data, patient or customer service call center information, social media and app data, and data licensed from a third party. Health companies from payers to providers (the traditional HIPAA-covered entities), pharma companies to medical device manufacturers, and academic research institutions to direct-consumer-products retain information that is subject to CCPA compliance.</p><p>More specifically, non-protected information includes the email addresses, advertising identifiers (cookies and mobile device IDs), and IP addresses collected via the websites of every health-related organization. It includes, for example, the information collected on patients and consumers about their interests and concerns for marketing purposes, which health-related organizations use to improve their community initiatives, patient engagement, and the quality of their patient care. It also includes geolocation information, biometric information (an individual’s physiological, biological, or behavioral characteristics), consumer purchase behavior, and third party demographic information that is used by both healthcare and non-health organizations for everything from enhancing consumer experience and research to user authentication or fraud prevention.</p><p>Some companies look to the “research exemption” as their safe harbor. However, this only applies to personal information used for “public or peer-reviewed” research in the public interest. There’s a litany of specific requirements for what qualifies. The most significant of these additional requirements is that the personal information used for research may not be used for any commercial purpose.</p><p><strong>What may or may not be exempt</strong></p><p>For organizations in the health space, there are three gray areas related to non-exempt information worth highlighting:</p><p>1. <em>The definition of de-identified information in the CCPA and in HIPAA are not the same</em>. HIPAA has two approved methods of de-identification: Safe Harbor and Expert Determination, neither of which align perfectly with the CCPA’s requirements. Safe Harbor fits more easily into the CCPA’s definition, but most companies use the Expert Determination method. In either case, it is possible that adequately de-identified data under HIPAA (which is no longer PHI covered by CCPA’s PHI exemption) may not be adequately de-identified under CCPA, which has stricter additional requirements, and would consequently be subject to CCPA obligations.</p><p>2. <em>Due to ambiguous wording, there is some debate over how the CCPA’s exemption (b), which is directed at both health organizations and patient information more generally, should be interpreted.</em> The exclusion could be read to suggest either that “providers of healthcare” under the CMIA and “covered entities” under HIPAA are organizationally excluded or that any information these organizations have on patients is excluded as long as they maintain it in the same manner as medical information (CMIA) or PHI (HIPAA). Given the way the CCPA’s applicability is structured, it seems unlikely that it applies wholesale to the organization and instead applies to a covered entity’s treatment of non-protected patient information.</p><p>3. <em>There is also debate over whether the CCPA applies to employee data</em>. The definition of personal information expressly includes “professional or employment-related information”, which suggests that it will at minimum apply to applicant information but will likely be interpreted to apply to all employee data. In the act, a consumer is defined as a “natural person who is a California resident”, and the definition is not further qualified.</p><p><strong>Compliance requirements for non-exempt information</strong></p><p>Businesses subject to the CCPA’s requirements will need to update their compliance programs to ensure they are respecting the information rights of California consumers. Some of the requirements are more prescriptive than others (on the bright side, this means companies know exactly what they need to do!). At a high level, they include:</p><ul><li>Revising privacy policies, website homepages, consent forms, and consumer-facing notices to inform consumers of their rights, the types of personal information being collected, how the information will be used, and whether the information will be sold to third parties.</li><li>Creating mechanisms to receive and authenticate consumer requests for information; to opt out of the collection, use, or sale of their personal information; to access and correct their personal information; to delete their personal information; and to port their personal information to another organization.</li><li>Maintaining a data inventory to trace what information has been collected, retained, processed, disseminated, and sold about a person so that a report can be produced for the consumer.</li></ul><p><strong>Conclusion</strong></p><p>While it’s true that the CCPA was written with the online advertising and retail industries in mind, it doesn’t restrict itself to a particular industry or a particular type or use of data. It covers personal information quite broadly and carves out exceptions for particular types or uses of data that are already regulated. This approach creates areas of ambiguity, as well as cases where the new requirements do not sync with existing rules.</p><p>As part of a heavily regulated industry, healthcare organizations are no strangers to legislative ambiguity. We all hope the CCPA’s ambiguities will be resolved before it goes into effect next year. In the meantime, it’s not too late to begin addressing the compliance obligations that do apply.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cddc1246c517" width="1" height="1" alt=""><hr><p><a href="https://medium.com/datavant/what-the-ccpas-exemptions-really-mean-for-health-companies-cddc1246c517">What the CCPA’s exemptions really mean for health companies</a> was originally published in <a href="https://medium.com/datavant">Datavant</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Data access and connectivity are ethical requirements for the healthcare industry: commentary on…]]></title>
            <link>https://medium.com/datavant/data-access-and-connectivity-are-ethical-requirements-for-the-healthcare-industry-commentary-on-d6d6212419f1?source=rss-d17646ee3754------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6d6212419f1</guid>
            <category><![CDATA[data-ethics]]></category>
            <category><![CDATA[healthcare]]></category>
            <category><![CDATA[hipaa]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[health-technology]]></category>
            <dc:creator><![CDATA[Patsy Bailin]]></dc:creator>
            <pubDate>Wed, 16 Jan 2019 16:26:32 GMT</pubDate>
            <atom:updated>2019-01-16T16:26:32.543Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Data access and connectivity are ethical requirements for the healthcare industry: commentary on ONC’s 2018 Report to Congress</strong></h3><p>Since the passage of HITECH in 2009, the Office of the National Coordinator (or ONC, which is part of the Department of Health &amp; Human Services) has been tasked with driving adoption of a nationwide health IT infrastructure. This effort is core to the vision of HITECH: a common system for the secure and seamless flow of health data between patients, providers, payers, and research institutions. Such a system could improve the quality and provision of medical care at the level of both an individual patient and the greater population.</p><p>ONC’s recently released <a href="https://www.healthit.gov/sites/default/files/page/2018-12/2018-HITECH-report-to-congress.pdf">progress report</a> identifies some of the challenges to achieving this vision, but also reiterates the agency’s commitment to that vision and the value of success.</p><p>Since ONC’s first report to Congress in 2012, it has dutifully documented its efforts and the progress the healthcare industry has made in access, usability, and interoperability of information and information technology. This year’s report, which covers the period between November 2016 and August 2018, emphasizes widespread (albeit regionally unequal) adoption of health information technology among healthcare entities; however, it concludes that the greater “digital footprint” has not yet brought with it the innovation in data accessibility and usability that HITECH intended.</p><p>For any patient who has tried to access medical records or any researcher who has tried to obtain public health data, this is not unexpected news. ONC reports that there are three barriers to progress on the data accessibility front:</p><ul><li><em>Technical barriers</em>, which include the inability to match data across records and the absence of standardized data formats and taxonomies.</li><li><em>Financial barriers</em>, such as<strong> </strong>the high cost of developing, implementing, and learning new health technology, particularly as changing requirements lead to ongoing maintenance and upgrades.</li><li><em>Trust barriers</em>, which stem from the legal and business incentives that cause healthcare entities to restrict the flow of information for competitive advantage, or as a result of misguided interpretations of compliance requirements.</li></ul><p>All of these barriers keep data inaccessible even in its electronic format, and the cost of this inaccessibility is harmful to both patients and our public health systems. Connecting and accessing health data is essential if the healthcare system as a whole is going to deliver high quality and seamless care for patients. For this reason, the ONC has focused its efforts and resources over the last two years on addressing these barriers through public-private forums; guidance on design architecture and data standards; new rulemaking; project funding; pilot programs, developer challenges, and inter-agency initiatives.</p><p>However, the economic and social benefits of accessible data and interoperable health IT programs are not the only reason to support the ONC’s work. Access and connectivity are not just technical challenges or a thorny collective action problem. <em>They are fundamental ethical requirements for the healthcare industry:</em></p><ul><li>A patient should not have to suffer because his or her primary care physician cannot access data from a specialist’s electronic health record (EHR) system.</li><li>A clinical trial for an innovative therapy that could help chronically ill patients should not be delayed because the contract research organization (CRO) cannot find valuable demographic data to inform site selection and patient recruitment.</li><li>An insurer should not be foreclosed from applying the findings of their behavioral health research to reduce insurance costs for their consenting customers.</li></ul><p>I believe data ethics in healthcare is not simply about protecting patient privacy; <em>it’s also about respect for access, choice, and portability</em>. After all, what value does improved health IT offer if not to ensure that both the patient and the provider can securely access medical data when they need it?</p><p>ONC’s work is critical for the healthcare industry. Their 2018 report suggests they are not giving up on the vision of a health information exchange infrastructure. I look forward to following ONC’s efforts in the next year and to working in parallel to support the same vision.</p><p><em>Disclosure: I am the Head of Privacy &amp; Data Ethics at Datavant, a company focused on securely connecting health data to improve patient outcomes.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6d6212419f1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/datavant/data-access-and-connectivity-are-ethical-requirements-for-the-healthcare-industry-commentary-on-d6d6212419f1">Data access and connectivity are ethical requirements for the healthcare industry: commentary on…</a> was originally published in <a href="https://medium.com/datavant">Datavant</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Applying the “Do No Harm” Principle to Health Data]]></title>
            <link>https://medium.com/datavant/applying-the-do-no-harm-principle-to-health-data-c3c3d33ad062?source=rss-d17646ee3754------2</link>
            <guid isPermaLink="false">https://medium.com/p/c3c3d33ad062</guid>
            <category><![CDATA[healthcare]]></category>
            <category><![CDATA[data-ethics]]></category>
            <category><![CDATA[health-technology]]></category>
            <category><![CDATA[hipaa]]></category>
            <category><![CDATA[privacy]]></category>
            <dc:creator><![CDATA[Patsy Bailin]]></dc:creator>
            <pubDate>Mon, 15 Oct 2018 16:46:23 GMT</pubDate>
            <atom:updated>2018-10-15T16:46:23.565Z</atom:updated>
            <content:encoded><![CDATA[<p>At Datavant, we build software that makes it possible to share patient data securely, but our mission is bigger than that: to make it easier for players in the healthcare system to connect and use their health data for the good of patients. This mission requires a broad conception of data ethics — one that encompasses both data security and patient privacy, but also an evaluation of the risk, cost and benefit of different data strategies. We believe that strong data ethics is essential for a company building a health data ecosystem, and we would like to share a few brief thoughts on our philosophical approach here.</p><p><strong>What is the “do no harm” principle and how does it apply to health data?</strong></p><p>One of the great ironies of health data is that the sources of the data — the patients — can derive limited value from their own information. Most patients need help from other people or organizations that can explain their data to them, use it to improve their care, or conduct additional analysis. In other words, in order to get value from their own data, patients have to share it, and patients’ willingness to share their data is based on trust that those they share it with will use it for good. In our view, these data holders — stewards, if you will — are bound to serve the patient in accordance with the most recognizable axiom of the healthcare profession: “First, do no harm.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*aIGoWscnIG5ocAVv" /><figcaption>The patient relationship is built on trust</figcaption></figure><p>Traditionally applied, the “do no harm” principle requires that healthcare providers weigh the risk that a given course of action will hurt a patient against its potential to improve the patient’s condition. In short, to perform a cost-benefit analysis. This cost-benefit analysis is rarely straightforward. All medical treatments have risks, and the calculation of each patient’s risk threshold is unique. Due to the sensitivity of the medical information and the vulnerability of the patient seeking care, the doctor is bound to confidentiality with respect to the patient’s information. And given the direct impact of the provider’s decision on the patient, the doctor must respect the patient’s right to understand the cost-benefit calculation and — whenever possible — to consent to any course of action.</p><p>When it comes to the use and disclosure of health data, the interpretation of the “do no harm” maxim is similar: data stewards must weigh the risk of harming a patient (often a breach of patient privacy), against the potential benefits. With health data, the harm of a breach or other violation of a patient’s data rights is often acutely felt by the individual while the benefit of analysis on an aggregated dataset is significant but spread across many patients. Data stewards must appreciate this asymmetry from the patient’s perspective, and guard patient privacy carefully while only sharing data for purposes that will improve patient outcomes.</p><p><strong>Breaches of privacy as patient harm</strong></p><p>In contrast to healthcare providers, the risk that data stewards assess is not bodily harm, but informational harm. Specifically, the loss of control over one’s unique and private information, which could result in reputational, emotional, or financial damage. The appropriate mitigation for informational harm is to remove the patient’s identifying information from the data prior to sharing it. In the data world, we refer to this process as a “data protection”, and it parallels the doctor’s obligation of confidentiality in the provider-patient relationship.</p><p>The notion of “confidentiality” or “data protection” in data sharing refers to enforcing technical and administrative controls around information access to minimize the risk of harm to the data subject. It is achieved through the use of strong security and privacy controls, which have been codified for healthcare players in the Health Information Portability and Accountability Act (HIPAA).</p><p>Under HIPAA, security controls are technical and administrative protocols that mitigate the risk of unauthorized access to and disclosure of information. These include things like access permissions and penetration testing. By contrast, privacy controls are infrastructure and process requirements that mitigate the risk of unauthorized access to and disclosure of identity.</p><p>HIPAA’s privacy requirements focus on de-identification as the primary identity protection mechanism. De-identification removes the identity of the patient from the data, thereby mitigating the risk of direct harm to the patient, which could be emotional, financial, or reputational damage resulting from the unauthorized access to or use of identifiable and sensitive information.</p><p><strong>Assessing patient benefit</strong></p><p>Under the “do no harm” principles, mitigating the risk of harm — in this case, a violation of privacy — is only half the challenge. The other half is ensuring that patients benefit from the value derived from data sharing.</p><p>When defining patient benefit, it’s worth considering why patients disclose information in the first place. Patients don’t voluntarily disclose their data unless they anticipate some value from doing so. There are four basic categories of patient value:</p><p><strong>1.</strong> <strong>Improved diagnosis</strong>, including both diagnostic accuracy and how the diagnosis is delivered</p><p><strong>2. Improved treatment</strong>, including treatment safety, efficacy and availability</p><p><strong>3.</strong> <strong>Improved care</strong>, including both quality and affordability</p><p><strong>4. Improved information</strong>, including both improved access to relevant medical information and greater control over personal data</p><p>We’ll briefly consider how these categories are referenced by data stewards doing a “do no harm” analysis below.</p><p><strong>“Do no harm” in practice</strong></p><p>Imagine a hospital and a health analytics company want to work together to determine correlations in patient symptoms, behavior, or health history that might help the hospital recognize patients who need urgent care or triage patients for more effective care. If the hospital can provide adequately de-identified health data to the analytics company, the privacy risk to the patient is mitigated, and there is benefit to the patient in the form of both improved quality of care and (hopefully) a more efficient diagnosis. In short, under a “do no harm” analysis, it makes sense to move forward.</p><p>Contrast this with a lender using medical information to ascertain whether an applicant should pay a higher rate because of a genetic condition. In this situation, the patient’s privacy is not protected (their medical information is not de-identified), and the lender is using the information to discriminate against certain types of borrowers based on genetic conditions. The applicant is harmed by the lender’s use of their personal data, and there is no corresponding benefit.</p><p>At Datavant, we believe that the healthcare system can unlock tremendous value through the responsible sharing of patient data across silos. And while the goal of “sharing responsibly” can present a number of ethical questions and challenges, we believe that the medical profession’s existing tenet — “do no harm” — serves as a strong first principle.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c3c3d33ad062" width="1" height="1" alt=""><hr><p><a href="https://medium.com/datavant/applying-the-do-no-harm-principle-to-health-data-c3c3d33ad062">Applying the “Do No Harm” Principle to Health Data</a> was originally published in <a href="https://medium.com/datavant">Datavant</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>