Skip to main content
Patient Protect circular logo mark in purple and white used for site navigationPatient Protect
Compliance Operations

HIPAA Care Coordination After the 2026 Final Rule: What Changed, and What Didn't

The 2026 HIPAA final rule, not yet in effect, permits sharing PHI with community organizations for individual care coordination. Minimum necessary is unchanged.

Patient ProtectPatient Protect Editorial Team·November 17, 2026·18 min read

Written and reviewed by the Patient Protect team — Joseph A. Perrin, CTO (federal infrastructure background, platform security architect), Angie Perrin, CSO (CHPC, 10+ years clinical practice), and Alexander Perrin, CEO (20 years enterprise SaaS, primary author of the Secure Care Research Institute research program). See editorial standards.

Share
HIPAA Care Coordination After the 2026 Final Rule

Most of what the final rule does for care coordination is clarification. HHS re-punctuated one definition, wrote a permission it says already existed into the regulatory text, and declined three 2021 proposals that would have changed how much a practice shares and on what standard. Reading the rule as loosening minimum necessary, or as obliging a practice to share, produces the wrong policy.

The rule is on public inspection as Federal Register document 2026-23429. It takes effect 60 days after publication, compliance is required 240 days after publication, and HHS will not act on the new requirements before then. Our page on the current HIPAA Privacy Rule covers the rules in force today. Our guide to the 2026 HIPAA Privacy Rule final rule covers access, fees and the Notice of Privacy Practices. Quotations here are from the public-inspection text; where we give Patient Protect's reading instead, we say so.

What the final rule changed for care coordination

  • Health care operations (§ 164.501) is re-punctuated so individual-level and population-based care coordination and case management both plainly count.
  • New § 164.506(c)(6) permits disclosures to community and social-service organizations, including home and community based services (HCBS) providers, for individual-level care coordination and case management.
  • New § 164.512(m) permits disclosures to relay-service communications assistants, and relay providers are excluded from the business associate definition for relay services.
  • Not finalized: a minimum necessary exception, a "good faith belief" standard and a "serious and reasonably foreseeable" threat standard.

Care-coordination changes in the 2026 final rule

  • Disclosures to community and social-service organizations

    45 CFR 164.506(c)(6) (new)
    Rule today:
    Permitted under existing treatment and operations rules, but often misread.
    Final rule:
    Expressly permits disclosure to social services agencies, community-based organizations, home and community based services providers and similar third parties for individual-level care coordination and case management.
    What a practice does:
    Treat it as a permission, not a duty. Minimum necessary applies where it applied before, and stricter state law and Part 2 still govern.
    Applies from:
    Effective date
  • Health care operations: care coordination clarified

    45 CFR 164.501
    Rule today:
    Commas in the definition let some read care coordination as population-based only.
    Final rule:
    Semicolons confirm that individual-level and population-based care coordination and case management are both health care operations. HHS calls this a clarification, not a substantive change.
    What a practice does:
    Mostly relevant to health plans. No new step for a provider practice.
    Applies from:
    Already HHS's position (restated)
  • Telecommunications Relay Services

    45 CFR 164.512(m) (new); 160.103
    Rule today:
    Relay providers sat awkwardly in the business associate definition.
    Final rule:
    Covered entities and business associates may disclose PHI to a TRS communications assistant as necessary to conduct covered functions, and TRS providers are excluded from the business associate definition for that service.
    What a practice does:
    No BAA is needed with a relay provider for relay calls. Minimum necessary still applies.
    Applies from:
    Effective date
  • Armed Forces permission extended to all Uniformed Services

    45 CFR 164.512(k)(1)
    Rule today:
    Applied to Armed Forces personnel.
    Final rule:
    Applies to all Uniformed Services personnel, which adds the USPHS and NOAA Commissioned Corps.
    What a practice does:
    Rarely relevant to a private practice.
    Applies from:
    Effective date

“Rule today” and “Final rule” paraphrase the regulation. “What a practice does” is Patient Protect’s reading of the work involved, not text from the rule.

Health care operations: punctuation HHS calls a clarification

In paragraph (1) of the definition, commas separated the activities that followed "population-based activities relating to improving health or reducing health care costs," which let some readers treat "population-based" as qualifying case management and care coordination too. HHS says it never read the definition that way. The final rule turns the commas into semicolons:

population-based activities relating to improving health or reducing health care costs; protocol development; case management and care coordination; contacting of health care providers and patients with information about treatment alternatives; and related functions that do not include treatment.

HHS "does not consider this clarification to be a substantive modification because the final rule does not alter our interpretation of the definition." It confirms that health care operations "encompasses all care coordination and case management activities by health plans and covered health care providers, whether individual-level or population-based."

The change matters mostly to health plans. In HHS's long-standing example, a doctor's-office nurse calling a patient about follow-up care is doing treatment, and a health plan's nurse making the same call is doing health care operations. For a provider practice, the relevant line is that "covered entities may disclose PHI to health plans for these purposes," under the permission for another covered entity's operations at § 164.506(c)(4), "when the applicable conditions are met." Those disclosures are subject to minimum necessary.

Patients can still request restrictions under § 164.522(a). A practice generally need not agree, but it is required to accept a request not to disclose to a health plan for payment or operations when the disclosure is not otherwise required by law and the PHI relates solely to an item or service paid for in full by the patient, or by someone other than the plan on the patient's behalf.

The new permission at § 164.506(c)(6)

(6) A covered entity may disclose an individual's protected health information to a social services agency, community-based organization, home and community based services provider, or similar third party that provides health or human services to specific individuals, for individual-level care coordination and case management activities (whether such activities constitute treatment or health care operations as those terms are defined in § 164.501) with respect to that individual.

HHS adopted the 2021 proposal "without modification."

Who can receive PHI under it

The rule defines none of the four categories. HHS worried that definitions "could inadvertently limit the application of this provision in varied clinical and community contexts." The recipient "does not have to be a health care provider and may instead provide health-related social or other supportive services, such as food or sheltered housing needed to address health risks and conditions." HHS's examples include a senior center helping arrange a home aide, a social service agency arranging housing for a patient leaving long-term care, and a food bank providing nutrition support for a referred patient with diabetes.

HCBS providers are a mixed group. HHS notes that some are health care providers under HIPAA's definition, some provide only human services such as non-medical transportation, and some provide both. Whether a recipient fits is the practice's determination: covered entities "remain responsible for determining whether a disclosure falls within treatment or health care operations and whether the recipient is engaged in individual-level care coordination or case management activities."

What it covers, and what it does not require

The permission reaches only activities "with respect to that individual." HHS excluded population-based activities so that disclosures remain "tied to the care of a specific individual." Population-based disclosures are still possible where § 164.506(c)(1) or another provision permits them, but (c)(6) is not the basis.

HIPAA requires no authorization or consent for a (c)(6) disclosure. HHS declined the conditions commenters proposed, including consent, advance notice beyond the Notice of Privacy Practices, an opportunity to object, care-plan documentation, screening assessments, written agreements with the recipient, and limiting recipients to organizations with particular privacy or security measures. A practice may still ask: a covered entity "is still permitted, but not required, to obtain an individual's consent to disclose the individual's PHI for TPO."

A clarification, and when it applies

HHS says "the Privacy Rule has long permitted disclosures of PHI to such entities for treatment or, in certain circumstances, health care operations," and that (c)(6) adds express language "to provide greater clarity about the scope of these existing permissions." What prompted it was uncertainty: HHS reports that some covered entities "are requiring authorizations for such disclosures."

The rule does not separately say when a permission starts to operate; its dates are framed around requirements. Our reading is that (c)(6), the definition change and the relay permission are part of the regulatory text from the effective date, as the change register above labels them. Given HHS's account of the existing permissions, the practical gap is small. Nothing that was not finalized becomes available on either date.

A permission, not a duty

Section 164.506(c)(6) says a covered entity "may disclose." It is not among the required disclosures in § 164.502(a)(2): disclosures to the individual under §§ 164.524 and 164.528, to a person the individual designates under § 164.524, and to the Secretary for compliance investigations. A request from a community organization creates no HIPAA obligation to send PHI. A patient's own access request directing a copy to that organization is a separate matter, governed by § 164.524.

HHS also "generally encourages covered entities to take an individual's expressed privacy preferences into consideration before making permitted disclosures," and a restriction a practice agrees to binds it.

Information blocking is a separate question. HHS says § 164.506(c) "does not prevent or relieve covered entities from complying with the information blocking regulations," which carry their own exceptions, including for reasonable and necessary practices that advance patients' privacy interests. Whether a particular refusal raises an information blocking issue is analyzed under those regulations, not under HIPAA.

What the permission does not change

Minimum necessary

"This final rule does not alter the minimum necessary requirements." As HHS restates § 164.502(b), disclosures to or requests by a health care provider for treatment are outside the standard, while disclosures "for treatment to third parties that are not health care providers and for health care operations remain subject to the minimum necessary standard." Where it applies, "a covered entity must take reasonable steps to limit the disclosure of PHI to the minimum necessary to accomplish the intended purpose."

A food bank or a housing agency is not a health care provider, so a disclosure to it is subject to minimum necessary. HHS's own example draws the line: a health plan whose diabetes program is run by a senior center may share "the member's demographic information and relevant diagnosis," and may not share "unrelated diagnoses and other nongermane health information." We would apply the same test to a practice's referral. A food bank needs what bears on the patient's diet, not the problem list. Our reading of § 164.502(b) as HHS describes it: when the recipient is itself a health care provider receiving PHI for its treatment of the patient, the treatment exception applies.

Exchanging through a health information organization requires a BAA with it, and for disclosures subject to the standard, HHS says that agreement has to limit the organization's disclosures accordingly. More in our guide to the HIPAA minimum necessary standard.

Business associate agreements

"Section 164.506(c)(6) does not impose any new requirements regarding business associate agreements." A BAA is required only when the recipient meets the definition of a business associate. Where the organization is "engaged by a covered entity to provide health-related services on behalf of the covered entity," the BAA must be in place before the disclosure. Where it is "providing services to the individual on its own behalf," no BAA is required.

Our examples: a food bank feeding your patient works for the patient. A care-navigation service you pay to follow up with your patients works for you. Our business associate agreement checklist covers the agreement itself.

Responsibility after the disclosure

Commenters asked for a safe harbor in case a recipient that HIPAA does not regulate mishandled the information. HHS said none was needed, because "a covered entity is not liable for subsequent breaches or improper use of health information by the person who receives it, including a person who is not regulated under HIPAA."

That covers what the recipient does next, not the disclosure itself. Practices remain subject to "the obligation to implement reasonable safeguards, to limit disclosures to the minimum necessary PHI as applicable, and to determine whether a recipient is acting as a business associate."

Law enforcement and child welfare

The permission "does not permit disclosures of PHI to law enforcement or child welfare agencies for law enforcement or investigatory purposes." The existing provisions "continue to apply independently." Disclosures to child welfare or protective services agencies remain permitted only under provisions such as those for public health activities and reports of child abuse, domestic violence and neglect. A law enforcement disclosure without authorization still has to be made pursuant to process and as otherwise required by law, or fall under another express permission.

State law, Part 2 and your notice

Where state or other federal law is more protective and a practice can comply with both, as with a state law requiring authorization for a disclosure HIPAA permits without one, the state law is not preempted and still applies. HHS: "nothing in this final rule affects the obligations of covered entities to comply with applicable state or other Federal laws that restrict the disclosure of sensitive information." Covered entities that are Part 2 programs must still "obtain patient consent when using or disclosing Part 2 records for treatment, payment, and health care operations purposes."

HHS also says (c)(6) disclosures "should remain consistent with the covered entity's NPP." The notice already has to describe, with at least one example, the disclosures a practice may make for treatment, payment and operations, and the final rule separately revises its required content by the compliance date. Our recommendation: when you revise it, read the treatment and operations language as a patient whose information is going to a housing agency would. See our Notice of Privacy Practices guide.

What the final rule did not finalize

Three of the 2021 proposals that bore on care coordination were not finalized.

Finalized

The changes with the most work attached.

  • 15-calendar-day access deadline 45 CFR 164.524(b)(2)
  • One extension of up to 30 calendar days 45 CFR 164.524(b)(2)(ii)
  • Clarifying a request does not stop the clock 45 CFR 164.524(c)(3)
  • When access must be free 45 CFR 164.524(c)(4)(ii)
  • Fee schedule for access and authorization copies 45 CFR 164.525 (new)
  • New Notice of Privacy Practices content 45 CFR 164.520(b)
  • Written acknowledgment no longer required 45 CFR 164.520(c)(2), (e)
  • Business associates and access requests 45 CFR 164.502(a)(4)(ii); 164.532(e)(3)

Proposed in 2021, not finalized

Each was proposed, or asked about, in January 2021. None of them is law.

  • An exception to the minimum necessary standard for disclosures for individual-level care coordination and case management.

    Outcome: Not finalized. The minimum necessary standard is unchanged.

    Treatment disclosures between providers were already outside minimum necessary. Disclosures to plans and non-provider third parties still have to be limited to what is needed.

  • Replacing "exercise of professional judgment" with a "good faith belief" standard, with a presumption of good faith, across several disclosure permissions.

    Outcome: Not finalized. The existing professional-judgment standards stand.

    Policies and training that describe a good-faith standard for family and emergency disclosures are describing a proposal.

  • Changing "serious and imminent threat" to "serious and reasonably foreseeable threat" in § 164.512(j).

    Outcome: Not finalized. "Serious and imminent" remains the standard.

    A threat-disclosure policy written to the proposal would permit disclosures the rule does not.

The minimum necessary exception

The proposal would have created an exception to minimum necessary for disclosures to, or requests by, a health plan or covered health care provider for individual-level care coordination and case management. HHS's decision: "This final rule does not adopt the proposed exception to the minimum necessary standard for individual-level care coordination and case management."

Because the exception and the permission were proposed together, it is easy to assume they were finalized together. A policy or training slide saying minimum necessary no longer applies to care coordination is describing the 2021 proposal.

HHS's reasons:

  • An exception "would erode individuals' confidence in the privacy of their PHI and their willingness to fully engage with the health care system."
  • The definition change and the new permission meet the same goals.
  • HHS was not convinced the benefits would "outweigh the interests of individuals in limiting the PHI that is shared with health plans."
  • Sharing beyond the minimum raises "the risk of unintended adverse consequences (e.g., more PHI exposed in the event of a breach), regardless of who receives the PHI."
  • Existing restrictions already "strike an appropriate balance."

Commenters, HHS reports, were evenly split.

The "good faith belief" standard

Several permissions rest on the provider's exercise of professional judgment, including the disclosures to family and caregivers in § 164.510(b) when a patient is present, absent or incapacitated. The 2021 proposal would have replaced "exercise of professional judgment" with "good faith belief" in five provisions, backed by a presumption of good faith that evidence of bad faith could overcome.

HHS: "The Department is not finalizing the proposed changes to the standards for good faith and professional judgment in 45 CFR 164.502 and 164.510-514." It concluded that a good faith standard "likely would introduce ambiguity without improving outcomes," was concerned the proposals could "increase complexity and burden for covered entities while chilling access to care," and agreed that these decisions "may require the exercise of clinical expertise." It intends to emphasize outreach and technical assistance instead.

Two points matter to practices treating mental health conditions. Neither § 164.510 nor § 164.512 "requires a legal determination of incapacity," and a patient's inability to make these decisions "may be transient or situational." A diagnosis of serious mental illness, "by itself, does not determine whether an individual can make independent decisions." Where Part 2 also applies, these permissions "do not negate Part 2's general requirement to obtain a patient's written consent for the disclosure of Part 2 records."

The "serious and reasonably foreseeable" threat standard

Section 164.512(j) permits a covered entity, consistent with applicable law and standards of ethical conduct, to use or disclose PHI when necessary to prevent or lessen a serious and imminent threat to the health or safety of a person or the public, subject to conditions. The proposal would have substituted "serious and reasonably foreseeable" and given heightened deference to workforce members with specialized training. HHS declined because the change "could increase uncertainty about when disclosures are appropriate," and referred providers to OCR's guidance on the serious and imminent standard for patients with mental health conditions and substance use disorder.

Telecommunications Relay Services

New § 164.512(m) permits a covered entity to disclose PHI to a relay communications assistant "as necessary to conduct covered functions," and a business associate to do the same on a covered entity's behalf whether or not its BAA addresses relay services. The business associate definition now excludes "a provider of telecommunications relay services, as defined in 47 U.S.C. 225(a)(3), with respect to enabling communications through services regulated under 47 CFR part 64."

Earlier HHS guidance covered a practice calling a patient through relay, reasoning that the patient could agree or object at the start of the call. That did not reach a staff member who is deaf, hard of hearing or deaf-blind, or who has a speech disability, using relay at work. The new text covers both. Minimum necessary still applies, and no BAA is needed with a relay provider for relay services.

Putting it to work in a small practice

This section is Patient Protect guidance, not text from the rule. To see where your practice stands across the whole final rule, take the free 2026 Privacy Rule readiness check.

Who can share what with whom

Recipient and purpose What permits it What limits it
Another health care provider, for its treatment of the patient Treatment, § 164.506(c) Minimum necessary does not apply
A health plan, for its individual-level care coordination or case management The plan's operations, § 164.506(c)(4), when its conditions are met Minimum necessary; paid-in-full restriction requests
A social services agency or community organization helping the patient with food, housing, transportation or day programs § 164.506(c)(6) Minimum necessary, unless the recipient is a health care provider receiving it for treatment
Any of these, for a population-level program Not (c)(6); only another provision that permits it Check before sending a list
Law enforcement or child welfare, for an investigation Not (c)(6); only the existing provisions for those purposes Route to your privacy officer
Family or caregivers of a patient who is absent, incapacitated or in an emergency § 164.510(b)(3), professional judgment of the patient's best interests Relevant PHI only
Someone reasonably able to prevent or lessen a serious and imminent threat § 164.512(j) Applicable law and standards of ethical conduct
A relay communications assistant § 164.512(m) Minimum necessary; no BAA with the relay provider

Over every row: a BAA only when the recipient works on your behalf, and stricter state law or Part 2 can require consent that HIPAA does not.

Document the decision

The rule does not make documentation a condition of a (c)(6) disclosure. We still recommend a short note for each disclosure to a recipient that is not a health care provider, because the rule leaves these judgments to you and a note made at the time is the only record of them:

  • the recipient, and what kind of organization it is;
  • the individual-level purpose, and whether you treated it as treatment or operations;
  • what you sent, and why that was the minimum necessary;
  • whether the recipient works for the patient or for you, and if for you, the BAA;
  • whether state law or Part 2 required consent, and whether you had it;
  • any preference the patient expressed or restriction you agreed to;
  • who decided.

For organizations you refer to often, write down once what a standard referral contains, so minimum necessary is decided deliberately per partner rather than at the front desk each time.

What to train

  • Individual-level coordination with a community or social-service organization needs no HIPAA authorization.
  • Send what the recipient needs for its part, and no more. Lists and program-wide sharing go to the privacy officer.
  • Requests from police, investigators or child welfare go to the privacy officer. Paragraph (c)(6) is not a basis for disclosures for law enforcement or investigatory purposes, and abuse and neglect reporting follows your existing policy.
  • Check consent requirements before sharing substance use disorder records or information your state treats as sensitive.
  • Disclosures to family and caregivers rest on professional judgment. Threat disclosures require a serious and imminent threat.

What to change in your policies

  • Name § 164.506(c)(6) in your uses-and-disclosures policy, with its limits: individual-level only, minimum necessary by type of recipient, never for law enforcement or investigations.
  • Remove language describing a care-coordination exception to minimum necessary, a good faith standard or a reasonably foreseeable threat standard.
  • If you require a signed authorization for every disclosure to a community organization, decide whether to keep doing so. State law or Part 2 may require it for some records; for the rest it is your choice.
  • List community organizations that work on your behalf with your business associates. Organizations working for the patient do not belong there.
  • Drop any BAA requirement for relay providers, and fold the notice review into the revisions due by the compliance date.

What Patient Protect does

Patient Protect is a security-first HIPAA compliance platform for independent healthcare practices, combining compliance program management with technical controls in one system. For the work in this article:

  • Policies & Procedures gives you policy and procedure starters to revise into your own, with version history and workforce acknowledgment tracking, so you can see who has acknowledged a revised care-coordination policy.
  • HIPAA Foundations Training trains the workforce and records each person's completion.
  • Vendor & BAA Governance records your business associates and the state of each agreement, which is where an organization working on your behalf belongs.
  • Smart Referrals handles referrals between provider offices.
  • Compliance Evidence & Records holds the policy versions, training records and other documents your program produces.

None of it makes the disclosure decision, and none of it makes a practice compliant by itself.

Frequently Asked Questions

Can a practice share PHI with a community-based organization without the patient's authorization?

Yes, under HIPAA, for individual-level care coordination or case management for that patient. The final rule's new § 164.506(c)(6) says so expressly, and HHS says these disclosures were already permitted for treatment or, in certain circumstances, operations. Minimum necessary applies when the recipient is not a health care provider, and stricter state law or Part 2 can still require consent.

Did the 2026 final rule create a minimum necessary exception for care coordination?

No. HHS proposed one in 2021 and did not adopt it. Treatment disclosures to health care providers remain outside the standard, as before; treatment disclosures to non-provider third parties and disclosures for health care operations remain subject to it.

Do I need a BAA with a food bank or housing agency I refer patients to?

Not because of the referral. Section 164.506(c)(6) adds no BAA requirement, and an organization serving the patient on its own behalf is not your business associate. A BAA is needed when the organization provides services on your behalf.

Does a social services agency's request oblige my practice to share?

No. Section 164.506(c)(6) is a permission; the rule says a covered entity "may disclose." A patient's own access request is a separate matter, and so are the information blocking regulations, which HHS says this provision does not relieve covered entities of.

Is my practice liable if the organization mishandles what we send?

Not for what the recipient does afterward, according to HHS. The practice remains responsible for the disclosure itself, including reasonable safeguards, minimum necessary and the business associate determination.

Did the final rule adopt a good faith standard for sharing with family?

No. The professional-judgment standards remain, and threat disclosures still require a serious and imminent threat. Neither the "good faith belief" standard nor the "serious and reasonably foreseeable" standard was finalized.


Sources. Federal Register document 2026-23429, public-inspection text: preamble sections IV.C through IV.F and IV.H, and the amended regulatory text at 45 CFR 160.103, 164.501, 164.506(c)(6) and 164.512(m). The full source list, with links and verification notes, is at the end of our guide to the 2026 HIPAA Privacy Rule final rule.

This article is general educational information, not legal advice. Evaluate HIPAA alongside applicable state law and other federal law, including 42 CFR Part 2.

Was this useful? Share it.

Share

Corrections & Updates

Healthcare security data changes as investigations progress, vendors update systems, and laws and guidance evolve. If you see something outdated, incomplete, or incorrect — or have newer source material — we’d appreciate hearing from you.

Submit a correction →

What would an OCR investigator find on your website?

Free 30-second scan — tracking pixels, security gaps, missing policies. See what’s visible before they do.

Subscribe to HIPAA Pulse.

Breach alerts, enforcement updates, and compliance intelligence — every two weeks.

© 2026 Patient Protect LLC. All rights reserved. Content may not be reproduced, scraped, or used to train AI models without written permission. Terms · DMCA