MTL-102: Intended Purpose, Users and Use Environments

What you will learn

By the end of this topic, you should be able to distinguish intended purpose from indications for use, define the patient population and intended users, characterise relevant use environments, and explain how these decisions shape the complete development and evidence strategy.

Why intended purpose comes first

The intended purpose is not a description written after the product has been designed. It is a controlled strategic definition of the medical purpose the manufacturer claims for the device. In the EU, the manufacturer's labelling, instructions, promotional or sales materials and clinical evaluation collectively communicate that purpose. In the US, intended use and indications for use similarly influence whether the product is a device, its classification and its regulatory pathway.

A vague statement leaves engineering teams to make different assumptions. A statement that is prematurely broad can enlarge the patient population, environments, risks, clinical evidence and regulatory burden. A statement that is artificially narrow may not describe the product the business actually intends to market.

The central principle

Define the intended purpose early enough to guide development, then control it as a lifecycle decision. Every claim should be supported by requirements, risk controls, usability work, verification, validation and clinical or performance evidence.

Four connected concepts

Intended purpose

The medical purpose and general function claimed by the manufacturer: what the device is intended to diagnose, prevent, monitor, predict, prognose, treat, alleviate or otherwise achieve.

Patient population

The people for whom the device is intended, including relevant condition, age, anatomy, physiology, disease stage, inclusion criteria and exclusions.

Intended users

Every person expected to interact with the device or its information: specialists, general healthcare professionals, technicians, carers, patients, service staff or administrators.

Use environments

The physical, technical, organisational and social conditions in which the device is stored, prepared, operated, cleaned, serviced, transported and disposed of.

These concepts should agree but should not be collapsed into one sentence so dense that nobody can review it. A short approved intended-purpose statement can be supported by controlled user, population and environment profiles.

Building a useful intended-purpose statement

A practical statement should answer the following questions at an appropriate level of specificity:

What is the device? Identify the device or system without relying on a brand name alone.
What does it do? State the medical purpose and principal function without promising unsupported outcomes.
For which condition or clinical situation? Define the indication or healthcare need.
For whom? Identify the target patient population and material exclusions.
By whom? State the intended user groups and necessary competence or training.
Where? Identify the intended environments and important boundaries.
For how long and how often? Address duration, frequency, contact and reuse where these affect safety or evidence.
With what? Identify essential accessories, medicinal products, software, networks or other devices on which the intended operation depends.

The statement should describe the product the organisation is prepared to develop, validate, support and promote. Commercial language, regulatory documentation and engineering assumptions must not silently describe different products.

Define intended users as real populations

“Healthcare professional” and “patient” are usually too broad to drive safe design. User profiles should consider education, clinical or technical competence, training, language, sensory and physical abilities, familiarity with technology, personal protective equipment, workload and the consequences of interruption or error.

Separate users by the tasks they perform. A patient may administer therapy; a nurse may prepare and supervise it; a pharmacist may configure a medicinal product; a service engineer may access diagnostic functions; and an administrator may manage identities and connectivity. Each role has different information needs, permissions, foreseeable errors and cybersecurity exposure.

Do not confuse user with patient

The patient receives the medical benefit or bears the clinical risk. The user interacts with the device. They may be the same person, but often they are not.

Characterise the complete use environment

The name of a location is only the beginning. “Hospital”, “home” or “ambulance” does not define the conditions the design must withstand. Consider:

Physical conditions

Temperature, humidity, altitude, lighting, noise, vibration, shock, ingress, contamination, cleaning agents, storage and transport.

Electrical and electromagnetic conditions

Power quality, grounding, batteries, electromagnetic disturbances, nearby transmitters and availability of backup power.

Digital environment

Networks, bandwidth, latency, cloud availability, mobile platforms, account management, time synchronisation, interoperability and security controls.

Human and organisational conditions

Staffing, supervision, interruptions, time pressure, shared equipment, handovers, training, maintenance and access to technical support.

A device intended for home use may be operated by a trained professional or a lay person, indoors or outdoors, with limited technical support. A device intended for emergency medical services may face transport, vibration, weather and rapidly changing clinical conditions. The environment therefore changes both the applicable standards and the evidence needed.

What these definitions drive

REG

Qualification, classification and market pathway

The claimed medical purpose and indications influence whether the product is regulated as a medical device, which classification rules apply and what submission or conformity-assessment route is needed.

RISK

Risk management

Users, patients, environments, duration, interfaces and reasonably foreseeable misuse define hazardous situations, exposure and appropriate risk controls.

USE

Usability engineering

User profiles, use environments, tasks and use scenarios shape the user interface, critical tasks, formative evaluation and usability validation.

REQ

Design inputs and architecture

Environmental limits, user capabilities, performance claims, accessories and external systems become testable requirements and interface constraints.

V&V

Verification and validation

Verification tests the specified conditions and limits. Validation uses representative users, products and environments to show that user needs and intended use are achieved.

LIFE

Labelling and post-market control

Instructions, training and promotion must remain consistent with the approved purpose. Complaints and field use reveal whether actual users and environments differ from the assumptions.

Worked example: a connected injection aid

Consider a reusable electronic accessory that detects events during self-injection and provides guidance through a mobile application. “Helps patients inject” is not sufficient. The team needs to decide whether the system guides preparation, confirms completion, records adherence or influences a clinical decision; which compatible injector and medicinal-product configurations are supported; and whether connectivity is essential to the medical function.

The patient population may include adults who self-administer a prescribed therapy, while excluding people unable to operate the system without assistance. Users may include patients, carers, healthcare professionals, trainers, service staff and system administrators. Environments may include the home, travel, clinics, storage and transport, with variable lighting, noise, connectivity, phone configuration and access to support.

Those decisions drive sensor performance, feedback, accessibility, environmental testing, mobile-platform support, authentication, offline behaviour, data integrity, training and validation scenarios. Broadening the purpose later—for example to paediatric use, a new injector family or clinical decision support—is a design and regulatory change, not simply revised marketing text.

Practical review checklist

The medical purpose and claimed benefit are clear.
The device, system boundary and essential dependencies are identified.
The condition, indication and patient population are sufficiently specific.
Intended users are separated by role, task, competence and training.
Use environments cover preparation, operation, storage, transport, cleaning, service and disposal as applicable.
Duration, frequency, body contact and reuse are defined where relevant.
Contraindications, exclusions and important limitations are visible.
Foreseeable misuse and off-label pressures have been considered without redefining them as intended use.
Claims, labels, instructions, clinical plans and promotional language are consistent.
Regulatory, clinical, engineering, usability, risk and commercial stakeholders have approved the same controlled baseline.
Each material element can be traced to requirements, risks and planned evidence.
A change process is defined for proposed expansion of users, populations, environments or claims.

Common misconceptions

“Intended purpose is a regulatory sentence.”

It is a product-definition decision with regulatory consequences. Engineering, clinical, commercial and lifecycle plans all depend on it.

“Anyone can use it if the interface is simple.”

Ease of use does not remove the need to define user populations, training, permissions and validation evidence.

“Home use just means lower environmental specifications.”

Home use may mean less supervision, more variable power and connectivity, children or pets nearby, storage extremes and limited access to support.

“We can broaden the claims after testing.”

New populations, purposes or environments can change risks, requirements, evidence, classification and regulatory obligations.

“Foreseeable misuse becomes intended use.”

No. Risk management must address reasonably foreseeable misuse, but that does not make the misuse an approved purpose or claim.

Seven things to remember

Define intended purpose before detailed design, not after it.
Keep the purpose, patient population, users and environments distinct but consistent.
Describe user groups through their real tasks and capabilities.
Characterise environmental conditions rather than naming locations alone.
Make claims consistent across technical, clinical, regulatory and commercial material.
Treat expansion of purpose, population, users or environment as controlled change.
Trace every important assumption into risks, requirements and objective evidence.