Patient app
Book a visit, see the token number, and read results without calling the front desk.
- Appointments with the doctor they choose
- Lab results, prescriptions and bills in one place
- Messages with their care team
{{product}} is a highly modular, very customizable and adaptable hospital management system. It carries a patient from the front desk or the ambulance bay to discharge: appointments, notes, prescriptions, labs, imaging, wards, the operation theatre and the bill, in your currency, time zone and formats.
Take the shift: tap a ready bed to admit whoever is waiting, a red bed to answer its alert, a yellow one to finish cleaning.
Patients, staff and our support team each see a different app, built for what they do. The hospital owner decides who on staff can see and change what.
Book a visit, see the token number, and read results without calling the front desk.
The outpatient queue, the emergency bay, the wards, the lab and billing, in your hospital's own colour and logo.
Most hospitals set themselves up. When you would rather have a hand, a technician from our team does it with your staff.
Most hospital software arrives as one large package you pay for in full and then work around. {{product}} is made of modules you switch on and off, with the settings a real hospital needs, and it is easy enough that your own staff can run the setup.
Registration, emergency, wards, lab, imaging, pharmacy and billing all write to the same patient. Nobody re-types a name.
Turn a module off and the records it made stay readable. The switch tells you exactly what stops and what stays before you flip it.
Departments, wards, beds, roles and branding are set from plain screens by your own staff. No consultants, no months-long rollout.
A base plan, a line for each module you run and a bed rate. Your quote is built from those lines and nothing else.
An administrator can export every record as a machine-readable file at any time, and that export keeps working even if an invoice is overdue.
Allergy clashes stop a prescription, a critical lab value alerts the doctor, and a second person releases results before the patient sees them.
Every hospital begins with the same core: patient records, appointments, outpatient care, roles and the audit log. Emergency, wards, theatre, lab, radiology, pharmacy, billing and insurance dock onto it when you run them, and undock when you don't.
Would you play this? The little colony above is a running simulation, not a picture of one. There is a game in it: build a hospital, staff it, keep the queue moving. If enough people ask for it, it gets built. Tell us you want it and we will count you in.
Each step picks up where the last one stopped. Nobody re-types a name, and a doctor opening the chart at night sees the same thing the day team saw.
One record per patient, found by phone number or ID in seconds.
The waiting room screen and the patient's phone show the same number.
Notes from your own templates and a prescription, checked against allergies.
Orders reach the lab directly. Critical results alert the doctor.
A bed from the live board. Nurses chart each dose and the fluids in and out.
Every service already on the bill, deposits taken off. The patient pays and leaves.
Nurses, doctors and the theatre team record what they do as they do it. A mistake is corrected, never erased, so the chart shows what was first written and who changed it.
Each dose is marked against the time it was due: given, held or refused, with who and when. A missed dose shows on the ward list.
Fluids in and out through the day, with running totals the doctor reads at the round.
Every admitted patient with what is running for each, so the round starts where the last one stopped. Round times, meal times and nurse shifts are set by the hospital.
Readings for a woman in labour, drawn as a cervicograph with alert and action lines, and closed out at delivery.
Theatres, the day's case list, the surgical safety checklist and the times of each case. The team on each case and the items used, with kits set up per payer, go on the bill when the case closes.
A diet order for each admitted patient, or home food from the family, and a kitchen board by ward and meal. Each meal is marked prepared and delivered, and goes on the bill at the price for the patient's payer. The kitchen sees the bed and the diet, never the diagnosis.
A small hospital often has one person registering, booking and taking money. {{product}} has a role made for that, and every figure on the bill can be traced back to the care that earned it.
Book, move and cancel for any doctor inside their own weekly hours. A new patient is asked about allergies before they are registered. The desk opens a patient's visits, family and bills, never their notes.
Take a deposit at admission, see what it covers, and refund what was not used, whole or in part.
Each item carries its own tax, set up by the hospital and frozen when the bill is issued. The printed bill shows the code, rate and tax per line.
The insurers and schemes you work with, each patient's cover, and a cashless pre-authorisation tracked from request to final approval. Each payer can have its own price list, and a visit or stay is charged at the rate of whoever pays.
Each counter opens and closes its own shift. Every payment gets a receipt number, and the patient gets the receipt as a message.
Money in by day, payment mode, department, category and doctor, with a download for your accountant.
A ten-bed clinic and a multi-speciality hospital run the same software. What changes is what each one switches on and how it is configured, and the hospital decides both.
Start with outpatient care. Add wards, a lab, a pharmacy or billing when you run them, with as many departments and beds as you have.
Bills in your currency, dates and numbers written the way your staff read them, and each hospital on its own clock and week.
One owner, several hospitals. Each keeps its own records, prices and staff; the owner signs in once and sees how every one of them is doing today.
Diagnoses are coded in ICD-10, so records read the same to insurers, auditors and the next doctor.
Wards, rooms and beds laid out the way your building is, and changed when the building does.
Your logo, your colour as the accent, and a choice of typefaces, including ones drawn for easier reading.
Same software either way, licensed to your hospital. Pick the one your policy and your team are comfortable with, and change later if that changes.
Your staff and patients open a web address. We run it, keep it up to date and back it up.
It runs on a server in your building or in your own cloud account, whichever your policy asks for.
When a family, an auditor or a court asks who saw what and when, the answer is already written down.
Every change to a record, with who made it, from where, and what it was before.
Opening a chart is recorded too, not only editing one. The owner can see all of it.
The owner holds the keys and hands out exactly the access each person needs, for as long as they need it. Large discounts and refunds wait for a second approver.
A doctor who works at two hospitals sees each one separately. Records never cross over.
A prescription that clashes with a recorded allergy is stopped before it reaches the pharmacy.
Staff and patients see your hospital's logo and colour, not ours.
Longer answers, with the details, are in the docs. Prices and the estimate are on the pricing page.
Yes. Each hospital sets its own time zone, currency, date format, number format and first day of the week, and diagnoses are coded in ICD-10. Records are stored in universal time, so a group with hospitals in different time zones reads them correctly.
Yes. A clinic can start with the base plan alone, which covers appointments, outpatient care and patient records. A larger hospital adds modules such as emergency, inpatient wards, laboratory, radiology, pharmacy and billing, and sets up as many departments, wards and roles as it runs.
Either. We can host it for you, with updates and backups handled. Or it runs on a server in your building or your own cloud account, as a build licensed to your hospital and covered by the licence agreement.
Yes. Every hospital pays the base plan, then each module has its own monthly price. Modules can be added or removed month to month, and beds are charged separately. Switching a module off keeps the records it made.
Nothing stops for the first 7 days; staff see a notice. After 21 days overdue, new bookings and registrations pause but every clinical workflow and billing continue. After 51 days, the hospital can care for patients already there, bill and read records, but not set up new wards or users. Patient care is never switched off automatically.
No. {{product}} is built to be easy to use. Once your account is open, your own staff can set up departments, wards and beds, roles, and your logo and colour in an afternoon. If you would rather not, our technician does it with you.
Not yet in clinical work. The AI assistant is coming: it will draft summaries and discharge notes for a clinician to review and sign, stay off until the hospital owner turns it on, and be priced separately. It never makes a clinical decision on its own.
Pick the modules you would switch on and set your bed count for a monthly figure. The docs walk through setup, roles, hosting and what happens to your records.