Procurement teams comparing volumetric infusion pumps should anchor the evaluation in documented performance methods rather than marketing summaries. The FDA recognizes AAMI TIR101:2021 as a complete standard for fluid delivery performance testing across syringe, container, and volumetric pumps, including enteral, PCA, and epidural modes [1]. That standard defines test methods but deliberately does not set clinical acceptability criteria or address measurement uncertainty [2]. A comparison therefore requires procurement staff to define their own thresholds for accuracy, alarm timing, and usability, then request evidence that maps to those thresholds. The most frequently reported infusion pump problems include software error messages, human factors issues, broken components, battery failure, alarm failure, and over- or under-infusion [4]. A procurement process that treats these failure categories as explicit decision points is more likely to surface meaningful differences between devices than one organized around feature lists alone.

Start with the recognized performance standard

AAMI TIR101:2021 provides fluid delivery performance test methods intended to cover the full range of use conditions and produce clinically relevant data on how a pump will perform in use [1]. The standard applies to volumetric infusion pumps for all indicated delivery modes and prescribed infusate sources, including a volumetric pump drawing from a syringe [3]. Because the document does not establish criteria for clinical acceptability, procurement teams cannot simply ask whether a pump passed TIR101 testing. They must specify which use conditions matter for their patient populations and what deviation from commanded flow is tolerable at low, intermediate, and high rates.

The FDA recognition record lists the standard under regulation 21 CFR 880.5725 for infusion pumps, including Class 2 product codes for general infusion, enteral, elastomeric, and insulin pumps, as well as accessories and infusion safety management software [1]. This regulatory mapping means a comparison should verify that the manufacturer's performance data covers the specific product code and intended route under evaluation. A pump cleared for one route or population does not automatically carry equivalent evidence for another. Procurement staff should request the test conditions, infusate properties, and device sample size behind any accuracy claim rather than accepting a single percentage figure without context.

Define accuracy, alarm, and hazard detection thresholds

The alternate controller enabled infusion pump regulation illustrates the level of specificity FDA expects for delivery accuracy and hazard detection. Testing must demonstrate that the device meets design input requirements under reasonably foreseeable conditions, including ambient temperature changes, pressure changes such as head-height and backpressure, and different drug fluidic properties [6]. Results must cover the programmable range of delivery rates and volumes using a statistically valid number of devices to account for variation between units [6]. A procurement comparison should ask whether submitted data reflect worst-case conditions or only nominal laboratory settings.

Hazard detection validation must show that the pump can detect relevant events such as occlusions or air in line within a clinically relevant timeframe across the programmable range of rates and volumes [6]. For occlusion alarms, documentation should include the specification for the longest time that may elapse before an alarm triggers under each delivery condition, along with typical results observed during performance testing [6]. These requirements give procurement teams a concrete checklist: request the longest alarm delay, not just the average, and confirm that testing covered the lowest and highest rates the facility will use.

A suggested evaluation workflow for a two-pump comparison

A procurement team could structure a comparison between two volumetric pumps in five steps. First, request AAMI TIR101:2021 test reports and record the stated accuracy at 0.1, 1, 10, 100, and 999 mL/hr, along with the test infusate and sample size [1]. Second, request the longest occlusion alarm delay at the lowest and highest programmed rates, not just the average [6]. Third, run a task-based usability evaluation with at least two clinician groups using the facility's own drug library scenarios, since published HFE procurement studies rarely include enough context to transfer [8]. Fourth, compare drug library configuration limits such as clinical care areas and medications per CCA against the facility's formulary structure [5]. Fifth, verify wireless quality of service requirements and EHR integration scope against the facility's network and software environment [6]. This workflow is a suggestion for organizing evidence requests; it does not establish clinical acceptability thresholds, which AAMI TIR101:2021 explicitly leaves to the user [2].

Use human factors evidence as a procurement filter

A 2025 review in Frontiers in Digital Health examined published studies using human factors and ergonomics evaluations to support purchasing decisions within infusion pump bidding processes [8]. The search retrieved 233 articles, and only five studies described an HFE analysis of infusion pumps supporting selection [8]. Those five studies were published between 2005 and 2019 and were conducted in Canada, the United States, and Hong Kong [8]. The studies differed in pump type, covering standard volumetric and smart pumps, analgesia pumps, and epidural pumps, and evaluated between two and four brands [8].

The review found that detailed information about procurement, including budget, timing, evaluation experts' profiles, and technical pump requirements, is lacking in all five publications, and only one indicates the number of pumps being acquired [8]. This evidence gap matters for procurement teams because it means published usability comparisons rarely provide enough context to transfer findings to another hospital. A facility should therefore run its own task-based usability evaluation with representative clinicians and its own drug library scenarios. The absence of published procurement detail is a reason to demand more documentation from vendors, not a reason to skip usability testing.

Build a side-by-side comparison around documented specifications

A manufacturer comparison guide for large volume pumps shows how vendor documents can support a structured evaluation when read critically. ICU Medical's comparison chart for the Plum 360, Plum Solo, and Plum Duo lists flow rate accuracy as plus or minus 10 percent for 0.1 to 0.9 mL/hr and plus or minus 5 percent for 1 to 999 mL/hr on the Plum 360, while the Plum Solo and Plum Duo are listed at plus or minus 3 percent for 0.1 to 999 mL/hr [5]. The chart also lists bolus rate ranges, drug library search, distal occlusion auto reset, secondary delivery independent of IV container head height, and prioritized alarms [5].

These vendor claims should be treated as starting points for verification, not as independent evidence. The comparison chart does not state the test conditions, infusate properties, or sample sizes behind the accuracy figures. Procurement teams should ask ICU Medical for the underlying test reports and confirm whether the stated accuracy covers the full range of use conditions described in AAMI TIR101:2021 [1]. The chart also lists clinical care areas at 40 for all three pumps and medications per CCA at 400 for Plum 360 and 1,000 for Plum Solo and Plum Duo [5]. These configuration limits are procurement-relevant because they constrain how a facility can structure its drug library.

Check software, interoperability, and total product life cycle documentation

FDA's total product life cycle guidance identifies software error messages and human factors as among the most frequently reported infusion pump problems [4]. The guidance recommends that sponsors provide a clear statement of indications for use, including the intended use environment, intended routes of administration, specific uses such as PCA, and the indicated treatment population [4]. Procurement teams should compare these indication statements across candidate pumps because a device indicated for adult, pediatric, and neonatal populations carries different documentation expectations than one limited to adult use.

The ICU Medical comparison chart lists wireless standards of 802.11 a/b/g/n for Plum 360 and 802.11 a/b/g/n/ac for Plum Solo and Plum Duo, along with IV-EHR integration support and auto-programming and infusion documentation [5]. For wireless connected devices, FDA documentation should describe the wireless quality of service required for proper use [6]. A procurement comparison should therefore request the minimum network conditions each pump requires and confirm that the facility's infrastructure can meet them. Interoperability claims should be tied to specific EHR platforms and software versions, not accepted as generic capabilities.