The Critical Care OSfor intensive care that never stands still
A cloud-native critical care information system: one live command centre for the unit, one workspace per bed, vendor-neutral device integration, continuous early-warning scores, and AI that advises while the clinician decides.
The Command Center
One unit. One picture. Always current.
The Command Center is the operational nucleus of the ICU: every bed, every device, every open alert on a continuous whiteboard that updates in real time. The interface is bed-centric; the data model is patient-centric.
Continuous whiteboard
Every bed on one live board: Grid, List, Wall and Map display modes, with display profiles for shared wall screens.
Capacity & readiness
Bed readiness lifecycle, unit capacity and admission/transfer/discharge coordination in one view.
Live event feed
Sub-second updates pushed to the board over a real-time channel. No refresh, no polling.
Staffing awareness
Live staffing panels, with nurse ratios and skill mix federated from the Nurse Module where installed.
Emergency operations mode
When an untriaged emergency is active, non-essential panels step aside and the unit sees what matters.
Device awareness
Connected-device status across the unit, so silent monitor drop-offs never go unnoticed.
The Bed Workspace
Everything about one patient, in one workspace
Open a bed and the entire clinical picture is there: eighteen domains rendered from a single canonical micro-timeline, from rounds and vitals to orders, imaging and family communication.
Vitals & hemodynamics
Standard vitals and advanced ICU parameters (CVP, cardiac output, ICP and pressure lines) resolved live from device twins with streaming telemetry.
Deterministic early-warning scores
NEWS2, qSOFA, MEWS and Shock Index computed continuously from monitored vitals by a pure rules engine. No black box.
Deterioration alerts
A clinical rules engine evaluates every vitals entry; critical lab values auto-raise alerts with an acknowledge-and-resolve lifecycle.
Unified ICU CPOE
One order entry surface with a searchable catalog and ~24 protocol order sets (sepsis bundle, ARDS, DKA, massive transfusion and more) activating as signed orders.
Structured handover
SBAR nursing and physician-coverage handovers: drafted from the record, signed by the outgoing clinician, acknowledged by the incoming one.
Code Blue & crisis mode
One action escalates acuity, raises a critical alert and opens a resuscitation timeline with rapid vitals entry.
Governed documentation
Template runtime with a flowsheet time-grid, durable drafts, notes history and co-signature workflows.
Protocols with compliance
Activate protocol bundles per patient and track task completion percentage against the protocol.
ICU micro-timeline
One canonical event timeline per patient (15 minutes to full admission) that every clinical view renders from.
Early Warning
Scores that compute themselves
A deterministic scoring engine turns monitored vitals into continuous early-warning scores: pure rules, no black box, every input traceable.
Computed live from monitored vitals
Computed live from monitored vitals
Computed live from monitored vitals
Computed live from monitored vitals
Deterioration that announces itself
Every vitals entry runs through the clinical rules engine. Critical lab values raise alerts automatically, alarms are prioritized in the Alarm Center, and new critical alerts are announced to assistive technology.
Waveform-rate data, handled properly
High-frequency telemetry streams into time-series storage built for physiologic data: hypertables with columnar compression on a dedicated path, so trend queries stay fast while the unit stays live.
Specialty ICUs
Twelve ICUs. One platform. Zero forks.
Specialty configuration packs re-skin the workspace per unit: widgets, documentation templates, order sets and score sets. Transfer a patient from the CICU to Step-Down and the workspace follows. Burn units get an interactive TBSA rule-of-nines map with a Parkland calculator.
Clinical Intelligence
AI advises. The clinician decides.
Every recommendation carries confidence, supporting evidence and generation time. Nothing is a black box, and AI never submits autonomous clinical orders. Available on Premium and Enterprise tiers.
Silent Watchman
Autonomous surveillance that produces evidence-backed clinical recommendations with confidence levels, every one accepted, rejected or overridden by a human. Enterprise tier.
Ask - evidence-grounded
Questions answered by structured retrieval over the chart, rules and telemetry; no number appears in an answer unless it exists in the evidence. Premium tier.
Morning brief & clinical summaries
AI-drafted rounding briefs and plain-language family updates, always reviewed and released by a clinician. Premium tier.
Clinical agent fleet
Risk-tiered agents for surveillance, order assistance and family communication. Each shows its model, prompt version and evidence provenance. Enterprise tier.
Voice documentation
In-browser dictation straight into note drafts; audio never leaves the device. Premium tier.
Governed autonomy
An org-level autonomy policy gates what AI may produce, and an AI-model governance lifecycle (register → validate → approve → deploy → retire) controls what runs.
Tele-ICU
Cover every unit from one cockpit
The Tele-ICU Cockpit triages every occupied bed across your units into a single prioritized worklist (critical alerts first, then acuity) with live vitals, open alerts and one-click remote chart review. Built for the command-centre model of remote critical care coverage.
- Cross-unit prioritized worklist, ordered by alerts and acuity
- Live vitals and open alerts per bed, at a glance
- One-click remote chart review into the full Bed Workspace
Also in the platform
- Clinical workflows: governed logic executing live, every decision explainable, with auditable step trails.
- Builder toolkit: author rules, order sets, templates and dashboards as governed configurations, no code required.
- Analytics: clinical and operational KPIs, bed-occupancy heat maps and threshold-based operational alerts.
- Family portal: clinician-released daily summaries, visit scheduling and consent management, with information governance built in.
Interoperability
A modern CIS without the monitor lock-in
Legacy critical care systems come welded to one vendor's hardware estate. Eruntar speaks the open standards, and treats every device gateway as a first-class citizen.
FHIR R4
Patient, Encounter, Device, Observation and ImagingStudy resources: inbound writes, transaction bundles, and outbound pull via SMART Backend Services.
HL7 v2
Inbound ADT admits, updates and discharges plus ORU results, acknowledged with standard ACKs.
Vendor-neutral device gateway
High-frequency telemetry ingest from monitor and ventilator gateways over an API-key-scoped endpoint. No hardware lock-in.
PACS & laboratory
Imaging study lists with deep links into your enterprise PACS viewer; released labs federate in from the Lab Module.
Signed webhooks
HMAC-signed outbound events to surrounding systems, with automatic disable on repeated failure.
Eruntar ecosystem
Attending and allergy context from the Doctor Module, staffing from the Nurse Module, results from the Lab Module: one patient record across modules.
Security & Governance
Zero Trust in operation
Every identity verified, every denial visible, every emergency access reviewed. Designed to support HIPAA, GDPR, ISO 27001 and SOC 2 requirements, with live compliance introspection mapping in-force controls to each framework.
Immutable audit
An append-only audit log (user, workstation, before/after, reason) enforced immutable at the database level.
Break-glass access
Time-boxed emergency elevation with a stated reason, supervisor fan-out and a visible banner. Access is never blocked; accountability is never bypassed.
Electronic witnessing
Independent second-user co-signature for controlled medicines, blood products and ventilator changes, with separation of duties enforced.
Encryption & isolation
Field-level AES-256-GCM encryption at rest, TLS in transit, and row-level multi-tenant isolation in the database.
Zero-Trust access
Capability-based RBAC with context-aware checks and role-adaptive navigation that fails closed.
Privacy screen
One tap masks PHI on shared unit displays without leaving the workflow.
Engineering
Built like infrastructure, because it is
Real-time by architecture
Live board updates are pushed, not polled, verified across multiple nodes with a Redis backplane.
Built for physiologic data
Time-series telemetry lands in TimescaleDB hypertables with columnar compression, so waveform-rate data never contends with clinical writes.
Offline-aware
The command centre keeps the last synced board through network loss, queues changes and shows the reconciliation backlog.
Wall displays & touch
Display profiles for wall screens, a touch density mode for bedside carts, and a PWA install path for tablets.
Accessible by default
Font scaling, contrast and reduced-motion modes, colour-vision-deficiency support and screen-reader alert announcements.
Observable in production
OpenTelemetry traces and metrics, PHI-safe structured logs, health probes and real-user performance beacons.
Frequently Asked Questions
What is a critical care information system (CIS)?
A critical care information system, also called a patient data management system (PDMS), is software that manages the intensive care unit's clinical workflow: bed and unit management, continuous vitals and device data, orders, medications, documentation, scoring and handover. Eruntar's ICU Module is a cloud-native CIS.
What is the difference between a PDMS and a general EMR?
A general EMR documents encounters; a PDMS is built for the data density of intensive care: continuous device telemetry, minute-level flowsheets, early-warning scores, alarms and unit-level operations. Eruntar's ICU Module is bed-centric in its interface and patient-centric in its data model.
Does the ICU Module integrate with patient monitors and ventilators?
Yes. Device data flows in through a vendor-neutral telemetry gateway API and each device is represented as a digital twin with live state, telemetry snapshots and an alarm lifecycle, without locking you into one monitor vendor's ecosystem.
Which early-warning scores does it calculate?
NEWS2, qSOFA, MEWS and Shock Index are computed continuously from monitored vitals by a deterministic rules engine. Assessment-based scores such as SOFA and APACHE II have dedicated surfaces in the specialty packs and activate as their nursing and neuro assessment inputs ship.
Does it support different ICU types like NICU, PICU or cardiac ICU?
Yes. Twelve specialty configuration packs (including MICU, CICU, SICU, Trauma, Neuro, Burn, PICU, NICU, HDU, Step-Down and Isolation) adapt widgets, documentation templates, order sets and score sets per unit. One platform, configured per specialty, not forked.
What is the ICU Command Center?
The Command Center is the unit's home screen: a continuous whiteboard of every bed with Grid, List, Wall and Map modes, capacity and staffing panels, a live event feed, device awareness and an emergency operations mode.
How does the ICU Module handle shift handover?
Handover is structured: an SBAR nursing or physician-coverage draft is prepared from the live record, reviewed and signed by the outgoing clinician, and electronically acknowledged by the incoming one, so nothing is handed over from memory.
Does it include tele-ICU capability?
Yes. The Tele-ICU Cockpit triages every occupied bed across units into one prioritized worklist with live vitals, open alerts and one-click remote chart review, designed for command-centre style remote coverage.
Is the AI safe for clinical use?
The module's stance is explicit: AI advises; the clinician decides. AI never submits autonomous clinical orders. Every recommendation carries confidence, evidence and provenance, autonomy is governed by an org-level policy, and each suggestion is accepted, rejected or overridden by a human, with an immutable audit trail.
Does the ICU Module support FHIR and HL7?
Yes. FHIR R4 read and write surfaces (including transaction bundles and SMART Backend Services pull) and HL7 v2 inbound ADT and ORU results are supported, alongside signed outbound webhooks.
How is patient data protected?
Field-level AES-256-GCM encryption at rest, TLS in transit, row-level multi-tenant isolation, capability-based access control, break-glass emergency access with review, and a database-enforced immutable audit log. The platform is designed to support HIPAA, GDPR, ISO 27001 and SOC 2 requirements.
Does it work when the network drops?
The command centre is offline-aware: it keeps the last synced board visible, queues changes locally and shows a reconciliation backlog until connectivity returns.
Can it run on wall displays and tablets?
Yes. Wall display modes and read-only display profiles cover shared unit screens, a touch density mode suits bedside carts, and the app installs as a PWA on tablets.
How is the ICU Module priced?
The ICU Module is currently in beta, and pricing will be announced at general availability. Beta access, including onboarding and close support from the team, is arranged through our contact page.
Is the ICU Module available today?
Yes, as a beta. Intensive care units can join the beta program to run Eruntar with close support and help shape the product before general availability.
Run Your ICU on Eruntar
The ICU Module is in beta. Pricing will be announced at general availability. Beta partners get early access, onboarding and go-live support, and a direct line to the team building it.