Template: Intended Use (for Medical Devices Under MDD / MDR)

Template Download

This is a free template, provided by OpenRegulatory.

If you are a user of Formwork, our eQMS software, choose “QMS” on the top menu and “OpenRegulatory Templates” on the left menu, and then open the relevant folder to find this template ready to load into Formwork.

If, for some mysterious reason, you’re using a different QMS Software, you can also simply download this template – specifically, as Word (.docx), PDF, Google Docs or Markdown file. Scroll down for a preview!

The template license applies (don’t remove the copyright at the bottom).

Tired of copy-pasting? If you want to save time and edit these templates directly, you can use Formwork, our eQMS software. And if you’re looking for step-by-step instructions for filling them out, check out our Wizard 🙂

Don't Miss Updates to This Template
Subscribe to our newsletter and we'll keep you posted on which templates we've changed.

Questions? Still Lost in Regulation?

Good news! Our goal is to provide lots of stuff for free, but we also offer consulting if you need a more hands-on approach. We get stuff done really fast. Have a look!

Template preview

Mapping of Requirements to Document Sections

MDR ClassMDR SectionDocument Section
(All)Annex II, 1.1 a) – d), h), i)(All)
ISO 14971:2019 SectionDocument Section
IEC 62366-1:2015 SectionDocument Section


  • Name: <product name>
  • Version: <product version>
  • Basic UDI-DI: <insert UDI-DI, if/when available>

Intended Use

Describe the core medical functionality of your device and how it treats, diagnoses or alleviates a disease. Keep it high-level so that this description is true for as long as possible even when the device is updated.

Intended Medical Indication

Describe the condition(s) and/or disease(s) to be screened, monitored, treated, diagnosed, or prevented by your software. Importantly, also list exclusion criteria: Maybe patients with a certain diagnosis should not be using your device.


List anything that you want to explicitly exclude from your intended use.

Patient Population

Describe the patient population your software is intended to be used on. Note that this may overlap with the user profile (section below), but not necessarily. Your software could be used by physicians to diagnose diseases in patients, so in that case, they don’t overlap. Some ideas for characteristics to describe: Age group, weight range, health, condition(s).

User Profile

Describe the typical user of the software. Some ideas could be: Qualifications, prior training (for your software), technical proficiency, time spent using the software.

Use Environment Including Software/Hardware

Describe the typical use environment. What sort of devices is this running on? Does the software only run on one device or multiple devices? Is it loud and chaotic like in an emergency ward? How’s the lighting?

Also, add other software or hardware which is required by your device. Most commonly, apps require users to have a smartphone with a compatible operating system (iOS / Android).

Operating Principle

It’s kind of a stretch to describe the “operating principle” of software. I guess this makes more sense for hardware devices. In any case, I’d just generally state what sort of input goes in and what output comes out, e.g. you could be processing images and returning diagnoses.

The device is stand-alone software. It receives input from the user and outputs information.

Part of the Body / Type of Tissue Interacted With

The device is stand-alone software. It receives input from the user and outputs information. It doesn’t come in contact with tissue or bodily fluids.

Variants / Accessories

Describe variants and/or accessories of/to this device, if applicable. For typical stand-alone software of startups, this shouldn’t be applicable.

Template Copyright openregulatory.com. See template license.

Please don’t remove this notice even if you’ve modified contents of this template.

Template preview


Leave the first comment