Get started
OperationsLive · in the productQueue & board

CommandView

The whole hospital on one live board: beds, theatres, bottlenecks.

Get CommandViewOpen the appAvailable nowHow pricing works →

What it is

The command centre over engines that already know: beds and admissions from WardLine and BedBoard, theatre states from TheatreFlow, the emergency department from TriageLine, early warnings, lab work still pending and ambulances on the way — one live view of where the hospital is stuck, refreshed from sources, copied from none. For a polyclinic, Doctors today shows every doctor’s room (where their tokens were last called), the patients they have seen and have with them, and what was collected today on their lines, shared across each bill pro rata by the same per-line attribution doctors’ shares use — read only; a count or a collection is changed in the app that owns it.

Who uses it
Built for: Every specialty
Reads
Live states from source apps, today’s encounters, tokens and payments
Writes
Bottleneck flags
Never
It does not hold its own state — a board that copies rows can disagree with its sources; a view cannot (the InboxOne rule).
Access
Only people whose role includes it — the clinic owner decides who
Your data
PHI-lite. Hosted in Boston, United States. On uninstall: Every record stays; only the workflow leaves.

In the product

Who uses it
Operations manager — the demo profile it is best tried as
Where it opens
Operations › Command Board /command
Permission
board.read
Every operations app in the handbook →

How it works

  1. Read the wallOperations board draws one tile per panel with the time and timezone it was read; beds, the emergency queue, theatres, ambulances, critical results and deterioration each come from the app that owns the fact, computed on every refresh; a polyclinic’s Doctors today tile lists each doctor’s room, patients seen and today’s collection.
  2. A panel that cannot be read says soEvery panel runs in its own transaction, so one missing source cannot take the other tiles down; that tile shows a dash and names the source it could not read, and the header counts how many would not answer this refresh.
  3. Read the bottlenecksEach entry carries the number that justifies it and the basis it was derived from, and the list is computed from every panel including the ones this hospital has hidden — hiding a panel does not hide the pressure it would have shown.
  4. Say what counts as pressureTighten and Relax move the thresholds this hospital calls pressure; the card says what they do — they change what the bottleneck list ranks, never what the panels measured.

Rules it keeps

What it does not do, by design. A listing with only benefits is an advertisement.

It does not hold its own state — a board that copies rows can disagree with its sources; a view cannot (the InboxOne rule).

AI in CommandView

AskQuestions about what is on screen — “What needs attention in CommandView today?” — answered with the records it read.
DraftSummaries and notes for the team, marked as drafts until a person signs.
Every answer shows its sources. Nothing AI writes is saved until a person accepts it.

See it on screen

Live product
01Command Board — The whole hospital on one live boardCaptured from the running demo clinic
CommandView — Command Board — The whole hospital on one live board
1 of 1

Connected to

Read out of the code, not the brochure: each app below is here because one service queries the other’s tables. Install either side and the hand-over is already wired.

See the whole clinic →

Questions clinics ask

What does CommandView do?
The whole hospital on one live board: beds, theatres, bottlenecks. The command centre over engines that already know: beds and admissions from WardLine and BedBoard, theatre states from TheatreFlow, the emergency department from TriageLine, early warnings, lab work still pending and ambulances on the way — one live view of where the hospital is stuck, refreshed from sources, copied from none. For a polyclinic, Doctors today shows every doctor’s room (where their tokens were last called), the patients they have seen and have with them, and what was collected today on their lines, shared across each bill pro rata by the same per-line attribution doctors’ shares use — read only; a count or a collection is changed in the app that owns it.
What data does CommandView read and write?
CommandView reads live states from source apps, today’s encounters, tokens and payments and writes bottleneck flags. Its data class is PHI-lite. Every app works on the same patient record — nothing is copied into a silo.
What does CommandView deliberately not do?
It does not hold its own state — a board that copies rows can disagree with its sources; a view cannot (the InboxOne rule).
What happens to our data if we uninstall CommandView?
Every record stays; only the workflow leaves.
Is CommandView available today?
Yes — CommandView is live in clinics today. Set up your practice on MedAppz and install it from your dashboard.

Want to see CommandView running on your own patients?

Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.

We use your name, phone number and clinic name for one thing: to answer this enquiry about MedAppz. It is stored on our own server, in the single region our trust centre names, and it is not sold or passed to anyone else.

Email us

You can withdraw either at any time: write to hello@medappz.com, or tell whoever calls you, and we will delete what you gave us.

More in Operations

All 97 →