Brazil SIUD UDI Data Transmission under IN 426/2026

1. Key takeaways

IN 426/2026 takes effect on 2026-03-01, and its core obligation can be compressed into one sentence: before a device is placed on the Brazilian market, its UDI data must be transmitted into SIUD — and only the UDI-DI. GRZAN’s judgment: this instruction changes little in labeling workload; what it changes is the pre-market process — with data not yet in the database, the product cannot be placed on the Brazilian market. [All articles cited in this piece are taken from the official consolidated text of IN nº 426/2026, not second-hand compilations.]

2. Legal basis

• Transmission and management of the UDI database SIUD — IN nº 426/2026, issued February 13, 2026 and published in the DOU on February 18, 2026 (issue 32, Part 1, page 209), Articles 3, 4, 5, Article 7 caput and §1, §2, §3, Article 8 caput and single paragraph, Article 9 caput and §1, §2, Articles 10, 11, 15 and 16
• UDI requirements — RDC nº 591/2021, published 2021, effective January 2022, Article 15 (as rewritten by RDC nº 884/2024, not the original text)
• Law on health offenses and sanctions — Lei nº 6.437/1977, dated August 20, 1977 and published in the DOU on August 24, 1977 (Part 1, page 11145), full text (list of sanctions)

3. Expert insights

Article 3 is the pivot of the whole instruction. It moves the transmission point forward to before placement on the Brazilian market and makes clear that only the UDI-DI is submitted; the UDI-PI does not enter the database and is maintained by the holder within its quality system to preserve traceability. GRZAN’s reading: SIUD is a catalog database, not a traceability database — the traceability duty stays on the company side. Article 4 allows single or batch transmission, and Article 5 requires each data set to correspond to a unique UDI-DI and one device model.

Articles 4 and 5 look procedural but actually decide data quality. Batch transmission lowers operating cost while raising the amplification factor of error — one template mistake contaminates the whole batch, and correction can only happen inside the window given by Article 7. GRZAN recommends validating with small batches before submitting in bulk.

Articles 6 and 8 also deserve to be read side by side. Article 6 provides that data becomes public once the disclosed date declared on submission is reached. Article 8 handles transfers of registration ownership, requiring the RDC 903/2024 procedure to be completed before touching SIUD; its single paragraph requires the successor company to transmit the UDI-DI for the new registration number within 30 days from the effective date of the specific resolution on cancellation and ownership transfer. GRZAN recommends running ownership-transfer projects as standalone workstreams to avoid timing misalignment between the two systems.

GRZAN reads Article 3 as a release gate, not a formatting requirement — if transmission is not completed before market placement, no amount of downstream labeling or channel work constitutes a compliance defense.

Article 7 gives two correction time limits (in the official wording, verbatim): the caput sets a grace period of 60 dias corridos, counted from publication of the UDI data, during which corrections may be made; §1 provides that after the grace period expires, only data not requiring a new UDI-DI can still be modified; §3 provides that where a new UDI-DI is required, the replacement must be completed within 30 dias corridos from publication of the change in the DOU; §2 makes clear that once the publication date is reached it cannot be changed. GRZAN warns that the last sentence is the easiest to ignore — the publication date cannot be moved, so scheduling must leave room for the correction window.

Article 9, caput lists three situations in which a deactivation date must be registered in SIUD within 30 days: the holder terminates supply in Brazil, the health license expires, or the registration is cancelled; §1 specially provides that in the cancellation case the period runs from the first business day after the cancellation decision is published in the DOU. Article 10 allows the holder to authorize a third-party user to transmit on its behalf, but responsibility is not transferred. Article 11 ties the mandatory transmission deadlines back to the class schedule of Article 15 of RDC 591/2021 and permits voluntary transmission before the mandatory date. Article 13 is the basis on which ANVISA suspends data transmission for a class of devices (see piece 46 of this series). Article 15 qualifies non-compliance as a health offense under Lei 6.437/1977. Article 16 sets the effective date at 2026-03-01. [Articles 3, 6, 7, 8, 9, 10, 11, 13, 15 and 16 above are all taken from the official consolidated text, not second-hand compilations.]

4. Practical recommendations

• Make completed SIUD transmission a hard prerequisite node in the Brazil release process.
• Validate against Article 5: each data set corresponds to a unique UDI-DI and one device model.
• Set up change monitoring: for changes requiring a new UDI-DI, count 30 calendar days from the DOU publication date.
• Where a third party transmits on your behalf, sign a written authorization and retain operation audit records (responsibility is not transferred under Article 10).
• Bring the three scenarios — production stop, license expiry and cancellation — into expiry reminders.
• Run a small-batch validation before bulk transmission to confirm template fields are correct.
• Run ownership-transfer projects as standalone workstreams: complete RDC 903/2024 first, then touch SIUD.

GRZAN recommends annotating every UDI-DI in the internal system with a status and a responsible person, attaching the deadlines of Articles 7 and 9 directly to the person rather than to the department. Deadlines attached to departments are most easily lost during staff handovers.

5. Verification checklist

• □ Verify the effective date 2026-03-01 (Article 16 of IN 426/2026)
• □ Verify that the pre-market transmission process is fixed in the SOP
• □ Verify the practice of transmitting only the UDI-DI and retaining the UDI-PI internally
• □ Verify monitoring of the 60 calendar days correction window and the 30 calendar days new-UDI-DI replacement
• □ Verify the 30-day deactivation triggers and their starting points
• □ Verify the bulk transmission template against the uniqueness requirement of Article 5
• □ Verify that ownership transfers have completed the RDC 903/2024 procedure
• □ Verify that every UDI-DI carries a status and a responsible person
• □ Verify the original text of IN 426/2026 against DOU issue 32

Regulatory information verified as of October 29, 2026

GRZAN Regulatory Team

GRZAN runs SIUD readiness end to end: account and transmission setup under IN 426/2026, UDI-DI data validation, correction-window monitoring under Article 7, deactivation and ownership-transfer handling, and audit-ready records for every transmission action. With market placement now gated by the database, we make sure your gate opens on time. For SIUD and UDI data transmission support in the Brazilian market, contact info@grzanglobal.com.