Where PHI is allowed to live: HIPAA and on-premise software
Why practices choose on-premise software for protected health information, what the business associate question actually asks, and where a local tool does and does not help.
The HIPAA Security Rule does not ban cloud software. What it requires is that protected health information be safeguarded by whoever holds it, and that a covered entity have a business associate agreement with any vendor that touches PHI on its behalf. Cloud vendors can and do meet that bar.
So why do practices keep asking for on-premise tools? Because the business associate agreement is a contract with a company whose security posture you cannot audit, and for a small practice the simplest way to reduce that exposure is to not create it. Software that never transmits PHI never needs a BAA for that data flow. That is the entire argument, and it is a good one.
What the BAA question is really asking
When a compliance officer asks "is this a business associate", they are asking three things at once:
- Does the vendor receive, store or process PHI?
- If so, is there a signed agreement that binds them?
- If the agreement is breached or the vendor is breached, what is the practice's exposure?
A tool that processes files entirely on the practice's own machine answers "no" to the first question, and the other two evaporate. That is a meaningfully simpler compliance position than signing an agreement and hoping.
Where on-premise does not save you
This is the part vendors leave out. Keeping PHI local moves the obligation; it does not remove it. A practice running local software still has to:
- Encrypt the disk. A stolen laptop with a patient database on it is a breach whether or not the software has a cloud component.
- Control access. Shared logins on a front-desk PC defeat every other control.
- Back up, and test the restore. Local data that is not backed up is one failed drive away from a reportable event.
- Dispose of hardware properly. Deleting files is not sanitising a disk.
- Apply the software updates. An unpatched local application is not safer than a patched cloud one.
An on-premise tool reduces the number of parties you have to trust. It does not reduce the number of things you have to do.
The audit question
What an auditor or a surveyor actually asks for is evidence that controls exist and operate. For local software that means: a device inventory showing which machines hold PHI, an encryption attestation per device, a backup log with a restore test, and a documented disposal procedure. None of that comes with any software purchase; it comes from doing the work.
What this choice does not fix
Local software reduces the number of parties who hold the data. It does not encrypt your disks, restrict logins, run your backups or train your staff. If the practice cannot do those things, no deployment model fixes it - and that is worth weighing honestly before committing to any of them.