Brazil Anvisa Medical Device Registration Consultant
Before commissioning tests or an ANVISA filing, establish whether the Brazilian medical-device regime applies, which risk rule controls, who will hold the product regularization and which existing evidence genuinely answers Brazilian requirements. A consultant should turn uncertainty into a documented route decision, not promise approval.
What a pre-filing consultant decides
This advisory stage produces a classification rationale, proposed notification or registration route, prioritized gap register, evidence-reuse assessment and responsibilities. It is not the actual filing, factory certification or a guaranteed authorization. For document submission and dossier coordination, see the ANVISA registration execution service.
First gate: device status and intended purpose
Start with the manufacturer’s exact Brazilian intended-use statement and claims, not a foreign certificate or marketing category. ANVISA publishes examples of products that are not regulated as medical devices; a borderline claim needs a written assessment.
- Is the principal claimed purpose diagnosis, prevention, monitoring or treatment, or is the product merely general laboratory, wellness or infrastructure equipment?
- Is it a conventional device, an in vitro diagnostic (IVD), standalone medical software (SaMD), an accessory, or a mixed-function system?
- Record the patient population, user, clinical setting, contact route and duration; one changed indication can change classification.
Also screen aesthetic-use equipment: the absence of a diagnostic claim does not, by itself, establish that an item is outside ANVISA's medical-device regime.
Classification-to-route decision matrix
For products within the regime, the classification rule and the intended use must be written down. The table is a routing screen, not a final classification for an unidentified product.
| Situation | Working route | Confirm before proceeding |
|---|---|---|
| Not a regulated medical device | Do not assume an ANVISA device notification is needed | Confirm exact claims against ANVISA scope/exclusion guidance; assess any other applicable regime. |
| General device: Class I or II | Notificação (notification) | Record RDC 751/2022 classification rule; prepare compliant evidence despite no prior technical review of notification. |
| General device: Class III or IV | Registro (registration) | Evaluate full dossier and applicable Brazilian GMP certification before filing. |
| IVD: any proposed class | Separate RDC 830/2023 analysis | Apply IVD-specific rules first; Classes I–II normally use notification, III–IV registration; do not import a general-device rule. |
Five facts that can reverse the proposed route
- Indication and claims: screening versus diagnosis, general monitoring versus a clinical decision.
- Technology: invasiveness, contact duration, implant status, energy delivery and software decision logic.
- Product boundary: accessory versus spare part; standalone software versus embedded functionality.
- Grouping: intended use and technical characteristics of each model in a proposed device family.
- Legal and operational chain: legal manufacturer, Brazilian holder/importer, sites, outsourced steps and planned product changes.
Gap register: test only after you know what is missing
Compare each claimed function and each proposed model with Brazilian obligations. Mark evidence as usable, usable with justification, missing or not yet applicable. The matrix prevents spending on tests that do not address the actual gap.
| Workstream | Evidence to inspect | Decision / red flag |
|---|---|---|
| Classification | Intended use, indications, variants and cited rule | Resolve conflicting claims and uncertain family boundaries first. |
| Safety and performance | Risk file, verification/validation, clinical or performance support | Map evidence to RDC 848/2024; explain gaps before commissioning new tests. |
| Standards and certification | Test reports, standards editions, conformity certificates | Check current recognized standards and whether mandatory SBAC/INMETRO conformity assessment applies; neither is universal. |
| Manufacturing and parties | QMS/GMP files, manufacturing sites, Brazilian applicant details | Check applicable RDC 665/2022 obligations and certification route where required. |
| Brazil-specific dossier | Portuguese labeling/IFU plan, model list, traceability and change history | Identify local adaptations and existing-market-authorization differences. |
Evidence reuse: acceptable input is not automatic approval
EU CE documentation, US FDA materials, ISO 13485 certificates, MDSAP records and international test reports may help build the evidence map. None by itself proves the correct Brazilian classification or substitutes for a Brazilian regularization. Match product versions, intended use, test scope, standard editions and Brazilian essential safety/performance requirements. ANVISA explicitly states that its recognition of a technical standard is not approval of a specific device.
ANVISA-recognized technical standards are generally voluntary unless an applicable regulation makes them mandatory; documented equivalence or a justified alternative method may be possible.
Recommended order and stop/go decisions
- Freeze the intended use, versions and product boundaries; confirm whether the device regime applies.
- Write down the RDC 751/2022 or IVD RDC 830/2023 rule and justify the notification/registration choice.
- Map evidence, identify any relevant INMETRO/SBAC and wireless/ANATEL questions, then commission only necessary additional work.
- Confirm the Brazilian applicant/holder and manufacturing chain. For foreign Class I/II manufacturers, ANVISA’s August 2026 notice routes manufacturer-code creation and updates through Solicita; Classes III/IV remain linked to GMP-certification petitions.
- Approve a gap-closure plan and only then transfer the verified project to filing and post-market change control.
What the manufacturer should receive
A useful advisory deliverable is a reasoned route memo naming the precise decision rule, unresolved assumptions, an evidence-by-requirement matrix, the proposed responsible entity and a sequence of work with decision gates. Product submission belongs to the ANVISA registration execution service.
For adjacent obligations, consult: the dedicated IVD filing service, INMETRO assessment advice, ANATEL advice for wireless functionality.
Frequently asked questions
Does a CE mark or FDA clearance replace ANVISA regularization?
No. Foreign materials can support the evidence assessment, but Brazilian scope, class, applicant and route must be checked independently.
May we market a Class I/II product immediately because notification has no technical pre-review?
No. The absence of prior technical review is not an exemption from completing the applicable notification process or meeting other requirements. Check the product’s regularized status. For Class I/II devices, do not market on the strength of a filing receipt alone: ANVISA describes authorization after publication of the notification in the Federal Official Gazette (DOU).
Can a foreign manufacturer submit without a Brazilian responsible party?
Do not assume so. Identify an appropriately eligible Brazilian applicant/holder and verify its authorizations and contractual control before allocating dossier ownership. For equipment and SaMD filings, ANVISA's manual states that the applicant must be a legally established Brazilian company with the relevant ANVISA operating authorization (AFE) and local sanitary operating licence (LF). Check the entity's authorized activities before choosing the holder.
Will adding an indication or software feature leave the original classification unchanged?
Not necessarily. Reapply the intended-purpose and relevant classification rules to the changed configuration; assess amendment or new-regularization implications before marketing it.
What if a device is an IVD or part of a connected system?
Use RDC 830/2023 for IVD classification; separately screen the device and wireless elements for other applicable conformity obligations. Avoid treating one approval as covering all functions.