ISO 13485:2016 MDR (EU) 2017/745 Traceable during audits

Custom medical QMS software development

A quality management system for medical devices is not a folder of documents with approval stamps. It is the system with which you demonstrate that a complaint leads to an action, that action to a changed procedure, and that procedure to retraining of exactly the people who work with it. Appfront builds such software to your requirements, and tells you when a validated off-the-shelf package is a better fit.

Your quality system is something different from your product software

Two topics are often confused. The first is software that is itself a medical device or is part of one. That falls under IEC 62304:2006+A1:2015 with safety classes A, B and C, is linked to ISO 14971 and follows a single product through to market approval. If that is your question, go to building medical device software.

This page is about the second: the internal system with which your organisation governs its processes, across all products. That exists even before a single line of product code has been written. It covers document control, complaints, CAPA, change management, training, suppliers, internal audits and management review.

Usually you need both. Your product software is assessed within the technical documentation of that product; your quality system is assessed as a system, year after year.

The trail an auditor follows

An audit is sampling, not a check on approval stamps: the auditor picks one case and follows it through your organisation to see whether there is evidence at every link.

Take a complaint from the field. First question: is this a complaint in the sense of the standard, or merely feedback? ISO 13485:2016 separates the two in clauses 8.2.1 and 8.2.2 and requires you to document how you make that distinction. Second question, with a clock attached: is it reportable, for which clause 8.2.3 requires a procedure? That clock starts at the moment you become aware of it; if your complaint flow is scattered across a mailbox, a service tool and a spreadsheet, that moment is not defensible.

If a CAPA follows, it comes with a root cause and a corrective action. Suppose that action changes a work instruction: that document had a previous version on which people were trained, and clause 6.2 asks not only that you train, but that you assess the effectiveness of that action. So the auditor will ask who worked with the old version, who was retrained, when, and what shows that it has stuck. And whether the employee who joined two weeks later was ever assigned that instruction.

1
Complaint and assessment

One entry point for all signals, with a recorded moment of awareness.

2
CAPA and root cause

Links back to the complaint and forward to what the action affects: procedures, risk analysis, batches.

3
Change and retraining

The new version assigns training to roles, including whoever joins later.

4
Effectiveness review

A scheduled task with its own evidence. As long as it remains open, the file stays open.

Why CAPA files get closed while the problem remains

Most organisations have their CAPA process neatly documented on paper. Where it goes wrong is almost always the same point: the action is carried out, someone ticks off that it happened, and the file is closed. What is missing is the later confirmation that the problem is genuinely gone. Implementation is not effectiveness. Only when that complaint category stays away, or a sample shows that people now work differently, have you demonstrated anything.

Clause 8.5.2 also asks for something that is often skipped: verifying that the corrective action itself has no adverse effect on regulatory compliance, or on the safety and performance of the device. An action that covers one risk and introduces another is not a solution.

CAPA procedures have for years been among the most frequently cited deficiencies in FDA inspection observations, with the same gist: closed without a substantiated effectiveness review. Software can enforce this by treating that review as a standalone task, not as a field in a form.

  • A review date that is separate from the implementation date
  • Evidence that must demonstrate effectiveness is defined in advance
  • A closing rule that keeps the file open until that review is complete

What such a system really needs to support

The modules are the easy part; any organisation can get document control, a complaints register and a CAPA list built. The difference lies in how it all fits together, and whether that holds up as people, versions and products change.

Relationships are the product

Complaint, deviation, CAPA, procedure, training assignment, supplier, batch number: each object refers to the others, in both directions. If those are typed-in text references, the trail exists only in the quality manager's head and leaves with them.

Approval date and effective date

A document has a moment of approval and a moment at which it becomes effective; retraining happens in between. A system that only knows the status approved cannot show who was allowed to work with which version on which day. Assign training to roles, not to a list of names entered once.

Permissions, signatures and logging

Who may approve is a question of role, not of person; otherwise the system grinds to a halt as soon as someone changes job. The audit trail records the old value, new value, who, when and why, and cannot be altered by anyone.

Data that feeds the management review

The management review requires a fixed set of inputs: complaint trends per product family, CAPA lead times, overdue effectiveness reviews, internal audit outcomes and supplier performance. If you have to pull those by hand from four systems, you have a reporting project on your hands.

The frameworks this system has to fit into

ISO 13485:2016 is the current edition, the third. In Europe, EN ISO 13485:2016+A11:2021 applies, with Annexes ZA and ZB showing, clause by clause, which MDR and IVDR requirements are covered fully, partly or not at all. Those annexes show where you need to do more than the standard.

The obligation comes from MDR (EU) 2017/745. Article 10(9) requires manufacturers to establish, maintain and continuously improve a quality management system, proportionate to the risk class and type of device, and lists what it must cover: regulatory strategy, risk management, clinical evaluation, change management, post-market surveillance and UDI.

A notified body is a conformity assessment body designated by a Member State and listed in the NANDO database; there are four in the Netherlands. For class I devices without sterility, measuring function or reusability, you declare conformity yourself; where those do apply, Annex IX of the MDR requires a surveillance audit at least annually and an unannounced audit at least once every five years. Market surveillance is handled by the IGJ (the Dutch Health and Youth Care Inspectorate).

If you supply outside Europe, more applies: the US Quality Management System Regulation took effect on 2 February 2026 and incorporates ISO 13485:2016 by reference into 21 CFR part 820; through the Medical Device Single Audit Program, a single audit can serve Australia, Brazil, Canada, Japan and the United States. If your system touches patients' personal data, your GDPR compliance platform comes into play as well.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

The validation burden that lands on you

This point often comes up too late in conversations about building in-house. Clause 4.1.6 of ISO 13485:2016 requires you to validate the application of computer software in your quality system before it goes live and again after changes to the software or its application, to an extent proportionate to the risk, with records that you retain.

With a bought eQMS, the vendor supplies a large part of that file. If you build it yourself, that burden shifts to you, every time a release touches a quality process. Every handy improvement to the CAPA workflow then calls for an assessment, a round of testing and a record.

That is manageable and sometimes worth it, but it is a recurring item in your quality organisation, not a project cost. If you don't plan for it, you will discover it during your first surveillance audit.

  • Risk class per system function, with the corresponding depth of validation
  • Test evidence at go-live and at every relevant change
  • A change procedure that determines when revalidation is needed
  • Validation records that outlive the system

When custom isn't the answer

For a considerable share of medtech organisations, a validated eQMS is the wiser choice; it would be dishonest not to say so. Packages such as Greenlight Guru, Qualio, MasterControl, Veeva Vault QMS and Matrix Requirements are built around the structure of ISO 13485 and carry part of the validation burden. If you have a standard portfolio and processes that don't differ materially, building is almost always the more expensive and slower route to the same result.

Custom development only becomes a reasonable trade-off in four situations. The first is a genuinely different process, for example an organisation that both manufactures devices and provides a self-regulated service under one system. The second is heavy integration, where record-keeping only works if the system is connected to your PLM, MES, production line or requirements tooling. The third is a package that forces your organisation into a straitjacket, leaving everyone to build workarounds in Excel. The fourth is being stuck on a vendor's roadmap.

There is a middle route that often works: the off-the-shelf package remains the system of record for the core processes, and you only build the part that differs. That requires an interface that maintains traceability across the system boundary, and two environments that are both validated under 4.1.6. That is why we start by asking where you differ; if it turns out that a package fits better, we will say so.

Frequently asked questions about medical QMS software

The questions quality managers ask just before they make a choice.

For many medtech organisations, that is indeed the better choice. Packages such as Greenlight Guru, Qualio, MasterControl, Veeva Vault QMS and Matrix Requirements are built around the structure of ISO 13485:2016 and come with validation documentation. Custom development only makes sense when your processes genuinely differ, or when you need to integrate heavily with your own development or production systems.

You do, as the manufacturer. Clause 4.1.6 of ISO 13485:2016 requires you to validate the use of computer software in the quality system before it goes into use and again after changes, in proportion to the risk. With a purchased eQMS, the vendor supplies a large part of that file; if you build it yourself, you draw it up for every release that affects a quality process.

It assesses your processes, not your supplier's software. It will, however, ask for your validation file under clause 4.1.6 and for traceability: can you follow a complaint through to the effectiveness review of the associated CAPA? Under Annex IX of the MDR, this happens at least annually, and unannounced at least once every five years.

Usually not. Software built around processes you haven't yet defined captures the wrong processes and makes them harder to change afterwards. Get your process architecture in order first, and only automate what has proven stable. If you are working towards a first certificate, you are better off with a validated off-the-shelf package.

Agree up front who owns the source code, where the validation file is kept, and in what format you can get your data out, including the audit trail and the links between records. Ask for documentation that another party can read. These questions apply just as much to a package vendor.

Article 10 of the MDR (EU) 2017/745 requires the technical documentation, the EU declaration of conformity and any certificates to remain available for at least ten years after the last device has been placed on the market, and at least fifteen years for implantable devices. For the system, that means exportable formats and a migration path.

Related services

These projects most often run alongside a quality system.

Custom medical device software development

For software that is itself a medical device: development in accordance with IEC 62304, risk management in accordance with ISO 14971 and technical documentation for market approval.

Custom GDPR compliance platform development

If you process patients' personal data, a record of processing activities, retention periods and data breach registration come on top: a separate file with its own supervision.

Discuss where your quality system differs

Tell us which processes don't fit what an off-the-shelf package assumes and which systems need to be involved. We'll go through which part you're better off buying, which part justifies building, and what the validation under 4.1.6 will require of you.

Edit content