Medical device nucleus architecture

A medical software package stored on a non-transitory, computer-readable storage medium, comprising:

• a plurality of software components programmed to provide one or more functionalities to one or more medical monitoring devices;
• wherein each of the plurality of software components is programmed to run independently as a daemon;
• wherein each of the plurality of software components is programmed to be modified without recompiling unchanged software components;
• wherein the plurality of software components is programmed to communicate to each other through at least one of the plurality of software components;
• wherein the medical software package is hardware agnostic and operating system agnostic;
• wherein the plurality of software components further comprise a plurality of reusable assets;
• wherein one of the plurality of reusable assets is a workflow manager programmed to store, add, remove, start, and stop manager programs resident in the non-transitory, computer-readable storage medium;
• wherein one of the plurality of reusable assets is a capability registry programmed to provide a bulletin board system where software components can post common object-oriented architecture messages and receive messages about changes to the posted common object-oriented architecture messages;
• wherein one of the plurality of reusable assets is a message manager programmed to provide an inter-process communications bus for sending common object-oriented architecture messages between the plurality of software components;
• wherein at least one of the posted common object-oriented architecture messages that is sent through the message manager includes a unique identifier and persists on the bulletin board system until another common object-oriented architecture message with the same unique identifier is posted to the bulletin board system;
• wherein one of the plurality of reusable assets is a configuration manager programmed to maintain persistent configuration of the one or more medical monitoring devices and provide a device configuration to a plurality of client software components;
• wherein one of the plurality of reusable assets is a component manager programmed to start up and shut down at least one of the plurality of software components;
• wherein the plurality of reusable assets form a single architecture that includes a set of portable and reusable software items designed to provide a base set of functionality for the one or more medical monitoring devices;
• wherein one of the plurality of reusable assets is a virtual operating system programmed to provide a fixed application programming interface between the single architecture and an underlying operating system;
• wherein one of the plurality of reusable assets is a virtual hardware programmed to provide a fixed application programming interface between the single architecture and underlying hardware and device drivers;
• and
• wherein the single architecture includes the workflow manager, the capability registry, the message manager, the configuration manager, the component manager, the virtual operating system, and the virtual hardware.