Table of contents
At a glance
What does the current QMSR change for a medical device manufacturer’s production and QMS software?
The QMSR took effect on 2 February 2026. The former § 820.70 was removed, and Part 820 incorporates ISO 13485:2016 through § 820.7. FDA explains validation of production and QMS software by reference to subclauses 4.1.6, 7.5.6 and 7.6. Approach and scope must reflect the risk of use. Update obsolete mappings while retaining applicable existing evidence. The 3 February 2026 CSA guidance supports risk-based implementation but does not replace binding requirements or assessment of the actual configuration.
- Old paragraphs shall not be unverifiedly considered as current mandatory sources.
- Assign ISO references, FDA supplements, and CSA recommendations separately.
- Gap in requirements and mere editorial reference only.
1. Define operation and software usage
The Quality Management System Regulation applies to the relevant medical device sector as specified in Part 820. A company is not identified solely by any US customer or software designation. Assess the role of the operation, the products, and where applicable, relevant exemptions. Only thereafter can the specific production or QMS application be appropriately classified.
In addition, distinguish software that is itself a medical device or a component of a medical device from software used for manufacturing and quality management. The current CSA Guidance addresses the latter category. A laboratory, planning, or documentation function may be relevant depending on its intended use. General office software is not solely deemed a validation-required application merely because it is used at the manufacturer's site.
2. Use the current regulatory structure
The QMSR is effective as of February 2, 2026. The current Part 820 incorporates §820.7 from ISO 13485:2016 and includes additional FDA requirements. §820.10 outlines the framework for a documented quality management system. The previous §820.70 has been superseded by the QMSR.
The FDA-CSA-Guidance of February 3, 2026 takes this structure into account. It refers to certain ISO subsections, including 4.1.6, 7.5.6 and 7.6, when validating software. The ISO-Verweise follow the FDA-Explanation here; complete standard requirements must be checked on the relevant text.
3. Establish a current requirements chain
Our own matrix helps distinguish between mandatory source, recommendation, and operational implementation. A SOP can combine multiple elements. Nevertheless, it must remain clear whether a specific instruction originates from a regulation, an incorporated standard, a guidance document, or an internal decision.
Do not rely solely on summary information or presentation materials to adopt normative details. For full implementation, responsible personnel must have access to the relevant requirements. A public FDA reference is sufficient to identify the applicable source; it does not automatically substitute for a comprehensive review of all pertinent normative content.
| Level | Specific reference | Significance for the software | Verification scope |
|---|---|---|---|
| Regulation | Part 820, specifically §§ 820.7 and 820.10 | Current QMSR Framework | Applicability and current references determine |
| Applicable Standard | ISO 13485:2016 within the QMSR framework | Applicable requirements based on specific usage scenario | Verify relevant full text within the organization |
| FDA-Addendum | About §820.35 for certain records | Additional content for the appropriate process | Assign specific data and evidence to particular cases |
| Final text is non-binding guidance | CSA 2026 | Risk-based Assurance Recommendations | Select appropriate methods with justified rationale |
| Own regulation | SOP and Work Instruction | Responsibility and Implementation | Do not establish an internal practice as a regulation. |
4. Distinguish three types of obsolete inventory
An outdated paragraph may represent a redactional issue, while the technical process remains adequately safeguarded. It could also indicate a genuine gap in requirements. A third possibility is a mismatched application: the system is currently being used for additional decisions that were not present in the original documentation.
Therefore, do not assess only search results under §820.70. Review the specific professional justification associated with each. Is it a general validation rationale, a specific documentation obligation, or an internal testing instruction? Re-categorize the statement and evaluate its implications. Simply replacing references globally may obscure incorrect associations.
5. Example: three documents from a complaint investigation application
A manufacturer uses an application for the capture and processing of complaints. Three documents contain outdated references. In the example, two additional data fields and a new automated routing feature have been introduced. These changes are evaluated separately from the source correction.
The planned actions link the current source assignment with the actually modified application. For each result, assess whether a document amendment is sufficient or whether additional requirements and supporting evidence are required. A simple reference update must not obscure the new functionalities.
| background | Finding | Professional judgment | Expected evidence |
|---|---|---|---|
| Validation SOP | General reference to the previous §820.70 | Update the requirement chain; assess the previous method for suitability | Justified source attribution and document amendment |
| Requirements overview | Two new complaint fields are missing | Compare current record contents with actual usage | Enhanced requirements and corresponding tests |
| Test completion | New redirection not recorded | Evaluate sequence of errors and existing controls | Targeted Assurance with Visible Open Points |
| Closure | Combine source corrections and functional changes together | Evaluate completed actions and remaining gaps separately | Traceable decision regarding current usage |
6. Utilize appropriate existing evidence where available
A new regulatory version does not automatically render any previous test obsolete. It is essential whether the test's conclusions remain relevant to current usage and present requirements. A documented test for detecting missing mandatory information may still be relevant. However, it does not validate any newly introduced forwarding logic.
CSA supports the use of appropriate existing evidence, including supplier information, provided such evidence is of sufficient quality and coverage. Review version, configuration, and scope. Specifically document the remaining gaps. A statement such as "already validated" is equally weak without this linkage, just as a blanket requirement to reperform all tests due to QMSR is insufficient.
7. Plan the involvement following open decisions
For a small or medium-sized company, effort depends mainly on the state of the requirements mapping and the actual scope of change. A well-described system with unchanged use presents different work from an application with unknown interfaces and undocumented rules. Estimate time and cost from those differences.
Name responsible parties for regulatory scope, specialist process, technical configuration, and evidence evaluation. These roles may be distributed across different organizational units. It is important that an open standard issue is not resolved by a technical assumption. Obtain the required standard access and clarify ambiguous interpretations prior to establishing specific testing expectations.
8. Checklist for a Robust Transition
Close the update with a clear and traceable overview: which sources were corrected, which knowledge gaps were identified, and what evidence supports current usage? A fully revised SOP alone does not answer the question regarding the actual system configuration.
The following internal list can be integrated into the existing change control process. It is not a complete QMSR-compliance catalog and does not serve as a substitute for ISO 13485. Its value lies in linking source documentation and specific software impacts.
- Operation, product area, and software usage restricted.
- Current Part 820 references and relevant Norman requirements assigned.
- Historical references have been assessed for their technical validity.
- Correct functional gaps separately.
- Existing evidence for current coverage is assessed.
- Additional assurance and open questions clearly addressed.
- Current usage, responsibilities, and change closure documented.
Project experience and collaboration
Review outdated references and retain evidence that remains applicable
If your SOP still cites former § 820.70, we examine the activity it supported with quality and the system owner. Where existing evidence still covers current use, a documented mapping to the current requirement may suffice. If the function, configuration or consequences of failure have changed, we assess the additional testing needed. We link the current requirement, actual use and risk-based evidence plan. Changing a section number alone cannot establish that link.
Frequently asked questions about Software validation under the FDA QMSR
Is §820.70 still the current basis for software validation?
No. The former § 820.70 has been deleted since 2 February 2026. The current Part 820 is decisive with the ISO-13485 requirements included in § 820.7 and the supplementary FDA rules. Historical documents may retain their references at that time; current working instructions require a suitable today's assignment.
Does QMSR apply to every software used by a medical device manufacturer?
Not every application has the same reference. The applicable operating and product scope as well as the concrete use for production or quality management are decisive. General business applications and device-related software are to be classified separately. A flat list according to product name is not sufficient.
Does CSA replace software validation?
CSA describes a risk-based approach to creating trust in the intended use. Guidance does not abolish binding validation requirements. It supports the selection of appropriate activities and evidence, rather than simply reducing the amount of documents.
Sources: [2]
Must all previous validations be performed anew?
Does the FDA Guidance serve as a substitute for ISO 13485?
No. The guidance explains and cites selected aspects. For complete application of the referenced standard, you need access to its relevant text. Public FDA references can assist with alignment but do not substitute for a full evaluation of the applicable normative requirements for your process.
How do we handle historical §820.70 references in closed files?
Is the supplier's ISO certificate sufficient?
A certificate can provide information on the quality management system. It does not automatically validate every function of your configuration. Review the actual supplier documentation and its scope of coverage. Existing relevant evidence may be utilized; any remaining use-specific questions must be addressed.
Sources: [2]
Does each new complaint function require the same test scope?
Does Part 11 no longer apply by QMSR?
However, its applicability remains to be separately evaluated. Electronic records required under Part 820 may additionally trigger Part 11 controls. CSA explicitly references this relationship and distinguishes between required evidence and technical logs lacking a corresponding record purpose.
Sources: [2]
What should be updated first?
Begin with applicability and requirement chain. Thereafter, active SOPs, system requirements, and gaps in validation evidence can be systematically reviewed and updated. A simple editorial replacement of all previous numbers may obscure the fundamental question of whether the current software usage is adequately secured.
Sources and review date
Source date: 7 October 2026. Regulatory requirements, guidelines, and industry practices must be categorized separately. Tables, figures, and case examples are to be considered standalone reference materials; they do not constitute completed product testing.
- 21 CFR Part 820 – Quality Management System RegulationCurrent QMSR text, effective 2 February 2026. See sections 820.1, 820.7, 820.10, 820.35 and 820.45.
- FDA: Computer Software Assurance for Production and Quality Management System SoftwareFinal guidance of 3 February 2026. Non-binding recommendations for production and quality management system software in the medical device sector.
Sources checked: .
Jointly develop the specific evidence process
We support you in aligning the current requirement chain and the existing software evidence with your medical device process.
- Computer system validation →
Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

