The SFDA Reliance Pathway under MDS-G030: Scope, Timeline and Exclusions

1. Key takeaways

On 2026-09-09 the SFDA published the SFDA Reliance Approach for Medical Device (MDS-G030, V1.0, serial number MDS-G-030-V1/260909), for the first time systematically recognising existing approvals from 6 recognised regulatory authorities (RRAs). A product holding a valid marketing authorisation from one RRA, technically identical to that approved device in design, manufacturing process and intended use, and meeting Saudi-specific requirements — SBC Part 401 electrical requirements, label, IFU and user-interface content and language, and temperature- and humidity-related storage and transport requirements — can use the reliance pathway. The official review timeline is 35–60 working days, identical across Class A/B/C/D; relying on existing approvals instead of a full independent assessment can compress it to 35 working days. Five categories are excluded: the self-registration pathway, the pathway based on substantial equivalence to a predicate device, custom devices, products under major RRA recall, suspension, withdrawal or restriction, and SaMD and AIeMD. On the QMS side, MDSAP certificates and audit reports issued by MDSAP auditing organizations are accepted. Regulatory information verified as of 29 October 2026.

• One valid RRA approval plus technical identity in design, manufacturing process and intended use opens the reliance pathway.
• Saudi-specific requirements cover SBC Part 401 electrics, label/IFU/interface content and language, and storage-transport conditions.
• Official timeline: 35–60 working days, uniform across Class A/B/C/D; reliance can compress it to 35 working days.
• Five exclusions: self-registration, predicate equivalence, custom devices, RRA-restricted products, SaMD and AIeMD.
• MDSAP certificates and audit reports are accepted as QMS evidence.

2. Legal basis

The reliance pathway rests on MDS-G030 itself, the law and implementing regulation above it, and the classification and bundling guidances that govern every application. Third-party retellings are marked as practical estimates with their verification actions.

3. Expert insights

1. Reliance is not mutual recognition — the SFDA keeps all decision power

The official Declaration in the Reliance Form contains a hard formulation: the applicant must confirm that the regulatory approvals submitted cover all medical devices listed in the application, while acknowledging that the SFDA retains full decision-making power over the marketing authorisation and may request additional information or data during review. This separates reliance from mutual recognition. Mutual recognition ends in automatic clearance; reliance only treats another regulator’s review report as input literature. The practical consequence for applicants: even holding an MDR CE certificate or TGA ARTG inclusion, the Rationale must be reorganised in the SFDA’s format, translating another authority’s conclusions into an argument structure the SFDA reviewer can quote directly. GRZAN normally drafts the Reliance Form as an independent argument document, not as a cover page for uploaded attachments.

2. What the 35–60 working days really mean

The band carries three layers of information. First, these are working days, not calendar days: 35 working days is roughly seven calendar weeks at minimum, and holidays (Ramadan and the compressed office days around Eid al-Fitr and Eid al-Adha) widen it further. Second, the same band applies to all four risk classes, so the marginal benefit is largest for Class D — routine MDMA review of high-risk devices is already the longest, so compression is greatest; for Class A/B the real saving is limited. Third, the premise is stated plainly: the application must be complete and the required documents complete. Once a deficiency letter is triggered, the clock no longer follows this band. Minimising the probability of deficiencies matters more than debating queue position. For AIeMD, companion diagnostics and combination products, the SFDA expressly reserves the right to request additional information, so even if these are theoretically not excluded, time budgets should assume a deficiency cycle.

3. What the pathway really changes is the global filing order

The customary sequence for the Middle East used to be: domestic registration, then CE/FDA, then top-up filings across GCC countries. After MDS-G030 the order should be inverted: when a product is planned to take its first approval among TGA, Health Canada, an EEA competent authority, PMDA or the MHRA, the MDMA should be budgeted as the second stop immediately after, because the technical file from that first approval is still warm. Conversely, if the company’s first overseas approval happens to be a US 510(k), this road is expressly excluded and needs a separate design (see https://www.grzan.cn/regulations/saudi/why-fda-510k-excluded-from-reliance-14 ). Another easily missed point: the RRA list can move — the SFDA states it may update the list periodically, adding IMDRF Management Committee member jurisdictions — so every new version of MDS-G030 warrants re-reading the list footnotes. The six list members and the eligibility logic are detailed in https://www.grzan.cn/regulations/saudi/reliance-pathway-eligibility-and-rra-13 .

4. Practical recommendations

• Open the GHAD / SFDA E-Services account and obtain the Establishment Number first; this is Step 1 and cannot be inverted with Step 2.
• Run an exclusion self-check before filing: self-declaration pathway, predicate substantial-equivalence pathway, custom devices, products under major RRA recall or restriction, SaMD and AIeMD — sign off item by item.
• In subsection (2.1) of the MDMA application Overview answer “Yes”, activate subsection (2.1.1), fill in the Country and Title, and upload each Evidence Document individually.
• When uploading the Annex (1) Reliance Form, the file name must read exactly “Reliance Form” and the applicable country must be set to “Saudi Arabia”; these are hard match points at system level.
• Expand the Rationale along the official fields: a summary of global regulatory status, evidence of the appropriateness of reliance, and confirmation of identity with the reference authority’s approved device in intended use, design, specifications, manufacturing information and labelling — a missing item means the argument is incomplete.
• For electrical products, check supply voltage, frequency and conductor insulation colours against Part 401 of the Saudi Building Code (SBC) first, and complete remediation before filing.
• Layer labels, IFU and user interfaces by user: Arabic for lay users; English or Arabic is acceptable for professional users.
• For the QMS step, submit the MDSAP certificate and the audit report issued by the MDSAP auditing organization, verifying that scope and validity cover this application.

5. Verification checklist

• □ A valid marketing authorisation or approval from at least 1 RRA (TGA / Health Canada / an EEA competent authority / PMDA / MHRA / FDA) is held
• □ Design, manufacturing process and intended use have been compared item by item with the RRA-approved device, with a technical identity comparison table
• □ The five Scope Exclusions have been self-checked item by item with signed records
• □ The risk class of every device has been re-verified against the current MDS-G008
• □ Multi-device applications have been checked against MDS-G028 family/system conditions: no more than 5 technical files and 50 items
• □ In Step 2, (2.1) is set to Yes, (2.1.1) Country and Title are filled in, and Evidence Documents are uploaded one by one
• □ Reliance Form file name and country field verified (“Reliance Form” / “Saudi Arabia”)
• □ SBC Part 401 electrical requirements, Arabic labelling and storage-transport remediation are closed
• □ The MDSAP certificate and audit report are within validity and their scope covers the application

How GRZAN can help. GRZAN provides medical device and IVD registration, quality system, authorised representative and local testing support for the Saudi Arabian market. Our team manages SFDA MDMA applications across classes, prepares reference-approval dossiers, and supports post-market vigilance obligations. Business enquiries: info@grzan.com