On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting unavailable, incomplete, incorrect, or non-exportable infusion records caused by access, date-range, pump identification, connectivity, software, or retrieval-system issues.
Step-by-Step Troubleshooting
1. Ensure Patient Safety and Preserve Relevant Data
Do not interrupt an active infusion solely to retrieve history or event-log information.
- Confirm that the pump is delivering the prescribed therapy without unresolved alarms.
- Have clinical staff transfer the infusion to another verified pump before restarting, disconnecting, or removing the affected device when troubleshooting could affect therapy.
- Do not clear pump information, perform a factory reset, reinstall software, or change the pump configuration.
- Preserve the pump in its current condition when the records may relate to a medication error, adverse event, or patient-safety investigation.
- Follow the facility’s risk-management and evidence-preservation procedures when an incident is suspected.
Expected outcome: The patient remains safely supported, and potentially important pump records are not altered or lost.
If the pump is involved in an adverse event, stop routine troubleshooting after documenting its condition and escalate through the facility’s investigation process.
2. Define Exactly What Information Is Missing
Clarify whether the complaint involves:
- Recent infusion history displayed at the pump
- A specific infusion or medication event
- Alarm or system-event records
- Programming changes
- Drug-library compliance information
- Auto-programming or auto-documentation records
- Records expected in Baxter reporting software
- A report that opens but contains incomplete information
- A file that cannot be generated, downloaded, opened, or transferred
Record:
- Pump asset number and serial number
- Approximate date and time of the infusion
- Care area or clinical location
- Medication or therapy involved, when appropriate
- Requested report type
- Exact error message
- Whether the problem affects one pump or multiple pumps
Expected outcome: The missing record and the system from which it should be retrieved are clearly identified.
3. Verify the Correct Pump Was Selected
Confirm that the pump being reviewed matches the device used for the reported infusion.
Compare:
- Biomedical asset tag
- Manufacturer serial number
- Pump identifier shown in the reporting system
- Wireless network identifier, when available
- Clinical location
- Date and time of use
Do not rely only on the room number or a handwritten pump number. Pumps may be exchanged, moved, or returned to Clinical Engineering before data review begins.
Expected outcome: The correct physical pump and electronic device record are being examined.
If the wrong pump was selected, repeat the search using the correct identifier and stop if the record is located.
4. Check the Pump’s Date and Time
Compare the date and time displayed by the Spectrum IQ with a verified facility time source.
Check for:
- Incorrect date
- Incorrect time
- AM/PM errors
- Time-zone mismatch
- Daylight-saving-time discrepancy
- Significant clock drift
- A clock that reset after extended power loss or service
An incorrect pump clock can cause records to appear outside the expected search window.
Do not change the date or time before documenting the original setting when the pump may be associated with an investigation.
Expected outcome: The pump time is correct or any discrepancy is documented and considered during the record search.
If the clock is incorrect, expand the report’s search range to include the offset. Correct the device time only according to facility policy and approved configuration procedures.
5. Expand the Search Date and Time Range
Repeat the history or reporting search using a wider period.
Include:
- Several hours before and after the reported event
- The previous and following calendar dates
- Any known pump-time discrepancy
- The complete period during which the pump was assigned to the patient area
Verify that no filters are unintentionally excluding:
- Completed infusions
- Stopped or canceled infusions
- Alarm events
- Manual programming
- Auto-programmed infusions
- Specific care areas
- Specific drug-library versions
- Specific pump types
Expected outcome: Records hidden by an incorrect date range or report filter become visible.
If the requested data appears, verify that it matches the correct pump and event, then stop.
6. Review Available History at the Pump
When the pump is safely removed from patient use, check whether the applicable history or event information can be viewed locally through the normal operator-accessible menus.
Do not enter restricted service functions unless authorized and trained.
Determine whether:
- The local history is present
- The local history is also missing
- Records stop at a specific date
- The pump displays an access or memory error
- The pump freezes, restarts, or becomes unresponsive while opening history
- Only reporting-system data is missing
Expected outcome: Clinical Engineering determines whether the failure is local to the pump or limited to an external reporting system.
If local records are available but external records are absent, continue with connectivity and reporting-system checks.
7. Confirm Normal Pump Operation
Inspect the pump for indications of a broader software or hardware problem.
Check for:
- Startup errors
- Unexpected reboots
- Frozen menus
- Slow response
- Technical-error messages
- Repeated loss of configuration
- Incorrect drug-library information
- Abnormal battery or power behavior
- Signs of liquid intrusion, impact, or physical damage
Power-cycle the pump only when:
- It is not connected to a patient
- Relevant incident data has been preserved or the restart has been authorized
- The pump is not frozen during an active investigation
- Facility procedures permit the restart
After restarting, confirm normal startup and check whether the history function is available.
Expected outcome: The pump operates normally, or evidence of a broader internal problem is identified.
If the pump reports a technical fault, repeatedly reboots, or cannot reliably access its menus, remove it from service and send it for bench evaluation.
8. Check Wireless Connectivity Status
The Spectrum IQ can communicate with supporting hospital systems through its configured network environment. Baxter describes the platform as supporting EMR integration and reporting functions, including event-level infusion information.
Confirm that:
- Wireless communication is enabled according to facility configuration
- The pump shows its normal network-status indication
- The pump is within an approved wireless coverage area
- The problem does not occur only in one room or unit
- Other Spectrum IQ pumps in the same area are communicating
- The pump has not recently been replaced, reconfigured, or returned from repair
- The device is associated with the correct network inventory record
Move the pump only to an approved test location when permitted. Do not alter wireless credentials or network configuration without authorization.
Expected outcome: The pump establishes normal network communication or the failure is isolated to connectivity.
If several pumps in the same location are affected, escalate to the appropriate network, integration, or Baxter system administrator rather than treating each pump as defective.
9. Compare With a Known-Good Spectrum IQ Pump
Using another Spectrum IQ pump with the same approved configuration:
- Place both pumps in the same authorized test area.
- Confirm that the known-good pump connects normally.
- Verify whether its recent test activity appears in the expected reporting application.
- Compare displayed network status and general configuration indicators.
- Do not perform a patient infusion solely for testing.
A simulated or facility-approved test infusion may be used when authorized and properly identified so it is not mistaken for clinical data.
Expected outcome: Clinical Engineering determines whether the problem follows the individual pump or affects the broader system.
If both pumps fail, investigate the network, server, interface, user account, or reporting application.
If only the original pump fails, continue toward device-specific escalation.
10. Confirm the Reporting-System Status
Check with the facility’s designated Baxter application, pharmacy informatics, integration, or IT support contact.
Determine whether:
- The reporting server is online
- Data processing is delayed
- A scheduled maintenance window is active
- An interface or application service has stopped
- Storage capacity is available
- A recent software, certificate, firewall, or network change occurred
- Other users can generate the same report
- Other pumps are uploading current information
- The system has a backlog of unprocessed records
Avoid restarting servers, changing database settings, or modifying interface services unless that work is within the technician’s authorized responsibility.
Expected outcome: A system-wide reporting interruption is identified or ruled out.
If the reporting system is unavailable, document the outage and route the issue to its assigned application owner.
11. Verify User Access and Report Permissions
Confirm that the person attempting the export:
- Is signed into the correct application
- Has permission to view the required care area
- Has access to the requested report type
- Is permitted to export or download information
- Is using an active account
- Is not affected by an expired password or locked account
- Can retrieve another pump’s records
Attempt the same report using an authorized known-good account when facility policy permits.
Do not share passwords or use another person’s credentials without authorization.
Expected outcome: Account or permission problems are corrected or ruled out.
If another authorized account works normally, refer the issue to the application administrator rather than servicing the pump.
12. Check Export Parameters and Destination
When records are visible but cannot be exported, verify:
- The requested file format
- The selected report range
- The destination folder
- Available storage space
- File-name length and unsupported characters
- Write permission for the selected location
- Whether the file already exists or is open
- Whether browser download restrictions are blocking the export
- Whether endpoint security software quarantined or blocked the file
- Whether the exported file requires an approved application to open
Attempt a small report using a short date range and an approved local or network destination.
Do not export protected health information to an unapproved removable drive, personal device, email account, or cloud-storage service.
Expected outcome: The report exports successfully or the failure is isolated to the workstation, destination, or application.
If the small report works, the original export may be too large or contain an unsupported parameter. Divide the request into smaller approved ranges.
13. Inspect Approved External Connections
When the facility’s retrieval process uses an approved cable, service computer, docking connection, or network adapter:
- Inspect the connection for looseness or damage.
- Confirm the correct approved accessory is being used.
- Check connectors for bent contacts, contamination, or impact damage.
- Reseat accessible external connections.
- Test with a known-good approved cable or workstation.
- Confirm that the computer recognizes the connected device or interface.
Do not connect unapproved USB devices, personal computers, or unknown software to the pump.
Expected outcome: A defective external cable, connection, computer, or accessory is identified or ruled out.
If replacing the external connection restores access, document the failed accessory and stop.
14. Preserve Diagnostic Information
Before escalating, collect:
- Complete error messages
- Screenshots when permitted
- Pump asset number and serial number
- Pump software version
- Drug-library version
- Pump date and time
- Reporting-system date and time
- Network-status indication
- Approximate time of the missing infusion
- Whether local history is present
- Whether other pumps are affected
- Whether the failure follows the pump
- Export file type and destination
- Steps already attempted
The Spectrum IQ service documentation includes procedures intended for trained service personnel. Do not attempt restricted event-log extraction, software installation, or internal service procedures without the required authorization and documentation.
Expected outcome: Sufficient information is available for Baxter, IT, pharmacy informatics, or bench-service personnel to continue without repeating basic checks.
If the Problem Persists
If the correct pump, date range, filters, user permissions, workstation, external connections, network availability, and reporting-system status have been verified, the remaining problem may involve:
- Corrupted or unavailable pump records
- Pump memory or software failure
- Failed wireless communication hardware
- Device-registration mismatch
- Server-side processing failure
- Database or application failure
- Interface configuration failure
- Unsupported software-version interaction
The device should be:
- Removed from service when pump-specific failure is suspected
- Labeled Out of Service
- Sent for authorized bench evaluation or Baxter support
- Preserved without further resetting when the records relate to an incident
Do not erase memory, reload software, replace internal components, or perform restricted log-recovery procedures unless trained, authorized, and working from the applicable controlled service documentation.
When multiple pumps are affected, leave clinically functional pumps in service only under facility-approved guidance and escalate the common infrastructure problem to the responsible application, network, pharmacy informatics, or Baxter support team.
Knowing when to stop protects patient data, preserves evidence, and prevents unnecessary device repair.
Clinical Use Tip
Do not troubleshoot history, export, or communication problems while the pump is delivering a critical medication if testing could interrupt therapy.
Move the patient’s infusion to another verified pump before restarting, disconnecting, or removing the affected device. Missing reporting data does not automatically mean the infusion failed, so independently verify the therapy’s clinical status before drawing conclusions.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Nursing reported that infusion history from Spectrum IQ pump asset 18452 for the previous evening was unavailable in the Baxter reporting application."
Cause
What was observed during troubleshooting.
Example:
"The pump’s local history was present, but the device showed no normal wireless connection and did not upload a controlled test record while a known-good pump uploaded successfully in the same location."
Resolution
What action was taken.
Example:
"Removed the pump from service, labeled it Out of Service, preserved its existing data, and forwarded it for authorized communication-system evaluation."
Helpful Details to Include (If Known)
- Patient was transferred before troubleshooting
- Asset number and serial number verified
- Exact missing date and time recorded
- Pump clock compared with facility time
- Search range expanded
- Report filters verified
- Local pump history checked
- Complete error message recorded
- Software version documented
- Drug-library version documented
- Wireless-status indication documented
- Known-good pump comparison completed
- Reporting-system status checked
- User permissions verified
- Export destination and storage checked
- Approved cables or workstation swapped
- Unusual resets or software behavior noted
- Incident data preserved
- Final device status documented
Final Thought
Infusion-record problems should be approached by protecting the patient and preserving the original data first. Verify the pump identity, clock, search settings, user access, external connections, and supporting infrastructure before assuming an internal failure. Clear documentation and appropriate escalation are especially important when the missing records may be part of a clinical investigation.
That is successful troubleshooting.