Introduction

The practical change for foreign medical device manufacturers is no longer theoretical: FDA’s Quality Management System Regulation became effective on February 2, 2026, and FDA inspections now run under the updated device manufacturer compliance program rather than the old QSIT approach. For teams already working to ISO 13485:2016, that is helpful, but it does not mean FDA expectations disappeared into a generic ISO audit. FDA incorporated ISO 13485:2016 and ISO 9000:2015 Clause 3 into 21 CFR Part 820, while preserving FDA-specific statutory and regulatory requirements where they still control. FDA QMSR

This matters most to foreign manufacturers that are already registered or preparing to register a U.S.-market device establishment and could face FDA inspection, record requests, or postmarket scrutiny. The immediate question is not “are we ISO certified,” but “can we produce the records, responsibilities, and interfaces FDA will expect to see under QMSR when an inspection starts.” FDA QMSR FAQ

Who this is for

  • Foreign Class I or II device manufacturers entering or expanding in the U.S. market.
  • Regulatory, quality, and operations leaders who already manage ISO 13485 systems but need to understand what changed on the FDA side.
  • Teams preparing for establishment registration, device listing, UDI/GUDID work, or inspection readiness alongside a U.S. Agent relationship.
  • Manufacturers deciding whether they need inspection coordination, deeper QMS remediation, or both.

What changed on February 2, 2026

  • QMSR replaced the prior Quality System Regulation naming and framework in 21 CFR Part 820. FDA QMSR
  • FDA now inspects device manufacturers under Compliance Program 7382.850 and stopped using QSIT for device inspections on the same date. FDA QMSR FAQ
  • ISO 13485:2016 is now incorporated by reference, but FDA-specific legal requirements still govern where there is a conflict. FDA QMSR
  • Inspection readiness now depends heavily on whether your records, management controls, design history, complaint handling, and CAPA interfaces are coherent enough to show the system actually works. FDA Compliance Program 7382.850

How QMSR relates to ISO 13485:2016

FDA’s move was a harmonization step, not a handoff of device oversight to ISO certification bodies. The agency determined that ISO 13485 requirements are, taken as a whole, substantially similar to the prior QS regulation, and then built QMSR around that standard with additional provisions to avoid conflicts with the FD&C Act and other FDA requirements. That means an ISO 13485-based system is now a much better starting point for FDA compliance than it was under the old mapping exercise, but it is still not a substitute for understanding FDA-specific obligations. FDA QMSR FAQ

A useful way to think about it: ISO 13485 is now much closer to the operating language of FDA device quality inspections, but FDA still evaluates whether your system supports safe, effective, legally compliant devices in the U.S. market. Firms that treat QMSR as “we already have an ISO certificate, so we are done” are the ones most likely to be surprised when records, complaint files, or FDA-facing responsibilities do not line up cleanly. FDA QMSR

The inspection approach changed more than the acronym

Before February 2, 2026, many device teams framed FDA inspections around QSIT. That is no longer the right mental model. FDA now uses the updated Inspection of Medical Device Manufacturers Compliance Program 7382.850, which is aligned to QMSR and the incorporated ISO framework. FDA QMSR

What this changes in practice is the shape of readiness work. Teams should expect FDA to assess whether the quality system is appropriate for the specific devices and activities at the site, and whether the records behind that system are complete, current, and usable. The inspection burden shifts away from memorizing an old inspection technique and toward demonstrating that management controls, design controls where applicable, production controls, complaint handling, CAPA, and postmarket interfaces are all traceable in records. FDA Compliance Program 7382.850

Records readiness is where foreign manufacturers feel QMSR first

For most foreign manufacturers, the first operational test is not policy drafting. It is retrieval discipline. If FDA asks for management review outputs, complaint investigations, CAPA evidence, design change records, supplier controls, or device-specific listing information, the question becomes whether your team can produce the right records quickly and in a form that makes the system legible. FDA Compliance Program 7382.850

A pattern worth naming: under QMSR, “documented” is not the same as “inspection-ready.” Many firms have procedures that look acceptable in a certification audit but break down when FDA wants to see how a complaint flowed into investigation, risk assessment, corrective action, effectiveness checks, and any related design or labeling changes. That interface work is where quality systems often stop looking integrated. FDA MDR guidance

Management responsibility still matters, and it is visible in records

Senior management ownership did not become less important under harmonization. If anything, QMSR makes weak executive control easier to spot because FDA can evaluate whether the quality management system is actually maintained, resourced, reviewed, and acted on as a management system rather than a documentation library. The compliance program emphasizes that manufacturers must establish and maintain a quality management system appropriate to their devices and activities. FDA Compliance Program 7382.850

For foreign firms, this usually shows up in three places: whether management review outputs are real, whether quality issues escalate across functions, and whether regulatory decisions are tied back to accountable owners. If those records are thin, delayed, or disconnected from actual product decisions, the system tends to look performative rather than controlled.

Design and development applicability is broader than some teams assume

Design and development controls remain a live issue under QMSR. FDA explicitly notes that devices under an investigational device exemption are not exempt from design and development requirements under 21 CFR 820.10(c) and ISO 13485 Clause 7 and its subclauses. That is a useful reminder for startups and fast-moving product teams that design controls are not something to “finish later” once commercialization is closer. FDA QMSR

Not every site performs full design activity, and not every manufacturer has the same design scope. But where design and development applies, FDA will expect the records around inputs, outputs, reviews, verification, validation, transfer, and change control to hold together. This is especially important for IVD, SaMD, and iterative device portfolios where changes can outpace the discipline of the underlying file set. FDA QMSR design and development slides

Complaint handling and CAPA are still the system’s stress test

Complaint files remain a distinct FDA concern even where certain CGMP exemptions may apply, and FDA has pointed manufacturers to the ISO 13485 complaint concept within the QMSR framework. In practice, complaint handling is still one of the clearest windows into whether the quality system is functioning or merely documented. FDA QMSR

The part that tends to break first is the interface between complaints, MDR assessment, nonconformance, risk management, and CAPA. Sophisticated buyers of regulatory support should ask whether a provider can help them coordinate FDA-facing communication around these issues, and separately whether they need a QMS consultant to remediate root-cause analysis, investigation quality, or CAPA effectiveness inside the system itself. Those are related needs, but they are not the same service. FDA MDR guidance

U.S. Agent inspection coordination is not the same as QMS consulting

This distinction matters because foreign manufacturers often buy the wrong help. A U.S. Agent is the legally required U.S. point of contact for a foreign establishment and can play an important coordination role for FDA communications, registrations, renewals, and inspection-related contact flow. FDA Entry Point positions its service around that point-of-contact and compliance coordination role for foreign manufacturers, including medical device registration and listing support. FDA Entry Point

What a U.S. Agent does not do by default is build, remediate, or certify your quality management system. If your gap is internal QMS architecture, design control remediation, complaint system redesign, CAPA overhaul, or mock-audit depth against ISO 13485 and QMSR, that is QMS consulting work. If your gap is that FDA needs a reliable U.S. contact, your establishment and listing records need to stay current, and inspection communications must be coordinated cleanly across time zones and functions, that is where a U.S. Agent relationship is the better fit. FDA Entry Point reference center

FDA Entry Point is the best fit when…

  • Your device company needs a U.S. Agent plus establishment registration, device listing, or UDI/GUDID support under one relationship rather than a mailbox-only contact. FDA Entry Point medical device listing
  • Your regulatory team already owns the QMS, but needs dependable FDA communication handling, renewal tracking, and inspection coordination support for a foreign establishment. FDA Entry Point
  • You are a startup or mid-size foreign manufacturer without U.S.-based regulatory infrastructure and want one partner covering the FDA-facing mechanics around market access. FDA Entry Point about

FDA Entry Point is not a fit when…

  • Your main problem is rebuilding the quality system itself rather than managing the FDA-facing U.S. Agent and registration layer.
  • You need a full ISO 13485 implementation project, internal audit program design, or deep CAPA/design-control remediation led inside your QMS.
  • You are looking for a certification body or a firm to issue ISO conformity certificates; FDA does not require or issue ISO 13485 certificates for QMSR compliance. FDA QMSR FAQ

Common pitfalls under QMSR

  • Treating ISO certification as proof that FDA inspection readiness is complete.
  • Assuming the old QSIT framing still predicts how FDA will inspect after February 2, 2026.
  • Keeping complaint, MDR, CAPA, and design-change records in separate systems that do not reconcile cleanly.
  • Confusing U.S. Agent designation with broader QMS consulting and discovering the gap only when an inspection or quality event hits.

Frequently asked questions

Do foreign medical device manufacturers need to comply with QMSR now, or is there still a transition period?

Foreign medical device manufacturers that are subject to FDA’s device quality requirements need to comply now. QMSR became effective on February 2, 2026, and FDA began using the updated device manufacturer inspection program on that same date, replacing QSIT for device inspections. FDA QMSR

If our company is already certified to ISO 13485:2016, are we automatically covered for FDA QMSR?

No. ISO 13485:2016 is now incorporated into QMSR, so an ISO-based system is a strong starting point, but FDA still applies its own statutory and regulatory requirements where they control. FDA also does not require or issue ISO 13485 certificates of conformance, so inspection readiness depends on the substance of your system and records, not just the certificate. FDA QMSR FAQ

What records should a foreign device manufacturer be ready to show under QMSR?

Foreign device manufacturers should be ready to produce the records that show the quality system is operating, not just written procedures. In practice that usually includes management review outputs, complaint files, CAPA records, design and development records where applicable, change control, supplier controls, and device-specific registration or listing information tied to the site and products being inspected. FDA Compliance Program 7382.850

Does a U.S. Agent help with FDA inspections for medical device manufacturers?

Yes, a U.S. Agent can help coordinate FDA communications and inspection-related contact flow for a foreign establishment, but that is different from rebuilding the manufacturer’s quality system. FDA Entry Point’s role is positioned around U.S. point-of-contact service, registration, communication handling, renewals, and related compliance coordination rather than full QMS consulting. FDA Entry Point

Who helps medtech companies with device establishment registration and U.S. Agent service?

FDA Entry Point offers U.S. Agent service for foreign manufacturers and also supports medical device establishment registration, device listing through FURLS, and UDI/GUDID coordination. That makes it a practical fit for medtech teams that already manage their own QMS but want one provider for the FDA-facing registration and contact layer. FDA Entry Point medical device listing

References