The 2026 HIPAA rule is a network problem.
The overhaul moving through OCR turns old addressable safeguards into hard mandates: encryption everywhere, MFA on every login, segmentation between sites. Almost none of it lives in software you can buy.
Rings Jonathan and the team 24x7.
400+ carriers and platforms, compared.
Half of this isn't even about computers
An office manager at a three-location medical practice put it well: half of the proposed HIPAA Security Rule changes are not about computers, they are about how the offices talk to each other. For years the rule let practices treat many safeguards as addressable, a word that in practice often meant a sentence in a binder and nothing more.
The 2026 overhaul working through the Office for Civil Rights changes that posture. The direction is unmistakable: encryption of patient data at rest and in transit, multi-factor authentication on every point of access, network segmentation, vulnerability scanning, tested backups. Less consider this, more do this and be able to prove it.
Where things stand
As of this writing the updated rule is proposed, not final. A good chunk of the exact control lists circulating online come from IT-vendor blogs rather than the rule text, so treat specifics as directional until OCR publishes the final version. Once that happens, the expected compliance clock is roughly 240 days, which is not much runway for practices running more than one location.
What's actually changing
Encryption everywhere, including in transit
Every time a chart, image, or billing file moves between offices or to a provider working remotely, it is expected to be encrypted the entire way. That is a connectivity decision, not a records-software checkbox.
MFA on every point of access
Not just the EHR login. Remote access, email, administrative accounts, the billing company's connection, the vendor who maintains imaging equipment. The requirement is built to find the one door left propped open.
Segmentation and a real network map
Waiting-room Wi-Fi, a smart thermostat, and the system holding patient records should not sit on the same flat network. You cannot segment what you have not mapped.
Tested backups and vulnerability scanning
We back up nightly and we have restored from backup and scanned for holes recently are two different sentences. The new posture wants the second one.
Why this lands hardest on multi-location practices
A single-office practice has a hard enough time with this. It gets genuinely difficult for a practice that has grown to three, five, eight locations, often by acquiring smaller practices that each came with their own internet provider and their own idea of a password policy.
The rule does not care that one office runs on fiber with a real firewall while another runs on a consumer cable modem. From OCR's chair it is one covered entity, and the weakest location sets the real exposure. One unencrypted link between sites, one location without MFA, and the yes you wrote down stops being true everywhere.
Every requirement is a network decision
Almost none of these mandates are satisfied by buying a product. Encryption in transit between sites means secure, encrypted connectivity, a properly built SD-WAN or VPN backbone, not whatever the cable company handed you. Segmentation means the network is deliberately divided so a problem in the waiting room cannot reach the records room. The EHR vendor will tell you their product is HIPAA compliant, and that is fine, but the rule applies to your whole environment, not just one application.
Quick win
Before spending a dollar on new tools, build one honest map.
- Every location and every internet connection
- Every way into your systems and every device touching the network
- Exactly how data travels between your sites
One network, three masters
The HIPAA direction, your cyber-insurance renewal, and plain common sense are converging on the same short list: MFA everywhere, EDR on every endpoint, tested backups, encryption, segmentation, and a real inventory behind it. The smart move is to build one defensible network across all your locations, then point every requirement at it, instead of chasing each questionnaire separately.
The bottom line
Get ahead of it while it is still directional. Build the map before you buy anything. Bring your weakest location up to the standard of your best one, because the rule grades on the weakest. Decide what your practice's network should look like on your terms, this quarter, calmly, instead of the week the final rule lands.
Related
Zero trust security, in plain English.
What zero trust means for a smaller business, and where to start.
Read →SecurityThe Cyber Threat Ohio Small Businesses Are Most Unprepared For
Ransomware gets the headlines. The threat most Ohio businesses are unprepared for is quieter: credential compr...
Read →ComplianceYour Cyber-Insurance Renewal Is Quietly Writing Your IT Roadmap
The 2026 renewal questionnaire reads like an IT project plan: MFA everywhere, EDR on every machine, tested bac...
Read →NetworkingThe 99.9% Uptime Promise: What Your SLA Won't Cover
99.9% uptime sounds bulletproof until you do the math. Here is what the guarantee actually covers, what it pay...
Read →Get ahead of the compliance clock
We map your locations against where the rule is headed and show you the real gaps. There is no advisory fee.
Book a call