Skip to main content

SFDA Definition vs EU MDR — Key Differences

Overview​

The SFDA's definition of a medical device was deliberately modelled on the EU MDR 2017/745 definition, making the two frameworks highly compatible. However, manufacturers relying solely on their EU classification and definition analysis should be aware of several practical differences.

Side-by-side comparison​

AspectSFDA (Medical Devices Law, Art. 1)EU MDR (Art. 2(1))
Core scopeInstruments, apparatus, software, materials for medical purposesInstruments, apparatus, software, materials for medical purposes
Mode of action exclusionExcludes pharmacological, immunological, metabolic principal actionExcludes pharmacological, immunological, metabolic principal action
Annex XVI devicesDevices without medical purpose may be regulated as devicesExplicit Annex XVI list
IVD inclusionIncluded in the same lawCovered by separate IVDR
Definition languageArabic primary (English translation in guidance)All EU official languages
Borderline guidanceMDS-G008MDCG guidance documents

Differences that matter in practice​

1. Annex XVI devices​

While both EU MDR and the SFDA regulate certain devices without a strict medical intended purpose, the SFDA's approach is implemented through MDS-G008 rather than a legislated fixed list. This means the scope of regulated aesthetic/non-medical devices in Saudi Arabia may differ slightly from EU MDR Annex XVI. Always verify in MDS-G008 rather than assuming EU Annex XVI status translates directly.

→ See Annex XVI Aesthetic Devices — SFDA Treatment

2. IVDs under one law​

In the EU, medical devices and IVDs are governed by two separate regulations (MDR and IVDR). In Saudi Arabia, both general medical devices and IVDs are governed by the same Medical Devices Law and its Implementing Regulation, with IVD-specific requirements addressed within MDS-REQ 1. This simplifies the regulatory landscape for IVD manufacturers.

3. Arabic as primary language​

The Medical Devices Law is published in Arabic as the authoritative text. The English translations provided in SFDA guidance documents (MDS-REQ series) are operational references but are not the legally authoritative source. In any ambiguity, the Arabic text governs.

4. Software qualifying criteria​

The SFDA's qualification criteria for software as a medical device follow IMDRF SaMD principles similarly to EU MDR, but the SFDA has not published a direct equivalent to the EU's MDCG 2019-11 software guidance. Manufacturers should apply conservative principles when assessing whether software qualifies under the SFDA definition.

5. Combination product boundary​

The SFDA applies a principal mode of action test for combination products (device + drug), consistent with EU MDR Article 1(8). However, the SFDA consults its Drug Sector on the medicinal component separately — there is no single combined approval pathway. In the EU, drug-device combinations are handled under one dossier submitted to either the EMA or a national competent authority.

Practical implication​

For most standard medical devices and IVDs, if your product qualifies as a medical device under EU MDR, it will qualify under the SFDA definition. However, always:

  • Verify borderline status using MDS-G008, not only MDCG documents
  • Re-run the classification analysis using SFDA rules (even though they are identical to EU MDR Annex VIII)
  • Document your SFDA-specific classification justification in the technical file — do not simply reference the CE certificate

Further reading​