Abstract: A set of software programs runs in a parallel configuration on local hospital servers. The software gathers all the data directed to it from a hospital patient's data sources (including, but not limited to, data formats from patient monitor devices, HL7 feeds, and other hospital data systems). Data can be time-synchronized, transformed, and routed from both currently networked device and non-networked devices. The data is made available for redisplay and analysis to system users and program agents.

Abstract: A set of applications can access a specific patient's real-time or historical physiological data from a clinical care unit and calculate new disease specific physiological indicators or be a virtual physiological monitor for that patient. The applications are run on a remote server and push the resulting data to an endpoint device.

Abstract: A patient alarm application provides a way for allowing clinical personnel to monitor and control patient-specific alarm settings. A user interface allows clinical personnel to compare graphical representations of unit population vital signs data with patient-specific vital signs data as well timelines of alarms for the patient. Analysis of the alarm data allows the user interface to show clinical personnel the estimated effects of changes to alarm threshold settings.

Abstract: A patient alarm application provides a way for allowing clinical personnel to monitor and control patient-specific alarm settings. A user interface allows clinical personnel to compare graphical representations of unit population vital signs data with patient-specific vital signs data as well timelines of alarms for the patient. Analysis of the alarm data allows the user interface to show clinical personnel the estimated effects of changes to alarm threshold settings.

Abstract: A patient alarm application provides a way for allowing clinical personnel to monitor and control patient-specific alarm settings. A user interface allows clinical personnel to compare graphical representations of unit population vital signs data with patient-specific vital signs data as well timelines of alarms for the patient. Analysis of the alarm data allows the user interface to show clinical personnel the estimated effects of changes to alarm threshold settings.

Abstract: The Alarm Management System allows hospitals and critical care units to manage alarms generated by patient monitors and includes the following components: The Alarm Dashboard provides a display of alarm history and trends categorized as desired by hospital administrators. The Alarm Criticality Discernment Tool assists in distinguishing between critical and non-critical alarms. This Tool can allow a clinician to accommodate patient-specific or doctor-specific rules, alarm thresholds, or exceptions. The Alarm Renderer Tool provides physiological data for a predetermined period before the alarm and upon receiving a patient alarm, allows the alarm and the physiological data displayed visually to be forwarded to a care provider to assist in the determination of the criticality of the alarm. The Alarm Router Tool is a set of rules and editor for routing and escalating unacknowledged alarms to other care providers and recording these events.

Abstract: A patient alarm application provides a way for allowing clinical personnel to monitor and control patient-specific alarm settings. A user interface allows clinical personnel to compare graphical representations of unit population vital signs data with patient-specific vital signs data as well timelines of alarms for the patient. Analysis of the alarm data allows the user interface to show clinical personnel the estimated effects of changes to alarm threshold settings.

Abstract: A set of applications can access a specific patient's real-time or historical physiological data from a clinical care unit and calculate new disease specific physiological indicators or be a virtual physiological monitor for that patient. The applications are run on a remote server and push the resulting data to an endpoint device.

Abstract: The Alarm Management System allows hospitals and critical care units to manage alarms generated by patient monitors and includes the following components: The Alarm Dashboard provides a display of alarm history and trends categorized as desired by hospital administrators. The Alarm Criticality Discernment Tool assists in distinguishing between critical and non-critical alarms. This Tool can allow a clinician to accommodate patient-specific or doctor-specific rules, alarm thresholds, or exceptions. The Alarm Renderer Tool provides physiological data for a predetermined period before the alarm and upon receiving a patient alarm, allows the alarm and the physiological data displayed visually to be forwarded to a care provider to assist in the determination of the criticality of the alarm. The Alarm Router Tool is a set of rules and editor for routing and escalating unacknowledged alarms to other care providers and recording these events.

Abstract: A set of software programs runs in a parallel configuration on local hospital servers. The software gathers all the data directed to it from a hospital patient's data sources (including, but not limited to, data formats from patient monitor devices, HL7 feeds, and other hospital data systems). Data can be time-synchronized, transformed, and routed from both currently networked device and non-networked devices. The data is made available for redisplay and analysis to system users and program agents.