Baxter Novum IQ

Asset Type

Infusion Pump

Manufacturer

Baxter

Model

Novum IQ

What This Guide Helps With

Troubleshooting failed barcode scans or patient-pump association caused by barcode quality, scanner condition, workflow, configuration, connectivity, or integration issues.

Step-by-Step Troubleshooting

1. Ensure Patient Safety First

Do not delay or interrupt a clinically necessary infusion solely to troubleshoot barcode scanning or electronic patient association.

• Notify the nurse responsible for the infusion.
• Confirm the correct patient, medication, pump, channel, concentration, dose, and programmed parameters using the facility-approved independent verification process.
• Use another verified pump when electronic association is required by hospital policy and cannot be completed safely.
• Do not scan test barcodes or associate the pump with another patient while it is actively infusing.

Expected outcome: The patient continues receiving the correct therapy without relying on an unverified electronic association.

The Novum IQ platform uses barcode-based workflows to associate the patient, medication, and pump and can support EMR auto-programming and auto-documentation when properly integrated.

2. Identify the Exact Point of Failure

Determine whether:

• The scanner does not activate.
• The scanner activates but does not read any barcode.
• Some barcodes scan while others do not.
• The patient barcode is read, but the pump rejects the association.
• The correct patient appears, but medication auto-programming does not proceed.
• The pump displays a network, server, interface, or association message.
• The problem affects one pump, one scanner, one patient, or multiple devices.

Record the complete displayed message and the workflow step where the failure occurs.

Expected outcome: The problem is separated into a scanning issue, patient-data issue, pump configuration issue, or connectivity/integration issue.

3. Inspect the Barcode and Wristband

Check the patient wristband or printed barcode for:

• Wrinkles, tears, smearing, fading, or missing sections.
• Curvature that prevents the entire barcode from being visible.
• Moisture, blood, lotion, disinfectant residue, or transparent tape.
• A barcode printed too lightly or at an incorrect scale.
• Multiple adjacent barcodes that could cause the wrong code to be captured.

Have clinical staff obtain a replacement wristband when the barcode is damaged or unreadable.

Expected outcome: A clean, flat, complete, facility-approved patient barcode is available.

If replacing the wristband resolves the problem, verify the correct patient association and stop.

4. Inspect and Clean the Scanner

Remove the pump from patient use before cleaning when required by hospital policy.

• Inspect the scanner window for fingerprints, dried residue, scratches, cracks, or clouding.
• Clean the scanner using only the facility-approved method and Baxter-compatible cleaning products.
• Allow the surface to dry completely.
• Confirm that no label, tape, protective film, mount, or accessory obstructs the scanner.

Expected outcome: The scanner window is clean, dry, intact, and unobstructed.

If cleaning restores reliable scanning, complete an operational check and return the pump according to facility procedure.

5. Check Scanning Technique and Environment

Using an approved test barcode or non-patient training workflow:

• Hold the complete barcode within the scanner’s field.
• Keep the barcode reasonably flat.
• Vary the distance and angle gradually.
• Avoid direct glare from procedure lights, windows, or reflective wristband material.
• Confirm that the scanner can acquire a barcode without repeated excessive attempts.

Do not use photographs, photocopies, or unofficially generated barcodes as the primary functional test.

Expected outcome: A properly presented, approved barcode scans consistently.

6. Test With a Known-Good Barcode

Test the scanner with a known-good barcode approved for the hospital’s Novum IQ workflow.

• If the known-good barcode also fails, suspect the scanner, pump configuration, or scanner connection.
• If the known-good barcode scans successfully, suspect the original wristband, barcode format, patient-registration record, or workflow selection.
• Do not associate the pump with a real patient solely for testing.

Expected outcome: The failure is isolated to either the scanning hardware or the specific barcode/data record.

7. Check the Scanner Connection and Physical Condition

When an external or connected scanning accessory is used:

• Confirm the scanner cable is fully seated at both ends.
• Inspect the cable, strain relief, and connector for bends, looseness, contamination, or damaged contacts.
• Confirm the scanner is connected to the designated pump or workstation port.
• Reseat the connection only when the pump is safely removed from clinical use.
• Test with a facility-approved known-good scanner or cable when available.

Do not force connectors or substitute unapproved commercial barcode scanners.

Expected outcome: The scanner is securely connected and recognized without intermittent operation.

If a known-good scanner resolves the issue, remove the failed accessory from service and document the replacement.

8. Confirm the Correct Pump Workflow and Configuration

Verify that:

• The pump is operating in the correct care area or clinical profile.
• Barcode-enabled patient-association functionality is available.
• The expected drug library or configuration is loaded.
• The user is following the facility’s established association sequence.
• The pump is not in a standalone, offline, demonstration, service, or other mode that prevents clinical association.
• The displayed patient-association screen matches the intended workflow.

Dose IQ provides facility-specific drug-library and pump configuration functions, while the IQ Enterprise Connectivity Suite supports integration and wireless distribution functions.

Expected outcome: The pump is in the correct clinical profile and is configured for the hospital’s barcode and interoperability workflow.

9. Verify Network Connectivity

Check the pump’s external connectivity indicators and compare them with a functioning Novum IQ pump in the same area.

• Confirm the pump shows the expected wireless or network connection.
• Move the pump to a location with known-good coverage when permitted.
• Check whether multiple pumps in the same unit are experiencing the same problem.
• Confirm that no recent wireless, certificate, VLAN, security, or server changes coincide with the failure.
• Have the appropriate IT or integration team verify that the pump can communicate with the IQ Enterprise environment.

The IQ Enterprise Connectivity Suite supports bidirectional EMR interoperability, auto-programming, auto-documentation, and wireless communication with the Novum IQ platform.

Expected outcome: The pump has stable connectivity to the required hospital systems.

If several pumps fail simultaneously, prioritize escalation to IT, pharmacy informatics, or the integration support team rather than replacing individual scanners.

10. Verify the Patient Registration Record

When the barcode scans but patient association fails, have authorized clinical or registration personnel confirm that:

• The patient is admitted to the correct encounter.
• The wristband barcode matches the active patient record.
• The patient is assigned to the correct nursing unit, room, or bed.
• The encounter has reached the EMR and interface systems.
• The wristband was not printed before a registration correction or encounter change.
• The scanned identifier is supported by the configured interface.

Clinical Engineering should not alter patient demographics or create test patient encounters without authorization.

Expected outcome: The scanned patient identifier matches an active record available to the infusion integration system.

If correcting or reprinting the wristband resolves the association, verify the displayed patient carefully and stop.

11. Compare With Another Novum IQ Pump

Using the same approved test conditions:

• Test the barcode on another properly functioning Novum IQ pump.
• Test the affected pump with a known-good barcode and scanner.
• Determine whether the problem follows the pump, scanner, barcode, patient record, location, or network connection.

Expected outcome: The failure is narrowed to a specific device, accessory, data record, or infrastructure component.

12. Perform a Controlled Restart

After the pump has been removed from patient use:

• Disconnect all patient-use accessories as required.
• Power the pump down normally.
• Wait for complete shutdown.
• Restart the device and allow it to reconnect fully.
• Confirm the correct profile, drug library, network status, date, and time.
• Repeat the approved barcode and patient-association functional test.

Do not repeatedly power-cycle a pump that displays a persistent system error.

Expected outcome: Temporary software or communication conditions clear and the scanner workflow operates normally.

If the restart resolves the issue, complete a full operational verification before returning the pump to service.

13. Review Logs and Infrastructure Status

When available to authorized Clinical Engineering personnel:

• Record the pump serial number, software version, configuration version, drug-library version, and time of failure.
• Review accessible device or connectivity logs for scanner, authentication, network, interface, or association errors.
• Check whether the IQ Enterprise server, EMR interface, admission-discharge-transfer feed, or wireless services experienced an outage.
• Provide the exact timestamp and displayed message to IT, pharmacy informatics, or Baxter support.

Do not modify server interfaces, certificates, device configuration, or drug libraries without change control and proper authorization.

Expected outcome: The responsible device or system component is identified for targeted correction.

If the Problem Persists

If the scanner cannot reliably read known-good barcodes, the scanner is not recognized, or the affected pump repeatedly fails patient association while comparable pumps function normally, common external causes have been ruled out.

The device should be:

• Removed from service.
• Labeled Out of Service.
• Sent for repair or bench evaluation.
• Escalated to Baxter technical support when scanner diagnostics, software correction, configuration restoration, or component replacement is required.

When multiple pumps are affected, escalate the event to the hospital’s IT, pharmacy informatics, cybersecurity, EMR integration, and Baxter support teams as appropriate.

Knowing when to stop and escalate a suspected internal or enterprise-system failure is proper troubleshooting.

Clinical Use Tip

Do not troubleshoot patient association by scanning another patient’s wristband or assigning an active pump to a test patient. Move therapy to a verified device when association is required for safe treatment.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"Nursing reported that the Baxter Novum IQ pump scanned the patient wristband but would not complete patient association."

Cause

What was observed during troubleshooting.

Example:
"The pump scanned a known-good barcode successfully, but it had no connection to the IQ Enterprise network and could not retrieve the active patient encounter."

Resolution

What action was taken.

Example:
"Removed the pump from clinical use, documented the connectivity failure, notified the integration team, and retained the pump Out of Service pending network and association verification."

Helpful Details to Include (If Known)

• Exact displayed error or status message
• Scanner activation or illumination behavior
• Scanner window inspected and cleaned
• Known-good barcode tested
• Replacement wristband tested
• Known-good scanner or cable tested
• Pump profile and drug-library version
• Wireless and server connection status
• Whether another pump completed the association
• Number and location of affected pumps
• Patient encounter verified by authorized staff
• Pump serial number and software version
• Date and time of the failed association
• Final device status

Final Thought

Patient identity and infusion programming must never be assumed because a barcode was scanned. Logical isolation of the barcode, scanner, pump, patient record, network, and interface protects the patient and supports appropriate escalation. Detailed documentation is especially important when the failure involves multiple interconnected hospital systems.

That is successful troubleshooting.