Clinical Development in medtech is not a generic planning exercise. It is the work of deciding what the device needs to prove, what the available data can already support, what still has to be generated, and how that logic should be documented.
At Qmed, Clinical Development sits between Regulatory Affairs and Clinical Affairs. It is the bridge between strategy and execution: the point where claims, risk, clinical evidence, study needs, and documentation are aligned early enough to avoid expensive rework later.
What Clinical Development means at Qmed
This function can include clinical development planning, clinical evidence strategy, clinical evaluation inputs, PMCF planning, literature strategy, protocol input, and broader evidence-linked documentation.
It also contributes to connected workstreams such as risk management, device description, labelling, and the wider technical documentation structure. The point is not to create more documents. It is to make sure the documents and decisions support the same regulatory story.
How Qmed supports here
We help teams review claims and intended purpose, understand evidence expectations, identify gaps, define clinical-development priorities, and connect those decisions to the documents and studies that follow.
This can be valuable early, when the evidence path is still open, and later, when a project has moved forward but the logic behind the documentation is starting to show weaknesses.
Annex XVI products without an intended medical purpose
For products covered by MDR Annex XVI, clinical development starts with a specific evidence question: what must the product prove when it may not have a medical purpose, but is still regulated under the MDR because of its function and risk profile?
Qmed helps manufacturers connect the Annex XVI regulatory pathway with the clinical evidence strategy. This can include reviewing intended use, claims, risk profile, existing data, possible clinical investigation needs, and how the evidence should be reflected in the clinical evaluation and technical documentation.
This is especially relevant for aesthetic and other non-medical products where the evidence logic should be clear before classification, notified body interaction, or market-access planning moves too far ahead.
Typical situations
Most often, medtech innovators come to us with one or more of the following challenges:
- the project is moving forward, but the evidence story still feels scattered
- claims, risk, and available data have not yet been brought into one clear plan
- a CER or technical file is being prepared before the underlying evidence logic is stable
- the team needs to decide whether more data is required, and if so what kind
- execution is being discussed before the upstream evidence questions are settled
Talk to Qmed
Tell us what your device needs to prove, what data you already have, and where the evidence path is still unclear.