Digest — 2026-09-13, The Clinical
One thing crossed the escalation bar. It is small in isolation and belongs to a standing charter rule that treats Amulet 360 as escalation-worthy on its own: "anything at all, until it launches."
1. Abbott revised the Amulet's IFU on 27 August — a contraindication change and a new pre-deployment check
openFDA shows a new PMA supplement, P200049/S021, decided 2026-08-28. It modifies a contraindication and adds a landing-zone-to-pulmonary-artery assessment, described in the agency's own record as being "to reduce the risk of pulmonary artery injury."
What is and is not established:
- This is a supplement to the current Amulet's PMA (P200049). It is not confirmed to be Amulet-360-specific — nothing in the record names the 360 by device model.
- It escalates anyway, independent of the 360 question, because your charter separately flags any guideline/IFU change that affects how you should speak about a device — and this is exactly that: a labeling change touching a contraindication and adding a required pre-deployment imaging check.
- The verbatim revised IFU language has not been read. What is in the corpus right now is the agency's own summary framing ("to reduce the risk of pulmonary artery injury"), not Abbott's actual contraindication text or the assessment's specific criteria. Do not repeat a device-specific instruction from this digest — the next run's highest-value single retrieval is reading S021's actual IFU/labeling text.
A second, purely administrative thing resolved alongside this, worth knowing so a stale number doesn't surface later: this corpus has carried an open, unexplained discrepancy since 2026-08-30 over whether P200049 has 19 or 20 supplements. It's neither — it's an artifact of how openFDA's own results.total field behaves. Two queries against the exact same PMA, run minutes apart with different query shapes, returned totals of 20 and 21. That's not new data arriving mid-session; it's the database's count metadata being unstable depending on how you ask. Closed as a known instrument quirk, not a real change in supplement count. One live gap from this: supplements S019 and S020 have unknown contents — worth a look next time someone's in openFDA for Amulet.
→ substrate/clinical--amulet-360
Also written this run, below the bar
A companion Abbott Assert-IQ study, read for the first time after six failed attempts. The paper this corpus has been trying to reach since 2026-08-30 (Europace 2026 Suppl. 1, PMC13300832) finally came through — not via PMC (still reCAPTCHA-blocked) or Europe PMC (still 429), but via a different NCBI route entirely. It's an Abbott-funded companion to the pause-false-positive work already in this corpus: 4,042 Assert-IQ devices, AF alert burden down 41%, pause alert burden down 83%.
This is not the number you're actually waiting on. It's a burden/volume reduction, not an adjudicated positive-predictive-value figure. The open question — does Abbott's very good pause-PPV number (0.01, from the Kamsani analysis) hold up in newer-generation devices — is still open. This paper makes it somewhat more likely the answer stays favorable, but it doesn't answer it.
→ substrate/clinical--icm-false-positive-evidence
The CY2027 remote-monitoring comment window closes tomorrow, 14 September. No news here — checked directly against CMS's own page again this run and nothing changed. Flagging only because of the date: after tomorrow, this window is closed for good, same as the SaMS window closed on 31 August. Scope is unchanged — it still doesn't reach the CIED codes (93293–93299) your Vector work bills under.
→ substrate/clinical--cms-cy2027-remote-monitoring
VIRTUES may or may not be built on Medtronic hardware. A vendor marketing case study (not CANet, not ESC) describing what reads as the same programme mentions Medtronic-implanted patients by name. It's one secondary source, and it doesn't settle whether the ESC-reported trial enrolled across vendors or just one. Filed as a lead, not a fact — the question of whether VIRTUES is a safety citation you can use broadly, or a single-vendor result, is still open.
→ substrate/clinical--virtues-virtual-cied-followup
Instruments
Two new retrieval blocks worth knowing about if you ever want a primary regulatory document yourself: regulations.gov now refuses this fleet's fetches outright (HTTP 403), and federalregister.gov's document pages now bounce through a bot-check wall instead of loading directly — both worked as recently as early August. Neither is expected to matter for anything you'd look up personally, but it means this corpus's own retrieval got a little more constrained this month.
PMC13300832 was finally read (see above) — worth noting only because it had failed six straight times before this run, via a route (NCBI's own efetch service) not previously tried.