Product guide
The whole system, screen by screen — 41 screenshots across 9 areas, captured from the live product. What each module does, and the engineering underneath it.
Every screenshot below is the real product UI — captured from a live CareIT HMS instance seeded with realistic sample data. No mockups, no concepts; names and figures are sample data, never real patients.
Watch it, read it, keep it
Watch the narrated walkthrough, scroll the screens below, or take the illustrated PDF with you.
CareIT HMS User Guide — PDF edition
51 pages, A4 · every module illustrated with the real UI, step by step · 11 MB
01 · Overview
Where every shift starts: a role-aware home and a notification stream that carries pointers, never PHI.
/dashboard
The landing screen for every role. Quick actions jump straight into the flows your permissions allow; the access panel shows exactly which roles and permissions you hold.
/notifications
The in-app notification inbox behind the header bell. Critical results, critical findings, and published rosters land here for everyone with authority to act.
02 · Front desk & scheduling
The flows that set the tone for the whole visit: finding the right chart, booking, and an honest queue.
/patients
The master patient index. Debounced search by name, MRN, or phone; keyboard-first (press / to search); merged duplicates stay visible with a badge so history is never hidden.
/patients/register
A four-step wizard — identity, contact, identifiers, review. Before anything is saved, the MPI checks for likely duplicates and makes you resolve them, so duplicate charts are caught at the door.
/patients/{patient}
One patient, one page. The identity banner — name, age, MRN, active allergies — is the same banner pinned to every clinical screen. Tabs cover demographics, allergies, encounters, documents, and billing.
/appointments
The clinic day at a glance, always in the facility’s own timezone. Each row advertises exactly the actions its state allows — confirm, mark arrived, start consultation, complete, cancel, no-show.
/queue
Walk-in queue tickets with call-next at the counter. Ordering is emergency → urgent → routine, then arrival — mirroring the server’s ordering exactly, so an emergency never waits behind a stack of routine tickets.
03 · Clinical care
From the consult room to the ward to the ICU — one append-only record, with the safety engineering visible.
/encounters/{encounter}
The 90-second consult workspace. Notes, vitals, diagnoses, orders, and prescriptions on one screen — no navigation mid-consult. Out-of-range vitals flag automatically the moment they are recorded.
/emergency
A board that triages. Unassessed arrivals pin to the top — an unknown in an ED is high risk until someone looks — then acuity 1→5, then longest wait. Never arrival order.
/ward
The bed board: wards, rooms, and beds with occupancy at a glance — who is where, and which beds are free to admit into.
/admissions
Every inpatient stay from admission to discharge. Discharge is deliberately two-step — discharge-pending can go back to admitted, because the second reviewer’s job is to be able to say no.
/admissions/{admission}
The electronic medication administration record. Scheduled doses per prescription, recorded as given, refused, or held — a refused dose never sits as “still due”. Dose times are typed by the ward exactly as prescribed; “TID” is shown verbatim, never guessed into clock times by a parser.
/icu
Intensive care stays with flowsheets, devices, and severity scores. Flowsheet entries can be corrected — the correction supersedes and the original stays visible, struck through.
/theatre
The surgical day: cases per theatre, block bookings that are actually enforced, and a case pipeline gated by the surgical safety checklist — a case cannot start until sign-in is recorded.
/maternity
Pregnancy episodes from antenatal visits through delivery and postpartum. Mother and newborn stay distinct patients linked by the delivery — the newborn gets their own MRN and chart.
04 · Specialties
Purpose-built clinical suites that write into the same record as everything else.
/dental/{patient}
A clickable FDI odontogram painted by each tooth’s current condition. Click a tooth to record a finding; corrections supersede the old finding and bump the chart version.
/optometry
Eye exams with per-eye acuity and pressure, and optical prescriptions with sign-once discipline: a signed prescription can only be superseded, never edited — two “current” prescriptions is how the wrong lenses get ground.
/vaccination/{patient}
Dose administration against real vaccine lots in stock, with dose-interval rules enforced (“too soon” is refused), adverse events (AEFI) recorded inline, and certificates anyone can verify by code.
/telemedicine
Remote consult sessions scheduled from real appointments. Consent gates the camera — no recorded consent, no session start — and join tokens are minted per participant, shown exactly once.
05 · Diagnostics & medication
Stat-first worklists, verify-then-release results, and dispensing with guardrails.
/orders
The diagnostic worklist, ordered stat → urgent → routine → longest-waiting, rendered exactly as the server sends it. Collection, result entry, verification, and release each advertise themselves only when legal.
/critical-results
The escalation queue for critical lab values. Everyone with acknowledge authority is notified; unacknowledged criticals escalate again on a deadline. A cleared queue — like this one — means every critical was answered.
/radiology
Imaging from accepted order to signed report: schedule, arrive, acquire (with PACS system, UID, and link metadata), then report. A study is final only when a radiologist signs — not when the scanner ran.
/pharmacy
Signed prescriptions land here oldest-first — the order the counter works them. Validation (with recorded alert overrides) comes before dispensing; controlled drugs demand a witness.
06 · Care coordination
Longer-running care, secure staff messaging, and the patient-facing surfaces.
/treatment-plans
Goal-driven care plans: goals, assignable activities with due times, progress notes, and formal reviews. A revise review bumps the plan version; a discontinue review ends it — with notes required either way.
/messages
Care-team threads with append-only discipline: a wrong message is redacted — leaving a visible tombstone with the reason — never silently deleted. Legal hold freezes a conversation; redaction is refused while a hold stands.
/portal-admin
Staff-side control of the patient portal: invite accounts, manage proxy access (a parent for a child), record consents, and set release rules for results. A critical result never auto-releases, whatever the rule says.
/mobile-devices
Registered mobile devices and the offline sync queue. Vitals captured offline apply through the same interpreter as bedside entry; anything that can’t apply surfaces as a conflict with its reason — accepted-and-dropped doesn’t exist here.
07 · Billing & finance
Charges are facts; invoices are presentations. Every screen downstream of that principle.
/invoices
All invoices with their real states. Every invoice is raised from charges captured at the point of care — a draft owes nothing until finalized, and its balance says so.
/invoices/{invoice}
One invoice, fully accounted: lines traced to captured charges, discounts with their approval trail, totals, and payments. Discounts enforce separation of duties — the requester can never be the approver.
/cashier
Shift-based cash management. Open a shift with a float, post payments against invoices, and reconcile at close — counted cash against cash takings only. Card and e-wallet takings are reported separately, so a variance actually means something.
/claims
Payer claims built from real charges: pick the policy, pick the claimable charges, validate, submit, and adjudicate line by line. A charge already on one claim can never be billed to a payer twice.
/accounting
Balanced journal batches exported to your general ledger, with two-person approval, transmission tracking, and acknowledgements. Exported batches are immutable — corrections happen as reversal batches, debits and credits swapped.
08 · Operations
Stock, people, numbers, and the health of the system itself.
/inventory
What is on the shelf, what is running low, and what is expiring — computed with the same availability rules dispensing uses, so the board and the dispenser can never disagree.
/inventory/purchase-orders
Procurement with a paper trail: suppliers, purchase orders with line items, two-person approval (the raiser cannot approve), and receiving that demands lot and expiry per line.
/workforce
Rosters, leave, attendance, and credentials in one board. Publishing a roster runs the minimum-staffing gate — a ward that would fall below its nurse floor refuses to publish, out loud.
/reports
Pre-aggregated nightly snapshots charted per metric — visits, collections, occupancy — plus queued exports that run in the background and deliver through expiring signed links.
/analytics
The analytics hub: versioned metric definitions, patient cohorts, and an async job queue. Cohorts enforce a k-anonymity floor at definition time — small groups can’t leak into a spreadsheet.
/system-health
Operational health for administrators: checks with latest samples, incidents with acknowledgement, maintenance windows (planned downtime pages nobody), and backup runs with restore tests that require evidence.
09 · Settings & governance
Licensing, the audit trail, and account security — the screens your IT director will ask for first.
/settings/modules
The module registry — all 29 modules with their tiers and dependencies. Toggles double as licensing: enable what your facility licenses, and the registry refuses combinations whose dependencies are off, verbatim.
/settings/audit
The hash-chained, append-only audit trail: privileged actions and PHI reads with actor, entity, IP, and before/after diffs. PHI-touching entries are tagged. This is the screen that answers “who saw what, when”.
/settings/security
Per-account security: enroll an authenticator app (TOTP), receive one-time recovery codes shown exactly once, and disable only with re-authentication.
A live walkthrough beats screenshots — we’ll run your facility’s journey through the real system.
