Pump integration means that the BD Alaris infusion pump system and Epic have a bi-directional connection enabling data to be sent back and forth. This interface allows for the orders in Epic to automatically program the pumps and for changes made at the pumps to be sent directly to the patient’s record in Epic. This workflow should prevent some errors which have occurred due to manual entry and improve intake documentation for infusions.

Resources

Primary Resources

• BD Alaris Pump/Infusion Verify Frequently Asked Questions - (Handout) Nursing subject matter experts from UIHC answer common questions regarding BD Alaris Pump Integration and the Infusion Verify activity.
• Epic and Alaris Pump Integration Trifold - (Handout) The basic steps for the pump integration workflows are provided.
• Start Primary and Secondary Infusion (ALAR001) - (eLearning: 10 min) Starting a primary and a secondary IV infusion and associating the Alaris pump to Epic using the integrated workflow.
• Associate/Disassociate a Running Infusion (ALAR003) - (eLearning: 10 min) Associating and disassociating a running infusion upon transfer and reviewing pumps in the Patient Lists workspace.
• Starting a Syringe Infusion (ALAR004) - (eLearning: 5 min) Starting a syringe infusion as a primary and associating the Alaris pump to Epic using the integrated workflow.
• Here’s How . . . Infusion Verify (POSS174) - (eLearning: 2.5 min) Get an overview of the Infusion Verify activity, where nurses verify rate and volume documentation for a patient’s infusions, all from one place.
• Validate Infusion Data in Infusion Verify - (Handout) Use Infusion Verify to validate infusion data for your patients’ infusions. In Infusion Verify, you can review volumes and file them to flowsheets while simultaneously filing actions to the MAR as needed.

Other Resources

• Alaris Pump Integration in Rover - (Handout) Pump integration is the process by which Alaris infusion pumps are associated to medication orders within Epic. This document offers step by step instructions for starting a primary and secondary IV infusions in Rover.  
• Starting a Primary - (Handout) With integration this process involves scanning the patient, medication, and pump. The nurse selects the pump as primary, completes the administration details, then sends them to program the pump.
• Starting a Primary (Syringe Pump) - (Handout) Process involves scanning the patient, syringe medication, and pump. The nurse selects the pump as primary, completes the administration details, then sends them to program the pump.
• Starting a Secondary - (Handout) Process involves scanning the patient, medication, and pump. The nurse selects the pump as secondary, completes the administration details, then sends them to program the pump.
• Documenting IV Volume Intakes - (Handout) Nurses should document intake volumes for infusions after ensuring that appropriate changes have been validated. This is most often done when validating the stopping of an infusion, clearing pumps, ending a shift, or transferring a patient.
• Disassociating a Pump - (Handout) Disassociating a medication from a pump must be done upon sending a patient with a running infusion to areas that do not require an ADT event in Epic (for instance when sending to MRI or CT).
• Association of a Running Infusion (with prior MAR Documentation) - (Handout) A pump may be associated when a patient already has an IV infusion running and has prior MAR documentation.
• Association of a Running Infusion (without prior MAR Documentation) - (Handout) A pump may be associated when a patient already has an IV infusion running without prior MAR documentation.
• Subsequent Bag Presentation - (PDF) The changes to the subsequent bag infusion workflows are outlined including fluid, continuous, and intermittent.

Return to Epic Resources