Do I need FDA approval to sell my device?

It depends on whether your product meets the definition of a medical device — which turns largely on the claims you make. A wellness product that tracks general fitness may fall outside FDA device regulation, while the same hardware with a diagnostic claim becomes a regulated device. Classification then determines the pathway: many Class I devices are exempt from premarket submission, most Class II devices need a 510(k) clearance, and Class III devices need PMA approval. Always confirm with a regulatory professional.

What is the difference between 510(k) and PMA?

A 510(k) demonstrates that your device is substantially equivalent to a legally marketed predicate device — it is the most common pathway for moderate-risk devices and usually does not require large clinical trials. PMA (Premarket Approval) is the far more demanding pathway for high-risk Class III devices, generally requiring clinical data proving safety and effectiveness. Novel moderate-risk devices without a predicate can use the De Novo pathway.

What is ISO 13485 and do I need it?

ISO 13485 is the international standard for medical device quality management systems. It defines how development and manufacturing must be controlled and documented: design controls, traceability, design reviews, verification and validation, and supplier management. Working within such a framework from the start is essential — regulators review your development process, not just your finished product.

How long does it take to develop a medical device?

Typically several years from concept to cleared product, depending on classification and clinical requirements. A simple Class I or 510(k)-pathway device can move much faster than a Class III implant requiring clinical trials. The biggest schedule killer is retrofitting quality and regulatory work late — teams that run design controls from day one consistently reach market sooner.

Is my product a medical device or a wellness product?

The line runs through your intended use and claims. "Helps you track your workout recovery" is generally wellness; "detects irregular heart rhythm" is a medical claim that triggers device regulation. The same hardware can fall on either side. Defining your claims strategy early — with regulatory guidance — is one of the highest-leverage decisions in the whole project.

Medical Device Development: FDA Classes, 510(k) vs PMA and Design Controls

The Premier League of Product Development

Medical device development is the most demanding branch of new product development. The same idea that would become a consumer prototype in a month must, in the medical world, travel a rigorous path of documentation, risk management, testing, and regulatory clearance — because here a mistake is not a product return, it is a patient safety issue. Demand for medical innovation — from surgical tools to wearable sensors — keeps growing, and so does the reward for teams that plan the journey correctly. This guide explains what it really takes to develop a medical device today, and why the most important decisions are made on day one. To be clear: this is educational content, not regulatory advice — every project should involve qualified regulatory professionals.

First Question: How Is Your Device Classified?

The first question in any medical device project is not "How will it work?" but "How is it classified?" The FDA sorts devices by risk, and the classification drives the entire development path:

Class I — lowest risk (think tongue depressors and bandages). Most are exempt from premarket submission but still subject to general controls.
Class II — moderate risk. Most innovative devices land here and typically go through the 510(k) pathway — demonstrating substantial equivalence to an existing, legally marketed device — or the De Novo pathway for novel devices with moderate risk and no predicate.
Class III — highest risk, typically life-sustaining or implantable devices. These require PMA (Premarket Approval), the most demanding pathway, generally including clinical data.

Choosing your first target market and claims is a strategic decision that shapes budget, timeline, and the design itself — which is why it must be made at the start of the project, not the end. The line between a "wellness gadget" and a regulated medical device runs exactly through the clinical claims you make, and understanding that line early can save years.

The Three Pillars: Quality, Risk, and Usability

Three internationally recognized frameworks accompany every serious medical device program:

Design controls and ISO 13485 — the quality management framework that defines how a medical device is developed and manufactured in a controlled, documented way: traceable requirements, documented design reviews, verification and validation, and supplier management. The FDA's quality system regulation expects design controls; development done outside such a framework simply will not be accepted.
ISO 14971 risk management — systematic mapping of every possible failure scenario, assessment of severity and probability, and mitigation built into the design itself. It is a living document that follows the product from first sketch to end of life.
IEC 62366 usability engineering — a large share of medical incidents stem from use errors, not technical failures. The standard requires designing the user interface around real use scenarios and running structured usability testing with representative users — physicians, nurses, or patients.

For devices with software — and nearly all of them have software today — add IEC 62304 for medical device software and increasingly strict cybersecurity expectations, which have become an integral part of FDA submissions. This is where disciplined embedded software development earns its keep.

The Trends Shaping the Field

Digital health and wearables — tiny sensors, wireless connectivity, and cloud platforms enable continuous monitoring outside the hospital: ECG patches, continuous glucose monitors, diagnostic-capable wearables. These products lean on advanced electronics development and careful power and antenna design.
AI as a medical component — algorithms for diagnosis and decision support are being cleared at a growing pace, and regulators have developed dedicated approaches for learning software. Documenting training data and proving performance are now part of the regulatory file.
Biocompatible materials and medical 3D printing — biocompatible resins and nylons enable 3D printing of skin-contact components, patient-specific surgical guides, and preclinical prototypes at a pace that was impossible before.

Clinical Evidence: Proving It Actually Works

Beyond engineering verification, a medical device must demonstrate safety and effectiveness: lab testing, biocompatibility testing, and — depending on classification and claims — clinical evaluation based on existing literature or a dedicated clinical study. Planning the evidence strategy early can save expensive studies: sometimes a small change in the product's claims or the choice of predicate device dramatically reduces what is required.

Why Regulatory Planning Starts on Day One

This is the classic, most expensive mistake in the field: build something that works first, deal with regulation "later." In practice, a device developed without documented design controls will need nearly complete redevelopment — because the FDA reviews not just the product, but the development process behind it. A non-biocompatible material, an electronic component without proper documentation, a user interface that never saw usability testing — any one of these can set a project back years. When the regulatory pathway is mapped from the start, it stops being an obstacle and becomes a roadmap.

How Projects House Runs a Medical Device Program

Definition and regulatory strategy — we define the clinical need, the product claims, and the expected classification in your target markets, and build a regulatory roadmap together with regulatory affairs consultants.
Multidisciplinary design under design controls — mechanics, electronics, software, and industrial design developed within a documented framework aligned with ISO 13485, with ISO 14971 risk management from the first drawing.
Prototypes and testing — functional prototypes, formative testing, and usability studies per IEC 62366, refined in fast iterations.
Verification and validation — full V&V against requirements, support through standards testing (medical electrical safety, biocompatibility, EMC), and preparation of the technical documentation for submission.
Transfer to manufacturing — hand-off to appropriately certified manufacturers through our global network, process validation, and support through manufacturing ramp-up and regulatory submission.

Building a Medical Device? Let's Plan the Path

The teams that reach clearance fastest are the ones that plan classification, quality, risk, and clinical strategy from day one. Tell us about your device through our contact form — we will map a safe route from clinical idea to market-ready product, together with your regulatory advisors.

Medical Device Development: From Concept to FDA-Ready Product