Skip to main content
. 2022 May 13;29(7):1286–1291. doi: 10.1093/jamia/ocac064

Figure 1.

Figure 1.

ICU Cockpit platform component diagram. Patient data originate from bedside medical devices installed in ICUs (top left), and via hospital services external to the ICU Cockpit platform (top right). External services such as laboratory analyses and patient metadata from the hospital patient data management system are collected via icuLAB and icuADT. Live bedside webcam video is fed through a separate service (icuCAM) which encodes and optionally blurs the video for patient privacy. The ICU Cockpit Live Environment (ICU Live env) is the central data packaging and distribution module using the icuKafka distributed messaging service. The live stream of any recorded signal and ML algorithm outputs (from icuML) can be visualized in the ICU Cockpit Frontend user interface (UI) (icuUI, bottom left) and stored in the live stream database (icuDB). Patient metadata, admission status, and clinical operations are accessible and edited through the Clinical Data Annotation user interface (icuCDA). Data postprocessing, analysis and algorithm development occur offline by researchers who receive archived and pseudonymized data from the research database (ResearchDB) after authorization. Offline validated algorithms are transferred to the icuML staging environment for integration. Integrated algorithms receive a constant data stream from icuKafka or icuDB, to perform necessary computations and transmit outputs back into the stream to be displayed and/or stored.