Paraguay Medical Device Registration 2026: UMDNS Nomenclature and DMNSO Codes

1. Key takeaways

1. Article 23 expressly adopts the Universal Medical Device Nomenclature System (UMDNS) maintained by ECRI (Emergency Care Research Institute) for the identification of the generic name of devices, so the vocabulary of the registration system is borrowed from an international standard rather than invented nationally.
2. Article 22 defines the registration code structure for Class I (NSO) products as: the letters DMNSO, plus a 6-digit product identification number, plus a hyphen, plus a 2-digit renewal count, in a form exemplified by DMNSO-000000-00. Every notified product on the market therefore carries a parseable identifier with two embedded facts: identity and history.
3. The final two digits of the code indicate the number of completed renewals of the product, from which the years the product has been present in the Paraguayan market can be read directly, since each renewal cycle runs against the 10-year validity of the NSO.
4. The operating instructions require the platform declaration of the generic name (following the Spanish name corresponding to the UMDNS code) and the UMDNS code; the trade name is declared in the format of generic name followed by brand or trade name, so the three fields form a single, internally consistent naming chain that reviewers check as a unit.

2. Legal basis

3. Expert insights

Insight 1: nomenclature standardization is the foundation on which all later data governance rests. By writing UMDNS into the regulation, Article 23 turns the generic name into a field that is not defined by the company but must take its value from the standard coding table. This is consistent with the coding logic of the national traceability system under Decreto N° 3668/2025, which builds the national catalogue of medicines and related products on the same principle: unify naming first, and only then discuss unique identification. Companies that fix their UMDNS mapping once, correctly, avoid a cascade of downstream corrections across registrations, renewals and traceability data. The reverse is equally true: a generic name improvised at filing time propagates into certificates, import documents and platform records, and every later correction multiplies across those systems. Where the Spanish name corresponding to a code is ambiguous, the chosen Spanish name should be documented with the mapping decision.

Insight 2: the final two digits of the code are readable compliance information. Given the DMNSO code of a Class I product, the last two digits state directly how many renewal cycles the product has survived in the market. For companies conducting channel due diligence, competitor analysis or distribution rights negotiations, this is publicly available information obtained at zero cost: a code ending in 00 shows that no renewal has yet taken place, while a higher count signals a longer certification history and, usually, greater difficulty in displacing the incumbent holder from the channel. Because the code appears on public listings, the same reading can be automated across a product family to map how long each competitor has held its notifications. A count of zero does not necessarily indicate a young product; it may equally indicate a recently transferred or re-declared notification, which due diligence should confirm.

Insight 3: the consistency requirements for declaration fields are detailed. The operating instructions require trade names to be entered as generic name followed by brand, sets to be entered as Sistema/Kit/Set de followed by generic name and brand, and models to be entered as reference code, identifying name and specification (dimensions, caliber, color, size and the like), and all of this must agree with the free sale certificate (CLV); where the CLV does not state the information, a separate manufacturer document must be attached. Field inconsistency is a common reason for rejection at the admission stage (practical estimate: project experience). Companies should therefore treat naming as a controlled document with an owner, not as a field typed at submission time. The comparison between the CLV and the platform fields should be run at every filing, not only at the first one, because certificates are reissued and fields drift over time.

4. Practical recommendations

1. Build a UMDNS code cross-reference table, fix the generic name and code for every SKU, and keep them consistent across batches and submissions, treating any change of code or name as a regulated event rather than an editorial edit.
2. Align model naming rules completely with the CLV; where the CLV does not cover an item of information, obtain a supplementary explanatory document from the manufacturer in advance, so the file never has to guess at a field the certificate left silent.
3. In due diligence, read the final two digits of competitor DMNSO codes to estimate certification age and channel stability before entering negotiations, and combine that reading with the identity of the registration holder visible in the public record.
4. Before platform submission, run one comparison of CLV fields against platform fields, so that model, brand and generic name do not diverge in any of the three places, and resolve every mismatch at the source document rather than by editing the platform entry to fit.

5. Verification checklist

• □ Cross-reference table of UMDNS codes and generic names established
• □ Trade names declared in the format generic name followed by brand
• □ Set names declared in the format Sistema/Kit/Set de followed by generic name and brand
• □ Model fields fully consistent with the CLV and manufacturer documents
• □ Competitor certification age checked through the final two digits of DMNSO codes
• □ Naming change procedure documented with a responsible owner
• □ Platform fields compared against the CLV at every submission

Regulatory information verified as of October 29, 2026.

GRZAN provides medical device registration support in Paraguay for manufacturers, importers and authorized representatives. For inquiries, contact info@grzanglobal.com.