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: 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 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: 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: 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: 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 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: 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: 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: 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 generating a user interface based on messages from a clinical environment is described. A data flow manager (DFM) in the cloud environment may check whether the information in a message received from a connectivity adapter in the clinical environment can be used to generate a user interface (UI). If the information can be used to generate a UI, the DFM may merge the information into the cache. The information merged into the cache can subsequently be used to generate a UI in response to a user request.

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: 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 generating a user interface based on messages from a clinical environment is described. A data flow manager (DFM) in the cloud environment may check whether the information in a message received from a connectivity adapter in the clinical environment can be used to generate a user interface (UI). If the information can be used to generate a UI, the DFM may merge the information into the cache. The information merged into the cache can subsequently be used to generate a UI in response to a user request.

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: 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: 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 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.