HIPAA bars covered entities and business associates from selling protected health information without each individual's authorization. Data de-identified by Safe Harbor or Expert Determination is no longer protected health information and may be licensed. A business associate may de-identify only if its agreement allows it. This is general information, not legal advice.
This page is general information, not legal advice. Whether your company can license a given dataset depends on your contracts, your privacy notices and the law where you and your customers are. Review it with your own counsel before signing anything.
Who HIPAA covers
HIPAA's Privacy Rule applies to covered entities and their business associates. Covered entities are health plans, health care clearinghouses, and health care providers that conduct standard transactions, such as billing, electronically. A business associate is a person or company that creates, receives, maintains or transmits protected health information to perform a service for a covered entity. Billing firms, transcription services, cloud hosts and many software vendors fall here.
HIPAA does not follow the data everywhere. An employer's own personnel files, a fitness app with no provider or plan behind it, and a retailer's purchase history are generally outside it, even when they reveal health details. Other laws may cover them.
This guide is general information, not legal advice. HIPAA questions turn on a company's role and its contracts. Have health care counsel review any plan to license health-related data.
What counts as protected health information
Protected health information, or PHI, is individually identifiable health information held or transmitted by a covered entity or business associate. It relates to a person's health or condition, the care provided, or payment for care, and it identifies the person or could reasonably be used to do so.
The definition is wider than clinical charts. Appointment schedules, claims, call recordings with patients, support tickets that mention a diagnosis, and billing notes are all PHI when tied to an individual. Operational records in a health care business should be presumed to contain PHI until shown otherwise.
Two exclusions are worth knowing. Records a covered entity holds in its role as an employer, such as staff sick notes in a personnel file, are not PHI. Information about a person who has been dead for more than 50 years is not PHI either. Neither exclusion is wide enough to carry a data license.
The prohibition on selling PHI
The Privacy Rule, at 45 CFR 164.502(a)(5)(ii), states that a covered entity or business associate may not sell PHI, except under an authorization from the individual. A sale means a disclosure of PHI where the covered entity or business associate receives remuneration, directly or indirectly, from or on behalf of the recipient in exchange for the PHI. The authorization must state that the disclosure will result in remuneration.
The rule lists exceptions that are not treated as sales. They include disclosures for public health purposes, for treatment and payment, for the sale or merger of the covered entity itself, to a business associate for work done on the covered entity's behalf, and for research where the price reflects only the cost of preparing and sending the data.
A paid license of identifiable patient records to an AI developer for commercial model training does not sit comfortably in any of these. Collecting signed authorizations from every individual in a large historical archive is rarely practical. In practice, the lawful route runs through de-identification.
De-identification: Safe Harbor and Expert Determination
Health information that has been de-identified under 45 CFR 164.514 is not PHI, and the Privacy Rule's limits, including the sale prohibition, no longer apply to it. The rule offers two methods.
A covered entity may assign a code so that it can re-identify records later. The code must not be derived from information about the individual, and the entity must not disclose how the code works. Free text is the hard part under either method. Clinical notes and call transcripts carry names, dates and places in unpredictable forms.
Whichever method is used, keep the evidence: the list of fields removed or transformed, the review of free text, and for Expert Determination the expert's signed report. HHS does not approve or certify de-identification, so the record is what a covered entity relies on if the work is questioned.
| Method | What it requires | Trade-off |
|---|---|---|
| Safe Harbor | Remove 18 listed categories of identifiers about the individual, relatives, employers and household members, and have no actual knowledge that what remains could identify the person | Predictable, but removes exact dates and small geographic areas |
| Expert Determination | A person with appropriate statistical and scientific knowledge determines that the risk of identification is very small for the anticipated recipient, and documents the methods and results | Can keep more detail, but needs an expert engagement and a written analysis |
Limited data sets and data use agreements
A limited data set is a middle category. It removes 16 categories of direct identifiers, such as names, contact details and record numbers, but may keep dates and some geography, such as city, state and ZIP code. It may be disclosed without authorization only for research, public health or health care operations, and only under a data use agreement.
The agreement must set the permitted uses, bar the recipient from identifying or contacting the individuals, and require safeguards. A limited data set is still PHI. That means the sale prohibition still has to be considered, and commercial model training is not obviously one of the three permitted purposes. A limited data set is seldom the right vehicle for a training-data license. Counsel should confirm before one is used that way.
What business associates may and may not do
A business associate's rights come from its business associate agreement, or BAA, and from the rule. It may use and disclose PHI only as the BAA permits or as the law requires. Business associates are directly liable under HIPAA for uses that go beyond that.
The key point for a vendor is de-identification. HHS guidance says a business associate may de-identify PHI only to the extent its BAA authorizes it to do so. A vendor that strips identifiers and licenses the result without that permission has used PHI for a purpose the agreement did not allow, even if the output is flawless.
A covered entity that wants a vendor to prepare de-identified data on its behalf can instruct the vendor to do so. In that case the vendor is working for the covered entity, and the resulting dataset is the covered entity's to license. Who holds the right to the de-identified output should be written into the agreement, because the rule itself does not say.
- May: perform the services named in the agreement.
- May: use PHI for its own management and administration, if the agreement says so.
- May: de-identify PHI and use the result, but only where the agreement expressly allows it.
- May not: sell PHI without the individuals' authorization.
- May not: use PHI to build or train products for itself unless the covered entity agreed and the use is otherwise lawful.
- May not: rely on silence in the agreement as permission.
State health privacy laws and data outside HIPAA
HIPAA sets a floor. State laws can be stricter, and several are. Some states have medical confidentiality statutes that reach beyond HIPAA's covered entities. Some protect particular kinds of records, such as mental health, reproductive health, genetic or substance use information, with extra conditions. Federal rules separately protect certain substance use disorder treatment records.
A newer group of state laws covers consumer health data held by companies that HIPAA does not reach. Washington's My Health My Data Act is the best known and requires a specific signed authorization before consumer health data is sold. State definitions of de-identified data do not always match HIPAA's. Check which states' residents are in the data before settling on a method.
A workable order of steps
For a health care organization or vendor considering a license, the questions run in a fixed order. First, settle the role: covered entity, business associate or neither. Second, if a business associate, read every BAA for a de-identification right and exclude data from clients whose agreements lack one. Third, choose the de-identification method and decide who performs it. Fourth, check state law for the populations involved. Fifth, document all of it.
Outrich Data does not buy identifiable patient records. Where health-related operational data is considered, the rights review comes first, and the de-identification method is recorded so a buyer can see which standard is claimed.