Critical care softwarethat keeps the whole unit in view

It is a critical care information system, also called a patient data management system, for hospital intensive care units. It covers the unit board and capacity, a clinical workspace for every bed, continuous vitals and device data, early warning scores, orders and protocol bundles, documentation, signed handover and unit-level alerting.

A general record documents encounters. Intensive care produces data at a different density: vitals every few seconds, minute-level flowsheets, device alarms and unit operations. The ICU Module is built for that. Its interface is organised by bed and its data model by patient, and every clinical view draws from one timeline per patient.

Either. Attending and allergy context comes from the Doctor Module, staffing from the Nurse Module and released results from the Laboratory Module when they are installed. Without them it reads and writes FHIR R4 resources, accepts HL7 v2 admissions and results, and takes device telemetry through a vendor-neutral gateway.

Yes. Device data comes in through a telemetry gateway that is not tied to any one monitor vendor. A monitor that goes quiet is marked disconnected after two minutes and raises a clinical alert after ten, so a silent drop-off at a bed is never mistaken for a stable patient.

NEWS2, qSOFA, MEWS and Shock Index, computed from the monitored vitals by a deterministic rules engine rather than a model. Every input is traceable. A governed hourly NEWS2 sweep raises an alert and a nursing task when a patient reaches the trigger. Assessment-based scores that need a nursing or neurological examination are not computed by the module.

Every vitals entry is evaluated against the clinical rules. A critical alert has to be acknowledged before it can be resolved, and one that nobody answers climbs on a timer: the charge nurse at ten minutes, the intensivist at thirty, the medical director at sixty. The chain is configuration, not code, so a unit can set its own.

Yes. Twelve specialty configuration packs, from adult medical and surgical units through trauma, neuro, burns, paediatric and neonatal to high dependency, step-down and isolation, adapt the workspace, documentation templates, order sets and score sets per unit. One platform, configured per specialty rather than forked.

The bed workspace has a handoff mode that gathers what the next clinician needs beside the SBAR draft: pending results, unreported imaging, scheduled medicines and open tasks. The outgoing clinician signs it and the incoming one acknowledges it, so nothing is handed over from memory.

The AI advises and the clinician decides. It never submits a clinical order, and it reaches patient data only through governed tools with their own access checks. A number that does not appear in the retrieved evidence causes the answer to be rejected rather than shown. Every recommendation carries its confidence and evidence, and each one is accepted, rejected or overridden by a person, with the decision recorded.

The team looking after that bed. Anyone else has to break the glass with a stated reason. That access is time-limited, visible on screen while it lasts, and reviewed afterwards by someone other than the person who used it. Access is never blocked in an emergency, and accountability is never bypassed.

No. The audit log is append-only and the database itself refuses updates and deletes to it. Controlled medicines, blood products and ventilator changes need a second person to witness them, and nobody can witness their own action.

The ICU Module is in beta, and pricing is announced at general availability. Units join the beta with onboarding and close support from the team, and help shape the product before it is priced. It will be sold on three editions: Standard for the unit board, bed workspace, device streaming and protocols, Premium for clinician-supervised AI, and Enterprise for autonomous surveillance, digital twins and multi-site coverage. Beta access is arranged through the form on this page.