Product Compliance And Certification For Wearable Medical Device In Brazil

Scope and evidence must be confirmed before any paid tests or filings.

Start with the intended claim, not the wristband

A wearable is not automatically a medical device because it measures a body signal, nor is it automatically exempt because it resembles a fitness tracker. Freeze the Brazilian intended purpose across packaging, app screens, alarms, advertising and clinical claims. Decide whether it only supports general fitness or is intended to diagnose, prevent, monitor or manage disease or a medical condition. ANVISA applies the device rules to the medical purpose, not the marketing name.

A connected wearable can trigger several independent regimes. The ANVISA product filing does not substitute for ANATEL radio homologation, applicable SBAC conformity assessment or personal-data compliance. The decisions below are classification prompts, not predetermined authorizations.

Wearable risk-classification decision table

Product/claim scenario	Key classification question	Practical consequence
Step counter or general fitness trend, with no medical claim	Do all app prompts, dashboards and commercial materials remain within general wellness rather than diagnosis or clinical monitoring?	A non-device conclusion may be defensible only after documented claims review; Bluetooth and privacy rules may still apply.
Wearable ECG, blood-pressure or oxygen trends offered for clinical monitoring	Is this active diagnosis/monitoring under Annex I Rule 10, and can a physiological variation create immediate danger?	Rule 10 commonly points to Class II, but its critical-parameter/urgent-danger branch points to Class III; never classify from sensor type alone.
Algorithm that issues diagnostic/therapeutic recommendations or high-stakes alarms	Is the software an accessory, integrated device software or independently regulated SaMD? What harm could an incorrect output cause?	Assess Rule 11 and RDC 657/2022 where applicable; depending on decision impact, software may fall into Classes II, III or IV.

Route gate: Under RDC 751/2022, Classes I–II use ANVISA notification; Classes III–IV require registration. An application is not the same as permission to sell. Record the applicable rule, the highest applicable risk, the intended user and the response expected to an alarm. Devices taking measurements are not all Class II.

Rule 11 also places other qualifying SaMD in Class I. Under RDC 657/2022, embedded software within a regulated medical device is outside that resolution’s separate SaMD route; its functions still need to be addressed in the device’s regulatory evidence. Do not treat every medical app or firmware update as a separately filed SaMD.

Brazilian regulatory layers: applicability matrix

Regulatory layer	Wearable trigger	Required decision / proof
ANVISA medical-device route	Medical purpose, connected sensor and intended clinical use	Classify complete system and accessories under RDC 751/2022; obtain notification (I–II) or registration (III–IV) through an eligible Brazilian holder.
Medical software / SaMD	App or cloud interprets signals, makes clinical decisions or monitors physiological processes	Map firmware, app and cloud functions; decide whether software is integral/accessory or separately regulated under RDC 657/2022; apply Rule 11 as relevant.
SBAC / INMETRO conformity	Electromedical equipment covered by compulsory certification rules	Check whether the model falls under RDC 549/2021 and ANVISA IN 283/2024; obtain the applicable accredited-body certificate before filing when required. Battery power alone is not a universal trigger.
ANATEL telecom homologation	Bluetooth, Wi-Fi, cellular or other covered radio/telecom function	Confirm homologation for the marketed product/configuration under Resolution 715/2019; a foreign radio report or medical registration is not a substitute.
Manufacturer / Brazilian operator	Overseas legal manufacturer, local holder, import and distribution activities	Confirm local applicant, manufacturer authorization and applicable AFE; assess ANVISA GMP/CBPF, especially for Class III–IV.
LGPD / health data	Identifiable ECG, glucose, SpO₂ or other health-related readings, app accounts and cloud sharing	Identify controller/processors, legal basis for sensitive data, security, retention and international transfers; ANVISA clearance does not authorize data processing.

Standards are not approvals. RDC 848/2024 sets essential safety/performance requirements. ANVISA-recognized technical standards help demonstrate conformity but do not themselves certify a device; compulsory SBAC certification is a distinct, model-specific requirement.

Accessory boundary: under Article 2, paragraphs 10–11 of RDC 751/2022, certain accessories made by the manufacturer exclusively to integrate its own already regularized devices, and covered in the technical dossier, do not require a separate notification or registration. This is a conditional exception, not a blanket exemption for chargers, straps or independently marketed accessories.

Wearable-specific evidence to assemble

Prepare one controlled system description covering the wearable, charger, app, firmware, backend and intended users. For each claimed medical function, connect the evidence to the hazard and to the actual commercial model:

Claims and classification: Portuguese-facing claims inventory, intended population/environment, clinical workflow, Annex I rule justification, and whether a clinician or layperson acts on alerts.
Sensor and human factors: accuracy and clinical/performance evidence for claimed parameters; motion/placement, skin contact and population limitations; alarm thresholds, missed alarms and false alarms where relevant.
Electrical and materials: battery/charger safety, electromagnetic compatibility and wireless coexistence as applicable; skin-contact biocompatibility, cleaning and reuse assumptions; identify relevant standards without assuming every IEC test is legally compulsory.
Digital chain: hardware/firmware/app/cloud version map, data loss and latency behavior, cybersecurity, algorithm validation, software changes and backup/fail-safe behavior.
Market documentation: technical dossier under RDC 751/2022, manufacturer authorization to the Brazilian holder, local operating permissions, applicable CBPF and SBAC proof, ANATEL product evidence and Portuguese labeling/IFU.

Dossier versus filing: for Class I–II notifications, Article 56 of RDC 751/2022 requires the holder to keep the technical dossier current and available for inspection; the whole dossier is not routinely submitted with the notification. The specific notification form, foreign-manufacturer authorization and applicable compulsory-certification evidence remain separate submission checks under Article 13.

Brazil launch gates and accountable parties

Sequence is a dependency map, not a promised processing schedule:

Lock claims and variants. Decide whether continuous monitoring, critical alerts, home use and clinical decision-support are claimed; list every SKU, radio module and app version.
Document classification. Apply RDC 751/2022 Annex I (notably Rules 10 and 11 where applicable); decide how integrated and standalone software will be regulated; flag borderline cases for a formal regulatory assessment.
Appoint the Brazilian responsible entity. Confirm authorized local applicant/holder and AFE for relevant activities, manufacturer authorization, and the GMP certificate/application pathway when relevant. Class III–IV registration approval depends on the published ANVISA CBPF.
Complete parallel testing and approvals. Obtain any mandatory SBAC certificate and ANATEL homologation for the precise marketed configuration; prepare technical evidence, Brazilian Portuguese labeling and IFU.
Release only after all applicable gates. Verify ANVISA regularization status/number, radio homologation, importer readiness and traceability; implement complaint, incident and field-action controls.

Portuguese labels, instructions and traceability

RDC 751/2022 requires labels and instructions in Portuguese. For regulated equipment, Article 49 addresses durable identification of the product/model, legal manufacturer or brand, ANVISA number and serial/traceability identifier, with limited size-based adjustments. The app must not quietly expand the authorized medical indication.

Consumer/home-use wearable: do not rely on online-only instructions. Article 54 prohibits exclusive non-printed instructions for equipment indicated for general home use or operation by laypeople. Check an appropriate printed IFU route.
Home/lay-use medical apps: for a separately regulated SaMD, check the app menu language as well as the paper IFU. RDC 657/2022 Article 6 permits English or Spanish menus only when all specified conditions are satisfied, including that the SaMD is not intended for lay users or home use. Do not assume an English-only consumer interface is acceptable.
If electronic instructions are additionally offered, control the version/product link, access and no-cost paper-request mechanism where applicable (Articles 50–53).
Place intended users, contraindications, operating limits, warnings about non-diagnostic readings where justified, alarms and maintenance instructions consistently across package, app and IFU.
Check applicable UDI phase-in by risk class and production date, as well as ANATEL marking requirements for the radio configuration; neither mark replaces ANVISA regularization.

Changes that can break an existing clearance

Reassess before release rather than assuming an existing notification/registration covers every update:

New claim: replacing fitness insights with arrhythmia detection or clinical triage can change device status, classification and evidence.
New algorithm: changing thresholds, AI models or cloud logic can change risk, software scope, verification and ANVISA variation category.
New hardware: replacing BLE chip, antenna, battery, charger or skin-contact material can affect ANATEL/SBAC scope and safety evidence.
New go-to-market setup: changing legal manufacturer, Brazilian holder, importer or package/IFU requires reviewing authorizations, regulatory filings and postmarket accountability.

For general medical-device filing mechanics rather than wearable interfaces, see medical-device compliance in Brazil. The classification cannot be finalized without the approved claims, full system architecture, intended users, clinical impact of failures and exact product/radio configurations.

Official regulatory sources

Primary sources (consult current consolidated requirements before submission):

Wearable-specific questions

Does a Bluetooth fitness watch need ANVISA approval?

Not solely because it uses Bluetooth or measures pulse. Evaluate the Brazilian medical intended purpose and all claims; an ordinary wellness product may fall outside medical-device regularization, while ANATEL requirements can still apply to its radio.

Is continuous ECG monitoring automatically Class II?

No. Rule 10 distinguishes ordinary active monitoring from critical vital-parameter monitoring where changes may pose immediate danger, potentially Class III. Intended patients, alarms and clinical setting matter.

Can a cleared sensor use any diagnostic AI app?

No. Evaluate the intended medical function and whether the algorithm is integrated, an accessory or SaMD. Rule 11 and RDC 657/2022 may alter the software risk class and the authorized system scope.

Can we launch with CE/FDA documents and a Bluetooth module certificate?

Those may support evidence, but do not automatically replace Brazilian ANVISA regularization, any required SBAC certificate or ANATEL homologation of the covered product/configuration.

Can a home-use wearable provide only a QR-code manual?

Not when Article 54 of RDC 751/2022 prohibits instructions being exclusively non-printed for general home-use/lay-operated equipment. Prepare compliant Portuguese labeling and an appropriate non-digital instruction provision.