What Is a Medical Device?

A medical device is, in plain terms, any product intended to diagnose, treat, monitor, or prevent a disease or condition — or to affect the structure or function of the body — without doing so primarily through chemical action absorbed into the body. That last clause is the load-bearing one: it is the line U.S. law draws between a device and a drug. Under that line, “medical device” turns out to be an enormous category, running from a tongue depressor and an adhesive bandage to an MRI scanner, an insulin pump, and an implantable pacemaker.

This page answers the broad question — what actually counts as a medical device, why the category is defined the way it is, and how it differs from the adjacent categories (drugs, biologics, in vitro diagnostics) that are frequently confused with it. It then points to CASRAI’s deeper library on medical device regulation, quality systems, and market pathways for readers who need the operational detail.

The Legal Definition of a Medical Device

In the United States, “device” is defined by statute at Section 201(h) of the Federal Food, Drug, and Cosmetic Act (FD&C Act), codified at 21 U.S.C. § 321(h). The definition covers “an instrument, apparatus, implement, machine, contrivance, implant, in vitro reagent, or other similar or related article, including any component, part, or accessory,” that is:

• recognized in an official pharmacopeia or formulary, or
• intended for use in the diagnosis of disease or other conditions, or in the cure, mitigation, treatment, or prevention of disease, or
• intended to affect the structure or any function of the body,

and which does not achieve its primary intended purposes through chemical action within or on the body and is not dependent on being metabolized to achieve those purposes. That final condition is what separates a device from a drug: a coronary stent holds an artery open mechanically; a statin lowers cholesterol through a chemical/metabolic pathway. Same general goal — treating cardiovascular disease — two entirely different legal categories, with different regulatory pathways attached to each.

Every other country with a device-regulation regime uses a broadly similar functional test, even where the statutory wording differs — the EU’s Medical Device Regulation (MDR, 2017/745) defines “device” almost identically, minus the U.S.-specific pharmacopeia clause.

Why the Definition Exists

The device/drug distinction is not a legal technicality for its own sake — it exists because the two categories fail differently and need different evidence to prove they’re safe. A drug’s risk profile is largely about systemic chemistry: absorption, distribution, metabolism, toxicity, drug-drug interaction. A device’s risk profile is largely about engineering and human factors: mechanical failure, biocompatibility of materials in contact with tissue, software defects, use error. Regulators built separate frameworks — new drug approval built around clinical pharmacology, device regulation built around risk-based classification and design controls — because forcing every device through a drug-style approval process would be both a poor fit for the actual risks and, for the large majority of low-risk devices, wildly disproportionate.

That’s also why device regulation is risk-tiered rather than uniform. FDA sorts devices into three classes based on the level of control needed to provide reasonable assurance of safety and effectiveness:

• Class I (low risk): General controls only — most are exempt from premarket review entirely. Typical examples: elastic bandages, tongue depressors, manual stethoscopes, non-electric wheelchairs.
• Class II (moderate risk): General controls plus “special controls” (performance standards, specific labeling, postmarket surveillance) — most reach market through the 510(k) premarket notification pathway. Typical examples: infusion pumps, powered wheelchairs, many diagnostic imaging systems, surgical drapes.
• Class III (highest risk): Devices that are life-sustaining, life-supporting, or present a significant risk of illness or injury — these generally require Premarket Approval (PMA), the most rigorous device pathway, with clinical data comparable in scope to a drug submission. Typical examples: implantable pacemakers, replacement heart valves.

CASRAI’s guide to FDA device classification, 510(k), and PMA pathways covers how a device is actually assigned a class and routed to a submission type. The predicate device and substantial equivalence guide covers the logic behind the 510(k) pathway specifically — the most common route to market for Class II devices.

Medical Device vs. Drug, Biologic, and In Vitro Diagnostic

Because “what is a medical device” is usually asked alongside a handful of adjacent categories, it’s worth being explicit about how each differs:

• Device vs. drug: covered above — the dividing line is mechanism (mechanical/physical/electrical action) versus chemical action metabolized by the body. See CASRAI’s guide to what a biologic drug is for the adjacent drug-side category.
• Device vs. biologic: a biologic is a product derived from a living organism — a vaccine, blood product, gene therapy, or monoclonal antibody — regulated under the Public Health Service Act and typically licensed via a Biologics License Application (BLA) rather than cleared or approved under the FD&C Act’s device pathways. Some products combine both: a drug-eluting stent or a prefilled autoinjector is a “combination product,” regulated under whichever component provides its primary mode of action, with FDA assigning a lead center (CDRH for devices, CBER/CDER for biologics/drugs) accordingly.
• Device vs. in vitro diagnostic (IVD): this one surprises people — in the U.S., an IVD is not a separate legal category from a device at all. It is a device: FD&C Act Section 201(h) explicitly includes “in vitro reagent” in the device definition, and IVDs are regulated under the same Title 21 device framework (with additional IVD-specific rules at 21 CFR Part 809). What changes is the mechanism of use — an IVD examines a specimen (blood, tissue, urine) outside the body rather than acting on the body directly. The EU draws a sharper line: IVDs are regulated under their own separate regulation, the IVDR (2017/746), distinct from the general MDR (2017/745), even though the products serve an analogous diagnostic function. See CASRAI’s guide to what an in vitro diagnostic is and the deep-dive on IVDR requirements for the EU-specific framework.

Software and Combination Products

Two categories that don’t fit the “physical object” intuition of “medical device” are worth calling out specifically, because both are unambiguously devices under the statutory test above:

• Software as a Medical Device (SaMD): software intended for a medical purpose — diagnostic algorithms, dose calculators, AI-based image analysis — that runs independently of a hardware medical device. It meets the same “intended to diagnose/treat/affect body structure or function” test as a physical instrument, and FDA regulates it accordingly, including software-specific guidance on cybersecurity and human factors. See CASRAI’s guide to Software as a Medical Device.
• Software that runs a device or accompanies it: firmware controlling an infusion pump or an app that displays data from a continuous glucose monitor is typically part of the device’s design controls rather than a standalone SaMD — CASRAI’s IEC 62304 guide covers the software lifecycle standard that applies here.

How a Device Is Built, Documented, and Kept on the Market

Once something is established as a device, it enters a lifecycle of quality and documentation obligations that runs from design through postmarket surveillance:

• Quality management system: device manufacturers build and maintain a QMS aligned to ISO 13485, the internationally recognized quality standard specific to medical devices, which FDA’s Quality Management System Regulation (QMSR, replacing the older 21 CFR Part 820 Quality System Regulation) now incorporates by reference.
• Design controls and the design history file: a documented, traceable record of design inputs, verification, validation, and changes — see CASRAI’s design history file guide.
• Unique Device Identification (UDI): most devices must carry a standardized identifier and be listed in FDA’s public device database — see CASRAI’s UDI guide.
• Postmarket obligations: adverse event reporting, complaint handling, and — for EU MDR devices — ongoing post-market clinical follow-up. CASRAI’s complaint handling guide covers the U.S. side of this.

Outside the U.S.: CE Marking and Global Variation

A device legally marketed in the U.S. is not automatically legal to sell elsewhere. In the European Union, a device must carry CE marking under MDR (or IVDR for diagnostics) before it can be placed on the market, following a conformity assessment that, for most device classes, involves an independent notified body rather than a government agency. Other jurisdictions — UKCA in the UK, Health Canada’s device licensing, Australia’s TGA, Japan’s PMDA — each run their own classification and review system, and a device cleared in one jurisdiction generally still needs a separate submission to reach another.

Who in a Research Organization Needs This

“Medical device” regulation touches more roles in a research institution than the phrase might suggest:

• Regulatory affairs staff classify devices, choose submission pathways, and maintain the technical documentation a device needs to stay on the market.
• IRB coordinators and clinical research staff encounter devices most often through an Investigational Device Exemption (IDE) — the mechanism that lets an unapproved device be used in a clinical study — which carries its own consent, risk-determination, and reporting requirements distinct from a drug IND.
• Compliance and quality staff maintain the QMS, document control, and CAPA processes a device manufacturer or device-using research unit needs under ISO 13485 or FDA’s QMSR.
• Procurement and equipment managers deal with the device definition from the buying side: confirming a purchased instrument’s classification, verifying vendor documentation, and building the maintenance/calibration records an accredited lab or clinical unit needs to keep. CASRAI’s guides to a medical equipment management plan, biomedical equipment inventory tracking and lifecycle management, and a hospital or clinic equipment procurement policy cover that side of the work in detail.
• Lab managers working with in vitro diagnostics or lab instrumentation need to know which pieces of equipment are devices subject to FDA/CLIA oversight versus general lab equipment that isn’t.

Frequently Asked Questions

Is a bandage a medical device?

Yes. A simple adhesive bandage meets the statutory test — it’s intended to affect the body (protecting a wound, supporting healing) without chemical/metabolic action — and FDA classifies most bandages as Class I, exempt from premarket review.

Is software a medical device?

It can be. Software intended for a medical purpose — diagnosis, treatment planning, patient monitoring — is regulated as Software as a Medical Device (SaMD) if it meets the same intended-use test as a physical device. General wellness apps that don’t make medical claims typically fall outside FDA’s device jurisdiction; the line depends on the specific intended use claimed for the software.

Do all medical devices need FDA approval before they can be sold?

No. Most Class I devices are exempt from premarket review entirely. Most Class II devices reach market through 510(k) clearance (demonstrating substantial equivalence to an existing device), which is a lower evidentiary bar than “approval.” Only Class III devices generally require full Premarket Approval (PMA). “Cleared” and “approved” are not interchangeable terms in FDA’s own usage.

What’s the difference between a medical device and medical equipment?

“Medical device” is the legal/regulatory category defined by statute. “Medical equipment” is a broader, non-regulatory umbrella that in everyday use often includes both regulated devices (infusion pumps, monitors) and non-device items (exam tables, general furnishings) that a hospital or lab still needs to procure and maintain. Procurement and equipment-management processes typically need to track both, even though only the device subset carries FDA/CE regulatory obligations.

Where to Go Next

This page is the entry point into CASRAI’s broader medical device and diagnostics quality coverage. From here, the most common next steps are: understanding how devices are classified and routed to a submission pathway, building out a ISO 13485 quality management system, or working through the design history file and other design-control documentation a device needs from concept through market. Research-administration readers focused on the buying and asset-management side should start with the medical equipment management plan guide.