EHR With a Patient Portal vs a Separate Portal: Which Do You Need?

Most certified EHRs come with a patient portal, and for many practices it is enough. A separate portal earns its cost when patients span several EHRs, when the workflows go beyond the chart, or when the organization is not a provider. Here is how to tell which case you are in.

In short

  • An EHR with a built-in patient portal is the default for most providers, because ONC certification requires that patients can view, download and transmit their health information, filter it by date and see a history of those actions.
  • A separate portal makes sense when patients deal with several EHRs or organizations, when the portal must run workflows the EHR portal does not, such as claims, referrals or care networks, or when the organization is a payer or administrator rather than a provider.
  • A separate portal reads clinical data from the EHR through the same certified FHIR APIs that third-party apps use, so plan the integration and the division of work between the two portals from the start.

If you run one EHR and your patients mostly need results, messages, appointments and bills, the portal that comes with your EHR is usually the right choice. ONC certification already requires it to let patients view, download and transmit their records. A separate portal is worth building when patients deal with several EHRs or organizations, when the portal has to run workflows the EHR portal cannot, or when your organization is a payer, administrator or care network rather than a single provider. In those cases the separate portal pulls clinical data from the EHR through standard FHIR APIs.

This comparison is for practice and health system leaders, and for digital health and payer teams, deciding whether to rely on an EHR's patient portal or put one of their own in front of patients.

What does an EHR's built-in portal have to do?

EHRs certified under ONC's §170.315(e)(1) criterion must let patients and their authorized representatives use internet-based technology to view, download and transmit their health information to a third party. The certification test method spells out what that means:

  • View: at minimum the USCDI data, assessment and plan of treatment, goals, health concerns, lab and diagnostic imaging reports, and in ambulatory care the provider's name and office contact information.
  • Download: an ambulatory or inpatient summary in human-readable form and in the C-CDA CCD format.
  • Transmit: send that summary by email to any address and by an encrypted method of electronic transmission.
  • Date filtering: choose data for a specific date or a date range.
  • Activity history: a record of each view, download and transmit, with date, time, user and, for transmits, the addressee, available to the patient.
  • Restriction requests: an internet-based way for patients to ask for restrictions on their data, with a compliance date of January 1, 2026 in the regulation.
  • Accessibility: WCAG 2.0 Level A at minimum, with Level AA allowed instead.

That is a solid floor. If your patients need exactly this, plus the scheduling, messaging and billing features most EHR portals add, a separate portal will cost you money without changing much for them.

What can a separate portal get from the EHR?

A separate portal does not need private access to the EHR. EHRs certified under §170.315(g)(10) must offer a standardized FHIR API with SMART App Launch for authorization and US Core profiles for the data, based on USCDI v3 and US Core 6.1.0, with newer versions approved through ONC's Standards Version Advancement Process. That gives a separate portal a predictable read path for the patient's record.

Each EHR vendor adds its own patterns on top. Epic's documentation, for example, describes patients launching a third-party portal from inside MyChart through an embedded EHR launch. For writing patient-reported readings back with its Observation.Create API, Epic says patients must have active MyChart accounts and that Epic customers are responsible for provisioning them. So even a separate portal often works alongside the EHR's portal and does not replace it.

How do the two options compare?

EHR patient portal and separate portal compared
QuestionEHR's portalSeparate portal
DataEverything in that EHR, no integration workWhat the EHR APIs expose, plus other systems
LoginOne per EHR organizationOne across all organizations behind it
WorkflowsThe vendor's standard setWhatever you design, including non-clinical
Brand and experienceLimited configurationFully yours
RoadmapThe vendor's release scheduleYours, with the cost of running it
ComplianceCertification covers view, download, transmitYou carry it for everything you build
  • Data. EHR portal: everything in that EHR, with no integration work. Separate portal: whatever the EHR APIs expose and the health system enables, plus data from other systems.
  • Login. EHR portal: one login per EHR organization. Separate portal: one login across all the organizations and systems behind it.
  • Workflows. EHR portal: the vendor's standard set. Separate portal: whatever you design, including non-clinical work.
  • Brand and experience. EHR portal: limited configuration. Separate portal: fully yours.
  • Roadmap. EHR portal: the vendor's release schedule. Separate portal: yours, along with the cost of running it.
  • Compliance. EHR portal: certification covers the view, download and transmit features. Separate portal: you carry accessibility, security and HIPAA obligations for everything you build.

When is the EHR's portal enough?

  • Your organization runs one EHR, and most patients see only you.
  • Patient needs are records, results, messages, appointments, refills and bills.
  • You have no product or engineering team to own a portal for years.
  • Your main problem is getting patients to use the portal you already have. Federal data shows that among people offered access in 2024, 87% of those encouraged by a provider used their portal, compared with 57% of those who were not encouraged. A better invite may help more than a new portal.

When do you need a separate portal?

Three situations come up again and again.

Patients cross several EHRs or organizations

In 2024, 59% of individuals had more than one online medical record or portal. People with more than one got them from primary care offices (68%), other providers (40%), insurers (30%), clinical labs (29%), pharmacies (24%) and hospitals (22%). If your service sits across several of these, for example a specialty network, a virtual care company or a care management program, a portal tied to one EHR leaves patients juggling logins.

The workflow is not in the chart

Some portals exist for work the EHR portal was never designed for. We built a self-service portal for a US third-party administrator offering 70+ bundled payments at 120+ outpatient surgery centers. Providers submit, track and manage referrals, claims and payments, and the system checks each claim and referral against defined parameters and enters it into the client's EHR, with a dashboard for the claims team to review questionable cases. The portal also integrates with the client's Salesforce organization. Claims and referrals are now processed three times faster, and inbound phone calls and emails dropped by 95%.

The users include a care network around the patient

Caregivers are a large group of users now. In 2024, 51% of individuals accessed the record of someone they care for or make decisions for, up from 24% in 2020. When families, helpers and care teams need different roles and permissions, a purpose-built portal is often the cleaner answer. Our white-label home care platform for a digital health company in Australia has five user roles, from the network owner to the wider helper network, with chat, a calendar with tasks and risk assessments that trigger education and guidance.

Can you run both?

Yes, and with a provider organization you often will, since the EHR portal does not go away. Decide which portal owns which job, so patients are not sent to two places for the same thing:

  • Pick one place for messages with the care team. Two inboxes means missed messages.
  • Decide where results are released first, and link to the other portal instead of copying the experience.
  • Keep the EHR as the source of truth for clinical data, and write back only through supported APIs.
  • If the EHR supports it, launch your portal from inside the EHR portal, or the reverse, so patients move between them without signing in twice.
  • Measure both. Track which tasks patients complete in each portal before you add or remove features.

What obligations come with a separate portal?

Building your own portal does not change the covered entity's duties. Patients keep their HIPAA right of access: the covered entity must act on a request within 30 days, with one extension of up to 30 more, and provide records in the form and format requested if readily producible. Recipients of federal financial assistance must make their web content and mobile apps conform to WCAG 2.1 Level A and AA, from May 11, 2027 for those with 15 or more employees and May 10, 2028 for smaller ones. If your company handles PHI for a covered entity, you also need a business associate agreement.

We sign a BAA before anyone on our team sees PHI, each clinician sees only their own patients, and we run a penetration test before launch. We have shipped Epic and athenahealth integrations, and for any other vendor platform we work from the vendor's documentation and sandbox. If you are weighing your EHR's portal against one of your own, talk to one of our engineers. Our free five-day technical audit ends with a written report on what your EHR's APIs allow and what a separate portal would add.