ITF Health

ISO 13485 for device makers and distributors

A medical device quality system built to the standard and to what SFDA expects your type of establishment to hold.

Standard
ISO 13485:2016, adopted as SFDA.MD/GSO ISO 13485
Certificate required
Manufacturers, importers and distributors in categories A and B
Authorised reps, categories C and D
Documented evidence, or an SFDA inspection
Certificates issued by
Bodies SFDA recognises: SFDA-licensed in the Kingdom, IAF-accredited outside it
First system
Timeline set at scoping, by what you do

ISO 13485:2016 is the quality management standard for medical devices. SFDA requires manufacturers, importers and distributors in establishment categories A and B to hold an ISO 13485 certificate from a body it recognises, and asks authorised representatives and category C and D importers and distributors for documented evidence or an SFDA inspection. We build that system with your people.

A medical device supply line from overseas manufacturer to authorised representative, importer, warehouse and hospital, with the ISO 13485 clause governing each handover: 7.4 purchasing, 7.5.9 traceability, 7.5.11 preservation. Design and production clauses sit above the distributor's part of the line as excluded. A return path carries complaints and recalls back down the line, with clause 8.2.2 complaint assessment and a branch to SFDA under 8.2.3.A DEVICE, FROM MAKER TO HOSPITALEXCLUDED OR NOT APPLICABLEJUSTIFIED IN THE MANUAL, 4.2.2DESIGN AND DEVELOPMENT · 7.3PRODUCTION CONTROLS · 7.5.1 · 7.5.6THE DISTRIBUTOR'S SYSTEMMANUFACTUREROVERSEASAUTHORISED REPIN THE KINGDOMIMPORTEROR DISTRIBUTORWAREHOUSEMDS-REQ 12HOSPITALTHE CUSTOMER7.4 PURCHASINGSUPPLIER FILE7.5.9 TRACEABILITYLOT AT GOODS-IN7.5.11 PRESERVATIONLOGGER DATA, READ7.5.9 TRACEABILITYLOT ON DELIVERYCOMPLAINTS AND RECALLS RUN BACK DOWN THE SAME LINEA MOCK RECALL TRACES ONE LOTTO EVERY HOSPITALSFDA8.2.3 REPORTING8.2.2 EVERY COMPLAINT ASSESSEDFOR A REPORTING DECISIONWHAT AN SFDA INSPECTOR ASKS A DISTRIBUTORTRACE ONE LOT TO EVERY HOSPITALSHOW THE COMPLAINT LOGWHO REPORTS AN ADVERSE EVENTWHO READS THE LOGGER DATA
A distributor's system, built around the handoversDesign and production sit outside it, with the justification written into the manualSwipe to pan
  1. 01 Enquiry
  2. 02 Survey
  3. 03 Scope
  4. 04 Plan
  5. 05 Execute
  6. 06 Evidence
  7. 07 Review
  8. 08 Next cycle

ISO 13485 for device makers and distributors sits at step 5 of the same eight steps, with health's names. You receive completed task records.

01

The distributor running a factory's manual

A common failure is a distributor holding a quality manual written for a factory.

It describes design control, production and process validation that the company does not do. Meanwhile the things a distributor must do well are thin or missing.

Ask a distributor to trace one lot of catheters from the day it arrived to the three hospitals that received it, and the answer is often a spreadsheet with the hospital column blank. Ask to see the complaint log, and product complaints sit beside late-delivery complaints. Ask how an adverse event reaches SFDA, and nobody owns it. Those are the questions an SFDA inspector asks. They are also the ones that matter on the day a manufacturer issues a recall.

ISO 13485 lets a company exclude design and development where it does not design, with the justification written into the manual. A distributor's system should be smaller than a manufacturer's, and sharper where the risk is: traceability, storage, complaints, reporting and control of the manufacturers it buys from.

02

What ISO 13485 adds to ISO 9001, and where it asks for more

Companies holding ISO 9001 often assume the step is small. It is not. ISO 13485 adds device-specific requirements and makes some shared ones stricter, because it is written for regulators rather than for customers.

RequirementWhat it means in practiceClause
Regulatory requirements built into the systemYour procedures cite what SFDA requires, not only what the standard says.Throughout, from 4.1
A medical device file per device typeOne file that holds or points to everything about the device.4.2.3
Risk management across product realisationA documented risk process, usually built on ISO 14971.7.1
TraceabilityLot or serial numbers traceable to the customer who received them.7.5.9
Preservation of productStorage and handling conditions controlled, and the records read.7.5.11
Complaint handlingEvery complaint assessed for whether it must be reported.8.2.2
Reporting to regulatory authoritiesA procedure that ends at SFDA, with a named person responsible.8.2.3
Validation of software used in the systemThe spreadsheet or system you track lots in is validated for that use.4.1.6
03

Documents you keep

01

The requirement map

What SFDA expects of your establishment type, on one page, with the requirements that sit beside the quality system.

02

The gap report

Clause by clause and SFDA requirement by requirement, with every exclusion justified.

03

The documented system

Sized to your activities and under your document control, with procedures written by the people who do the work.

04

The traceability register

Lot or serial numbers from goods-in to the customer, and the mock recall record that tests it.

05

The complaint and vigilance procedure

Every complaint assessed, ending at a written decision on whether it is reported to SFDA.

06

The internal audit report and review minutes

The system audited as an assessor would audit it, then reviewed by management, before anybody external arrives.

04

Seven steps, from category to readiness pack

Each step ends with something on paper.

  1. 01

    Establish your category and role

    Manufacturer, authorised representative, importer, distributor or a mix, and which SFDA requirements follow. Ends with the one-page requirement map.

  2. 02

    Walk a device through the business

    From purchase order to hospital delivery, and back again for a complaint or a recall. Ends with the process map, risks marked.

  3. 03

    Gap analysis

    Every clause and every mapped SFDA requirement against what exists. Ends with the gap report and the justified exclusions.

  4. 04

    Build

    Procedures written with the people who do the work, and forms designed for the warehouse floor, all under document control.

  5. 05

    Run it

    Real records: goods received, deliveries made, a complaint handled and a mock recall traced from goods-in to the hospital.

  6. 06

    Internal audit and management review

    The system audited as an assessor would audit it, findings closed, then reviewed and minuted by management.

  7. 07

    You choose a certification body

    You approach a body SFDA recognises, on your schedule, with the readiness pack in hand.

05

A Riyadh distributor, from a borrowed manual

A Riyadh distributor supplies single-use devices to hospitals from several overseas manufacturers. Its licence renewal is due, a hospital tender has asked for ISO 13485, and it holds ISO 9001 with a manual a previous consultant wrote for a manufacturing plant.

We start with a mock recall: pick a lot delivered last year and trace it. The goods-in record has the lot number; the delivery notes do not. The warehouse temperature logger records every hour, and nobody has read the data in months. Complaints about damaged cartons and complaints about device performance share one log, and none has been assessed for reporting to SFDA.

The manual is cut down to what the distributor does, with design and production excluded and justified. Lot numbers are added to the delivery note and the traceability register. The logger data is reviewed weekly and the review is signed. Complaints are split, and device complaints go through an assessment that ends at a reporting decision. A supplier file is opened for each manufacturer, holding its marketing authorisation, its certificate and the agreement.

After the team has produced records, the mock recall is repeated and traces to every hospital. The distributor holds a quality manual with justified exclusions, a procedure set, the traceability register, two mock recall records, the complaint and vigilance log, a supplier file per manufacturer, an internal audit report and management review minutes. It then approaches a certification body of its own choosing.

06

SFDA's expectations, by establishment

The standard is the same for everyone. What SFDA asks you to hold is not. Its March 2025 guidance, MDS-G024, maps each clause of ISO 13485 to its own requirements. Your category as an importer or distributor comes from the questionnaire you completed in SFDA's GHAD system, and if you do not know it, it is the first thing we find out.

A full system, with a certificate

A full ISO 13485 system with a certificate from a body SFDA recognises, covering design wherever you design. Beside it sit an industrial licence, the technical documentation for each device and its marketing authorisation.

  • Design and development in scope wherever you design
  • Production and process validation records from the system in use
  • A medical device file for each device type
07

Questions device companies ask

Q01

We only distribute. Do we really need ISO 13485?

If SFDA places you in category A or B, yes, a certificate. In categories C and D, SFDA accepts documented evidence or its own inspection, and the evidence is an ISO 13485 system either way. The system for a distributor is smaller than for a manufacturer.

Q02

We hold ISO 9001. Is that enough?

Not for SFDA. ISO 13485 adds device-specific requirements and makes some ISO 9001 requirements stricter, as the table above shows. Your 9001 system is a good foundation, and much of it carries over.

Q03

What goes in a medical device file?

Clause 4.2.3 asks for one file per device type that holds or points to everything about it: the description and intended use, the labelling, the specifications, and the procedures for making, storing, handling, installing and servicing it. For a distributor, much of it is the manufacturer's documentation, referenced and kept current.

Q04

Can you get us certified?

No. We build the system and you approach a certification body SFDA recognises. SFDA keeps the two roles apart: staff of the bodies it licenses must not have consulted on medical devices, and may hold no financial interest in the companies they assess.

Q05

How long does it take?

The timeline is set at scoping, from what you do with devices and what your current system already covers. Most of it is spent producing records, which need time to exist.

Start with the requirement map

One page that says what SFDA expects of your establishment type, and where your current system stands against it.

Book a gap call