There’s no such thing as HIPAA certified software. HIPAA compliant software development means building to the Security Rule’s safeguards, documenting a risk analysis, and signing business associate agreements with every vendor that touches protected health information. The big 2025 proposal to tighten the Security Rule is still not final, and the federal agenda now targets 2027. Build to today’s rule, design so the proposed changes are easy to adopt, and test the controls, not just the features.
HIPAA compliant software development means building to the Security Rule’s safeguards, with a documented risk analysis, access controls, audit logs and business associate agreements with every vendor handling PHI. No official HIPAA certification exists.
Most guides to HIPAA compliant software development make two mistakes. They describe the proposed 2025 Security Rule changes as if they were already law, and they treat a cloud provider’s business associate agreement as if it made your application compliant. Neither is true.
This guide sorts what’s required today from what’s only proposed, explains what cloud BAAs actually cover, and shows how to test the controls auditors and investigators look for. It’s written for CTOs and product leaders building software that touches patient data, the kind of work our healthcare and life sciences team supports.
This is educational information from an engineering firm, not legal advice. Work with qualified HIPAA counsel on your specific obligations.
What HIPAA requires today, and what’s only proposed
Today’s Security Rule splits technical safeguards into required and addressable. Unique user IDs and emergency access are required. Encryption and automatic logoff are addressable. A January 2025 proposal would make far more mandatory, but it isn’t final, and the federal agenda now targets July 2027.

Addressable doesn’t mean optional. Under 45 CFR 164.312, you must implement an addressable safeguard if it’s reasonable and appropriate, or document why not and what you did instead. For encryption in a modern application, it’s very hard to argue it isn’t reasonable.
| Technical safeguard | Status today | Under the 2025 proposal |
|---|---|---|
| Unique user identification | Required | Required |
| Emergency access procedure | Required | Required |
| Audit controls | Required | Required, with more detail |
| Automatic logoff | Addressable | Proposed to become required |
| Encryption at rest and in transit | Addressable | Proposed to become required, with limited exceptions |
| Multi-factor authentication | Not named in the rule | Proposed to become required |
Current Security Rule vs the January 2025 proposed rule.
HHS published the proposal in the Federal Register on January 6, 2025. In 2025 the government’s regulatory agenda aimed to finalize it by May 2026. The latest Unified Agenda entry moved it to long-term actions with a July 2027 target. Dates may move again.
Our advice is simple. Build encryption, MFA and automatic logoff in now. They’re good engineering, investigators already expect them, and if the rule is finalized you won’t be retrofitting.
Who counts as a business associate?
Any vendor that creates, receives, maintains or transmits protected health information on behalf of a covered entity is a business associate, and needs a BAA. That includes a software development firm whose engineers can reach production data, a hosting provider and a support desk that sees patient records.
It also includes cloud providers that can’t read your data. HHS’s cloud computing guidance says a provider storing encrypted PHI is still a business associate even without the key. The conduit exception, for services that only transmit data, is narrow and rarely applies to software.
A practical design choice follows. If your development partner works only with de-identified data in non-production environments and never touches production, the BAA question changes. Decide that deliberately, with counsel, rather than letting it happen by accident.
Cloud BAAs: what they cover and what they don’t
AWS, Microsoft Azure and Google Cloud all offer BAAs, but each covers only specific eligible services, and each states plainly that there’s no HIPAA certification. The BAA covers their infrastructure. Your configuration, code and access controls remain your responsibility.

- AWS says there’s no HIPAA certification for a cloud provider, and that PHI should only be processed in HIPAA-eligible services covered by its BAA. A non-eligible service holding PHI is outside the agreement.
- Microsoft includes its BAA by default through its Product Terms, also notes there’s no HHS-approved certification, and says a BAA doesn’t automatically make a customer compliant. If you sell software built on Azure to healthcare customers, they sign a BAA with you, not with Microsoft.
| Layer | Cloud provider | You and your development team |
|---|---|---|
| Data centers and hardware | Yes | No |
| Eligible managed services | Platform security | Configuration, encryption settings, access |
| Application code | No | Yes |
| Identity, roles and MFA | Provides the tools | Configures and enforces them |
| Audit logs | Provides the services | Turns them on, retains and reviews them |
| Risk analysis and policies | No | Yes |
Shared responsibility for HIPAA workloads in the cloud.
Our cloud security team treats the eligible services list as an architecture constraint from day one. Finding out after launch that your search index or analytics tool isn’t covered is an expensive surprise.
Start with a risk analysis, because OCR does
A risk analysis is the Security Rule’s starting point. It identifies where PHI lives, how it moves, what could go wrong and how likely and harmful each threat is. And it’s the requirement OCR enforces most visibly.
OCR runs a Risk Analysis Initiative focused on organizations that skipped or botched this step. A July 2026 settlement with a health plan for $450,000 was its 14th action under that initiative and its 20th ransomware enforcement action, according to Nixon Peabody’s summary. The pattern is consistent. Ransomware hits, OCR investigates, and the missing risk analysis becomes the finding.
For a software team, the risk analysis should produce three things. A data flow diagram showing every place PHI is stored, processed or sent. A ranked list of threats. And a list of controls, each mapped to a test. That last part is where engineering and compliance meet.
Technical safeguards to build in from the first sprint
- Unique accounts for every user, with role-based access so people see only the PHI their job needs
- MFA for all users, and phishing-resistant MFA for administrators
- Encryption in transit with current TLS, and at rest using managed keys, with key access logged
- Automatic session timeout, tuned to the clinical setting. A shared nursing station and a patient app need different settings.
- Audit logs that record who viewed, changed or exported PHI, kept in a store that application admins can’t edit
- An emergency access procedure for when normal access fails, logged and reviewed afterward
- No PHI in application logs, error messages, analytics events or URLs
- Backups that are encrypted, tested and restorable
That second-to-last item causes more real-world exposure than people expect. A debug log that captures a full request body or an analytics tag that records a page URL with a patient ID in it quietly puts PHI somewhere nobody is protecting. Our web and mobile development team builds log scrubbing in as a default rather than a cleanup task.

Testing HIPAA controls, not just features
Test the safeguards as rigorously as the features. Verify access control and session timeouts, confirm audit logs capture every PHI access, scan logs and test environments for leaked PHI, use de-identified test data, pen test before launch, and keep the evidence.

Functional testing proves the app works. Compliance testing proves it protects data the way your risk analysis says it does. Our compliance testing team treats these as separate test suites, and runs both on every release.
| Control | How to test it | Evidence to keep |
|---|---|---|
| Access control | Automated tests that each role can reach only its permitted records | Test results per release |
| Session timeout | Automated test that idle sessions expire at the set time | Configuration and test output |
| Audit logging | Perform view, edit and export actions, then confirm each appears in the log | Sample log entries |
| PHI leakage | Scan application logs, error output and analytics payloads for patient identifiers | Scan reports |
| Encryption | Verify TLS configuration and that storage encryption is on | Scanner output, configuration screenshots |
| Overall security | Penetration test before launch and after major changes | Report and remediation record |
HIPAA control testing matrix.
Test data needs its own rule. Real patient data shouldn’t sit in development or QA. HHS’s de-identification guidance describes two methods, Safe Harbor, which removes 18 specified identifiers, and Expert Determination, where a qualified expert certifies the re-identification risk is very small. Synthetic data generated from scratch avoids the question entirely.
Automate as much of this as possible. Access control and audit log tests belong in the same pipeline as your other regression tests, which our QA automation team builds so every release produces its own evidence.
Build on the cloud directly, or use a compliance platform?
Two paths dominate. You can build directly on HIPAA-eligible services from AWS, Azure or Google Cloud and own every configuration decision. Or you can build on a compliance-focused hosting platform that wraps those services with preconfigured logging, encryption and policies, and signs its own BAA with you.
| Build directly on cloud | Compliance platform | |
|---|---|---|
| Speed to first release | Slower. You design the landing zone, logging and policies | Faster. Much of the baseline is preset |
| Control | Full control over architecture and services | Limited to what the platform supports |
| Cost pattern | Cloud costs plus your team’s time | Platform fee on top of compute |
| Evidence for audits | You build and maintain it | Partly provided by the platform |
| Exit | Nothing to migrate away from | Plan the exit before you sign |
Building directly on cloud vs using a compliance platform.
Neither choice is compliance by itself. A platform reduces setup work, but your application code, access rules, risk analysis and testing still belong to you. For a startup shipping its first product with a tiny team, a platform can be the sensible start. For an established organization with an existing Azure or AWS footprint and a security team, building directly usually fits better, and keeps one set of controls across every system.
Either way, check the BAA chain end to end. Your customer signs with you, you sign with the platform or cloud provider, and every subcontractor that touches PHI sits somewhere in that chain with its own agreement.
HIPAA vs HITRUST vs SOC 2
Healthcare buyers ask about all three, and they aren’t the same kind of thing.
HIPAA
- Federal law, not a certification
- Applies to covered entities and business associates
- Proven through risk analysis, policies and evidence
SOC 2
- An independent CPA attestation on security controls
- Common in enterprise procurement
- Doesn’t by itself show HIPAA compliance
HITRUST
- A certifiable framework built for healthcare
- Maps to HIPAA and other standards
- Takes serious time and budget to achieve
HIPAA, SOC 2 and HITRUST compared.
Which you need depends on who you sell to. Large health systems increasingly ask vendors for SOC 2 or HITRUST on top of a signed BAA. A smaller clinic group may only ask for the BAA and a security questionnaire. Ask your target customers before committing to a certification program.
Penalties and breach notification in 2026
HHS adjusts HIPAA civil money penalties for inflation each year. Its January 2026 adjustment set the maximum penalty per violation at $73,011 and the calendar-year cap for identical violations at $2,190,294. HHS has also used enforcement discretion since 2019 to apply lower annual caps for lesser culpability tiers, so actual exposure depends on the circumstances.
Breach costs dwarf the fines. IBM’s 2025 research, as reported by TechTarget, put the average healthcare breach at $7.42 million, the costliest of any industry for the 14th year running.
On notification, the Breach Notification Rule requires notice to affected individuals without unreasonable delay and no later than 60 days after discovery. Breaches affecting 500 or more people also require notice to HHS and, in some cases, the media within the same window. Build the logging that lets you answer who was affected quickly, because you’ll need it.
Who we are
Upen Group is a digital transformation and engineering company headquartered in Irving, Texas. Our web and mobile development, cloud security, data engineering and compliance testing teams help healthcare and health-tech organizations build software designed around the Security Rule’s safeguards, and test the controls before go-live. Ask any development partner, including us, directly whether they will sign a BAA for your project and what certifications they hold.
The short answer
There’s no HIPAA certification. Build to today’s Security Rule, starting with a documented risk analysis, and add encryption, MFA and automatic logoff now, since the 2025 proposal would require them and investigators already expect them. Use only BAA-covered cloud services, keep PHI out of logs and test environments, and test your safeguards as seriously as your features.
Building or modernizing software that handles patient data? Send us a short description of the application and where it runs, and we’ll come back with a safeguards and testing checklist mapped to the Security Rule.
What healthcare CTOs ask us
Is there such a thing as HIPAA certified software?
No. HHS doesn’t certify software or vendors for HIPAA, and AWS and Microsoft both say so on their own compliance pages. Compliance is shown through risk analysis, safeguards, policies and evidence.
Does our development partner need to sign a BAA?
If their people can create, receive, maintain or transmit PHI, including through production access, yes. If they work only with de-identified data and never reach production, the answer may differ. Confirm with counsel.
Once we sign AWS’s or Azure’s BAA, are we compliant?
No. The BAA covers the provider’s eligible services and infrastructure. Your configuration, code, access controls, logging and risk analysis remain your responsibility.
Is encryption required under HIPAA today?
It’s an addressable safeguard, which means you must implement it if reasonable and appropriate or document an equivalent alternative. In practice almost every modern application should encrypt, and the 2025 proposal would make it mandatory.
When will the proposed Security Rule update take effect?
Nobody knows yet. It was proposed in January 2025, and the latest federal agenda lists it as a long-term action targeted for July 2027. Build the key controls now so the date doesn’t matter.
Can we use real patient data in testing?
Avoid it. Use data de-identified by Safe Harbor or Expert Determination, or fully synthetic data. Real PHI in test environments widens your exposure and your BAA obligations.
Do we need SOC 2 or HITRUST as well?
Not legally. Commercially, large health systems increasingly ask for one, alongside a signed BAA. Check what your target customers require before choosing.
