The Role of User Needs in Design Controls

by | Jan 28, 2022 | Compliance, Consulting Group, Design Controls, QMS, Quality, Quality Systems, Regulatory, Standardization, Standards

Engaging in medical device product development requires establishing and documenting design controls. The FDA requires design controls for almost all medical devices (except for a select few Class I devices). The very foundation of design controls is the user’s needs as they start the design control process and are required to complete verification and validation of the finished device.

Defining user needs helps prevent drift in the design controls process by helping to focus on the development of the product specifically for the specified user needs. Here are some tips that may help when trying to determine your user needs:

  1. Start with high-level speculations about user needs. However, it’s essential to continue digging deeper into the user group and understanding what the user wants.
  2. Research. Journal articles, analysis of existing products, academic studies, and interviews are great ways to investigate the user requirements.
  3. Document! Documentation of clearly defined user needs is a requirement for design controls and helps further along when user needs are translated into design inputs.

The user needs are developed first and then translated into design inputs, design processes, and design outputs. The reasoning behind creating user needs first and building off of them for the entire design controls process is to have the ability to prove the medical device does what it claims to do and is suitable for the intended purpose. As a part of documenting the user needs, it is also imperative to define both the intended use and the indications for the use of the medical device.

  • Indications for use: describe the specific purpose of the device and what it primarily does.
  • Indications for use include outlining the situations, diseases/conditions, or circumstances where the product may be used.

User Needs are usually determined first and then translated into the necessary design inputs. It is imperative to decide what the user needs for the specific device during this translation, as this will be the design input. The design input needs to be precise and have clear details on how the device will end. For help with design controls or other QMS or regulatory projects, EMMA International can help. Contact us today at 248-987-4497 or

Alexis Ferrier

Alexis Ferrier

Alexis is a Technical Writer at EMMA International. She has research and development experience in both device and drug products. Additionally, Alexis has experience in quality assurance, quality control, regulatory requirements, and international compliance. She holds a Bachelor of Science in Chemistry from Michigan Technological University.

More Resources

FDA Adverse Event Reporting 

FDA Adverse Event Reporting 

When reporting an Adverse Event to the Food and Drug Administration (FDA) the best method is to utilize the FDA Adverse Event Reporting System (FAERS). FAERS is a database that contains adverse event reports, product quality complaints that led to an adverse event, and medication error reports1. All FAERS reports are easily accessible to the public. 
De Novo Classification

De Novo Classification

A device can be registered for the De Novo pathway if there is evidence of the safety and effectiveness of the device and there is not a previously legally marketed predicate device1. When determining if your device can go through the De Novo process there are two pathways available to determine the device classification.
Abbreviated 510k submission

Abbreviated 510k submission

There are three types of 510K, Premarket Notifications, which can be submitted to the Food and Drug Administration (FDA) traditional, abbreviated, and special. Abbreviated and Special 510K submissions can be utilized when the submissions meet the certain factors presented by the FDA. When submitting an abbreviated 510K the submission must include the elements that are identified in 21CFR 807.87 for the information required in a premarket notification submission.

Ready to learn more about working with us?

Pin It on Pinterest

Share This