The doctor's day, and the AI consultation inside it.
One doctor's own view, carried across every establishment they practise at. Their patients, their queue, the consultation, the prescription, the ward round, the discharge narrative and their own earnings statement. Where Dock answers 'what is happening in this hospital', Medico answers 'what is waiting for me'.
Who uses it: The clinician — doctor, AYUSH practitioner, and the nurse at the bedside
What is on the screen today.
Every line below is a screen that exists, grouped as the module groups it. The count comes from the same build register the published status page reads.
17 of 17 serving today CBS Medico is 100% complete against its own screen list. The whole of it, screen by screen with the testing protocol, is in the user guide.
Everyday
- Home -- today's work Today's work, over one aggregate read
- My patients The clinician's own list, distinct from the desk view
The consultation
- Consult, prescribe, save Prescribing and interaction checks, written against a real encounter record
- Patient timeline One patient's record as a single ordered stream, with the filter chips served from the API
- Prescription print Prints with the prescriber's registration and the interactions caught at prescribing. Printed from Medico
My work
- Reviews queue The review queue, over its own endpoint
- Ward round notes Read and write, per admission
- Discharge authoring The narrative is written at discharge, and DK-18 reads it back and amends it afterwards
- My follow-ups Due, overdue and summary, on a screen. It is the facility's list, not mine -- the endpoints carry no attending clinician
- Alerts BE-6 — no per-user alert queue endpoint
Everyday
- Clinical Buddy Mounted and role-guarded on all three routers — asking the assistant a clinical question is separated from curating what it knows
- Messages -- in- and out-patient Threads, participants, priority, offline queue
More
- Reports Reports, with saved views and a server-side export
- My earnings A doctor's own statement, scoped by the token rather than by a parameter, so one consultant cannot open another's
- Institution A clinician's read-only view of the facility profile
- Settings Notification preferences, on a settings screen of their own
- Help Answers all three modes. The top-bar help icon used to 404 on every Dock and Care page
Getting in
- Sign in Shared with DK-28
No configuration of Medico lets a model write to a record, message a patient or close a follow-up. Every AI statement is labelled, cited and logged, and a clinician accepts, changes or rejects it before it becomes part of the record.
True of Medico, and of no other module
- A consultant sees their own earnings and cannot open another's — the statement is scoped by the signed-in token, not by a parameter in the address bar.
- Every AI suggestion is labelled, cited and logged, and none of it acts on its own. A clinician remains in the loop for anything that reaches a patient.
One record underneath, four doors onto it.
A patient registered at the front desk in Dock is the same patient the clinician opens in Medico, the same record the family reads in Care, and the same patient the pharmacy serves at Counter. No module holds its own copy.
The hospital management system: registration, beds, theatre, billing, the laboratory, the store, the roster and the audit trail — everything that belongs to the establishment rather than to one clinician or one patient.
FeaturesThe patient's own door: appointments, medicines, the reports and bills the hospital has released to them, the people looking after them, and the check-in, fall and SOS from the device at home.
FeaturesThe dispensary — medicines, surgicals and other consumables: the sale, dispensing against a prescription, stock in and out, expiry, the credit book, the day book and the statutory registers a drug inspector asks for.
FeaturesSee CBS Medico against your own way of working.
Thirty minutes, your own case, and an honest answer about whether it fits the way your establishment already runs.