- Problem
- Operational numbers are assembled by hand from departmental systems.
- What answers it
- Live views for wards, theatre, purchasing, blood bank, collections and campaigns, running on the work the departments just did.
- Outcome
- The same figure appears in the department’s own register and in the management view, because it is the same work.
Solutions
The same platform, read from where you sit
A hospital system is bought by one team and lived with by nine. Each section states the problem as that team describes it, what answers it, and what changes operationally — not a claimed percentage, because we have no basis for one.
For hospital leadership
Hospital leadership
You are asked what happened yesterday across a hospital that runs on several systems. The answer usually arrives as a spreadsheet, a week late, and disagrees with another spreadsheet.
- Problem
- Revenue leaks between the department that did the work and the bill.
- What answers it
- Charges are raised where the work is ordered and land in one account, with a state on every line and a close before discharge.
- Outcome
- Unbilled and unchecked work is visible as a state, not discovered at month end.
- Problem
- Growth means another hospital, another system, another reconciliation.
- What answers it
- Several hospitals are served by one platform, with their own users, roles, numbering and documents.
- Outcome
- A new unit is opened as a setup exercise rather than as a second system.
For doctors
Doctors
The record you need is usually somewhere — in another department, on paper, or in a system you do not have open.
- Problem
- History, results and medication live in different places.
- What answers it
- A patient folder carrying the timeline, problem list, allergies and earlier encounters, reachable from any clinical screen.
- Outcome
- The consultation starts from what is known about the patient, not from a blank page.
- Problem
- Ordering means leaving the note and finding the patient again.
- What answers it
- Investigation and medication ordering inside the consultation, priced and queued to the department that will fulfil it.
- Outcome
- One pass through the screen produces the note, the order and the charge.
- Problem
- Documentation forms never quite match the speciality.
- What answers it
- Forms defined in the application by the departments that use them, with their own rules, surfaced on the right encounter.
- Outcome
- Departments get the form they actually use, without waiting for a software release.
For nursing
Nursing
Ward work is coordination: which bed, which order, which drug, which meal, which handover.
- Problem
- Bed state is on a whiteboard and out of date by the afternoon.
- What answers it
- A ward board with live occupancy, and every move recorded.
- Outcome
- Admission, transfer and discharge decisions run off one current picture.
- Problem
- Orders arrive verbally and are written down again.
- What answers it
- Doctor orders and the nursing response on the same admission, with administration recorded against the order.
- Outcome
- What was ordered, what was given and who gave it are one chain rather than three records.
- Problem
- Observations, care plans and notes are on separate paper.
- What answers it
- Observations, care plan, notes, allergies and diet in the same patient workspace.
- Outcome
- The handover is the record, rather than a summary of it.
For pharmacy
Pharmacy
Two jobs at once: a clinical one and a supply chain one, usually on two different systems.
- Problem
- Prescriptions arrive on paper and are typed in again to dispense.
- What answers it
- A queue of orders from the clinics and wards, supplied against the right store and batch.
- Outcome
- The order, the supply, the stock movement and the charge are one action.
- Problem
- Clinical pharmacy work is real but unrecorded.
- What answers it
- Pharmacist review, medication reconciliation, counselling, ward rounds, adverse reactions and stewardship, all captured.
- Outcome
- Interventions are recorded and reportable rather than informal.
- Problem
- Expiry, recall and controlled drugs need registers that survive an inspection.
- What answers it
- Expiry and recall handling, cold-chain logs, controlled drug registers and compliance reporting.
- Outcome
- The register is a by-product of the day rather than a reconstruction before an audit.
For laboratory
Laboratory
Most laboratory disputes are custody disputes: where the sample went, and when.
- Problem
- Samples move between collection points and laboratories without a record.
- What answers it
- Collection, rejection with a reason, dispatch, receipt and reconciliation at every hand-off.
- Outcome
- Any sample can be placed in time and in someone’s hands.
- Problem
- Result formats differ per investigation and end up as free text.
- What answers it
- Templates with structured fields per investigation, plus capture of outsourced reports.
- Outcome
- Results stay structured and comparable across visits.
- Problem
- The clinician never sees the result land.
- What answers it
- Authorised results publish to the chart that raised the order, with outstanding orders visible on the clinical boards.
- Outcome
- Chasing results stops being a phone call.
For finance & billing
Finance & billing
The month-end question is always the same: why does the bill not agree with the claim?
- Problem
- Discounts and price exceptions are applied inconsistently at the counter.
- What answers it
- Price lists that are proposed, approved and versioned, with discount policies and per-role limits.
- Outcome
- Every charged price can be explained, including what it was on the day it was charged.
- Problem
- Payer share, co-pay and packages are reconciled in a spreadsheet.
- What answers it
- Patient and payer share held on every charge, with packages, pre-approval and corporate cover on the admission.
- Outcome
- The split is worked out once, and the claim is generated from it.
- Problem
- Receivables ageing is a manual exercise.
- What answers it
- Invoices raised from closed bills, payments allocated back to source bills, with ageing and payment reporting.
- Outcome
- Outstanding balances are traceable to the bills they came from.
For operations & administration
Operations & administration
Clinical work stops when the logistics stop: no bed, no stock, no vehicle, no sterile set.
- Problem
- Purchasing is approved over email and reconstructed afterwards.
- What answers it
- Requests, orders, receipts, requisitions, adjustments and write-offs, each with its own approval.
- Outcome
- Every commitment has a documented approver.
- Problem
- Sterile supply, transport and dietary services sit outside the system.
- What answers it
- Sterile supply batches, transport requests and fleet records, dietary planning and service queues.
- Outcome
- Support services are requested, approved and costed like any other hospital service.
- Problem
- Opening a department means a development request.
- What answers it
- Departments, roles, services, prices, numbering, documents and menus are all maintained in the application.
- Outcome
- Operational change is setup work with a record of who changed what.
For hospital it
Hospital IT
You inherit whatever the vendor built. The question is how much of the next five years needs the vendor.
- Problem
- Every change request becomes a release.
- What answers it
- Screens, menus, roles, forms, documents, numbering and appearance are all settings.
- Outcome
- Routine change is administration rather than deployment.
- Problem
- Permissions are enforced by hiding buttons.
- What answers it
- What a role can open is set per hospital, and what may be done there is granted separately and enforced by the platform.
- Outcome
- Access control does not depend on the interface behaving.
- Problem
- A second hospital means a second everything.
- What answers it
- One platform serving every unit, with per-hospital users, roles, numbering and documents.
- Outcome
- One system to run, keep current and back up.
For quality & compliance
Quality & compliance
An audit asks who did what, when, and on whose authority. Most systems answer the first half.
- Problem
- Changes to money and stock are untraceable after the fact.
- What answers it
- Who created and who last changed a record is kept throughout, and changes to prices, cover, discounts and bill closure leave their own record.
- Outcome
- A change can be attributed to a person and a moment.
- Problem
- Approvals happen outside the system.
- What answers it
- Raise-and-approve queues across purchasing, refunds, prices, adjustments and transport.
- Outcome
- The approver is part of the record, not a memory.
- Problem
- Clinical safety registers are assembled before an inspection.
- What answers it
- Theatre checklists and infection follow-up, transfusion and look-back registers, adverse reaction and controlled drug registers, cold-chain logs.
- Outcome
- The register exists because the work was done in the system.
Bring the team that will actually use it
The demo that decides a hospital system is the one where the ward sister, the pharmacist and the finance controller are all in the room asking about their own day.