Home / Services / Patient portal development

Patient portal development

A patient portal your patients actually finish using.

For practices and clinic groups that want patients to book, fill out intake forms and pay online, without calling the front desk. We build the portal on the web and on the phone, connected to the tools you already use.

Talk about your project

The problem

Most clinics already have a portal that came with their EHR. Patients forget the login, the forms are long and generic, and booking still ends in a phone call. Staff then re-type answers from paper or email into the chart. A portal only helps when patients can finish what they started, on their own phone, in a few minutes.

What we build into a portal

  • Booking and rescheduling. Patients pick the visit type, online or in person, and a time that is shown correctly in their own time zone.
  • Intake forms that get finished. Short forms for each visit type, saved as the patient goes, filled out at home before the visit.
  • Records and messages. Visit summaries, documents and secure messages, each shown only to the people who should see them.
  • Payments. Card payments and balances through a payment provider, so card details never touch your servers.
  • Web and phone. A web portal and a React Native app for iPhone and Android that share the same rules and data.

What drives the cost

Every portal is different, so we don't publish a single price. These are the things that move it the most:

  • How many patient flows. Booking alone is smaller than booking plus intake, records, messages and payments.
  • Connections to your EHR and other tools. A clean, documented API is quicker to connect than one that needs exports or a middle layer.
  • Web, phone or both. A web portal is one build; adding iPhone and Android apps adds design, testing and store releases.
  • Visit types and rules. Each visit type, provider rule, state or insurance check adds cases to design and test.
  • Support after launch. Fixes, updates and new features can be a one-off handover or a monthly retainer.

The price and timeline are fixed in writing after a short scoping call, before any work starts.

How long it takes

The schedule depends on the scope above. Every project follows the same steps, and you see working screens early:

  1. Scoping call. We map how patients book, prepare for and pay for visits today, and agree on what the first release includes.
  2. Design and clickable screens. You test the main flows with sample data before we build them.
  3. Build in short rounds. Working screens to review regularly, with your EHR and payment connections added as we go.
  4. Testing and release. The full patient journey tested end to end, then released on the web and in the app stores.

HIPAA and patient data

Built to HIPAA requirements, the way Talha worked at PsychPlus: access by role, audit logs of who opened or changed patient data, encryption when data is stored and sent, and least-privilege access for our team and your tools. Early builds and demos use sample data, never real records. There is no official HIPAA certification for developers; we build the technical controls your compliance team asks for and document them, and your organization stays responsible for compliance.

Proof

Talha worked on booking, intake forms, patient sessions and provider calendars for PsychPlus, a US mental health platform with a patient portal and app. He also built CruzMédika, a patient app for booking visits and keeping records.

Case study: PsychPlus
Web and mobile work by Talha Manzoor as a Senior Software Engineer with the PsychPlus team, not an HTH client project. The product, brand and data belong to PsychPlus. Screens use sample data.

Project: CruzMédika
Find a provider, book a consultation and keep prescriptions and records in one React Native app.

Questions

Can the portal work with our EHR?

Usually, if the EHR has an API you can give us access to. We read its documentation before we commit to an integration, and tell you plainly if it can't be done well.

Do we have to replace the portal that came with our EHR?

No. Many clinics keep it for records and add a simpler booking and intake flow in front of it. We'll tell you which route makes sense on the scoping call.

Who owns the code?

You do. The code, designs and accounts are handed over to you, and we document how to run and update the portal.

Can you look at our current portal first?

Yes. We can send you two or three quick ideas for your booking and intake, based only on your website, at no cost.

Related