Client Portal
A branded space where your customers see their documents, requests and invoices without emailing you.
Next.js · TypeScript · PostgreSQL · Auth.js
Explore
From $529
Your carePatient1 / 8
CRM & SalesHealthcareLive
Patient Portal
Most of a clinic's phone traffic is four questions asked repeatedly: when am I in, what did the test say, can I have a refill, and what is this invoice. This answers all four before the phone rings, and gives the front desk the same lists across every patient.
- From
- $749
- Function
- 24
- Roles
- 2
- Users
- Unlimited
Next.js · TypeScript · PostgreSQL · Auth.js
Inside the app
What it does out of the box
24 connected functions on one schema, spanning two sides of the same clinic. Everything below is in the template before a line of customisation.
Your care
Opens on the next appointment, what is still pending from the lab, what is unpaid and what requests are open. Four answers before the phone rings.
Results
Every result the clinic has released, by department and status. A pending result is visible but not downloadable, because releasing it is a clinical decision.
Prescriptions
Active and expired medication with dose, frequency and prescriber, and a refill request that goes to a person rather than approving itself.
Appointments
A month calendar with the booked days marked, the selected day in detail, and a history that keeps the missed ones on the record.
Billing
The full amount charged, what the insurer settled, and the share that is actually yours. Patients are entitled to see all three.
Support
An administrative channel with categories that deliberately exclude symptoms, and a thread the patient can read back.
Clinic today
Open tickets, appointments today, overdue invoices and active patients, with attendance and ticket sources charted.
Clinic schedule
The whole diary by clinician and location. Unconfirmed is the number that predicts a wasted slot, so it is a status rather than a footnote.
Invoices across patients
Filtered by payer and status, showing what is still outstanding after the insurer settled, which is the only figure worth chasing.
Ticket queue
One queue, one owner per ticket, aged from when the patient raised it rather than from when somebody opened it.
What it is not
Not a clinical system. It does not calculate reference ranges, flag abnormal values, check interactions, dispense, or triage anything.
Access
A patient reaches their own record and nothing else, enforced at the database row level, with every staff read written to an access log.
Permissions
Two sides, one build
A patient sees their own record and nothing else, enforced at the database row level rather than by hiding buttons. Clinic staff see the same information across every patient, and every record they open is logged.
Patient8 functions
Their own record, and only their own
- Next appointment, pending results and what is unpaid
- Results by department, downloadable once released
- Prescriptions, with a refill request that reaches a prescriber
- A month calendar for booking and rescheduling
- Invoices split into charged, settled and your share
Clinic staff16 functions
The same lists, across every patient
- Open tickets, today’s list and what is overdue
- The clinic-wide diary by clinician and location
- Invoices filtered by payer, with outstanding balances
- One ticket queue with an owner and an honest age
- Every record opened is written to the access log
The build
Every function in the box
24 functions, all of them live in the preview. Nothing on this list is a mockup or a roadmap item.
Access
- Sign in
Patient side
- Your care
- Results
- Prescriptions
- Appointments
- Billing
- Support
Clinic side
- Clinic today
- Clinic schedule
- Billing
- Ticket queue
Throughout
- Row-level access per patient
- Access log on every staff read
- No clinical interpretation anywhere
What you get
Delivered as a repository, not a login.
Clinics, practices and care providers who want a patient-facing portal they own outright.
- 11 production functions spanning the patient side and the clinic desk
- Full source code and PostgreSQL schema in your repository
- Role-based access control, enforced server-side
- Immutable audit log written on every change
- Responsive layouts, usable on a phone, not just resized
- CSV import and export on every core record
- Deployment configuration for your cloud account
- Twelve months of updates, and no per-seat charge ever
Access and evidence
Built for the access review
In healthcare the question is never only what changed, but who looked. Record access is logged whether or not anything was edited, and access follows the care relationship rather than a job title.
- Every record view is logged, not just every change
- Access scoped by care relationship, enforced server-side
- Reception can see scheduling and billing, never clinical records
- Results are released by a clinician, never automatically
- Locum and agency accounts expire on a date, automatically
- Consent recorded, versioned and withdrawable
- Self-hosted or in-region, so patient data never leaves your control
Related
Apps that pair with this one
Customer Success Hub
Health scores, renewal calendars and QBR prep for the team that keeps revenue from leaking.
Next.js · TypeScript · PostgreSQL · Recharts
Explore
From $649
Employee Hub
Announcements that require an action, tracked per employee, with reach reporting for managers.
Next.js · TypeScript · PostgreSQL · Auth.js
Explore
From $649
Questions
Patient Portal, in practical terms
Do I get the source code for Patient Portal?
Yes. The repository, application code, database schema, migrations, seed data and deployment configuration, is transferred to your organisation on delivery. There is no licence key and nothing that calls home.
Is this compliant with health data regulation?
The template gives you the mechanisms compliance depends on, access logging on reads, scoped permissions, consent records, retention rules and self-hosting in your own region. It does not, and cannot, make you compliant by itself: that depends on your policies, contracts and how you operate it. We scope the specific controls your regulator expects as part of a fitted build.
Who can see a patient's record?
Only staff with a care relationship to that patient, and the patient themselves. Scope is enforced at the database row level rather than by hiding navigation, so a reception account cannot reach clinical records even by manipulating a URL. Every view is logged.
Does it replace our clinical system?
No. It is the patient-facing layer that sits in front of whatever you already run. A fitted build integrates with your practice management or clinical system so appointments and documents flow both ways, leaving the clinical record where it is.
Can Patient Portal be changed to match our clinic?
That is the usual route. A fitted build adjusts appointment types, result release rules, consent wording, ticket categories, billing and cover, branding and up to two integrations, and typically takes one to three weeks from a signed scope.
What does it cost to run?
Hosting only, paid to your own cloud provider, roughly $50 to $200 a month depending on patient volume and document storage, with in-region hosting available where residency rules require it.
Want Patient Portal shaped around your process?
A fitted build adjusts fields, stages, roles and integrations to how your team already works. One scoping call, a fixed price, one to three weeks.
