ContactBook a call

Industries/ Healthcare/ Patient portals

Patient portal software that works before the visit, and after it

Patients book and move appointments, complete their forms at home and pay invoices without ringing the desk. Results and letters appear only when a clinician releases them, and every view is recorded.

A middle-aged woman at her kitchen table checking a clinic appointment and a letter on a tablet, reading glasses on, morning light.
Used by
Patients, reception, clinicians and the practice manager
Takes the place of
Phone bookings, clipboard forms and results given over the phone
Connects to
Your practice management system, card payments and SMS
Built with
Our customer portals service

Where it hurts today

A normal week, before it exists

A patient who wants to move Thursday's appointment rings at 8.30am, along with everyone else who wants something before work. The line is engaged, so they try again at lunch, and reception is checking someone in while the phone rings out. By the time anyone answers, the slot they wanted has gone. Multiply that by every booking, cancellation and question about what to bring, and the desk spends its morning on calls a screen could have handled.

New patients complete history and consent forms on a clipboard in the waiting room, often while their appointment time ticks past. Someone types them up at the end of the day, guessing at handwriting and chasing the missing signature. Insurer details arrive half complete, so the invoice goes out late or to the wrong place. Letters still go out by post, and copies of clinic letters sit in a tray until someone has time to send them.

Results are the hardest part. A patient rings to ask whether their scan report has arrived. Reception cannot discuss it, and should not try, so a message goes onto the clinician's list and a call-back happens days later. Meanwhile the team checks identity over the phone with a name and a date of birth, which anyone with a little information could supply. Everyone knows it is not ideal, and nobody has had time to fix it.

What it does

Patient portals, feature by feature

A portal built around the questions patients bring to the desk, and the moments before and after a visit when they need something from you.

  1. 01

    Online booking against your real diary

    Patients see only the appointment types you choose to offer online, with the right length, site and clinician for each. Availability comes straight from your practice diary, a slot is held while the patient confirms, and your rules apply: new patients book an initial assessment first, and some appointment types stay with reception.

  2. 02

    Digital intake forms before the visit

    History, consent and insurer forms go out with the booking confirmation, with a reminder if they are still open two days before. Returning patients confirm or change what they told you last time instead of starting again. Answers land in the record as structured entries, and reception can see whose forms are done.

  3. 03

    Test results and letters released by a clinician

    Nothing appears in the portal just because it arrived. A clinician opens the letter or result, decides whether to release it, and can add a short note or choose to speak to the patient first. The patient gets a message saying a document is waiting, never what it says.

  4. 04

    Secure sign-in with passkeys and two-factor

    Sign-up is matched against the record you already hold, then confirmed with a code sent to the mobile number on file, or in person at the desk. Patients sign in with a passkey, or a password and a second factor. Parents, guardians and carers get their own logins with access you define.

  5. 05

    Online invoices and insurer details

    Patients see each invoice, what their insurer is expected to cover and what is theirs to pay, and can pay by card in a couple of taps. They can upload an insurer authorisation code or a new membership number themselves, and download receipts for their own claims.

  6. 06

    Admin requests, not a clinical inbox

    Patients can ask for a receipt, update an address or request a copy of a letter, and each request lands in the reception queue with an owner. The portal states clearly, in wording your clinical lead approves, that it is not for clinical questions or urgent help, and where to go instead.

A day with it

How the day runs instead

A normal Tuesday at a two-site physiotherapy and podiatry clinic, with the portal running alongside the phone.

  1. 6.40am
    New patient

    She books an initial physiotherapy assessment on her phone during the commute, choosing the evening slot at the nearer site. The confirmation arrives with links to the history and consent forms. She fills them in over lunch, adds her insurer's authorisation code, and never needs to ring.

  2. 8.15am
    Receptionist

    He opens the arrivals list for the day. Each patient shows whether their forms are complete. Two are still open, and both have had their automatic reminder. One patient prefers the phone, so he rings her and completes the form with her while the line is quiet.

  3. 11.30am
    Physiotherapist

    Between patients, she reads a scan report that came in overnight, adds two plain sentences saying she will go through it at the next session, and releases it. The patient receives a text saying a document is waiting in the portal, and nothing more.

  4. 2.00pm
    Practice manager

    She checks the invoices paid through the portal since Monday and the authorisation codes patients have uploaded. Three accounts show an insurer query, and she passes them to finance with the patient's own upload attached, rather than asking anyone to phone.

  5. 6.10pm
    Carer with proxy access

    A daughter who manages her father's appointments moves his podiatry review to next week from her own login. She can see his appointments and invoices, as agreed with him and the practice, but not his letters, and the change appears in the diary at once.

What it connects to

Works with what you already run

The portal is a window onto the systems you already run. It does not become another place where patient records are kept.

  • Practice management system

    Appointment types, availability and patient details are read from your diary through its API, ideally a FHIR interface where one is offered, and bookings are written back the same way, so phone and portal bookings land in one place.

  • Electronic record or document store

    Completed forms are written into the record as structured entries or attached documents, depending on what your system accepts. Released letters and results are read from it, never copied permanently into the portal.

  • Card payments

    Invoices are paid through your card payment provider's hosted payment page or fields. Card numbers never pass through the portal, and the payment status is written back against the right invoice automatically.

  • SMS and email

    Verification codes, booking confirmations and notices that something is waiting. Messages carry times, sites and links, but no clinical information, because phones and inboxes are often shared with family.

The first version

Start small, then grow it

A first version should be useful on day one and small enough to get right. This is where we would usually draw the line, and what tends to follow once people are using it.

In the first version

  • Online booking and rescheduling for follow-up appointments with existing patients
  • New patient history and consent forms sent with every booking confirmation
  • Sign-up matched to the existing record, with passkeys or two-factor sign-in
  • An arrivals list for reception showing whose forms are complete
  • A log of every patient view, change and download from the first day

Once it is in use

  • Letters and results released by clinicians, once the release process is agreed with them
  • Online invoice payment and patient uploads of insurer authorisation codes
  • Proxy logins for parents, guardians and carers, with limits you define
  • Admin requests from patients routed to the reception queue with an owner

Buyer's guide

Before you commission one

Four decisions worth making before you commission a patient portal, whoever ends up building it.

  1. 01

    Built-in portal or custom

    Most practice management systems include a patient portal, and if yours covers booking, forms and payments in a way patients find easy, use it. It is cheaper, supported and already connected. A custom portal earns its place when you run several systems the built-in one cannot reach, need rules it cannot express, such as proxy access or release steps, or want one front door across sites on different software.

  2. 02

    What to gather first

    Pull together the calls reception takes most often, your current paper forms, your appointment types with their lengths and booking rules, and the interface documentation for your practice system. Ask your supplier whether it offers a FHIR or other documented API, and on what terms. Those four things decide most of the scope before anyone draws a screen.

  3. 03

    Who should own it

    A practice manager or operations lead should own the portal day to day, with a named clinician owning the release of results and letters, and your data protection lead signing off access rules. Reception should have a voice from the start, because they will field every question patients have about it and will know first when something is confusing.

  4. 04

    How you will know it is working

    Watch the signals that matter at the desk: how many bookings and changes arrive online rather than by phone, how many forms are complete before patients arrive, how quickly invoices are paid, and what patients ask reception about the portal itself. A rising number of calls about logging in is a design problem to fix, not a patient problem.

Terms worth knowing

The words you will meet

FHIR API
FHIR is a standard from HL7 for exchanging health information, such as appointments and patient details, between systems. If your practice system offers a FHIR interface, a portal can connect to it in a well-understood format rather than through a custom export, which makes the connection easier to build and to maintain.
Passkeys
A passkey is a sign-in credential kept on the patient's phone or computer and approved with the same fingerprint, face or PIN they already use on that device. There is no password to forget or steal, and passkeys resist phishing, which matters when an account holds health information.
Proxy access
Access to a patient's account by someone acting for them, such as a parent, guardian or carer. Good proxy access gives that person their own login with limits on what they can see, rather than a shared password, so every action is recorded against whoever actually took it.

Handled with care

The details that matter here

A portal puts patient information on screens you do not control. These are the details we work through with your data protection lead and clinical lead before anything goes live.

  • Proxy access with clear limits

    A parent's access to a teenager's account, or a carer's access to an older patient's, needs rules about age, consent and what each person can see. We agree those rules with your data protection lead and clinical lead, build them into the permissions, and make every proxy action visible in the log.

  • Release rules that fit your region

    We design the release step with your clinicians and compliance lead: who can release what, whether a note is needed, and what can wait. In the US, the information blocking rules apply to providers, so delays need a recognised reason. The portal never interprets a result. It only shows what has been released.

  • Messages that give nothing away

    A text on a lock screen or an email in a shared family inbox can be read by anyone nearby. We keep every notification free of clinical detail, and for sensitive services we agree neutral wording with you, so even the name of the clinic can be left out if you prefer.

  • Never the only route

    Some patients will always prefer the phone, and some need help to use a screen. We design to WCAG 2.2 at level AA, test with screen readers, large text and keyboards, write in plain language, and keep phone bookings going into the same diary.

Guides

Worth reading first

Questions

What buyers ask first

Do patient portals integrate with practice management systems?

They should, because a portal that does not is a second diary nobody trusts. We connect to your practice system through its interface, ideally a documented API or a FHIR endpoint, so bookings, patient details and forms flow both ways and reception keeps working in the system they know. If yours offers no usable interface, we will tell you plainly what that means before anything is built, including whether your supplier's own portal would serve you better.

How do you get patients to use a patient portal?

Some will not, and the phone should stay open for them. Uptake comes from making the portal the quickest route to something patients already want: the next appointment, the form they must complete, the receipt for their insurer. We add links to every confirmation, a prompt at the desk and a code to scan in the waiting room, then show you how many patients are using it so you can decide where to push.

Should test results be released to patients automatically?

By default we build release as a deliberate step by a clinician, because a result without context can worry a patient. Rules differ by region, though. In the US, the information blocking rules that came from the 21st Century Cures Act apply to healthcare providers, so holding information back needs to fit a recognised exception. Your compliance lead decides what can wait, we build the rule they set, and the portal never interprets a result.

Can parents or carers access a patient's portal account?

Yes, through proxy access with its own login, never a shared password. You decide what each kind of proxy can see: a carer might manage appointments and invoices but not letters, and access to a teenager's account may change as they get older. Your data protection lead and clinical lead agree the rules, the patient's consent is recorded where it applies, and every proxy action is logged.

Who owns the patient portal and the data in it?

You do. Patient information stays in your own systems, and the portal holds only what it needs to work, such as accounts, logs and form drafts, in hosting in the region your obligations require. The source code, the hosting accounts and the documentation are yours, so another team could take it on. We agree data handling in writing with your data protection lead before any real patient is invited.

Tell us what patients ring the desk about

Walk us through the calls reception takes most often. We reply within 48 hours and will tell you plainly which ones a portal should answer and which should stay with a person.

More for healthcare

What else we build for healthcare