Five QMSR Warning Letters, One Pattern: FDA Is Citing Risk, Design, and Suppliers as a Chain.

The Quality Management System Regulation has been in effect since February 2, 2026, and enforcement is now visible in numbers. On November 16, Covington & Burling published its quarterly review of device warning letters for July through September 2026. As of that date, FDA had posted nine letters from the quarter. Eight alleged quality system violations. Five of those came from inspections conducted under the QMSR, and three from inspections conducted under the older Quality System Regulation.
The pattern in the five QMSR letters is the useful part. All five cited ISO 13485 Clause 7.4, purchasing. Four cited Clause 7.3, design and development. Four cited Clause 7.1, planning of product realization, which is where ISO 13485 places risk management. The three QSR-era letters looked similar in a different vocabulary: all three cited design controls under 21 CFR 820.30, and one cited purchasing controls under 820.50.
Nine letters is a small sample, and each letter is FDA's position on one company, not a rule. But the overlap is specific enough to take seriously, because the three clauses are not independent. In the two QMSR letters analyzed most closely, FDA cited them as links in a single chain.
Why these three clauses travel together
Under the QSR, risk management was implicit, a requirement read into design controls. ISO 13485:2016, which the QMSR incorporates by reference, makes it explicit. Clause 7.1 requires an organization to document one or more processes for risk management in product realization and to keep records of the activities. Clause 7.3 covers design and development from planning through transfer, including, in 7.3.9, control of design changes and determining their significance for function, performance, usability, safety, and regulatory requirements. Clause 7.4 requires criteria to evaluate, select, monitor, and re-evaluate suppliers, and verification of what is purchased.
The FDA Law Blog has argued that the most significant change from QSR to QMSR is its focus on risk management, and that risk-related observations under Clause 7.1, combined with process and record observations, have become the most common category on Form 483s, at more than 20% of all citations. Usability, which the QSR left implicit, now appears expressly in the standard as well.
The practical consequence is that risk management in an ISO 13485 system is not a document in a design history file. It is a process that should receive input from, and send output to, design changes, suppliers, complaints, corrective actions, and validation. An inspector can pick any of those and trace the line back to the risk file. The warning letters show that is exactly what is happening.
Linemaster Switch: risk without a feedback loop
FDA's letter to Linemaster Switch Corporation, issued May 27 after an inspection from February 4 through March 6, concerns foot-pedal accessories used to control medical devices including Class IV medical lasers. It cites five violations. The risk management finding is the thread running through them.
FDA said the company's risk management procedure did not define how risk activities are performed and documented, who is responsible for conducting and approving them, when documentation must be updated, or how post-market feedback, including complaints, adverse events, and recalls, is incorporated into risk management. It also said the company lacked a process failure modes and effects analysis for a foot-pedal accessory used to control Class IV lasers.
The other findings show what an unconnected risk file looks like in practice. FDA described undocumented rework, a customer corrective-action request with no recorded root cause or corrective action, inadequate environmental control for temperature-related calibration effects, and software validation records missing raw data, acceptance results, a statistical or sample-size rationale, and verification that the software reliably measures and detects nonconformance. Each of those would normally generate a risk input: rework changes process risk, a customer complaint changes occurrence estimates, a calibration drift changes detectability. The letter implies that none of that reached the risk process.
Koven Technologies: one product change, four controls
The Koven letter, issued July 21 after an inspection from February 2 through 6, concerns Doppler devices and shows the chain in the other direction, starting from a design change.
FDA cited Clause 7.3.9 for failure to document and assess the design changes involved in adding a fetal application to a Doppler device. It said the company could not provide documentation of the specific changes, supporting validation, an assessment of whether a new 510(k) was required, or the date distribution began for the fetal use. That is a change-control failure, and it is the same kind of record the O.N. Diagnostics letter, covered in an earlier piece, examined for a software change.
The same change reappears in risk management. FDA said the risk files did not address fetal-specific hazards, including thermal and acoustic exposure, diagnostic accuracy, misinterpretation, delayed care, and false reassurance, even though the devices were labeled or cleared for fetal use. A design change altered the intended use, and the risk file did not follow.
Then the supplier. FDA said the contract manufacturer implemented the labeling or indication change without adequate supporting documentation, the quality agreement did not adequately govern design changes beyond labeling, and the company had no documented site assessment for a supplier whose own procedure was treated as highest- or critical-impact. That is a Clause 7.4.1 finding. Finally, the company did not evaluate returned products reporting performance or reliability failures as complaints, which FDA cited under 21 CFR 820.35(a). Returns and service tickets that meet the definition of a complaint are an input to risk management; if they are not recognized as complaints, they never get there.
Seen together, Koven's letter reads as a single event, a product change, that was not controlled at four points: design, risk, supplier, and post-market intake.
What the QSR-era letters add
A third group is worth knowing about. Letters to IsoTis OrthoBiologics, Longhorn Vaccines and Diagnostics, and Medline Industries, issued after February 2 but based on inspections that predated the QMSR, allege QSR violations. But they also state that corrective actions must be taken under the QMSR. The practical effect is that a company with an open QSR-era observation should plan its remediation to the ISO 13485 clause structure, not the legacy citation, and expect reinspection under QMSR.
A way to test your own chain
The letters do not prescribe a remediation plan, and no single document name or method is required. But they suggest a short evidence test that follows the chain instead of auditing each clause in isolation.
Trace a recent change. Pick a design, labeling, indication, or process change from the last year. Confirm there is a change record, verification and validation, a risk review, a documented decision on whether a new submission was needed, and notice to any supplier who implements it.
Walk the signals back to the risk file. Sample complaints, returns, service tickets, adverse events, rework records, and supplier issues. For each, find where the risk file was reviewed or updated, or a reason it was not.
Read your quality agreements as a change-control document. Check who controls changes to design, labeling, and process, how the supplier must notify you, and whether your critical suppliers have a documented site assessment.
Test the risk procedure for the four things FDA named at Linemaster. Does it say how activities are performed and documented, who approves them, when records are updated, and how post-market data enters the process?
Check execution evidence. Choose one promised control, such as rework, corrective action, environmental monitoring, or software validation, and confirm the raw data, acceptance criteria, approvals, and effectiveness checks exist and agree.
Re-map open QSR-era observations to the QMSR clauses, and confirm the corrective actions would stand up under the new framework.
Keeping it in proportion
A warning letter communicates FDA's position that it found significant violations and gives the company a chance to respond. Covington's alert summarizes the allegations without drawing conclusions, and the same caution applies here: nine letters across a quarter do not establish a rate of enforcement. What they do show, consistently, is where inspectors have been looking. The questions FDA asked were not exotic. They were whether the risk file knows what the complaint file knows, whether a design change reaches the people who implement it, and whether a supplier operates under terms that keep the manufacturer in control.
Quality teams that audit these clauses one at a time can pass each audit and still fail the trace. The teams better prepared for the next inspection are the ones that practice the trace.
Sources: Covington & Burling LLP, Quarterly Medical Device Warning Letters Update: July–September 2026 (November 16, 2026); FDA warning letters to Linemaster Switch Corporation (May 27, 2026; CMS 730215) and Koven Technologies, Inc. (July 21, 2026; CMS 734643); FDA Law Blog, The QMSR is Here: FDA's First QMSR Warning Letters (August 12, 2026); Pure Global, FDA QMSR Warning Letters Focus on Risk and Design Changes (August 13, 2026); FDA warning letters to IsoTis OrthoBiologics, Longhorn Vaccines and Diagnostics, and Medline Industries (February and March 2026); ISO 13485:2016, clauses 7.1, 7.3.9 and 7.4.



Comments