Weekly External PMS Digest (FDA) — Feb 6–13, 2026

1) What changed this week (with direct source links)

A. Recalls / Early Alerts (High-priority external signals)

1. Glucose monitor sensor recall (classified as Class I) — Abbott FreeStyle Libre 3 / Libre 3 Plus
   URL: https://www.fda.gov/medical-devices/medical-device-recalls-and-early-alerts/glucose-monitor-sensor-recall-abbott-diabetes-care-removes-certain-freestyle-libre-3-and-freestyle
   Why it matters: This is explicitly treated as a potentially high-risk issue and updated to Class I.

2. Detachable coil system recall — J&J MedTech / Cerenovus Cerepak detachable coil system
   URL: https://www.fda.gov/medical-devices/medical-device-recalls-and-early-alerts/detachable-coil-system-recall-jj-medtechcerenovus-inc-remove-cerepak-detachable-coil-system
   Why it matters: Neurovascular devices and implantables often trigger stricter internal escalation and CAPA linkage when relevant.

3. Early Alert — Heart pump issue (Abiomed)
   URL: https://www.fda.gov/medical-devices/medical-device-recalls-and-early-alerts/early-alert-heart-pump-issue-abiomed
   Why it matters: “Early Alert” items are exactly the kind of signal that auditors will ask how you monitor and document.

4. Emergency response safety kit recall (classified as Class I) — Airlife Broselow Pediatric Emergency Rainbow Tapes & related items
   URL: https://www.fda.gov/medical-devices/medical-device-recalls-and-early-alerts/emergency-response-safety-kit-recall-airlife-removes-certain-broselow-pediatric-emergency-rainbow
   Why it matters: Kit/labeling/configuration issues can be relevant beyond the named SKU if your products rely on similar packaging, IFU controls, or kit assembly steps.

5. Class 2 Device Recall — Philips Azurion systems (database record)
   URL: https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfRES/res.cfm?id=218253
   Why it matters: The FDA recall database record is the “hard proof” artifact many RA/QA teams prefer for verification and citation.

B. Safety communications (clinical / field risk signals)

6. Risk of false positive blood lead test results with certain capillary blood collection tubes used with Magellan / LeadCare systems (updated)
   URL: https://www.fda.gov/medical-devices/safety-communications/risk-false-positive-lead-test-results-certain-capillary-blood-collection-tubes-used-magellan
   Why it matters: This is the kind of cross-product interaction risk (collection device + analyzer workflow) that can affect downstream users—even when you’re not the manufacturer of the primary test system.

C. Regulatory / inspection-process change (audit-facing signal)

7. QMSR / inspection process update (inspection program change reference)
   URL: https://www.fda.gov/medical-devices/postmarket-requirements-devices/quality-management-system-regulation-qmsr
   Why it matters: FDA notes a shift in the inspection process they use (compliance program update). For RA/QA leaders, this is a “regulatory change signal” worth logging with a short applicability note.

2) Patterns worth discussing (what an RA/QA team can do with this)

Pattern 1 — “External signals” are increasingly about system interactions and configuration risk

This week includes examples where harm/impact is driven by how devices behave in real workflows (alerts, sensors, accessory compatibility, kit configurations). The practical RA/QA move: make sure your review log captures why it’s relevant or not to your specific intended use, user environment, interfaces, and accessories.

Pattern 2 — Proof of review matters as much as review itself

Auditors rarely accept “we check the FDA site.” They want evidence: what you saw, when you captured it, when you reviewed it, what you decided, and what you did next. That’s the exact gap an External PMS Evidence Pack is meant to close.

3) What to do this week (action checklist you can actually execute)

• Triage each signal above as High / Medium / Low relevance to your device family (with 1–3 sentence rationale).

• If any signal is relevant, record at a minimum:

  • Published date (FDA)

  • Captured date (your system)

  • Reviewed date (your team)

  • Decision + rationale

  • Action owner + due date (if applicable)

• Export the week as an audit-ready artifact (PDF/ZIP) and file it in your QMS/eQMS as “External PMS Review Evidence”.

4) Why does this belong in your External PMS system (not a newsletter)

A weekly digest is useful only if it feeds a repeatable compliance outcome:
Signals → Relevance Review → Decision Record → Exportable Evidence Pack
That last step is what turns “information” into “inspection-ready proof.”