Top patient portal development companies (August 2026 Edition)

Buyer's GuideAug 21, 2026 · 14 min read

Short answer

Choosing patient portal software comes down to HIPAA compliance, clean EHR integration over HL7 FHIR, secure patient messaging, and reliable identity - bought off-the-shelf or built custom. RaftLabs meets the custom-build bar with HIPAA-compliant healthcare software shipped since 2015, a 4.9/5 Clutch rating, and fixed-price engagements at $29-$49/hr.

Key Takeaways

  • The first decision is not the vendor, it is the model: buy a portal bundled with your EHR, license an EHR-agnostic portal, or build a custom one. Getting that wrong costs more than picking the wrong company.
  • Most patient portal builds fail on integration and identity, not features. The EHR connection over HL7 FHIR and the way you match a login to the right patient record belong in the first sprint, not the last two weeks.
  • HIPAA compliance is an architecture decision, not a checkbox added near launch. Access rules, audit logging, and encryption have to be designed into the data model that holds protected health information.
  • A portal only delivers value if patients use it. Provider encouragement and a clean mobile experience drive adoption far more than the length of the feature list.
  • Ask every shortlisted company to walk one real patient-access boundary live - log in as a patient, then as a provider, and confirm each sees only what they should.

Every patient portal starts with a feature list and fails somewhere else. The demo looks fine: a patient logs in, sees a lab result, books an appointment, sends a message. Then the portal has to talk to the EHR, and the read is fine but the write-back drops a booking on the floor. Or two family members share an email and the portal shows one person the other's diagnosis, because patient identity was treated as a login problem rather than a safety problem. Or the security review asks how protected health information is logged and the answer is a shrug. Patient portal software lives and dies on the parts a buyer cannot see in a demo: how it connects to the systems that already hold the record, how it proves a login belongs to the right patient, and how confidentiality is built into the data model. The companies on this list have shipped healthcare software where those decisions were made in the first sprint, not discovered in production.

This category is hard to buy well because the market mixes two different things under one search. Some names below are portal products you license and configure, often bundled with an EHR. Others are software companies that build a custom portal for you. Both are valid, and the most expensive mistake is choosing the wrong shape before you choose the vendor. So we vetted each option on the things that actually matter in health software: real HIPAA-compliant track record, EHR integration depth over HL7 FHIR, patient identity and access discipline, pricing honesty, and fit with the kind of buyer reading this. The wrong-fit option is more expensive than the more expensive option.

The eight patient portal software options on this list are Epic, RaftLabs, Oracle Health, athenahealth, Bridge Patient Portal, Empeek, Klara, and TechMagic. RaftLabs is on this list. We wrote our own entry with the same directness we applied to everyone else.

In 2024, 77% of individuals were offered online access to their health records and 65% accessed them at least once - ONC, 2024

How we evaluated this list

A buyer's guide is only as honest as its criteria, so here are ours before the companies. We did not rank on brand or rating alone. A big EHR logo tells you a portal is widely deployed, not that it fits a practice that runs a different record system. A high directory score tells you clients were happy, not that a firm has shipped software that handles protected health information correctly. We weighted evidence of real HIPAA-compliant healthcare software, integration depth in the systems a portal depends on, discipline around patient identity and access, transparency on how work is priced, and fit with the reader's profile. Where a rating could not be verified against a live profile during sourcing, we say so and hedge rather than repeat a number we could not confirm.

We evaluated each option on five criteria:

CriterionWhat we looked for
Shipped healthcare softwareA live product handling protected health information, not a generic portal template
EHR integration depthEvidence of clean HL7 FHIR and HL7 v2 interfaces, ideally with discrete write-back
Identity and access disciplinePatient identity verification, role-based access, and audit logging built into the architecture
Pricing transparencyA published rate band, a clear license model, or an honest quoting process
Buyer fitA track record with buyers who match the reader -- practices, health systems, and digital-health teams

No company paid for placement on this list.


1. Epic

Epic is the largest EHR vendor in United States acute care, and its patient portal, MyChart, is the portal most American patients have already used. By ONC and market-tracker estimates, Epic held roughly 42% of the acute-care hospital market in 2024, which means MyChart is the default patient experience across a large share of the country's hospital beds. For a health system already running Epic, MyChart is not really a separate decision. It comes with the record system.

What MyChart does well is breadth inside the Epic world. Patients view results, medications, immunizations, and clinical notes, schedule and check in for appointments, request refills, message their care team, and join telehealth visits. A feature called account linking lets a patient pull several MyChart-connected organizations into one view. Because the portal and the record share one data model, the read-and-write behavior that trips up third-party portals is largely a solved problem here.

The reason Epic is the entry to read carefully against your own situation is the same thing that makes it strong. MyChart is excellent if your future is Epic, and close to irrelevant if it is not. It is not sold as a standalone portal to a practice running a different EHR, and it does not bend to a workflow or brand that Epic does not already model. For a large organization standardizing on Epic, that depth is hard to match. For a multi-specialty group on mixed systems, or a digital-health company where the portal is the product, this is the wrong shape of option.

Notable work -- Epic is deployed across a large share of United States hospitals and academic medical centers, and MyChart has been widely recognized in patient-engagement coverage. Specific client outcomes vary by organization, so evaluate MyChart against your own EHR footprint and ask peer Epic sites about their real adoption numbers rather than relying on the brand.

Pricing signal -- Pricing is not publicly listed and is enterprise-scale, tied to an Epic EHR contract rather than a standalone portal license. Expect health-system economics, and confirm total cost through your Epic agreement.

What to watch -- MyChart is the right choice almost only if you are on Epic or moving to it. A practice on another EHR, or a team that needs a custom patient experience across several record systems, will not get there with MyChart and should look at an EHR-agnostic portal or a custom build.

  • Best for: Hospitals and health systems already standardized on the Epic EHR that want the bundled patient portal.

  • Specialization: EHR-integrated patient portal, records access, scheduling, secure messaging, telehealth

  • Pricing: Not publicly listed; enterprise, tied to an Epic contract

  • Clutch: Not a dev-shop listing -- evaluate via peer Epic references and KLAS


2. RaftLabs

RaftLabs is an AI-first tech studio that has built custom software for established businesses since 2015, with real healthcare work spanning remote patient monitoring and telehealth. Its custom patient portal software work centers on the parts of a health product that decide whether it survives contact with real patients and real regulators: HIPAA-compliant architecture, EHR integration over HL7 FHIR, patient identity and role-based access, audit logging, and secure messaging. Engagements start with a scoped discovery sprint that fixes the integration list and the identity model before a line of product code gets written.

The reason that order matters is specific to health software. The EHR connection and patient identity are where late-stage rework hides, so RaftLabs treats them as the first architectural decisions rather than settings added near launch. Confidentiality, audit trails, and access rules are designed into the data model, not layered on after the first patient sees data that was not theirs.

In practice the discovery sprint produces two artifacts before design starts: an integration map that lists every system the portal must exchange data with, in which direction, and over which standard, and an access matrix that says exactly which role can read and write each field. Those two documents are where most of the real cost lives, and pinning them down early is what lets a fixed price hold. It is also what makes the difference on the day the system meets a real edge case -- a caregiver who needs proxy access to a dependent's record, a lab result that must post within a defined window, a patient who shares an email with a family member. RaftLabs runs discovery precisely so those cases are named while they are cheap to handle, in the data model, rather than discovered after launch when they mean a migration of protected health information.

Notable work -- RaftLabs has shipped HIPAA-compliant remote patient monitoring and telehealth software for United States healthcare clients, including work that integrates video visits, e-signatures, and device data on HIPAA-eligible cloud infrastructure. It has also delivered at enterprise scale for clients such as Vodafone and T-Mobile, evidence of building with the security and reliability regulated data demands. It has not published a standalone patient-portal case study on this list, so ask to see relevant HIPAA, EHR-integration, and access-control work directly during scoping.

Pricing signal -- $29-$49/hr with fixed-price engagements and milestone payments, scoped after the discovery sprint that defines the integration list and identity model. Fixed-price suits buyers who want a known number before EHR and compliance complexity is priced in.

What to watch -- RaftLabs owns the full delivery stack -- discovery, architecture, engineering, and delivery -- which fits organizations that want one team accountable end to end for a custom portal. An organization that has decided to standardize on a bundled EHR portal and only needs configuration, or one that wants to license an existing product and go live in weeks, is better served by a portal product or a configuration partner than by a custom build.

  • Best for: Health systems, practices, and digital-health teams building a custom HIPAA-compliant patient portal end-to-end.

  • Specialization: HIPAA-compliant architecture, EHR integration over HL7 FHIR, patient identity and access, secure messaging, telehealth

  • Pricing: $29-$49/hr, fixed-price engagements

  • Clutch: 4.9/5


3. Oracle Health

Oracle Health, the former Cerner, is the second-largest EHR vendor in United States acute care, and its patient portal, HealtheLife, is the bundled patient experience for organizations on the Oracle Health record system. Like MyChart, it is less a standalone purchase than a component of the EHR decision, so the buyers who should read this entry are the ones already on Oracle Health or weighing a move to it.

HealtheLife covers the expected ground. Patients view, download, and transmit their records, including results, radiology reports, discharge summaries, and clinical notes, with lab results often posted within a day of being finalized. They message their care team over a HIPAA-compliant channel, manage appointments, and request refills. Oracle has publicly rebuilt the portal around AI-assisted features, including plain-language explanations of results and AI-assisted scheduling, which is a real shift for a health-system-scale portal.

Oracle Health earns its place because a serious portal shortlist has to include the large EHR-bundled options, and because the depth an EHR vendor brings to its own portal is genuinely hard to replicate. The portal and the record share a data model, so the read-and-write consistency third-party portals fight for comes closer to free here. The honest caveat is the mirror image of that strength. HealtheLife is built for the Oracle Health world. If your reason for reading this guide is that a bundled portal cannot express your workflow, your brand, or a patient journey that spans several systems, an EHR vendor's own portal will pull you back toward the record system rather than toward the experience you wanted.

Notable work -- Oracle Health is deployed across many United States hospitals and health systems, and its revamped AI-powered patient portal has been covered in healthcare IT press. Specific outcomes vary by site, so evaluate HealtheLife against your own record system and ask peer Oracle Health organizations about real patient adoption.

Pricing signal -- Pricing is not publicly listed and is enterprise-scale, tied to an Oracle Health EHR contract. Expect health-system economics and confirm total cost through your Oracle agreement.

What to watch -- HealtheLife is the right choice mainly if you are on Oracle Health or moving to it. A practice on another EHR, or a team that needs a bespoke patient experience, will not get there with a bundled portal.

  • Best for: Hospitals and health systems on the Oracle Health (Cerner) EHR that want the bundled patient portal.

  • Specialization: EHR-integrated patient portal, records access, secure messaging, AI-assisted scheduling and explanations

  • Pricing: Not publicly listed; enterprise, tied to an Oracle Health contract

  • Clutch: Not a dev-shop listing -- evaluate via peer references and KLAS


4. athenahealth

athenahealth is a widely used EHR and practice-management platform, especially among ambulatory practices and physician groups, and its patient experience comes through the athenaPatient app and the athenaOne Patient Portal. It sits between the two hospital giants above and the smaller specialists below: cloud-based, practice-focused, and bundled with the record and billing system rather than sold as a separate portal.

The patient-facing feature set is solid for outpatient care. Patients see their health information, self-schedule appointments, check in and complete documentation before a visit, message their care team, attend telehealth visits, and pay bills. The athenaPatient mobile app adds biometric login so patients are not re-entering a password every visit, which sounds small but is exactly the kind of friction that decides whether people actually use a portal. Because the portal ties into athenaOne, the billing and scheduling data patients see is the same data the practice runs on.

The important limit is stated plainly in athenahealth's own materials: athenaPatient is available only to practices that have enabled the athenaOne Patient Portal. So this is a strong option if athenahealth is your record and billing system, and not an option at all if it is not. For a growing physician group already on athenaOne, turning the portal on is a configuration decision rather than a build. For an organization on a different EHR, or one that needs a patient experience athenahealth does not model, it is the wrong shape.

Notable work -- athenahealth serves a large base of ambulatory practices and physician groups across the United States, and athenaPatient is available on both major app stores. Specific outcomes vary by practice, so confirm fit against your own systems and ask peer athenaOne practices about patient adoption.

Pricing signal -- Pricing is not publicly listed and is tied to an athenaOne subscription, typically a percentage-of-collections or per-provider model rather than a standalone portal license. Confirm total cost through your athenahealth agreement.

What to watch -- The portal requires athenaOne. A practice on another EHR cannot license athenaPatient on its own, and a team that needs a custom or multi-system patient experience should look at an EHR-agnostic portal or a custom build.

  • Best for: Ambulatory practices and physician groups already on athenaOne that want the bundled patient app and portal.

  • Specialization: Practice-focused patient portal, self-scheduling, pre-visit check-in, telehealth, bill pay

  • Pricing: Not publicly listed; tied to an athenaOne subscription

  • Clutch: Not a dev-shop listing -- evaluate via peer athenaOne references


5. Bridge Patient Portal

Bridge Patient Portal is the entry for buyers who are not standardizing on one big EHR and its bundled portal. Bridge is a vendor-neutral, EHR-agnostic patient engagement product: instead of coming with a record system, it interfaces with them. By its own materials it connects to 15 or more EHR and revenue-cycle systems, and it supports HL7 and FHIR with deep, discrete write-back, which is the hard part most portals skip. For a multi-facility group running more than one EHR, or an organization that wants one branded patient experience across systems, that neutrality is the whole point.

The feature set is what you would expect from a dedicated portal: secure messaging, online self-scheduling, bill pay, customizable patient intake forms, and access to a consolidated health record. Because Bridge is built around the 21st Century Cures Act patient-access requirements, it leans into standardized API access to records rather than treating interoperability as an afterthought. It is closer to a configurable product than a from-scratch build, which lands it between the licensed EHR portals and the custom-build companies on this list.

Bridge earns its place because the configure-and-integrate path is real and often right. An organization whose processes are close enough to standard, but whose EHR estate is messy, gets a branded portal faster by licensing Bridge and paying for the interfaces than by building from zero. The honest caveat is that a configurable product still bends your workflow toward what it models. If your patient journey is genuinely unusual, or the portal is the core of a product you are taking to market, a configurable portal will eventually feel like a ceiling, and a custom build is the better fit.

Notable work -- Bridge is a documented EHR-agnostic patient engagement vendor with interfaces across many EHR and revenue-cycle systems and support for Cures Act patient-access APIs. Specific client references are not verified here, so ask for references on your exact EHR systems and confirm the write-back depth you need before signing.

Pricing signal -- Directory listings cite entry pricing starting around $500 per month, with total cost driven by the number and complexity of EHR, RCM, lab, and imaging interfaces. Treat the entry figure as a floor and get a quote that itemizes every interface.

What to watch -- Bridge is a configurable product, so it expects your workflow to fit within what it supports. A team whose patient journey is highly custom, or who is building a portal as the core of a market product, should confirm the fit before committing, or consider a custom build.

  • Best for: Multi-facility groups and organizations on mixed EHR systems that want one EHR-agnostic branded portal.

  • Specialization: EHR-agnostic patient engagement, HL7 and FHIR interfaces with write-back, self-scheduling, bill pay

  • Pricing: From about $500/mo per directory listings; interface complexity drives cost

  • Clutch: Not a dev-shop listing -- verify via direct EHR-specific references


6. Empeek

Empeek is a healthcare-only software company, based in Austin with a Ukrainian engineering team, that builds custom health products under HIPAA with HL7 and FHIR competence. Where the entries above are portals you license, Empeek is a firm you hire to build one. Its work spans AI health software, remote patient monitoring, and diagnostic tooling, which is the kind of adjacent experience that matters, because a team that has already shipped RPM has already dealt with device data, patient identity, and clinical audit trails.

For a buyer who has decided to build rather than license, a healthcare-only specialist is a shorter learning curve than a generalist. Empeek carries a strong verified review base at an accessible rate, which makes it a credible option for a digital-health team or a provider organization that wants a custom portal without hospital-scale consulting economics. Its focus is health software specifically, not a general product studio that also takes healthcare work.

The reason a healthcare-only focus is worth paying for, rather than dismissing as positioning, is that health software carries patterns a team either has internalized or has not. A portal has to verify that a login belongs to the right patient before it shows a single result. It has to handle proxy access for a parent or caregiver without leaking data. It has to log every access to protected health information because a breach investigation will ask. A firm that has built in this space raises these on the first call. A generalist raises them after they become defects. Ask Empeek, or any build firm here, to describe the trickiest patient-identity or EHR-integration problem it has solved, and listen for whether the answer is specific.

Notable work -- No specific patient-portal engagement is verified here. Empeek's public profile centers on healthcare software, RPM, and diagnostic AI under HIPAA with HL7 and FHIR work. Ask to see a live healthcare product and reference clients in your space, and confirm the EHR systems it has integrated.

Pricing signal -- $25-$49/hr per its Clutch profile, among the more accessible bands for a healthcare specialist, delivered from a Ukrainian team.

What to watch -- Empeek is a build firm, not a product you can license and switch on in weeks. A buyer who needs a portal live quickly and whose workflows are standard may be better served by a bundled or EHR-agnostic product than by a custom build.

  • Best for: Digital-health teams and provider organizations building a custom HIPAA-compliant portal at an accessible rate.

  • Specialization: Healthcare-only software, RPM, diagnostic AI, HIPAA and HL7 FHIR

  • Pricing: $25-$49/hr per Clutch

  • Clutch: 5.0/5 (20 reviews)


7. Klara

Klara is not a full patient portal, and that is the point of including it. It is a conversational patient engagement and communication platform used across more than 40 specialties, and it solves the one thing most portals do worst: getting patients to actually respond. Klara centralizes text messages, web chat, calls, and voicemail, with voicemail-to-text, into a single HIPAA-compliant conversation thread, so a practice talks to a patient the way the patient already communicates rather than forcing a portal login.

The feature set is built around communication and light workflow: secure two-way messaging between patients, providers, staff, and outside parties like pharmacies, plus automated appointment reminders, no-show follow-up, digital intake, and post-visit outreach. It also offers telemedicine with virtual waiting rooms. For a practice whose real problem is not records access but the daily grind of phone tag and missed messages, Klara can outperform a heavier portal on the metric that matters, which is whether patients engage at all.

Klara earns its place because adoption is the metric patient software is quietly judged on, and a full portal that patients ignore has failed at its job. The honest caveat is scope. Klara is a communication and engagement layer, not a system of record, and it is not a substitute for a portal that must expose the full chart, handle bill pay, or write structured data back into an EHR. Many practices run it alongside a portal rather than instead of one. If your requirement is deep records access and EHR write-back, Klara is a complement, not the answer.

Notable work -- Klara is a documented patient communication platform used across many specialties, with HIPAA-compliant messaging and telemedicine. Specific client references are not verified here, so ask for references in your specialty and confirm how it fits alongside your existing portal or EHR.

Pricing signal -- Pricing is not publicly listed and is typically quoted per practice or per provider. Get a quote scoped to your provider count and confirm what integrates with your EHR.

What to watch -- Klara is a communication and engagement layer, not a full records portal. A buyer who needs deep chart access, bill pay, or EHR write-back should treat Klara as a complement to a portal, not a replacement for one.

  • Best for: Practices whose core problem is patient communication and engagement rather than deep records access.

  • Specialization: Conversational patient engagement, HIPAA-compliant multi-channel messaging, digital intake, telemedicine

  • Pricing: Not publicly listed; per-practice or per-provider quote

  • Clutch: Not a dev-shop listing -- evaluate via specialty references and G2


8. TechMagic

TechMagic is a product-engineering company, headquartered in Lviv with United States and United Kingdom presence, and roughly half its work is in healthcare. Like Empeek, it is a firm you hire to build, not a product you license. What distinguishes it on a portal shortlist is its work as a Medplum partner, which signals real familiarity with FHIR-native, developer-first health data infrastructure rather than only bolting a portal onto a legacy EHR.

For a buyer building a modern, standards-first patient portal, that background matters. A team fluent in FHIR-native tooling starts from interoperability rather than retrofitting it, which is exactly the discipline the 21st Century Cures Act now expects. TechMagic carries a large verified review base, which gives a buyer a real pattern to read on how it delivers, and its healthcare depth means it is not learning HIPAA on your budget.

The transfer from EHR and health-data work to a patient portal is direct. A team that has built FHIR interfaces knows that the write-back is the hard part, that patient identity has to be solved before any data renders, and that audit logging is not optional in a system that touches protected health information. TechMagic sits at a higher rate band than the accessible specialists, which fits a buyer who wants a modern, standards-first build and can support that investment. Ask it to walk through a FHIR integration it shipped and an identity edge case it handled, and judge how cleanly that maps to your portal.

Notable work -- TechMagic is a documented product-engineering firm with a large healthcare practice and a Medplum partnership for FHIR-native health data work. Specific patient-portal client outcomes are not verified here, so ask for a live healthcare product and confirm the EHR and FHIR integrations relevant to your build.

Pricing signal -- $50-$99/hr per its Clutch profile, a mid-market band consistent with a modern, standards-first product-engineering firm.

What to watch -- TechMagic is a build firm at a mid-market rate, best suited to a modern standards-first portal. A buyer who needs a portal live in weeks, or whose workflows are standard enough for a bundled product, may not need a custom build at this band.

  • Best for: Teams building a modern, FHIR-native custom patient portal who value standards-first health-data engineering.

  • Specialization: Product engineering, healthcare, Medplum and FHIR-native builds, HIPAA

  • Pricing: $50-$99/hr per Clutch

  • Clutch: 4.8/5 (54 reviews)


Side-by-side comparison

OptionPrimary strengthTypical engagementPricing
EpicDominant EHR-bundled portal (MyChart)Bundled with an Epic EHR contractNot publicly listed; enterprise
RaftLabsHIPAA, EHR integration, and identity built in from sprint oneEnd-to-end custom portal build$29-$49/hr, fixed-price
Oracle HealthEHR-bundled portal with AI features (HealtheLife)Bundled with an Oracle Health contractNot publicly listed; enterprise
athenahealthPractice-focused portal bundled with athenaOneConfiguration on athenaOneNot publicly listed; subscription
Bridge Patient PortalEHR-agnostic portal with write-backLicense plus interface buildFrom ~$500/mo; interfaces drive cost
EmpeekHealthcare-only build firm at an accessible rateCustom healthcare build$25-$49/hr per Clutch
KlaraPatient communication and engagement layerLicense, per practice or providerNot publicly listed; per-provider
TechMagicFHIR-native, standards-first build firmCustom healthcare build$50-$99/hr per Clutch

The question that separates buying a portal from building one

Most buyers compare patient portal options on price or feature list and get the model wrong before they get the vendor wrong. The real fork on this list is whether you should license a portal at all, or build one, and if you license, whether you take the one bundled with your EHR or an EHR-agnostic product on top. Picking a company before you have answered that question is how organizations spend six figures building a portal their EHR already shipped, or spend a year fighting a bundled portal that never fit their patient journey.

Portal products -- Epic, Oracle Health, and athenahealth most clearly, and Bridge as the EHR-agnostic option -- serve the organization whose patient workflows are close enough to standard that configuring a mature product is cheaper and safer than building. If your future is one big EHR, the portal that comes with it will beat a custom build on records consistency and time to first login, every time. If you run several EHR systems and want one branded experience, an EHR-agnostic product like Bridge is the middle path. Klara sits alongside any of these as a communication layer when engagement, not records access, is the pain.

Build firms -- RaftLabs, Empeek, and TechMagic -- serve the organization whose patient journey, branding, or integration needs are the specific reason a bundled portal keeps failing. That is when a custom portal earns its cost: a multi-specialty group that needs one patient login across systems no single portal spans, or a digital-health company where the portal is the product and a licensed template would cap the roadmap. The best of these firms will tell you honestly, before quoting a build, whether a configured product would serve you first.

There is a practical test for which side of the fork you are on. List the three things your current patient experience gets wrong, and for each ask whether the problem is a portal that does not fit or a workflow that is genuinely unusual. If patients cannot find a result, that is a configuration or adoption problem, and a build is overkill. If patients need one login across three record systems that no product unifies, that is a build problem, and forcing a rigid portal will only move the pain around. Most organizations have a mix, which is why strong engagements often start with a build firm scoping which parts are truly custom and which should ride on an existing product through integration. A firm that insists everything must be custom, or a vendor that insists everything fits its product, is selling its own shape rather than solving your problem.

Getting the model wrong is more expensive than getting the vendor wrong. A custom portal solving a problem a bundled product would have handled is wasted money. A bundled portal forced onto a patient journey it cannot express is a slow tax on every patient interaction for years. Spend the first conversations on the model, not the price, and the vendor choice gets much easier.

A data point worth pricing in

Micky Tripathi, the former National Coordinator for Health IT, said the data-sharing rules under the 21st Century Cures Act "force a culture change" on an industry that had long treated patient records as something to guard rather than share.

"The Cures Act forces a culture change." -- Micky Tripathi, former National Coordinator for Health IT

The numbers show that shift landing. By the ONC's 2024 data brief, 77% of individuals were offered online access to their health information, up from 73% in 2022, and 65% accessed their records at least once in the past year, up from 57%. App-based access rose to 57%, from 51% in 2022 and 38% in 2020. The single strongest driver was not the feature list. It was provider encouragement: 87% of patients who were encouraged to use their portal did so, against 57% of those who were not. For a buyer, that reframes the whole decision. The portal that wins is not the one with the longest feature list. It is the one patients actually open, which means mobile experience, identity that does not lock people out, and a clean connection to the record all matter more than a marketing sheet. When you compare options, the cheapest number often quietly assumes the simplest answer to integration and identity, and the gap only shows once the second EHR or the caregiver-access case lands. The options that put HIPAA, integration, and identity in the first conversation are the ones that keep a portal out of the rebuilt majority.

The verdict

Epic for hospitals and health systems already on the Epic EHR that want the bundled MyChart portal. RaftLabs for organizations building a custom HIPAA-compliant portal end-to-end, with EHR integration and patient identity designed in from the first sprint. Oracle Health for systems on the Oracle Health EHR that want its AI-enhanced bundled portal. athenahealth for ambulatory practices already on athenaOne. Bridge Patient Portal for multi-facility groups on mixed EHR systems that want one EHR-agnostic branded portal. Empeek for digital-health teams building custom at an accessible rate. Klara for practices whose real problem is patient communication rather than records access. TechMagic for teams building a modern, FHIR-native custom portal.

The first filter is the model: license a bundled portal, license an EHR-agnostic one, or build custom. The second filter is the specific depth your portal needs -- deep EHR write-back, multi-system identity, telehealth, or engagement. Match those two questions to the right option on this list, and confirm the HIPAA and patient-access story with a live walkthrough before you sign.


RaftLabs builds HIPAA-compliant patient portals -- EHR integration over HL7 FHIR, secure messaging, and patient identity designed in -- with one team accountable from discovery to delivery. No handoff gap. 4.9/5 on Clutch. Talk to a founder about your patient portal project.

Ask an AI

Get an instant summary of this post from your preferred AI assistant.

Frequently asked questions

A custom patient portal MVP covering secure login, records access, appointment requests, and secure messaging typically costs $40,000-$90,000. A full platform with deep EHR write-back over HL7 FHIR, telehealth, bill pay, patient intake forms, and multi-facility support typically runs $100,000-$250,000 or more. The biggest cost drivers are the number and type of EHR, lab, and billing systems you integrate, and the depth of that integration - a single discrete FHIR write-back interface can add 30-50% to a base estimate. Off-the-shelf portals shift the cost from build to license and per-provider fees, so compare the three-year total, not just the first invoice. Ask any company to break the quote down by module and by integration so you can see what the EHR connection actually costs.
A production-ready custom patient portal MVP takes roughly 12-18 weeks from kickoff. A full platform with EHR write-back, telehealth, and multi-facility support takes 24-36 weeks. Licensing and configuring an existing portal is faster to first login, often a few weeks, but the EHR interface work and patient-identity mapping still take real time. Teams that run a discovery phase and lock the integration list and identity model before writing product code are consistently faster, because the EHR connection is where late-stage rework hides.
Buy or license an existing portal when your workflows are standard and the portal that ships with your EHR covers them. Build custom when your patient journey, branding, or integration needs are the reason the bundled portal keeps failing your team - for example a multi-specialty group that needs one patient login across several EHR systems, or a digital-health product where the portal is the product. A good partner will tell you honestly which camp you are in before quoting a build. A red flag is a company that recommends a full custom build without first asking whether the portal you already own would serve you at a fraction of the cost.
Modern patient portals connect to an EHR through HL7 FHIR APIs for structured data like results, medications, and appointments, and older HL7 v2 interfaces for systems that predate FHIR. The 21st Century Cures Act requires certified EHRs to expose standardized FHIR APIs, so read access to records is more consistent than it used to be. The harder part is write-back - letting a patient book an appointment or send a message that lands correctly inside the EHR. Ask any vendor which specific EHR versions they have integrated, whether they support discrete FHIR write-back or only read, and to name an integration they got wrong once and fixed.
Good answers name specific controls: role-based access so a patient sees only their own record, audit logging on every access to protected health information, encryption in transit and at rest, a signed business associate agreement with every subprocessor, and strong patient identity verification at sign-up. The answer should treat compliance as an architecture decision made in the first sprint, not a checklist added before launch. A vague answer that equates HIPAA with a hosting certificate, or that cannot explain how it matches a login to the correct patient, means the team has not built for the confidentiality health data demands.
Ask to see a live healthcare product and walk one access boundary in it - log in as a patient, then as a provider, and confirm the patient cannot see another patient's data. A company with genuine healthcare experience will have a story about a specific HIPAA, identity, or EHR-integration edge case it got wrong once and fixed. It will also name the EHR systems it has connected to. The red flag is a portfolio of generic dashboards with no live healthcare product, or a team whose only compliance reference is a hosting badge rather than an architecture decision.
You should, from the first commit - every repository, cloud account, and integration credential in your name. Patient data is among the most regulated data your organization holds, so a company that hosts it in accounts you cannot access, or that cannot commit to full source-code ownership, is building a dependency you will pay to unwind later. With a licensed portal, confirm data export rights and an exit plan in the contract before you sign. With a custom build, confirm code and data ownership in writing before the first sprint.