B. Braun Space Infusion Pump System

Asset Type

Infusion Pump

Manufacturer

B. Braun

Model

Space Infusion Pump System

What This Guide Helps With

Troubleshooting failed pump-to-patient association, unavailable auto-programming, or missing infusion documentation caused by workflow, connectivity, identification, or interface issues.

Step-by-Step Troubleshooting

1. Ensure Patient Safety First

Do not interrupt or reprogram an active infusion solely to correct an interoperability or documentation problem.

• Confirm the pump is delivering the prescribed medication at the correct programmed rate.
• Have clinical staff independently verify the medication, concentration, dose, route, patient, and channel.
• Use the facility-approved manual programming and documentation workflow until interoperability is restored.
• Transfer the infusion to another verified pump before restarting or removing the affected device when continued therapy is required.

Expected outcome: The patient continues receiving the correct therapy without relying on unavailable auto-programming or auto-documentation.

If the pump’s displayed therapy does not match the active medication order, notify clinical staff immediately and follow the facility’s medication-safety escalation procedure.

2. Clarify the Exact Association Failure

Determine whether:

• The pump cannot be associated with the patient.
• The patient or encounter does not appear.
• The medication order is unavailable.
• Auto-programming information does not transfer to the pump.
• The pump accepts programming but documentation does not return to the EMR.
• One pump, one channel, one bed, or the entire care area is affected.
• The problem began after a patient transfer, bed change, pump replacement, or new encounter.

Record the exact displayed message and the approximate time of failure.

Expected outcome: The failure is identified as an association, order-retrieval, programming, or documentation problem.

3. Confirm the Correct Patient, Encounter, and Location

Ask clinical staff to verify:

• The patient is admitted to the correct encounter.
• The patient is assigned to the correct room and bed.
• The active medication order belongs to the current encounter.
• The patient was not recently discharged, transferred, merged, or moved.
• The workstation, scanner, pump, and EMR are using the same patient context.

Patient and device association is essential because B. Braun interoperability workflows depend on the hospital network, EMR data, and bedside verification process.

Expected outcome: The correct patient, active encounter, bed assignment, and medication order are available.

If an incorrect patient is displayed, stop. Do not associate the pump or accept transferred programming.

4. Repeat the Approved Association Workflow

Have trained clinical staff repeat the facility-approved workflow from the beginning.

This may include:

• Scanning the clinician badge.
• Scanning the patient wristband.
• Scanning the medication.
• Selecting the prescribed order.
• Scanning or selecting the pump or infusion channel.
• Confirming the association on the appropriate screen.

Inspect barcodes for damage, poor print quality, condensation, curved placement, or incorrect labels.

Expected outcome: The pump, patient, medication order, and intended channel associate successfully.

If association succeeds, verify that the programmed parameters exactly match the order before starting or continuing therapy, then stop troubleshooting.

5. Check the Barcode Scanner and Workstation

When barcode scanning is part of the workflow:

• Confirm the scanner is powered and recognized by the workstation.
• Test it using an approved non-patient barcode or facility test workflow.
• Check the scanner cable, charging base, or wireless connection.
• Try a known-good scanner when permitted.
• Confirm the workstation is logged into the correct clinical application.
• Check for frozen applications, pending login prompts, or expired sessions.

Expected outcome: Barcodes are captured correctly and appear in the intended application fields.

If the scanner fails outside the infusion workflow, route the scanner or workstation issue to the appropriate support team.

6. Inspect the Pump and Docking Connections

Check the affected Space pump and any connected SpaceStation, communication module, or network interface.

• Confirm the pump is fully seated and mechanically secure.
• Inspect accessible contacts and connectors for contamination, moisture, bent components, or physical damage.
• Remove nonessential accessories that may interfere with proper seating.
• Compare the installation with a working pump in the same area.
• Reseat the pump only after the infusion has been safely transferred or the device is no longer connected to a patient.

Expected outcome: The pump is securely connected without visible damage or obstruction.

Do not insert tools into contacts or disassemble the docking or communication hardware.

7. Check Pump Network Status

Review the pump or communication-system indicators available to Clinical Engineering.

Look for:

• Missing network or wireless indicators.
• A disconnected or offline status.
• Repeated connection attempts.
• Unusual communication-module lights.
• Incorrect date or time.
• A network status different from nearby functioning pumps.

B. Braun’s integrated infusion platforms use the hospital network and standardized healthcare communication to exchange programming and documentation data with EMR or patient-data systems.

Expected outcome: The affected pump shows the same normal network state as functioning pumps nearby.

Do not change wireless, security, certificate, address, or server settings without authorization.

8. Compare With a Known-Good Pump

When safe and permitted:

• Place a known-good Space pump in the same docking position or care location.
• Check whether the known-good device can complete the approved association workflow.
• Test the affected pump in a known-good location after removing it from patient use.

Interpretation:

• Known-good pump also fails in the original location: Suspect a location, network, workstation, bed-mapping, or interface issue.
• Affected pump fails in multiple working locations: Suspect the pump, communication module, configuration, or device record.
• Failure follows one patient or encounter: Suspect patient-registration, order, or EMR association data.

Expected outcome: The problem is isolated to the device, location, patient record, or enterprise interface.

9. Confirm the Pump Is Correctly Identified in Supporting Systems

Coordinate with the approved infusion-system administrator, integration team, or clinical informatics team to verify:

• The pump serial number or device identifier is correctly entered.
• The device is assigned to the correct facility or care area.
• The pump is active in the infusion-management system.
• The communication module is not duplicated or retired.
• Room and bed mappings match the current hospital configuration.
• The pump has the approved software and drug-library configuration.
• There are no pending deployment, registration, or synchronization errors.

Expected outcome: The physical pump matches its electronic device record and assigned location.

Clinical Engineering should not independently edit production interface mappings unless specifically authorized.

10. Determine Whether the Failure Is Local or Widespread

Check whether other Space pumps can auto-program and auto-document.

• Test another pump in the same room.
• Check another bed in the same unit.
• Ask whether other units are affected.
• Review approved system dashboards or alert consoles.
• Contact the interface, network, pharmacy-informatics, or EMR support team when multiple devices are affected.

Expected outcome: The scope is identified as one device, one bed, one unit, or an enterprise-wide interruption.

A widespread failure is unlikely to be corrected by replacing or repairing an individual pump.

11. Check for Delayed or One-Way Communication

Determine whether:

• Programming reaches the pump but documentation does not return.
• Documentation appears after a delay.
• Start, stop, rate-change, or alarm data are selectively missing.
• Data appear under the wrong encounter, bed, time, or channel.
• The pump is communicating with infusion-management software but not the EMR.

Auto-documentation may include infusion, device, and alarm information, while auto-programming uses order information verified through the EMR workflow.

Expected outcome: The failed communication direction and affected data type are identified.

Preserve timestamps and device identifiers for the integration team.

12. Perform a Controlled Restart Only When Safe

After the device has been removed from patient use:

• Power the pump down normally.
• Disconnect it from the docking position or external accessories as appropriate.
• Wait briefly.
• Reconnect and restart the device.
• Allow sufficient time for network registration.
• Repeat only the approved test association workflow.

Do not restart servers, communication appliances, production interfaces, or enterprise applications unless directed by the responsible support team.

Expected outcome: The pump reconnects and the association workflow becomes available.

If restarting resolves the issue, complete a functional check and verify successful programming and documentation before returning the device to service.

13. Review Logs Without Clearing Information

When authorized tools are available, collect:

• Pump serial number.
• Communication-module identifier.
• Date and time of the failure.
• Room and bed.
• Pump and channel involved.
• Displayed error message.
• Network status.
• Patient encounter identifier according to privacy policy.
• Whether auto-programming, auto-documentation, or both failed.
• Results from known-good device testing.

Do not clear pump history, reset configuration, remove device records, or overwrite logs before the event is reviewed.

Expected outcome: Support teams receive enough information to trace the transaction across the pump, network, integration platform, and EMR.

If the Problem Persists

If patient context, orders, barcode workflow, physical connections, network status, location mapping, and known-good comparisons have been checked, common external causes have been ruled out.

The problem may involve:

• Pump communication hardware.
• Docking or communication-module failure.
• Device registration or configuration.
• Wireless or network infrastructure.
• Bed or location mapping.
• EMR interface processing.
• Integration-server services.
• Patient or order-message synchronization.

The affected device should be:

• Removed from service when the failure follows the pump.
• Labeled Out of Service.
• Sent for repair or bench evaluation.
• Escalated to B. Braun technical support or the appropriate integration team when required.

When multiple pumps are affected, escalate as a system or interface incident rather than exchanging pumps repeatedly.

Knowing when to stop device-level troubleshooting and involve networking, informatics, pharmacy, or manufacturer support is proper troubleshooting.

Clinical Use Tip

Do not troubleshoot association or interoperability problems by repeatedly rescanning an active high-alert infusion.

Move the patient’s therapy to a verified manual workflow first. Auto-programming and auto-documentation improve workflow safety, but they do not replace independent verification of the medication order, pump settings, patient identity, and active infusion.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"Nursing reported that the B. Braun Space pump would not associate with the patient, preventing auto-programming and infusion documentation."

Cause

What was observed during troubleshooting.

Example:
"The pump communicated normally in another room, but the original bed mapping did not match the patient’s current EMR location after transfer."

Resolution

What action was taken.

Example:
"Clinical informatics corrected the bed mapping, and Clinical Engineering verified successful patient association, order transfer, and infusion documentation using the approved test workflow."

Helpful Details to Include (If Known)

• Exact error message recorded
• Patient and encounter verified
• Room and bed assignment verified
• Barcode workflow repeated
• Scanner tested
• Pump and docking connections inspected
• Network indicators checked
• Known-good pump tested
• Affected pump tested in another location
• Device identifier and serial number recorded
• Auto-programming tested
• Auto-documentation tested
• Failure time documented
• Interface or informatics team contacted
• Final device status documented

Final Thought

Auto-programming and auto-documentation failures require a structured review of patient safety, clinical workflow, device association, physical connections, network communication, and system mapping. Isolating whether the problem follows the pump, patient, bed, or interface prevents unnecessary repairs and supports faster escalation. Accurate CCR documentation gives every involved team the information needed to trace and resolve the failure.

That is successful troubleshooting.