Skip to content

Privacy and preparation

Healthcare admin retention versus reuse: keeping is not permission

By SourceX Editorial · Reviewed by Noah Loul ·

9 sections

Short answer

Retention rules say how long a record must be kept and for whom; they never decide whether it may be reused for AI. Reuse depends on HIPAA's use and disclosure rules, business associate agreements, client and payer contracts and state law. Review the two separately: map each administrative record family to why it is kept, who controls reuse and what counsel must settle.

Record timeline

Healthcare admin retention

This page covers healthcare admin retention versus reuse: keeping is not permission.Illustrative

Key takeaways

  • A retention duty explains why a record is held; it neither authorizes nor forbids a new use such as AI training.
  • HIPAA sets no retention period for medical records, only six-year retention for its own compliance documentation.
  • A business associate may de-identify client data for its own purposes only if its agreement allows it, according to HHS.
  • De-identification changes privacy status, not ownership or contract limits, so client and payer terms still need review.
  • Map each administrative record family separately: why it is kept, who controls reuse, the open question and the reviewer.

Why should retention obligations and permission for AI reuse be reviewed separately?

Because they answer different questions. A retention obligation says how long a record must be kept and for whom, usually a regulator, an auditor, a contract counterparty or the patient. Permission for AI reuse depends on whether a new use or disclosure is allowed at all, which turns on HIPAA's use and disclosure rules, business associate agreements, payer and client contracts and state law.

A record you must keep for ten years is held for that purpose. The obligation does not authorize a new purpose, and it does not forbid one either. Treating the retention schedule as a reuse inventory is the most common shortcut in healthcare administration, and it tends to fail in both directions: teams assume long-retained data is theirs to use, or assume that anything still under retention is untouchable.

This page keeps to administrative and nonclinical records such as claims, remittances, eligibility checks, authorization paperwork and call logs. It is general information for the people who run those operations, not legal advice, and the map it offers is a draft for counsel and a privacy officer to review.

What the retention rules actually require, and what they leave unsaid

Most retention periods in this area attach to a specific record type and a specific reason, and none of them speaks to AI. Reading them closely is the fastest way to see why they cannot settle reuse.

HHS states plainly that the HIPAA Privacy Rule has no medical record retention requirement and that state law generally governs how long medical records are kept. What HIPAA does set is a six-year period for its own compliance documentation: policies, procedures and other required documentation under the Privacy Rule, and security documentation under the Security Rule, counted from creation or the date last in effect, whichever is later.

What the retention rules actually require, and what they leave unsaid
RuleRecord it coversPeriodWhat it does not decide
HIPAA Privacy Rule documentation, 45 CFR 164.530(j)Privacy policies, notices and other documentation the rule requiresSix years from creation or last effective dateWhether any patient data may be used for a new purpose
HIPAA Security Rule documentation, 45 CFR 164.316(b)(2)Security policies, procedures and required records of actionsSix years from creation or last effective date; HHS calls it a minimumAnything about the data the safeguards protect
HIPAA and medical recordsMedical records themselvesNone set by HIPAA; state law generally governsReuse; HIPAA's use and disclosure rules apply while records are held
Medicare provider documentation, 42 CFR 424.516(f)Documentation CMS's fact sheet describes for providers under that sectionSeven years from the date of service, per the CMS fact sheetWhether the provider or its vendor may reuse the records
Medicare Advantage contracts, 42 CFR 422.504(d)Plan books, records and documents, extended to contracted providers and downstream entitiesTen years from contract end or audit completion, whichever is laterAny use beyond audit, inspection and the contract's purposes

Where permission for reuse comes from instead

Permission for reuse is built from the rules on uses and disclosures, the contracts that passed the data to you and the form the data will take when it leaves. Each of these is a separate gate.

For a covered entity, protected health information may be used or disclosed only as the Privacy Rule permits or the individual authorizes. HHS guidance says a covered entity may not sell protected health information without an authorization that states the disclosure will result in remuneration. For a business associate the gate is narrower still: HHS explains that a business associate may use the information only as its agreement permits, and that it may de-identify the information for its own purposes only if the agreement allows it. HHS's sample agreement provisions suggest the parties say whether, and how, the business associate may de-identify.

Once data meets the HIPAA de-identification standard it is no longer protected health information, and HHS's guidance describes two ways to meet it: expert determination and the safe harbor removal of listed identifiers. De-identification changes the privacy status of the data. It does not create ownership, and it does not override a client contract that limits what a vendor may do with a client's records.

The retention and reuse issue map

Use one row per record family, not per system. The columns separate why the record is kept from who controls reuse, so the two questions cannot collapse into one. A row is ready for counsel when every cell names a document, not an assumption.

The retention and reuse issue map
Record familyWhy it is keptWho controls reuseReuse question to settleReviewer
Claims and remittances (837 and 835 transactions)Payer audits, appeals, state law and client contractsCovered entity; a billing vendor only as its agreement allowsDoes the agreement permit de-identification for the vendor's own purposes?Privacy officer and contract counsel
Prior authorization requests and determinationsPayer program rules and plan audit windowsCovered entity or plan; delegated vendors by contractCan the administrative fields be separated from attached clinical documents?Privacy officer and utilization management lead
Eligibility and benefits checksBilling support and client contract termsCovered entity; clearinghouse terms may also applyDo clearinghouse or payer portal terms restrict reuse of responses?Contract counsel
Patient access call recordings and transcriptsClient contracts, state recording law, plan marketing rules where applicableCovered entity; the call center as business associateWere callers told of recording, and does that notice reach AI use?Privacy officer and counsel
Denial, appeal and correspondence lettersAppeal deadlines and audit supportCovered entityDo letters quote clinical detail that must be removed first?Privacy reviewer
Scheduling and no-show logsOperations and client reportingCovered entity or practice management vendorIs the minimum necessary for the task far smaller than the log?Operations lead and privacy reviewer
HIPAA compliance documentationSix-year documentation rulesThe organization itselfIs this even patient data, or a confidentiality and copyright question?Compliance officer
Records under a Medicare Advantage contractTen-year audit and inspection rightsPlan, and downstream entities as their contracts allowDoes the downstream contract limit use to the plan's purposes?Contract counsel

Drawing the field line: administrative evidence in, clinical narrative out

Keep the fields the administrative task needs to reach its outcome and nothing that describes a patient's condition beyond that. HHS describes the minimum necessary standard as reasonable efforts to limit uses, disclosures and requests to what the purpose requires; the same discipline is the right starting point for deciding what an AI dataset should contain, whatever legal path the data takes.

For a task such as classifying denial reasons or predicting which claims need a corrected resubmission, the necessary evidence is administrative: payer and plan type, dates, claim status history, denial and adjustment reason codes, the action taken and its outcome. Diagnosis codes are a judgment call that privacy review should make for the specific task; free-text clinical notes, attached records and treatment narratives stay out.

  • Keep: payer, product line, claim and service dates, status transitions, reason codes, resubmission and appeal steps, outcome and elapsed time.
  • Review case by case: diagnosis and procedure codes, provider specialty, place of service, and free-text denial explanations that may quote clinical facts.
  • Exclude: clinical notes, attached medical records, images, medication lists, and any narrative that explains a patient's condition.
  • Exclude regardless of task: direct identifiers that de-identification would remove, unless an approved path other than de-identification has been chosen by counsel.

Worked example (illustrative): a billing company's denial history

Everything in this example is invented; the counts and durations are labelled illustrative and no money amounts appear. A revenue cycle company works for three physician groups as a business associate. It holds seven years of claim, remittance and appeal history for each client because its client contracts require it to keep records for that long after each claim closes.

Its operations team proposes licensing a dataset of roughly 400,000 illustrative denied claim lines with their appeal outcomes. The retention schedule is the first thing they produce, and it shows the data is lawfully held. It answers none of the reuse questions.

Running the map: two of the three client agreements are silent on de-identification, and one permits it only to provide services to that client. Under HHS's explanation of business associate permissions, the company cannot de-identify any of the three clients' data for its own licensing purposes as the agreements stand. The path forward is a conversation with each client, which as covered entity may agree to amend the agreement or may decide to license its own data directly. The appeal letters in the set also quote clinical history in a minority of cases, so the dataset design drops the letter text and keeps only the appeal step, dates and outcome.

The useful result is not a yes or no. It is a short list of documents to change, a smaller field set and a named decision-maker for each client.

The exception: records held under audit, hold or a closed contract

Some records are under a stronger obligation than ordinary retention: an open payer audit, a litigation hold, a contract that has ended or a client that has left. These change what you may do to the originals, and they often change who decides about copies.

A hold or an open audit means the original records must stay intact and retrievable; making a de-identified extract is a separate act that counsel should approve so that nothing about the held set changes. When a client relationship ends, the agreement usually governs return or destruction of the client's information, and a vendor that kept data only because return was infeasible should not assume it can now repurpose it.

The reverse case also matters. When a retention period ends, the obligation to keep data ends, but permission to reuse it does not appear. Whether de-identified data can be kept after that point is its own question, covered on a separate page linked below.

Signals that end the internal review and call for counsel

Stop the internal review and bring in counsel and a qualified privacy reviewer when any of the following is true. These are the points where a reasonable operations team can no longer settle the question from documents it controls.

  • The organization is a business associate and the agreement does not expressly allow de-identification for its own purposes.
  • Any proposed transfer involves identifiable data and anything of value in return, which raises HIPAA's sale provisions.
  • Records come from a Medicare Advantage plan or other program contract with its own use limits for downstream entities.
  • State law adds categories such as substance use, mental health, reproductive health or genetic information to the data in scope.
  • Call recordings or messages were captured under a notice that never mentioned uses beyond service and quality.
  • Records are under a legal hold, an open audit or a dispute with the client.

After the map: licensing administrative history

When the map is complete and the people who control each record family have agreed to a path, a healthcare administration business can consider licensing a narrow administrative dataset. SourceX works with such businesses to turn selected records into licensed datasets for AI, covering qualification, rights review, contracting, preparation and delivery.

A billing company or practice manager can start with a short company assessment that needs no data upload, and claims or remittance records move only after it approves the scope and terms and signs. The rights questions in the map come first in that process, because de-identification alone does not supply them.

Frequently asked questions

Does HIPAA say how long medical records must be kept?

No. HHS says the HIPAA Privacy Rule does not include medical record retention requirements and that state law generally governs how long they are kept. HIPAA does require six-year retention of its own compliance documentation, such as policies and procedures.

If we must keep records for ten years, can we use them for AI during that time?

Not because of the retention duty. A retention requirement explains why the data is held; it does not authorize a new use or disclosure. Reuse depends on HIPAA's use and disclosure rules, your agreements and state law, reviewed separately.

Can a billing company de-identify client data and license it?

Only if its business associate agreement allows de-identification for the company's own purposes, according to HHS guidance. Many agreements are silent or limit use to services for that client. Without that permission, the client as covered entity is the one who can decide.

Is de-identified healthcare administrative data free to license?

De-identified data that meets the HIPAA standard is no longer protected health information, but contracts with clients, payers or clearinghouses can still limit its use. Ownership and contractual rights need their own review.

What should stay out of an administrative AI dataset?

Clinical notes, attached medical records, treatment narratives and any detail about a patient's condition that the administrative task does not need. Codes such as diagnoses should be included only after a privacy reviewer decides they are necessary for the specific task.

Sources

  • HHS says the HIPAA Privacy Rule does not include medical record retention requirements and that state laws generally govern retention. Source
  • HHS's Privacy Rule summary requires covered entities to keep privacy policies, notices and other required documentation until six years after the later of creation or last effective date. Source
  • HHS's Security Rule guidance sets six-year retention for required security documentation from creation or last effective date and calls it a minimum. Source
  • CMS's fact sheet on 42 CFR 424.516(f) says the regulation requires medical records to be kept for seven years from the date of service. Source
  • CMS's Medicare Managed Care Manual describes ten-year retention of Medicare Advantage books and records from contract end or audit completion. Source
  • HHS guidance says protected health information may not be sold without an authorization stating that the disclosure will result in remuneration. Source
  • HHS says a business associate may de-identify protected health information for its own purposes only if its business associate agreement permits it, and that de-identified data is no longer protected health information. Source
  • HHS's sample business associate agreement provisions address whether and how the business associate may de-identify information. Source
  • HHS's de-identification guidance describes the expert determination and safe harbor methods under 45 CFR 164.514(b). Source
  • HHS describes the minimum necessary requirement as reasonable steps to limit uses, disclosures and requests to what the intended purpose needs. Source

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your company qualifies