How to Pick a Healthcare App Development Company
Pick a healthcare app development company that has already shipped software handling protected health information, will sign a business associate agreement with you, and can name the HIPAA-eligible service behind every piece of your stack, from the database to the push notifications. If your app has to read or write records in Epic or Oracle Health, add a fourth test: they have built against a real FHIR sandbox. A shop that passes all four is worth a proposal.
This is for a founder about to hire someone to build a patient-facing or clinician-facing app. You have three proposals, they all say "HIPAA compliant," and the prices are $60,000 apart. Here is how to tell them apart, what the work costs on the market, and when you should not hire an agency at all.
When HIPAA Applies to Your App, and When It Does Not
Start here. Founders either over-build for HIPAA or ignore rules that do apply to them.
HIPAA covers three kinds of organizations, called covered entities: health plans, health care clearinghouses, and health care providers that bill or transact electronically. It also covers their business associates, meaning any company that creates, receives, stores or sends protected health information on a covered entity's behalf. If a clinic, a hospital or an insurer pays you or partners with you, and your app touches their patients' data, you are almost certainly a business associate. So is every vendor under you that touches that data.
Some quick tests:
- A clinic gives your app to its patients to book visits, message a nurse or see lab results. HIPAA applies. You sign a BAA with the clinic.
- A clinician uses your app to chart, triage or review patient data. HIPAA applies.
- A consumer downloads your sleep or cycle tracker and types in their own data, with no provider or insurer involved. HIPAA usually does not apply.
- A consumer app that later sells to health plans crosses the line the day that contract is signed.
Outside HIPAA does not mean outside the law. The FTC's Health Breach Notification Rule covers vendors of personal health records and the companies that serve them, and the July 2024 amendments made it explicit that health apps and connected devices are in scope. If your wellness app pulls data from more than one place, say a wearable plus what the user types in, assume it applies. A breach there means notifying users within 60 calendar days, notifying the FTC (at the same time as users if 500 or more people are affected), and notifying local media when 500 or more residents of one state are hit. Civil penalties run up to $53,088 per violation after the January 2025 inflation adjustment. The FTC has used this rule: GoodRx paid a $1.5 million civil penalty in 2023 for sharing health data with advertising platforms.
One more thing on the calendar. HHS proposed a major update to the HIPAA Security Rule in January 2025 that would make encryption and multi-factor authentication firm requirements instead of "addressable" ones. The final rule has been pushed to an estimated July 2027 on HHS's regulatory agenda. A good agency builds as if it already passed. On a new codebase that costs little.
Which Vendors Sign a BAA
Your app is only as compliant as the least compliant service it sends PHI to. Every one of those vendors needs a business associate agreement, and many only cover certain products or plans. Here is where the common ones stand as of this month. Check each vendor's page again before you sign, because these change.
- AWS offers its BAA through AWS Artifact in the console, and you can accept it yourself. PHI should only live in services on AWS's HIPAA Eligible Services list. You can run other services in the same account, just not with PHI in them.
- Google Cloud signs a BAA that covers a named list of products, including Cloud SQL, Firestore, Cloud Storage, the Cloud Healthcare API and Identity Platform, each with its own conditions. Google's HIPAA page does not list Firebase-branded products. Firebase Authentication, Realtime Database, Crashlytics and Google Analytics for Firebase should be treated as outside the BAA. If an agency proposes "Firebase for everything" on a HIPAA app, ask which pieces they will swap for the Google Cloud equivalents.
- Microsoft Azure includes its HIPAA BAA by default for covered entities and business associates through the Microsoft Product Terms and Data Protection Addendum. It still only covers in-scope services.
- Supabase signs a BAA, but only on the Team or Enterprise plan with the paid HIPAA add-on, and the project has to be configured as a HIPAA project with the required controls left on. A Supabase Pro project does not qualify.
- Twilio signs a BAA only for customers on its Security Edition or Enterprise Edition, and only for products on its HIPAA-eligible list. SMS reminders that carry PHI need both.
- Stripe does not sign BAAs. Payment processing mostly falls under a HIPAA exemption, so it is usually fine, as long as nobody puts a diagnosis or a drug name in a line item description.
The vendors that trip people up are the boring ones: error tracking, session replay, product analytics, email, crash reporting, the AI model you call to summarize a visit. A stack trace with a patient's name in it is PHI. So is a session recording of someone filling in a symptom form. A good agency hands you a data map listing every vendor, what data reaches it, and whether there is a BAA. We wrote up what this adds to a budget in HIPAA compliance costs.
Push notifications deserve their own line. Apple and Google do not sign BAAs for APNs or FCM, so the payload should say "You have a new message" and nothing more. The app fetches the content once the user opens it.
Questions to Ask Before You Sign
Ask these on the first call. A team that has done the work answers them in plain sentences without checking with someone. A team that has not will say "we follow HIPAA best practices" and change the subject.
Who on this team has shipped software with PHI in it?
Ask for names, the product, and what their role was. Then ask for a private reference call with one of those clients. Healthcare clients often cannot be named publicly, but a call is a normal request.
How do you handle audit logging?
The Security Rule requires that you can record and examine activity in systems holding PHI. In practice that means an append-only log of who viewed or changed which record, when, and from where, kept for years and kept out of reach of the app's normal database users. The right answer names a design: a separate audit table or service, write-only from the app, with a retention period. The wrong answer is "we use CloudWatch."
Where is data encrypted, and who holds the keys?
You want TLS 1.2 or later in transit, AES-256 at rest on databases, backups and file storage, and keys managed in AWS KMS, Google Cloud KMS or Azure Key Vault. Ask what is stored on the phone. A good answer is "as little as possible, in the Keychain or Android Keystore, and cleared on logout."
How do access controls work?
Role-based access with the minimum necessary rule built in: a front desk user sees appointments, not lab results. Multi-factor authentication for every clinician and admin. Session timeouts on shared devices. Ask how they test that one patient can never load another patient's record by changing an ID in a request. That bug causes more real breaches than anything exotic.
How do you de-identify data for analytics and testing?
HIPAA allows two methods: Safe Harbor, which strips 18 listed identifiers, and Expert Determination, where a statistician signs off. Ask which one they use for analytics, and confirm that staging and test environments never hold real patient data.
What does your incident response plan look like?
Who gets paged, who decides whether it is a reportable breach, and how fast you hear about it. HIPAA gives covered entities up to 60 days to notify patients after discovering a breach, and your BAA with the clinic will likely require you to tell them much sooner.
For the questions that apply to any agency, like who owns the code and how change orders work, use our checklist on how to vet a software development agency.
EHR Integration Is Its Own Skill
If your app needs to pull a patient's medications, write a note back to the chart, or launch inside the clinician's EHR, the agency needs FHIR experience specifically. FHIR is the HL7 standard most US EHRs now expose, and SMART on FHIR is the OAuth-based layer that lets your app launch from inside the EHR with the right patient and user already in context.
What to ask:
- Have you registered an app on Epic on FHIR? Epic's developer site at fhir.epic.com gives free sandbox access with synthetic patients and issues separate non-production and production client IDs. Someone who has done this can tell you how long each health system took to approve the app.
- Have you worked with Oracle Health (formerly Cerner) or athenahealth? Each one implements FHIR a little differently. Resources that work in one sandbox return different fields, or nothing, in another.
- Patient launch or provider launch? A patient-facing app usually uses standalone launch so patients can connect their own records. A clinician tool usually launches from inside the EHR. They are different builds with different approval paths.
- Write-back? Reading data is the easy part. Writing notes, orders or flowsheet values back into a chart takes more approvals and much more testing.
Budget time for this, not just money. The sandbox can work in a week. Getting a specific health system to turn your app on in production often takes two to six months of security reviews, questionnaires and an IT committee meeting you are not invited to. An agency that promises live Epic integration in your first eight weeks has not done it.
Red Flags in a Healthcare App Proposal
- "HIPAA certified." There is no official HIPAA certification. HHS does not certify vendors. A company saying it has one is either confused or selling.
- No BAA in the contract. If the agency will see or host PHI, it is a business associate and owes you a BAA. If they say they never touch production data, the contract should say that too.
- Firebase or Supabase on the free or entry plan for PHI. Neither qualifies. See the list above.
- Real patient data in staging. Ask how they seed test data. Synthea, the open-source synthetic patient generator, is the usual answer.
- Google Analytics, Meta Pixel or session replay on logged-in screens. HHS warned in its tracking technologies guidance that these can disclose PHI. A federal court struck part of that guidance in 2024, the part about public pages, but logged-in patient screens are still squarely in scope.
- No risk assessment in the plan. A security risk analysis is required under HIPAA. For a first version it can be modest, but it has to be written down.
- A fixed price for "full Epic integration." Nobody controls a health system's approval timeline. Fixed price for the sandbox build is fine. Fixed price for go-live is a guess.
In-House, Specialist Agency, Freelancer or Product Studio
There are four realistic ways to get a HIPAA app built. Here is how they compare on market rates and fit.
| Option | Market rate | Best for | Watch out for |
|---|---|---|---|
| In-house hire | Roughly $160,000 to $230,000 base for a senior full-stack engineer in a major US market, plus equity and benefits. You need two or three to cover mobile, backend and security. | A funded company where the software is the business and work runs for years | Three to five months to hire. Engineers with real PHI experience are scarce and expensive. |
| Healthcare-specialist agency | $150 to $275 an hour blended in the US. First versions often land between $150,000 and $400,000. | Deep EHR write-back, multi-hospital rollouts, or anything heading toward FDA clearance | Long discovery phases and heavy process for a product still looking for its first users |
| Freelancer | $90 to $200 an hour for experienced US engineers. $30 to $70 offshore. | A prototype with synthetic data, or one feature added to an app that already has compliance in place | One person owning security, audit logs and on-call. Many will not sign a BAA or carry cyber insurance. |
| Product studio | $120 to $225 an hour blended. A first version often lands between $80,000 and $250,000. | A founder who needs design, mobile, backend and launch in one team, with standard HIPAA controls and read-only FHIR | Studios without PHI experience. Ask the questions above before you sign. |
Our take: for a first version with HIPAA controls and light EHR reads, a product studio with PHI experience on the team is the sweet spot. You get the people who design the screens and the people who build the backend in the same weekly demo. Go to a healthcare specialist when integration depth is the product, and hire in-house once you have revenue and a roadmap that runs for years.
What a HIPAA App Costs and How Long It Takes
These are market ranges from US and Western European teams for design and development. They include the HIPAA engineering, not the separate compliance program.
- A focused first version, one platform or cross-platform in React Native or Flutter, one user type, secure messaging or booking, audit logging, no EHR integration: roughly $80,000 to $150,000, over three to five months.
- A typical patient plus clinician product with two user types, a web dashboard for staff, video visits through a BAA-covered provider, and read-only FHIR: roughly $150,000 to $300,000, over five to eight months.
- A complex platform with EHR write-back, several health systems, remote monitoring devices or clinical decision support: $300,000 to $600,000 and up, over eight to fourteen months, and production EHR approvals on top.
HIPAA itself usually adds 15 to 30 percent to a comparable non-health build. That covers audit logging, stricter access control, encryption and key management, the paid tiers of vendors that sign BAAs, and more testing. Then there are the running costs: compliance automation tools like Vanta or Drata at roughly $10,000 to $30,000 a year, a penetration test at $8,000 to $30,000, and hosting that is often two to three times a hobby-tier bill because of the plans BAAs require.
For the full build sequence, see how to build a healthcare app. For ranges on apps outside healthcare, our app development cost page breaks down what moves the number.
What drives the spread: user types, a staff dashboard, how many EHRs you connect to, and whether you write back to the chart. A clinic partner with its own security team can save you months of policy writing.
When Hiring an Agency Is the Wrong Call
We are an agency, so take this from someone with a reason to say the opposite. In healthcare, the wrong build is expensive, and sometimes the right answer is to not build at all.
- A white-label platform covers it. If you are a therapy practice or a nutrition clinic that needs booking, video visits, intake forms and billing, platforms like Healthie, SimplePractice or Doxy.me already sign BAAs and cost hundreds a month, not six figures. Healthie also offers APIs and a white-label app if you want your own brand. Build only the part that makes you different.
- You need to be a certified EHR. If your product has to carry ONC Health IT certification so providers can use it for federal reporting programs, you need a team that has taken a product through certification, usually a specialist or your own hires. A general agency will learn on your money.
- Your app is a medical device. Software that diagnoses or treats can fall under FDA rules as software as a medical device. That means a quality management system, design controls and IEC 62304 documentation from day one. Hire a firm that has done FDA submissions, or a regulatory consultant first.
- It is a wellness app with no provider involved. You may not need HIPAA at all. Do not pay a 30 percent premium for controls you are not required to have. Build for the FTC rule and state privacy laws, which is lighter, and design so you can add HIPAA controls later.
- You are a health system with an Epic team. Your own analysts can often build what you need inside MyChart or with Epic's tools faster than an outside team can get production access.
How We Work With Sensitive Records
We have not shipped a healthcare app, and we will not pretend otherwise. We are a product team that designs and builds the whole app, and we treat personal records and what the law allows as design work from the first week.
HouseFax is the closest example. It gives a house a verified record: permits pulled from the county, receipts and warranties filed from a connected inbox, and an AI capture flow that reads a photo of an invoice and files it by system. Before the screens were final, we audited every data claim against what is legally and technically obtainable. Address-level insurance claims are restricted under the FCRA, so that feature became an owner-consent flow. It is in build as a React Native and Expo app on an Express and tRPC backend with MongoDB and Clerk, with 158 phone screens designed, and it has not launched yet.
If you are comparing proposals for a healthcare app, send them over and we will tell you which questions above each one leaves unanswered, even if you hire someone else. Book a free strategy call


