IMED vs IFDA: Understanding Iran’s Medical Device Regulatory Bodies

1. Key takeaways

The Iran Food and Drug Administration (IFDA) is the executive agency under the Ministry of Health and Medical Education (MOHME), and the General Directorate of Medical Equipment and Supplies (IMED) is the directorate-general level unit inside IFDA that handles device matters. The two stand in a relationship of containment, not of parity. GRZAN’s warning is concrete: placing the two side by side, or swapping one for the other, produces entity errors in letters of authorisation, agency contracts and appeal documents. The direct consequence is rejection at formal examination; the indirect consequence is that the responsible entity becomes difficult to prove when a later dispute arises. Because every Iranian document circulates among reviewers who read these names as precise structural statements, an error in one letter can propagate through an entire file, and correcting it afterwards costs more time than writing it correctly at the start. The discipline required is small but strict: one fixed vocabulary for the whole company, applied in contracts, submissions, correspondence and internal templates alike, so that no document ever implies that IMED and IFDA are two parallel authorities competing for the same competence. The structure is easiest to remember by function: MOHME holds the legal mandate derived from the foundational statute, IFDA converts that mandate into executive action across the food, drug and device sectors, and IMED is the specialised unit where device files are actually opened, reviewed and coded. Each layer answers a different question, and a document is only correct when it names the layer that answers the question the document is asking. Companies that adopt this vocabulary in their first Iranian document rarely need to relearn it; companies that improvise wording per document spend the whole project correcting themselves.

2. Legal basis

1. The Law Concerning the Regulations on Medical, Pharmaceutical and Food and Beverage Affairs, FAOLEX LEX-FAOC227692, 1955-06-20, Articles 1 and 3 (the authorising body is the Ministry of Health).
2. IFDA organisational structure: the Iran Food and Drug Administration is established under MOHME; the General Directorate of Medical Equipment and Supplies handles device matters, with the portal imed.ir; the tracing and authenticity verification system is ttac.ir — the naming hierarchy is recorded in public industry databases covering the Iranian pathway; no official organisational instrument number has been published through open channels, so this is a practical estimate. For practical work, the operative fact is not the instrument number but the portal through which each function is exercised, and both portals should be referenced exactly as the authority itself writes them.
3. The Executive Regulation of the Supreme Health and Food Security Council, FAOLEX LEX-FAOC227712, 2019-01-14.

3. Expert insights

Insight one: industry usage and the official structure diverge. International material often describes IMED as the “Iranian medical device authority” and IFDA as a “food and drug bureau”. In reality, in most submission scenarios the system-operation layer is imed.ir while the legal authorisation layer is MOHME. Writing “submitted to IMED” and “under the authority of MOHME” in company documents is not contradictory, but the two must never be merged into a single entity. The safe habit is to ask, for every document, which layer it addresses: operational documents may name IMED and its portal freely, while anything carrying legal weight — authorisations, contracts, appeals — names MOHME and IFDA and mentions IMED only as the handling unit. The divergence is not a defect of the international material; it reflects a real gap between how the system is described abroad and how it operates at home, and the company’s own documents must follow the domestic structure.

Insight two: TTAC is a third system — do not confuse it with the other two. The tracing and authenticity verification system (ttac.ir) handles identity, registration codes and traceability, and is separate from the submission function of imed.ir. Companies scheduling a project commonly omit the TTAC step, mistaking it for something “generated automatically once registration is complete”. It is not automatic: it is a distinct system with its own registration logic, and leaving it unplanned delays the point at which products can actually circulate and be traced in the market. A simple scheduling rule prevents the omission: every submission plan lists three systems — imed.ir, ttac.ir and the foreign-exchange linkage — and closes each line only when its registration is confirmed.

Insight three: entity errors propagate into contract validity. If a contract with the authorised representative names the authorised object as IMED rather than MOHME/IFDA, the authorisation may be found ambiguous in its direction when a dispute arises locally in Iran. GRZAN recommends using the formulation “Ministry of Health and Medical Education (MOHME) / Iran Food and Drug Administration (IFDA)” in contracts and letters of authorisation, with the handling unit stated separately. This keeps the legal chain unambiguous at every level and gives local counsel a clean structure to argue from if the relationship is ever tested before a forum. The same discipline applies to internal correspondence, because statements written casually in emails have a way of resurfacing in disputes years later.

4. Practical recommendations

1. Unify the internal glossary: all company documents use the four-level vocabulary — MOHME (authorisation layer), IFDA (execution layer), IMED (handling layer), TTAC (tracing layer) — without local variations, and review the vocabulary whenever an organisational change is announced on the authority’s portals.
2. Use the “two-layer formulation” in letters of authorisation and contracts: first name the authorising authority (MOHME/IFDA), then note the handling unit (IMED) in parentheses.
3. Assign system operations to separate owners: imed.ir submissions and ttac.ir tracing are followed by different responsible persons, so that neither system is left unattended.
4. Cite the level explicitly in appeal documents: when citing a basis, give the legal provision and the reference number of the handling unit’s opinion together, so the reviewer can trace the argument across both layers at a glance.

5. Verification checklist

• □ The internal glossary has been unified and distributed to every member of all Iran-related project teams
• □ Letters of authorisation and agency contracts use the two-layer formulation for institutional names
• □ Separate responsible persons have been designated for imed.ir and ttac.ir
• □ Historical documents have been screened for entity wording and corrected where necessary
• □ Appeal and communication templates embed the correct institutional hierarchy wording

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 manages IFDA (Iran FDA) registration procedures, and supports post-market vigilance obligations. Business enquiries: info@grzanglobal.com