On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
A pocket, Cubie, or mini-drawer is not detected because of seating, obstruction, contamination, damage, configuration, or local connection problems.
Step-by-Step Troubleshooting
1. Protect Medication Security
Do not use an unrecognized compartment for medication storage or access until identification and locking functions are reliable.
Coordinate with pharmacy for alternate secure medication storage or dispensing if needed.
Expected outcome: Medications remain secure and available through an approved alternate process.
2. Confirm the Exact Recognition Problem
Identify:
- Specific drawer.
- Specific pocket, Cubie, or mini-drawer.
- Whether it is physically present but not shown.
- Whether recognition is intermittent.
- Whether the issue began after restocking, cleaning, relocation, or component replacement.
Record any displayed message exactly.
Expected outcome: The problem is isolated to a specific compartment and operating condition.
3. Inspect Seating and Installation
Check whether the compartment appears fully seated and aligned in its normal position.
Look for:
- Partially inserted components.
- Misalignment.
- Packaging or labels interfering with seating.
- An item lodged beneath or around the compartment.
Do not force components into place.
Expected outcome: The compartment is correctly seated with no visible obstruction.
If proper reseating using an approved user-accessible method restores recognition, proceed to final verification and stop troubleshooting.
4. Inspect for Contamination or Damage
Inspect accessible surfaces and interfaces for:
- Debris.
- Medication residue.
- Cracks.
- Bent or damaged accessible features.
- Evidence of liquid intrusion.
Use only approved cleaning methods and do not probe electrical contacts with metal tools.
Expected outcome: The compartment and accessible interface are clean and physically intact.
5. Compare With a Known-Good Compartment
When institutionally permitted and configuration allows, compare the affected component with a known-good equivalent.
The purpose is to determine whether the issue follows the removable component or remains with the cabinet position.
Do not move medication assignments or secured inventory casually for testing.
Expected outcome: The problem is localized to either the removable compartment or the cabinet location.
6. Verify Drawer Function
Confirm the parent drawer opens, closes, and locks normally.
A broader drawer mechanical or communication issue may prevent recognition of individual compartments.
Expected outcome: The parent drawer operates normally or a larger drawer problem is identified.
7. Check Cabinet Application Status
Confirm the cabinet is fully online and synchronized and that no broader application condition is preventing normal inventory hardware recognition.
Do not make unapproved configuration changes.
Expected outcome: The cabinet application state is normal and the issue remains localized.
8. Coordinate Configuration Verification
If the hardware appears intact but the compartment is not recognized, have the appropriate pharmacy informatics or authorized system administrator verify that the expected drawer or compartment configuration matches the physical hardware.
Clinical Engineering should not alter medication assignments or security configuration without authorization.
Expected outcome: Physical configuration and system configuration agree.
9. Perform Final Functional Verification
After correction, verify the compartment:
- Is recognized consistently.
- Opens or releases appropriately if applicable.
- Locks securely.
- Reports the correct state.
- Is available to the authorized application workflow.
Expected outcome: Recognition and secure operation remain normal through repeated basic checks.
If successful, troubleshooting can stop.
10. Escalate Persistent Recognition Failure
If seating, contamination, physical condition, parent drawer operation, and approved configuration have been checked, stop external troubleshooting.
Potential remaining categories include compartment electronics, position sensing, drawer interface, wiring, or controller-level problems.
Expected outcome: The affected hardware is removed from medication service and routed for technical repair.
If the Problem Persists
Common external seating, contamination, drawer, and configuration causes have been ruled out.
The cabinet should be:
- Removed from service when secure medication control cannot be assured.
- Labeled Out of Service.
- Sent for repair or bench/on-site evaluation.
- Evaluated using manufacturer documentation and approved test equipment.
- Repaired or configured only by qualified personnel.
Return to service only after the affected compartment is consistently recognized and secure medication control is verified.
Knowing when to stop before dismantling compartment electronics is proper troubleshooting.
Clinical Use Tip
An intermittently recognized medication compartment should be treated as unreliable until recognition and locking are proven stable.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Pharmacy reported one Cubie in the Pyxis MedStation ES was physically installed but not recognized by the cabinet."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found the Cubie was not fully seated because packaging material was interfering with its position."
Resolution
What action was taken.
Example:
"Removed the obstruction, reseated the Cubie using the normal accessible procedure, and verified consistent recognition and secure operation."
Helpful Details to Include (If Known)
- Specific drawer and compartment.
- Exact displayed message.
- Intermittent versus constant failure.
- Recent restocking or cleaning.
- Seating condition.
- Visible debris or damage.
- Known-good comparison result.
- Parent drawer operation.
- Configuration verification.
- Final recognition and locking status.
Final Thought
Verify seating, obstruction, physical condition, and configuration before assuming an electronic failure, preserve medication security throughout testing, and escalate when recognition remains unreliable.
That is successful troubleshooting.