The question that decides your entire budget
Before you start developing anything health-related, one question determines the whole development path: does your product meet the FDA's definition of a medical device? The answer changes your budget, timeline, documentation burden, testing requirements, and marketing channels. A consumer product can go from concept to shelf in months. A regulated medical device requires a quality system, design controls, clinical or performance evidence, and a submission process that can double or triple development cost and add a year or more to the schedule.
The reverse error is worse. Marketing an unapproved medical device exposes you to enforcement action, removal from retail and online marketplaces, import refusal, and liability. So you run this test on day one — not after the product is designed.
The definition: intended use decides, not technology
The principle at the heart of US, European, and most other frameworks is the same, and it surprises almost every founder: a medical device is defined by its intended use, not by what is inside it.
Under the Federal Food, Drug, and Cosmetic Act, a device is broadly an instrument, apparatus, machine, implement, in vitro reagent, or similar article — including software — that is intended for use in the diagnosis, 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 effect through chemical action or by being metabolized.
Read that carefully. The exact same optical sensor can be a toy, a fitness product, or a Class II medical device. The difference is entirely in what you say it does.
The four-question test
When we evaluate a new product, these are the questions that settle it:
- What is the stated intended use? Is the product meant to diagnose, treat, monitor, or mitigate a medical condition — or only to support general healthy living?
- What claims will you make? “Tracks your heart rate during exercise” is a fitness product. “Detects irregular heart rhythm” is a medical device. Your packaging, website, ad copy, app store description, and even your sales deck are all part of the record.
- Who is the target audience? A product aimed at patients, post-surgical recovery, or people with a named condition moves toward the medical definition even without an explicit claim.
- How does it act on the body? If it physically affects the body — energy delivery, electrical stimulation, radiation, pressure, suction, heating, sampling — the probability that it is a device rises sharply.
The gray zone: general wellness or medicine?
Most real dilemmas sit on the seam between wellness and medicine. The FDA has published guidance specifically for low-risk general wellness products, and the boundary it draws is roughly this: claims about general fitness, relaxation, sleep quality, weight management, or mental acuity, made without reference to a specific disease, generally stay outside device regulation — provided the product is low risk.
Concrete examples of the line:
- A band that counts steps and reports sleep quality is generally a wellness product. The moment it alerts the user to possible sleep apnea, it has crossed over.
- A massage device sold for relaxation is a consumer product. The same device marketed for treating chronic pain is a different regulatory story.
- A scale that reports weight is a consumer product. A scale that flags fluid retention as a sign of heart failure decompensation is not.
Software alone can be a medical device with no hardware whatsoever — an app that recommends a drug dose or analyzes symptoms to suggest a diagnosis falls inside the definition. That category has its own rules and its own vocabulary; see software as a medical device (SaMD).
Two more things worth knowing. Regulators publish guidance documents aimed precisely at these borderline categories, and reading the relevant one is usually more useful than reasoning from first principles. And the answer can differ by market: a product treated as general wellness in the US may be a regulated device in Europe. If you plan to sell in several markets, run the definition test separately for each.
If the answer is yes, here is what follows
Once the product falls inside the definition, the next step is determining its risk class, because that is what sets how heavy the path will be — see FDA medical device classes. From there you choose a submission route, and the differences between the main pathways are laid out in the FDA approval process for medical devices.
You will also need a quality management system, which for most manufacturers means building to ISO 13485 requirements and the FDA's aligned quality system regulation, with design controls, risk management, and design history documentation from the first sketch. Prototyping changes character too — see medical device prototyping. Price it honestly before you commit: full detail is in how much it costs to develop a medical device.
Sometimes the definition is a strategic choice
Because the stated intended use governs, founders occasionally have genuine room to maneuver — and it can be used well or badly.
Used well: launch first as a general wellness product with honest, non-diagnostic claims, generate revenue and real-world usage data, and pursue the regulated indication afterward with a funded company and evidence in hand. Many successful health hardware companies followed exactly that sequence.
Used badly: build a product that obviously performs a diagnostic function, then dress the marketing in wellness language and hope nobody notices. Regulators look at the whole picture, including how customers actually use the product and what your own materials imply. Getting this wrong late is far more expensive than choosing a regulated path early.
Whichever way you go, design the hardware so the regulated version is reachable: sensor accuracy that can withstand validation, traceable design records, and an architecture that will not need to be rebuilt when a claim changes.
An important disclaimer
This article is educational engineering guidance, not legal or regulatory advice. Projects House is a product engineering firm, not a law firm or a regulatory consultancy. Device classification decisions carry legal consequences; confirm your specific situation with qualified regulatory counsel, and use the FDA's own guidance documents and formal classification request processes where appropriate.
Run the test before you spend
Projects House develops health and medical hardware, and we start every such project by mapping intended use, claims, and the regulatory consequences of each — because that decision constrains every engineering choice that follows. If you are unsure which side of the line your product sits on, describe it through our contact form and we will walk you through the implications. More background is in our medical device development section.