Smiths Medical Medfusion 3500

Drug Library Missing, Outdated, or Will Not Load

On this page

Asset Type

Infusion Pump

Manufacturer

Smiths Medical

Model

Medfusion 3500

What This Guide Helps With

Troubleshoots missing or unavailable drug-library content caused by configuration, communication, deployment, version, or server-related problems.

Step-by-Step Troubleshooting

1. Protect the Patient and Maintain Therapy

Do not alter drug-library configuration on a pump actively supporting a patient. If the required safety library is unavailable for the intended therapy, follow facility policy and provide an appropriately configured replacement pump.

Expected outcome: Patient therapy uses equipment with the required verified configuration.

2. Confirm the Exact Library Problem

Determine whether the library is completely missing, appears outdated, fails to load after deployment, contains an unexpected version, or is unavailable only within a particular profile or care area.

Expected outcome: The specific configuration discrepancy is documented.

3. Verify Device Identification and Assignment

Confirm the pump's identity and intended clinical assignment according to facility records. Make sure the unit has not been moved from another area with a different approved configuration.

Expected outcome: The device is being compared with the correct expected library and profile.

4. Compare With a Known-Good Pump

Check another properly functioning Medfusion 3500 assigned to the same clinical environment. Compare visible library or configuration information available through normal authorized interfaces.

Expected outcome: The expected library state and version can be distinguished from a pump-specific problem.

5. Check Power and Normal Startup

Restart the pump only when it is safely removed from clinical use. Observe whether the drug library becomes available after a normal startup and whether any configuration or communication messages appear.

Expected outcome: The pump completes startup normally and either loads the expected library or provides a reproducible failure condition.

6. Verify Network Availability if Library Distribution Uses the Network

Confirm that the pump has the expected network connection and that the relevant infrastructure is available. Determine whether other similar pumps are experiencing the same problem before assuming a device failure.

Expected outcome: Network-dependent library distribution has an available communication path.

7. Verify the Authorized Deployment Status

Using the facility's approved management process, determine whether the library was actually assigned, distributed, and accepted for this device or device group. Do not manually create or alter clinical drug data outside the approved governance process.

Expected outcome: The pump's expected deployment state is confirmed.

8. Check for Broader System Impact

Determine whether the problem affects one pump, multiple pumps in one area, or the entire fleet. Coordinate with pharmacy, medication-safety, IT, or the responsible system administrator as appropriate.

Expected outcome: A device-specific problem is separated from a server, deployment, or enterprise configuration issue.

9. Verify the Correct Library After Correction

After an authorized deployment or connectivity correction, confirm that the expected approved library or profile is displayed and remains available after a normal restart.

Expected outcome: The intended approved configuration is present and stable. If confirmed, troubleshooting can stop after documentation.

10. Escalate Unresolved Configuration Failure

If the pump cannot obtain or retain its required drug library despite verified infrastructure and authorized deployment, remove it from clinical use requiring that library and escalate to qualified service or system administration.

Expected outcome: A misconfigured pump is prevented from unintended clinical deployment.

If the Problem Persists

Common causes involving device assignment, startup, network availability, deployment status, and system-wide configuration have been evaluated. The remaining problem may involve device configuration, software, server communication, database assignment, or another service-level condition.

The device should be:

Any corrected pump should have its approved library, profile, communication state, and basic pump operation verified before clinical return. Knowing not to improvise medication-safety configuration is proper troubleshooting.

Clinical Use Tip

Treat the drug library as a controlled medication-safety configuration; never substitute an unapproved local workaround for the facility's authorized deployment process.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"Clinical staff reported that a Medfusion 3500 did not display the expected current drug library for their care area."

Cause

What was observed during troubleshooting.

Example:
"Clinical Engineering found the pump had not received the current authorized library deployment assigned to that device group."

Resolution

What action was taken.

Example:
"The approved library was deployed through the authorized system process, the correct configuration was verified after restart, and the pump was returned to service."

Helpful Details to Include (If Known)

Final Thought

Medication-library troubleshooting requires both technical verification and configuration control. Confirm assignment, connectivity, and authorized deployment before assuming a device failure, then escalate unresolved discrepancies appropriately.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide