Risk Management under ISO 14971 for Jordan Registration

1. Key takeaways

The risk management file (under ISO 14971) is a stand-alone submission item in the Jordanian registration dossier; it is not an annex to the quality management system certificate. GRZAN’s conclusion is that the JFDA lists risk analysis as a routine component of the technical documentation, placed on the same footing as the device description, intended use, test reports and clinical evaluation report.

• Second conclusion: Jordan’s risk management requirements are tied to the product classification. The classification determination itself weighs four dimensions — intended use, degree of invasiveness, duration of contact and powered nature — and these dimensions are precisely the inputs of the risk analysis. The two documents must corroborate each other rather than speak past one another.
• Third conclusion: the common deficiencies concentrate in three places — the risk analysis does not cover local use scenarios, the acceptability judgement on residual risk lacks a basis, and the analysis does not correspond to the warnings in the instructions for use. All three are correctable at the drafting stage.

2. Legal basis

The risk analysis requirements for registration in Jordan rest on the instruments listed below, each shown with its reference, publication date and the location of the relevant provisions.

Provision numbers are subject to the Arabic originals published in the Jordanian Official Gazette and issued by the JFDA.

3. Expert insights

The observations below set out how GRZAN aligns a risk management file with Jordan’s classification and labelling expectations at the drafting stage.

Insight 1: the risk analysis is supporting material for the classification rationale. Jordan’s classification considerations (intended use, degree of invasiveness, duration of contact, powered nature) overlap heavily with the hazard identification inputs of the risk analysis. When GRZAN compiles the dossier, it has the two documents share the same product description to guarantee consistency. Sharing the description also means that a revision to one document flags the need to re-check the other.

Insight 2: local use scenarios should be built into the risk analysis. Jordan’s climatic conditions (high temperature, dryness), its grid parameters (220V/50Hz, practical estimate), and the differences in the conditions of using institutions may introduce hazards not covered by the risk analysis of the country of origin. This is a point on which Jordanian review may raise supplementary comments. Hazards never encountered in the home market can become live issues in Jordan’s operating environment.

Insight 3: the acceptability judgement on residual risk must have a basis. The risk analysis cannot simply state the conclusion that a risk is “acceptable”; it must state the standard, benchmark or literature on which the judgement rests. GRZAN recommends listing the sources of the acceptability criteria in the document. A stated basis gives reviewers something concrete to accept or challenge, rather than a bare assertion.

Insight 4: risk control measures should correspond to the instructions for use. If a risk control relies on a warning or an operating restriction in the instructions for use, then the Arabic instructions for use must carry the corresponding wording. A disconnect between the risk file and the instructions for use is a common deficiency item for the JFDA. The cross-check is performed against both language versions, since the Arabic wording is the one reviewers and users actually read.

Insight 5: the dynamic update obligation of risk management extends into the post-market phase. Post-market adverse events and FSCA information should flow back into the risk analysis file, forming a closed loop. This is a direction that the JFDA will continue to strengthen on its internationalisation path (WHO listing, PIC/S and ICH ambitions). A closed loop also shows the reviewer that the risk file is a living document rather than a submission artefact.

4. Practical recommendations

• First, let the risk analysis and the classification rationale share the product description. Consistency between the two documents is the foundation of a smooth review. A single shared description eliminates the drift that appears when two authors write independently.
• Second, supplement hazard identification for local use scenarios. Run supplementary analysis targeting the hot and dry environment, local grid conditions, and the differences in the capabilities of using institutions. The supplementary analysis is documented in the same file, so reviewers see one integrated risk picture.
• Third, state the basis for the residual risk acceptability judgement in the document. Cite standards, benchmarks, or the risk levels of comparable products already on the market. Citing the source of each criterion is what converts an opinion into an auditable judgement.
• Fourth, build a cross-reference table between the risk file and the instructions for use. Ensure that every risk controlled through the instructions has corresponding wording in both the Arabic and English versions. The table is maintained through the product lifecycle, not only for the initial submission.

5. Verification checklist

• □ The risk management file has been compiled under ISO 14971 and submitted as a stand-alone document
• □ The product descriptions in the risk analysis and the classification rationale are identical
• □ Hazard identification for local use scenarios (high temperature and dryness, 220V/50Hz) has been supplemented
• □ The residual risk acceptability judgement states the standard or benchmark relied upon
• □ Risk control measures correspond one-to-one with the warnings in the Arabic and English instructions for use
• □ An update mechanism exists for flowing post-market adverse events back into the risk file
• □ The cited provision numbers have been re-verified against the Arabic text of the Official Gazette

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