How to do a gap analysis for MDSAP requirements
How to do a gap analysis for MDSAP requirements: Short answer: break ISO 13485:2016 and the extra requirements of the five MDSAP authorities (FDA, Health Canada, TGA, ANVISA, and MHLW with PMDA) into individual items, link each item to the procedure or record that meets it, and treat every item with nothing linked as a gap. Organise the work by the seven processes of the MDSAP audit model, classify each gap as missing, partial or undocumented, give it an owner and a date, then re-run the map after every procedure change. In Matrix Quality, that gap list runs as an internal audit checklist whose findings link straight to CAPA.
A note on our interest: we build quality software at Matrix One. Matrix Quality is the electronic quality management system for medical device and life science companies that have outgrown paper, Word, Excel and SharePoint/Google Workspace. It suits growing teams of 20 to 1,000 people who need an audit-ready, validated QMS without an enterprise price or an enterprise rollout. The method below works in a spreadsheet as well, and the product section says plainly where software changes the cost.
An MDSAP gap analysis compares your existing quality management system against the requirements of all five MDSAP regulatory authorities at once, so you find out where one process satisfies four jurisdictions and where it satisfies none. The work is a mapping exercise: list the requirements, link each one to the process that meets it, and the requirements left with nothing linked to them are your gaps.
What is MDSAP, and which regulators accept it?
The Medical Device Single Audit Program lets one audit, performed by an authorised auditing organisation, satisfy the quality system requirements of five regulators at the same time. The audit model is built on ISO 13485:2016 and then extended with the country specific requirements each authority adds.
| Authority | Country | Status of MDSAP |
|---|---|---|
| Health Canada | Canada | Mandatory for Class II, III and IV devices. MDSAP certification replaced the previous CMDCAS scheme on 1 January 2019. |
| FDA | United States | Voluntary. The FDA says it may continue to accept MDSAP audit reports as a substitute for routine inspections. Electronic Product Radiation Control activities are still inspected by the FDA. |
| TGA | Australia | Voluntary. Accepted as evidence toward conformity assessment. |
| ANVISA | Brazil | Voluntary, and widely used to support Good Manufacturing Practice certification. |
| MHLW and PMDA | Japan | Voluntary. Accepted as part of the QMS conformity assessment. |
The EU is not a member. An MDSAP certificate does not satisfy Regulation (EU) 2017/745, so a manufacturer selling in Europe still needs its notified body assessment separately. That is the single most common misunderstanding we hear about the programme.
The programme is wider than its five members. The FDA MDSAP page, updated 18 December 2025, lists the EU, Singapore's HSA, the UK MHRA and the WHO prequalification programme for IVDs as official observers, and seven affiliate members: Argentina's ANMAT, Israel's Ministry of Health, Kenya's Pharmacy and Poisons Board, Korea's MFDS, Mexico's COFEPRIS, South Africa's SAHPRA and Taiwan's TFDA. None of them is a member, so the five authorities stay the scope of the analysis.
The same page says the MDSAP documents moved on 18 December 2025 to a new MDSAP website managed by the TGA. If your gap analysis template quotes an audit model document from an old FDA hosted copy, check it against the current version before you map anything to it.
What changed for US manufacturers when the QMSR took effect on 2 February 2026?
The US column of an MDSAP gap analysis got shorter. The FDA QMSR page says the Quality Management System Regulation took effect on 2 February 2026 and amends 21 CFR Part 820 to incorporate ISO 13485:2016 by reference, together with clause 3 of ISO 9000:2015 for terms and definitions. FDA adds that this now specifically requires risk management.
Two consequences for the mapping. First, most rows that used to sit under the old Quality System Regulation now collapse into the ISO 13485:2016 rows you already have. Second, the FD&C Act and its regulations still control where they conflict with ISO 13485, so keep separate US rows for medical device reporting under 21 CFR Part 803 and for corrections and removals under 21 CFR Part 806.
Inspections changed on the same day. FDA stopped using the Quality System Inspection Technique (QSIT) and moved to Compliance Program 7382.850, retiring 7382.845 and 7383.001. If your gap analysis borrowed its structure from QSIT subsystems, rebuild it on the seven MDSAP processes below instead.
Why run a gap analysis before an MDSAP audit?
Because the alternative is discovering the gaps during the audit. Most manufacturers arrive at MDSAP with a quality system already certified to ISO 13485:2016, which covers the majority of the audit model but not the country specific additions. A gap analysis tells you how much of the remaining work is genuinely new and how much is documentation of things you already do.
It also stops you building five parallel quality systems. Run properly, the analysis usually shows that one procedure can satisfy several jurisdictions with a small addition, which is the entire point of the programme.
What does the MDSAP audit model actually cover?
The audit model is organised into seven processes rather than into clause numbers, and your gap analysis should follow the same structure so the output maps onto how you will be audited.
| Process | What the auditor examines |
|---|---|
| Management | Quality policy, objectives, planning, management review, and the resources committed to the quality system. |
| Device marketing authorisation and facility registration | That the devices you are auditing are actually registered in each market, and that the registrations are current. |
| Measurement, analysis and improvement | Data analysis, internal audit, nonconformity handling and corrective action. |
| Medical device adverse events and advisory notices reporting | Complaint handling, reportability decisions, and each country's reporting timelines and formats. |
| Design and development | Design controls, design transfer and design changes. Not applicable if you do not design. |
| Production and service controls | Process validation, product identification and traceability, and servicing. |
| Purchasing | Supplier evaluation, purchasing information and verification of purchased product. |
Where do the five jurisdictions add requirements beyond ISO 13485?
These are the areas where an ISO 13485:2016 certified system most often falls short, and therefore where a gap analysis earns its keep.
| Area | What changes by jurisdiction |
|---|---|
| Adverse event reporting | Timelines and thresholds differ. Each authority has its own reportability criteria, forms and clocks, and a single generic complaint procedure will not satisfy all five. |
| Recalls and advisory notices | Each country defines what triggers a field action and who must be told, within what period. |
| Registration and licensing | Evidence that the specific device is authorised in the specific market, kept current, including changes that require notification. |
| Brazil Good Manufacturing Practice | ANVISA adds GMP requirements under RDC 665/2022, which go beyond ISO 13485:2016 in several production and record keeping areas. |
| Japan | MHLW Ministerial Ordinance 169 adds requirements including the roles of the marketing authorisation holder and specific Japanese language documentation. |
| Canada | Canadian Medical Devices Regulations obligations sit alongside the standard, including licence conditions and specific record retention. |
How do you run the gap analysis, step by step?
Fix the scope. Which devices, which sites and which of the five markets. A gap analysis for markets you do not sell into is wasted effort, and scope creep is the most common reason these stall.
Build the requirement list as discrete items. Break each regulation into individually identifiable requirements rather than working from whole documents. One requirement, one row, one identifier.
Map your processes to those requirements. Link each requirement to the procedure, work instruction or record that satisfies it. A link is a claim you have to be able to defend.
Find the unlinked requirements. Anything with nothing linked to it is a gap. This is the actual output and it should take minutes to produce once the links exist.
Classify each gap. Missing entirely, partially covered, or covered in practice but not documented. The three need very different amounts of work and conflating them ruins the plan.
Assign and schedule. Each gap needs an owner and a date, and the plan needs to fit inside your audit timeline rather than alongside it.
Re-run it after the changes. A gap analysis is a live view, not a one-off document. If re-running it is expensive, that is a sign the links live in a spreadsheet rather than in a system.
Why do gap analyses fail?
Four patterns, and all four produce an analysis that looks complete. The first is mapping at document level: claiming a whole procedure covers a whole regulation, which hides every specific requirement inside it. The second is treating a link as evidence, when a link is only a claim until someone checks the linked process actually does what the requirement asks.
The third is doing it once. Regulations change, and a static spreadsheet is out of date the first time a procedure is revised. The fourth is scoping to ISO 13485:2016 alone and assuming the country specific additions are minor, which is exactly where the findings come from.
We hear the spreadsheet problem directly. Across 176 recorded sales calls between February and September 2026, the most common trigger was teams still running quality on Word, Excel and paper (17 companies), ahead of a disliked incumbent tool (15) and engineering and quality held in separate systems (10), per our prospect pain point quote bank of 9 September 2026. Each of those is a place where a gap map goes stale.
How does this work in Matrix Quality?
In Matrix Quality the gap analysis runs through audit management. You plan it as an internal audit, build the MDSAP requirement list as a configurable checklist, record each gap as a finding, and link each finding to CAPA in one click so it carries an owner, a due date and closure evidence. That is how the supplier and audit management page describes it, read on 4 November 2026.
Controlled documents are reviewed, approved, versioned and linked with full traceability, according to the Matrix Quality product page, so a finding can point at the procedure version it concerns. The medical device page says every quality process is structured around ISO 13485, FDA 21 CFR Part 820 and EU MDR. MDSAP's country additions for Brazil, Japan, Canada and Australia are not on that list, so those checklist rows are yours to write.
Published pricing starts from EUR 10,000 a year, there are more than 50 modules, and go-live takes 2 to 6 weeks with our team supporting migration from paper, Word, SharePoint or Google Workspace (product page, read 4 November 2026). Matrix One says 500 life science companies worldwide use Matrix Quality.
What about the design and development process?
Design controls usually sit in a separate tool, and the MDSAP design and development process audits them. If that tool is Matrix Req, a separate Matrix One product, its Compliance Checker imports a standard you hold as a PDF, turns it into a checklist and evaluates each requirement against your project evidence in Matrix Req. Findings are classed as Structural Gap, Contradiction, Execution Gap or Uncertainty, and your team reviews every result before anything is documented.
Matrix Req and Matrix Quality sit on the same Matrix One platform but keep separate records, so run the design half and the quality system half as two checklists and reference one from the other. Our rankings for each half are in the best eQMS software and best requirements management software posts.
What do you need in place before Matrix Quality works?
A short list, and none of it is MDSAP specific except the first item.
The scope decision from step one: which devices, which sites and which of the five markets.
An inventory of your current controlled documents and where each one lives today.
A named approver for each document type, because approval routes are configured, not guessed.
A go-live date, since go-live runs 2 to 6 weeks and the audit date will not move.
Time from your own team for migration, which our team supports rather than does alone.
What should you read next?
For the programme itself, including certification and maintenance, see our guide to MDSAP certification. For the standard underneath the audit model, see what ISO 13485 requires. And because internal audit is one of the seven processes and a frequent source of findings, the internal audit checklist is worth working through before the auditor arrives.
For the US side after the QMSR, see the best QMS software for ISO 13485 and the FDA QMSR. Gap findings become corrective actions, so the best CAPA management software comparison is the next step once the list exists.
Summary: how do you do a gap analysis for MDSAP requirements?
Break ISO 13485:2016 and the country requirements of the five MDSAP authorities into individual items, link each one to the procedure or record that meets it, and treat everything left unlinked as a gap, organised by the seven processes of the audit model. Since 2 February 2026 the FDA rows largely fold into ISO 13485:2016 under the QMSR, while adverse event reporting, field actions and registration evidence still differ by market. Matrix Quality runs the list as an audit checklist with findings linked to CAPA.
Map item by item, never procedure to regulation, or every specific gap hides inside a document.
Spend the effort on the country additions, above all adverse event reporting, which is where findings come from.
Re-run the map after every procedure change, which only stays cheap if the links live in a system.
For the ranking of eQMS tools that can hold this work, see the best eQMS software.
Last updated: 4 November 2026.
Common questions about MDSAP gap analysis
Only in Canada, where MDSAP certification has been required for Class II, III and IV devices since 1 January 2019 and replaced the earlier CMDCAS scheme. For the United States, Australia, Brazil and Japan the programme is voluntary, although each authority accepts MDSAP audit results in its own way. The EU is not part of the programme at all.
No. Regulation (EU) 2017/745 is outside the programme, so a manufacturer selling in Europe still needs a notified body conformity assessment separately. The EU is an official observer of MDSAP, not a member, according to the FDA MDSAP page updated 18 December 2025. Treating MDSAP as covering Europe is the most common misunderstanding we see, and it is an expensive one to discover late.
For a manufacturer already certified to ISO 13485:2016, the mapping itself is usually a few weeks of focused work. What takes longer is closing the gaps, particularly adverse event reporting procedures that have to handle five different sets of timelines and thresholds. Scope the analysis narrowly and the mapping goes quickly.
For most processes, yes, and that is the point of the programme. The exceptions are the areas where the authorities genuinely differ, principally adverse event reporting, field actions and registration evidence. There the usual answer is one procedure with country specific sections rather than five separate procedures.
A gap analysis asks whether your system is designed to meet the requirements. An internal audit asks whether the system as designed is actually being followed. You need both, and in that order: auditing against a system with known design gaps tells you very little.
No, and plenty of manufacturers do the first one in a spreadsheet. The difficulty is the seventh step, re-running it after changes. A spreadsheet map is accurate on the day it is written and decays from then on, so the question is less whether you can produce one and more whether you can keep it current.
Yes, it shortens the US column. Since 2 February 2026, 21 CFR Part 820 incorporates ISO 13485:2016 by reference, so most US quality system rows map to the ISO 13485 rows you already hold. Keep separate US rows for medical device reporting under Part 803 and corrections and removals under Part 806, because the FD&C Act and its regulations control where they conflict with the standard.
Moving into Matrix Quality takes 2 to 6 weeks to go live, with our team supporting you in migrating documents from paper, Word, SharePoint or Google Workspace. Your side brings an inventory of controlled documents, a named approver per document type and time from the people who own those documents. Do the MDSAP gap analysis first, so the migration carries the fixed procedures rather than the gaps.
Keep the old system readable until every migrated record has been checked, and time the switch away from the audit date. Matrix Quality can be configured to your existing workflows in its validated configuration center, per the product page, which means procedures do not have to be rewritten just to fit the tool. Re-run the gap analysis on the new system before the auditor arrives.
Request a demo and get started today.
See how Matrix One connects your requirements, risks, tests, and documentation in one platform.
Thank you
A member of our team will be in contact within 48 hours.