A command center that extends the same live patient model to remote intensivists. One worklist across the entire network. Live device data and full documentation power for every bed at every facility. Built on the same unified clinical record as the Clinician Assistant — so a patient's data moves between bedside and command center without translation, batching, or loss.
* The Joint Commission, Sentinel Event Alert 58: Inadequate Hand-off Communication (2017) — communication failures are associated with up to 80% of serious medical errors.
For Virtual Care to work, the remote intensivist needs to see what the bedside team sees — at the same fidelity, in the same moment. That requires more than a remote view of the EHR. It requires the same unified clinical record that the Clinician Assistant maintains at the bedside, extended to the command center. Every reading and the assessment of it together. One record, not two.
No batching. No translation. No reconciliation between command center notes and the bedside EHR. The bedside team and the command center are working from the same unified record — and the patient's data moves between them in real time.
A record is what was captured. A model is what's running now. DocBox maintains the unified record as a live patient model — the running representation of the patient that persists across time, travels with the patient through transfers and across connected sites, and supplies the same operational signal to the bedside, the command center, and everything downstream.
The hospital network owns the model. Downstream systems are consumers of it — not owners of it. That separation is what keeps DocBox vendor-neutral and what keeps the data ready for the next clinical AI use that hasn't been built yet.
The Clinician Assistant runs at the bedside. Virtual Care runs at the command center. Both are built on the same connected foundation — five architectural principles that determine how device data and documentation enter, relate, persist, and stay neutral across vendors and across sites.
Most existing Virtual Care offerings are layered on top of separate vendor stacks — proprietary hubs, isolated worklists, and reconciliation work between the command center and the bedside EHR. DocBox Virtual Care runs on the same unified clinical record and live patient model as the Clinician Assistant — so there's no parallel data world for the remote intensivist to maintain.
| Traditional Virtual Care (Philips eICU, Hicuity, etc.) | EHR-bolted remote view (Epic, Cerner remote) | DocBox Virtual Care | |
|---|---|---|---|
| Data source | Separate stack — proprietary hub, isolated database | Lagging EHR snapshots | The same live patient model the bedside team uses |
| Worklist | Vendor-locked, fixed views | Designed for retrospective review, not live oversight | Open-standards worklist — configurable by unit and specialty |
| Remote documentation | Separate notes that need to reconcile back to the EHR later | Limited or read-only remote access | Bidirectional remote documentation — validated and unvalidated states preserved |
| Integration cost | Significant — device interfaces, EHR bridges, training stack | Adds latency and reconciliation overhead | Already integrated — same foundation as the bedside product |
| Network expansion | Each new site is a new integration project | Inherits the EHR's site-by-site constraints | Each new site joins the network through the same connected foundation |
DocBox Virtual Care does not replace your monitors, your EHR, or the rest of your hospital infrastructure — it sits on the same unified record the Clinician Assistant uses at the bedside, and extends it to the command center.
An open-standards worklist that puts every patient in the network on one screen — live vitals, location, acuity, active orders. Validated and unvalidated data states preserved side by side. Configurable by unit and specialty. The remote intensivist sees the same single pane of glass as the bedside team, with the same documentation power.
One Virtual Care hub can extend specialist coverage across an entire network — academic, community, and rural facilities simultaneously. The same live patient model that runs at the bedside is what the command center sees. Network expansion compounds: every new site adds data, analytic depth, and leverage on every existing intensivist.
When a patient moves between sites, the live patient model moves with them. Transfer-readiness, current device state, last assessment, active care plan — the receiving team sees the full model before the patient arrives. The handoff becomes a confirmation rather than a reconstruction. Communication failures during care transitions are associated with up to 80% of serious medical errors (The Joint Commission); the model-based handoff is built to remove that gap at the source.
For the full scenario: the post-craniotomy transfer use case →
Virtual Care lives in the command center. The Clinician Assistant lives in the room where the patient is — combining device data and clinical documentation into the unified record that Virtual Care then extends to remote intensivists. Either can be deployed first; both can be deployed together.
See the Clinician Assistant →Virtual Care inherits every integration the Clinician Assistant has built over 18 years — bedside devices, hospital systems, downstream programs — and extends them across the network.
Virtual Care runs across multiple facilities, often spanning regulatory environments. DocBox is built for that posture from the ground up — and built around the principle that the hospital network owns its data, not us.
Full HIPAA technical safeguards, audit logging, role-based access controls, and breach-notification posture — extended across the network.
AES-256 at rest, TLS 1.2+ in transit. Bedside-to-command-center traffic is encrypted end-to-end across every connected site.
On-premises, hospital-hosted cloud, or hybrid. Per-site policy supported. Each facility's data stays where its compliance posture requires.