Minneapolis-St. Paul, Minnesota
ISO 13485 consulting for Twin Cities device makers.
Since February 2026 ISO 13485:2016 has been the substance of US federal law. The FDA still will not require your certificate, will not issue you one, and says it exempts you from nothing.
We work in the Kansas City metro. Engagements here run remotely, with on-site visits at the points where being in the building changes the outcome — gap analysis, internal audit, and the certification audits themselves. We do not maintain an office in this market and would rather say so than imply otherwise.
The standard became law. The certificate did not.
On 2 February 2026 the FDA's Quality Management System Regulation took effect, amending 21 CFR Part 820 by incorporating by reference the requirements of ISO 13485:2016. On the same day the FDA stopped using the Quality System Inspection Technique it had used for device inspections for decades.
That is a genuinely large change, and for a metro with this density of device manufacturing it is the most consequential regulatory event in years. But almost every consulting page describing it gets the conclusion backwards.
Here is what the FDA itself says, in its own words: “The FDA will not require certificates of conformance to ISO 13485 and will not issue certificates of conformance to ISO 13485.” And: “A certificate of conformance to ISO 13485 will not exempt a manufacturer from an FDA inspection.”
So both halves of the common pitch are wrong. You are not required to hold the certificate. And holding it buys you no inspection relief whatsoever. What you are required to do is conform to the requirements — which are now, quite literally, the text of the regulation you are inspected against.
Industry in Minneapolis
- Medtronic Operational headquarters at 710 Medtronic Parkway in Fridley. The principal executive office is in Ireland, which is why we write operational rather than global
- Boston Scientific Minnesota is the company's largest workforce at roughly 8,700 people, though the headquarters is in Marlborough, Massachusetts
- The device supply base Roughly 360 FDA-registered establishments across the metro — the contract manufacturers, specification developers and sterilisers the primes buy from
- Minnesota OSHA Minnesota runs its own OSHA plan covering private-sector employers. MNSTAR and MNSHARP do not reference ISO 45001, and we will not pretend they do
- Minnesota's device supply tier The contract manufacturers, sterilisers and specification developers around the primes — where a first ISO 13485 certificate is most often a customer requirement rather than a choice
Why conforming to ISO 13485 is not the same as complying with the QMSR
This is the part that catches organisations who assume an existing ISO 13485 certificate means the work is done. Part 820 did not become ISO 13485. It incorporated it, and then kept its own sections on top.
820.10 requires compliance with the FDA-specific parts that ISO 13485 has no equivalent for — 21 CFR 803 medical device reporting, 806 corrections and removals, 821 device tracking and 830 unique device identification — and extends traceability requirements to life-sustaining devices.
820.35 carries more explicit complaint-record and investigation requirements than ISO 13485 does.
820.45 covers device labelling and packaging, including inspection of label accuracy before release. The FDA added it because it judged ISO 13485's labelling provisions insufficient on their own.
A gap assessment that stops at the ISO 13485 clause list will miss all three. That is the single most common way a confident device manufacturer gets a surprise at inspection.
What is actually true about this metro, measured
We are going to correct something we see written about the Twin Cities constantly, because it is checkable and it is wrong.
Minneapolis is not the largest medical device cluster in the United States. Counting FDA-registered device establishments, the metro ranks fifth — behind Los Angeles, New York, Boston and Chicago.
What is true, and better, is density. The Twin Cities carry roughly 360 FDA-registered device establishments (openFDA, August 2026 refresh), which works out at about 95 per million residents. Among the fifty-one US metros over a million people, only San Jose is denser. And among metros over three million, the Twin Cities are first — San Jose and Salt Lake City are both far smaller.
That is the honest version of the claim, and it survives a local reading it. It also describes something real: this is not a metro with a few enormous device companies, it is a metro where device work is woven through a very large small-manufacturer base — 4,201 manufacturing establishments, 3,749 of them under 100 employees (US Census County Business Patterns, 2023).
One naming point, since locals notice: Medtronic's principal executive office is in Ireland. Minneapolis is its operational headquarters — and the Medtronic Parkway address is physically in Fridley. Boston Scientific, likewise, is headquartered in Massachusetts; Minnesota is simply where its largest workforce is.
Where the money went in 2025
Minnesota's economic development department reported 122 expansion projects, $3.2 billion invested and 2,223 new jobs across the state in 2025. Life sciences was the largest sector by capital, at $1.7 billion across fourteen expansions.
Inside this metro: Boston Scientific committed $139 million and around 440 new jobs at Maple Grove. Beckman Coulter committed $50 million and 300 new jobs at Chaska, on a 148,000 square foot addition.
One boundary worth stating because it is the exact trap: Niron Magnetics' $169.7 million plant is in Sartell, which is the St. Cloud metro, not this one. The company is headquartered in Minneapolis. Headquarters here, plant elsewhere — and a page that counts it as a Twin Cities investment was not checked.
Minnesota runs its own OSHA plan — and one claim to be careful with
Minnesota operates an OSHA-approved State Plan covering most private-sector workers as well as state and local government. That matters for any ISO 45001 compliance obligations register built here, because a register assembled from federal OSHA sources alone will be structurally wrong.
What we will not tell you is that ISO 45001 is a route into MNSTAR or MNSHARP, Minnesota's cooperative safety programmes. We read both programme descriptions and neither mentions ISO 45001. MNSTAR requires a safety and health management system with named elements — leadership, employee involvement, hazard identification and control, training — but it names no ISO standard. ISO 45001 is a good way to build and evidence such a system. It is not a qualification for the programme, and anyone telling you otherwise has not read the page.
One practical note for device work specifically: the FDA's regulation applies to your establishment whether or not you hold a certificate, so the question is never whether to build the system. It is only whether to have a third party attest to it — and that answer usually comes from your customers rather than from the regulation.
How we work with companies here
We are based in the Kansas City metro and run Twin Cities engagements remotely, with on-site work at the points where being in the building changes the outcome — the gap analysis walkthrough, the first internal audit cycle, and the certification audits themselves.
For device work the on-site portion concentrates on production and process controls, and on the design history and device master record structure. Those are assessed by following the record through the building, not by reading a procedure about it.
The consultant who scopes the engagement does the work. No handoff to a junior implementer after the sale.
What an engagement covers
- QMSR gap assessment Your system against 21 CFR Part 820 as it now reads — which means ISO 13485:2016 plus 820.10, 820.35 and 820.45. An assessment that stops at the ISO clause list is the most common way this goes wrong.
- ISO 13485 system build A device quality management system built around your processes and your device classes. See ISO 13485.
- The FDA-specific overlay Medical device reporting under Part 803, corrections and removals under 806, device tracking under 821 and UDI under 830 — the requirements ISO 13485 has no equivalent for and 820.10 makes mandatory.
- Complaint handling and labelling control 820.35 and 820.45, both of which the FDA kept precisely because it judged the ISO text insufficient on its own.
- Gap analysis and roadmap Two to four weeks, fixed scope and price, with a clear go or no-go before real money is committed.
- Internal audit and management review Auditor-grade internal audits and a facilitated management review producing recorded decisions.
- ISO 45001 under MNOSHA Minnesota runs its own OSHA plan covering the private sector. A compliance obligations register built on federal requirements alone is incomplete here — see ISO 45001.
Questions we get from companies in this market
Does the FDA now require ISO 13485 certification?
No, and this is the most common error on the subject. The FDA states plainly that it will not require certificates of conformance to ISO 13485 and will not issue them. It also states that holding one will not exempt a manufacturer from an FDA inspection. What changed on 2 February 2026 is that the requirements of ISO 13485:2016 were incorporated by reference into 21 CFR Part 820 — so conformance to the substance is now mandatory, while the certificate remains a commercial choice.
We already hold ISO 13485. Are we compliant with the QMSR?
Not necessarily, and this is where confident organisations get caught. Part 820 incorporated ISO 13485 and then kept FDA-specific sections on top of it. Clause 820.10 requires compliance with medical device reporting, corrections and removals, device tracking and UDI — none of which ISO 13485 covers. Clause 820.35 carries more explicit complaint investigation requirements. Clause 820.45 covers labelling and packaging, added because the FDA judged the ISO provisions insufficient. A certificate tells you nothing about those three.
Is Minneapolis the largest medical device cluster in the country?
No, and we would rather correct that than repeat it. By FDA-registered establishment count the Twin Cities rank fifth, behind Los Angeles, New York, Boston and Chicago. What is true is density: roughly 95 registered establishments per million residents, second only to San Jose among metros over a million, and first among metros over three million. That is a stronger claim than the false one, and it describes something real about how device work is distributed through this market.
Is Medtronic headquartered in Minneapolis?
Its operational headquarters is here. Its principal executive office is in County Galway, Ireland. And the Medtronic Parkway address is physically in Fridley, which uses a Minneapolis mailing address. We mention it because it is the kind of detail that tells you whether a consultant checked anything, and because supplier qualification paperwork occasionally turns on getting a legal entity right.
Does ISO 45001 help us get into MNSTAR?
Not as a qualification. We read the MNSTAR and MNSHARP programme descriptions and neither mentions ISO 45001. MNSTAR requires a safety and health management system with specified elements, and ISO 45001 is a perfectly good way to build and evidence one — but it is not a route in, and the programme does not recognise it as such. Minnesota does run its own OSHA plan covering private-sector workers, which is the more important fact for most employers here.
What will certification cost?
Audit days are set from the number of people within your certification scope against a published table, then adjusted for factors including system maturity and single-site operation. Device work generally sits at the higher end because of scope complexity. Our certification cost breakdown reproduces the table so you can check any quote you receive.
Other standards we support in Minneapolis
Other standards in Minneapolis
This page is about ISO 13485, which is what this metro's industry asks for most often. We cover these here too.
- ISO 9001 in Minneapolis The Twin Cities are known for medical devices. But 3,749 manufacturers here have fewer than 100 employees, and the overwhelming majority of them make something else entirely.
- ISO 14001 in Minneapolis Minnesota gives you nothing for having an environmental management system. It does impose planning and reporting duties with no federal equivalent — and one of them has a date on it.