Web Mister AI · Product family

Your clinic.One intelligent pulse.

Reception, appointments, medical records, pharmacy, lab, imaging, insurance and billing — one workspace, one patient file, one ledger underneath.

Explore Web Clinic See the platform

The Vital Sign — the Web Clinic product mark

/app/clinicLive clinic dashboard · real product

The Web Clinic executive dashboard showing live clinic indicators, waiting queue, doctor status and revenue analytics

0
clinic screens
0
operating sections
0
accounting core

What is actually in the box

A complete clinic, not a patient list.

Web Clinic ships fifty-four working screens across eleven sections — from the moment a patient walks in to the moment the revenue lands in the general ledger.

Daily clinic

Waiting queue
Triage station
Nursing station
Emergency board
Appointments
Patients & medical files
Encounters (EMR)
Body map

Orders & procedures

Prescriptions & dispensing
Laboratory
Radiology
Procedures
Dental chart
Surgery
Referrals
Consent & SOAP templates

Money

Point of sale
Invoices & collection
Cash shifts
Expenses
Patient receivables
Service packages
Doctor commissions
Payroll

Insurance

Claims lifecycle
Contracts & coverage
Pre-approvals
Insurer receivables
Insurer aging

Stock & reporting

Medicines & supplies
Expiry & shortage alerts
Controlled register
Report centre
No-show report
Procedure profitability
Clinic-scope tax return

The identity

The Vital Sign

One continuous line carries the whole product idea — from a patient who has not been seen yet, to an outcome worth recording.

01
The Baseline
Calm before care — every patient starts somewhere.
02
The Heartbeat
Vitals monitored live — the clinic never blinks.
03
The Heart
The pulse softens into a heart — medicine becoming care.
04
The Glowing Point
Health restored — a bright, healthy outcome.

Platform

An operations surface over a real accounting core.

Most clinic software stops at the clinical record and hands finance a spreadsheet. Web Clinic is built as a clinic-shaped surface on top of one shared ledger — so a visit, an invoice and a journal entry are the same event seen from three sides.

One patient file
Summary, appointments, visits, prescriptions, lab and imaging, invoices, insurance and a full timeline — assembled by a single scoped read, not stitched across modules.
Care becomes an invoice
Closing an encounter bills it. The resulting sales document opens in the same workspace, and posts to the ledger without a second entry.
Scoped to the clinic
Every read is guarded and scoped to the clinic product. Shared accounting screens open inside the clinic shell — never a jump into another product's data.
Roles that hold
Permissions are enforced twice: a server guard before any data loads, and a database guard on every write. Hiding a menu item is not a permission model.

Patients

A complete view of every patient.

The registry is a working CRM, not a directory. Search by name, file number, mobile or national ID; filter by status, gender and insurance; sort and page through the whole panel. Opening a patient opens their entire history.

The file has tabs, not tables
Summary, appointments, visits, prescriptions, lab and imaging, invoices, insurance and a chronological timeline — one record per patient.
Duplicates caught at registration
Registering a new patient runs a duplicate check before the record is created.
Chronic follow-up and immunisations
Dedicated recall screens track chronic-disease follow-up and the immunisation record separately from ad-hoc visits.

/app/clinic/patients

Live panel indicators — active, new this month, outstanding balance

Search by name, file, mobile or national ID

Every row opens the full patient file

Appointments

Turn every appointment into a connected workflow.

A daily operations centre with list, day-timeline and week views. Booking detects doctor and room conflicts before it writes, warns on same-day duplicates, and hands straight over to the encounter.

Conflicts caught before booking
The booking dialog checks the doctor's and the room's calendar, and flags a second appointment for the same patient on the same day.
Appointment to encounter
Starting a visit from an appointment opens the clinical encounter already bound to that patient and doctor.
The queue is a board
Reception runs a drag-and-drop patient-flow board with live counters and auto-refresh — arrival, triage, in exam, done.

/app/clinic/appointments

List · day timeline · week

Quick actions on every appointment card

Clinical records

The patient story, structured around the visit.

The encounter is the unit of clinical work. Chief complaint and vitals open it; procedures, prescriptions, lab and imaging orders hang off it; closing it bills it. Opening a record writes an audit entry automatically.

Orders belong to the encounter
Lab and radiology orders are created against an open encounter, and results return to the same record.
Reading a record is logged
Encounter detail loads through a guarded call that writes a view-encounter audit entry — access is evidence, not assumption.
Beyond notes
Body map, dental chart, surgery board, referrals, medical documents, informed-consent templates and SOAP note templates are all first-class screens.

/app/clinic/encounters

Open encounters with chief complaint

Procedures, prescriptions and orders in the record

Pharmacy · Lab · Imaging

Orders that know your stock.

Prescribing, dispensing, lab work and imaging run inside the same tenant as your inventory — so a prescription can be checked against what is actually on the shelf, and dispensing moves real stock.

Dispensing decrements inventory
Dispensing a prescription draws from the pharmacy warehouse and reduces stock — it is a stock movement, not a note.
Expiry and shortage alerts
Dedicated screens surface items expiring soon and items below reorder level, plus a controlled-substances register.
Lab and imaging worklists
Orders and results for laboratory and radiology are tracked as worklists with status, not as free text in a note.

/app/clinic/pharmacy · /lab · /radiology

Insurance

The claim, from approval to settlement.

Insurance is a full sub-system: contracts with coverage rates, medical pre-approvals, the claim lifecycle, insurer receivables and an aging view with payments — not a checkbox on the invoice.

Contracts drive coverage
Coverage rates live on the insurance contract, so what the patient pays and what the insurer owes are derived, not typed.
Aging by insurer
Receivables are bucketed per insurance company with claim counts and totals, so slow payers are visible.
Pre-approvals tracked
Medical pre-approval requests are managed on their own screen and carried into the claim.

/app/clinic/claims

Billing & operations

From care to payment, then to the ledger.

Point of sale for reception and pharmacy, invoices and returns, receipt and payment vouchers, cash shifts with their own reports, expenses, patient receivables and deposits — all posting into the same accounting core the clinic already runs on.

Shifts close properly
Cash sessions are opened, reconciled and reported — the till is part of the accounting system, not a drawer.
Staff cost is clinic cost
Doctor commissions, payroll, loans, deductions, attendance and leave all live in the clinic, with commission calculable on billing or on collection.
Packages and price lists
Services carry prices and groups; packages bundle them for sale.

/app/clinic/pos · /shifts · /commissions

Insights

Understand how the clinic is performing.

The executive dashboard reads once and shows everything: today against the period, the waiting queue, which doctors are busy, revenue by doctor, department and service, payment mix, claim status and stock alerts — filtered by day, week, month, six months, year, or all time.

Reports that answer questions
No-show report, procedure profitability, pharmacy report, refunds register and a clinic-scope tax return — beside trial balance, income statement, balance sheet and cash flow.
Operational, not vanity
Average wait time, rooms occupied, open encounters, pending prescriptions, open lab and imaging orders — the numbers a clinic manager acts on.

/app/clinic/reports · /report-center

Clinical intelligence

Intelligence where it actually matters.

Web Clinic does not sprinkle a chat box over a database. Two engines run at the two moments where a mistake is expensive — writing a prescription, and filling a schedule. Both are deterministic: they need no external AI provider and no API key, so no clinical data leaves the system to produce them.

The prescription safety net

One check the moment a prescription is written: patient allergies, duplicate drugs, what is genuinely on hand in your pharmacy, controlled-substance rules, and whether the quantity is plausible for the dose and duration.

A clinic system does not know your stock; a pharmacy system does not know your patient. Owning both in one tenant makes the check immediate rather than an integration.

A check whose data was not supplied is reported as not performed — never as passed.

No-show aware scheduling

Estimates the probability that each appointment is missed, using the clinic's own history — hour, weekday, lead time, service type and the patient's record — then recommends a calculated overbooking level.

An empty chair is a silent loss that appears in no report. The recommendation balances lost revenue against the wait time that annoys patients.

Factors below a minimum sample are excluded and declared. Without enough history the answer is “unknown”, not “0%”.

Operations the assistant can actually run

Clinic actions are registered operations backed by database procedures, scoped so the assistant can only reach what the clinic owns.

Book an appointment
Books a patient with a doctor at a given time.
Start an encounter
Opens a visit for a patient with a doctor, accepting chief complaint and vitals.
Order labs
Creates a laboratory order linked to an open encounter.
Order imaging
Creates a radiology order linked to an open encounter.
Dispense a prescription
Dispenses from the pharmacy warehouse and reduces stock.

Both engines produce recommendations and alerts for a clinician — never an automatic clinical decision.

/app/clinic/reports/no-show

Architecture

Access you can prove.

Permissions are structural, not cosmetic.

Guarded twice
A server-side guard runs before any data is loaded, mirroring a database-level guard on every write. Typing the URL directly does not get you in.
Scoped reads
Clinic data is read through security-definer procedures gated on clinic product access, under row-level security.
Multi-tenant by construction
Every read is bound to the organisation. The clinic never sees another tenant's records — or another product's.
Clinical access is logged
Opening an encounter writes an audit entry as part of the read itself.

Described from the product's own access-control implementation. No compliance certification is claimed.

Part of the Web Mister AI family

One core. Many verticals.

Web Clinic is one product in the Web Mister AI family. Each vertical is a real operating surface over the same accounting core — the clinic shares its ledger, inventory and reporting engine with the rest of the platform, which is exactly why a dispensed prescription can move stock and post revenue in one action.

Web ClinicAccountingPharmacyRestaurantSalonHotelSchoolHuman resources

Products listed are verticals present in the platform. Web Clinic is the product described on this page.

Get started

See it running on your clinic's day.

The fastest way to judge Web Clinic is to walk one patient through it — arrival, triage, encounter, prescription, invoice, claim.

Explore the platform

Request a demo

Your clinic.One intelligent pulse.