// blog
HIPAA Basics for Web Developers Building a Patient Portal
If your web app creates, receives, stores or sends electronic protected health information for a healthcare provider, the HIPAA Security Rule applies. Its technical safeguards (45 CFR 164.312) are access control (unique user IDs, emergency access, automatic logoff, encryption), audit controls, integrity, person or entity authentication, and transmission security. Vendors that handle the data for you, such as hosting, need a business associate agreement. This is a summary for developers, not legal advice.

You’re building a patient portal, a booking flow with health questions, or an app that shows scans. Somewhere a person says “it has to be HIPAA compliant”. Here’s what that means for the code. This is a developer’s summary, not legal advice; the practice’s compliance officer or lawyer has the final word.
Does it apply?
HIPAA applies to covered entities (most healthcare providers, health plans, clearinghouses) and their business associates: anyone who creates, receives, maintains or transmits protected health information (PHI) on their behalf. If you build or host software that handles a provider’s patient data, you’re likely a business associate, and so is your hosting provider.
The technical safeguards
The Security Rule’s technical safeguards are in 45 CFR 164.312. In developer terms:
| Safeguard | In your app |
|---|---|
| Access control | A unique account per user (no shared logins); an emergency access procedure; automatic logoff after inactivity; encryption of stored data |
| Audit controls | Logs of who viewed, changed, exported or shared what, kept and reviewed |
| Integrity | Protect PHI from improper change or deletion: permissions, checksums, backups |
| Person or entity authentication | Verify users are who they say: strong passwords plus a second factor |
| Transmission security | Encrypt in transit (HTTPS everywhere, TLS between services) and guard against tampering |
Some are “required”, others “addressable”: addressable means implement it if reasonable, or document why not and what you do instead. Encryption at rest and in transit are addressable on paper; in practice, do both.
Business associate agreements
Every vendor that handles PHI for you needs a business associate agreement (BAA): hosting, database, backup, email or SMS that carries health details, error tracking that captures request data. HHS’s cloud guidance says a cloud provider storing PHI is a business associate even if the data is encrypted and it can’t read it.
Habits that keep you out of trouble
- No PHI in URLs, logs or error reports. Use IDs; scrub request bodies before logging.
- No health details in emails and texts. “You have a new message in the portal” instead.
- No third-party trackers behind the sign-in. HHS has issued guidance on online tracking technologies.
- Least privilege: staff see what their job needs.
- Backups, tested restores, and a plan for a breach.
- Read files in the browser when you can. Our DICOM viewer never uploads a patient’s files, so there’s nothing on the server to protect. See showing medical images without uploading them.
Key takeaways
- If you handle a provider’s patient data, you’re likely a business associate.
- Technical safeguards: access control, audit controls, integrity, authentication, transmission security.
- BAAs with every vendor that touches PHI, hosting included.
- Keep PHI out of URLs, logs, emails and trackers.
We’re glad to share what we know. When you want a patient portal built with these safeguards from day one, we’ll put all of it to work on your project, and because we build with AI-assisted development, it costs far less than you might expect. Let’s talk.
Frequently asked questions
Is encryption required by HIPAA?
In the Security Rule, encryption of stored data and of data in transit are 'addressable' specifications: you must implement them if reasonable and appropriate, or document why not and what you do instead. In practice, encrypt both.
Does my hosting provider need to sign a BAA?
If it stores or processes protected health information for you, HHS's guidance treats it as a business associate, even if the data is encrypted and it has no key. Use providers that sign one.
Can I use analytics on a patient portal?
Be very careful. Third-party tracking on pages where patients are signed in can disclose health information. HHS has issued guidance on online tracking technologies; the simplest course is no third-party trackers behind the sign-in.
































































































































