Patient portal
Appointments, results and documents sit in one place, and a follow-up is booked from the appointment card without a call to reception.
- Buildfrom $2,850
- Timeline4–7 weeks
- Supportfrom $570/mo
Who this suits: Clinics where results are handed over on paper or in a messenger, and reception spends the line on whether a test is ready.
What is in the first version
- sign-in by code
- appointments and results
- notes and certificates
- rebooking
The figures above are the package this sits on: CRM or client portal. Anything past its edges the calculator adds before the work starts, not after.
How the path goes
- 01
Signing in proves the patient
Sign-in goes by phone with a code matched against the record in your medical system, never by a mailed link.
- 02
A result appears once confirmed
Not when the laboratory uploads a file: a doctor's check stands between the upload and the patient seeing it.
- 03
The follow-up sits beside the appointment
The doctor sets a check-up, and the booking button leads to that doctor with the service already chosen.
What decides whether this works or annoys people
A bare result reads as diagnosis
Next to every result stands who will comment on it and when, or a value out of range loads reception.
What the locked screen shows
A notification carries the fact that something is ready and never the name of the test, and the same rule governs SMS.
One number for the whole family
A parent, a child and a relative share one number, so the link between representative and patient is in the first version.
What to measure once it is live
- results collected without reception
- calls about a ready result
- follow-ups booked in the portal
- no-shows after a reminder
Why this comes out faster
The shape of this one is known: the states, the edge cases and the things that usually go wrong have been decided before. Nothing here is a template, and the saving is not in your half of the work. It goes into your process, your content and the systems this has to talk to, which is the part nobody can have solved in advance.
A likely stack for this
Picked against the task when we scope it, not decided in advance. This is the shelf it usually comes off.
- The portalTypeScriptReactNext.js
- Server and dataNode.jsPostgreSQLPrismaRedisS3
- Exchange with the clinic system and notificationsPythonFastAPIn8nTelegram Bot APIDockerGrafana
Price it yourself, right here
Five steps, and you can see the number without leaving a contact. The estimate accounts for the kind of work, what you already have and what it will need inside.
These bills do not come from us
- SMS with codes and reminders
- licences for the medical and lab systems
- hosting and storage for scans
- the doctor's electronic signature and its authority
Asked before the first call
- Does this replace our medical system?
- No. The medical system stays the truth for the schedule, appointments and results, and the portal is its face for the patient; where it has an API we read through it, otherwise through a folder.
- Where is the medical data kept?
- In your own infrastructure and in the jurisdiction you name. We keep no copy, developer access to live data is closed, and every opening of a patient record is logged.
- Who answers a patient who asks a question?
- Your own member of staff, and it is not an open chat: the question is attached to an appointment, with an addressee and a time to answer by. No automatic answering about health.