Programming With Interoperability-Subsequent Primary Infusion (Pump Module) - CareFusion Alaris 8015 User Manual

Programming with Interoperability—Subsequent Primary Infusion (Pump
Hospital policy should determine the preferred method for
programming subsequent infusions.
Subsequent infusion for the Pump module refers to new bags,
syringes, or containers used with the Pump module.
An automated programming request for a matching
subsequent infusion can be sent to a Pump module that is
infusing, paused, delayed, or alarming (including Infusion
Complete - KVO).
Pre-populating an active Pump module is allowed if all of the
following infusion parameters match between the subsequent
infusion automated programming request and the running
infusion:
• Drug or Fluid name (alias or NDC)
• Drug Amount (not applicable for fluids)
• Drug Amount units (not applicable for fluids)
• Diluent Volume (not applicable for fluids)
• Dosing units (not applicable for fluids)
• Patient Weight/BSA (if used)
NOTE:
If the infusion that is running on the Pump module is a custom
concentration, the Drug Amount and Diluent Volume still must
match between the incoming subsequent infusion automated
programming request and the running infusion.
The pre-population of infusion parameters workflow for
subsequent bags is unchanged from the initial bag; scan
patient, scan medication label, scan Alaris Pump module, see
Programming with Interoperability—Initial Primary Infusion on
page 2-62. The infusion parameters for the subsequent bag
must meet the required matching criteria. If the matching
criteria are met, the infusion parameters are pre-populated on
the PC unit without interruption of the currently running
infusion.
Programming with Interoperability and Guardrails Suite MX
2-72
Module)
Alaris System User Manual – with v9.33 Model 8015
FU
RATE (mL/h)
CHANNEL
SELECT
PAUSE
CHANNEL
OFF
RESTART
Pump and Syringe Modules Section