eduKateSG · Why Science?
Read the 2026 QMSR as a connected evidence system
Use FDA’s effective QMSR through incorporated standards, FDA-specific provisions, risk, design, suppliers, production, feedback, CAPA, records and inspections.
A medical device can pass a single test and still fail if purchasing, production, complaints or changes are poorly controlled. A quality management system joins those activities so risks and decisions stay visible throughout the product lifecycle.
FDA’s Quality Management System Regulation became effective on 2 February 2026. It amends device CGMP requirements in 21 CFR part 820 by incorporating ISO 13485:2016 while preserving FDA-specific law, definitions and supplemental requirements.
Did you know? Incorporation by reference does not replace 21 CFR part 820 with a private checklist. Manufacturers must read the incorporated standard together with FDA provisions and the rest of applicable device law.
This guide supports quality-system literacy. It does not audit a manufacturer or interpret a legal obligation for a specific device.
Chapter index
Chapters 1–9: rule, definitions and management system
- 1. The QMSR became effective on 2 February 2026
- 2. ISO 13485:2016 is incorporated by reference
- 3. FDA definitions control where specified
- 4. Part 820 remains an FDA regulation
- 5. Risk management runs through the system
- 6. Management responsibility needs evidence
- 7. Document control protects the current method
- 8. Records show what actually happened
- 9. Design and development require planned controls
Chapters 10–17: lifecycle controls, records and inspection evidence
- 10. Purchasing controls extend to suppliers
- 11. Production controls preserve validated conditions
- 12. Identification and traceability answer different questions
- 13. Feedback and complaints enter the quality system
- 14. Nonconforming outputs need controlled disposition
- 15. Corrective action addresses causes
- 16. FDA inspections use a new process
- 17. A complete QMSR receipt links the lifecycle
A quality system becomes useful when decisions, responsibilities, risks and records remain connected. FDA’s amended 21 CFR part 820 is titled the Quality Management System Regulation and became effective two years after the final rule was published. This turns compliance into a traceable system of evidence.
Try this
Evidence question: Which official rule, program record, audit file or submission document supports the point about the qmsr became effective on 2 february 2026? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the organization, object, version, date, result and one limit for the qmsr became effective on 2 february 2026. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for the qmsr became effective on 2 february 2026, its identifier or version context, and one limit that must remain visible.
FDA’s QMSR became effective on 2 February 2026 and changed the regulatory map for device manufacturing. The rule incorporates the medical-device quality-management-system standard and Clause 3 of ISO 9000:2015 while retaining FDA law. It also keeps product risk connected to process control.
Try this
Evidence question: Which official rule, program record, audit file or submission document supports the point about iso 13485:2016 is incorporated by reference? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the organization, object, version, date, result and one limit for iso 13485:2016 is incorporated by reference. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for iso 13485:2016 is incorporated by reference, its identifier or version context, and one limit that must remain visible.
Incorporating ISO 13485:2016 does not erase FDA-specific requirements or definitions. Definitions in the Federal Food, Drug, and Cosmetic Act and FDA regulations can supersede terms in the incorporated standards. A document matters because people use it to make and verify decisions.
Try this
Evidence question: Which official rule, program record, audit file or submission document supports the point about fda definitions control where specified? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the organization, object, version, date, result and one limit for fda definitions control where specified. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for fda definitions control where specified, its identifier or version context, and one limit that must remain visible.
The strongest record shows how a requirement moves through design, production, feedback and correction. Manufacturers must read the incorporated clauses together with supplemental provisions and other applicable FDA requirements. The lifecycle becomes clearer when inputs, outputs and changes are dated and approved.
Try this
Evidence question: Which official rule, program record, audit file or submission document supports the point about part 820 remains an fda regulation? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the organization, object, version, date, result and one limit for part 820 remains an fda regulation. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for part 820 remains an fda regulation, its identifier or version context, and one limit that must remain visible.
A quality system becomes useful when decisions, responsibilities, risks and records remain connected. Quality planning, design and development, supplier control, production, feedback and corrective action should use risk proportionately. This turns compliance into a traceable system of evidence.
Try this
Evidence question: Which official rule, program record, audit file or submission document supports the point about risk management runs through the system? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the organization, object, version, date, result and one limit for risk management runs through the system. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for risk management runs through the system, its identifier or version context, and one limit that must remain visible.
FDA’s QMSR became effective on 2 February 2026 and changed the regulatory map for device manufacturing. Policy, objectives, responsibility, authority, resources and management review create an accountable quality structure. It also keeps product risk connected to process control.
Try this
Evidence question: Which official rule, program record, audit file or submission document supports the point about management responsibility needs evidence? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the organization, object, version, date, result and one limit for management responsibility needs evidence. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for management responsibility needs evidence, its identifier or version context, and one limit that must remain visible.
Incorporating ISO 13485:2016 does not erase FDA-specific requirements or definitions. Approved procedures, distribution, revisions, obsolete copies and change history should show which instruction governed work. A document matters because people use it to make and verify decisions.
Try this
Evidence question: Which official rule, program record, audit file or submission document supports the point about document control protects the current method? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the organization, object, version, date, result and one limit for document control protects the current method. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for document control protects the current method, its identifier or version context, and one limit that must remain visible.
The strongest record shows how a requirement moves through design, production, feedback and correction. Device and process records, approvals, dates and results support traceability beyond written procedures. The lifecycle becomes clearer when inputs, outputs and changes are dated and approved.
Try this
Evidence question: Which official rule, program record, audit file or submission document supports the point about records show what actually happened? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the organization, object, version, date, result and one limit for records show what actually happened. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for records show what actually happened, its identifier or version context, and one limit that must remain visible.
CHAPTER 9 OF 17 · Follow product evidence
9. Design and development require planned controls
A quality system becomes useful when decisions, responsibilities, risks and records remain connected. Inputs, outputs, reviews, verification, validation, transfer and changes should remain linked to intended use and risk. This turns compliance into a traceable system of evidence.
Try this
Evidence question: Which official rule, program record, audit file or submission document supports the point about design and development require planned controls? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the organization, object, version, date, result and one limit for design and development require planned controls. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for design and development require planned controls, its identifier or version context, and one limit that must remain visible.
CHAPTER 10 OF 17 · Follow product evidence
10. Purchasing controls extend to suppliers
FDA’s QMSR became effective on 2 February 2026 and changed the regulatory map for device manufacturing. Selection, evaluation, monitoring and communicated requirements should match the effect of a supplied product or service on device quality. It also keeps product risk connected to process control.
Try this
Evidence question: Which official rule, program record, audit file or submission document supports the point about purchasing controls extend to suppliers? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the organization, object, version, date, result and one limit for purchasing controls extend to suppliers. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for purchasing controls extend to suppliers, its identifier or version context, and one limit that must remain visible.
CHAPTER 11 OF 17 · Follow product evidence
11. Production controls preserve validated conditions
Incorporating ISO 13485:2016 does not erase FDA-specific requirements or definitions. Instructions, equipment, environment, monitoring, acceptance and process validation support consistent manufacture. A document matters because people use it to make and verify decisions.
Try this
Evidence question: Which official rule, program record, audit file or submission document supports the point about production controls preserve validated conditions? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the organization, object, version, date, result and one limit for production controls preserve validated conditions. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for production controls preserve validated conditions, its identifier or version context, and one limit that must remain visible.
CHAPTER 12 OF 17 · Follow product evidence
12. Identification and traceability answer different questions
The strongest record shows how a requirement moves through design, production, feedback and correction. Identification distinguishes product and status, while traceability follows specified history, application or location where required. The lifecycle becomes clearer when inputs, outputs and changes are dated and approved.
Try this
Evidence question: Which official rule, program record, audit file or submission document supports the point about identification and traceability answer different questions? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the organization, object, version, date, result and one limit for identification and traceability answer different questions. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for identification and traceability answer different questions, its identifier or version context, and one limit that must remain visible.
CHAPTER 13 OF 17 · Improve and inspect
13. Feedback and complaints enter the quality system
A quality system becomes useful when decisions, responsibilities, risks and records remain connected. Postmarket information should be evaluated, investigated when appropriate and connected to reporting, risk and corrective action. This turns compliance into a traceable system of evidence.
Try this
Evidence question: Which official rule, program record, audit file or submission document supports the point about feedback and complaints enter the quality system? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the organization, object, version, date, result and one limit for feedback and complaints enter the quality system. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for feedback and complaints enter the quality system, its identifier or version context, and one limit that must remain visible.
CHAPTER 14 OF 17 · Improve and inspect
14. Nonconforming outputs need controlled disposition
FDA’s QMSR became effective on 2 February 2026 and changed the regulatory map for device manufacturing. Identification, segregation, evaluation, investigation and disposition prevent unintended use and feed improvement. It also keeps product risk connected to process control.
Try this
Evidence question: Which official rule, program record, audit file or submission document supports the point about nonconforming outputs need controlled disposition? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the organization, object, version, date, result and one limit for nonconforming outputs need controlled disposition. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for nonconforming outputs need controlled disposition, its identifier or version context, and one limit that must remain visible.
Incorporating ISO 13485:2016 does not erase FDA-specific requirements or definitions. A strong CAPA record defines the problem, investigates root causes, implements action and checks effectiveness. A document matters because people use it to make and verify decisions.
Try this
Evidence question: Which official rule, program record, audit file or submission document supports the point about corrective action addresses causes? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the organization, object, version, date, result and one limit for corrective action addresses causes. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for corrective action addresses causes, its identifier or version context, and one limit that must remain visible.
The strongest record shows how a requirement moves through design, production, feedback and correction. From 2 February 2026 FDA stopped using QSIT and began using the updated medical-device-manufacturer inspection compliance program. The lifecycle becomes clearer when inputs, outputs and changes are dated and approved.
Try this
Evidence question: Which official rule, program record, audit file or submission document supports the point about fda inspections use a new process? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the organization, object, version, date, result and one limit for fda inspections use a new process. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for fda inspections use a new process, its identifier or version context, and one limit that must remain visible.
CHAPTER 17 OF 17 · Improve and inspect
17. A complete QMSR receipt links the lifecycle
A quality system becomes useful when decisions, responsibilities, risks and records remain connected. Record product and site scope, applicable clauses, risks, procedures, responsibilities, suppliers, validation, acceptance, feedback, complaints, CAPA, changes, training, internal audits and management review. This turns compliance into a traceable system of evidence.
Try this
Evidence question: Which official rule, program record, audit file or submission document supports the point about a complete qmsr receipt links the lifecycle? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the organization, object, version, date, result and one limit for a complete qmsr receipt links the lifecycle. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for a complete qmsr receipt links the lifecycle, its identifier or version context, and one limit that must remain visible.
Contents · Previous chapter · Continue at the Science Learning Hub
Quality improves when every control leaves a retraceable record
The QMSR is best read as a network: risk shapes controls, controls shape records, feedback tests assumptions and corrective action improves the system. A procedure without evidence of use is incomplete.
Save the site and product scope, applicable regulatory requirements, quality manual and policies, responsibilities, objectives, risk files, design and transfer records, suppliers and purchasing data, process validation, production and acceptance evidence, identification and traceability, feedback, complaints, reporting decisions, nonconformities, CAPA, training, document changes, internal audits and management reviews.
| Reading object | What it can support | Question to keep visible |
|---|---|---|
| Requirement map | Connects clauses and FDA provisions | Which rule controls this decision? |
| Quality record | Shows performed work and result | Who approved it and when? |
| Risk control | Links hazard to process or product action | How is effectiveness monitored? |
| CAPA record | Shows cause, action and verification | Did recurrence fall? |
Sources and next reading
Substantive resource claims in this article were checked against the primary pages below. A structured record is a route into evidence; it does not by itself prove a scientific conclusion. Recheck the live record, evidence labels and release context before using it in assessed work or research.
For a classroom enquiry, save a short research receipt containing the question, search terms, selected object, exact identifier, version, access date and the evidence boundary you observed. Add the file or page that supports each statement. This small routine turns browsing into accountable science learning and gives a teacher, classmate or future analyst a route they can independently follow.
Before sharing the conclusion, ask another reader to retrace the route without verbal hints. If they reach a different version, file or interpretation, improve the receipt and narrow the claim. Reproducibility begins with this practical check. It teaches careful reading, supports fair collaboration and keeps uncertainty visible while evidence moves from an online service into notes, analysis and a final explanation.
A useful final review separates five questions. What object was found? Which organisation or repository maintains it? What exact evidence was inspected? Which statement does that evidence support? What remains uncertain? Answer each question in one sentence, then connect every answer to a visible field, file or source page. This review catches common mistakes: citing a collection when a file supplied the value, treating the newest release as the analysed release, confusing permission with scientific suitability, or turning a discovery count into a conclusion. It also gives students a calm way to improve work. A missing detail becomes a next research step instead of an invitation to guess. When the route is complete, the final explanation can stay simple because the identifiers, dates, versions, limitations and supporting evidence are already organised underneath it.
Primary sources
- FDA QMSR Overview — accessed 25 October 2026.
- FDA QMSR Frequently Asked Questions — accessed 25 October 2026.
- FDA Quality and Compliance — accessed 25 October 2026.
- FDA QMSR Final Rule — accessed 25 October 2026.
- FDA Risk-Based Inspections under QMSR — accessed 25 October 2026.