How does DEPLOY track the Withings ScanWatch ECG recall?
The Withings ScanWatch FDA Class-2 recall operates as a canonical worked example of incident-tracking at FDA medical-device primary-source verification depth. Per Agent A IncidentStatusEvent substrate at [/incidents/withings-scanwatch-ecg-recall-2022](https://registry.deploy.report/incidents/withings-scanwatch-ecg-recall-2022): the U.S. Food and Drug Administration (FDA) issued a Class-2 recall on the Withings ScanWatch ECG feature in 2022. The recall operates at FDA medical-device primary-source verification depth (tier 2 primary-FDA-database per [DEPLOY's 9-tier source-quality rubric](/explainers/source-quality-rubric)); the recall sub-tier is structurally distinct from the CPSC consumer-product-safety sub-tier exercised in the [Fitbit Ionic burn recall narrative](/explainers/how-deploy-tracks-the-fitbit-ionic-burn-recall). CRITICAL within-entity verification-state framing: the ScanWatch is a multi-feature device with FDA-cleared ECG + SpO2 (K201456) intersecting with the regulatory recall framing; per [verified-vs-claimed at within-entity granularity](/explainers/verified-vs-claimed-within-entity), the recall affects the ECG feature specifically while other ScanWatch features remained available; the broader [Withings entity](/explainers/what-is-withings) continues at verified-shipped state across the ScanWatch + ScanWatch 2 + ScanWatch Nova product line. Per [DEPLOY's biometric cluster framework](/explainers/biometric), the recall operates within the hybrid analog watch archetype that Withings anchors. This piece documents the catch as framework-in-action worked example: FDA medical-device incident-tracking discipline + within-entity feature-granularity verification-state distribution + multi-tier primary-government-record source-quality demonstration operating at editorial-anchor depth.
FDA Class-2 recall
ScanWatch ECG feature; temporary or medically reversible adverse consequences classification
ECG affected; other features available
Within-entity feature-granularity verification-state distribution
Tier 2 primary-FDA-database
FDA medical-device sub-tier verification depth
FDA sub-tier vs CPSC sub-tier vs ITC sub-tier
Multi-tier primary-government-record sub-tier diversity across biometric incident series
Withings ScanWatch hybrid analog archetype
Cohort positioning per biometric cluster framework
Mid-2026
Snapshot date
The Withings ScanWatch ECG recall: FDA medical-device sub-tier of primary-source verification
In 2022, the U.S. Food and Drug Administration (FDA) issued a Class-2 recall on the Withings ScanWatch ECG feature. Per Agent A IncidentStatusEvent substrate, the recall operates at FDA medical-device primary-source verification depth, structurally distinct from the CPSC consumer-product-safety primary-source sub-tier exercised in the Fitbit Ionic burn recall narrative.
Per DEPLOY's incident-tracking discipline (see /methodology/how-we-track-safety-incidents), the framework discipline operates at multiple verification axes simultaneously:
- FDA medical-device primary-source verification at tier 2 primary-FDA-database per DEPLOY's 9-tier source-quality rubric. The FDA Class-2 recall classification + recall identification number + scope (feature affected + remediation framework + classification rationale) operate at FDA primary-source verification depth.
- Within-entity feature-granularity verification-state distribution: the ECG feature operates at recalled state during the recall window; other ScanWatch features (SpO2 + heart rate + sleep tracking + step counting) remained available; the broader Withings entity continues at verified-shipped state across the broader ScanWatch product line + subsequent generations (ScanWatch 2 + ScanWatch Nova).
- Multi-tier primary-government-record sub-tier demonstration: the recall operates at FDA medical-device sub-tier within tier 2 primary-FDA-database; structurally distinct from the CPSC consumer-product-safety sub-tier exercised in the Fitbit Ionic narrative + structurally distinct from the ITC patent-trade sub-tier exercised in the forthcoming Amazfit Helio Ring ITC investigation narrative. Three distinct primary-government-record sub-tiers operationalized editorially across the biometric incident series.
The verified state per FDA primary source
The recall operates at FDA primary-source verification depth. Per Agent A IncidentStatusEvent substrate, the verified incident scope:
- Affected device: Withings ScanWatch ECG feature. The ScanWatch is a hybrid analog watch with embedded digital biometric sensors + small OLED display per the Withings entity anchor.
- Recall classification: FDA Class-2. Per FDA's recall classification framework, Class-2 designation indicates the use of, or exposure to, the product may cause temporary or medically reversible adverse health consequences (distinct from Class-1 reasonable probability of serious adverse health consequences or death; distinct from Class-3 use or exposure unlikely to cause adverse health consequences).
- Affected feature: ECG monitoring specifically. Per DEPLOY's biometric cluster framework, ECG is genuinely cleared across the biometric cohort (Apple Watch + Pixel Watch + Fitbit + Withings + Samsung carry substantial clearance breadth at the ECG layer); the ScanWatch ECG feature operates within this clearance scope at FDA 510(k) K201456 verification depth per Agent A's existing ScanWatch entity scope.
- Cross-property registry depth: incident record at /incidents/withings-scanwatch-ecg-recall-2022 (200 LIVE registry verification); entity scope at Withings registry company + ScanWatch registry model + entity anchor at /explainers/what-is-withings.
Per cap-flag-as-trust-signal, specific verification axes operate at primary-source depth + others at cap-flag depth pending additional primary-source confirmation:
- Verified per FDA primary source: Class-2 recall classification + affected feature (ECG) + recall scope at the feature level + Withings IR-confirmed recall acknowledgment.
- Cap-flagged pending additional primary-source verification: specific recall identification number + specific units affected + specific remediation timeline + specific recall completion rate cap-flagged pending FDA recall database primary-source confirmation + Withings IR-confirmed remediation framework. The Agent A IncidentStatusEvent substrate carries the load-bearing structural framing; per-claim verification axes within the IncidentStatusEvent operate at structurally distinct verification depths.
Within-entity feature-granularity verification-state distribution at Withings ScanWatch
Per verified-vs-claimed at within-entity granularity, the framework discipline operates at within-entity verification-state distribution at the feature layer within a single device. The Withings ScanWatch ECG recall illustrates the framework discipline operating at feature-granularity:
ECG feature (recalled state during recall window): the FDA Class-2 recall affects the ECG monitoring feature on Withings ScanWatch. Per cap-flag-as-trust-signal, specific recall window dates + scope + remediation framework operate at Agent A IncidentStatusEvent depth pending additional Withings IR + FDA primary-source confirmation.
SpO2 feature (verified-shipped + ongoing): SpO2 monitoring across the ScanWatch line operates at verified-shipped state continuously. Per DEPLOY's biometric cluster framework, SpO2 is part of the substantial-cleared-for-size FDA posture Withings anchors at the hybrid analog watch archetype.
Other features (verified-shipped + ongoing): heart rate monitoring + sleep tracking + step counting + activity tracking + Withings+ subscription advanced health insights all operate at verified-shipped state continuously.
Within-entity verification-state distribution operates simultaneously. Per verified-vs-claimed at within-entity granularity, the framework discipline reads the ScanWatch device at verified-shipped state + reads individual features at structurally distinct verification states (ECG at recalled state during recall window; SpO2 + heart rate + sleep + step + activity + Withings+ subscription features at verified-shipped state continuously). Same device. Multiple verification states at feature granularity.
The framework parallels the Whoop BPI saga within-entity feature-granularity worked example (verified-shipped device + unresolved-FDA-dispute feature simultaneously) + the Apple Watch SpO2 saga within-entity verification-state across dates + jurisdictions (same device + four verification states varying by date + jurisdiction). The Withings ScanWatch ECG recall extends the within-entity feature-granularity pattern to a third canonical worked example demonstrating the framework discipline operating at feature-granularity within a single device.
Multi-tier primary-government-record sub-tier demonstration
Per DEPLOY's 9-tier source-quality rubric, tier 3 primary-government-record encompasses multiple primary-source sub-tiers across distinct regulatory agencies. The biometric incident narrative series operationalizes three distinct sub-tiers editorially:
FDA medical-device sub-tier (this narrative): Withings ScanWatch ECG Class-2 recall operates at FDA medical-device regulatory primary-source verification depth. FDA 510(k) database + recall database + Warning Letter database + premarket approval database operate within this sub-tier. The FDA's medical-device classification framework + clearance pathway + post-market surveillance operate at structurally distinct verification depth from other tier 3 primary-government-record sub-tiers.
CPSC consumer-product-safety sub-tier (Fitbit Ionic narrative): Fitbit Ionic burn recall operates at CPSC consumer-product-safety regulatory primary-source verification depth. CPSC recall database + injury report database + remediation framework operate within this sub-tier. The CPSC's consumer-product-safety classification framework operates at structurally distinct verification depth from FDA medical-device classification + ITC patent-trade investigation.
ITC patent-trade sub-tier (forthcoming Amazfit Helio Ring narrative): Amazfit Helio Ring ITC investigation operates at ITC patent-trade regulatory primary-source verification depth. ITC Section 337 investigation database + determination database + exclusion order database operate within this sub-tier. The ITC's patent-trade regulatory framework operates at structurally distinct verification depth from FDA + CPSC sub-tiers.
Per DEPLOY's editorial process, the three sub-tier demonstration operates at framework discipline across regulatory-source-tier diversity within a single cohort. Each sub-tier has its own primary-source database + classification framework + post-determination remediation/enforcement structure; per-claim source-quality verification reads each at its specific sub-tier primary-source verification depth rather than collapsing them into uniform tier 3 primary-government-record framing.
Why DEPLOY tracks this incident at editorial-anchor depth
Medical-device recalls operate at the framework-discipline layer where institutional partners audit at insurance underwriting + medical-device regulatory + standards body validation contexts. The Withings ScanWatch ECG recall operates at multiple framework-discipline layers:
Incident-tracking discipline at FDA medical-device sub-tier: FDA medical-device primary-source verification is load-bearing for medical-device recall claims; trade-press coverage referencing the recall must cite FDA primary-source attribution to operate at primary-source verification depth. Per /methodology/how-we-track-safety-incidents, DEPLOY's incident-tracking discipline operates the FDA + CPSC + NHTSA + agency-specific primary-source verification at the incident-record layer.
Within-entity feature-granularity verification-state discipline: the recall affects ECG feature specifically; other ScanWatch features remain at verified-shipped state. Per verified-vs-claimed at within-entity granularity, within-entity verification-state distribution operates at structurally distinct layer from device-as-a-whole verification + product-line-granularity verification.
Source-quality per-claim discipline at multi-tier primary-government-record sub-tier diversity: FDA medical-device sub-tier of tier 2 primary-FDA-database verification operates structurally distinct from CPSC consumer-product-safety sub-tier of tier 3 primary-government-record + ITC patent-trade sub-tier of tier 3 primary-government-record. Per DEPLOY's 9-tier source-quality rubric, the three sub-tier demonstration operationalizes regulatory-source-tier diversity within the biometric incident series.
Cohort positioning: per DEPLOY's biometric cluster framework, the Withings ScanWatch recall sits within the smartwatch + band cohort + within the hybrid analog watch archetype Withings anchors. The Withings entity anchor anchors the hybrid analog watch archetype + substantial-cleared-for-size FDA posture; the ECG recall operates as a within-entity feature-granularity verification-state at the affected-feature layer.
The corrections journal cross-property reference
DEPLOY's corrections journal at registry.deploy.report/corrections operates the structural incident + regulation + recall data surface across the registry property. The Withings ScanWatch ECG recall operates as an IncidentStatusEvent at the canonical corrections-data layer. This piece compounds the structural corrections data with framework-in-action narrative depth at the news-pub-lane layer.
Per DEPLOY's editorial process, cross-property credibility coherence operates across:
- Registry property: canonical IncidentStatusEvent at /incidents/withings-scanwatch-ecg-recall-2022 with structural recall data + cross-references.
- News-pub lane: this piece operating framework-in-action narrative depth + within-entity feature-granularity framing + multi-tier sub-tier demonstration.
- Methodology canonical references: cross-references to /methodology/how-we-track-safety-incidents (incident-tracking protocol) + /explainers/verified-vs-claimed-within-entity (within-entity verification-state framework) + /explainers/source-quality-rubric (multi-tier primary-government-record sub-tier diversity) + /explainers/how-deploy-tracks-the-fitbit-ionic-burn-recall (parallel CPSC sub-tier framework-in-action narrative).
The catch demonstrates the discipline operationally at editorial-anchor depth. Within-entity feature-granularity verification-state surfaces honestly + primary-source-anchored verification at the incident layer at FDA medical-device sub-tier + cohort positioning at the cluster framework layer + multi-tier sub-tier demonstration across the biometric incident narrative series + cross-property credibility coherence across registry + news-pub + methodology surfaces simultaneously.
For the canonical Withings entity anchor, see what is Withings. For the canonical registry incident record, see the Withings ScanWatch ECG recall incident at registry.deploy.report. For the parallel CPSC sub-tier framework-in-action narrative, see how DEPLOY tracks the Fitbit Ionic burn recall. For the framework discipline at within-entity feature-granularity layer, see verified-vs-claimed at within-entity granularity. For the source-quality classification at multi-tier primary-government-record sub-tier diversity, see the 9-tier source-quality rubric. For the methodology canonical references on incident tracking, see /methodology/how-we-track-safety-incidents. For the biometric cluster framework, see the biometric cluster.
| Framework axis | ScanWatch ECG (affected feature) | ScanWatch other features | Discipline layer |
|---|---|---|---|
Feature-state | Recalled state during recall window | Verified-shipped state continuously (SpO2 + heart rate + sleep + step + activity + Withings+ subscription) | Within-entity feature-granularity verification-state distribution |
Primary-source verification | FDA medical-device tier 2 primary-FDA-database (Class-2 recall classification) | FDA 510(k) K201456 ScanWatch ECG clearance + ongoing operational state | Source-quality per-claim at FDA medical-device sub-tier |
Within-entity device state | ScanWatch device continues; ECG feature in recall state | ScanWatch product line continues (ScanWatch + ScanWatch 2 + ScanWatch Nova) | Framework operates at within-entity feature-granularity |
Multi-tier sub-tier | FDA medical-device sub-tier of tier 2 primary-FDA-database | FDA medical-device sub-tier (clearance scope) + Withings IR sub-tier (commercial-deployment scope) | Multi-tier primary-government-record sub-tier demonstration |
Cohort positioning | Recalled feature within hybrid analog watch archetype | Hybrid analog watch archetype operates at substantial-cleared-for-size FDA posture | Cluster framework discipline at cohort positioning layer |
Corrections journal reference | IncidentStatusEvent at /incidents/withings-scanwatch-ecg-recall-2022 | Cross-references from /companies/withings + this narrative + entity anchor + ScanWatch product line continuity framing | Cross-property credibility coherence |
Frequently asked questions
- What was the Withings ScanWatch ECG recall?
In 2022, the U.S. Food and Drug Administration (FDA) issued a Class-2 recall on the Withings ScanWatch ECG feature. Per Agent A IncidentStatusEvent substrate at /incidents/withings-scanwatch-ecg-recall-2022, the recall affects the ECG monitoring feature specifically on the Withings ScanWatch hybrid analog watch. FDA Class-2 designation indicates the use of, or exposure to, the product may cause temporary or medically reversible adverse health consequences; distinct from Class-1 (reasonable probability of serious adverse health consequences or death) + Class-3 (use or exposure unlikely to cause adverse health consequences).
- Does the recall affect all Withings ScanWatch features?
No, the recall affects the ECG feature specifically. Per verified-vs-claimed at within-entity granularity, the framework discipline operates at within-entity verification-state distribution at the feature layer. ECG feature: recalled state during recall window. SpO2 + heart rate + sleep tracking + step counting + activity tracking + Withings+ subscription features: verified-shipped state continuously. Same device. Multiple verification states at feature granularity. The broader Withings entity continues at verified-shipped state across the ScanWatch + ScanWatch 2 + ScanWatch Nova product line.
- What does FDA Class-2 mean?
Per FDA's recall classification framework: Class-1: situation where there is a reasonable probability that the use of, or exposure to, a violative product will cause serious adverse health consequences or death. Class-2: situation where the use of, or exposure to, a violative product may cause temporary or medically reversible adverse health consequences or where the probability of serious adverse health consequences is remote. Class-3: situation where the use of, or exposure to, a violative product is not likely to cause adverse health consequences. The Withings ScanWatch ECG recall is Class-2 per Agent A IncidentStatusEvent substrate; the classification reflects FDA's assessment of the recall's health-consequences scope.
- How does this compare to the Fitbit Ionic recall?
The Withings ScanWatch ECG recall operates at FDA medical-device sub-tier of primary-FDA-database (tier 2 per DEPLOY's 9-tier source-quality rubric). The Fitbit Ionic burn recall operates at CPSC consumer-product-safety sub-tier of tier 3 primary-government-record. The two sub-tiers are structurally distinct: FDA medical-device regulates medical-device clearance + post-market surveillance + Class-1/2/3 recall classification; CPSC consumer-product-safety regulates consumer-product-safety + injury reports + remediation framework. Per-claim source-quality verification reads each at its specific sub-tier primary-source verification depth rather than collapsing them into uniform tier 3 framing.
- Why is multi-tier primary-government-record sub-tier diversity important?
Per DEPLOY's 9-tier source-quality rubric, tier 3 primary-government-record encompasses multiple primary-source sub-tiers across distinct regulatory agencies. The biometric incident narrative series operationalizes three distinct sub-tiers editorially: FDA medical-device (this narrative) + CPSC consumer-product-safety (Fitbit Ionic narrative) + ITC patent-trade (forthcoming Amazfit Helio Ring narrative). Together they demonstrate framework-in-action across regulatory-source-tier diversity within a single cohort + provide editorially substantive substrate for institutional partnership conversations where regulatory-tier discipline matters (insurance underwriting + standards body engagement + regulator awareness).
- Why document this incident as a framework-in-action narrative?
Institutional partners audit DEPLOY's framework discipline at the operational-practice layer. This piece operates at narrative-canonical depth: how the incident-tracking discipline applies (FDA medical-device primary-source verification at tier 2 primary-FDA-database); what within-entity feature-granularity verification-state distribution emerges (ECG recalled + SpO2/heart rate/sleep/step/activity verified-shipped simultaneously); what multi-tier sub-tier demonstration matters (FDA medical-device + CPSC consumer-product-safety + ITC patent-trade sub-tiers across biometric incident series); what cohort positioning matters (biometric cluster smartwatch cohort + hybrid analog watch archetype Withings anchors); what cross-property credibility coherence operates (registry IncidentStatusEvent + news-pub narrative + methodology canonical references simultaneously).
The Withings ScanWatch ECG recall framework-in-action narrative documents DEPLOY's incident-tracking discipline at FDA medical-device primary-source verification depth. 2022 FDA Class-2 recall on the Withings ScanWatch ECG feature per Agent A IncidentStatusEvent substrate at /incidents/withings-scanwatch-ecg-recall-2022. FDA Class-2 designation indicates use of, or exposure to, product may cause temporary or medically reversible adverse health consequences. Per DEPLOY's 9-tier source-quality rubric, FDA medical-device sub-tier of tier 2 primary-FDA-database verification depth is load-bearing; structurally distinct from CPSC consumer-product-safety sub-tier (exercised in Fitbit Ionic burn recall narrative) + ITC patent-trade sub-tier (forthcoming Amazfit Helio Ring narrative). Within-entity feature-granularity verification-state distribution operates: ECG feature at recalled state during recall window; SpO2 + heart rate + sleep + step + activity + Withings+ subscription features at verified-shipped state continuously. Same device. Multiple verification states at feature granularity. Third canonical worked example alongside Whoop BPI saga + Apple Watch SpO2 saga demonstrating within-entity feature-granularity discipline. Per cap-flag-as-trust-signal, residual claim categories cap-flagged pending additional primary-source confirmation: specific recall identification number; specific units affected; specific remediation timeline + completion rate; specific Withings IR-confirmed remediation framework. Cross-property credibility coherence: registry IncidentStatusEvent at /incidents/withings-scanwatch-ecg-recall-2022 + this news-pub narrative + methodology canonical references at /methodology/how-we-track-safety-incidents + /explainers/verified-vs-claimed-within-entity + /explainers/source-quality-rubric + parallel Fitbit Ionic CPSC narrative operate simultaneously. How DEPLOY verifies →
Continue reading
What is Withings?
Canonical Withings entity anchor; hybrid analog watch archetype with mechanical-digital design + substantial-cleared-for-size FDA posture + cohort-mature peer-reviewed validation depth.
Read article →
How DEPLOY tracks the Fitbit Ionic burn recall
Parallel framework-in-action narrative at CPSC consumer-product-safety sub-tier (vs FDA medical-device sub-tier this narrative); multi-tier primary-government-record sub-tier demonstration.
Read article →
Verified-vs-claimed at within-entity granularity
Framework operating at feature-granularity within a single device; Whoop BPI + Apple Watch SpO2 + Withings ScanWatch ECG sagas as parallel worked examples.
Read article →
The 9-tier source-quality rubric
DEPLOY's 9-tier source-quality classification; multi-tier primary-government-record sub-tier diversity across FDA + CPSC + ITC + USPTO + Federal Register + agency-specific databases.
Read article →
Compare alternatives
Withings ScanWatch ECG recall registry incidentWithings registry companyWithings entity anchorFitbit Ionic burn recall narrative (parallel CPSC sub-tier)