FDA Early Alert: Philips Lumify Ultrasound App May Require Probe Re-registration and Interrupt Prehospital Scanning (October 2026)

FDA Early Alert: Philips Lumify Ultrasound App May Require Re-registration and Interrupt Prehospital Scanning

Published: 19 October 2026, 19:32 | Category: Recalls and Safety Announcements

On 9 October 2026, the US Food and Drug Administration (FDA) issued an early alert regarding the Philips Lumify diagnostic ultrasound system. The iOS and Android applications may, without warning, require users to re-register probes that were already registered. Scanning must wait until registration is complete, and registration depends on Wi-Fi or cellular signal. Risks are higher in prehospital and field settings. As of 29 September 2026, Philips had reported 8 serious injuries and 4 deaths. The FDA recommends using the device only where signal is available and keeping backup ultrasound ready.

What happened

On 9 October 2026, the FDA Center for Devices and Radiological Health (CDRH) issued an early alert for the Philips Lumify diagnostic ultrasound system. Early alerts are used to flag device issues that may present a high risk. The FDA stated that Philips sent a letter to affected customers on 24 September 2026 recommending updates to the instructions for use.

The issue: app and probe registration

According to the FDA summary, the Lumify Android or iOS app may fail to recognize a probe that was previously registered and may display a re-registration requirement without warning before point-of-care use. Scanning is blocked until registration is completed. The registration process requires Wi-Fi or cellular signal. Even when the hardware and probe are at hand, the software can lock the scanning function.

Highest-risk settings

The FDA noted that Lumify users in ambulances, aircraft and field environments face higher risk because network signal is more limited in those locations. Philips has received reports that unexpected re-registration events prevented scanning in prehospital environments and delayed patient care; these events occurred in locations without Wi-Fi or cellular signal.

Affected scope

The FDA page lists affected software versions including iOS 2.X, 5.0, 5.1.2 and 5.1.3, and Android 1.X, 3.X, 4.X, 5.1 and 5.1.1. The Lumify system consists of a Philips probe, the Lumify app and a compatible Android or iOS device. It is intended for diagnostic ultrasound imaging and blood flow analysis and is transportable and may be used outside the hospital, such as in ambulances. The issue is not limited to a single host device; it follows app version and probe registration status.

FDA recommendations

The actions recommended by the FDA and Philips include:

• Use the device only in areas where Wi-Fi or cellular signal is readily available, unless a backup ultrasound device is within reach.
• Always have a backup ultrasound device or other examination method ready.
• Forward Philips' customer letter to all users and post a notice next to affected devices for easy reference.

The FDA stated that it is still evaluating this potential high-risk issue and that the page will be updated as important information becomes available.

Additional connectivity issue

The same early alert also noted that when the Lumify probe USB cable is connected to the user's tablet or phone, the connection may disconnect or be unstable, affecting continuous operation and causing delays in diagnosis and treatment. Philips stated that it is evaluating the cause and seeking solutions and will inform customers subsequently.

Injury reports and next steps

As of 29 September 2026, Philips had reported 8 serious injuries and 4 deaths related to this issue. The FDA stated that Philips is developing a software update and will issue a follow-up notification when the update is available, describing the actions to be taken. For users, until the update is implemented, backup equipment and network availability are the practical fallback measures.

Sources and scope notes

Sources:

• US Food and Drug Administration (FDA) — Early Alert: Diagnostic Ultrasound System Issue from Philips Ultrasound, https://www.fda.gov/medical-devices/medical-device-recalls-and-early-alerts/early-alert-diagnostic-ultrasound-system-issue-philips-ultrasound, published 9 October 2026.
• US Food and Drug Administration (FDA) — CDRH New: News and Updates, https://www.fda.gov/medical-devices/medical-devices-news-and-events/cdrh-new-news-and-updates, entry dated 9 October 2026.

Verification scope and access date: The above pages were accessed on 19 October 2026 to verify the alert text, affected software versions, recommendations and injury report figures. The original Philips customer letter was not accessed.

Scope note: This article is an interpretation of publicly available regulatory information. It does not constitute a conclusion or commitment regarding any specific product, company or registration application. The official text prevails, and information may change with subsequent official updates.

AIMEILI Regulatory Interpretation

For regulatory affairs teams, this early alert highlights that software and connectivity dependencies can be safety-critical elements of a medical device, not only IT features. A probe re-registration function that can block scanning affects essential performance and safe use in the intended environment. Manufacturers of ultrasound and other connected devices should assess whether similar authentication, registration or cloud-dependent functions are adequately covered in the risk management file, software lifecycle processes, usability engineering, cybersecurity controls and labelling.

The alert also reinforces the need for robust change control. App behavior, registration logic, connectivity requirements and instructions for use should be evaluated under the applicable change assessment and regulatory notification requirements in each market. Where a device is already distributed, field safety communications and customer notices should be consistent with local post-market surveillance and reporting obligations. The FDA characterizes this as an early alert, not a final recall determination; nevertheless, the reported injuries and deaths underscore the potential severity of access-blocking software events.

Business Impact

Global manufacturers, distributors, CROs and regulatory affairs teams should consider the following actions:

• Fleet-level risk assessment: Identify devices and app versions with connectivity-dependent registration or authentication, and prioritize prehospital, field, ambulance and aircraft use cases.
• Customer and distributor communications: Ensure that field notices, instructions for use updates and posted warnings reach all users, including emergency medical services and remote-site operators.
• Clinical trial and CRO operations: For studies using point-of-care ultrasound in low-signal environments, include backup imaging provisions, site training and protocol safeguards to avoid delayed or missed assessments.
• Supply continuity and backup planning: Advise customers to maintain backup ultrasound or alternative examination methods until a validated software update is implemented.
• Post-market surveillance and CAPA: Track complaints involving app registration, connectivity loss and cable disconnection, and evaluate whether reporting thresholds are met in relevant jurisdictions.

AIMEILI view: the practical lesson is that registration status, network dependency and software update readiness should be treated as part of device safety and business continuity planning, especially for transportable and prehospital ultrasound systems.