
On November 16, 2026, the U.S. Department of Health and Human Services (HHS) Office for Civil Rights (OCR) rolled out a major update to the HIPAA Privacy Rule. Officially titled HIPAA Privacy Rule: Changes to Support Coordinated Care and Case Management and Reduce Regulatory Burdens, the rule takes effect 60 days after publication (with a 180-day compliance window for covered entities).
If you run a medical practice, manage a hospital’s compliance program, or run a tech company supporting healthcare clients, you don’t need a 400-page legal brief—you need to know what actually changes on the ground. Here is a straightforward breakdown of the updates, why they matter, and how to prepare without getting tripped up by hidden compliance traps.
Why HHS Updated the Rule
For years, HIPAA has sometimes gotten in the way of common sense. Patients struggled to get quick access to their own medical records, clinics wasted hours collecting signatures on privacy forms nobody read, and care teams hesitated to share basic info with housing or food programs out of fear of triggering a federal violation.
The 2026 update fixes those bottlenecks. It shifts HIPAA toward faster patient access, smoother teamwork across care providers, and less unnecessary paperwork—all without lowering the bar for keeping patient data safe.
1. Patients Get Faster, Easier Access to Their Records
The updated rule puts patients firmly in the driver’s seat when it comes to their Protected Health Information (PHI):
Faster Turnaround Times: The old 30-day window to hand over medical records is gone. Covered entities now have to respond much faster—within 15 calendar days (with one 30-day extension allowed if truly needed).
Personal Health Apps: If a patient asks you to send their electronic health records directly to a personal health app on their phone, and your system has the capability to do it, you have to make it happen. (Note: Once that data lands in a consumer app the patient chose, HIPAA generally stops covering it—so clear patient education matters).
Clearer, Fairer Fees: The rule spells out when records must be provided completely free of charge and requires you to give patients advance notice of any copying fees before you process their request.
Sending Records to a Designee: Patients can direct you to send an electronic copy of their EHR records straight to someone they trust, like a family caregiver or another specialist.
Less Red Tape for Identity Checks: You can no longer put patients through overly burdensome identity-verification hoops just to see their own records. Security still matters, of course, but verification needs to be reasonable and user-friendly.
2. Easier Teamwork for Care Coordination
Good healthcare doesn’t happen in a vacuum. The new rule clears up confusion around sharing information to help patients get whole-person care:
Health Plans Have More Flexibility: Health plans can more easily use and share PHI to coordinate care and manage cases for their members.
Connecting Patients to Community Support: Covered entities are now expressly allowed to share PHI with social service agencies, community-based organizations, housing programs, behavioral health support teams, and food security initiatives to coordinate care. For example, a hospital discharge planner can share relevant health details with a local housing program to make sure a chronically ill patient isn’t discharged to the street.
3. Cutting Unnecessary Red Tape
To balance out the faster timelines on records requests, HHS stripped away several outdated administrative headaches:
Goodbye to Written Privacy Notice Signatures: You no longer have to make a "good faith effort" to get patients to sign an acknowledgment form saying they received your Notice of Privacy Practices (NPP).
Easier Communication for Patients with Disabilities: You can share PHI with Telecommunications Relay Services (TRS) communications assistants to help patients who are deaf, hard of hearing, deaf-blind, or have a speech disability—and you don't need a Business Associate Agreement (BAA) to do it.
Expanded Mission Readiness Sharing: Building on existing rules for the Armed Forces, disclosures of PHI to command authorities for mission readiness are now permitted for personnel in the U.S. Public Health Service (USPHS) Commissioned Corps and the NOAA Commissioned Corps.
What Covered Entities and Vendors Need to Do
Whether you are a hospital, clinic, health plan, or a vendor supporting them, the fundamentals haven't changed: even where red tape is cut, you are still 100% responsible for protecting PHI under the HIPAA Privacy, Security, and Breach Notification Rules.
Here is your quick prep list before the compliance deadline hits:
Update Your Medical Records Workflow: Make sure your Health Information Management (HIM) team and patient portals can handle the 15-day turnaround, personal health app exports, and advance fee notices.
Streamline Front-Desk Intake: Stop collecting NPP signature acknowledgments, update your privacy notices, and train front-desk staff on the simpler identity verification rules.
Refresh Care Coordination Policies: Give your case managers clear guidelines on sharing data safely with community and social service partners.
Audit Your Vendors and BAAs: Check your vendor list to make sure everyone who actually touches or stores PHI has a current Business Associate Agreement in place.
Conclusion & My Immediate Takeaways
The 2026 HIPAA update is a welcome dose of common sense. It speeds up patient access, supports real-world care coordination, and eliminates busywork that never actually protected patient privacy.
As you look at what to tackle first, here are my immediate takeaways from this Final Rule:
1. Eliminating the Notice of Privacy Practices (NPP) Acknowledgment Is an Instant Operational Win
For years, front-desk staff spent countless hours chasing patients for signatures acknowledging they received a Notice of Privacy Practices, only for compliance teams to scan, store, and audit those forms. Eliminating this requirement delivers immediate, practical savings:
Faster Patient Check-In: Less paperwork at the front desk means shorter lines and a smoother intake experience.
Lower Labor and Storage Costs: Staff no longer have to print, scan, index, and archive thousands of acknowledgment sheets.
Fewer Audit Headaches: Missing signature forms used to be one of the easiest ways to get dinged during a compliance audit—now that risk is off the table.
2. The TRS Exception Highlights Why Most Organizations Misclassify Business Associates
The Final Rule’s decision to exclude Telecommunications Relay Services (TRS) providers from the definition of a Business Associate is a great reminder of how often organizations get Business Associate classifications wrong.
My go-to, simplified description of a Business Associate has always been: a subcontractor you pay for services using PHI provided by you or your clients on your behalf. Under official HHS rules (45 CFR 160.103), any outside person or company that creates, receives, maintains, or transmits PHI on behalf of a covered entity (or another business associate) is generally a Business Associate.
In practice, most healthcare organizations under-classify vendors rather than over-classify them. They frequently overlook everyday vendors that regularly store or access PHI, including:
Cloud hosting providers and managed service providers (MSPs)
IT support companies and backup/disaster recovery vendors
Document shredding companies with access to PHI
EHR support contractors and medical transcriptionists
Release-of-information (ROI) vendors, billing/revenue cycle companies, and data analytics firms
(Important note: Cloud service providers that store electronic PHI are Business Associates—even if the data is encrypted—and are not protected by the conduit exception.)
Not Every Entity That Encounters PHI Is a Business Associate
To classify vendors accurately, you have to look at the function performed, the nature of access, whether PHI is maintained, and whether a specific regulatory exception applies. Under HHS guidance, the "conduit exception" is intentionally narrow—it applies only to organizations that merely transport information without accessing it on a routine basis.
Examples of business types that touch or transmit PHI during healthcare operations, yet are exempt from being Business Associates, include:
The U.S. Postal Service (USPS)
Private Couriers (such as FedEx, UPS, and DHL) when acting solely as couriers transporting sealed records
Telecommunications Carriers acting strictly as transmission conduits
Internet Service Providers (ISPs) providing transmission-only services
Telecommunications Relay Services (TRS) Providers under the 2026 Final Rule
Banks and Financial Institutions performing standard, HIPAA-authorized payment processing functions
(One crucial distinction: A courier delivering a sealed box of paper records is a conduit. A transportation company handling living organs, blood products, tissue, or transplant materials is participating in healthcare operations involving human biological materials—not simply transmitting information—so do not assume the conduit exception applies.)
One of the most challenging aspects of HIPAA compliance is that the rules often appear simple at a high level but become highly nuanced when applied operationally. Determining whether a vendor is a Business Associate, whether an exception applies, or whether a disclosure is permissible frequently requires analysis beyond what most organizations can reasonably perform without specialized expertise. These peculiarities are precisely what complicate compliance obligations for Covered Entities, Business Associates, and their subcontractors.
This reality is one of the reasons we developed the Certified HIPAA Security Officer (CHSO) program and the EPI Compliance platform. Both were designed to help organizations transform complex regulatory requirements into repeatable operational processes, improve workforce competency, and reduce the risk of compliance gaps created by misunderstood requirements, overlooked vendors, and evolving regulatory expectations.
Final Thoughts: Compliance Is a Living Process
My overall advice is simple: remember that no compliance program is static. In fact, the exact opposite is true. Regulatory updates, emerging technologies, and shifting operational environments mean your organization must maintain living policies, flexible procedures, and ongoing training programs that adapt right alongside them.
When in doubt, always ask the question and verify the answer. Above all, make sure to avoid relying on the phrase, "We’ve always done it this way." In today's regulatory landscape, that mindset and justification are guaranteed to get you into trouble.
Disclaimer: This article—including its discussion of Business Associate classifications and regulatory exceptions—is provided strictly for educational and informational purposes and does not constitute legal advice. Healthcare organizations, covered entities, business associates, and subcontractors should consult qualified legal counsel and compliance professionals when making Business Associate determinations or implementing organization-specific compliance policies.
About Dr. Jose I. Delgado
Dr. Jose I. Delgado is the founder and CEO of Taino Consultants, a veteran-owned, 8(a) graduate healthcare IT consulting firm based in St. Augustine, Florida. With over 30 years of experience in healthcare compliance and government contracting, Dr. Delgado has helped organizations navigate HIPAA, MACRA/MIPS, and federal IT security requirements.
Need help with healthcare compliance?
Taino Consultants provides HIPAA compliance consulting, MACRA/MIPS compliance support, and healthcare IT modernization services for government and private healthcare organizations.
Schedule a consultationRelated articles

Should Your Healthcare Organization Add Laboratory Services? A Strategic Guide for Executives and Practice Owners

Dental Practices in the U.S.: Protecting Profitability Amid Rising Labor Costs, DSO Competition, and Compliance Scrutiny
