Forum

Notifications
Clear all

When meeting the Spec is not Enough: Verification vs. Validation

7 Posts
7 Users
0 Reactions
108 Views
(@dcapera)
Posts: 50
Trusted Member
Topic starter
 
[#1649]

The regulation defines verification as confirming that 'specified requirements' are fulfilled, and design validation as confirming that device specifications conform with 'user needs and intended use'. Where could a team pass verification but still fail validation, and what does that tell us about how carefully a design input must be written?


 
Posted : 04/11/2026 5:35 am
(@james-olson)
Posts: 33
Eminent Member
 

The fundamental difference between the definitions of design inputs and design specifications leave plenty of opportunity for an instance where verification is passed but validation is failed. An example that comes to my mind would be a heart rate monitor that meets all dimensional specifications, but is extremely loud and disrupts the patient. This quality that affects the patient negatively is not accounted for by the specifications, and instead depends on the qualitative requirements (inputs). This instance highlights the importance of taking into account both numeric specifications and the user needs when proceeding through the design process. This example also tells us that both a DID and DSD must very clearly state the requirements of the medical device (for the inputs or specifications respectively). Doing so allows the verification and validation processes to catch any parameters that are different than what is desired, or lead to an undesired effect.


 
Posted : 04/11/2026 5:31 pm
 chk9
(@chk9)
Posts: 6
Active Member
 

I think both verification and validation are important and one cannot exist without the other. Verification goes in hand with validation as if its not in the proper technical specifications it may not work properly. Some things may need to be a specific size to work. Going to your point of how well a design input is written also raises the question of who are the ones providing the input? Are patients or healthcare professionals involved in the design process and is the validation process conducted with real use scenario and environments in mind? A device can't be considered complete if it only operates in a lab setting. It should be usable when it needs to be. The goal of verifying and validating is to create a device that is reliable technically and practical for the intended users. It brings up the question of how can someone design and ensure the product will provide both practicality and functionality for the intended users. 


 
Posted : 06/11/2026 5:29 pm
 aca
(@aca)
Posts: 72
Trusted Member
 

There can be situations where a medical device could pass verification but fail validation, like an infusion pump that delivers medication at the correct flow rate but has a challenging user interface. Even though the pump does meet the technical specification, the nurses might accidentally select the wrong settings or function. Through this case it shows that a device can function exactly as designed but still create risks for the people using it due to its complexity. Therefore, this is the reason usability and human factors should be considered early in the design process instead of only during final testing.
Furthermore, this case also shows how it's essential to write design inputs that are specific and measurable instead of just stating that a device is easy to use or ergonomic. Engineers should determine requirements for how quickly users should complete certain tasks or how they can recognize warnings. Therefore, this would make it simpler to evaluate whether the device meets the user needs.


 
Posted : 08/11/2026 5:47 pm
(@afg28)
Posts: 32
Eminent Member
 

I think if the product met the design verification specifications but did not meet design validation, the design inputs were poorly defined to begin with. Specifications are made based off of the original design inputs. If the project team interpreted the inputs from the user/customer and drafted specifications around them, there should be little risk of failing design validation. Often times project teams will also meet with key opinion leaders in the market regularly to ensure the products continuously meets their needs in a fast paced competitive market.


 
Posted : 08/11/2026 8:40 pm
(@alina-kolenovic)
Posts: 33
Eminent Member
 

Design verification and design validation are two incredibly important processes that work in tandem to ensure successful device design and future manufacturing. Device verification focuses on the technical aspect of the design and how well it meets previously set requirements (drawings, dimensions, etc.) On the other hand, design validation focuses on the functional performance of the device and how well it can meet the identified user needs. Although both are necessary components of device design, they are inherently different. There are many instances where a team could pass verification but not validation, and vice versa. The struggle is ensuring that a device passes both types of testing. Take a glucose monitor as an example. The specification of the device is that it has to have an accuracy of 95% or higher in measuring glucose levels. The customer need is that it should be easy for users to utilize in their daily life. A company could make a device that meets all of the outlined requirements, but users struggle to use it because of a small display with small writing and confusing instructions. Poorly written design inputs can make it so that a device achieves the specified requirements, but does not pass validation. As a result, medical device companies must make sure to balance their considerations of both design specifications and customer needs and carefully write their design inputs. Writing clear, detailed, and understandable design inputs is key to developing a device that achieves both verification and validation. The design inputs are the foundation of a product's design, so inputs that are confusing, incomplete, or conflict with other inputs can lead to failures in later stages and lead to resource losses. 


 
Posted : 08/11/2026 8:43 pm
(@grs29)
Posts: 30
Eminent Member
 

I think one of the biggest challenges is that engineers can sometimes focus too much on meeting the technical requirements that they overlook how the device will actually be used in a real-world environment. From speaking to engineers in the industry, I've learned that this becomes a real challenge in many teams. For example, a medical device can meet all its required specifications but still be difficult for a doctor to operate or for a patient to use independently at home. 

This is why design inputs should also consider who will be using the device, where it will be used, and under what conditions. One approach that could help is incorporating feedback from patients or users of the devices throughout the development process rather than waiting for the final validation stage. This could help identify any issues early in the process, when design changes are easier and less costly to implement. I also know that there getting feedback comes with its own challenges, specifically in translating subjective comments, such as comfort or ease of use, into measurable design inputs that engineers could actually verify. Finding a balance between verification and validation is essential to ensuring a device is technically functional, practical, and safe for users. 


 
Posted : 08/11/2026 9:02 pm
Share: