Healthcare apps
HIPAA compliant app development: what we build, and what stays your job
HIPAA compliant app development means building software in which the Security Rule's technical safeguards (access control, audit controls, integrity, authentication and transmission security) are implemented as specified, protected health information is kept to the minimum, and every vendor that touches it is under a business associate agreement. We build those parts. Compliance itself is your programme, run with your counsel.
- Safeguards
- 45 CFR 164.312, built in
- Hosting
- Your AWS, Google Cloud or Azure account
- Our access to PHI
- Designed to be none
- Web app range
- $5,500–22,000 indicative
Updated · By the Codebrix team
What the phrase means, and what it does not
HIPAA's rules bind covered entities (health plans, clearinghouses and providers who transact electronically) and their business associates. Under 45 CFR 160.103, a business associate is anyone who creates, receives, maintains or transmits protected health information (PHI) on a covered entity's behalf, and that includes subcontractors doing the same for a business associate. Whether your app is in scope depends on who you are and whose data it holds. Settle that with counsel first.
There is no certificate to buy. AWS states there is no HIPAA certification for a cloud provider, and Microsoft says there is no HHS-approved certification programme. What we can do is implement the safeguards, document each one, and give your compliance lead evidence for their risk analysis.
Our healthcare page for clinics covers India's rules; this page is for the US.
The technical safeguards, mapped to the build
Administrative and physical safeguards are mostly your policies and premises. The technical ones in 45 CFR 164.312 land in our code:
| Standard and specification | Status in the rule | How we build it |
|---|---|---|
| Access control: unique user identification | Required | Individual accounts only, no shared logins; your SSO where you have one |
| Access control: emergency access procedure | Required | A documented break-glass role that is time-limited, logged and alerted |
| Access control: automatic logoff | Addressable | Idle timeouts on web and app sessions, short-lived tokens, re-authentication for exports |
| Access control: encryption and decryption | Addressable | Encryption at rest with cloud-managed keys; field-level encryption for the most sensitive columns |
| Audit controls | Standard (no sub-specifications) | An append-only log of who viewed, created, changed or exported which record, and when |
| Integrity: authenticate ePHI | Addressable | Record versioning instead of overwrites, checksums on stored files, backups proven by test restores |
| Person or entity authentication | Standard (no sub-specifications) | Multi-factor sign-in for staff; scoped keys for service-to-service calls |
| Transmission security: integrity and encryption | Addressable | TLS on every connection, HSTS, and no PHI in push notification, SMS or email text |
Addressable does not mean optional. Under 45 CFR 164.306(d), you must assess whether each addressable specification is reasonable and appropriate, implement it if so, and otherwise document why and adopt an equivalent measure where reasonable. We implement every one in the table by default. If you decide otherwise, that decision and its record sit with your compliance lead.
HHS's proposed rule of 27 December 2024 would, among other changes, require encryption of ePHI at rest and in transit with limited exceptions. The current rule stays in effect meanwhile; as of November 2026 we found no final rule, so check the linked page.
Business associate agreements, with cloud vendors and everyone else
HHS's guidance on cloud computing says a cloud provider that stores ePHI is a business associate even if the data is encrypted and it holds no key, and that a covered entity using one without a BAA is in violation of the HIPAA Rules. All three major clouds offer a BAA, each in its own way (as of November 2026):
| Cloud | How the BAA is offered | What to check |
|---|---|---|
| AWS | A standard Business Associate Addendum, reviewed and accepted in AWS Artifact in the console | Keep PHI in services on AWS's HIPAA Eligible Services list |
| Google Cloud | Customers must review and accept Google's BAA; Google says to talk to your account manager to execute it | Keep PHI in products the BAA covers; Google says building a compliant solution is the customer's job |
| Microsoft Azure | Included in the Microsoft Product Terms by default for covered entities and business associates | Keep PHI in in-scope Azure services |
The same test applies to email, SMS, error tracking, analytics, support desk and AI model APIs: each signs a BAA covering that service or never receives PHI.
Keeping PHI small
The Privacy Rule's minimum necessary standard, in 45 CFR 164.502(b), asks covered entities and business associates to make reasonable efforts to limit PHI to the minimum needed for the purpose. In a build, that turns into concrete choices:
- A data inventory before design: each field, why it is needed, who sees it, how long it is kept.
- Fewer fields: pick lists over free text, and no date of birth unless matching needs it.
- Role-based views: the front desk sees the schedule, billing sees billing, clinicians see notes.
- Synthetic data only in development and staging; production in your cloud account, with no production database credentials for our engineers.
- Exports gated by role and logged; no PHI in URLs, notifications, crash reports or analytics.
De-identification for analytics, testing and AI features
45 CFR 164.514 gives two routes. Expert determination: a qualified expert applies statistical methods and documents that the risk of identifying anyone is very small. Safe harbor: remove 18 kinds of identifier, and have no actual knowledge that what remains could identify someone. The safe harbor list surprises product teams, because it includes:
- All elements of dates except the year, such as appointment, admission and discharge dates, and ages over 89.
- Geographic units smaller than a state, with a narrow exception for the first three digits of some ZIP codes.
- Web URLs and IP addresses, so raw server logs and analytics data are not de-identified by default.
- Device identifiers and serial numbers, full-face photos and any other unique identifying number or code.
For AI features, the model gets only what the task needs. If PHI must reach an AI provider, that provider signs a BAA covering the service; otherwise we de-identify first.
Logs and tracking: where PHI leaks
Application logs and error trackers are where PHI often escapes, inside a request body or error message. We scrub at the logger, so sensitive fields never leave the app, and test that with fake records.
HHS's bulletin on online tracking technologies says tracking code on user-authenticated pages generally has access to PHI, and that such vendors need a BAA and a permitted basis before PHI is disclosed. On 20 June 2024 a federal court in Texas vacated the part of that bulletin dealing with unauthenticated public pages, and HHS notes this on the page. Our default: no third-party pixels or session replay on logged-in pages, booking flows or the portal sign-in page.
Timeline, cost and what you provide
Our indicative ranges are $5,500 to $22,000 for a web application over 6 to 16 weeks and $9,000 to $33,000 for an iOS and Android app over 8 to 20 weeks. Audit logging, break-glass access, key management and vendor reviews add time, and the fixed quote after discovery reflects them. You pay per milestone. We work remotely from Noida; our page for US businesses covers hours and contracts, and medical practice websites covers the public site around the app.
From you: counsel and a named privacy or security officer, your risk analysis (or who will do it), and cloud accounts in your company's name with the BAA accepted before PHI arrives.
Frequently asked questions
Can you guarantee our app will be HIPAA compliant?
No. HIPAA compliance covers your whole organisation: policies, training, risk analysis, vendor contracts and staff behaviour, not only software. We implement the Security Rule's technical safeguards as specified, keep PHI to the minimum, and document each control for your compliance lead and counsel.
Will Codebrix sign a business associate agreement?
If our team will create, receive, maintain or transmit PHI on your behalf, HIPAA requires a BAA, and we settle that during discovery before any access is granted. We prefer designs in which our engineers never handle production PHI: we work on synthetic data and your staff hold production access, so the question may not arise.
Which cloud should a HIPAA app run on?
AWS, Google Cloud and Microsoft Azure all offer a BAA as of November 2026, each covering a defined list of services. Pick the one your team already knows, accept the BAA before PHI arrives, and keep PHI inside covered services only. We set the account up in your company's name, not ours.
Does HIPAA require encryption?
Under the current Security Rule, encryption is addressable: you assess it and either implement it or document a reasonable alternative. HHS proposed in December 2024 to make it required with limited exceptions; we found no final rule as of November 2026. We encrypt at rest and in transit by default.
Can we use large language models in a HIPAA app?
Only if the AI provider signs a BAA that covers the specific service you call, or if the data is de-identified first under HIPAA's expert determination or safe harbor method. Check each provider's current terms. We design AI features to send the minimum text needed, and keep prompts and responses out of general application logs.
Does every health app need HIPAA?
No. HIPAA applies to covered entities and their business associates. A consumer app people use on their own, with no covered entity behind it, may fall outside HIPAA, though other federal and state laws can apply. Ask counsel before you design the data model.
Sources
- 45 CFR 164.312, Technical safeguards (LII, Cornell)
- 45 CFR 164.306, Security standards: general rules (LII, Cornell)
- 45 CFR 160.103, Definitions incl. business associate (LII, Cornell)
- 45 CFR 164.502, Minimum necessary (LII, Cornell)
- 45 CFR 164.514, De-identification (LII, Cornell)
- HHS: Guidance on HIPAA and Cloud Computing
- HHS: Use of Online Tracking Technologies by HIPAA Covered Entities and Business Associates
- HHS: 2025 HIPAA Security Rule Notice of Proposed Rulemaking
- AWS: HIPAA compliance
- Google Cloud: HIPAA compliance
- Microsoft Learn: HIPAA and Azure
Related
Medical practices, US
Medical practice website design for US practices that keeps PHI out of the wrong places
Medical practice website design for US clinics: booking and patient forms planned around PHI, no ad pixels on PHI pages, honest reviews and WCAG 2.2 AA.
Read moreWeb applications
Custom web application development for portals, dashboards and internal tools
Custom web application development for portals, dashboards and internal tools: roles, Postgres, integrations and tests. Fixed price, code in your name.
Read moreMobile apps
A mobile app development company in India for iOS and Android
Mobile app development company in India building iOS and Android apps with React Native or Flutter. Fixed quote, weekly test builds, store launch handled.
Read moreHealthcare
A healthcare app development company in India that builds for clinics
Healthcare app development company in India for clinics: booking, reminders, patient portals and websites, built with the DPDP Act and ABDM in mind.
Read moreAI integration
AI integration services for the software you already run
AI integration services that add LLM assistants, document search, summaries and classification to your product, tested on your data with cost limits set.
Read moreUnited States
An offshore web development company in India for US businesses
Offshore web development company in India for US businesses: USD pricing, Stripe or wire payment, IP assigned to you, and a planned ET and PT overlap.
Read more