Almost every electronic health record comes with a patient portal: MyChart with Epic, the athenahealth portal, eClinicalWorks' healow, and others. Before commissioning anything, be clear about what yours cannot do. For a single practice on a single EHR with standard needs, the vendor portal is usually the right answer and costs nothing extra to build.
Custom patient portal app development is for the cases where it is not: organisations running more than one clinical system, services the EHR does not model, and digital health companies for whom the portal is the product.
What a patient portal needs to do
- Identity and access. Secure sign-up, identity verification, multi-factor login, and proxy access for parents and carers.
- Appointments. Book, reschedule, cancel, join a video visit, complete check-in and forms beforehand.
- Records. Results, visit summaries, medications, immunisations, documents.
- Messaging. Secure messages with the care team, with routing and response expectations.
- Prescriptions. Refill requests and pharmacy details.
- Billing. Statements, estimates, payments and payment plans.
- Notifications. Reminders by text, email and push, without putting clinical detail in the message.
When the EHR vendor portal is enough
- One organisation, one EHR, mainstream specialties.
- Patients who interact with you a few times a year.
- No need for your own brand or a mobile app beyond what the vendor offers.
When a custom patient portal wins
1. More than one system behind the scenes
A group that has grown by acquisition may run several EHRs plus separate billing, imaging and lab systems. Patients do not want four logins. A custom portal presents one front door and talks to each system behind it.
2. A service model the EHR does not fit
Membership and concierge care, behavioural health programmes, fertility journeys, physiotherapy with home exercise plans, remote monitoring, clinical trials. Each has steps, content and data that a general portal treats as an afterthought.
3. The portal is the product
Telehealth and digital health companies compete on the patient experience. They need to own it, measure it and change it weekly.
4. Engagement the vendor portal cannot drive
Care-plan tasks, education tied to a diagnosis, questionnaires that feed back into the record, family and carer coordination.
Integration: the part that decides the budget
A portal is only as good as its connection to the clinical record. Modern EHRs expose patient data through HL7 FHIR APIs, and in the United States the 21st Century Cures Act requires certified EHRs to offer standardised patient-access APIs. SMART on FHIR is the usual way to authorise an app against them. In practice:
- Reading data (results, medications, appointments) through FHIR is well supported.
- Writing back (booking into the real schedule, filing a message or form into the chart) varies by vendor and often needs their specific APIs or an integration engine.
- Older systems may still need HL7 v2 interfaces.
- Vendor app-programme approval can add weeks to the timeline. Plan for it.
HIPAA and security requirements
- A business associate agreement with the developer, the cloud host and any messaging or video provider.
- Encryption in transit and at rest, with keys managed properly.
- Role-based access, session timeouts and multi-factor authentication.
- Audit logs of every access to patient data.
- Proxy access rules, including the sensitive handling of adolescent records.
- Accessibility to WCAG standards. Patients include people with every kind of impairment.
What patient portal development costs
| Build | What it includes | Typical range |
|---|---|---|
| Core web portal | Login, appointments, records view, messaging | $50k-$110k |
| Portal with mobile apps | iOS and Android, push notifications, check-in | $90k-$180k |
| EHR integration | FHIR read, scheduling and messaging write-back | $20k-$70k per system |
| Telehealth and payments | Video visits, statements, payment plans | $30k-$80k |
| Multi-system patient platform | One portal over several EHRs and billing systems | $200k-$450k+ |
The spread within each range is mostly integration depth. A read-only portal over one modern EHR sits at the low end; two-way scheduling across several systems sits at the high end.
The build-vs-buy test
- List what patients ask for that your current portal cannot do. If the list is short, configure what you have.
- Count the systems a patient touches. More than one is the strongest argument for custom.
- Check your EHR's API programme before you budget. It sets what is possible.
- Decide whether the portal is a utility or a differentiator. Only differentiators justify owning it.
See what we build on the healthcare software page, including the patient portal, telemedicine platform and medical billing software. For the wider argument, read the workflows off-the-shelf EHRs cannot handle and what a custom mobile app costs, or price your scope with the cost calculator.
Frequently asked questions
What is patient portal app development?
Designing and building a secure web or mobile application that lets patients book appointments, see results and records, message their care team, request refills and pay bills. It includes integration with the electronic health record and the security controls HIPAA requires.
How much does it cost to develop a patient portal?
A core web portal typically costs $50k to $110k, and a portal with iOS and Android apps $90k to $180k. EHR integration adds roughly $20k to $70k per system. A platform that unifies several EHRs and billing systems is usually $200k to $450k or more.
Does a patient portal have to be HIPAA compliant?
Yes, in the United States, because it stores and transmits protected health information. That means business associate agreements with every vendor involved, encryption, access controls, multi-factor authentication and audit logging of access to patient data.
Can a custom patient portal integrate with Epic or other EHRs?
Yes. Most modern EHRs expose patient data through HL7 FHIR APIs, usually authorised with SMART on FHIR. Reading data is well supported; writing back appointments, messages or forms depends on the vendor and may need their specific APIs and app-programme approval.
Should we build a custom portal or use our EHR vendor portal?
Use the vendor portal if you run one EHR and have standard needs. Build custom when patients would otherwise face several logins across systems, when your service model does not fit the vendor portal, or when the patient experience is the product you compete on.