The Evolving Landscape of Health Data Protection Laws in the United States

Kathrin Gardhouse
Jun 5, 2024
Share this post
Sharing to FacebookSharing to LinkedInSharing to XSharing to Email

The healthcare sector in the United States has seen a profound transformation in its approach to data privacy, paralleling significant technological advancements, in particular the electronic health record (EHR). This article explores the trajectory of health data protection legislation in the U.S., highlighting key developments in EHR development and adoption and ongoing challenges in balancing privacy with technological integration.

The 1970s and 1980s: Laying the Foundation

The journey of health data protection in the US begins in the 1970s and 1980s, not with specific health data laws but with broader regulations that set the stage for future, more focused legislation. During this era, the US saw the inception of foundational privacy laws that would later influence healthcare regulations:

The Privacy Act of 1974: This Act regulates the collection, maintenance, use, and dissemination of personally identifiable information about individuals that is maintained in systems of records by federal agencies.

Health Maintenance Organization Act of 1973: Although primarily aimed at providing federal endorsement, certification, and assistance for the establishment of HMOs, this act also set standards for medical record keeping in HMOs.

These laws did not address digital records explicitly since the digital handling of health information was not yet a widespread practice. However, they established a baseline concern for the privacy of personal data within federal record systems.

The 1990s to Present – HIPAA and its Expansions

The 1990s marked a pivotal era in health data protection in the United States with the enactment of the Health Insurance Portability and Accountability Act (HIPAA) of 1996. HIPAA aimed primarily at enabling people to maintain insurance coverage between jobs, simplifying healthcare communications, and reducing healthcare fraud and abuse.

Recognizing the growing prevalence of electronic records, HIPAA was expanded in the 2000s as a comprehensive response to the need for national standards for health data privacy and security.

Privacy Rule: The Privacy Rule, introduced after HIPAA's enactment, was finalized in December 2000 and went into effect in April 2003. It establishes national standards for the protection of individually identifiable health information by regulating how covered entities use and disclose protected health information (PHI).

Security Rule: Complementing the Privacy Rule, the Security Rule was finalized in 2003 and implemented in 2005. It sets national standards for securing electronic protected health information (ePHI) by specifying a series of administrative, physical, and technical safeguards for covered entities to ensure the confidentiality, integrity, and availability of ePHI.

These developments reflected a significant shift towards reinforcing and expanding the regulatory framework around health data protection, addressing both the opportunities and vulnerabilities presented by digital and electronic health records systems.

The significance of HIPAA results from the fact that unlike earlier, more fragmented legislation, HIPAA provides a comprehensive framework for data protection across the healthcare industry, affecting healthcare providers, insurance providers, and third parties.

Electronic Health Records (EHR)

The development of electronic health records (EHR) and the corresponding infrastructure has been significantly shaped by government incentives and regulations aimed at increasing adoption across the healthcare sector. The Health Information Technology for Economic and Clinical Health (HITECH) Act, enacted in 2009 as part of the American Recovery and Reinvestment Act, marked a pivotal point in this evolution. Prior to its enactment, only 9 percent of hospitals had adopted EHR. In 2021, this number had increased to 96 percent (78 percent for office-based physicians).

The HITECH Act introduced substantial financial incentives for healthcare providers to adopt and meaningfully use EHR systems, channeling billions of dollars into the sector. It also established penalties, beginning in 2015, for Medicare providers that failed to demonstrate meaningful use of EHRs. This carrot-and-stick approach spurred a dramatic increase in EHR adoption rates, from modest levels prior to the act to substantial majority adoption within a decade. The HITECH Act also addresses additional privacy and security concerns associated with the transmission of EHR, including by updating HIPAA Security and Privacy Rules.

The infrastructure for EHR in the United States is primarily provided by private service providers rather than the government. While the federal government, particularly through initiatives under the Office of the National Coordinator for Health Information Technology (ONC), plays a significant role in setting standards, regulations, and providing funding and incentives (especially as seen in the HITECH Act), the actual development and maintenance of EHR systems are largely the domain of private companies.

These private EHR providers design, build, and support the software and systems that healthcare organizations use to manage patient data. Major companies in this sector include Epic Systems, Cerner Corporation, and Allscripts, among others. These companies compete in a robust market to offer EHR solutions that meet the certification criteria established by the government, which ensures their systems support meaningful use capabilities such as e-prescribing, the electronic exchange of health information to improve quality of healthcare, and provide clinical decision support.

However, the journey was not without challenges; factors such as the cost of EHR systems, complexity of integration, interoperability, concerns over privacy and security, and the initial resistance from healthcare providers due to the disruption of established workflows, slowed down the momentum.

Further legislative actions have continued to refine the EHR adoption landscape. For instance, modifications to the HITECH Act and the introduction of the Medicare Access and CHIP Reauthorization Act of 2015 (MACRA) have helped to streamline the requirements and further integrate EHR use into the broader healthcare quality and reimbursement frameworks.

Despite these efforts, ongoing issues such as interoperability between different EHR systems and the burden of regulatory compliance have persisted, affecting the full realization of a unified digital health record system. Nonetheless, these laws and the corresponding development of EHR infrastructure have undeniably transformed healthcare practices, enhancing the potential for improved clinical outcomes, patient management, and data analytics, albeit with an ongoing need for adjustments and improvements in system implementation and functionality.

State Health Privacy Laws

In the United States, state privacy laws operate alongside federal regulations like HIPAA to govern the protection of personal health information. While HIPAA sets a national standard, states can enact stricter privacy protections. Many US states have enacted privacy laws that also apply to health information and there are also state laws that specifically regulate health information, such as California’s Confidentiality of Medical Information Act (CMIA).

These state-specific laws often address gaps in HIPAA or adapt to local priorities and concerns, leading to a patchwork of regulations that healthcare providers must navigate. This layering of state and federal laws means that compliance can be complex, requiring healthcare entities to adhere not only to HIPAA but also to the varying requirements of state laws where they operate.

Addressing Modern Challenges: Mobile and Digital Health

As technology has advanced, the integration of mobile health apps, telemedicine, and AI in healthcare has indeed brought complex challenges to the forefront, particularly around privacy and the application of existing regulations like HIPAA.

Mobile Health Apps and HIPAA

Mobile health apps often fall outside the direct scope of HIPAA due to the nature of the entities that develop and operate them. HIPAA regulations specifically apply to covered entities (like doctors, hospitals, and health plans) and their business associates. Many mobile health app developers do not fit into these categories; they are neither healthcare providers, plans, nor do they typically have formal relationships with these covered entities that would bring them under HIPAA's jurisdiction. This can lead to significant privacy vulnerabilities, as these apps may collect, store, and potentially share sensitive health information without adhering to the stringent privacy and security protections required by HIPAA.

For instance, a fitness tracking app that collects health data directly from consumers and uses this information for performance metrics or health tips is not necessarily conducting transactions covered by HIPAA, such as billing insurers or exchanging health information with doctors. Without the constraints of HIPAA, the data handling practices of these apps can vary widely, and they may not be obligated to protect user data with the same rigor as a covered entity would be.

AI and Machine Learning in Healthcare

The use of AI and machine learning in healthcare raises its own set of complex questions related to data usage, patient consent, and potential biases. AI systems often require large datasets to train algorithms that can make predictions or aid in diagnostics. These datasets may contain vast amounts of personal health information. Under HIPAA, the use of such data is tightly regulated; however, the nuances of AI might complicate compliance. For instance, obtaining patient consent for using their data in AI training can be challenging, especially when data might be de-identified for research but still could be re-identified under certain circumstances.

Moreover, AI systems can potentially introduce biases that affect patient outcomes. These biases can stem from the data used to train algorithms, which might not be representative of all demographic groups. Addressing these biases and ensuring fairness in AI-driven healthcare outcomes is crucial but difficult, as it involves not only technological solutions but also careful consideration of the ethical implications of deploying AI in healthcare settings.

Conclusion

The U.S. has made significant strides in health data protection, with HIPAA and its numerous updates serving as the cornerstone of efforts to safeguard patient information. However, the digital age continues to introduce new challenges that require ongoing legislative and regulatory adaptations. The shift towards digital health records, telemedicine, and AI-driven tools necessitates a dynamic approach to privacy that balances innovation with the need to protect sensitive health information.Looking ahead, U.S. health data protection laws will need to evolve continually to address these challenges, ensuring that regulations keep pace with technological advancements to safeguard patient privacy without stifling innovation. This balance will be crucial as healthcare systems increasingly rely on digital solutions to enhance patient care and operational efficiency.

Further Resources

We previously published a number of resources that inform about how Private AI can facilitate the protection of health data and thus compliance with health data protection laws. In short, Private AI can reliably detect and redact protected health information in large data sets, whether composed of structured or unstructured data. To see the tech in action, try our web demo, or request an API key to try it yourself on your own data. For more information, see further resources below:

Data Left Behind: AI Scribes’ Promises in Healthcare

Data Left Behind: Healthcare’s Untapped Goldmine

The Future of Health Data: How New Tech is Changing the Game

Why is linguistics essential when dealing with healthcare data?

Why Health Data Strategies Fail Before They Start

Private AI to Redefine Enterprise Data Privacy and Compliance with NVIDIA

EDPB’s Pseudonymization Guideline and the Challenge of Unstructured Data

HHS’ proposed HIPAA Amendment to Strengthen Cybersecurity in Healthcare and how Private AI can Support Compliance

Japan's Health Data Anonymization Act: Enabling Large-Scale Health Research

What the International AI Safety Report 2025 has to say about Privacy Risks from General Purpose AI

Private AI 4.0: Your Data’s Potential, Protected and Unlocked

How Private AI Facilitates GDPR Compliance for AI Models: Insights from the EDPB's Latest Opinion

Navigating the New Frontier of Data Privacy: Protecting Confidential Company Information in the Age of AI

Belgium’s Data Protection Authority on the Interplay of the EU AI Act and the GDPR

Enhancing Compliance with US Privacy Regulations for the Insurance Industry Using Private AI

Navigating Compliance with Quebec’s Act Respecting Health and Social Services Information Through Private AI’s De-identification Technology

Unlocking New Levels of Accuracy in Privacy-Preserving AI with Co-Reference Resolution

Strengthened Data Protection Enforcement on the Horizon in Japan

How Private AI Can Help to Comply with Thailand's PDPA

How Private AI Can Help Financial Institutions Comply with OSFI Guidelines

The American Privacy Rights Act – The Next Generation of Privacy Laws

How Private AI Can Help with Compliance under China’s Personal Information Protection Law (PIPL)

PII Redaction for Reviews Data: Ensuring Privacy Compliance when Using Review APIs

Independent Review Certifies Private AI’s PII Identification Model as Secure and Reliable

To Use or Not to Use AI: A Delicate Balance Between Productivity and Privacy

To Use or Not to Use AI: A Delicate Balance Between Productivity and Privacy

News from NIST: Dioptra, AI Risk Management Framework (AI RMF) Generative AI Profile, and How PII Identification and Redaction can Support Suggested Best Practices

Handling Personal Information by Financial Institutions in Japan – The Strict Requirements of the FSA Guidelines

日本における金融機関の個人情報の取り扱い - 金融庁ガイドラインの要件

Leveraging Private AI to Meet the EDPB’s AI Audit Checklist for GDPR-Compliant AI Systems

Who is Responsible for Protecting PII?

How Private AI can help the Public Sector to Comply with the Strengthening Cyber Security and Building Trust in the Public Sector Act, 2024

A Comparison of the Approaches to Generative AI in Japan and China

Updated OECD AI Principles to keep up with novel and increased risks from general purpose and generative AI

Is Consent Required for Processing Personal Data via LLMs?

The evolving landscape of data privacy legislation in healthcare in Germany

The CIO’s and CISO’s Guide for Proactive Reporting and DLP with Private AI and Elastic

The Evolving Landscape of Health Data Protection Laws in the United States

Comparing Privacy and Safety Concerns Around Llama 2, GPT4, and Gemini

How to Safely Redact PII from Segment Events using Destination Insert Functions and Private AI API

WHO’s AI Ethics and Governance Guidance for Large Multi-Modal Models operating in the Health Sector – Data Protection Considerations

How to Protect Confidential Corporate Information in the ChatGPT Era

Unlocking the Power of Retrieval Augmented Generation with Added Privacy: A Comprehensive Guide

Leveraging ChatGPT and other AI Tools for Legal Services

Leveraging ChatGPT and other AI tools for HR

Leveraging ChatGPT in the Banking Industry

Law 25 and Data Transfers Outside of Quebec

The Colorado and Connecticut Data Privacy Acts

Unlocking Compliance with the Japanese Data Privacy Act (APPI) using Private AI

Tokenization and Its Benefits for Data Protection

Private AI Launches Cloud API to Streamline Data Privacy

Processing of Special Categories of Data in Germany

End-to-end Privacy Management

Privacy Breach Reporting Requirements under Law25

Migrating Your Privacy Workflows from Amazon Comprehend to Private AI

A Comparison of the Approaches to Generative AI in the US and EU

Benefits of AI in Healthcare and Data Sources (Part 1)

Privacy Attacks against Data and AI Models (Part 3)

Risks of Noncompliance and Challenges around Privacy-Preserving Techniques (Part 2)

Enhancing Data Lake Security: A Guide to PII Scanning in S3 buckets

The Costs of a Data Breach in the Healthcare Sector and its Privacy Compliance Implications

Navigating GDPR Compliance in the Life Cycle of LLM-Based Solutions

What’s New in Version 3.8

How to Protect Your Business from Data Leaks: Lessons from Toyota and the Department of Home Affairs

New York's Acceptable Use of AI Policy: A Focus on Privacy Obligations

Safeguarding Personal Data in Sentiment Analysis: A Guide to PII Anonymization

Changes to South Korea’s Personal Information Protection Act to Take Effect on March 15, 2024

Australia’s Plan to Regulate High-Risk AI

How Private AI can help comply with the EU AI Act

Comment la Loi 25 Impacte l'Utilisation de ChatGPT et de l'IA en Général

Endgültiger Entwurf des Gesetzes über Künstliche Intelligenz – Datenschutzpflichten der KI-Modelle mit Allgemeinem Verwendungszweck

How Law25 Impacts the Use of ChatGPT and AI in General

Is Salesforce Law25 Compliant?

Creating De-Identified Embeddings

Exciting Updates in 3.7

EU AI Act Final Draft – Obligations of General-Purpose AI Systems relating to Data Privacy

FTC Privacy Enforcement Actions Against AI Companies

The CCPA, CPRA, and California's Evolving Data Protection Landscape

HIPAA Compliance – Expert Determination Aided by Private AI

Private AI Software As a Service Agreement

EU's Review of Canada's Data Protection Adequacy: Implications for Ongoing Privacy Reform

Acceptable Use Policy

ISO/IEC 42001: A New Standard for Ethical and Responsible AI Management

Reviewing OpenAI's 31st Jan 2024 Privacy and Business Terms Updates

Comparing OpenAI vs. Azure OpenAI Services

Quebec’s Draft Regulation Respecting the Anonymization of Personal Information

Version 3.6 Release: Enhanced Streaming, Auto Model Selection, and More in Our Data Privacy Platform

Brazil's LGPD: Anonymization, Pseudonymization, and Access Requests

LGPD do Brasil: Anonimização, Pseudonimização e Solicitações de Acesso à Informação

Canada’s Principles for Responsible, Trustworthy and Privacy-Protective Generative AI Technologies and How to Comply Using Private AI

Private AI Named One of The Most Innovative RegTech Companies by RegTech100

Data Integrity, Data Security, and the New NIST Cybersecurity Framework

Safeguarding Privacy with Commercial LLMs

Cybersecurity in the Public Sector: Protecting Vital Services

Privacy Impact Assessment (PIA) Requirements under Law25

Elevate Your Experience with Version 3.5

Fine-Tuning LLMs with a Focus on Privacy

GDPR in Germany: Challenges of German Data Privacy (Part 2)

Comply with US Executive Order on Safe, Secure, and Trustworthy Artificial Intelligence using Private AI

How to Comply with EU AI Act using PrivateGPT