In short
- An EMR-agnostic patient portal owns the patient account, permissions and user experience, and reads and writes clinical data through a separate adapter for each EHR.
- ONC certification requires certified EHRs to offer a standardized FHIR API built on US Core and SMART App Launch, which makes read access across vendors practical.
- Scheduling, messaging, forms and payments still differ by vendor, so plan per-EHR write paths, careful patient matching and clear data provenance from the start.
An EMR-agnostic patient portal is a portal that does not belong to any one EHR. It keeps its own patient accounts, permissions and design, and it reaches each EHR behind it through a separate adapter. Certified EHRs in the US must offer a standardized FHIR API based on US Core and SMART App Launch, so reading a patient's results, medications, problems and notes across vendors is now a well-defined job. Writing back, booking appointments, messaging and payments are not standardized in the same way, so those parts need per-vendor work. The design goal is that adding a new EHR means adding an adapter while the rest of the portal stays as it is.
Why would one portal need to sit on top of many EHRs?
Patients already juggle portals. ASTP/ONC Data Brief No. 77 reports that 59% of individuals had more than one online medical record or portal in 2024, up from 50% in 2022. They got them from primary care offices, other providers, insurers, labs, pharmacies and hospitals. Only 7% used an app that pulls several portals together.
On the provider side, the same situation appears when an organization runs more than one EHR: a medical group that grew through acquisitions, a management services organization that supports independent practices, a specialty network whose members chose their own systems, or a digital health company that serves patients of many health systems. Each EHR ships its own portal. An EMR-agnostic portal gives those patients one login and one brand.
What do certified EHR APIs guarantee?
The ONC certification criterion §170.315(g)(10), the standardized API for patient and population services, is what makes a vendor-neutral portal realistic. A certified Health IT Module must respond to single-patient requests for all data elements marked mandatory and must support in the adopted standards. The test method lists these standards:
- FHIR Release 4.0.1.
- USCDI v3, with USCDI v5 approved as an advanced version through the Standards Version Advancement Process.
- US Core Implementation Guide STU 6.1.0, with STU 7.0.0 and STU 8.0.1 approved as advanced versions.
- SMART App Launch 2.0.0, with 2.2.0 approved as an advanced version.
- Bulk Data STU 1 for multiple-patient export, with STU 2 approved as an advanced version.
- OpenID Connect Core 1.0.
The criterion also sets behavior a portal can rely on. Connections must use TLS 1.2 or above. On first connection, the server must issue a refresh token valid for no less than three months to confidential apps and to native apps that can secure one. Patients must be able to decline offline access. And the authorization server must revoke an app's access at the patient's direction within one hour of the request.
The API Conditions of Certification at 45 CFR 170.404 add transparency rules. Developers must publish complete business and technical documentation through a public link with no preconditions, and publish all terms, including fees. By December 31, 2024, they had to publish service base URLs for every module certified to (g)(10), at no charge, as FHIR Endpoint resources with Organization details that include name, location and facility identifier. When an app registers, the developer must complete authenticity verification within ten business days and enable the app for production within five business days after verification.
What do the standard APIs leave out?
US Core defines the minimum constraints on FHIR resources and the minimum RESTful interactions for accessing patient data. It was built for reading. A patient portal does much more than read, and those features depend on each vendor's own APIs and program terms:
- Appointment search, booking, rescheduling and cancellation.
- Secure messaging threads between patients and care teams.
- Intake forms and questionnaires written back to the chart.
- Medication refill requests.
- Statements, balances and payments.
- Proxy relationships and caregiver accounts.
For each of these, we work from the vendor's documentation and sandbox, and we plan the integration per EHR. We have shipped Epic and athenahealth integrations. Expect each vendor to differ in what is exposed, in what is behind a developer program or a fee, and in how the customer health system has configured its instance.
How should an EMR-agnostic portal be structured?
Think of the portal as four layers, each with its own job.
- Accounts and identity: the portal's own patient accounts, sign-in, proxy relationships and consent records. This layer never depends on a particular EHR.
- Patient linking: a record of which patient ID in which EHR belongs to which portal account, with how and when each link was made.
- A canonical data model: the portal's internal shape for results, medications, problems, allergies, appointments and documents. Basing it on US Core keeps the mapping thin for FHIR sources.
- EHR adapters: one per vendor, or per vendor version, that translate between the canonical model and that EHR's APIs, handle its authorization, rate limits and errors, and declare which features it supports.
Store feature support as data in each adapter instead of branching in code. If one EHR supports online booking and another does not, the adapter says so, and the portal shows a call-to-book option for patients of the second one.
How do you link one patient across several EHRs?
There are two ways, and the safer one should come first. In the patient-authorized path, the patient signs in once to each organization's SMART authorization server from inside the portal. SMART lets the server share launch context, such as the selected patient, with the app, so the link is made by the patient's own login rather than by a guess. In the matching path, the portal matches demographics against an EHR patient search on behalf of the organization. Matching is useful for staff-initiated enrollment, but it can link the wrong person. Use strict rules, require a second identifier, and send uncertain matches to a staff review queue rather than linking them automatically.
Which data should you store, and which should you fetch live?
Fetching everything live keeps data fresh but makes the portal as slow and as available as the slowest EHR. Storing everything makes the portal a second medical record that you must keep in sync. Most portals land in between: cache what patients look at often, such as recent results and upcoming appointments, with a clear refresh rule, and fetch older history on demand. Always show where each item came from and when it was last updated, so a patient with records in two systems can tell them apart.
How does a patient connect a new organization?
SMART App Launch defines a discovery document at .well-known/smart-configuration relative to each FHIR server base URL, which tells the portal where to send the patient for authorization and which features the server supports. Version 2.2.0 also defines User-Access Brands, a format providers can use to publish branding information for patient-facing apps. Combined with the published service base URLs, that lets a portal show a searchable list of organizations with recognizable names and logos instead of asking patients to pick a server URL.
Scopes limit what the portal may do. Request only the resource types each feature needs. If the portal only shows results and medications, it should not ask for everything the server offers, and the consent screen the patient sees will be shorter for it.
Where do EMR-agnostic portals usually break?
- Duplicate data. The same medication or allergy appears in two EHRs with different names. Group items carefully and never merge clinical data silently.
- Uneven content. One EHR returns clinical notes as structured text, another as attached documents, a third not at all. Design screens that degrade gracefully.
- Expired authorization. A refresh token valid for three months still expires. Tell the patient before a connection lapses and make reconnecting one tap.
- Declined offline access. A patient who declines offline access will need to sign in to that organization again for each session. Explain the choice plainly.
- Vendor upgrades. New versions of US Core and SMART arrive over time. Keep adapters versioned and run contract tests against each vendor's sandbox on a schedule.
- Rate limits and outages. One slow EHR must not block the whole portal. Load each source independently and show partial results.
What about the staff side of the portal?
Most portals also have a staff view for messages, forms and requests. Its access rules must be as strict as the EHR's. In the systems we build, each clinician sees only their own patients, which keeps the staff view in line with how care teams are organized and limits exposure when an account is compromised.
What should you test before launch?
- Every adapter against the vendor sandbox, with test patients that have long histories, missing data and unusual characters in names.
- Linking and unlinking an organization, including revocation from the EHR side and the one-hour revocation requirement.
- A patient with records in two EHRs, to see how duplicates and provenance look on screen.
- Behavior when one EHR is down or slow.
- Proxy access across organizations, which is easy to get wrong when each EHR models proxies differently.
We sign a BAA before anyone on the team sees PHI, and we run a penetration test before launch.
Planning a portal across several EHRs?
Talk to an engineer at Onix Health about the EHRs behind your portal and the features patients need. Our free five-day technical audit ends with a written report on what each EHR exposes, where adapters are needed and what to build first.
Sources
- ASTP/ONC: §170.315(g)(10) standardized API for patient and population services, test method
- 45 CFR 170.404: API Conditions and Maintenance of Certification (Cornell LII)
- HL7: US Core Implementation Guide
- HL7: SMART App Launch Implementation Guide
- ASTP/ONC Data Brief No. 77: individuals' access and use of patient portals and smartphone health apps, 2024