Under HIPAA, covered entities and business associates generally must make reasonable efforts to limit uses, disclosures, and requests for protected health information (PHI) to the minimum necessary to accomplish the intended purpose. The main exceptions, as HHS lists them, cover disclosures to or requests by a health care provider for treatment, disclosures to the individual, uses or disclosures under the individual's authorization, required disclosures to HHS for enforcement, uses or disclosures required by other law, and uses or disclosures required for compliance with HIPAA's Administrative Simplification Rules. For psychiatric QMEs and their staff, the first step is to identify the legal basis for a record request or disclosure, then determine whether minimum necessary and any additional protections apply.
TL;DR:
- Covered entities must identify which workforce members need PHI, the categories they need, and the conditions on access.
- Routine disclosures and requests can follow standard protocols. Non-routine disclosures and requests require individual review against reasonable criteria.
- Provider disclosures and requests for treatment, disclosures to the individual, authorized uses and disclosures, and disclosures required by law are among the exceptions to minimum necessary.
- A workers' compensation request is not automatically exempt. Its legal basis matters, and separately maintained psychotherapy notes have additional protections.
- BAAs must establish permitted uses and disclosures and require appropriate safeguards and reporting. Page-cited review tools can support documentation, but citations do not authorize a disclosure.
Table of Contents
- What the minimum necessary standard covers and when it applies
- Exemptions: when minimum necessary does not apply
- How to implement minimum necessary: policies, roles, and protocols
- Business associates, vendors, cloud services and BAAs: limiting PHI downstream
- Special cases: psychotherapy notes, entire-record requests, and research
- Common compliance errors, enforcement, and breach-reporting implications
- Practical checklist and policy template elements for implementers
- Defensibility and documentation in practice
- Using ChartInsight™ to document minimum necessary decisions
- Sources
- FAQ
What the minimum necessary standard covers and when it applies
The minimum necessary requirement appears at 45 CFR 164.502(b), with implementation specifications at 45 CFR 164.514(d). Where it applies, it requires reasonable efforts to limit PHI to the amount reasonably needed for the specific purpose. It addresses three distinct activities: uses within an entity, disclosures to outside parties, and requests for information from another covered entity.
Policies for workforce access need three elements: who needs access, what categories of PHI those people require, and the conditions under which access is granted. That structure comes directly from the regulation and helps an entity explain how it applies the rule.
The regulation distinguishes routine and non-routine disclosures and requests. For recurring disclosures subject to minimum necessary, such as certain workers' compensation payment disclosures, covered entities can use standard protocols defining the information reasonably necessary for that transaction type. Individual review of each qualifying routine disclosure is not required.
Non-routine disclosures and requests require individual review against established criteria. As HHS states: “Non-routine disclosures and requests must be reviewed on an individual basis in accordance with these criteria and limited accordingly.” Assigning a designated reviewer and recording the reasoning can make that process consistent, but the minimum necessary provisions do not require a named privacy officer to approve every non-routine disclosure.
Minimum necessary is a limit on otherwise lawful activity, not a stand-alone authorization to release records. A QME referral or a request for a complete file does not, by itself, establish the legal basis for disclosure.
Exemptions: when minimum necessary does not apply
Minimum necessary is broad, but it is not universal. HHS guidance lists specific categories where the standard does not apply.
Disclosures to or requests by health care providers for treatment are exempt. For example, when a treating psychiatrist requests records from another provider to coordinate a claimant's treatment, minimum necessary does not constrain that disclosure or request. This exemption does not automatically cover an independent medical-legal evaluation merely because the evaluator is a health care professional, and it does not remove separate protections for psychotherapy notes.
Other exceptions include disclosures to the individual, uses or disclosures under a valid individual authorization, uses or disclosures required by other law, required disclosures to HHS for Privacy Rule enforcement, and uses or disclosures required for compliance with HIPAA's Administrative Simplification Rules. An authorization defines the permitted scope; a legal requirement defines what must be disclosed. Neither is permission to release unrelated information beyond that scope.
Workers' compensation requires particular care. Under HHS workers' compensation guidance, disclosures required by state or other law are exempt from minimum necessary and must be limited to what that law requires. Disclosures under a valid individual authorization are also exempt from minimum necessary.
Disclosures permitted under the workers' compensation provision at 45 CFR 164.512(l), or made for payment, generally remain subject to minimum necessary. HHS explains that information may be shared to the full extent authorized by applicable workers' compensation law. When a state workers' compensation or other public official represents that the requested information is the minimum necessary for the intended purpose, reasonable reliance on that representation is permitted. This is not a blanket reliance rule for every claims administrator or private requester.
How to implement minimum necessary: policies, roles, and protocols
Turning the regulation into daily practice starts with a written policy identifying the workforce members who need access to PHI, the categories each needs, and appropriate access conditions. A vague statement such as “staff may access records as needed” does not explain those distinctions.
An illustrative matrix should be adapted to the entity's actual functions and lawful access needs:
- Billing staff: demographic, coding, and supporting clinical information reasonably needed for their assigned billing functions.
- Claims reviewers: information reasonably necessary for the claim-related purpose, subject to the applicable legal basis and access conditions.
- Clinical reviewers and QME/AME physicians: records lawfully supplied for the evaluation, including an entire record when justified or when an applicable exception governs. The evaluator's title alone does not authorize access.
- Legal staff and paralegals: information needed for their assigned work, within the governing authorization, legal process, and confidentiality restrictions.
A subpoena's wording is not the whole analysis. HHS explains that a covered entity not party to litigation must meet specified conditions before responding to a subpoena without a court order, such as obtaining satisfactory assurances about notice or a qualified protective order, or taking the prescribed steps itself.
For recurring disclosures subject to minimum necessary, define the information released, recipient category, purpose, and conditions in a standard protocol. Review requests that fall outside those protocols individually against reasonable criteria.
Pro Tip: Establish non-routine review criteria before an unusual request arrives. Record the purpose and legal basis separately from the clinical information supporting the requested scope.
A disclosure-decision log can record what was requested, what was released, the legal basis, the reviewer, and the applicable protocol or individualized reasoning. This is a recommended operational control, not a claim that the minimum necessary standard prescribes those fields for every disclosure. Separate documentation, accounting, and security requirements may also apply.
Training should match workforce duties. Under 45 CFR 164.530(b), covered entities must train new workforce members within a reasonable period after joining and affected members within a reasonable period after material policy changes, and document that training. An annual refresher and policy review can be useful internal practices; they are not fixed intervals prescribed by the minimum necessary standard.
Business associates, vendors, cloud services and BAAs: limiting PHI downstream
An outside vendor generally is a business associate when its functions or services for a covered entity involve creating, receiving, maintaining, or transmitting PHI, subject to the definition and applicable exceptions. The relationship depends on what the vendor does, not its marketing label. Subcontractors performing those functions for a business associate can also be business associates. HHS business-associate guidance explains the framework and exceptions.
Under the HHS sample business associate agreement provisions, a BAA must establish permitted and required uses and disclosures, restrict other uses and disclosures except as required by law, require appropriate safeguards, and require reporting of unauthorized uses or disclosures, including breaches of unsecured PHI. It must also address other required matters, including applicable subcontractor obligations. A contract cannot authorize activity that would violate the Privacy Rule if performed by the covered entity, except for the limited purposes the rule permits.
Reasonable reliance is available when a professional who is the covered entity's workforce member or business associate requests PHI to provide professional services and represents that the request is the minimum necessary for the stated purpose. Reliance must be reasonable under the circumstances; it is not automatic approval of any vendor request. See 45 CFR 164.514(d)(3)(iii).
Cloud and AI vendors deserve specific attention. A cloud service provider storing encrypted PHI for a covered entity or business associate remains a business associate even if it lacks the decryption key. HHS cloud computing guidance explains that the required BAA and applicable Security Rule safeguards still apply.
A practical vendor due-diligence checklist:
- Confirm that the BAA establishes permitted uses and disclosures and meets all applicable contract requirements.
- Ask whether customer PHI, prompts, or outputs are used for model training or improvement, and seek explicit contractual restrictions matching the intended use. A no-training clause is a contractual safeguard, not a universally prescribed HIPAA clause.
- Verify encryption protections, incident-reporting procedures, and contractual notification timelines.
- Confirm that applicable subcontractor restrictions and safeguards flow down to downstream processors.
Special cases: psychotherapy notes, entire-record requests, and research
Psychotherapy notes have protections beyond those for ordinary psychiatric records. HHS explains that these are a mental health professional's notes documenting or analyzing counseling-session conversations, maintained separately from the rest of the medical record. The definition excludes medication prescribing and monitoring, session times, treatment modalities and frequencies, clinical test results, and summaries of diagnosis, functional status, treatment plans, symptoms, prognosis, and progress.
Most uses and disclosures of psychotherapy notes require the individual's authorization, subject to the specific exceptions in 45 CFR 164.508(a)(2). Even disclosure to another treating provider generally requires authorization. A psychiatric QME should not assume that a release covering ordinary progress notes or medication records also covers separately maintained psychotherapy notes. An authorization for psychotherapy notes generally cannot be combined with an authorization for other records.
When minimum necessary applies, an entire-record use, disclosure, or request must be specifically justified as reasonably necessary for its purpose. HHS explains that an entity can document that justification for identified purposes in its policies, rather than justify every qualifying disclosure separately. An apportionment question may explain why historical records matter, but it does not automatically authorize access to every record or override other confidentiality protections.
The 2016 NCVHS letter to the HHS Secretary recommended that HHS clarify adequate justification for entire-record requests through examples and use cases. It is an advisory recommendation, not a separate requirement for a particular approver or access-log format.
Research access follows its own track. An Institutional Review Board or Privacy Board can waive authorization under defined conditions. A covered entity may reasonably rely on compliant research documentation or representations as establishing minimum necessary for the research purpose. That reliance remains conditional; it is not a blanket exemption for research. See the HHS FAQs.
Common compliance errors, enforcement, and breach-reporting implications
One preventable error is treating “the complete file” as a sufficient explanation when minimum necessary applies. Another is assuming that narrowing the file makes an otherwise unauthorized disclosure lawful. Policies should address both questions: whether disclosure is permitted and what scope is appropriate.
An inadequate BAA can create a compliance problem, but the absence of a contractual restriction does not erase the business associate's independent HIPAA obligations.
For cross-jurisdiction reading, a Swedish compliance vendor's news summary discusses an Italian GDPR case involving medical photos on social media. It is background context, not HIPAA guidance or evidence of a U.S. minimum necessary violation.
Not every minimum necessary lapse requires breach notification. However, an impermissible use or disclosure is presumed to be a breach unless an applicable exception applies or the covered entity or business associate demonstrates a low probability that the PHI was compromised. Notification requirements concern breaches of unsecured PHI. HHS breach guidance identifies at least four risk-assessment factors: the nature and extent of the PHI, the unauthorized recipient, whether the information was actually acquired or viewed, and mitigation.
Stop further impermissible disclosure, preserve the relevant facts, involve the responsible privacy personnel, and document the notification decision. HHS permits providing the required notifications without first performing the low-probability risk assessment.
Practical checklist and policy template elements for implementers
A practical implementation plan combines required policies with clearly identified internal controls:
- Identify the legal basis for each common disclosure type and whether minimum necessary applies.
- Document workforce access categories, PHI categories, and access conditions.
- Establish protocols for routine disclosures and requests subject to minimum necessary.
- Establish criteria and individual review for non-routine disclosures and requests; assign internal responsibility for that review.
- Use a disclosure-decision log where useful to record purpose, authority, scope, reviewer, and protocol or individualized reasoning.
- Review BAAs for all applicable requirements and evaluate additional contractual protections for cloud and AI services.
- Train the workforce as required and update policies when necessary. Choose a periodic review schedule appropriate to the practice.
HHS deliberately made the standard flexible enough to accommodate different operations. A generic template still needs adjustment for the entity's actual workforce, referral relationships, and disclosure purposes.
For non-routine requests, the justification should identify the purpose, requester, lawful disclosure basis, and scope. An illustrative entry is: “Psychiatric treatment records released to QME [name] for the evaluation in claim [number], following request dated [date]. Disclosure authority: [applicable authorization, law, or other permitted basis]. Scope and rationale: [records and reasons]. Separately maintained psychotherapy notes withheld unless a valid psychotherapy-note authorization or an applicable exception supports release.” This entry documents a decision; it is not itself an authorization or a complete legal form.
BAA review should include permitted uses, subcontractor obligations, incident and breach reporting, and any negotiated restrictions on model training. Those topics do not replace the full set of applicable BAA requirements. Quarterly log spot checks and an annual full policy review are possible internal review schedules, not fixed intervals prescribed by the minimum necessary standard.
Defensibility and documentation in practice
A disclosure decision may later need to be explained to a privacy officer, regulator, or court. The decision must be lawful, and the documentation should make its basis understandable.
For a psychiatric QME evaluation, page citations can help identify the clinical material relevant to a stated purpose, such as a prior diagnosis or medication history. They should sit alongside the disclosure authority and scope rationale, not substitute for them.
That is the practical argument for citation discipline: the reviewer can locate the supporting record without reconstructing it from memory. A cited summary can support verification, but neither a citation nor a summary establishes legal permission to disclose the underlying information.
Using ChartInsight™ to document minimum necessary decisions
Documenting the clinical context for a record request can involve locating specific details across a large, multi-provider file. ChartInsight™ produces page-cited chronologies, narrative summaries, and medication lists, alongside extracted vitals. These outputs can support review and documentation of information already lawfully available to the reviewer.
- Source-page citations in supported outputs open the relevant page in the built-in PDF viewer.
- Custom templates help standardize medical-legal reports and peer reviews.
- DOCX and PDF exports preserve page citations, supporting verification after export.
- According to its security page, ChartInsight™ executes BAAs, has undergone a SOC 2 Type II examination, uses AES-256 encryption at rest and TLS 1.3 in transit, and does not use customer records, prompts, extracted information, or outputs to train or improve AI models.
Those controls do not establish a customer's legal authority to upload or disclose a particular record. Reviewers still read the full record; the workflow benefit is less manual chronology assembly and citation work, not reading fewer pages.
See how ChartInsight™ works or book a demo to review the citation workflow and vendor safeguards.
Sources
This article draws on the following guidance and regulations. The NCVHS letter is an advisory recommendation, not binding law.
This article is general information, not a substitute for advice from a qualified lawyer. Consult a qualified legal professional about the applicable federal, state, and record-specific requirements before implementing a disclosure protocol.
- HHS: Minimum Necessary Requirement
- HHS: Minimum Necessary FAQs
- HHS: Disclosures for Workers' Compensation Purposes
- HHS: Business Associates
- HHS: Sample Business Associate Agreement Provisions
- HHS: Guidance on HIPAA and Cloud Computing
- HHS: Extra Protections for Psychotherapy Notes
- HHS: Subpoenas Without a Court Order
- HHS: Breach Notification Rule
- 45 CFR 164.514: Minimum Necessary Implementation Specifications
- 45 CFR 164.508: Authorization Requirements
- 45 CFR 164.530: Administrative Requirements
- NCVHS: 2016 Recommendation on the HIPAA Minimum Necessary Standard
FAQ
What is the HIPAA minimum necessary requirement?
Where it applies, it requires covered entities and business associates to make reasonable efforts to limit uses, disclosures, and requests for PHI to the amount reasonably needed for the intended purpose. Exceptions include disclosures to or requests by providers for treatment, disclosures to the individual, authorized uses and disclosures, and disclosures required by law. Minimum necessary does not itself authorize disclosure.
What is the new HIPAA rule in 2026?
There is no single rule accurately described as “the new HIPAA rule in 2026.” The minimum necessary standard is addressed at 45 CFR 164.502(b) and 164.514(d). Identify the specific rulemaking and effective or compliance dates when evaluating a claimed change, and consult HHS and the Federal Register rather than relying on an unspecific headline.
What qualifies as minimum necessary PHI?
It is the PHI reasonably needed to accomplish a defined purpose. For workforce access, the entity identifies who needs access, the categories of PHI needed, and appropriate access conditions. When the standard applies, an entire record must be specifically justified as reasonably necessary; an appropriate policy can document that justification for identified purposes.
What are the 5 basic rules of HIPAA?
There is no single official five-item checklist that substitutes for the applicable HIPAA requirements. HHS discusses the Privacy, Security, Breach Notification, and Enforcement Rules, while HIPAA's Administrative Simplification framework also includes transaction-related requirements. Minimum necessary is a Privacy Rule standard, not a separate rule in a simplified five-rule framework.

