HIPAA Compliant Software Development: The Complete 2026 Guide
by GainHQ Editorial Team | Jul 12, 2026 | Software Development Insights | Editorial policy
Table of Contents
- What does HIPAA compliance mean for software?
- Does HIPAA apply to your software?
- HIPAA Security Rule requirements: required vs addressable
- Is encryption required under HIPAA?
- Status of the 2025 HIPAA Security Rule proposal (as of October 2026)
- Business associate agreements: vendors, cloud and AI services
- De-identification for test data and analytics
- Building HIPAA compliance into the software development life cycle
- Breach notification: what the software must support
- Common gaps in HIPAA software projects
- How to evaluate a HIPAA software development partner
- How GainHQ can help
HIPAA compliant software development means building and running software so that the organisation using it can meet the HIPAA Privacy, Security and Breach Notification Rules for the protected health information (PHI) the software touches. There is no such thing as a HIPAA-certified product. Compliance belongs to the covered entity or business associate, and the software is one part of how it gets there.
For development teams, the practical core is the HIPAA Security Rule at 45 CFR Part 164, Subpart C. It sets administrative, physical and technical safeguards, and lets each organisation choose measures based on its own risk analysis. This guide walks through those requirements, the contracts that sit around them, and how to build them into a normal software development life cycle.
Note: This article is general information, not legal advice. HIPAA obligations depend on your role and facts. Check the current regulation text on eCFR and HHS guidance, and talk to qualified counsel before making compliance decisions.
What does HIPAA compliance mean for software?
HIPAA compliance for software means the software lets its operator protect the confidentiality, integrity and availability of electronic PHI (ePHI), and only use or disclose PHI in ways the rules permit. The Security Rule's general requirement is to protect against "reasonably anticipated threats or hazards" to ePHI that an organisation "creates, receives, maintains, or transmits".
Three points shape every build decision:
- No certification exists. HHS states that it "does not endorse or otherwise recognize private organizations' 'certifications'" for the Security Rule, and that such certifications do not remove an organisation's legal obligations. A vendor badge that says "HIPAA certified" is marketing, not a regulatory status.
- The rule is flexible, not a checklist. Organisations "may use any security measures" that reasonably and appropriately meet the standards, taking into account size, technical capabilities, cost, and the probability and criticality of risks (§164.306(b)).
- Minimum necessary applies to design. Covered entities and business associates must make reasonable efforts to limit PHI to the minimum necessary for the purpose, with some exceptions such as disclosures for treatment. In software terms, that means role-scoped queries, views and APIs rather than "return the whole record".
Does HIPAA apply to your software?
HIPAA applies based on who you are and whom you handle PHI for, not on whether your product is "health related". The rules cover covered entities (health plans, health care clearinghouses, and health care providers that conduct certain transactions electronically) and their business associates, as defined in 45 CFR §160.103.
A business associate is a person or company that creates, receives, maintains or transmits PHI on behalf of a covered entity, or provides certain services to it that involve PHI. A subcontractor is anyone a business associate delegates a function to, and subcontractors handling PHI carry business associate obligations too.
| Situation (illustrative) | Likely HIPAA role | What it means for the software |
|---|---|---|
| A clinic's own patient portal, built and run by the clinic | Covered entity | Clinic owns full Privacy, Security and Breach obligations |
| A vendor hosting and operating that portal for the clinic | Business associate | Vendor must sign a BAA and meet the Security Rule |
| The cloud provider storing the vendor's ePHI | Subcontractor (business associate) | BAA between vendor and cloud provider |
| A consumer wellness app people download and use on their own, with no covered entity involved | Often outside HIPAA | Other laws may apply; check HHS and FTC app resources |
These rows are illustrative, not legal conclusions. HHS publishes health app guidance that "explains when an app developer may be acting as a business associate", and links to an FTC tool covering other federal laws that may apply to health apps.
HIPAA Security Rule requirements: required vs addressable
Every Security Rule implementation specification is labelled either "Required" or "Addressable" in the regulation text. Required specifications must be implemented. Addressable does not mean optional: the organisation must assess whether the specification is reasonable and appropriate, implement it if so, and if not, document why and implement an equivalent alternative where reasonable.
This distinction is where most online checklists go wrong. Encryption and automatic logoff, for example, are addressable under the current rule, not flat mandates. In practice, many teams do implement them, because skipping them requires a documented justification that holds up to scrutiny.
Administrative safeguards
Administrative safeguards are the management processes behind the software. The standards in §164.308 that most affect engineering teams are:
| Standard / specification | Label | Engineering implication |
|---|---|---|
| Risk analysis | Required | Assess risks to ePHI across every system, data store and integration before design is final |
| Risk management | Required | Turn findings into backlog items and track them to closure |
| Information system activity review | Required | Someone must regularly review audit logs and access reports, not just collect them |
| Assigned security responsibility | Standard | A named security official |
| Security awareness and training (incl. log-in monitoring, password management) | Standard; specs Addressable | Training for everyone with access, including engineers |
| Security incident procedures: response and reporting | Required | Runbooks to identify, respond to, mitigate and document incidents |
| Contingency plan: data backup, disaster recovery, emergency mode operation | Required | Retrievable exact copies of ePHI and tested restore paths |
| Evaluation | Standard | Periodic technical and non-technical evaluation after changes |
| Business associate contracts | Required (written contract) | BAAs with every vendor that handles ePHI for you |
HHS describes risk analysis as "the first step" in the security process and notes that the Security Rule does not prescribe a specific methodology. NIST SP 800-66 Rev. 2 (February 2024) is NIST's resource guide for implementing the Security Rule and is a useful structure for that work.
Physical safeguards
Physical safeguards in §164.310 cover facility access, workstation use and security, and device and media controls. For cloud-hosted software, much of the facility layer sits with the cloud provider under its BAA, but your team still owns workstation policy for laptops that can reach ePHI, and the required disposal and media re-use specifications: ePHI must be removed before media is reused or disposed of.
Technical safeguards
Technical safeguards in §164.312 are the ones developers implement directly in code and infrastructure. Here is each one with its exact label:
| Standard | Implementation specification | Label | What it looks like in software |
|---|---|---|---|
| Access control | Unique user identification | Required | No shared accounts; every human and service has its own identity |
| Access control | Emergency access procedure | Required | A controlled, logged "break-glass" path to ePHI |
| Access control | Automatic logoff | Addressable | Session timeouts set by risk |
| Access control | Encryption and decryption | Addressable | Encryption at rest for databases, files, backups |
| Audit controls | (standard only) | Standard | Mechanisms that "record and examine activity" in systems holding ePHI |
| Integrity | Mechanism to authenticate ePHI | Addressable | Checksums, signed records, write controls against improper alteration |
| Person or entity authentication | (standard only) | Standard | Verify that a user or system is who it claims to be |
| Transmission security | Integrity controls | Addressable | Detect modification in transit |
| Transmission security | Encryption | Addressable | TLS for every network path carrying ePHI |
Two details matter for builders. First, the current rule does not name multi-factor authentication; it requires "procedures to verify" identity, and MFA is one common way to meet that. Second, audit controls must record and examine activity, but the scope and depth of logging is set by your risk analysis, and the administrative side requires that someone actually reviews it.
Is encryption required under HIPAA?
Under the current Security Rule, encryption at rest and in transit is addressable, not required. That said, the breach rules give a strong reason to encrypt. A breach notification duty applies to "unsecured" PHI, defined in §164.402 as PHI not rendered unusable, unreadable or indecipherable using a method HHS specifies.
HHS's breach guidance names those methods: encryption of data at rest consistent with NIST SP 800-111, encryption in transit that complies with NIST SP 800-52 (TLS), 800-77 or 800-113, and media destruction consistent with NIST SP 800-88. It also says decryption keys should be stored separately from the data they protect. In practice that means managed key storage and a policy that keys never sit next to the database they unlock.
Status of the 2025 HIPAA Security Rule proposal (as of October 2026)
As of 26 October 2026, the proposed changes to the HIPAA Security Rule are not final. HHS's Office for Civil Rights issued the proposal on 27 December 2024, and it was published in the Federal Register on 6 January 2025 (90 FR 898, RIN 0945-AA22). The Federal Register lists no final rule under that RIN, and HHS's fact sheet states that "the current Security Rule remains in effect" while rulemaking continues.
The most recent Unified Agenda entry for the rule lists it as a long-term action with final action targeted for July 2027. The 2025 Spring agenda had targeted May 2026. Agenda dates are targets, not commitments.
According to HHS's fact sheet, the proposal would, among other changes:
- Remove the distinction between required and addressable specifications, with limited exceptions.
- Require encryption of ePHI at rest and in transit, and multi-factor authentication, each with limited exceptions.
- Require a technology asset inventory and a network map of ePHI movement, reviewed at least every 12 months.
- Require written procedures to restore certain systems and data within 72 hours.
- Require vulnerability scanning at least every six months and penetration testing at least every 12 months.
None of these are law today. Many teams build to them anyway, because they are good security practice and retrofitting later costs more. Just do not describe them to clients or auditors as current requirements.
Business associate agreements: vendors, cloud and AI services
A business associate agreement (BAA) is the written contract HIPAA requires before a vendor creates, receives, maintains or transmits ePHI on a covered entity's or business associate's behalf (§164.308(b), §164.314). The contract must require the vendor to comply with the Security Rule, flow the same terms down to its own subcontractors, and report security incidents and breaches.
HHS's sample BAA provisions also cover permitted uses, support for patients' access and amendment rights, return or destruction of PHI at termination, and HHS access to records. HHS notes the sample language alone "may not be sufficient" to form a binding contract under state law.
For software teams, the BAA question applies to every service in the architecture:
- Cloud hosting. HHS's cloud computing guidance says a cloud provider that stores ePHI is a business associate even if it holds only encrypted data and has no key. The "conduit" exception is "limited to transmission-only services".
- Email, logging, monitoring, error tracking and support tools. If ePHI can reach them, they need a BAA or must be configured so ePHI never does.
- AI and LLM APIs. The same test applies. If a prompt or file sent to a model provider contains PHI, that provider is handling PHI on your behalf, so you need a BAA covering that specific product and configuration, or you keep PHI out of the request. Vendor BAA terms vary by product tier and change over time, so check current terms before you design around one.
De-identification for test data and analytics
De-identified health information is not PHI, so it falls outside the Privacy Rule. HIPAA allows two methods under §164.514(b): Safe Harbor, which removes 18 listed identifiers and requires no actual knowledge that the rest could identify someone, and Expert Determination, where a qualified expert determines and documents that the re-identification risk is "very small".
HHS's de-identification guidance clears up two common errors:
- Under Safe Harbor, all date elements except the year are removed, and ages over 89 are grouped as 90 or older. The first three ZIP digits may stay only if that three-digit area contains more than 20,000 people; otherwise they become 000.
- Under Expert Determination, there is "no explicit numerical level" of risk that universally qualifies. Any fixed percentage you see quoted is a choice, not a HIPAA rule.
The engineering takeaway: staging, QA and demo environments should run on synthetic or properly de-identified data. Copying production PHI into a test database extends every safeguard and BAA obligation to that environment.
Building HIPAA compliance into the software development life cycle
The most reliable way to build HIPAA compliant software is to attach each Security Rule duty to a phase of your existing software development life cycle, so compliance work happens as normal engineering work rather than a pre-launch scramble.
| SDLC phase | Activity | HIPAA hook |
|---|---|---|
| Discovery and requirements | Map every place PHI enters, is stored, moves and leaves; record minimum-necessary access per role in the product requirements document | Risk analysis scope; minimum necessary |
| Architecture | Choose services with BAAs; plan tenant and data isolation; key management | §164.308(b), §164.312, cloud guidance |
| Backlog and stories | Write security requirements as testable acceptance criteria (for example, "PHI fields never appear in application logs") | Risk management |
| Build | Unique IDs, role checks, audit events, TLS everywhere, encryption decisions documented | §164.312 technical safeguards |
| Test | Synthetic or de-identified test data; access-control and logging tests; security testing | §164.514; evaluation |
| Release | Incident runbook, backup and restore tested, documentation filed | §164.308(a)(6), (a)(7); §164.316 |
| Operate | Regular log review, access reviews, re-run risk analysis after significant changes | §164.308(a)(1), (a)(8) |
Documentation is part of the build. Policies and any required records must be kept for six years from creation or from when they were last in effect, whichever is later.
If the product is multi-tenant, data isolation deserves its own design review. Our guide to multi-tenant architecture covers the isolation models, and SaaS security best practices covers the wider controls most HIPAA programmes build on.
Breach notification: what the software must support
Software must give its operator enough information to meet breach deadlines. A business associate must notify the covered entity without unreasonable delay and no later than 60 calendar days after discovering a breach of unsecured PHI, identifying affected individuals where possible.
The covered entity must then notify affected individuals on the same "without unreasonable delay, no later than 60 days" basis, and notify HHS: at the same time for breaches affecting 500 or more people, or in an annual log for smaller ones. Sixty days is a ceiling, not a target. BAAs often set shorter reporting windows, so engineering needs audit trails that can answer "whose records were accessed, when, and by whom" quickly.
Penalties for violations are tiered by culpability under §160.404, and the dollar amounts are adjusted for inflation every year and published at 45 CFR Part 102.
Common gaps in HIPAA software projects
Most compliance problems in software projects come from data flowing somewhere nobody mapped. The recurring ones:
- PHI in logs, traces and error reports sent to tools with no BAA.
- Production PHI copied into staging or developer laptops.
- Third-party scripts and SDKs (analytics, chat widgets, session replay) on pages where PHI is entered or displayed, without assessing what they receive.
- Missing subcontractor BAAs further down the chain, such as a vendor's own email or storage provider.
- SOC 2 or HITRUST treated as "HIPAA compliance". These private frameworks can provide useful evidence, but HHS does not recognise private certifications as satisfying the Security Rule, and they do not replace a BAA.
- A template risk analysis that does not reflect the real system, and is never updated after architecture changes.
How to evaluate a HIPAA software development partner
A development partner that will access, host or process PHI for you is likely a business associate and should sign a BAA. One that works only with synthetic data and never touches PHI may not need one. Either way, the questions below separate partners who understand the rules from those who repeat marketing claims. You can fold them into a software development RFP.
| Question to ask | A good answer shows |
|---|---|
| Will your team access PHI, and will you sign a BAA? | Clear view of their role; willingness to sign where they handle PHI |
| Which specifications are required vs addressable, and how do you document addressable decisions? | Knowledge of §164.306(d), not "everything is required" or "we're HIPAA certified" |
| How do you keep PHI out of logs, test data and third-party tools? | Specific techniques: field redaction, synthetic data, BAA-covered tooling |
| Which cloud services will hold ePHI, and are they under a BAA? | Named services and the BAA chain |
| How will the build support our risk analysis and breach deadlines? | Data-flow maps, audit events, restore tests, documentation handover |
| What is your view of the 2025 Security Rule proposal? | Knows it is proposed, not final, and can design for it without claiming it is law |
Be wary of any partner, tool or platform that calls itself "HIPAA certified". As HHS has said, no such certification is recognised.
How GainHQ can help
GainHQ is a custom software development company with 15+ years of building software, 13+ products shipped, and a team of 30+. We build our own products, including Payrun (HR and payroll) and Gain.io (CRM and helpdesk). If you are planning software that will handle sensitive data, we can help with architecture, requirements and secure delivery practices, working alongside your compliance and legal advisers. GainHQ does not provide legal advice or compliance certification. See our custom software development services.
Frequently asked questions
Is there a HIPAA certification for software?
No. HHS states it does not endorse or recognise private organisations' "certifications" for the Security Rule, and such certifications do not remove legal obligations. Compliance belongs to the covered entity or business associate operating the software, not to the product itself.
Is encryption required by HIPAA?
Under the current Security Rule, encryption at rest and in transit is "addressable": you must implement it if reasonable and appropriate, or document why not and use an equivalent measure. Encrypting to HHS-specified standards also means lost data may not count as "unsecured" PHI for breach notification.
Is multi-factor authentication required under HIPAA?
Not under the current rule, which requires procedures to verify that a person or entity is who they claim to be. MFA is a common way to meet that. The January 2025 Security Rule proposal would require MFA with limited exceptions, but as of October 2026 it is not final.
Has the 2025 HIPAA Security Rule update been finalised?
No, as of 26 October 2026. It was published as a proposed rule on 6 January 2025, HHS says the current rule remains in effect, and the latest Unified Agenda targets final action for July 2027. Check HHS for updates.
Does my health app need to be HIPAA compliant?
It depends on your role. If you create, receive, maintain or transmit PHI for a covered entity, you are likely a business associate. A consumer app used independently may fall outside HIPAA but still be subject to other laws. HHS and the FTC publish tools for working this out.
Is SOC 2 or HITRUST enough for HIPAA?
No. They are private frameworks and can supply useful evidence, but HHS does not recognise private certifications as meeting the Security Rule. You still need a risk analysis, the required safeguards and a BAA wherever a vendor handles PHI for you.
Do cloud providers need to sign a BAA?
Yes, if they store or process ePHI for you. HHS says a cloud provider holding only encrypted ePHI without the key is still a business associate. The conduit exception covers transmission-only services, not storage.
What are the HIPAA technical safeguards?
Section 164.312 sets five standards: access control, audit controls, integrity, person or entity authentication, and transmission security. Unique user IDs and emergency access are required; automatic logoff, encryption and integrity mechanisms are addressable.