Abstract: A system for automatically programming an infusion device is disclosed. An infusion device can be activated to send a first message indicating that the medical device is ready to receive automated programming. A terminal, separate from the infusion device, may be used by a user to request an automated programming message be sent to an unidentified medical device, and the terminal displays the medical device as being ready to receive automated programming. The user may then confirm, using the terminal, that the automated programming message is for the medical device and the system automatically causes, responsive to receiving the confirmation, the automated programming message to be transmitted to the medical device, the automated programming message causing the medical device to be configured according to predetermined operational parameters.

Abstract: An infusion device receives an instruction indicating a total volume to be infused (VTBI) of a fluid for a pumping element to pump through a fluid tube into a patient connector. The infusion device pumps the fluid according to a pumping rate, and causes 2024/102124 an air-in-line sensor to measure an amount of air within the fluid tube according to a sensitivity level. The infusion device determines that a first VTBI threshold has been met, and outputs a notification or reduces the pumping rate. The infusion device determines that second VTBI threshold has been met, and increases the sensitivity level of the air-in-line sensor based on the first and second VTBI thresholds having been met.

Abstract: An infusion device includes a fluid pump and a processor. The processor is configured to receive an automated programming request (APR) from a device manager, where the APR includes an indicated order type. The processor is also configured to determine an implied order type for the APR based in part on whether the fluid pump is active. Additionally, the processor is configured to determine whether the indicated order type is compatible with the implied order type. If the indicated order type is compatible with the implied order type, the processor sends an acknowledgment message to the device manager and programs the fluid pump according to the operating parameters. However, if the indicated order type is incompatible with the implied order type, the processor sends a non-acknowledgment message and an error message to the device manager and rejects the command to automatically program the fluid pump according to the operating parameters.

Abstract: A method for managing patient hydration is provided. The method includes receiving a fluid delivery request that includes a first programmed amount of a first fluid to be provided by a first medical device. Additionally, the method includes identifying a second programmed amount of a second fluid provided by or to be provided by a second medical device. Further, the method includes determining that a medical device operation should be adjusted based on the first and second programmed amounts. Finally, the method includes adjusting the medical device operation responsive to the determination and based on the fluid delivery request and the first and second programmed amounts.

Abstract: A system and method for validating clinical device configurations is disclosed. A test instance of an infusion device is created based on a request, and an automated programming command is transmitted to the test instance. The automated programming command includes validation information for validating clinical order data, and a programming response is generated by the test instance based on the automated programming command, and provided for storage in a records system. In some implementations, the response includes an image, or reference to the image, of a graphical user interface that would be presented by the infusion device configured according to the validation information.

Abstract: An automated asset identification system and method is disclosed. A request to create an identification template is received for a medical device based on a first identifier currently assigned to the medical device and provisioning information obtained from an identification server, and the provisioning information is received based on the request. The identification template is generated based on the first identifier and the provisioning information and, responsive to generating the identification template, a visualization of the identification template is provided to the medical device for display on a display screen of the medical device.

Abstract: An infusion system includes a network data transceiver and a processor configured to determine, at the infusion device, when the infusion device is in a prepared state. In response to determining that, and while, the infusion device is in the prepared state: the processor is configured to present, on a display of the infusion device, a unique identifier of the infusion device, wait for an indication that the unique identifier of the infusion device was scanned by a scanner to associate the infusion device with an infusion order. The processor is configured to receive configuration information associated with the infusion order, and automatically configure the infusion device to cause infusion of a medical fluid specified in the infusion order based on parameters of the infusion order provided by the received configuration information.

Abstract: A system for scanning and validating clinical order device configurations is disclosed. A test instance of an infusion device is created based on a request, and an automated programming command is transmitted to the test instance. The automated programming command includes validation information for validating clinical order data, and a programming response is generated by the test instance based on the automated programming command, and provided for storage in a records system. In some implementations, the response includes an image, or reference to the image, of a graphical user interface that would be presented by the infusion device configured according to the validation information.

Abstract: An infusion system includes a network data transceiver and a processor configured to determine, at the infusion device, when the infusion device is in a prepared state. In response to determining that, and while, the infusion device is in the prepared state: the processor is configured to present, on a display of the infusion device, a unique identifier of the infusion device, wait for an indication that the unique identifier of the infusion device was scanned by a scanner to associate the infusion device with an infusion order. The processor is configured to receive configuration information associated with the infusion order, and automatically configure the infusion device to cause infusion of a medical fluid specified in the infusion order based on parameters of the infusion order provided by the received configuration information.

Abstract: A system for scanning and validating clinical order device configurations is disclosed. A test instance of an infusion device is created based on a request, and an automated programming command is transmitted to the test instance. The automated programming command includes validation information for validating clinical order data, and a programming response is generated by the test instance based on the automated programming command, and provided for storage in a records system. In some implementations, the response includes an image, or reference to the image, of a graphical user interface that would be presented by the infusion device configured according to the validation information.

Abstract: The disclosed systems and methods provide patient care unit (PCU) order confirmation. A method may include authorizing a user to operate a medication delivery device. The method may also include retrieving, in response to the authorizing, a user history associated with the user, wherein the user history includes one or more dispensing records for pending medications. The method may also include determining, based on a context that includes the user history, one or more medication order candidates for present administration. The method may also include presenting a user interface for confirming a medication order from the one or more medication order candidates. The method may also include configuring at least one parameter of the medication delivery device based on the confirmed medication order received from the user interface.

Abstract: A trigger condition for entering a syringe empty mode is determined. The trigger condition includes adjusting an operational parameter of an infusion device associated with the syringe to complete a fluid delivery performed by the syringe. The fluid delivery is monitored and, responsive to the fluid delivery satisfying the trigger condition, the infusion device is caused to enter the syringe empty mode. While in the empty mode, a flow rate or threshold associated with the fluid delivery is adjusted to facilitate emptying a fluid from the syringe, and an alert is provided when the threshold associated with the fluid delivery has been satisfied.

Abstract: The subject technology provides for automatic selection of a disposable medication container during an infusion. A user interface configured to display a selectable list of disposables and configured for receiving a selection of a disposable from the selectable list for use in providing a therapy to a patient by the medical device. When an indication of a selected disposable is received, a first sensor or a motor associated with the medical device is adjusted to provide the therapy to the patient, according to a characterization of the selected disposable. Automated programming data configured to instruct an infusion device regarding an infusion of a medication is received from a server, and includes disposable information, including a selection of the disposable. The selectable list of disposables is then bypassed and not displayed when the automated programming data is received and selects the selected disposable.

Abstract: A method includes receiving a request to activate a medical device. Response to receiving the request, the method includes generating an automatic programming request (APR) for programming the medical device, receiving a message indicating that the APR failed to activate the medical device, and obtaining historical programming records (HPR)s. The method includes determining that parameters in the APR correspond to historical parameters, identifying a set of HPRs including a historical parameter value corresponding to a requested parameter value included the APR, and generating a deviation metric indicating a degree of difference between a secondary parameter value included in the APR and a corresponding historical parameter value. The method includes, responsive to a determination that a deviation metric meets a criticality threshold, changing a drug library record associated with the respective set of deviations and providing an indication to review the changed drug library record.

Abstract: An infusion pump is secured within a lockbox configured to enclose and prevent access to the infusion pump and a medication receptacle of the infusion pump, the lockbox including a lockbox control interface configured to obtain authorization for access to the lockbox from a pump communication interface of the infusion pump and enclosed within the lockbox. The lockbox control interface is electronically coupled with the pump communication interface. Transmission of a wireless credential is made to the pump communication interface by way of being received at the lockbox control interface or at the pump interface through the lockbox. The lockbox control interface receives the authorization from the pump communication interface for access based on the wireless credential and performs an action according to the received authorization for access. Action includes unlocking the lockbox or the lockbox control interface extending the pump's interface to the authorized user.

Abstract: The disclosed systems and methods manage more notifications between medical devices. A method includes obtaining information corresponding to a clinician and determining whether the information satisfies coordination criteria. The method includes, in accordance with a determination that the clinician is associated with the first medical device and a second medical device, detecting a first and second notification generated by respective medical devices. The method includes identifying, based on detecting the respective notifications, alert information including medical information for a patient receiving medical treatment from the first and second medical device. The method includes determining, based on the identified information, notification priorities between the respective notifications.

Abstract: A method for detecting an occlusion in a fluidic channel of an infusion device that includes flowing a fluid within the fluidic channel during a first period of time in which a flow rate of the fluid is set to a first flow rate; pausing, the flow rate for a second period of time; measuring, a first pressure at a location along the fluidic channel during the second period of time; increasing, after measuring the first pressure, the flow rate to a second flow rate; pausing, the flow rate for a fourth period of time; measuring, after pausing the flow rate, a second pressure at the location during the fourth period of time; computing, at a processor, a difference between the first and second pressures; and in accordance with a determination that the magnitude of the difference satisfies the threshold, providing an indication, of a presence of the occlusion.

Abstract: A method includes receiving a request to activate a medical device. Response to receiving the request, the method includes generating an automatic programming request (APR) for programming the medical device, receiving a message indicating that the APR failed to activate the medical device, and obtaining historical programming records (HPR)s. The method includes determining that parameters in the APR correspond to historical parameters, identifying a set of HPRs including a historical parameter value corresponding to a requested parameter value included the APR, and generating a deviation metric indicating a degree of difference between a secondary parameter value included in the APR and a corresponding historical parameter value. The method includes, responsive to a determination that a deviation metric meets a criticality threshold, changing a drug library record associated with the respective set of deviations and providing an indication to review the changed drug library record.

Abstract: The disclosed systems and methods for reducing alarm strain generated by a medical device. A medical device for reducing generated alarm strain includes a display to present visually perceivable information, an audio output to present audibly perceivable information, processors coupled with the display and the audio output, and memory storing instructions that, when executed by the processors, cause the medical device to perform operations. The instructions, when executed, cause the medical device to receive a notification regarding the medical device. The notification is associated with an audible manifestation and a visual manifestation. The instructions, when executed, also cause the medical device to detect that a user is focused on the medical device, after said detection of the user, determine a volume adjustment to the audio output for presenting the audible manifestation, and adjust the audio output to cause presentation of the audible manifestations according to the volume adjustment.

Abstract: When automated programming data configured to instruct an infusion device regarding an infusion of a medication is received from a server, the disclosed system and method identifies a deviation in the data with respect to stored programming data. Without rejecting the data for the deviation, the infusion device instead sends an acknowledgement of the automated programming data and the deviation, and determines a user interface workflow for correcting the deviation. The infusion device then provides for display one or more user prompts according to the determined user interface workflow to resolve the deviation. If the deviation is resolved by way of user responses, then the infusion is activated. Otherwise, an indication is sent to the server regarding the deviation.