Paraguay Medical Device Registration 2026: DINAVISAPy Migration and the Closed Transition Window

1. Key takeaways

1. Article 32: registration applications filed in paper form and still under assessment could continue through DINAVISAPy, provided the requirements of the resolution were met and the corresponding fee paid within 30 working days from the date the resolution entered into force. The migration was thus conditional on two cumulative elements, not one.
2. Consequence of missing the deadline: files not completed within the period were deemed rejected and archived as a matter of law (denegados y archivados de pleno derecho). There was no recovery mechanism and no extension regime for the transition window.
3. Article 33: applications already pending on DINAVISAPy before the entry into force had to be aligned with the technical and legal requirements of the resolution. No number of days was set for this adjustment and no specific late consequence was attached to it.
4. The transition window was counted from the entry-into-force date of September 16, 2024 established by Article 36. It has long since expired, and the file statuses it produced are now historical facts that must be verified case by case.

2. Legal basis

The three provisions form the transition architecture of the resolution: Article 36 fixes the effective date, Article 32 governs the paper backlog with a hard deadline, and Article 33 governs the electronic backlog with an alignment duty. The contrast between the two treatment regimes is itself a source of interpretation for how DINAVISA handles formalization generally.

For companies that inherited portfolios from distributors or from earlier market-entry attempts, the transition chapter still has audit value. A file that predates the resolution should be checked for which treatment it received: whether it completed the Article 32 migration with its fee, whether it was aligned under Article 33, or whether it ended as denied and archived. The answer determines what instrument the company holds today — an effective registration, a file under the old regime, or nothing — and that determination cannot be made from internal memory alone; it requires the file history on the platform or the archive status from the authority. Reconciling the portfolio against these outcomes is a one-time exercise that prevents costly surprises at renewal or change filings.

3. Expert insights

Insight one: this is a historical window that has already closed, but the logic of the rule still operates. The 30-working-day window ran from 2024-09-16 and has long since lapsed. The value of reading Article 32 today lies not in remediation but in understanding the procedural rigidity of DINAVISA: transition arrangements come with finite windows, and expiry operates de pleno derecho — automatically by law — with no restoration mechanism. This is a reliable predictor of how the authority will treat any future transition or compliance deadline, so portfolio planning should never assume grace periods that the text does not grant.

Insight two: for electronic files already in the system, Article 33 requires adaptation, not re-submission. Unlike Article 32, Article 33 requires pending electronic cases to adjust their technical and legal content to the resolution; it sets no number of days and prescribes no specific consequence for delay. The difference between the two provisions shows that the regulator deliberately treated cases that were already digitalized differently from cases still on paper. For portfolio managers, the practical meaning is that the two populations of legacy files carry different levels of residual risk and require different monitoring.

Insight three: migration required both meeting the requirements and paying the fee. Article 32 placed meeting the requirements of the resolution and paying the corresponding fee side by side, and both were indispensable. This mirrors every subsequent procedure under the regime: formal and financial requirements are parallel thresholds, not sequential ones. A project checklist that closes only the documentary side while leaving the payment unconfirmed creates a false sense of completion, and the file remains exposed precisely where the rule is strict.

Insight four: the episode also illustrates the fee logic of transitions. Even in a forced migration designed by the authority, the fee obligation appeared alongside the substantive requirements, and files that missed either element were denied and archived. This confirms a pattern visible throughout the resolution: payments are never waived by the existence of a special procedure, however favorable its purpose. For companies, the planning rule that follows is simple — every procedural scenario, however routine or exceptional, should be budgeted from day one with both its documentary track and its payment track, because the history of this transition shows that neither substitutes for the other and the deadline applies to both.

4. Practical recommendations

1. Complete the requirement alignment for legacy electronic files under Article 33, comparing each field against Article 6 and the Instructivo requirements item by item.
2. Where a legacy file has already been archived under Article 32, re-apply under Article 26 and pay the fee; do not seek restoration of the original file.
3. Start every new project with electronic submission through DINAVISAPy; do not retain any paper pathway in the process design.
4. Enter the parallel threshold of formal requirements plus payment into the project checklist, so neither element is ever completed without the other.
5. Preserve the outcome evidence for every legacy file — the completed migration with its fee receipt, the alignment record, or the denial and archive notice — as the authoritative status of that application going forward.

5. Verification checklist

• □ Legacy electronic files aligned with requirements under Article 33
• □ Archived files re-applied for under Article 26 (no restoration sought)
• □ All new projects submitted electronically through DINAVISAPy
• □ Both elements of requirements plus payment confirmed as complete
• □ Status of the transition window (30 working days from 2024-09-16) confirmed

Regulatory information verified as of October 29, 2026.

GRZAN provides medical device registration support in Paraguay for manufacturers, importers, and authorized representatives, covering legacy file assessment, DINAVISAPy submissions, and portfolio risk review. Contact info@grzanglobal.com for tailored guidance on this topic.