FDA's QMSR changes the device inspection baseline
The rule now incorporates ISO 13485:2016 by reference and replaces QSIT with a new inspection process, shifting the questions device manufacturers should ask of quality systems and evidence.
Editorial figure by RegQuality Review. Source context: U.S. Food and Drug Administration.
Harmonisation does not erase FDA-specific work
QMSR brings the U.S. device quality framework closer to the international medical-device quality standard, but it does not turn an ISO 13485 certificate into proof of complete FDA compliance. FDA states that the statute and implementing regulations control where there is a conflict, and its page retains specific applicability, records, and inspection context.
Device manufacturers should update internal mappings, procedures, training, audit criteria, management-review inputs, and inspection preparation based on their own products and operations. A software provider can support those controlled changes; it cannot perform the manufacturer's regulatory judgment.
A better way to evaluate eQMS fit
The useful buyer question is not whether a product is QMSR compliant. It is whether the system can support the organization's defined processes, preserve objective evidence, connect risk to quality activity, maintain records over required periods, and produce intelligible information during an inspection.
Demonstrations should follow a device-specific scenario across design or production change, supplier impact, risk, complaints, CAPA, and management review. Teams should ask which relationships are native, which are configured, and which depend on procedures or external systems.
What changed in the market
Providers now have an incentive to relabel existing ISO 13485 features as QMSR readiness. Buyers should require dated product evidence and resist language that implies FDA endorsement. FDA does not approve commercial eQMS products as compliant implementations for a manufacturer.
RegQuality Review will map provider capabilities to specific controlled workflows and standards references. Alignment claims will be presented as claims unless supported by documentation, observation, and a clearly bounded use case.
Enterprise buyer test
Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.
A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.
What we will watch next
RegQuality Review will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.