STED Technical File Requirements for Medical Device Registration in Iran

1. Key takeaways

Iran accepts a technical dossier built on the GHTF Summary Technical Documentation (STED) framework, but accepting the structure is not the same as accepting the content, and a direct copy-and-translate submission is not enough. The judgement of GRZAN is that the STED provides structural commonality, while the differentiated requirements of Iranian review are concentrated in 3 modules — Persian-language translations, conformity with ISIRI standards, and adaptation to the local environment. These 3 modules have no corresponding position in a standard STED and must be added as dedicated chapters. Whether a technical file is usable can therefore be judged by a simple test: whether these three chapters are present. The value of the test is that it costs nothing: a dossier either contains the three chapters or it does not, and the answer is visible before any reviewer sees the file.

• Iran accepts the STED as the skeleton of the technical file, yet the skeleton alone does not carry a dossier through review.
• The Iran-specific requirements concentrate in three modules: Persian translations, ISIRI standard conformity, and local environment adaptation.
• Because a standard STED has no built-in position for these three modules, they must be added as separate chapters in every dossier.
• The most efficient test of whether a technical file is fit for submission is simply to check whether these three chapters exist and are complete.

2. Legal basis

The legal and normative references supporting this module are the following.

1. GHTF Summary Technical Documentation (STED) structure and declaration of conformity: Iran accepts a declaration of conformity based on the GHTF STED — see the entry for Iran in the World Health Organization publication Overview of medical device naming systems in WHO Member States, which cites the classification and submission documents published on imed.ir.
2. Requirements for Persian-language labels, instructions for use and translated technical documentation — based on publicly available industry materials; no official Iranian document number has been released through public channels, so this is a practical estimate.
3. ISIRI mandatory national standards: where a corresponding standard exists, conformity is judged against that standard — this is a practical estimate.

3. Expert insights

Insight 1: the STED buys “structural trust”, not “content compliance”. When a reviewer opens a dossier and recognises a familiar STED skeleton, the cost of understanding the document drops immediately: the reviewer knows where the device description sits, where the verification evidence sits and where the declarations are filed. This familiarity is genuinely valuable, and it is why the framework is accepted in the first place. However, familiarity with the structure says nothing about whether the content satisfies the requirements that are specific to Iran. A reviewer may navigate the dossier effortlessly and still find that the sections on language, standards and local conditions are missing. The most common inefficient practice that GRZAN observes is exactly this: a STED that has been translated and submitted as it stands, on the assumption that the framework itself does the work. It does not. The framework earns the reviewer’s patience; only the added local content earns the approval. The reviewer’s patience is a limited resource, and a structure that spends none of it on orientation leaves more of it for the substance.

Insight 2: the three supplementary chapters are the minimum necessary adaptation. The practice at GRZAN is to append, beyond the standard STED, three fixed chapters: a note on language and translations, a comparison table against ISIRI standards, and a statement on adaptation to the local environment. The chapters are deliberately short — each one addresses a single question the reviewer is certain to ask, and each one answers it in a place the reviewer can find without searching. Their brevity should not be mistaken for insignificance. These chapters are precisely what determines whether the dossier passes in one round, because they convert silent assumptions into explicit statements. A dossier that leaves these questions implicit forces the reviewer to raise them as deficiency requests, which costs far more time than the chapters would have cost to write. Each chapter also gives the applicant a fixed place to answer a question that would otherwise surface scattered across the review.

Insight 3: version and date management is an invisible quality checkpoint. Every module of the technical file should carry a version number and a date, and those markings should be aligned with the validity periods of the test reports and certificates referenced elsewhere in the dossier. Reviewers cross-check these alignments as a matter of routine: a certificate issued under one version of a standard, a report dated later than the file it supports, or a document cited without a date all read as signs of a dossier assembled rather than managed. None of these mismatches is fatal on its own, but each one triggers questions, and questions extend the review. Consistent version and date markings are invisible when they are done well — which is exactly why they are worth doing well. The discipline costs little to establish at the start and grows expensive to retrofit once several modules have drifted apart.

4. Practical recommendations

• Adopt a fixed template of STED plus three supplementary chapters: a uniform structure avoids rebuilding the dossier for every project and makes internal quality control predictable. A template approved once becomes the fastest safe starting point for the next project.
• Build a version–date cross-reference table: consolidate the versions and validity periods of all referenced documents into a single table, so that reviewers and your own team can cross-check them quickly.
• Lay translations out in parallel with the originals: in the key chapters, place the Chinese, English and Persian text side by side, reducing the reviewer’s comprehension cost.
• Make the index searchable: provide a hierarchical table of contents and a page-number index, shortening the time a reviewer needs to locate any module.

5. Verification checklist

• □ The technical file has been structured on the STED framework
• □ The three supplementary chapters — language and translation notes, ISIRI comparison table, local environment adaptation statement — have been added
• □ A version–date cross-reference table has been built for all referenced documents and aligned with certificate validity periods
• □ The key chapters have been laid out with Chinese, English and Persian text in parallel
• □ A hierarchical table of contents and a page-number index have been provided in the dossier

Regulatory information verified as of October 29, 2026

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 prepares IFDA-compliant dossiers, and supports post-market vigilance obligations. Business enquiries: info@grzanglobal.com