Back to home Medtech Regulation · 10 min read

Why a medical device takes years to reach the ward.

Founders new to medtech are often surprised by how long the road is from working prototype to hospital purchase. Most of that time is evidence, not engineering.

A bedside medical monitor beside a stack of documents and a checklist

The short version

  1. 01 Most of the time from prototype to ward goes on evidence, documentation and approval.
  2. 02 Start a quality system with design controls early; retrofitting one is slow and costly.
  3. 03 The regulatory route, set by risk class and market, largely decides the timeline.
  4. 04 Hospitals need workflow, service and outcome evidence before they buy.

The prototype works. It measures what it should, it fits in a nurse's hand and the first clinicians to try it want one. In consumer hardware, that is the moment to start manufacturing. In medical devices, it is closer to the moment the real project begins.

The gap surprises founders because it is mostly invisible. It is filled with documents, tests, audits and clinical evidence, all of which exist to answer one question for a regulator and a hospital: can we trust this device with a patient?

Design controls start earlier than you think

Regulators expect a device to be designed under a quality system, with design controls that trace every requirement to a test that proves it is met. Teams that built their prototype informally often have to go back and document, or redo, work they thought was finished. Starting a quality system early, even a lightweight one, is usually cheaper than reconstructing one later. Engineering teams outside medtech face a version of this too, which is why we argue for one set of requirements for the whole machine.

Two words matter here. Verification shows the device was built the way it was specified. Validation shows that what was specified actually meets the needs of the people who use it, in the setting where they use it. Both need evidence, and both start with a documented look at hazards, much like a cobot risk assessment on a factory floor.

We had a finished product and an unfinished file. The file took longer.

Co-founder, diagnostics startup

The regulatory route sets the clock

How long the next stage takes depends on the device's risk class and the market. The review itself is the short part: the FDA's goal is a decision on a 510(k) within 90 FDA days, a count that stops while the agency waits for answers to its questions. The years go on what comes before and after it: the design and verification work, any clinical study and the hospital's own evaluation. In the United States, many moderate-risk devices are cleared through the FDA's 510(k) route by showing they are substantially equivalent to a device already on the market, while novel high-risk devices need premarket approval, which usually requires clinical data. In the European Union, the Medical Device Regulation requires most devices beyond the lowest class to be assessed by a notified body.

Each route has its own evidence bar, and choosing one is a strategic decision as much as a regulatory one, and the guidance documents the FDA plans to publish, covered in our look at its 2027 guidance agenda, show where those bars are moving. A device designed to fit an existing category can sometimes reach market far sooner than one that creates a new category.

Then the hospital has its own questions

Clearance lets a device be sold. It does not make anyone buy it. Hospital procurement teams want to know how the device fits existing workflows, what training it needs, how it connects to their systems, who services it and whether there is evidence it improves outcomes or saves money. Pilots and health-economic data often take as long to assemble as the regulatory file.

None of this is a reason not to build medical devices. It is a reason to plan the evidence alongside the engineering from the first month, and to fund the company for the whole road rather than just the prototype.

About the author

Nkem Adeyemi

Nkem Adeyemi edits the medtech and agritech desks. A biomedical engineer by training, she worked in quality and regulatory roles at two device makers before moving into reporting, and grew up on a mixed farm that still argues about yield maps. She writes for buyers, clinicians and growers who want to know what the evidence shows, which approvals matter and whether a new sensor or device does what its maker says.

All stories by Nkem 3 stories

Keep reading

Liked this?
Get five more.

For founders, engineers and operators who would rather read the spec sheet than the press release.

The Town Crier Free

Your week in industry, in five minutes.

One email on Wednesday morning. The stories worth your time this week, and nothing else.

No spam. Unsubscribe anytime.