
MedTech Startup Regulatory Readiness Quiz
Assess Your Compliance Gaps in 2 Minutes
What the quiz checks
What the quiz checks
The seven questions follow the order regulatory foundations usually need to fall into place for a medical device or IVD startup: market choice, intended purpose, classification, quality system, risk management, design controls, and clinical evidence. Each one builds on the last, so a gap early in the sequence tends to cause rework later rather than staying contained. This quiz is one of Qserve's self-assessment tools. Answer honestly rather than aspirationally; the gap report is only useful if it reflects where you actually are.
Should you target the EU or the US first?
The EU and the US regulate medical devices differently, and that difference should shape which market you enter first. In the EU, most devices need a notified body to certify conformity under EU MDR (IVDR for in vitro diagnostics); in the US, many devices reach the market through an FDA 510(k) premarket notification, which shows the device is substantially equivalent to one already legally marketed.
The two routes can differ widely in the evidence they require, their cost, and their timeline. Treat the choice as a regulatory decision as much as a commercial one and revisit it if your funding timeline or target indication changes.
Why does the intended purpose come before everything else?
The intended purpose is a written statement of what the device does, for which patients, by which users, and in which setting and it drives classification, clinical evidence, and risk management downstream. EU MDR calls it the intended purpose; the FDA splits the same idea into intended use and indications for use.
Write it once, put it under document control, and use identical wording across your labeling, your website, and your investor materials. A changed intended purpose after classification is one of the more common sources of rework we see.
How is a medical device or IVD classified?
Classification decides who reviews your device and how much evidence you need, and it's usually the first gate to close. In the EU, classification follows the rules in Annex VIII of EU MDR (IVDs follow the parallel rules in Annex VIII of the IVDR); in the US, the FDA's product classification database lists device types with their class and product code.
Software is the most common surprise: under Rule 11 of EU MDR, software that informs a diagnostic or therapeutic decision is usually class IIa or higher, not class I. Record which rule or product code you applied and why. A notified body or FDA reviewer will ask.
What does a startup actually need in its quality management system?
EU MDR Article 10 and theFDA Quality Management System Regulation both require a quality management system, and both now build on ISO 13485. For a startup, the priority is a small system the team actually uses: document control, design controls, risk management, and supplier control.
Auditors look for records that show these processes working, not procedures that only exist on paper. Qserve's QA support team typically helps startups build exactly this scaled-down version first.
What does ISO 14971 require for risk management?
Risk management for a medical device or IVD follows ISO 14971, starting at the design stage and continuing for the device's whole life. A hazard list or FMEA is a starting point, not a finished risk management file. The standard also requires a risk management plan, verification of each control, a benefit-risk evaluation, and a report.
Risk controls become design requirements, so a hazard caught late in development usually means a redesign and repeated testing, not a quick fix to the label.
What are design controls, and what do reviewers check?
Design controls are the documented path from user needs to a finished design: verification shows the design meets its specifications; validation shows it meets user needs and its intended purpose. ISO 13485 clause 7.3 sets these out, and the FDA QMSR incorporates the same requirements for the US market.
Reviewers use a traceability matrix to check nothing was missed. It links every user need and design input to a test result. If that link is missing, expect a finding, not just a question.
What clinical evidence do you need for CE marking or FDA clearance?
EU MDR and the FDA both expect clinical evidence matched to the device's risk, and supporting every claim made for it. Under EU MDR, a clinical evaluation plan maps each claim to its evidence under Article 61 and Annex XIV of the EU MDR; relying on an equivalent device's data instead requires technical, biological, and clinical similarity plus access to that device's own data, rarely realistic for a startup.
A clinical investigation needs sign-off from an ethics committee and a competent authority in the EU, and in the US may also need an investigational device exemption (IDE). Qserve's Clinical Evaluation team can map your claims to the evidence you'll actually need before you start collecting it.
Get support closing these gaps
Qserve helps medical device and IVD startups put these foundations in place, from regulatory strategy and classification through to quality systems and clinical evidence. Our Startup team works specifically with early-stage companies, so the advice is sized to where you actually are, not to an enterprise quality system you don't need yet.
Frequently Asked Questions
Couldn't find your question?
Should a medtech startup launch in the EU or the US first?
There is no default answer. It depends on the regulatory route for your device in each market, the clinical evidence each route needs and your funding timeline. Decide early, and build your quality system and evidence base so they can serve the second market later.
When should a startup set up a quality management system?
Before design work goes far. Design controls are part of the QMS, and design work done outside them may need to be documented again or repeated. Start with the core processes and expand the system as the company grows.
How is medical device software classified under EU MDR?
Under Rule 11 in Annex VIII of EU MDR. Software that provides information used for diagnostic or therapeutic decisions, or that monitors physiological processes, is usually class IIa or higher. Other software is class I. In the US, the FDA classifies software using its own system of device types and product codes.
What is the difference between intended purpose and intended use?
Under Rule 11 in Annex VIII of EU MDR. Software that provides information used for diagnostic or therapeutic decisions, or that monitors physiological processes, is usually class IIa or higher. Other software is class I. In the US, the FDA classifies software using its own system of device types and product codes.
Can a startup rely on equivalence instead of a clinical investigation?
Sometimes, but it is harder under EU MDR than many founders expect. The device must be technically, biologically and clinically similar to the other device, and you need access to that device's data. For implantable and class III devices, this usually means a contract with the other manufacturer. Check early whether this route is realistic for your device.
Latest blogs
-1.png)
This blog explores the key regulatory challenges and practical considerations involved in developing companion diagnostics for clinical trials in the US and EU.
.png)
Class B and Class A-sterile IVDs now need notified body sign-off. Get the 8-step plan to apply before May 26, 2027, and what the IVDR 2.0 proposal could change.
-4.png)
ISO 9001:2026 has been published: translate ISO 9001:2026 developments in your supply chain into effective ISO 13485 supplier controls.
