Preventative Care

HIPAA Risk Tool 3.7: Remote ePHI Security Mandate

Listen to this article · 8 min listen

The remote work explosion in healthcare has been a headache for security teams trying to keep a perimeter around patient data. Well, the federal government’s own HIPAA risk assessment tool finally caught up. With the release of version 3.7 in late 2026, the feds are now forcing the issue, and for anyone in charge of compliance or security, it means you have a lot of work to do re-mapping exactly where your Electronic Protected Health Information (ePHI) actually lives. It’s not just on the server in the basement anymore.

Version 3.7: Expanding the Scope to Every Location

The federal HIPAA risk assessment tool’s scope just got a lot bigger. As noted on the lead page from Paubox, version 3.7 now explicitly includes remote access and telework as locations where you handle ePHI. This change officially drags home offices, remote sessions on company servers, and any other off-site environment into your formal risk assessment. This update is a fundamental shift in how you must inventory and evaluate your vulnerabilities. It was always easy to sort of ignore the security mess of ePHI being accessed from a laptop on a kitchen table. The working assumption was that the “office” was the only place that needed serious security controls. Version 3.7 kills that assumption and makes it clear that the location of ePHI doesn’t matter. It’s all subject to the same strict security rules. This means a clinician checking patient charts from their home office, a billing specialist processing claims from a Starbucks, or a developer accessing a test database from their apartment all now fall squarely inside the assessment’s broadened scope.

The HIPAA Security Rule: A Universal Standard for ePHI

For any health data company, this expanded scope ties directly back to the HIPAA Security Rule, which is the baseline for protecting ePHI no matter where it is. For instance, the compliance materials for Tempus AI are built around the HIPAA Security Rule and its definition of ePHI, which is why they are a good practical example of this scope in action. The Security Rule applies the same whether your ePHI is on a server in a locked room or a laptop in a bag. The required safeguards, access controls, audit controls, integrity checks, transmission security, and physical security, must cover every single environment where ePHI exists. For remote work, that has some very direct consequences. It means you have to:

  • Implement strong access controls: You’ve got to make sure only authorized people can access ePHI, period, regardless of where they are. This means mandatory multi-factor authentication (MFA) and permissions that are as tight as possible. NIST guidance on access control for remote work
  • Establish audit trails: You need logs of who accesses ePHI and what they do to it so you can spot anything suspicious. This is a pain to manage across a distributed workforce, but it’s absolutely essential for accountability.
  • Ensure data integrity: You must protect ePHI from being changed or deleted, whether on purpose or by accident. This requires secure device configurations and data backup plans that actually account for all those remote laptops.
  • Secure data in transit and at rest: Encrypt ePHI when it’s moving across a network and when it’s sitting on a device. This includes every laptop, desktop, and mobile phone used by your remote staff.
  • Address physical safeguards: This is tough for a home office, but you need to advise employees on securing their workspace to prevent someone else from getting to their device. This could be as simple as policies on screen locking and making sure they don’t leave sensitive papers out.

Where ePHI Now Travels: An Expanded Field

By adding remote access and telework to the federal tool, the government is demanding you get a complete picture of every pathway and endpoint your ePHI touches. The office walls no longer define your security perimeter. The perimeter now includes:

  • Employee Home Offices: The obvious one. You need to assess the security of their home Wi-Fi, the physical security of their work devices, and whether they’re actually following your policies.
  • Co-working Spaces and Public Networks: These places present huge challenges for network security and privacy, especially if employees are logging in from a shared public Wi-Fi.
  • Mobile Devices: Your team’s smartphones and tablets, which are constantly getting lost, stolen, and connected to sketchy networks.
  • Cloud-Based Applications and Services: Many AI health tools are cloud-based. While the vendor secures the infrastructure, your organization is still on the hook for how your team accesses and manages ePHI inside those apps.
  • Personal Devices Used for Work (BYOD): If you let people use their own computers or phones for work, those devices have to meet the exact same security standards as company gear. No exceptions.

This new reality requires you to get ahead of risks instead of reacting to them. You must operate on the assumption that ePHI will be accessed from anywhere, and build your security framework to handle that.

What an Updated Location Inventory Looks Like

You need to take a hard look at your location inventory, because the SRA tool now officially counts all those places that were easy to ignore before. An updated location inventory for version 3.7 goes way beyond a list of office buildings. It requires a detailed map of every single point where ePHI is created, received, stored, or sent.

For each remote or telework location, your inventory needs to break down:

  • Device Type: Is it a company laptop, a personal desktop, a phone?
  • Network Connection: Are they on a secure home Wi-Fi, a public hotspot, or are they connected through a VPN? (Are you sure?)
  • Software and Applications: What exact AI tools, Slack, or other software are they using to get to ePHI?
  • Physical Environment: What’s the physical security like? Is the door locked? Are they using a privacy screen?
  • User Training: Has this person been specifically trained on securing ePHI while working from home?

This complete inventory is the only way you can do a real risk assessment and find the vulnerabilities that are unique to each remote work situation. As Paubox’s page on the update records, the scope has widened, and as Tempus AI’s materials show, the HIPAA Security Rule gives this change its teeth. Every one of these new locations now needs the same security discipline you apply to your main office. When the federal tool adds remote access, the Security Rule’s reach extends past the office door. This isn’t a suggestion. It’s a direct question on your compliance checklist that demands your immediate attention. The impact on AI workflow regulations healthcare HIPAA FDA is obvious: any HIPAA compliant AI health apps or HIPAA compliant digital health platforms have to prove their security works across all user access points, no matter the location. Your AI health HIPAA compliance checklist needs to be updated to make sure you’re grilling vendors on their remote access and telework security posture. HHS guidance on remote work and HIPAA Just because OCR hasn’t set a hard deadline or announced specific fines for this update doesn’t mean you can wait. By formally adding remote work to the SRA tool, regulators are sending a clear signal. If you don’t adapt your compliance program to this bigger scope, you’re setting yourself up for major non-compliance findings down the road. Proactive assessment isn’t just a good idea. It’s now the minimum requirement for protecting ePHI in healthcare’s distributed world. OCR enforcement actions for HIPAA violations

Frequently Asked Questions

How does version 3.7 of the federal HIPAA risk assessment tool change the scope of what needs to be assessed?

Version 3.7 explicitly adds remote access and telework to the scope of locations handling electronic protected health information (ePHI). This means home offices, remote sessions, and any other off-site environments where ePHI is accessed, processed, or stored must now be formally included in risk assessments. This update signifies a fundamental shift in how organizations must inventory and evaluate potential vulnerabilities beyond traditional office settings.

What specific types of remote locations are now included in the HIPAA risk assessment scope?

The expanded scope includes employee home offices, co-working spaces, public networks, and mobile devices used for work. It also encompasses cloud-based applications and services where ePHI may reside or be accessed. This broadens the perimeter of ePHI security beyond the traditional physical office.

What are the key implications of this update for applying the HIPAA Security Rule to remote work?

The HIPAA Security Rule’s core principle is location-agnostic, meaning its safeguards must extend to every environment where ePHI is present, including remote and telework settings. This requires implementing robust access controls, establishing audit trails, ensuring data integrity, securing data in transit and at rest, and addressing physical safeguards for remote work environments. Organizations must apply the same scrutiny to ePHI regardless of its physical setting.

What specific safeguards are emphasized for remote and telework settings under the updated guidance?

Organizations must implement robust access controls, including strong authentication and multi-factor authentication, and establish audit trails for all ePHI access. They also need to ensure data integrity through secure configurations and backups, secure data in transit and at rest via encryption, and advise employees on physical safeguards for their remote work environments to prevent unauthorized access.

Share
Was this article helpful?

Editorial Team

The Editorial Team at HIPAA AI Health is a group of writers and editors who cover health, workplace wellness, and everyday care. They research each story and publish under a shared desk byline — experts in their fields, working as one team.