Skip to main content

HIPAA Compliant App Development: Requirements, Architecture, and Cost

hero image

If your product is going to be storing or transmitting patient data for a US clinic, hospital, or health plan, then you must follow HIPAA compliant app development practices. It’s not just standard app development; HIPAA requirements dictate certain aspects of your architecture from the very beginning of the engineering process.

This guide is for emerging healthcare businesses and provider organizations looking at HIPAA compliance. It covers who must comply, the HIPAA requirements for healthcare apps that process protected health information (PHI), current and proposed safeguards, when an app builder is sufficient, and the factors that affect cost.

What Is HIPAA Compliant App Development?

HIPAA compliant app development involves designing, building, and operating software to ensure the organization meets HIPAA requirements for all protected health information the app processes. HIPAA regulates organizations and their data handling practices; it does not certify code, frameworks, or app listings. Compliance depends on the operating company, not the app itself.

Diagram of four HIPAA terms: Covered entity, BAA contract, Business associate, and PHI

Four terms carry most of the weight:

  • Protected health information. Individually identifiable health information that a covered entity or its business associate holds or transmits, in any form. The electronic kind is called ePHI (HHS, Summary of the HIPAA Privacy Rule).
  • Covered entity. Health plans, health care clearinghouses, and most health care providers (HHS, Health App Use Scenarios & HIPAA, 2016).
  • Business associates. Companies that create, receive, maintain, or transmit PHI on a covered entity’s behalf. Among its examples, HHS lists an app developer contracted by a provider and a cloud service provider that stores ePHI (HHS, Business Associates FAQs).
  • Business associate agreement (BAA). The contract that binds a business associate to protect the PHI it receives.

Teams often underestimate how much of their patient data counts as PHI. 

Under the Safe Harbor de-identification method, HHS lists 18 identifiers that must be removed before sensitive health data stops being PHI. The obvious ones are names and SSNs. The list also includes email addresses, device identifiers and serial numbers, IP addresses, full-face photos, and all date elements more specific than a year.

Does Your App Need to Be HIPAA compliant?

Whether you need to build a HIPAA compliant mobile app depends on your client and who you send the data to rather than the features of the app. HHS makes it clear that the same functionality (e.g., glucose tracking) may or may not be covered by HIPAA depending on whether a covered entity is involved.

SituationDoes HIPAA apply?Why
A provider contracts you for an app its patients use for remote patient monitoring, messaging, or telemedicine, and the data flows into its EHRYesYou handle PHI on the provider’s behalf, which makes you a business associate
A health plan offers members your app to view records and check claimsYesYou are a business associate of the plan
You build or run patient portals or an EHR for a clinicYesThe portal or record system is offered by a covered entity
A consumer downloads your wellness app and enters her own readingsNoNo covered entity is involved
A doctor recommends your app and the patient sends a report from itNoThe doctor did not hire you to handle PHI
A consumer asks your app to exchange data with her provider’s EHRNoYou act for the consumer, not for the provider

You’re not exempt from regulation just because you’re not subject to HIPAA. The FTC’s Health Breach Notification Rule applies to vendors of personal health records that fall outside of HIPAA’s scope, and as of July 2024, health app and connected device makers are subject to it. The FTC Act and state privacy laws may also apply. The FTC has a Mobile Health Apps Interactive Tool (developed with HHS and the FDA) which will help you determine which federal laws apply.

Five questions will tell you where you stand:

  1. Is your customer, or whoever pays you, a provider, a health plan, a clearinghouse, or one of their contractors?
  2. Does the app create, receive, store, or send health information that can be tied to a person?
  3. Who decides where the data goes: the patient or the covered entity?
  4. Has a client asked you to sign a BAA, or will one expect it?
  5. If you also sell a direct-to-consumer version, is its data kept separate from the version you run for covered entities?

If the first four answers point toward a covered entity, build HIPAA requirements from the first sprint. The same applies to healthcare apps on mobile, on the web, or on both. If the answers are mixed, walk through them with our healthcare software team before the architecture is fixed.

HIPAA Rules Developers Must Follow

Three rules shape the product. A fourth document, still a proposal, may change one of them.

Diagram of HIPAA rules: Privacy Rule, Security Rule, Breach Notification Rule, and Proposed Security Rule update

Privacy Rule

The Privacy Rule determines what you can do with patient data. It sets out the permitted uses and disclosures of protected health information and gives patients rights in relation to that data.

Developers are most impacted by HHS’s Minimum Necessary standard. The covered entity must limit the use, disclosure, or request of PHI to the minimum necessary for the intended purpose. That said, the standard does not apply to disclosures for treatment or to the patient. In practice, you’d limit each screen and each API response to the user’s role. A billing clerk shouldn’t be able to see clinical notes, and an analytics event shouldn’t contain a diagnosis.

HIPAA Security Rule

The HIPAA Security Rule applies to electronic PHI. It requires covered entities and business associates to implement administrative safeguards, physical safeguards, and technical safeguards to ensure the confidentiality, integrity, and availability of that data.

Two aspects of the rule are often a source of confusion. One is that it doesn’t specify technologies at all, but rather requires reasonable and appropriate measures taking into account the size of your organization, the systems you have, and your risk profile. The other is that implementation specifications are either required or addressable. An addressable control is not optional; you either implement it or you document why it is not reasonable and provide an equivalent alternative (HHS, FAQ 2001, 2013).

This is where IT security and compliance part ways. Proper risk assessment and documentation underpin strong data security and access controls. Documentation without controls is of no value.

Breach Notification Rule

Diagram of HIPAA breach notification timelines for affected individuals, HHS, media, and business associates, plus encrypted PHI note

A breach is an impermissible use or disclosure that compromises PHI, and it is presumed to be one unless a risk assessment shows a low probability that the data was compromised. The deadlines, as set out in HHS guidance on the Breach Notification Rule:

  • Affected individuals: without unreasonable delay, and no later than 60 days after discovery.
  • HHS: within the same 60 days when 500 or more people are affected. Smaller breaches are reported once a year, within 60 days after the year ends.
  • Media: when a breach affects more than 500 residents of one state or jurisdiction.
  • Business associates: notice to the covered entity no later than 60 days after discovery. Check your BAA, because clients often negotiate a shorter window.

One detail matters for architecture. The rule covers unsecured PHI. Patient data encrypted by a method HHS recognizes is not unsecured, so its loss does not trigger notification.

What the Proposed Security Rule Update Means for New Apps

HHS has put out the first significant rewrite of the HIPAA Security Rule in years, and it is not law. The notice of proposed rulemaking was published in the Federal Register on January 6th 2025 (90 FR 898), with the comment period closing on March 7th 2025. As of the date of writing (November 2026), no final rule has been published, and HHS states that the existing Security Rule remains in effect. The proposal is still in progress and could be modified, delayed, or withdrawn at any point, so check its status before you make any reliance on anything in this section.

According to the HHS fact sheet, the proposal would:

  • remove the split between required and addressable specifications, with limited exceptions;
  • require encryption of ePHI at rest and in transit;
  • require multi factor authentication;
  • require a technology asset inventory and a network map of how ePHI moves, updated at least every 12 months;
  • require vulnerability scans every six months, penetration tests every 12 months, and a compliance audit every 12 months;
  • require written procedures to restore lost systems and data within 72 hours;
  • require business associates to verify their technical safeguards every year.

None of this binds a new app today, but most of it is what a careful team does anyway. If you start a build now, encrypt by default, plan multi-factor authentication for every account that reaches PHI, keep the data flow map current, and budget for ongoing monitoring and testing.

Technical Safeguards Every HIPAA compliant App Needs

Technical safeguards are set out in 45 CFR 164.312 and comprise five standards: access control, audit controls, integrity, person or entity authentication, and transmission data security (HHS, Security Standards: Technical Safeguards). For each of these, we note the current requirements, the proposed 2025 changes, and the best practice.

Diagram of HIPAA administrative safeguards: risk analysis, policies and ownership, workforce training, contingency planning, and business associates

Data Encryption at Rest and in Transit

Under the current rule, encryption of data at rest and in transit is an addressable implementation specification. That means you either implement it, or you document why it isn’t reasonable and appropriate in your case and put an equivalent alternative measure in place (HHS, FAQ 2001, 2013). The 2025 proposal would make encryption required, with limited exceptions.

Treat encryption as a must-have. It’s very difficult to justify having unencrypted patient records in any environment, and PHI encrypted with a method HHS recognizes is not considered unsecured, so losing it doesn’t trigger breach notification. Use TLS for all connections (including internal), encrypt your databases, your backups, and your file storage with your keys properly secured. You must track all your data copies (caches, exports, crash dumps, etc.) in secure data storage.

User Authentication and Multi-Factor Authentication

The current rule requires that you verify the identity of any individual or system that is requesting ePHI and assign them a unique ID. It makes no requirement as to passwords, biometrics, or MFA. So to say that HIPAA requires MFA at this time is incorrect. MFA would be required under the proposed rule with a few limited exceptions.

Enable MFA for clinicians, administrators, support staff, and anyone with production access as a standard security measure.

Role-Based Access Control

The rule requires access controls that will only allow authorized individuals and software to access ePHI. It doesn’t specify a particular model, but role based access controls are very commonly used and are consistent with the minimum necessary standard of the Privacy Rule, which would expect access to be consistent with job functions.

Define roles on the basis of actual job functions, default deny access, regularly review the access lists, and remove access straight away when someone leaves.

For a telehealth solution with remote patient monitoring for a US clinic, we were looking at streaming data from wearables that was stored in the cloud. Patient data was protected via encryption, access controls, regular security audits, and by archiving the older records so that the data in play was always current.

Audit Logs and Audit Trails

Audit controls are required (you must implement controls to record and review activity in systems that contain ePHI). The standard doesn’t specify what needs to be logged or for how long, so your risk analysis will need to determine that. The proposal would require a compliance audit every 12 months.

A practical baseline would be to log every view, every change, every export, and every deletion of PHI (including user, time, and record details), as well as logins, failed logins, and permission changes. Audit trails should be append-only, admin access should be restricted, and alerts should be set for any anomalous activity. PHI should not be in the log text.

Data Integrity, Backups, and Emergency Access

The integrity standard requires policies and procedures to protect ePHI from improper alteration or destruction. An emergency access procedure is also required to allow authorized staff to access the records in the event of an outage or crisis. Backup and disaster recovery plans are part of the administrative safeguards in 45 CFR 164.308(a)(7). The proposal would require written procedures for the restoration of systems and data within 72 hours.

Use checksums and record versioning to ensure data integrity. Carry out regular restore drills to confirm your backups work. Emergency access should be time-limited, granted to a single individual, and properly logged.

Mobile-Specific Measures

These are the best practices for building a HIPAA compliant mobile app. The current rule 

has no mobile-specific section, and the closest specification, automatic logoff, is addressable. HHS guidance on cloud computing states that covered entities and business associates may use cloud services for ePHI, provided they sign a BAA with the provider and keep the required safeguards for healthcare apps in place (HHS, Guidance on HIPAA & Cloud Computing, 2016). When the patient data lives in the cloud, the device that reaches it still needs its own protection:

  • Short session timeouts, with user authentication repeated before PHI is shown again.
  • No PHI stored on the device where you can avoid it. Fetch on demand, and encrypt and expire anything you must cache.
  • Remote wipe capabilities, or at least remote session revocation, for staff devices.
  • Hidden content in the app switcher and no PHI in screenshots or notifications.

Teams that offer mobile app development services treat these as routine, and our guide to healthcare mobile app development covers the platform details.

Administrative and Physical Safeguards

These rules are about people and process, and no amount of good code replaces them. The administrative safeguards, in 45 CFR 164.308, come down to five habits:

  • Risk analysis. A required, documented assessment of risks to all the ePHI you hold. HHS sets no method or frequency, but expects the process to be ongoing (HHS, Guidance on Risk Analysis, 2010).
  • Policies and ownership. Written security policies, a named security official, and sanctions for staff who break the rules.
  • Workforce training. Security awareness for everyone with access, developers and support agents included.
  • Contingency planning and evaluation. Backup, recovery, and periodic reviews of whether your measures still work.
  • Business associates. A signed contract with every subcontractor that handles PHI for you.

Physical safeguards cover facility access, workstations, and devices and media. For a cloud-hosted app, the data center belongs to the provider under its BAA. Laptops, office access, test phones, and the disposal of old hardware stay with you.

Data migration and staff onboarding are where these safeguards get tested. When we built an EHR system for a network of children’s clinics in the UK, the team moved records from paper files and a legacy CRM by cleaning and verifying the data, mapping old fields to the new database, and validating the result. Staff training ran as four days of consultations, one set per department.

HIPAA compliant Infrastructure and Business Associate Agreement

Host PHI only with a cloud provider that has signed a business associate agreement with you, and assume the configuration is your job. HHS is direct on the first point. A cloud provider that stores ePHI is a business associate even when it holds only encrypted data and no key, and using one without a BAA is a violation. In its Guidance on HIPAA & Cloud Computing, HHS also notes that it does not endorse or certify any cloud product.

The second point is the shared responsibility model, and the large providers spell it out themselves. AWS limits PHI to its HIPAA-eligible services and states that customers must configure those services and remain responsible for their own compliance. Microsoft says that using Azure does not automatically make a solution compliant (Microsoft Learn, HIPAA). 

Google Cloud’s HIPAA documentation describes the same split. We name these three as examples only. Our reviews of HIPAA compliant cloud storage and HIPAA compliant hosting providers go into the options.

Three things stay on your side of the line:

  • Secure data storage: Work out which services store PHI and confirm each one is covered by the BAA. Encrypt the data they hold and keep those services off the public internet.
  • Data flows: map every transfer (including email and SMS gateways, logging, analytics, and third-party APIs). Each recipient must have a BAA in place or else no PHI.
  • Integrations. Fast Healthcare Interoperability Resources (FHIR) is the standard way of exchanging records with EHRs. Our article on the FHIR standards goes into more detail as to how that works.

Integrations are also one of the most common reasons a healthcare project runs late. Jelvix’s diabetes and chronic care platform developed a reusable FHIR and HL7 integration framework, which meant there was no need to build a custom integration for each new provider site. That reduced the go-live time from 16-20 weeks to 6.

How to Build a HIPAA compliant App: Step by Step

Building a HIPAA compliant app takes seven steps, and the first three happen before anyone writes code:

  1. Risk assessment. Determine whether HIPAA applies, identify the PHI you will be holding, and open the risk analysis document that all subsequent decisions will be based upon.
  2. Data flow map. Show where the PHI comes in, where it sits, who can see it, and where it goes. Flag every third party.
  3. Architecture: pick the BAA-covered services, then deal with encryption and key management, roles, logging, and how the tenants are separated.
  4. Development: use synthetic data in dev/test environments, keep the secrets out of the code, and review the access checks as rigorously as you review the features.
  5. Security testing: run vulnerability scans and a penetration test, test each role’s permissions, and restore from backup at least once.
  6. Launch. Sign the BAAs, finalize the policies, train the support staff, and confirm who gets the call if an issue arises.
  7. Ongoing compliance. Continue with the ongoing monitoring of logs and alerts, regular review of audit trails and access lists, conduct regular audits, and update your risk analysis as and when the product changes.

HIPAA compliant App Builders vs. Custom Development

App builders, meaning no-code and low-code platforms whose vendors sign a BAA, suit simple cases such as intake forms, scheduling, or a basic internal tool. Custom development is the better choice when the app has to integrate with an EHR, follow a specific clinical workflow, or meet data requirements a platform can’t.

CriterionApp builderCustom development
Feature scopeWhatever the platform’s components allowWhatever the workflow needs
IntegrationsPrebuilt connectors; EHR and device links are limitedBuilt to the systems you use
Control over patient dataData sits in the vendor’s environment and formatYou choose where data lives and how it is structured
ResponsibilityVendor secures the platform; configuration and users are yoursYou own the whole stack, with a cloud provider under BAA
Support and changeTied to the vendor’s roadmap and pricingYour own team or partner, on your schedule

Whichever route you take, the risk analysis, the policies, and user management remain yours. A builder’s BAA covers the platform, not the way you set it up.

If you can’t tell which side your project falls on, an hour with engineers who have shipped healthcare apps under HIPAA usually settles it.

HIPAA compliant App Development Cost

The budget for healthcare apps is dictated by the scope and the amount of PHI you’re going to be handling. HIPAA is rarely just a single line in the estimate. A basic patient portal is a very different project from a full EHR build with device integrations, and they’re both going to be very different in price. All of those factors will have an impact on the overall figure:

  • Type of app. A scheduling tool, a telemedicine platform, and remote patient monitoring carry different loads.
  • Feature scope. Every feature that touches PHI brings its own access rules, logging, and tests.
  • Number of integrations. Each EHR, Fast Healthcare Interoperability Resources (FHIR), or device connection adds work.
  • Expected user base. Scale affects architecture, hosting, and support.
  • Compliance requirements. HIPAA in the US, GDPR if you serve people in the EU, and FDA rules if the software qualifies as a medical device.
  • Security testing. Penetration tests, scans, and remediation before launch and after major releases.
  • Hosting. BAA-covered services from your cloud provider, separate environments, logging, and backups.
  • Support. Monitoring, updates, and periodic reviews for as long as the app runs.

The cheapest saving is PHI you decide not to collect. A field you never store needs no encryption, access rule, or breach plan.

To get a figure for your own scope, request a project estimate. For a wider view across app types, see our breakdown of healthcare app development cost.

Common HIPAA Compliance Mistakes in App Development

Four mistakes are easily made when an app is built in a rush.

Diagram of four common HIPAA mistakes in app development: PHI in push notifications and logs, third-party tools without a BAA, assuming HTTPS is enough, and storing PHI on the device

PHI in push notifications and logs

A lock screen that displays a test result or a debug log that prints out a patient record is going to expose protected health information to anyone who looks at it. How to avoid it: keep your notification text generic (“You have a new message”) and strip any identifiers from your logs.

Third-party tools without a BAA

Analytics SDKs, chat widgets, crash reporters, and email and SMS services often receive patient data, and you may never know. A vendor that handles your PHI is a business associate. How to avoid it? List every SDK and every outbound endpoint and either sign a business associate agreement with each vendor or remove the PHI prior to the data leaving.

Assuming HTTPS is enough

HTTPS protects data in transit. The Security Rule also requires access control, audit controls, integrity, authentication, and the associated administrative controls. How to avoid it: check the design against each of those standards in turn.

Storing PHI on the device

A lost phone with cached records is a reportable incident waiting to happen. How to avoid it: keep the server as the source of truth, and encrypt and expire anything cached.

One mistake is not technical: telling patients nothing about what the software does with their data. When we built an AI chatbot for a private hospital, patients were at first uneasy about AI accessing their personal and medical data. Trust grew once they used the chatbot and got quick, accurate answers. Good data security goes further when users are told, in plain words, what a tool can see and why.

Is There a HIPAA Certification?

There is no official HIPAA certification for apps, for companies, or for cloud services. HHS says nothing in the Security Rule requires a company to certify compliance, that it doesn’t endorse or recognize any certifications issued by private bodies, and that such a certificate in no way precludes HHS from finding a violation at a later date.

What the rule does require is that you periodically assess your technical, administrative, and physical safeguards (either in-house or via an outside firm). Third-party frameworks such as HITRUST and SOC 2 cover many of the same controls and can be useful evidence for your clients. They are not HIPAA certifications, and they do not in any way replace your own risk assessment.

One point on the search term itself. The vast majority of people searching for HIPAA certification are looking for training certificates for individual staff. Those certificates simply prove a person completed a course and tell you nothing about the software.

How Jelvix Approaches HIPAA compliant App Development

Jelvix is a healthcare software development company with 145+ healthcare projects delivered over 16+ years. We hold ISO/IEC 27001, ISO 27701, and ISO 13485 certifications and follow HIPAA-aligned development practices from the architecture stage onward.

The step that matters most for healthcare apps comes before any code. During Compliance and Architecture Planning, specialists work out whether HIPAA, FDA, or GDPR applies, based on where the patients and the data are located, and build those requirements into the architecture. Our security management practices describe how project data is handled internally.

Diagram of seven steps to build a HIPAA-compliant app: risk assessment, data flow map, architecture, development, security testing, launch, and ongoing compliance

A healthtech company running hypertension monitoring services for provider networks in the US and UK had device and EHR data scattered across formats. Our engineers built a remote patient monitoring platform for hypertension around a single data pipeline that connects blood pressure devices, wearables, the EHR, and AI services, without replacing the client’s existing platform. Device onboarding became 70% faster, and risk prediction accuracy improved by 30% over the baseline.

Whether the product is a patient portal, a remote patient monitoring tool, or a HIPAA compliant mobile app for clinicians, the development rewards early decisions. Work out whether the law applies, map the data, choose infrastructure under a BAA, and write the risk analysis before you design the first screen.

FAQ

  • Can an app be HIPAA compliant?

    An app cannot hold compliance status by itself, because HIPAA applies to organizations. It can be built and operated so that the covered entity or business associate behind it meets the Privacy, Security, and Breach Notification Rules. HHS does not certify or approve apps.
  • Does my app need to be HIPAA compliant?

    Yes, if it handles identifiable health information on behalf of a health care provider, a health plan, a clearinghouse, or one of their contractors. A consumer wellness app with no covered entity involved generally falls outside HIPAA. The FTC's Health Breach Notification Rule and state privacy laws may still apply to it.
  • How can I make my app HIPAA compliant?

    Start with a documented risk analysis, then put administrative, physical, and technical safeguards in place for the PHI the app handles. Sign a business associate agreement with your cloud provider and with every vendor that receives patient data.
  • How much does it cost to build a HIPAA compliant app?

    The cost depends on the type of app, the feature scope, the number of integrations with EHRs and devices, the expected user base, and the regulations that apply. Security testing, hosting, and ongoing support add to it. A basic patient portal costs less than a full EHR build with device integrations.
  • How long does it take to build a HIPAA compliant app?

    The timeline for building a HIPAA compliant mobile app depends on scope and integrations. The first operational build typically ships in two to four months, with updates every one to four weeks after that. Jelvix experts name defined scope and responsive stakeholders as the biggest schedule drivers.
  • Is AWS HIPAA compliant?

    AWS signs a business associate agreement with customers and publishes a list of HIPAA-eligible services that may be used for PHI. The customer has to configure those services correctly and stays responsible for its own HIPAA compliance. Hosting on AWS does not make a web product HIPAA-compliant by default.
  • What is the difference between HIPAA and GDPR?

    HIPAA is a US law that applies to covered entities and their business associates, and it protects PHI. GDPR is an EU data security and privacy regulation that protects the personal data of people in the EU in every sector and treats health data as a special category under Article 9. Their deadlines differ too: GDPR expects a breach report to the supervisory authority within 72 hours where feasible, while HIPAA allows up to 60 days to notify individuals. An app that serves both US and EU patients has to meet both.
Rate this article:
Rate this blog

Subscribeto our newsletters

Select topics you are interested in:

Please enter valid email address
Required field

Thank you!

You've successfully subscribed.

Read latest articles

We couldn't process your request

"Something went wrong. Please try again later."

Have a project? Let’s get to  work!

Please enter your name
Please enter valid email address
Please enter from 25 to 500 characters
Required field

Thank you for sharing your needs with us!

We will contact you within 24 hours to discuss your project in more detail.

We couldn’t process your request

"Something went wrong. Please try again later."

Get the AI guide that helps you make smarter business decisions.

Plus, join 3,000+ readers receiving practical tech and business tips — no spam, just results.

BONUS FREE Guide

"Do You Really Need AI for Your Business?"

Please enter a valid name
Please enter a valid email
Required field

Thank you for Subscribing!

We couldn't process your request

Something went wrong. Please try again later.