The First Warning Letter Under the QMSR: Lessons from the Linemaster Case

On May 27, 2026, the FDA issued a Warning Letter to Linemaster Switch Corporation, a manufacturer of foot switches for medical devices, including controllers used with Class IV medical lasers. The letter is based on an inspection carried out between February 4 and March 6, 2026, very close to the QMSR coming into effect on February 2, 2026. As far as is known, this is the first Warning Letter that cites QMSR violations directly. It is not just another Warning Letter. It holds several lessons that every manufacturer, including Israeli manufacturers selling to the US market, would do well to take in.

What actually happened

The inspection resulted in five findings, all presented on the basis of clauses in ISO 13485:2016, because the QMSR adopts the standard almost word for word. Let's go through them.

  1. Rework without documentation (clause 8.3.4)

In a particular production job, an assembler did not tighten screws as required in the calibration process. The manager ordered rework: torque tightening and recalibration of all the relevant units.

The problem is that none of this was documented. The company's internal procedure explicitly requires rework to be documented on a dedicated form, with specific manufacturing and inspection instructions, and that did not happen.

The FDA did not stop at noting the procedural violation. It wrote explicitly that improper calibration of these foot switches could cause unintended activation of the laser or insufficient power output. In other words, this is a direct safety risk that the documentation was supposed to catch.

  1. Risk management that was not performed (clause 7.1)

The specific foot switch at the center of the inspection had no Process FMEA, even though the company's internal procedure requires one. But the problem runs deeper, because the procedure itself did not define who is responsible for performing and approving risk management activities, when the documentation needs to be updated, and how market data, such as complaints and adverse events, is fed into the risk management file.

This point comes up often in inspections, and having a procedure is really not enough.

The procedure needs to define clearly who does what and when. Otherwise, even if someone tries to follow it, there is no way to prove that it was done correctly.

3. A corrective action that stays on paper (clause 8.5.2)

A SCAR (Supplier Corrective Action Request) opened in 2023, after six foot switches failed a calibration test at the customer, was simply never investigated. In the official response sent to the customer, the "root cause" field was left empty, and the "corrective action" field said "N/A."

This is exactly the kind of gap internal audits are supposed to catch before the FDA arrives. A corrective action that was opened and never handled is a sign that the system does not work in practice, not a documentation problem.

4. Lack of control over the work environment (clause 6.4.1)

This is where the most interesting detail in the whole letter comes out. As far back as 2013, the company identified that temperature fluctuations cause an unintended shift in a sensor's output, which affects measurement accuracy. The only solution implemented was a firmware change. No procedures or controls were put in place for temperature monitoring to show that the devices maintain accurate calibration under changing conditions.

5. Validation of test software (clause 7.6)

The software used to calibrate and test the product had not been adequately validated. There was no raw data, no pass or fail criteria, and no statistical analysis. In addition, the FDA investigator observed repeated COM port errors at the test stations, which the staff treated as "routine" without investigating them. Between 2023 and 2025, units that had passed the company's internal calibration test were returned because they failed a calibration test at the customer. In other words, the internal quality check did not catch real problems that the customer did catch.

Two lessons worth taking from this case

1. A 483 response must include a timeline

For each of the five findings, the FDA wrote the same sentence: the adequacy of the response could not be determined. Apparently this was because the company described its intention to update procedures, carry out a retrospective review of records and correct the deficiencies, but it did not provide a timeline for implementation and did not attach the actual revised documents.

This is a critical point for anyone submitting a 483 response. In the FDA's eyes, a correction plan without target dates is almost the same as "no plan." If you commit to updating a procedure, performing a retrospective review or revalidating, attach a realistic target date to each step. Even if the date slips later, you have a basis for showing that the process is being managed.

2. Old quality records do not disappear

Some of the evidence the FDA used in the letter dates back to 2013, while the QMSR only came into effect in February 2026.

That means the regulatory basis cited is new, but the evidence that proved the violation is much older.

It is a bit like getting a traffic ticket for driving at a speed that was legal at the time, where the ticket relies on today's updated speed limit.

Either way, in both cases there may have been a real problem, but the legal basis cited does not match the period in which the action took place. This question is legally relevant only if you intend to contest the citation. If you do not intend to contest it, you simply need to understand that old quality records will still serve as the basis for findings, even under a new regulation.

The practical conclusion is not to assume that investigators look only at records from the last year. If you have an old REA, corrective action, rework or validation record that was never properly closed, it is still there, waiting for the FDA investigator...

What does this mean for you?

Israeli manufacturers selling to the US market do not need to wait for an inspection to check themselves against these five topics.

It is worth doing a short internal round and asking:

  • Is every rework actually documented, not just described in a procedure?

  • Does your FMEA cover all product lines, not only the convenient ones?

  • Are there open corrective actions that have been left without a defined root cause?

  • Are there work environment requirements, such as temperature or humidity, that affect product performance but that nobody monitors systematically?

  • Has software used for testing or measurement gone through full validation, with raw data and clear criteria?

If your answer to any of these questions is hesitant, now is the time to deal with it, rather than waiting for the next inspection.