FDA Read Their Release Notes. Then It Cited Three Software Changes in a Warning Letter.

When FDA inspected O.N. Diagnostics in March 2026, the agency's evidence that a new machine learning model had shipped did not come from a regulatory submission. It came from the company's own engineering records: a set of release notes dated June 11, 2024, and the software version control log. Those documents, ordinary artifacts of any software team, became the basis for a warning letter that FDA issued on September 1 and posted on October 6. The letter says the company's software was adulterated and misbranded because of changes it made without a new marketing submission.
The case has already drawn plenty of commentary, and the FDA Law Blog waited for the dust to settle before weighing in on October 26. Its conclusion is that software companies will be living with this letter's implications for a long time. For quality and regulatory teams, the useful question is not whether FDA's reasoning is the final word. It is what your own change records would look like if an investigator read them cold.
What happened
The inspection, conducted March 12-17, 2026, covered the company's VirtuOst and VirtuOst Vertebral Fracture Assessment software. The VFA product was originally cleared under K171435 to visualize vertebral deformities on spine CT sections, classify fracture type and grade, and support physician management of osteoporosis.
FDA identified three changes it considered significant enough to require a new submission:
A new machine learning algorithm. FDA's reasoning was broad: a model trained on different data, built with a different architecture, or optimized for a different objective may perform differently across patient populations, imaging equipment, and clinical settings, so the change alters how the device performs and fails and must be adequately validated.
A move from a desktop application to a web-based architecture. FDA pointed to network-exposed attack surfaces, authentication weaknesses, and other cybersecurity risks inherent to internet-accessible platforms. According to the law firm's summary, the company itself acknowledged during the inspection that the move expanded its cyberattack surface.
A migration of the underlying technology platform (the specifics are redacted in the public letter). FDA said this required comprehensive re-verification and re-validation of the entire codebase, including changes to third-party libraries and dependencies, and noted that it had not reviewed the Software Bill of Materials or documentation of the affected third-party components.
Three things quality teams should notice
Engineering artifacts are inspection evidence. The release notes and version log were not written for FDA, but FDA used them to establish what changed and when. Any assumption that internal technical records stay internal does not survive an inspection. The practical consequence is that release notes, tickets, commit histories, and architecture diagrams should be consistent with the regulatory assessment made at the time of the change, because an investigator can compare them.
The shelf life of a change decision is long. The release in question dates to June 2024. The inspection came in March 2026, and the letter in September 2026, more than two years after the change shipped. A decision made quickly in a sprint, perhaps by engineering alone, can be examined long after the people and context that produced it have moved on.
Architecture and dependencies count as changes. The letter treats hosting model and platform migration as regulatory events, not just implementation choices. For manufacturers who view re-platforming or swapping libraries as internal engineering decisions, that is a significant shift in what needs a documented regulatory assessment.
Where commentators disagree with FDA
It is worth being precise here, because the letter is an enforcement document and not a rule. The FDA Law Blog's analysis argues that FDA appears to treat the need to validate a change as equivalent to the need for a new 510(k). FDA's own guidance on deciding when to submit a 510(k) for a software change recognizes that validation is required even when no new submission is needed, and the regulation, 21 CFR 807.81(a)(3)(i), turns on whether a change could significantly affect safety or effectiveness. The authors say the letter does not obviously track either, and read it as FDA signaling that certain categories of change, including new models and architecture migrations, will draw a new-submission expectation regardless of the traditional threshold.
That is one law firm's view, and the company has the opportunity to respond to the agency. Even so, a manufacturer should not wait for the argument to resolve in its favor. The documented regulatory risk is that FDA may read your version history the same way.
How the pre-authorization path fits
This letter lands in the same month that CDRH launched a dedicated web page on predetermined change control plans, which now lists 240 authorized devices. A PCCP is the sanctioned way to get future model updates and other planned modifications authorized in advance, so that implementing them within the plan does not require a new submission each time. The public sources do not say whether O.N. Diagnostics had one, and it would be unwise to infer anything about that. The broader point is the contrast: change that happens inside an authorized plan is expected; change that happens outside one is assessed from scratch, and FDA may reach its own conclusion.
A practical checklist
Run a retrospective review. For each release since your last clearance, confirm there is a documented assessment of whether a new submission was needed, using the structure in FDA's software-change guidance. Gaps are far easier to find yourself than to explain to an investigator.
Widen what counts as a change. Include retraining or new training data, objective-function changes, hosting model, platform migrations, and third-party library swaps in your change-control triage.
Put regulatory affairs and quality in the decision. Technical change boards that do not include someone accountable for the 510(k) analysis create exactly the kind of record this letter exposes.
Reconcile the paper trail. Compare release notes and version logs with the formal change records. Where they diverge, fix the process, not just the documents.
Keep the SBOM current. FDA noted that it had not reviewed the SBOM or third-party component documentation. Treat component changes as something to document at the time they happen.
Evaluate a PCCP for your next submission if you expect regular model or software updates.
The lasting lesson for quality leaders is that a change-control process is only as strong as its weakest assumption about who might read the record later. This letter suggests the reader may be an investigator, and that they will start with your own release notes.
Sources: FDA Law Blog, If You Change It, FDA Will Come: What the O.N. Diagnostics Warning Letter Means for SaMD Modifications, October 26, 2026; U.S. Food and Drug Administration warning letter to O.N. Diagnostics, LLC (issued September 1, 2026; posted October 6, 2026); Medtech Insight, FDA's New PCCP Pages, October 22, 2026; FDA CDRH News and Updates, October 20, 2026.



Comments