Patient Portal Software: Per-Seat Cost vs. Custom Build

Patient portal functionality — appointment requests, secure messaging, records access, intake forms — is commonly bundled into EHR and practice-management platforms as a module priced per provider, per active patient, or per portal login. As a practice grows its patient base, the exact metric the portal is meant to encourage (more patients engaging self-service) is the one driving the bill up.

Where the per-seat model breaks down for patient-facing tools

• Provider-based pricing penalizes practices for adding clinicians, even when the portal’s actual usage is driven by patient volume, not provider count.
• Active-patient pricing ties cost directly to portal adoption succeeding — the same misaligned incentive seen in other client-facing licensing models.
• Feature bundling often forces a practice into a higher EHR tier just to unlock portal features it needs, even if the rest of that tier goes unused.

What a purpose-built patient portal covers

	EHR-native patient portal module	Third-party patient engagement tool	Custom-built portal
Pricing	Per provider or per active patient	Separate subscription, its own tier	One flat monthly fee
Cost as patient volume grows	Rises	Rises	Unchanged
Integration depth	Native to the EHR	Add-on sync, sometimes delayed	Built to sync with your specific EHR/PM system

A custom patient portal synced to the practice’s existing EHR or practice-management system delivers appointment requests, secure messaging, and records access on a flat monthly fee — the practice’s EHR stays the clinical system of record.

Compliance and access control still come first

Nothing about moving to a flat-fee model changes the access-control and data-handling standards a patient-facing tool has to meet. A custom build is scoped to the same standard the practice already applies to protected health information, not a generic vendor default — this is a design requirement from day one of the build, not an afterthought.

Compare the broader build-vs-license tradeoff at custom software vs. SaaS: total cost compared. The client-facing pattern here parallels what’s covered for a different regulated industry in a client portal for insurance without per-seat fees.

Frequently asked questions

Does a custom patient portal replace our EHR?

No — it’s a patient-facing front end synced to your existing EHR or practice-management system through its API. Clinical documentation and records stay exactly where they are.

Can it handle appointment scheduling across multiple providers or locations?

Yes, when scoped to your specific scheduling rules and provider/location structure during the build — that’s a requirements decision, not a limitation of the flat-fee model.

Why not just use the EHR’s built-in portal and eat the cost?

For some practices that’s the right call, especially at low patient volume. The math shifts as patient volume or provider count grows — that’s the comparison worth running before renewal, not after.