From Health 201FailSystems

how automated healthcare fails, how you'd know, and what to do at each tier — every claim sourced, reviewed continuously


Incident

LATITUDE Clarity server software can hold back AF Burden alerts from LUX-Dx implantable cardiac monitors

Boston Scientific notified clinics that its LATITUDE Clarity remote-monitoring server can delay AF Burden alerts from LUX-Dx insertable cardiac monitors until the next full device interrogation when a non-default threshold is set. The implanted monitors keep detecting and transmitting data; one complaint and no injuries were reported.

Fact-checked 11 November 2026

TierThe sources document delayed alert notification under one configuration but no change in how care was delivered. How tiers are assigned.

What happened

In an August 2026 Urgent Medical Device Correction, Boston Scientific said that when the AF Burden alert threshold is set to '>0 hours per day' (a non-default configuration), the LATITUDE Clarity server does not convert the daily device check into a full device interrogation as intended. Without a full interrogation the system cannot evaluate the alert, so notification of an AF Burden alert may be delayed until the next full interrogation, which is triggered by another alert, a scheduled remote follow-up, or a patient- or clinic-initiated interrogation. The company said the implanted monitor keeps detecting AF, storing data and transmitting device data. Boston Scientific reported one complaint and no patient injuries or deaths, and said a server software update is planned. Until then it advised changing the threshold to another setting or enabling AF Event alerts with a minimum duration such as 2 minutes, and does not recommend replacing implanted monitors. It said delayed notification may delay clinical evaluation or treatment of an atrial arrhythmia, while the most serious consequences remain hypothetical. FDA's recall database lists the correction as Class 2 (Z-3081-2026), initiated 6 August 2026 and posted 2 September 2026, with software design as the cause.[1,2]

Documented harm

None documented (one complaint; no injuries or deaths reported, per Boston Scientific and FDA).

What it teaches

  • In remote monitoring, a working sensor does not guarantee a timely alert; the server-side path that turns data into a notification can fail silently.
  • Non-default alert configurations can follow code paths that are tested less, so clinics should know which settings deviate from defaults.
  • Two independent alert mechanisms for the same condition give a fallback when one path silently stops.

Sources

  1. Class 2 Device Recall LUX-Dx Insertable Cardiac Monitor System, LATITUDE Clarity server software (Z-3081-2026). U.S. Food and Drug Administration (Medical Device Recalls database), 2 September 2026. Primary Dataset · link checked 2026-11-02
  2. Product Advisory – Potential delayed AF Burden Alert notification from LATITUDE Clarity (Field Action 97627645A-FA). Boston Scientific, August 2026. Supporting Guidance · link checked 2026-11-02

All incidents · Devices · Human handoff

Information only, not advice. FailSystems is an aggregation and synthesis of published sources. It is not consulting, engineering, legal, regulatory or medical advice, and using it creates no professional relationship. Health systems are complex and no approach fits every organisation: anything you adopt is your own decision, at your own risk, and should be checked against the current official sources and by qualified people who know your setting. Full disclaimer.

Dealing with an incident right now? This site is a reference, not an incident-response service. Activate your organisation's emergency operations plan and incident command, and: