Regulations and compliance · Practical guide

QMSR and ISO 13485: when do you need the full text of the standard?

An FDA document that mentions an ISO clause gives only part of the basis for a software requirement. Medical device manufacturers need to identify the incorporated edition, their own activity and the actual provision available to them. Build traceable references and distinguish a summary in guidance from the text of the standard.

Table of contents

At a glance

What can you conclude from FDA references to ISO 13485?

The QMSR incorporates ISO 13485:2016 through § 820.7 and adds US requirements. FDA’s CSA guidance explains that subclauses 4.1.6, 7.5.6 and 7.6 require validation of production and QMS software for its intended use. The approach and extent of validation and revalidation must reflect the risk of use, including the impact on product conformity. This account follows FDA’s description. The full ISO standard was not independently assessed for this article. Consult the applicable standard for the exact wording and conditions.

  • The included document is ISO 13485:2016(E), third edition, dated 1 March 2016.
  • A guidance summary does not replace the evaluation of a specific normative passage.
  • Requirements, scope of application, and implementation must remain distinguishable.

1. Start with activity and software purpose

This article addresses production and quality management software within the applicable US medical device context. QMSR is effective as of February 2, 2026. Whether Part 820 applies to your organization depends on the products and activities involved. An ISO certificate alone does not answer this question.

The CSA Guidance is not a general instruction for validating software functions of a medical device. First, describe the intended operational use: Does the application support complaint management, in-process quality control, or document management? What decisions depend on its outcomes? A product name and designation of "standard software" is insufficient for this purpose.

The general QMSR classification is addressed in the linked foundational contribution. Here, the pathway from normative reference to substantiated software requirement is the focus.

Sources: [1] [2] [3]

Further reading:

2. Identify the edition actually incorporated by reference

21 CFR § 820.7 references ISO 13485:2016(E), Third Edition, issued on March 1, 2016. § 820.10 integrates applicable ISO requirements with the other requirements of Part 820. This does not result in the automatic adoption of any subsequent version of the ISO standard nor does it replace all FDA requirements with a certificate.

Record in the source register the title, edition, access path, and relevant clause. When translating or adopting regional versions, verify alignment with the referenced text. Identical file names do not indicate identical legal references. Ensure authorized personnel who are evaluating specific requirements have legitimate access.

This article does not claim an independent review of the complete ISO standard text. It explains the actually available eCFR and FDA references, as well as a logical approach to addressing open detail questions.

Sources: [1]

3. Separate documented statement from open detailed inquiry

A robust requirement statement identifies its source and the specific assertion made therein. Additionally, it must be evident which question remains open. Thus, a translated presentation statement does not inadvertently become a binding inspection directive.

The FDA outlines in its CSA Guidance at sections 4.1.6, 7.5.6, and 7.6 the validation of software for intended use in manufacturing or quality management system (QMS) operations. Approach and activities for validation and revalidation must align with the usage risk, including its impact on product compliance. The following work guide is an independent implementation aid and does not constitute a complete compliance matrix. The exact ISO wording was not independently interpreted for this article.

Labour assistance: a comprehensible source
SourceSubstantiable statementNext step
21 CFR § 820.7 Certain ISO edition is included Secure output and access to the relevant text
21 CFR § 820.10 Applicable ISO requirements and supplementary Part 820 requirements form the framework Assign own responsibilities and additional US requirements
FDA CSA 2026, pages 2–4 References to ISO 13485 clauses 4.1.6, 7.5.6 and 7.6 Check the affected norm passage for intended use.
Own process Determine the actual consequences of failure and the controls Define measurable requirements and provide justified evidence

Sources: [1] [2]

4. Example: a requirement with a clearly defined expected outcome

A medical device manufacturer brings the checks for a production order together electronically. In this example, the order may proceed to the next decision only when A, B and C are complete in their valid versions. This three-part rule is an assumption of the example and is not a universal ISO requirement.

Requirement R-17 links process purpose, responsible role, and source pathway. The specific norm assignment remains open until the applicable section has been reviewed. The team may refine its procedure, but it must not treat an open norm question as conclusive validation evidence.

The matrix verifies identities and versions. Three data records alone do not establish the completeness of three distinct required tests.

Own required matrix for R-17
Valid evidenceFindingExpected
A, B, C 3 different required steps Prerequisite fulfilled
A, B 2 of 3 Not provided; C missing
A, B, B 3 data records, only 2 required identities Dublette does not replace C.
A, B; C in invalid revision C not in the required state Clarify revision; no automatic equivalence

Sources: [2] [1]

5. Define technically verifiable acceptance criteria

"System complies with ISO 13485" is not a valid acceptance criterion for R-17. Describe permitted states, missing evidence, and the responsible decision authority. The observed behavior can then be assessed against a predefined expectation.

Separate functional requirements from design decisions. Status field, list, or technical locking mechanism are possible design choices. The first evidence question is whether an incomplete order could be erroneously treated as complete. A positive screen display alone does not answer this question.

The FDA approach is purpose- and risk-driven. It does not prescribe fixed test volumes or a single document format. Explain which uncertainty a test, an evaluation of existing evidence, or any other assurance activity actually reduces.

Sources: [2]

Further reading:

6. Assign supplier documentation to its actual subject matter

A certificate or validation package may contain useful information. However, verify whether the statement pertains to an organization, a development process, a software version, or your specific workflow. A general supplier certificate does not automatically address R-17.

Conversely, supplier documentation may indeed include customer-specific evidence. Assess the actual scope, transferability, and remaining gaps. Existing appropriate documentation does not need to be blindly duplicated solely based on its origin.

A missing normative pathway, an unknown software version, and a missing test specification represent distinct gaps. Assign a responsible party and a specific clarification step to each, rather than grouping them under "incomplete documentation."

Sources: [2] [1]

7. Distinguish source changes and software changes

A software modification is evaluated for its impact on R-17 and the evidence supporting it. A change in source requires a comparison of output, scope of use, and content. A new publication date alone does not constitute a new obligation.

Avoid old checklists that output former Part-820 sections unchecked as current QMSR text. § 820.40 is now listed in the eCFR as "Reserved". A historically correct reference can be misrepresented in today's evidence.

Obtain traceable justification for prior decisions and complement the current assessment. An updated source register should not obscure which text formed the basis of a previously completed review.

Sources: [1] [2]

8. What should be clarified prior to requirement approval

QA integrates the regulatory reference, the department describes the usage and IT clarifies technical limitations. Effort increases significantly when usage purposes are unclear, different versions of standards are in effect, and supplier claims are unsubstantiated. A shared source document can facilitate work; a specific format is not required.

  • Record why Part 820 applies to the product and activity.
  • Included ISO release and access to relevant sections clarified.
  • FDA Statement, normative text and own interpretation indicated.
  • Determine technical requirements, including negative cases.
  • Supplier records refer to the version and usage.
  • Evaluate open-source questions prior to completion.

Sources: [1] [2]

Project experience and collaboration

Distinguish a reference to a standard from evidence that a function works

With Quality, we trace a software requirement from its applicable source to the intended test. We distinguish the FDA's explanation, the authoritative standard your company must provide and your own implementation. An ambiguous reference may need clarification. Missing evidence for an actual function needs a suitable test. Certification of an organisation does not replace testing of a particular software function.

Frequently asked questions about QMSR references to standards

Does the latest ISO-13485 output automatically apply?

The current § 820.7 references ISO 13485:2016(E), Third Edition, issued on March 1, 2016. This inclusion is significant for QMSR reference. A subsequent norm publication would not automatically constitute the same legal reference solely based on its release.

Sources: [1]

Does the FDA-CSA Guidance supersede the normative text?

It includes the FDA statements and references cited herein. For a precise evaluation of conditions or exceptions, you require the relevant normative text passage. Indicate when a statement refers to an FDA reference and is not substantiated by direct review of the normative document.

Sources: [2] [1]

Which ISO clauses does the FDA reference in the software context?

The FDA-Guidance of February 3, 2026 specifies ISO-13485 subsections 4.1.6, 7.5.6 and 7.6. According to their description, they require software to be validated as part of the production or quality management system for the intended use. Approach and activities of validation and revalidation must correspond to the risk of use, including its effect on product conformity. This summary is based on the FDA-Guidance; the exact standard wording and its conditions are set out in ISO 13485:2016.

Sources: [2]

Does this CSA Guidance for Software apply to medical devices?

This applies to software used in production and quality management. It is not a general guidance on the validation of software functions for medical devices. Separate these intended uses, even if your organization develops or operates both types.

Sources: [2]

Is an ISO-13485 certificate a proof of functionality for a specific software requirement?

An organization-related ISO-13485 certificate does not prove any individual software function. Check its actual scope and the evidenced statement. The specific requirement still needs a suitable functional proof; it cannot be derived automatically from a certificate for the quality management system.

Sources: [1] [2]

Can we define requirements prior to obtaining the standard?

You may describe intended use, consequences of failure, and technical requirements. The unverified normative assignment remains open. Do not issue this draft version as conclusive evidence of compliance with the respective normative requirement.

Sources: [1] [2]

Must acceptance criteria always contain numbers?

No. The rule that all three required verification steps must be available in a valid state is clearly demonstrable. Numbers can help clarify business decision-making, but they neither replace identity verification nor provide a justified evaluation of errors.

Sources: [2]

What marks the beginning of a meaningful initiative for a small company?

Take an actually used software process and document its purpose, decisions, and source pathway. Clarify the relevant normative references and outstanding evidence. From this, a reusable approach is established before adopting extensive, generic checklists.

Sources: [1] [2]

Sources and review date

Source date: 7 October 2026. US medical device context based on actual applicability. ISO detailed references are based on FDA/eCFR; the full text of ISO was not independently evaluated for this article. Tables are for internal reference purposes only.

  1. eCFR: 21 CFR Part 820 – Quality Management System RegulationCurrent eCFR status as of 07.10.2026 (data as of 05.10.2026); §§ 820.1, 820.7, 820.10, and 820.35. ISO 13485:2016(E), third edition dated 01.03.2016, incorporated by reference.
  2. FDA: Computer Software Assurance for Production and Quality Management System SoftwareFinal Guidance dated 03.02.2026; printed pages 2–4 and 6–8, Sections III and V.A(1): Medical device production/QMS software and references to ISO 13485. Recommendations, no verified ISO full text available.
  3. FDA: Quality Management System Regulation – QMSROfficial status page, accessed 07.10.2026; QMSR effective since 02.02.2026, incorporating ISO 13485:2016.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Source reference and software requirements are linked

We support you in defining your process, assigning available sources, and planning appropriate documentation. Open standard questions remain visible and are addressed strategically.

  • 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.

Send a project enquiry Customer testimonials →