Morning Overview

ChatGPT can now read your medical records and answer questions about your health

Patients across the United States can now take their full medical records, upload them to ChatGPT, and ask the AI chatbot to explain lab results, flag potential drug interactions, or summarize years of clinical notes. Federal law gives individuals broad rights to obtain those records from hospitals and insurers. But the moment a patient pastes that data into a consumer AI tool, the federal privacy protections that governed the records inside a clinic vanish, creating a gap that no existing regulation explicitly closes.

Why the HIPAA gap matters for patients using ChatGPT

The core tension is straightforward. Under federal rules spelled out in access regulations, individuals hold a right of access to their designated record sets, which include clinical notes, lab reports, imaging results, billing records, and insurance information held by covered entities and their business associates. Hospitals, physician practices, and health plans must provide copies of those records on request, often through patient portals that allow direct downloads.

Once a patient downloads that file and uploads it to ChatGPT, the data crosses a legal boundary. HIPAA applies to covered entities and their business associates, not to the patient or to the consumer software the patient chooses. OpenAI is not a covered entity. It has no business associate agreement with the patient’s hospital. The protections that restricted how a clinic stored, shared, or used the data simply do not follow the file into the chatbot’s servers.

Analysis published by Harvard researchers directly addresses this question and concludes that HIPAA does not protect what a person voluntarily shares with ChatGPT. The legal framework was designed decades before general-purpose AI tools existed, and it was built around the relationship between patients and their healthcare providers, not between patients and software companies.

This gap raises a practical question: will state regulators step in where federal rules fall short? A reasonable hypothesis holds that routine patient uploads of full medical records to general-purpose AI could generate measurable spikes in state attorney-general investigations of data brokers within the next year and a half, even without new federal legislation. The logic is simple. Health data that leaves HIPAA’s perimeter enters a space governed primarily by state consumer protection statutes and the Federal Trade Commission’s authority over unfair or deceptive practices. If AI companies retain, use, or share that data in ways patients did not expect, state attorneys general already have tools to investigate. Whether those investigations actually materialize depends on whether consumer complaints reach a volume that forces action, a threshold that grows more likely as AI-assisted health queries become routine.

What federal access rights actually cover

The scope of records patients can obtain is wider than many people realize. According to guidance from the U.S. Department of Health and Human Services on personal health information, the right of access extends to a broad array of health information. That includes medical records, billing records, lab reports, clinical case notes, and other data maintained in a patient’s designated record set by covered entities and business associates.

Patients can request electronic copies, and providers generally must fulfill those requests within thirty days. Many health systems now offer one-click downloads through apps that comply with interoperability rules. The practical result is that millions of people already hold portable digital copies of their health histories on personal devices. The barrier between a patient’s phone and a ChatGPT prompt is a copy-paste or a file upload, nothing more.

That ease of transfer is exactly what makes the privacy question urgent. The records were created and stored under strict security and privacy requirements. Encryption standards, access controls, audit logs, and breach notification obligations all applied while the data sat inside a hospital’s electronic health record system. None of those requirements bind OpenAI or any other consumer AI platform when a patient voluntarily hands over the same information.

Where legal protections break down after upload

The Harvard Law School analysis traces the boundary clearly. HIPAA’s Privacy Rule restricts how covered entities handle protected health information. When a patient exercises the right of access and then shares that information with a third party that is not a covered entity or business associate, the Privacy Rule no longer applies to the recipient. ChatGPT, Google’s Gemini, Anthropic’s Claude, and every other consumer chatbot fall outside HIPAA’s reach in this scenario.

What does apply? OpenAI’s own terms of service and privacy policy govern how the company handles data users submit. Those policies can change. They are not subject to the same enforcement mechanisms as HIPAA, which carries civil and criminal penalties administered by HHS. A patient who uploads records to ChatGPT is relying on a corporate privacy policy rather than a federal statute backed by decades of regulatory enforcement.

State laws add a patchwork of partial coverage. Some states have health data privacy statutes that extend beyond HIPAA’s scope. Washington state’s My Health My Data Act, for example, applies to entities that are not HIPAA-covered and regulates the collection, sharing, and sale of consumer health data. But coverage varies dramatically by state, and enforcement depends on resources and political priorities within each attorney general’s office.

Unresolved questions for patients

For patients, the legal nuances translate into a series of unresolved practical questions. The first is how long AI companies keep uploaded records and what they do with them. If a chatbot uses medical histories to improve its models, that secondary use may surprise users who assumed their data would be confined to a single conversation. Even if policies promise limited retention, patients have little visibility into whether those promises are honored in practice.

A second question is how easily data can be linked back to an individual. Some AI providers say they de-identify or aggregate user inputs, but full medical records often contain rare diagnoses, procedure dates, and combinations of medications that make re-identification plausible. De-identification techniques that work for large datasets may be less effective when a single person’s entire health history is involved.

Third, patients must consider downstream sharing. If an AI vendor partners with other technology companies, cloud providers, or analytics firms, medical records entered into a chat window could circulate far beyond the original platform. Each additional recipient introduces another point of potential exposure, and most of those actors operate outside HIPAA.

These uncertainties leave patients with difficult trade-offs. The same tools that can help decode jargon-filled lab reports or compare treatment options also create new vectors for privacy loss. For people managing complex or stigmatized conditions, the risk of unintended disclosure may feel especially acute.

In the absence of clear federal rules, practical safeguards fall largely on individuals. Patients who choose to use AI tools can strip out names, dates of birth, addresses, and insurance numbers before uploading documents, though that does not fully eliminate re-identification risk. They can review privacy policies, disable data-sharing settings where possible, and favor tools that offer local processing or enterprise agreements with health systems that bring them under HIPAA as business associates.

The broader policy conversation is only beginning. Lawmakers could decide to extend HIPAA-like protections to certain categories of consumer health data, or to require explicit consent and strict limits on how AI companies use medical information. Regulators might also push for greater transparency around retention periods, model training practices, and security controls for health-related uploads.

Until those debates translate into concrete rules, the HIPAA gap will remain. Patients are legally empowered to obtain and control their medical records, but once those records leave the healthcare system and enter a chatbot, they step into a landscape governed by contracts and fragmented state laws rather than a comprehensive federal privacy framework. Anyone considering that step has to weigh the convenience and insight AI can provide against the reality that, for now, their most sensitive data may be least protected precisely when they seek the most help understanding it.

More from Morning Overview

*This article was researched with the help of AI, with human editors creating the final content.