Abstract: A distributed system can include a server outside of a clinical environment and a connectivity adapter and a plurality of infusion pumps within the clinical environment. The connectivity adapter can monitor microservices that measure the quality of connectivity adapter's performance. If the performance is below a threshold level, a message indicating poor performance can be sent to the server. The message can be sent when a prior message relating to poor performance has not already been sent within a predetermined time period.

Abstract: A distributed system can include a server outside of a clinical environment and a connectivity adapter and a plurality of infusion pumps within the clinical environment. The connectivity adapter can monitor microservices that measure the quality of connectivity adapter's performance. If the performance is below a threshold level, a message indicating poor performance can be sent to the server. The message can be sent when a prior message relating to poor performance has not already been sent within a predetermined time period.

Abstract: Various techniques for facilitating communication with and across a clinical environment and a cloud environment are described. For example, a method for authenticating a network device residing in the clinical environment using a token is described. An authentication proxy in the cloud environment can receive a request from a connectivity adapter in the clinical environment and retrieve a security token from an authentication system in the cloud. The connectivity adapter can use the security token to send signed requests to the authentication system.

Abstract: Various techniques for facilitating communication with and across a clinical environment and a cloud environment are described. For example, a method for tagging messages with facility identifiers in a manner that does not require changing the identifiers when logically re-arranging the facilities. A connectivity adapter in the clinical environment can receive a message from an infusion pump and tag the message with only permanent IDs such that when the facility in which the connectivity resides is categorized under a different system or region, the identifiers in the message need not be updated.

Abstract: A distributed system can include a server outside of a clinical environment and a connectivity adapter and a plurality of infusion pumps within the clinical environment. The connectivity adapter can receive from the server a location of an update, such as a drug library update or an operational software update, to be delivered to the infusion pumps. The location can be received over a first messaging communication channel of a network, and the update data can be received over a second, data communication channel of the network. The update data can be stored at the connectivity adapter such that it can be sent to the infusion pumps.

Abstract: Various techniques for facilitating communication with and across a clinical environment and a cloud environment are described. For example, a method for converting infusion pump messages having one format into standardized dataset messages having another format is described. When a connectivity adapter in the clinical environment detects a new pump protocol, the connectivity adapter may generate a message converter that can convert pump messages into standardized dataset messages. The message converter can be used to convert pump messages into standardized dataset messages. The standardized dataset messages may include information additional data or metadata not included in the pump messages.

Abstract: Various techniques for facilitating communication with and across a clinical environment and a cloud environment are described. For example, a method for tagging messages with facility identifiers in a manner that does not require changing the identifiers when logically re-arranging the facilities. A connectivity adapter in the clinical environment can receive a message from an infusion pump and tag the message with only permanent IDs such that when the facility in which the connectivity resides is categorized under a different system or region, the identifiers in the message need not be updated.

Abstract: A distributed system can include a server outside of a clinical environment and a connectivity adapter and a plurality of infusion pumps within the clinical environment. The connectivity adapter can monitor microservices that measure the quality of connectivity adapter's performance. If the performance is below a threshold level, a message indicating poor performance can be sent to the server. The message can be sent when a prior message relating to poor performance has not already been sent within a predetermined time period.

Abstract: A system can include a plurality of infusion pumps and a connectivity adapter in a clinical environment. The connectivity adapter can receive update data, such as a drug library update or an operational software update, and can store the update data within the clinical environment. The connectivity adapter can send the update data to a predetermined number of infusion pumps that have requested the update. At least two subsets of the infusion pumps can receive different blocks of the update data at about the same time. Further, the same or different update data can be provided to the infusion pumps at about the same time.

Abstract: Various techniques for facilitating communication with and across a clinical environment and a cloud environment are described. For example, a method for authenticating a network device residing in the clinical environment using a token is described. An authentication proxy in the cloud environment can receive a request from a connectivity adapter in the clinical environment and retrieve a security token from an authentication system in the cloud. The connectivity adapter can use the security token to send signed requests to the authentication system.

Abstract: A distributed system can include a server outside of a clinical environment and a connectivity adapter and a plurality of infusion pumps within the clinical environment. The connectivity adapter can monitor microservices that measure the quality of connectivity adapter's performance. If the performance is below a threshold level, a message indicating poor performance can be sent to the server. The message can be sent when a prior message relating to poor performance has not already been sent within a predetermined time period.

Abstract: Systems and methods for dynamically and intelligently estimating analyte data from a continuous analyte sensor, including receiving a data stream, selecting one of a plurality of algorithms, and employing the selected algorithm to estimate analyte values. Additional data processing includes evaluating the selected estimative algorithms, analyzing a variation of the estimated analyte values based on statistical, clinical, or physiological parameters, comparing the estimated analyte values with corresponding measure analyte values, and providing output to a user. Estimation can be used to compensate for time lag, match sensor data with corresponding reference data, warn of upcoming clinical risk, replace erroneous sensor data signals, and provide more timely analyte information encourage proactive behavior and preempt clinical risk.

Abstract: Various techniques for facilitating communication with and across a clinical environment and a cloud environment are described. For example, a method for tagging messages with facility identifiers in a manner that does not require changing the identifiers when logically re-arranging the facilities. A connectivity adapter in the clinical environment can receive a message from an infusion pump and tag the message with only permanent IDs such that when the facility in which the connectivity resides is categorized under a different system or region, the identifiers in the message need not be updated.

Abstract: Various techniques for facilitating communication with and across a clinical environment and a cloud environment are described. For example, a method for providing messaging in a clinical environment during a network outage is described. During a network outage, messages in the queue may become stale. A connectivity adapter may remove those messages from the queue. When the network connection is restored, the connectivity adapter may transmit any remaining messages in the queue.

Abstract: Various techniques for facilitating communication with and across a clinical environment and a cloud environment are described. For example, a method for providing messaging in a clinical environment during a temporary network interruption is described. A connectivity adapter may keep the messages in the queue despite the temporary network interruption. As long as the network connection is restored before the messages become stale, the connectivity adapter may be able to transmit the messages in the queue despite the network interruption.

Abstract: Systems and methods for dynamically and intelligently estimating analyte data from a continuous analyte sensor, including receiving a data stream, selecting one of a plurality of algorithms, and employing the selected algorithm to estimate analyte values. Additional data processing includes evaluating the selected estimative algorithms, analyzing a variation of the estimated analyte values based on statistical, clinical, or physiological parameters, comparing the estimated analyte values with corresponding measure analyte values, and providing output to a user. Estimation can be used to compensate for time lag, match sensor data with corresponding reference data, warn of upcoming clinical risk, replace erroneous sensor data signals, and provide more timely analyte information encourage proactive behavior and preempt clinical risk.

Abstract: An infusion pump is configured to execute one or more alarm actions according to an alarm protocol. An alarm manager of the infusion pump is configured to receive alarm configuration comprising one or more alarm protocols, each protocol comprising one or more alarm parameters. The alarm manager is also configured to determine the presence of an alarm condition and perform an action associated with the one or more alarm parameters in response to determining the presence of the error condition.

Abstract: Various techniques for facilitating communication with and across a clinical environment and a cloud environment are described. For example, a method for detecting missing messages from a clinical environment is described. A data flow manager (DFM) in the cloud environment may check the message ID of each message received from a connectivity adapter in the clinical environment. If the DFM detects a skip in the message IDs, the DFM may request the missing messages from the connectivity adapter.

Abstract: Various techniques for facilitating communication with and across a clinical environment and a cloud environment are described. For example, a method for authenticating a network device residing in the clinical environment using a token is described. An authentication proxy in the cloud environment can receive a request from a connectivity adapter in the clinical environment and retrieve a security token from an authentication system in the cloud. The connectivity adapter can use the security token to send signed requests to the authentication system.

Abstract: A drug library management system generates versions of drug library data that can be used by infusion pumps, and version of drug library data that can be used by systems or components in a clinical environment other than infusion pumps. One version of the drug library data may be customized for a particular infusion pump, while another version may be a generalized version that can be used by middleware systems that process messages received from various infusion pumps that are using a different version of the drug library data. The generalized version may be archived separately from a drug library database used by the drug library management system to generate the various versions.