Skip to main content

Staffing For Doctors · For your practice

Compliance

11 Remote HIPAA Compliance Breakdowns Small Practices Miss

Most HIPAA exposure in a remote setup comes from a handful of quiet, fixable failures, shared logins, home Wi-Fi, a missing vendor BAA, no training records. Eleven concrete breakdowns small practices miss and how to close each one.

May 15, 2026 9 min readBy Danny Nabavi, Founder, Staffing For Doctors
0111 Remote HIPAA Compliance Breakdowns Small Practices Miss

Most HIPAA exposure in a remote setup does not come from sophisticated attacks. It comes from a handful of quiet, ordinary breakdowns that a busy small practice never gets around to fixing: a shared login, a home Wi-Fi network, a vendor without a signed agreement, a training log that does not exist. Each one is mundane, and each one is exactly what an enforcement action is built on.

Below are eleven compliance breakdowns small practices most often miss with remote staff, grouped by where they hide. None require a compliance department to close, they require attention. For the deeper risk picture, see the non-specialized virtual staff HIPAA risk guide.

02Breakdowns in access and credentials

Breakdowns in access and credentials

1. Shared login credentials. When two or more remote staff share one account, you lose the ability to attribute any access to a person, which destroys your audit trail and violates the minimum-necessary principle. Every staffer needs a unique login.

2. No multi-factor authentication. A password alone is a single point of failure, and remote access multiplies the exposure. MFA on the EHR and payer Marketplaces is one of the cheapest, highest-impact controls available.

3. Access that never gets revoked. A staffer changes roles or leaves and their account stays live for weeks. Stale access is a standing risk; revoke the same day, not the same quarter.

4. Over-broad access. A scheduler who can see billing, a biller who can see clinical notes they never touch. Access should be scoped to the role, nothing more.

03Breakdowns in devices and networks

Breakdowns in devices and networks

5. Unsecured home Wi-Fi. Open or default-password home networks are a soft target. Remote staff should work over a secured network, and PHI should never traverse public Wi-Fi.

6. PHI stored on local drives or personal cloud. Files saved to a personal laptop or a consumer cloud account are outside your control and your BAA. Policy should prohibit it and devices should enforce it.

7. No screen lock or disk encryption. A device left unlocked or unencrypted turns a lost laptop into a reportable breach. Automatic screen lock and full-disk encryption are baseline.

04Breakdowns in agreements and vendors

Breakdowns in agreements and vendors

8. A missing BAA with the VA or vendor. The single most common and most damaging gap: remote staff or a staffing vendor handling PHI with no Business Associate Agreement in place. Sign it before any access.

9. Subcontractors not covered. Your vendor may use subcontractors who also touch PHI. The agreement must extend to them, or there is an uncovered link in the chain.

05Breakdowns in training and oversight

Breakdowns in training and oversight

10. No workforce training records. Even well-meaning staff create risk when untrained, and in an audit, training you cannot evidence did not happen. Keep dated records for every remote person, refreshed on a cadence.

11. Audit logs that are never reviewed. Collecting access logs without reading them gives a false sense of safety. Schedule a recurring review for unusual access patterns and document it. To close these gaps with a trained, agreement-backed team, start a conversation or weigh the options on the pricing page.

06Frequently Asked Questions

Frequently Asked Questions

A missing Business Associate Agreement with the virtual assistant or staffing vendor. Letting remote staff touch PHI with no signed BAA is both the most common and most damaging gap, and it is a frequent enforcement finding.

Shared credentials make it impossible to attribute access to an individual, which destroys your audit trail and breaks the minimum-necessary principle. Every remote staffer needs a unique login with multi-factor authentication.

Yes. Open or default-password home networks are soft targets, and PHI should never travel over public Wi-Fi. Remote staff should work on a secured network, with PHI kept off local drives and personal cloud accounts.

Yes. In an audit, training you cannot evidence is treated as if it never happened. Keep dated records for every remote person and refresh the training on a regular cadence.

Very little. Logs only protect you when reviewed, so schedule a recurring check for unusual access patterns and document it. An unreviewed log gives a false sense of safety.

Sign BAAs before access, enforce unique logins and MFA, scope access to roles, secure devices and networks, keep training records, and review logs on a schedule. A trained, agreement-backed staffing partner closes most of them at once.

Ready to see what a specialty-trained virtual medical assistant can do for your practice?

Free 20-minute consultation. No commitment required.

07Practice essentials

Get the Practice Forward playbook

One email per week with practical advice on staffing, operations, and patient experience. No fluff.

No spam. Unsubscribe anytime.

Let's talk about your practice

More time for your patients