Short answer

Start from what the supplier does to your device. If a developer’s output implements a risk control or a clinical function, it needs close oversight. Define the scope, and the responsibilities you keep. Ask for evidence of how the supplier actually works, close the gaps in a quality agreement (especially notice of changes before they happen and access to records), and accept every delivery yourself. Then monitor: deliveries, changes, defects and a periodic review. An ISO 13485 certificate is one possible input, not a requirement for every supplier, and never a substitute for controlling what you receive.

What stays with the manufacturer

When a development partner writes your device software, the manufacturer still owns the intended purpose, the requirements, risk management, verification acceptance, release and every regulatory decision. The supplier does work and provides information. A sensible split looks like this:

Who does what when development is outsourced
ActivityManufacturerDevelopment supplier
Intended purpose, requirements, design decisionsOwns and approvesProposes, clarifies
Implementation of the supplied partReviews interfaces and outputsPerforms
Supplier-side testing and recordsReviews; keeps accessPerforms and keeps
Acceptance of each deliveryPerforms and approvesSupports
Risk management of the devicePerforms and approvesProvides information
Changes to the supplied partAssesses and decides before implementationNotifies in advance, provides evidence
Release, labelling, regulatory decisionsDecidesNo role
Complaints, vigilance, field actionsPerformsSupports investigation

Write the split down in the quality agreement. Unclear ownership surfaces at the worst moment: in a Notified Body audit, or during a field action.

What the requirements say

  • EU MDR Article 10(9) requires the manufacturer’s QMS to address “resource management, including selection and control of suppliers and sub-contractors”.
  • EU MDR Annex IX, section 2.2(b): where design, manufacture or verification is carried out by another party, the QMS documentation must describe the methods of monitoring and “the type and extent of control applied to the other party”.
  • Notified Body audits can reach your suppliers. Under Annex IX, the initial audit, the surveillance audits and the unannounced audits may include the premises of the manufacturer’s suppliers or subcontractors “if appropriate” or “where appropriate” (sections 2.3, 3.3 and 3.4).
  • ISO 13485:2016 covers outsourced processes (4.1.5) and purchasing (7.4). That means documented criteria for evaluating and selecting suppliers based on their ability to supply, their performance, the effect on the device and the risk (7.4.1). Purchasing information includes, where applicable, a written agreement that the supplier will notify changes before implementing them (7.4.2). Purchased product is verified in proportion to risk, and supplier changes are assessed for their effect on the device (7.4.3).

None of these says “ISO 13485-certified suppliers only”. They require control proportionate to risk, and evidence that you exercise it.

Decide the level of oversight

Ask what would happen to patients, users or your records if the supplier’s output were wrong, late or unavailable. Use the answer to set a risk category, and write down why. The forms below use three categories, scored as classes 1 to 3 in the approved supplier list:

  • Significant risk (class 1) for the manufacturing process and product or QMS: the output implements device functions, risk controls or clinical algorithms. Expect a full evaluation, a quality agreement, acceptance of every delivery, prior notice of changes and periodic review.
  • Moderate risk (class 2): the service affects availability, data or security (hosting, monitoring) but not device logic. Expect certificates and service terms checked for scope, incident and change notification, and an annual review.
  • Negligible risk (class 3): no effect on the device or QMS records. Basic due diligence.

These categories are a management choice, not a device class. If you use a numeric score to compare suppliers, treat it as an aid. A high score does not offset a missing change-notice clause for a supplier that implements a risk control.

What evidence to ask for

Ask for records, not promises. For a software development supplier:

Evidence to request from a software development supplier
AreaWhat to requestWhat a good answer looks like
CompetenceRole profiles of the people who will do the work; relevant projectsNamed roles with experience in your kind of software, not just a company brochure
Development processDevelopment and code review procedure; which lifecycle activities they will perform for youDefined, followed, and mapped to what your IEC 62304 process needs from them
Version control and buildsRepository and tagging practice; how a build is identifiedEvery delivery traceable to a commit and a build ID
TestingA sample test plan and executed recordExpected and actual results, tester, build, anomalies
DefectsDefect workflow and escalationSafety-relevant defects escalated to you within an agreed time
Change controlChange procedure; what they count as a changeInterface and behaviour changes trigger a notice to you before implementation
SecuritySecure development practice; vulnerability handlingAgreed disclosure to you and fix timelines
RecordsRetention and accessRecords kept for your required period and available to you and your auditors
Sub-tier suppliersWho else is involvedDeclared, and used only with your prior approval
ExitHand-over arrangementsCode, documents and data can be handed over at the end of the contract

A certificate tells you an external body audited the supplier’s QMS against a standard, within a scope. If you rely on it, check the scope, validity and issuing body, and note what it does not cover. In the example, the API supplier held no ISO 13485 certificate. Its capability was assessed from its process and records, and the manufacturer kept acceptance testing.

The quality agreement

The agreement turns your evaluation into obligations. For a development supplier, check it covers:

  • Scope and deliverables, including which records come with each delivery.
  • Change notification: what counts as a change (include interface and schema changes, not just major versions), how much notice, what the notice contains, and that nothing is deployed before your decision.
  • Defects and vulnerabilities: reporting times, escalation of safety-relevant issues, disclosure.
  • Records: retention for at least the period you need, and access for you, your Notified Body and authorities.
  • Audits: your right to audit, and cooperation with Notified Body audits where appropriate.
  • Sub-tier suppliers: only with your prior approval.
  • Acceptance: criteria, and who accepts.
  • Exit: hand-over of code, documentation and data.

After approval: changes, acceptance, reviews

  1. Accept every delivery yourself, in proportion to risk: contract tests, regression tests, review of the supplier’s records. A supplier cannot accept its own work on your behalf.
  2. Assess changes before implementation. Compare the notice with what it affects: requirements, tests, risk controls, interfaces. Decide, record the decision, and only then let the change in. A supplier notice is not a release authorisation. Changed requirements then need re-verification. See how the traceability matrix handles changes.
  3. Review periodically: deliveries and acceptance results, nonconformities and CAPAs, notified and unnotified changes, open conditions, certificate changes. Rate responsiveness, quality, quantity, on-time delivery, cost and support, and compare actual performance with the desired baseline you recorded at the initial evaluation: how the software or service should work when it is functioning correctly. Then decide: retain, improve through a CAPA, or remove.
  4. Keep the register current, with scope, status, review dates and triggers.

Worked example

Fictional example

Example Manufacturer A outsources the report-delivery API of Example SaMD A, a fictional laboratory reporting application, to Example Development Supplier A (EX-SUP-001).

Example SaMD A: evaluation of the API supplier
StepWhat happened (fictional)
ScopeDevelopment and maintenance of the report-delivery API. The API’s acknowledgement drives the “Delivery pending” status, which is part of risk control EX-RC-03.
Risk categorySignificant (class 1): supplier output implements part of a risk control. Every delivery is acceptance-tested by the manufacturer.
EvidenceCompetence summary, development and review procedure, sample test record, recovery description, vulnerability statement, pilot delivery. No ISO 13485 certificate, and none relied on.
GapsDraft contract had no advance notice of interface changes and no access to test records. Recovery had never been exercised.
DecisionApproved with conditions on 6 July 2026, after the quality agreement closed the first two gaps. Recovery exercise required before production use (done 18 August).
MonitoringAcceptance tests on every delivery; first periodic review set for 23 October; earlier review after a failed delivery, an unnotified change or a scope change.
What went wrongOn 24 August the supplier deployed a renamed acknowledgement field without notice. Acceptance tests caught it in the test environment. The cause: its notification trigger only fired on major version numbers.
OutcomeCAPA EX-CAPA-002 changed both sides’ controls. Three later interface changes were notified and accepted before deployment. At the 23 October review the supplier was kept, with closer monitoring of interface changes.

The example is useful because it fails. Approval was sound and the agreement had the right clause, but the supplier’s internal trigger did not match the agreement. The manufacturer’s acceptance testing caught the change before release, and the CAPA (see CAPA for medical software) fixed both sides of the process. Our internal audit guide shows the earlier audit that checked the agreement.

Fictional example. Suppliers, records, dates and decisions are invented. Risk categories and review intervals are local choices for this example, not regulatory classes or mandated intervals.

From practice: before founding TrustedTraceMed I worked on projects where a critical development partner built the device software, including a haemodialysis SaMD certified under EU MDR and an AI dental X-ray product with three suppliers. In both, the manufacturer kept final approval of the documentation.

Signs that need a closer look

  • The supplier cannot show a single executed test record, only a test strategy.
  • Builds cannot be traced to commits, or releases are deployed directly to production.
  • “We will tell you about major changes”, with no definition of a change.
  • Undeclared subcontractors, or offshore teams that appear only in invoices.
  • No access to records after the contract ends.
  • A certificate whose scope does not include software development, or that has expired.
  • Pressure to skip your acceptance testing “because our CI is green”.

Download the forms

Free to download, no sign-up. Forms open in Word or LibreOffice Writer; the approved supplier list in Excel or LibreOffice Calc.

  • Initial supplier evaluation — formDOCX · 16 KB · v1.0 · Nov 2026 · TTM-TPL-SUP-01Supplier and evaluation details, category, what the supply is needed for, criticality, reason and trigger, risk category, evidence reviewed, desired baseline, required steps (agreement, audit, acceptance criteria) and approval.
    Download DOCX
  • Ongoing supplier evaluation — formDOCX · 16 KB · v1.0 · Nov 2026 · TTM-TPL-SUP-02Certificates, regulatory compliance, audit dates, ratings from unsatisfactory to excellent (including actual versus desired baseline), risk estimation factors and the recommendation: retain, improve via CAPA, or remove.
    Download DOCX
  • Supplier change notification — formDOCX · 14 KB · v1.0 · Nov 2026 · TTM-TPL-SUP-03Change overview with urgency and category, current state, proposed change and reason, affected product and documentation, and the risk assessment.
    Download DOCX
  • Supplier evaluation report — formDOCX · 14 KB · v1.0 · Nov 2026 · TTM-TPL-SUP-04Evaluation result (approved, conditionally approved, not approved), required actions and the supplier monitoring plan.
    Download DOCX
  • Approved supplier list — templateXLSX · 14 KB · v1.0 · Nov 2026 · TTM-TPL-SUP-05Live register: status, certifications, risk class 1–3, approval, contract, contacts, criticality for the QMS, evaluation dates and baseline check. Risk scoring and history of amendments tabs.
    Download XLSX

Each template has a document control block and [placeholders] for your company name, product name and document IDs. Adapt it to your own procedures before use. Completing it does not establish conformity or guarantee certification. Select the criteria that fit each supplier’s scope and risk.

Need help setting this up with a real development partner? Supplier controls are part of ISO 13485 QMS implementation. Ongoing coordination with suppliers, reviews and CAPA follow-up can run under ongoing QA/RA support.

Sources