Patient Portal Features: What a Portal Must Do and What It Should

A patient portal feature list in three tiers: what regulations and certification require, what patients actually use according to federal survey data, and the staff-side features that decide whether the portal saves work or creates it.

In short

  • Some patient portal features are required: certified EHR portals must let patients view, download and transmit their records with date filters and an activity history, patients have a HIPAA right to their records within 30 days, and recipients of federal funding must meet WCAG 2.1 AA for web and mobile content.
  • Federal survey data shows what patients use most: in 2022, 90% of those who accessed their records viewed test results and 70% viewed clinical notes, and by 2024, 51% of individuals had accessed the record of someone they care for.
  • The features that decide whether a portal saves staff time are on the back-office side: message routing, release rules for results, proxy management and a queue for exceptions.

A patient portal must, at minimum, let patients see their health information, download it, send it to someone else, and do so in a way people with disabilities can use. Beyond that floor, the features worth building first are the ones patients actually use: test results, clinical notes, appointments, messages, and access for caregivers. The features that decide whether the portal saves staff time sit behind the scenes: how messages are routed, when results are released, how proxies are managed and where exceptions go.

For product owners and practice leaders writing a portal specification or reviewing a vendor's, the features fall into three tiers: required, expected and operational. Required features come from regulations and certification criteria, and the expected ones from federal survey data on what patients use.

Which patient portal features are required?

Three sets of rules set the floor. Which ones apply depends on who you are, but a portal built to meet all three is easy to sell to any provider.

Certification: view, download and transmit

EHRs certified under ONC's §170.315(e)(1) must give patients and their authorized representatives these capabilities:

  • View at least the USCDI data, assessment and plan of treatment, goals, health concerns, lab reports and diagnostic imaging reports, plus the provider's name and contact details in ambulatory care, or admission and discharge details and discharge instructions in inpatient care.
  • Download an ambulatory or inpatient summary in human-readable form and as a C-CDA CCD document.
  • Transmit the summary by email to any address and by an encrypted method.
  • Select data for a specific date or a date range.
  • See an activity history of every view, download and transmit, with date, time, user and addressee.
  • Request restrictions on their data through an internet-based method, with a regulatory compliance date of January 1, 2026.

The criterion also requires WCAG 2.0 Level A at minimum. If you are building a portal outside a certified EHR, this list is still the clearest specification of what patients expect from record access.

HIPAA: the right of access

Under 45 CFR 164.524, patients can inspect and get a copy of their information in the designated record set. The covered entity must act within 30 days, with one extension of up to 30 more days if it explains the delay in writing. It must provide the information in the form and format requested if readily producible, including electronic formats. A patient can also direct, in a signed written request, that a copy be sent to a person they designate. A portal with download and transmit features makes most of these requests self-service.

Accessibility: WCAG 2.1 AA

45 CFR 84.84 requires recipients of federal financial assistance to make the web content and mobile apps they provide, directly or through contracts and licenses, conform to WCAG 2.1 Level A and AA. Recipients with 15 or more employees must comply from May 11, 2027, and those with fewer from May 10, 2028. In practice this means screen reader support, keyboard navigation, sufficient contrast, text that resizes, labeled form fields and accessible error messages, on the web portal and the apps alike.

Information blocking rules sit around all three. They apply to healthcare providers, developers of certified health IT and health information networks, and treat practices likely to interfere with access to electronic health information as a risk. Design defaults that share, such as releasing results to the portal, are the safer choice.

Which features do patients actually use?

ONC's 2022 data brief reports what people did among those who accessed their records in the past year:

  • Viewed test results: 90%.
  • Viewed clinical notes: 70%.
  • Downloaded their health information: 32%.
  • Sent their information electronically to a third party: 20%.

The 2024 brief adds two trends that should shape the feature list. App access keeps growing: 57% of people who accessed their records used an app in 2024, up from 38% in 2020. And caregivers are now a core user group: 51% of individuals accessed the record of someone they care for or make decisions for, up from 24% in 2020.

What should a portal's core feature set include?

Based on the required floor and the usage data, a sensible first release covers:

  • Test results, with reference ranges, a plain-language note where the care team adds one, and a clear path to ask a question about a result.
  • Clinical notes and visit summaries, searchable by date.
  • Appointments: view, book or request, reschedule, cancel, and pre-visit forms and check-in.
  • Secure messaging with the care team, with clear expectations about response times and what not to send through messages.
  • Medications and refill requests.
  • Bills and payments.
  • Download and share: the summary download, transmit to a third party, and a way to connect apps the patient chooses.
  • Proxy access for caregivers and parents, with roles and limits.
  • Notifications by email, text or push that point into the portal without putting PHI in the message.
  • Profile and preferences: contact details, language, notification settings.

Telehealth links, education content, care plans and remote monitoring come next, depending on your care model. They matter more for chronic care and home care programs than for a general practice.

How should proxy access work?

Proxy access needs more design than it first appears, and the 2024 data shows caregiver use more than doubled since 2020. Design for these cases:

  • Parents of young children, with access that changes as the child reaches the age your state sets for adolescent privacy.
  • Adult patients who invite a family member, choose what that person can see and do, and can revoke access at any time.
  • Legal representatives whose authority is verified by staff before access is granted.
  • A proxy who manages several people, switching between them without signing out.
  • A clear display, on every screen, of whose record is open.

Our white-label home care platform for a digital health company in Australia shows how far role design can go. It has five roles: the Captain who owns the network, an Admin, Helpers, Inner-circle helpers and the wider helper network of family and friends. Tasks can be marked visible to the inner circle only, and helpers accept the tasks they can take on.

Which staff-side features decide whether the portal saves work?

Every patient feature has a staff side. If it is missing, the portal moves work from the phone to the inbox instead of removing it.

  • Message routing by topic and location, so a billing question does not land with a nurse.
  • Result release rules: which results go to the portal immediately and which wait for a clinician's note, set within what information blocking rules allow.
  • Proxy management: a queue to verify representatives and a log of who granted access.
  • Form intake that writes into discrete EHR fields where possible, instead of only a PDF in the chart.
  • An exceptions dashboard for cases the system cannot process automatically.
  • Access scoped to each user's role, so each clinician sees only their own patients.

Our provider portal for a US third-party administrator is an example. Chat sits in the portal's main areas and routes to the right department, with saved conversations so users continue where they left off. Claims and referrals are checked automatically against defined parameters and entered into the client's EHR, and a dashboard lets the claims team review questionable cases. Claims and referrals are now processed three times faster, and inbound calls and emails dropped by 95%.

What can wait until after launch?

  • Features that duplicate another portal your patients already use well.
  • Custom dashboards and health trackers without a clinical owner who will look at the data.
  • Chatbots that answer clinical questions. Start with routing and FAQs.
  • Rarely used administrative forms that staff can handle by phone for now.

Then measure. Track how many patients start and finish each task. A feature people start and abandon shows where the design breaks. A feature nobody starts is either hard to find or not needed.

We sign a BAA before anyone on our team sees PHI and run a penetration test before launch. If you are writing a portal specification or reviewing a vendor's feature list, talk to one of our engineers. Our free five-day technical audit ends with a written report on what to build first, what your EHR's APIs support and what can wait.