Decreto 4725 Article 18: The Technical File Checklist for INVIMA Registration

1. Key takeaways

Article 18 of Decreto 4725 de 2005 (published December 26, 2005) is the sole statutory entry point for the INVIMA technical documentation list. It defines which document types must be submitted; it does not define what those documents should look like. Colombia has no technical documentation format specification or template that stands outside the decree, so Article 18 reads short while the real workload sits entirely in the assembly of the dossier.

The GRZAN position is blunt: when a technical file is returned, nine cases out of ten fail not because a document is missing but because the documents do not match one another. The official review timeline for standard registration is 90 working days, and the deficiency response period is 90 days; a single unanswered deficiency is treated as a procedural suspension. Every gap on the Article 18 list is ultimately settled in time, which is why internal consistency checks matter more than volume.

2. Legal basis

3. Expert insights

#### 1. Article 18 gives you document types, not a document template; the assembly logic must be built in-house

The decree lists the mandatory items of the technical file but offers no table of contents structure, no numbering rules and no page specifications. The applicant therefore faces two options: carry over the manufacturer’s existing format, such as an EU technical documentation set or an FDA submission package, or reorganize the dossier around the way an INVIMA reviewer actually reads. GRZAN insists on the second option. The reviewer’s reading order runs from what the device is to why it is safe and effective, and once those two threads can be followed within ten minutes, the probability of a deficiency notice drops significantly. A dossier that mirrors the reviewer’s own logic costs nothing extra to build, yet it removes the friction that generates most deficiency letters in Colombian device reviews.

#### 2. The classification conclusion is the first brick of the technical file; Art. 6 and Art. 7 must be placed in front

Article 6 sets out four classification logics aligned with the EU approach: independent assessment of each system, software follows its host device, multi-purpose devices take the highest risk, and conflicting rules resolve to the highest class. Article 7 sets out 18 classification rules, grouped into non-invasive, invasive, active and special rules. When the classification conclusion is wrong, every risk assumption behind the file is misaligned: Class IIb and III devices follow the standard registration route of Art. 16, while Class I and IIa devices follow the automatic registration route of Art. 17, and the intensity of review on the two routes differs completely. GRZAN therefore prepares the classification reasoning as a standalone booklet, annotating the applicable rule numbers of Art. 7 one by one, rather than burying the conclusion inside the device description where it cannot be challenged or verified directly.

#### 3. Ninety working days and a 90-day deficiency window: gaps are settled in time

The official review timeline of 90 working days for standard registration excludes the back-and-forth of deficiency cycles, and Decreto 582 de 2017 amended the processing timelines precisely because deficiency loops stretch the real schedule beyond prediction. The deficiency response period is 90 days, and a single failure to respond is treated as a procedural suspension. The economic meaning is straightforward: it is better to spend two extra weeks on an internal consistency check before the first submission than to trade one deficiency cycle for a faster first filing. Every missing or inconsistent item on the Article 18 list is finally paid in time, not in money, and the exchange rate is fixed by these two clocks.

#### 4. Language is a two-layer structure: Spanish as the base layer, English permitted as an annex

All submission documents must be in Spanish; technical or scientific information may be submitted in English provided it is accompanied by an official Spanish translation. This is not an exemption that permits an English-only filing, but a bundled requirement of an English original plus a Spanish rendering. GRZAN recommends placing a one-page Spanish overview at the front of every booklet, stating the conclusions, the parameters and the basis for those conclusions, with the English source attached as an annex. The purpose is to spare the reviewer the work of digging through material written in a non-native language, and to keep the argument of each booklet readable without constant cross-referencing between two languages.

4. Practical recommendations

1. Have the GRZAN regulatory team issue a one-page classification reasoning note first, specifying the applicable rule numbers under Art. 7 and the final risk class, and determine the Art. 16 or Art. 17 route accordingly.
2. Have the applicant (titular) reorganize the dossier into seven functional domains: device description, classification reasoning, design and manufacture, performance and safety verification, sterilization and shelf life, labeling and instructions for use, and risk and clinical evidence, each booklet opening with a Spanish overview.
3. Have the registration specialist build a parameter reconciliation table that aligns model numbers, specifications and materials in the device description line by line with the same parameters in the verification reports and the draft labels, completing one cross-check before submission.
4. Have the documentation engineer unify page numbering and naming rules so that file names match the dossier directory after upload to SIRIS, preventing mismatches when reviewers search by name.
5. Have the translation vendor complete the Spanish renderings, covering conclusions, parameter tables and figure captions, never the body paragraphs alone.
6. Have GRZAN maintain a deficiency early-warning ledger after submission with countdown management of the 90-day response window, so that a single missed response never triggers a procedural suspension.

5. Verification checklist

• □ The classification reasoning cites the classification logics of Art. 6 and the specific rule numbers of Art. 7
• □ The route, standard registration under Art. 16 or automatic registration under Art. 17, has been confirmed against the risk class
• □ The technical file is divided into booklets by the seven functional domains, each with a Spanish opening overview
• □ English technical information carries an official Spanish translation covering parameter tables and figure captions
• □ Key parameters such as model, specification and material are identical across the description, the verification reports and the draft labels
• □ File names match the dossier directory numbering for retrieval after upload to SIRIS
• □ The 90-day deficiency response period is managed on a countdown ledger

Regulatory information verified as of October 29, 2026

All conclusions for external use are based on the current regulatory texts published by the competent authorities and are verified item by item before delivery.

GRZAN supports manufacturers entering the Colombian market with registration dossiers and conformity documentation, covering technical file assembly under Decreto 4725 de 2005, classification reasoning, legalization and official Spanish translation coordination, and lifecycle maintenance before INVIMA. Our regulatory team keeps every deliverable aligned with the texts currently in force. For inquiries about documentation support for Colombia, contact info@grzanglobal.com.