Quality management · ISO 13485:2016

ISO 13485 QMS implementation for medical software

A quality management system built for how software companies actually work: compatible with sprints and CI/CD, with IEC 62304 and ISO 14971 integrated — not a manufacturing template with your logo on it.

Price
€20,000 tailored · €30,000 from scratch
My part takes
3 months tailored, 6 months from scratch
Documents
30–50+ controlled documents, depending on scope
Work format
Remote, with on-site option

Who this is for

  • Medical software start-ups preparing for CE marking or UK market access
  • SaMD companies entering the EU, the UK, Singapore or Malaysia
  • Software companies whose customers require ISO 13485 certification
  • Teams that have outgrown ad hoc processes
  • Companies moving from MDD to EU MDR, where the QMS needs updating
  • AI/ML developers who need controlled change management for models

Why software QMSs go wrong

  • Templates that don’t fit software — design controls written for physical prototypes, not sprint-based development. Auditors notice when the QMS doesn’t match real workflows.
  • No link to IEC 62304 — ISO 13485 design and development controls must map to your software lifecycle, or you can’t show traceability.
  • No change control for releases — every release is a design change and needs a documented decision.
  • Infrastructure left out — your development environment, CI/CD pipeline, cloud hosting and backups must be covered.
  • Supplier controls that ignore SaaS — cloud providers, critical software components and outsourced development need proportionate controls.

So before writing a single SOP, I spend the first weeks documenting how your team works — tools, release cadence and team structure — and design processes your team will actually follow.

What you get

Core QMS processes

  • ISO 13485 gap analysis with a written remediation plan
  • Quality manual, quality policy, scope and process map
  • Document and record control
  • Design and development controls mapped to IEC 62304
  • Risk management (ISO 14971) built into development and change control
  • Management review procedure and templates
  • CAPA — non-conformities, root cause analysis, effectiveness checks
  • Internal audit programme with internal auditor training

Software-specific processes

  • Software development lifecycle (IEC 62304) for safety classes A, B and C
  • Configuration and change management — version control, change requests, release authorisation
  • Verification and validation — plans, protocols, requirements-to-test traceability
  • Cybersecurity management — vulnerability handling, penetration testing, incident response (MDCG 2019-16)
  • Infrastructure and environments — development, test and production, including cloud
  • Supplier and purchasing controls, including cloud and outsourced development
  • Post-market processes — complaints, PMS, vigilance and PSUR procedures
  • Certification audit preparation — Stage 1 and Stage 2, mock audit, response to findings
Agile and DevOps

ISO 13485 that works with how you ship

You don’t need to give up sprints, CI/CD or frequent releases. The standard sets requirements for outcomes and records, not for a waterfall process.

Design controls at sprint level

Design inputs and outputs mapped to user stories and features; design reviews built into your existing ceremonies.

Change control for CI/CD

Gates at release level, not commit level. Test evidence captured from your pipeline, and a release authorisation step that fits your cadence.

Traceability in your tools

Requirements-to-test traceability kept in Jira, GitHub or Azure DevOps rather than in a separate spreadsheet.

Risk in the backlog

ISO 14971 analysis triggered by new design inputs and updated during the sprint, not once a year.

Lean records

Records captured where the work happens — commits, test reports, review comments — with manual records kept to what the standard requires.

Processes people follow

Workshops with developers and product owners so the QMS is understood and used. A QMS that only lives in a folder fails at the first surveillance audit.

Guide: ISO 13485 design controls in Jira and GitHub →

Software lifecycle

IEC 62304 inside the QMS

IEC 62304 (current edition: IEC 62304:2006+AMD1:2015) sets the software lifecycle processes for medical device software. In this service it is not a separate document set: the software development plan, safety classification (A, B or C), SOUP management, verification records and maintenance process are built into the same procedures and tools as your design controls.

If you only need help with IEC 62304 — for example to close gaps found by a Notified Body — ask for that scope in the free call.

Stages and timing

A full implementation over six months. A tailored implementation built on processes you already have takes about three months.

  1. Weeks 1–3

    Current-state gap analysis

    Your processes, development workflow, tools and team structure assessed against ISO 13485. Deliverable: written gap analysis with priorities.

  2. Months 1–2

    Quality manual and core procedures

    Quality manual, document control and management responsibility procedures; the QMS document structure and numbering.

  3. Months 2–4

    Process documentation

    The remaining SOPs, work instructions, forms and templates, reviewed with your team until they are workable.

  4. Months 4–5

    Go-live and training

    Roll-out, training, first quality records, first management review, CAPA and internal audit started.

  5. Months 5–6

    Internal audit and certification readiness

    A full internal audit cycle, findings closed, preparation for the Stage 1 and Stage 2 audits, and support during the certification audit.

The certification audit itself is scheduled and carried out by the certification body or Notified Body you choose. Ask candidates for their current lead times when you request quotes.

Who does what

Responsibilities in a QMS implementation
ActivityYour teamMeCertification body / Notified Body
Quality policy, scope, resourcesTop management decidesDrafts, advisesAudits
Procedures and formsReviews, approvesWrites and adaptsAudits
Using the processes and keeping recordsEvery dayCoaches, checksSamples records
Internal audit and management reviewOwns, attendsRuns the first cycle, trains auditorsReviews evidence
Certification decision——Decides

What I need from your team

  • A management representative with authority to approve documents
  • Access to your development tools and current documents
  • Time from developers and the product owner for workshops and reviews
  • Someone who will own the QMS day to day after go-live

Not included

  • Certification body or Notified Body fees
  • EU MDR technical documentation for your product — see EU MDR consulting
  • Support for later surveillance audits — available as ongoing QA/RA support
  • eQMS software licences

Price

Three tiers with set prices:

  • Template package — €5,000, 1 month. Predefined SOP and document templates: the fastest route to a documented QMS when a baseline structure is enough. What the templates cover.
  • Tailored implementation — €20,000, 3 months. A QMS customised to your product and scope, with hands-on guidance through the setup. Right-sized for a defined SaMD scope.
  • Full implementation — €30,000, 6 months. A complete QMS built from scratch, with end-to-end ownership of the build, for complex or first-time systems. Paid in three stages: 25% on signing, 25% at month 3, 50% at month 6.

Every QMS engagement includes a signed quality agreement, an agreed communication plan and a roadmap with subtasks, owners and estimates. Fees are in EUR, excluding applicable taxes.

Certification body fees for the initial audit and annual surveillance audits are separate; request quotes from two or three bodies.

Related case · QMS from scratch

Haemodialysis patient management SaMD

A complete ISO 13485 QMS built for the manufacturer, with SOPs and templates, ahead of EU MDR and Malaysia MDA submissions.

Read the case →

Questions about ISO 13485

EU MDR Article 10(9) requires every manufacturer to have a quality management system. EN ISO 13485:2016 is the harmonised standard used to show that the QMS meets this requirement. For Class IIa and higher, the Notified Body audits your QMS as part of the conformity assessment, so a separate ISO 13485 certificate is not legally required for CE marking. Many customers, and some regulators outside the EU, still ask for one.

About three months for a tailored implementation built on processes you already have, and six months for a complete QMS built from scratch, to readiness for the certification audit. The certification body’s scheduling and the Stage 1 and Stage 2 audits come after that.

Yes. Neither ISO 13485 nor IEC 62304 requires waterfall development. The key is design controls that fit your sprint cadence: design inputs and outputs at feature level, change control that gates releases rather than blocking development, and traceability in the tools your team already uses.

€20,000 for a tailored implementation (3 months) or €30,000 for a complete QMS built from scratch (6 months, paid 25% / 25% / 50%). If a baseline structure is enough, the template package costs €5,000. Fees are in EUR, excluding taxes. Certification body fees for the initial audit and annual surveillance audits are separate and quoted by the body you choose.

ISO 13485 certification covers your organisation’s quality management system, not a specific product. CE marking under EU MDR covers a specific device. For Class IIa and higher, the Notified Body assesses both your QMS and the device’s technical documentation and clinical evaluation. I can support both workstreams.

Yes, through ongoing QA/RA support: management review, CAPA, regulatory updates, internal audits and preparation for surveillance audits.

Plan your QMS

A free 30-minute call: your current processes, what the QMS needs, and how long it will take.

Request a free call