Medical device projects can go surprisingly far before one of the most fundamental questions has been answered properly:
What exactly is the device intended to do, for whom, and under which conditions?
For an early-stage company, an unclear intended purpose can send product development, classification, testing and clinical planning in the wrong direction from the beginning.
But this is not only a startup problem.
Established manufacturers face the same question when products evolve, claims change, new patient populations are considered, software functionality is added, new markets are entered, or legacy documentation is brought up to current regulatory expectations.
The intended purpose is therefore not simply a sentence written at the beginning of a development project.
It is one of the anchors that should keep the product, evidence and regulatory documentation aligned throughout the device lifecycle.
What does intended purpose actually define?
Under the EU MDR, the intended purpose is the use for which the manufacturer intends the device, based on information supplied on the label, in the instructions for use, in promotional or sales materials or statements, and as specified in the clinical evaluation.
This is important because intended purpose is not confined to one section of the technical documentation.
It needs to remain consistent across the way the device is described, developed, evaluated and ultimately presented to users and customers.
The terminology can sometimes create confusion as well. In MDR guidance, “intended use” is generally considered to have the same meaning as “intended purpose”, while concepts such as the indication describe more specifically the clinical condition the device is intended to address.
In practice, a useful intended purpose usually needs to give enough information to understand questions such as who the device is for, what medical purpose it serves, who uses it, where or under what conditions it is used, and what clinical effect or function is expected.
Getting those fundamentals clear has consequences far beyond wording.
For new devices, it sets the direction
When a product is still being developed, the intended purpose influences many of the decisions that follow.
Classification is one obvious example. The device’s intended medical purpose, duration and nature of use, invasiveness, anatomical location and other characteristics can determine which MDR classification rules apply.
The same principle carries into software. For medical device software, the intended purpose is fundamental to determining whether the software qualifies as a medical device and how it should be classified. MDCG guidance explicitly uses the manufacturer’s intended purpose as a central part of that assessment.
But classification is only one consequence.
The intended purpose also affects product requirements, risk management, usability, verification and validation, clinical evaluation and, where needed, clinical investigation.
If the device is being developed without a sufficiently clear clinical starting point, teams can end up making technically reasonable decisions that do not support the product they eventually want to place on the market.
That can be expensive to correct later.
Established products need the same attention
For an established manufacturer, the intended purpose may feel settled.
The device has been on the market for years. The technical documentation exists. The IFU has already been approved internally countless times.
But products rarely remain completely static.
Software functionality is added. Accessories change. A product begins to be used in a broader patient population. New clinical evidence becomes available. Marketing language evolves. A distributor identifies an opportunity in a new clinical setting. The company begins planning entry into another market.
At some point, the product that exists today may no longer be described as clearly by wording originally created several years ago.
That does not mean the intended purpose should be constantly rewritten. Changes to it can have significant regulatory consequences.
It does mean manufacturers should periodically ask whether the device, its evidence and the way it is being communicated still tell the same story.
Claims need to stay within the regulatory story
This is one of the areas where established companies can encounter difficulties without making any formal change to the intended purpose.
The MDR definition specifically connects intended purpose not only to the label and IFU, but also to promotional and sales materials or statements.
That makes the relationship between regulatory documentation and commercial communication particularly important.
Over time, marketing language can naturally become more ambitious.
A technically accurate statement about what the device does can gradually turn into a stronger statement about what it achieves clinically. A website may describe benefits more broadly than the IFU. Sales material developed for a specific customer group may introduce wording that is not clearly reflected in the clinical evaluation.
None of these situations necessarily begins as a regulatory project.
But the cumulative result can be a gap between what the company says the device does and what the available evidence actually supports.
An intended-purpose review can therefore be useful not only during product development but also when reviewing claims, websites, brochures and other customer-facing material.
Clinical evaluation depends on getting the intended purpose right
The relationship with clinical evaluation is especially important.
Under the MDR, the depth and extent of clinical evaluation must be appropriate to the device’s nature, classification, intended purpose and risks, as well as the manufacturer’s claims.
That means it is difficult to define what constitutes sufficient clinical evidence until the intended purpose is sufficiently clear.
- What clinical benefit is expected?
- For which patients?
- Under what clinical circumstances?
- Which claims need to be demonstrated?
- What outcomes would meaningfully show that the device performs as intended?
These questions influence literature searches, state-of-the-art analysis, equivalence assessments, PMCF planning and clinical investigations.
This also connects directly with clinical investigation design. MDR guidance recommends looking at documents including the IFU, labelling, Clinical Evaluation Plan and Clinical Evaluation Report when assessing whether a planned clinical use falls within the manufacturer’s intended purpose.
If the intended purpose is vague, the clinical evidence strategy can become vague as well.
If it is unnecessarily broad, the manufacturer may create an evidence burden that is much larger than expected.
Risk management needs the same clinical starting point
Risk management also depends on understanding how the device is intended to be used.
Identifying hazards without a clear intended purpose can leave important questions unanswered.
Who will interact with the device? In what environment? For how long? On which patient population? What happens if the expected clinical performance is not achieved? What reasonably foreseeable misuse needs to be considered?
A product used by a healthcare professional in a controlled hospital environment presents a different use scenario from one intended for unsupervised home use.
Similarly, expanding a product into a different population or clinical setting may introduce risks that were not central to the original assessment.
The intended purpose therefore helps define the context in which safety and performance are evaluated.
Product changes should trigger the question again
Not every design change affects the intended purpose.
Changing a supplier, updating packaging or replacing a technically equivalent component may have no effect on it at all.
Other changes deserve closer attention.
A new indication, different anatomical site, expanded patient population, different intended user, additional software functionality or new clinical claim may alter the scope of the device’s intended use.
When changes like these are considered, the question should not only be:
Can we technically make this change?
It should also be:
Does this change what we are claiming the device is intended to do?
If the answer is yes, the impact may extend into classification, clinical evidence, risk management, usability, verification and validation, technical documentation and potentially conformity assessment activities.
This is why intended purpose belongs within change-control and regulatory-impact discussions for mature products as much as it belongs in early product development.
Market expansion can expose weaknesses in the original definition
Entering another market can also reveal ambiguity that was previously easy to overlook.
A manufacturer may have successfully built its EU documentation around a particular intended purpose, only to discover during FDA planning that the indications for use, patient population or technological characteristics need to be described much more precisely for the US regulatory strategy.
The same can happen in reverse.
This does not mean regulatory wording should be made identical across every jurisdiction. The legal frameworks and terminology differ.
But the underlying product concept should remain coherent.
If the company struggles to explain consistently what the device does, for whom and why, that is often a sign that the intended purpose needs closer examination before additional regulatory documentation is built around it.
Too broad and too narrow can both cause problems
Defining the intended purpose is partly an exercise in finding the right level of precision.
A very broad intended purpose may initially feel commercially attractive because it appears to preserve flexibility.
But broader claims can also expand the clinical evidence, risk-management and verification questions the manufacturer needs to address.
At the other extreme, wording that is unnecessarily narrow can constrain how the product can legitimately be positioned or used later.
The objective is not to make the statement as broad or as narrow as possible.
It is to describe the product accurately enough that the rest of the regulatory strategy can be built around it.
That requires input from more than one function.
Clinical experts understand the medical need and patient population. Development teams understand the technology. Commercial teams understand the intended market. Regulatory and quality specialists understand how those decisions translate into classification, evidence and documentation.
The strongest intended-purpose definitions usually emerge when those perspectives are brought together early.
A useful point to revisit throughout the lifecycle
For a startup, intended purpose is one of the first regulatory questions that should be answered before development progresses too far.
For an established manufacturer, it becomes something slightly different: a reference point against which product changes, new claims, clinical evidence and market expansion can be assessed.
In both cases, the value is the same.
A well-defined intended purpose gives the organisation a clearer basis for deciding what needs to be developed, what needs to be demonstrated and what can ultimately be claimed about the device.
It helps classification make sense. It gives clinical evaluation a defined question to answer. It creates context for risk management and testing. And it gives different teams a common understanding of the product they are actually bringing to market.
When that foundation is unclear, the uncertainty tends to spread into everything built on top of it.
At MDS, we support manufacturers with intended-purpose definition and review as part of regulatory strategy, product development, classification, clinical evaluation and technical documentation work. This can be particularly useful early in development, but also when an existing product, its claims or its target markets are changing.
If the intended purpose of your device is still being defined, has evolved over time, or is creating uncertainty elsewhere in the regulatory documentation, we can help establish a clearer clinical and regulatory foundation.
You can contact us at sales@mdsfinland.com or via Book a Meeting.
