Hybrid Patient Portal Solutions: Web, a Mobile App, or Both?

A hybrid patient portal serves the same accounts, data and permissions through a web app and mobile apps. The work is deciding which tasks go to each channel, meeting app store, NIST and accessibility rules on both, and knowing when web alone is enough.

In short

  • A hybrid patient portal is one product with one backend, one identity system and one permission model, delivered through both a web app and mobile apps.
  • Federal survey data shows that in 2024, 57% of people who accessed their records online used an app and 42% used only the web, so most patient groups need both channels.
  • Put first contact, long forms and proxy setup on the web, put frequent tasks and notifications in the app, and hold both to the same authentication and WCAG 2.1 AA accessibility rules.

A hybrid patient portal is one product delivered through two front ends: a web app that works in any browser and mobile apps for iOS and Android. Both share one backend, one patient account, one set of permissions and one copy of the data. For most providers this is the right answer to the web-or-app question, because patients use both. In 2024, 57% of people who accessed their records online used an app and 42% used only the web, according to ASTP/ONC. What remains to decide is which tasks go where, and how to keep the two channels from drifting apart.

What does "hybrid" mean for a patient portal?

The word gets used for three different things, and it helps to separate them before anyone writes an estimate.

  • Hybrid delivery: a web portal and mobile apps that sit on the same backend. This is the meaning used here.
  • Hybrid code: one cross-platform codebase, such as React Native or Flutter, that produces both the iOS and Android apps. It is a build choice inside the mobile channel.
  • A wrapped website: the web portal placed inside a thin native shell and published to the app stores. It looks like a shortcut, but it often fails app review and adds little to what the web portal already does.

A sound hybrid portal usually combines the first two: a responsive web app, plus cross-platform mobile apps, both calling the same API.

How do patients split their time between web and app?

ASTP/ONC Data Brief No. 77 tracks how people reach their online records. Among those who accessed records at least once in the past year, app use rose from 38% in 2020 to 51% in 2022 and 57% in 2024. Web-only access fell from 60% to 48% to 42% over the same years. The brief counts people who use both an app and the web as app users, so the web is still part of the routine for many of them.

The same brief shows that 59% of people had more than one online record or portal in 2024, from primary care offices, other providers, insurers, labs, pharmacies and hospitals. Your portal competes with several others for space on the phone and for a password the patient remembers. That is a strong argument for making the first visit work on the web, with no install required, and earning the app install later.

Which tasks belong on the web, and which in the app?

Split the work by patient task. Each task has a natural channel, and the other channel should still handle it, only with less polish.

  • Web first: account activation from a text or email link, long intake and pre-visit forms, bill review and payment, downloading records, setting up proxy access for a family member, and anything a caregiver does from a work computer.
  • App first: results notifications, appointment reminders and check-in, secure messages, medication refill requests, daily symptom or device readings, and anything the patient does several times a week.
  • Both, equally: viewing results and notes, booking and moving appointments, and reading care instructions.

If you can only fund one channel at launch, look at how often your patients need you. A practice that sees patients once or twice a year can start web-first. A remote monitoring program, a chronic care service or a care team that messages families daily needs the app from day one.

When is a web-only portal enough?

A well-built responsive web app covers episodic care: a single procedure, a specialist referral, a lab visit, a bill. It needs no app store review, ships updates instantly to every user and works on any device.

Installable web apps narrow the gap further. Since iOS and iPadOS 16.4, a web app that the user has added to the Home Screen can ask for permission to send push notifications, as long as the request responds to a direct user action such as tapping a subscribe button. Those Home Screen web apps also support the Badging API. The catch is the extra step: the patient has to add the app to the Home Screen first, and many will not.

When do you need native or cross-platform apps?

  • Patients use the portal weekly or daily, for monitoring, care plans, or coordination with family.
  • You need reliable push notifications without asking patients to install a web app by hand.
  • You connect to Bluetooth devices such as blood pressure cuffs or scales, or to the phone's health data.
  • You want biometric unlock on the device so patients do not type a password for every check.
  • Field staff or caregivers need the app to keep working with a weak connection.

Apple's App Store Review Guidelines shape what the app must be. Under guideline 4.2, an app should include features, content and UI that elevate it beyond a repackaged website, which is why a wrapped web portal is risky. Medical apps that could provide inaccurate data or be used for diagnosing or treating patients may be reviewed with greater scrutiny. Apps that support account creation must also offer account deletion within the app. And under guideline 5.1.3, apps may not store personal health information in iCloud, and data from HealthKit or the Clinical Health Records API may not be used for advertising or marketing.

How do you keep one backend behind both channels?

Most hybrid portals that go wrong do so because the web and the app become two products. The backend design prevents that.

  • One API for both clients. Business rules, such as who may see a result or when a slot can be booked, live on the server, never in client code.
  • One identity provider and one session model, so a patient who changes a password or revokes a proxy on the web is signed out of the app too.
  • One permission model for patients, proxies and staff, checked on every request.
  • Shared content and copy, served from the backend, so instructions and consent text match on both channels.
  • Feature flags per channel, so a feature can launch on the web while the app release waits for store review.
  • A minimum supported app version. Old app builds stay on phones for months, so the API must reject versions it no longer supports and prompt an update.
  • Notifications that say a new message or result is waiting, with the content behind sign-in, so nothing clinical shows on a lock screen.

What should authentication look like on each channel?

NIST SP 800-63B-4 is the federal reference for authentication strength. At authentication assurance level 2 (AAL2), it requires two distinct authentication factors and says verifiers shall offer at least one phishing-resistant authentication option. It recommends that the overall reauthentication timeout be no more than 24 hours and the inactivity timeout no more than 1 hour at AAL2. Passwords used as a single factor need at least 15 characters, and passwords used only as part of multi-factor authentication need at least 8. Use of the phone network for one-time codes is restricted, and email is not allowed as an out-of-band authenticator.

In practice that means the same account policy on both channels, with different convenience layers. On the web, offer a phishing-resistant option such as a platform authenticator. In the app, let the patient unlock a stored session with the device biometric, within the timeouts you set on the server.

What accessibility rules apply to web and app?

Both channels fall under the same accessibility rule if your organization receives federal financial assistance from HHS. The Section 504 rule at 45 CFR part 84, subpart I, covers web content and mobile applications and adopts WCAG 2.1 Level AA as the technical standard. An interim final rule, effective May 7, 2026, moved the compliance dates: recipients with 15 or more employees now have until May 11, 2027, and recipients with fewer than 15 employees until May 10, 2028.

Plan accessibility work for the apps as well as the website. Screen reader labels, dynamic text size, color contrast and focus order have to be tested on iOS and Android as well as in browsers, and on every release.

How do the running costs compare?

A web-only portal has one release pipeline and one test matrix. Adding apps adds two store listings, store review on every release, yearly OS updates to absorb, device testing and the support burden of old versions in the field. A cross-platform codebase removes most of the duplicate client code, but not the store work or the device testing. Count that ongoing work in the decision so it does not surprise you in year two.

How do you decide?

  • List the ten tasks patients and caregivers do most often, and how often each happens.
  • Mark which tasks need push, devices, biometrics or offline use. Those point to the app.
  • Mark which tasks happen at first contact or at a desk. Those must work on the web.
  • Check who your users are. Caregivers, older patients and people with several portals often start on the web.
  • Decide the backend rules once, then build the channels on top. Launch both if the task list calls for it, or web first with the app as a planned second release.

What does a hybrid build look like in practice?

Our home-based care platform for a digital health company in Australia combines both channels. We built the mobile apps in React Native for iOS and Android, plus a web dashboard for organization-level administration. It supports five user roles with different access, chat with attachments, a calendar with tasks, and risk-assessment flows that trigger education and interventions based on patient answers. Six white-label apps are live on that foundation, and the partnership has run since 2017.

Whatever the channel mix, security work comes first. We sign a BAA before anyone on the team sees PHI, and we run a penetration test before launch.

Deciding between web, app or both?

Talk to an engineer at Onix Health about your patients' tasks and your current portal. Our free five-day technical audit ends with a written report on the channel split, the backend changes and the order to build them in.