On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
This guide helps troubleshoot a Configuration Required alarm on the Smiths Medical Medfusion 4000 infusion pump. This alarm indicates the pump does not have a valid configuration available for safe clinical use. It may affect drug libraries, care areas, infusion limits, infusion properties, clinical profiles, and medication delivery setup.
Step-by-Step Troubleshooting
Ensure Patient Safety First
- Remove the Medfusion 4000 from patient use immediately if the alarm appears during setup or before an infusion.
- Do not attempt to bypass the alarm or use the pump for medication delivery until the correct configuration is installed and verified.
- Use a backup infusion pump if therapy needs to continue.
- Expected outcome: Patient care is not dependent on a pump with missing or invalid configuration.
- Why it matters: A configuration issue can affect drug libraries, limits, infusion properties, clinical profiles, and safe pump operation.
Verify the Reported Alarm and Behavior
- Power on the pump and confirm the displayed alarm is Configuration Required.
- Note whether the alarm appears at startup, after battery replacement or service, after attempted software/configuration update, after network or PharmGuard activity, or when selecting a care area, drug, or infusion mode.
- Document whether the pump allows any clinical setup steps or remains locked out by the alarm.
- Expected outcome: The alarm is confirmed and the timing is documented.
- Why it matters: This separates a true configuration problem from a user selection issue, temporary startup condition, or unrelated pump fault.
Confirm the Pump Is Not Being Used Clinically
- Check whether the pump is assigned to a patient care area or was pulled from active clinical circulation.
- If it was found in use or staged for use, notify clinical staff that it should not be used until Clinical Engineering verifies the configuration.
- Expected outcome: The pump is isolated from clinical use.
- Why it matters: A pump without a valid configuration may not contain the correct facility-approved drug libraries or infusion limits.
Check for Simple Setup or Selection Issues
- Review whether the pump is asking for a profile, care area, drug library, or configuration selection.
- Confirm the user did not simply select an unavailable or incorrect program option.
- Check whether the expected care area or drug program is missing from the pump.
- Expected outcome: The alarm is not caused by an incorrect user selection.
- Why it matters: Some configuration-related complaints may appear during setup if the expected profile or drug program is not available.
Verify Power and Battery Stability
- Connect the pump to a known-good AC power source.
- Confirm the pump remains powered without restarting, shutting down, or losing settings during startup.
- Inspect the power cord, power supply connection, and battery status.
- Expected outcome: The pump powers reliably while configuration is checked.
- Why it matters: Interrupted power during configuration transfer or startup can contribute to incomplete setup or failed validation.
Check for Recent Service, Update, or Configuration Activity
- Determine whether the pump was recently returned from repair, updated, reconfigured, moved between departments, added to a new drug library group, connected to PharmGuard Toolbox, cleared, reset, or restored.
- Review any recent service notes or work orders for configuration-related activity.
- Expected outcome: Any recent change that may have affected pump configuration is identified.
- Why it matters: Configuration Required often points to a missing, incomplete, invalid, or not-yet-taught configuration.
Confirm the Correct Facility Configuration Is Available
- Using the appropriate facility workflow, verify that the approved Medfusion 4000 configuration and drug program exist in PharmGuard Toolbox or the approved configuration management system.
- Confirm the configuration matches the facility, department, care area, and intended pump use.
- Do not load an unverified, outdated, or incorrect configuration.
- Expected outcome: The correct approved configuration is identified before loading anything to the pump.
- Why it matters: Installing the wrong library or care area profile can create medication safety risk.
Reinstall or Teach the Approved Configuration
- Use the approved PharmGuard Toolbox or network configuration workflow to load the correct validated configuration to the pump.
- Follow facility procedure for teaching the configuration to the pump.
- Do not manually create or modify infusion properties at the pump unless this is part of the approved validated workflow.
- Expected outcome: The pump accepts the configuration and the Configuration Required alarm clears.
- Why it matters: Custom configuration and infusion properties must be reviewed, validated, and taught to pumps before medical use.
Verify Configuration After Loading
- After the configuration is loaded, restart the pump and confirm the alarm does not return.
- Verify that the expected care areas, drug programs, infusion modes, limits, and facility settings are present.
- Confirm date, time, network status, and any facility-required identifiers are correct if applicable.
- Expected outcome: The pump starts normally and displays the correct approved configuration.
- Why it matters: Clearing the alarm alone is not enough. Clinical Engineering must confirm the correct configuration is actually installed.
Perform Functional Readiness Checks
- Confirm display and keypad response.
- Confirm normal startup behavior.
- Verify alarm tone operation.
- Check AC and battery status.
- Confirm syringe detection and setup behavior as applicable.
- Verify expected configuration and drug library access.
- Restart the pump and confirm the Configuration Required alarm does not return.
- If this resolves the issue, return the pump to service according to facility process and document the configuration verification.
If the Problem Persists
If the Configuration Required alarm returns after the approved configuration is installed and verified, external and common causes have been ruled out. A persistent configuration alarm may indicate failed configuration transfer, corrupted configuration data, software issue, memory problem, communication issue, or another internal device fault.
Remove the device from service, label it Out of Service, and send it for repair, bench evaluation, or vendor/service review.
Knowing when to stop is proper troubleshooting.
Clinical Use Tip
Never troubleshoot on an active patient. A pump with missing or invalid configuration should not be used for infusion. Move the patient to a backup device first, then verify that the correct facility-approved configuration and drug program setup are installed before returning the pump to service.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Smiths Medical Medfusion 4000 displayed Configuration Required alarm at startup. Pump was not available for clinical use due to missing or invalid configuration/drug program setup."
Cause
What was observed during troubleshooting.
Example:
"Pump did not have a valid facility-approved configuration loaded, or configuration was incomplete/invalid following setup or service activity."
Resolution
What action was taken.
Example:
"Removed pump from clinical use. Verified approved facility configuration in PharmGuard Toolbox/network workflow. Loaded and taught correct configuration to pump. Restarted pump, confirmed Configuration Required alarm cleared, verified expected care areas/drug programs, and returned pump to service."
Helpful Details to Include (If Known)
- Alarm behavior
- Accessories swapped
- Power behavior
- Environmental factors
- Indicator lights
- Final device status
Final Thought
Configuration alarms on infusion pumps must be handled carefully because they directly affect medication safety. Clinical Engineering should confirm the alarm, rule out simple setup and power issues, reload only the approved validated facility configuration, and verify the pump before returning it to service. If the alarm persists, escalation is the correct action.
That is successful troubleshooting.