Gap Analysis Method for Iranian Medical Device Registration Projects

1. Key takeaways

The greatest cost of an Iranian project is not the official fees but the round trips caused by deficiency requests. The judgment of GRZAN is that performing the gap analysis at the project initiation stage significantly reduces the probability of deficiency requests, at an investment far below the time cost of a single deficiency round. The gap analysis should cover four dimensions — entity qualification, pathway applicability, documentation completeness and localisation adaptation — and it should classify problems into three levels, blocking-level, delay-level and optimisation-level, handling each level separately so that the project plan can respond to each with the right sequencing. The classification is what converts a list of findings into a sequenced project plan.

• The four dimensions of the gap analysis are entity qualification, pathway applicability, documentation completeness and localisation adaptation, each scored item by item.
• Each finding is rated as met, partially met or not met, so that the output supports a resourcing decision rather than a simple document list.
• Blocking-level problems must be resolved before project initiation; delay-level problems can run in parallel with other work; optimisation-level items can be perfected after market entry.
• The gap analysis report must state a timeline range and a budget range, marked as a practical estimate and not as a commitment.
• After remediation, one re-evaluation is performed to confirm that blocking-level problems have been cleared before formal submission.
• International documentation structure — the GHTF Summary Technical Documentation (STED) format and ISO 13485:2016 system evidence — forms the dossier skeleton generally accepted by Iran.
• The gap analysis answers three decision questions: whether the project is worth doing, how long it would take, and where the main risks lie.
• The re-evaluation closes the loop: it verifies that the remediation actually changed the finding, not merely that work was performed.

2. Legal basis

The prior approval principle rests on the Law Concerning Regulations of Medical, Laboratory, Pharmaceutical and Food and Beverage Affairs, recorded in FAOLEX as LEX-FAOC227692, dated 1955-06-20, Article 3, which makes prior authorisation the legal premise of any market activity in this field.

The Law on Maximum Utilization of the Country’s Production and Services Capacities in Support of Iranian Goods, adopted in Iranian year 1398 (2019), consisting of 24 articles, applies through Article 1: where similar goods exist within the country, import registration will not be processed. A gap analysis that ignores this rule will miss the single most common blocking-level problem.

On structure and system evidence: the GHTF Summary Technical Documentation (STED) structure together with ISO 13485:2016 quality system evidence constitutes the internationally standard dossier skeleton and is generally accepted by Iran — this is a practical estimate. It nonetheless provides the most reliable organising frame for a dossier intended to pass review with the fewest round trips.

3. Expert insights

Insight 1: the output of the gap analysis is a decision basis, not a document checklist. Many companies reduce the gap analysis to the question of which documents are still missing, which is a low-value exercise. The GRZAN gap analysis report must answer three questions: whether this project is worth doing at all, how long it would take to complete, and where the main risks lie. Only when the analysis supports an investment decision does it justify the effort spent on it. A report that answers these three questions can be taken to a management meeting, which is where the go/no-go decision actually belongs. Findings that do not affect any of the three answers belong in the optimisation tier, not in the executive summary. Scores without recorded evidence cannot survive a management challenge.

Insight 2: blocking-level problems must be solved before project initiation. Examples are a product that faces an Iranian-made equivalent, a local entity whose qualification is insufficient, or a product that cannot provide a Persian-language interface. Investing in a project while such problems remain unsolved amounts to paying the tuition fee first and learning the lesson afterwards; the sequencing rule exists precisely to prevent that outcome. The Persian interface example illustrates the character of blocking-level items: they are capability questions, not workload questions, and workload cannot substitute for capability.

Insight 3: delay-level problems can be handled in parallel. For example, where a test report requires supplementary testing, that work can proceed at the same time as the preparation of other documentation, without serial waiting. The three-level classification exists so that the project plan can parallelise the delay-level items instead of letting them inflate the critical path. Parallel handling is what keeps the timeline range in the report honest, because a serialised plan would inflate it. The parallel tracks also give the project an early warning: if a delay-level item slips, the timeline range, not the go decision, is what moves.

4. Practical recommendations

• Score the four-dimension checklist item by item: entity qualification, pathway applicability, documentation completeness and localisation adaptation, each rated as met, partially met or not met.
• Handle the findings in three grades: blocking-level before project initiation; delay-level in parallel; optimisation-level after market entry, with owners and dates attached to each item.
• Output timeline and budget ranges: the gap analysis report must give a timeline range and a budget range, marked as a practical estimate and not as a commitment.
• Build in a re-evaluation mechanism: after remediation, re-evaluate once and confirm that blocking-level problems have been cleared before formal submission.

5. Verification checklist

• □ The four-dimension gap checklist has been completed and scored item by item
• □ The findings have been classified into blocking-level, delay-level and optimisation-level and scheduled separately
• □ Blocking-level problems have been cleared, or a clear solution exists for each of them
• □ The gap analysis report states timeline and budget ranges marked as a practical estimate
• □ One re-evaluation has been completed after remediation

How GRZAN can help. GRZAN provides medical device and IVD registration, quality system, authorised representative and local testing support for the Iranian market. Our team manages IFDA registration applications, prepares reference-country dossiers, and supports post-market vigilance obligations. Business enquiries: info@grzanglobal.com