On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshoot unexpectedly short mobile-device runtime during Lumify scanning by checking battery condition, charging, background activity, heat, connections, and device health.
Step-by-Step Troubleshooting
1. Protect the Patient and Plan for Continuity
Do not begin or continue a clinically important examination when the mobile device is likely to shut down before completion.
Move the examination to another verified system or use an adequately charged approved device when needed.
Expected outcome: Patient care is not interrupted by avoidable loss of mobile-device power.
2. Confirm the Battery Complaint
Ask whether runtime has gradually decreased or suddenly changed, and whether rapid drain occurs only while using Lumify.
Document starting and ending battery levels over a controlled test interval when practical rather than relying only on subjective reports.
Expected outcome: The battery drain is confirmed and associated with a specific operating condition.
3. Verify Normal Charging
Use the approved charging setup for the mobile device and confirm that the device indicates charging normally.
Inspect the charger, cable, and connector for damage or looseness.
Expected outcome: The mobile device charges normally. If a defective external charger or cable is identified and replaced with an approved known-good component, verify charging and troubleshooting can stop.
4. Check Mobile Device Battery Condition
Review any normal user-accessible battery-health information provided by the mobile device.
Look for swelling, case separation, excessive heat, or other physical signs of battery deterioration.
Expected outcome: No physical battery hazard is present. A swollen, damaged, or abnormally hot device is removed from service immediately.
5. Check Background Activity
Close unnecessary applications and verify that unrelated high-power functions are not actively consuming resources during testing.
Do not disable security, management, or required clinical services.
Expected outcome: Battery consumption reflects normal Lumify operation rather than excessive unrelated device activity.
6. Check Display and Device Operating Conditions
Confirm the display is not unnecessarily set to an extreme brightness level and that the device is not operating in an unusually hot environment.
Assess whether a case, mount, or position is trapping excessive heat.
Expected outcome: The mobile device operates under normal thermal and display conditions.
7. Inspect the Lumify Connection
Verify the transducer USB connection is secure and the application recognizes the transducer normally.
Repeated connecting, disconnecting, application relaunching, or abnormal USB behavior can complicate battery-drain reports.
Expected outcome: Lumify operates normally without repeated reconnection or communication faults.
8. Compare With a Known-Good Device
When available, operate the same Lumify transducer on another known-good compatible mobile device under comparable conditions.
Expected outcome: The comparison shows whether abnormal battery drain follows the original mobile device rather than the transducer or application workflow.
9. Perform Controlled Runtime Verification
Begin with an adequately charged device and perform an approved nonpatient scanning test under typical conditions.
Observe for excessive heating, abnormal shutdown, or battery consumption significantly different from the known-good device.
Expected outcome: The mobile device maintains adequate stable operation for its intended workflow. If the observed drain is normal and reproducible on comparable devices, no repair may be necessary.
10. Escalate Confirmed Abnormal Battery Performance
If the original device continues to drain unusually quickly after charger, background activity, environmental, and comparison checks, remove it from clinical use.
Expected outcome: A potentially deteriorated mobile device battery or internal power problem is referred for qualified evaluation.
If the Problem Persists
External charging and operating causes have been ruled out. Remaining possibilities include degraded battery capacity, mobile-device power-management faults, internal charging problems, software-related excessive power consumption, or other service-level device conditions.
Remove the mobile device from service, label it Out of Service, and send it for repair or bench evaluation. Evaluate it using approved device-manufacturer and Philips guidance as applicable. Battery replacement or internal mobile-device repair should be performed only by qualified personnel.
Before return to clinical use, confirm normal charging, stable Lumify operation, acceptable runtime for the facility's intended workflow, and absence of abnormal heating.
Clinical Use Tip
For portable ultrasound, battery condition is part of equipment readiness; verify adequate charge before taking Lumify into an examination where immediate replacement may be difficult.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Clinical staff reported that the Lumify mobile device battery was draining rapidly and could not complete normal scanning sessions."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering confirmed abnormal battery loss on the original mobile device while the same transducer operated normally on a known-good compatible device."
Resolution
What action was taken.
Example:
"Clinical Engineering removed the affected mobile device from service and verified normal Lumify operation and runtime using an approved replacement device."
Helpful Details to Include (If Known)
- Starting and ending battery levels
- Approximate scanning activity during test
- Whether rapid drain occurs outside Lumify
- Charger and cable tested
- Battery-health information
- Mobile device temperature
- Background applications observed
- Display settings
- Known-good device comparison
- Any unexpected shutdown
- Final equipment status
Final Thought
Battery complaints should be verified under controlled conditions. Check charging hardware, device health, background load, and environment before assuming battery failure, then escalate confirmed abnormal power behavior appropriately.
That is successful troubleshooting.