Draft for Nick’s review. This note is a working draft in Nick’s voice. It is not published advice, and it is not a legal, procurement, or technical opinion until he edits it.
The coordinated-care rule is a feed problem
OCR’s HIPAA final rule on coordinated care is effective January 18, 2027, with compliance due July 17, 2027. For an HIE, a Medicaid agency, or a health plan, the work is in the workflow and the agreement.
On November 16, 2026, HHS OCR finalized a HIPAA Privacy Rule aimed at coordinated care and individual engagement. I am planning against an effective date of January 18, 2027 and a compliance date of July 17, 2027. Confirm both against the Federal Register before they land in a project plan. What follows is an operator’s reading. It is not legal advice.
The rule will be summarized, fairly, as a privacy update. A stronger individual right of access, including electronic PHI through a personal health app when the covered entity can produce it in that form. A shorter clock on access requests, reported as fifteen calendar days with a single extension. Clearer room for care coordination and case management, including disclosures to social service agencies, community-based organizations, and similar third parties. Less ceremony around the notice of privacy practices, including the end of the good-faith attempt to collect a written acknowledgment.
That summary is necessary. It is also incomplete when the disclosure in question is not a release-of-information desk. When the disclosure is an ADT feed, an encounter alert, a care-management file, or a community partner who has never seen the notice, the rule is an operations problem with a date on it.
I would rather have three questions answered for one real workflow than a crosswalk that covers every workflow and touches none of them.
Who in the current exchange is a covered entity, who is a business associate, and who is a community partner the rule now contemplates. A participation agreement written for treatment, payment, and health care operations does not automatically answer a social-care referral. The agreement has to match the disclosure.
When the record a person wants is assembled from more than one source, who produces the copy. The right of access sits with the covered entity. An HIE that acts as a business associate needs the business associate agreement to say which party actually produces it. Pointing at the vendor has never been a satisfying answer. This rule is a reason to read those agreements again.
Which care-coordination flow already moves data, and which one has been held because the old rule felt ambiguous. Permission is not a feed. A feed still has to be timely, limited to what the recipient needs, and aimed at someone who will use it. The groups that will be ready in July are the ones that pick a transition alert, a health-plan care-management file, or a closed-loop referral and trace it: sender, recipient, minimum necessary, identity, agreement.
July 17, 2027 will arrive on a Saturday, and the following Monday the question will be the same. A memo that never touches a feed will still be unfinished.
Document behind this note: HHS OCR announcement, HIPAA Privacy Rule changes to support coordinated care, November 16, 2026.
Write to Nick Regier if this is the decision in front of you.