Guide · Medical devicesUpdated October 15, 2026

How to run a medical device clinical study, step by step

A device study is not a drug trial with a different product. The pathway depends on risk class and region, the standard is written for devices, and device-specific records matter. Here are ten steps from first question to close-out, and the data setup that makes the later steps easier.

  • Ten steps, start to close-out
  • US and EU pathways in plain terms
  • Not legal advice: verify the texts

Free sandbox · No credit card · 21 CFR Part 11 aligned

Illustrative device study plan · demo, months
123456789101112131415161718

Month

Pathway and plan

Classification, investigation plan

Approvals

Ethics, regulator as required

Build and site start-up

Forms, training, device supply

Enrolment and follow-up
Analysis and close-out

Lock, report, archive

Demo timings only. Real timelines depend on risk class, regulator and site readiness.

The short version

  • Start with the question the study must answer. Is it a feasibility study, a pivotal study to support clearance or approval, a conformity assessment study or a post-market study? That choice drives the rest.
  • The regulatory pathway depends on region and risk. In the US, significant-risk device studies generally need an Investigational Device Exemption (21 CFR Part 812) while non-significant-risk studies follow abbreviated requirements under IRB oversight. In the EU the Medical Device Regulation sets rules for clinical investigations. Check the current text for your device.
  • ISO 14155 is the device GCP standard. Many sponsors and regulators use it as the quality framework. Check which edition is current for your region before you write the plan.
  • Devices bring their own records. Device accountability, usability, device deficiencies, adverse device effects and software versions all need to be designed into the data collection from day one.
  • Small teams can run these studies. A well-scoped plan, a clear data build and a system that you can change yourself cover most of the operational risk.

Context

What is different about a device study

A medical device clinical study tests the safety and performance of a device in people. The product may be a catheter, an implant, a diagnostic, a wearable sensor or a piece of software that meets the definition of a device. Compared with a drug trial, the intervention is often tied to a procedure and a user (the clinician), the product can change between versions during development, and the end-points are frequently performance measures as well as safety outcomes. There is also usually no placebo in the pharmaceutical sense, which makes the design question of comparator and blinding an early decision.

Regulation reflects that. The sponsor needs to understand classification, the right study type for the stage of development and the evidence a notified body or regulator will expect. This page gives you the working outline. The detailed regulatory choices, such as whether your study needs an IDE or a competent authority application, are for your regulatory adviser to confirm against the current texts. For the software angle on the same topic, see EDC for medical device clinical trials and ISO 14155 clinical investigation software.

The process

Ten steps from idea to archived study

Order varies by device and region, but most studies pass through each of these.

  1. 1

    1. Define the intended use and the evidence gap

    Write the intended purpose in one paragraph, who uses the device, on whom and in what setting. Then list what you still need to show: safety, performance, usability or clinical benefit. If you cannot state the gap, you cannot design the study.

  2. 2

    2. Classify the device and choose the pathway

    Risk class and region decide the route. In the US, check whether the study is significant risk (IDE) or non-significant risk (abbreviated requirements, IRB oversight) and whether a pre-submission meeting with FDA would help. In the EU, check the clinical investigation articles and Annex XV of the MDR and the competent authority process in each country. Confirm with a regulatory specialist.

  3. 3

    3. Choose the study design and endpoints

    Feasibility, pivotal or post-market. Pick the comparator, sample size logic, primary performance and safety endpoints and the follow-up schedule. A sample size calculator and a schedule of assessments builder help you test the design before it is fixed.

  4. 4

    4. Write the clinical investigation plan

    The plan (the protocol for devices) covers rationale, design, device description, procedures, monitoring, adverse event and device deficiency reporting, statistical analysis and data handling. ISO 14155 sets out content expectations. Use a protocol template as a starting structure.

  5. 5

    5. Plan quality, risk and monitoring

    Document the risks to participants and to data quality, and scale monitoring to them. Risk-based monitoring is accepted for device studies; see risk-based monitoring and SDV software. Decide who monitors, how often and what is verified against source.

  6. 6

    6. Get the approvals

    Ethics committee or IRB approval, and a regulator application where required (an IDE application for significant-risk US studies, a competent authority or notification route in the EU). Prepare the participant information and consent materials in parallel; the IRB submission checklist lists what to assemble.

  7. 7

    7. Set up data capture

    Build the eCRFs and the schedule from the plan, with device-specific forms. Decide roles, edit checks and the export before you enrol. Test the build in a sandbox. See the data section below.

  8. 8

    8. Start sites and manage the device

    Train investigators on the plan, the device and the forms. Agree device supply, labelling, storage and return, and keep an accountability log. Assign delegation of duties. Open sites only when approvals, training and system access are in place.

  9. 9

    9. Enrol, collect and monitor

    Consent, screen, treat and follow up according to the plan. Track safety events, device deficiencies and deviations as they occur, answer queries and review dashboards routinely. Amendments go through ethics and, where needed, the regulator before the build changes.

  10. 10

    10. Close out, analyse and archive

    Reconcile open queries and events, lock the database, analyse, write the report and archive records for the period your regulations and contract require. Plan the archive early; see clinical trial data archiving and retention.

Pathways at a glance

US and EU routes compared in plain terms

A simplified orientation, not a substitute for the regulation text or advice.

QuestionUnited StatesEuropean Union
Main legal frameworkFDA regulations including 21 CFR Part 812 (IDE), Parts 50 and 56 (consent and IRB)Medical Device Regulation (EU) 2017/745, clinical investigation articles and Annex XV, plus national rules
Who reviewsIRB; FDA for significant-risk studies under an IDEEthics committee and the competent authority in each member state, as the national route requires
Risk splitSignificant risk vs non-significant riskDepends on class and on the purpose of the investigation
Good clinical practice referenceFDA regulations; ISO 14155 is a recognised consensus standardISO 14155 is widely used; check harmonisation status for the edition you follow
Safety reportingUnanticipated adverse device effects and others per Part 812Serious adverse events and device deficiencies per the MDR and national rules

Check the current edition of each source. Secondary sources disagree on some current-edition details of ISO 14155.

Rehearse your device study build free

Build the visits, device accountability form and adverse device effect form, add edit checks and enter test participants. The free sandbox has every feature, with no credit card and no time limit.

Build your device study free

Data setup

What to capture in a device study, and how

Device studies need the usual forms (demographics, eligibility, medical history, concomitant medications, vital signs) and several that are specific. Use the eCRF design guide to keep fields tied to endpoints, then add the device forms below. The same casebook should hold them so that the investigator, monitor and statistician see one record.

Design for the people who will use it. Device investigators are often procedural clinicians with limited time, so keep forms short and put required fields where the procedure data is naturally recorded. Calculated fields can remove arithmetic from the form, and the audit trail records who changed what and why. If your study uses a wearable or sensor, see EDC for wearable device studies.

Device-specific forms to plan for

Not every study needs all of these; the plan decides.

  • Device identification and accountability: model, lot or serial number, software version, date of use, date returned.
  • Procedure details: operator, technique, duration, any intra-procedural issues.
  • Adverse events and adverse device effects, with causality to the device and the procedure.
  • Device deficiencies and malfunctions, including whether they could have led to harm.
  • Usability or user experience questionnaires where the plan includes them.
  • Protocol deviations and device-related corrective actions.

What you do in Capture

Capture is a self-serve EDC where the study team builds the forms directly.

  • Upload the clinical investigation plan and let the AI study builder draft the visit schedule and forms, then review every item; nothing is saved without human review.
  • Add edit checks that raise an auto-query when a value breaks a rule, and set source data verification per field for risk-based monitoring.
  • Invite site staff with role-based access; the audit trail is field-level with timestamp, user, old value, new value and reason for change.
  • Export CSV or Excel with a data dictionary, or SDTM datasets as SAS XPT with Define-XML, when the statistician is ready.
  • Use 21 CFR Part 11-aligned controls, with validated use remaining a shared responsibility with the sponsor.
Device accountability · demo form
Subject 002-0017 · Visit 1 (Implant)Draft

Device

Device model

DVMODEL
DEMO-A 3.5 mm

Serial number

DVSERIAL
DM-0042731

Software version

DVSW
v1.4.2

Used as intended

DVINT
YesNo

Deficiency

Device deficiency observed

DVDEF
NoneYes

If Yes, an event form opens

Demo form with made-up values. Build the version your plan requires.

Avoiding trouble

Common problems in device studies and the fix

Study type unclear

Write the purpose (feasibility, pivotal, post-market) in the plan summary and check the pathway with a regulatory adviser before you set a budget.

Device and software versions drift

Capture the version at every use. If the device changes mid-study, treat it as a plan amendment and assess the impact on the data.

Under-reported device deficiencies

Make a deficiency question mandatory on every procedure form and train sites on what counts as one.

Operator effects ignored

Record the operator and a learning-curve indicator if the plan expects one, so the analysis can adjust.

Registration and transparency forgotten

Ask your adviser whether the study must be registered (for example in ClinicalTrials.gov or the EU database) and when results are due.

Data cannot be exported in time

Open a test export in the first month. See EDC implementation mistakes.

FAQ

Questions teams ask before they switch

Something not covered here? Ask us directly.

What is a medical device clinical study?

A clinical study that evaluates the safety, performance or clinical benefit of a medical device in human participants. Depending on region it is called a clinical investigation, a device trial or an IDE study, and it follows the rules for device studies rather than drug trial rules.

Do all device studies need an IDE?

No. In the US, significant-risk device studies generally need an Investigational Device Exemption under 21 CFR Part 812, while non-significant-risk studies follow abbreviated requirements under IRB oversight. Some studies are exempt. Confirm with FDA guidance and your IRB.

What is ISO 14155?

ISO 14155 is the international good clinical practice standard for clinical investigations of medical devices in humans. Check which edition is current and how your regulator treats it before you write the plan.

How long does a device clinical study take?

It varies widely with risk class, regulator and follow-up length. Feasibility studies can run in months, pivotal studies often take years. Use a timeline planner with realistic approval and enrolment assumptions.

What data does a device study collect that a drug trial does not?

Device identification and accountability, software versions, procedure and operator details, device deficiencies and malfunctions, and usability measures, in addition to the usual safety and efficacy data.

Can a small company or university run a device study without a CRO?

Yes, many do, but the sponsor remains responsible for compliance. A clear plan, a regulatory adviser, a monitoring approach scaled to risk and a self-serve data system you control keep the workload manageable.

Is Capture suitable for medical device studies?

Capture is a self-serve EDC with eCRF builder, ePRO, eConsent, audit trail and exports, suitable for Phase 1 through 3 and device investigations. You build the device-specific forms yourself in a free sandbox.

Set up your device study free

Free sandbox with every feature. No credit card, and you pay only when you go live with real participants.

Build your device study free