Medical device design and prototyping: innovations that make devices safer to use

Good medical device design helps people complete essential tasks safely, rather than simply adding another feature. Human factors engineering keeps that focus by examining the intended users, their environments and how they interact with a product. This guide shows how to connect that approach with medical device prototyping, digital development tools, risk management and practical design decisions (FDA).

How can medical device usability improve without compromising safety?

Medical device usability improves through a repeatable process: understand the intended users, identify use-related risks, develop suitable interfaces and evaluate whether people can perform essential tasks. Safety and usability should inform the same design decisions rather than compete for attention. FDA guidance places safe, effective use by intended users at the centre of human factors engineering (FDA).

Start by challenging the assumption that a technically correct product is straightforward to operate. FDA identifies lighting, noise, user capabilities and experience as relevant design considerations, so a control that looks clear on a designer's monitor needs evaluating in its intended setting (FDA).

For an illustrative home-monitoring device, ask whether someone can tell a completed measurement from an interrupted one. Consider separate completion messages, clear next steps and confirmation that a result has been saved. These are design hypotheses to test, not evidence that a particular interface is already safe.

The useful innovation is the improvement you can demonstrate, not the novelty of the feature.

Turn user research into testable design requirements

User-centred design begins with understanding the work around a device, not just the moment someone presses a button. Include preparation, unpacking, setup, cleaning, storage and disposal in your research plan. FDA's description of the user interface covers packaging, labels, controls, displays and instructions, so all of these interactions matter for usability (FDA guidance).

For healthcare product design, organise research around specific decisions:

• Users: Identify who prepares, operates, maintains and troubleshoots the device. Avoid treating clinicians, patients and carers as interchangeable.
• Environments: Investigate space, lighting, distractions, connectivity and the availability of assistance.
• Tasks: Observe sequences of actions, including handovers and recovery after interruptions.
• Evidence: Record what happened, the likely explanation and which requirement or design decision needs investigation.

Translate observations into requirements that can be evaluated. Instead of writing "the display must be intuitive", specify the information users need to identify, the circumstances in which they need it and the evidence that will demonstrate success.

For example, investigate whether users recognise the active operating mode before starting treatment. Keep the requirement separate from the proposed solution: an extra confirmation screen might help, but it should not become mandatory before alternatives have been explored.

Medical device prototyping: where digital tools and simulation add value

Digital tools add value when they answer defined development questions and make design alternatives easier to compare. Computational simulation can complement physical evidence, while interactive prototypes let you explore proposed interfaces. Where computational models support regulatory submissions, FDA recommends a risk-informed assessment of their credibility (FDA modeling and simulation).

Choose the tool after identifying the uncertainty. Use a clickable prototype to investigate navigation, for instance, rather than building production software before the workflow has been explored. For questions about mechanical performance, define the model's purpose, assumptions and supporting evidence before relying on its output. For the physical side, see our guide to the medical device prototyping process, stage by stage.

A practical medical device prototyping workflow looks like this:

1. Define the question: Identify the decision the prototype or model must support.
2. Choose the representation: Use the level of detail the question needs, rather than maximum visual realism.
3. Connect the evidence: Record the design version, assumptions, results and resulting changes.
4. Check the limits: Decide what still needs physical testing or evaluation with representative users.

Avoid attaching a universal time-saving percentage to this approach. Set project-specific measures instead, such as how quickly a design question is resolved or how many unresolved issues reach the next review.

Design connected medical devices around understandable states

For a connected product, evaluate the device, embedded software, companion app and supporting services as one user journey. FDA's cybersecurity guidance covers device design, labelling and submission documentation for products with cybersecurity risk, so security belongs alongside the experience you are designing (FDA cybersecurity guidance).

Consider a hypothetical monitoring system that loses its network connection. The design review should distinguish between taking a measurement, storing it locally and transmitting it successfully. Avoid assuming that one reassuring symbol communicates all three states.

Test proposed messages for practical understanding. Ask participants what has happened, what remains possible and what they would do next. Include interrupted pairing, expired sessions and unsuccessful updates where they are relevant to the intended system.

Medical device website design deserves a related but separate review. If a website supports product selection, onboarding or support, check that users can identify their model and find the right information. Keep commercial messaging separate from safety instructions, and decide who reviews content when the product changes. These are useful content-governance questions, not a substitute for evaluating the device itself.

Build regulatory evidence into everyday development

Regulatory planning should establish which requirements apply to your product, its intended purpose and its target markets. For US manufacturers within scope, FDA's Quality Management System Regulation became effective on 2 February 2026 and incorporates ISO 13485:2016 by reference, so teams should use the current framework rather than rely solely on legacy procedures (FDA QMSR).

Keep the roles of the relevant standards distinct. ISO 13485 addresses quality management systems, ISO 14971 addresses medical device risk management, and IEC 62366-1 specifies a process for analysing, specifying, developing and evaluating usability as it relates to safety. They are related, but not interchangeable.

A useful working record makes the reasoning behind decisions easy to follow:

Use this structure to support traceability, not just to fill in documents before submission. At each review, follow one important task through the records. If the team cannot explain why a control exists or what supports it, investigate the gap before moving on.

Separate learning from validation

Early evaluation and final validation serve different purposes. Formative evaluation investigates a developing design and informs improvements. Human factors validation evaluates the final interface with representative users, critical tasks and realistic conditions. FDA also recommends that validation training approximates what actual users would receive (FDA guidance).

Plan early prototype sessions around specific uncertainties rather than a general request for feedback. For a proposed control layout, observe task completion before discussing preferences. Record hesitations and misunderstandings, then investigate their causes instead of immediately adding instructions.

Before validation, review whether the interface, packaging, instructions and training reflect the intended product. Agree how observations will be captured and analysed, and avoid coaching participants through difficult steps. Where problems emerge, investigate what the design contributed rather than treating participant confidence as proof of success. If you need matching units for a study, see our guide to small-batch production for medical devices.

The distinction matters commercially as well as technically: FDA notes that interface flaws found during formative work can be easier and less expensive to fix than those discovered during validation.

Give multidisciplinary teams shared decisions

Medical device product design needs clear ownership across disciplines. Bring human factors, engineering, software, quality, regulatory and manufacturing perspectives into decisions that cross their boundaries. Rather than asking each function to approve a finished proposal, give the group a defined problem and the evidence available so far.

If you are choosing a design or prototyping partner, ask how their team will connect research findings to requirements and test evidence. Request an explanation of change control, responsibilities and handovers, and check that they can work within your quality system. An impressive prototype does not by itself show readiness for manufacture or submission.

Set decision gates around evidence: what has been learned, what remains uncertain and who will resolve it. That keeps collaboration focused on the product rather than the volume of activity reported.

Make the next improvement demonstrable

Start your next design review with one essential user task. Examine the evidence, identify the unresolved risk and choose the smallest useful experiment to inform the decision. That gives medical device design and prototyping a practical direction: clearer interactions, better-supported choices and a development record that explains why the design deserves confidence.

Medical device design and prototyping: questions

What is human factors engineering in medical device design?

It is the process of examining intended users, their environments and their interactions with a device so that essential tasks can be performed safely and effectively.

Why prototype a medical device early?

Early prototypes let you investigate specific uncertainties, such as navigation or control layout, while changes are still easier and less expensive to make than at validation.

What is the difference between formative evaluation and validation?

Formative evaluation investigates a developing design and informs improvements. Validation evaluates the final interface with representative users, critical tasks and realistic conditions.

How do ISO 13485, ISO 14971 and IEC 62366-1 differ?

ISO 13485 covers quality management systems, ISO 14971 covers risk management, and IEC 62366-1 covers the usability engineering process as it relates to safety.

Talk to us about your medical device prototypes

At Complete Fabrication we make appearance models, functional prototypes and trial batches for medical device teams from our workshop near Cambridge. Send your CAD files, the quantity and the stage you are at, and we will recommend a process and confirm the cost and timeline. Call +44 1223 836837, email info@compfab.co.uk, or contact us. See also our medical device prototyping service.

References

1. US FDA. Human factors considerations. https://www.fda.gov/medical-devices/human-factors-and-medical-devices/human-factors-considerations
2. US FDA. Human factors and medical devices. https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance/human-factors-and-medical-devices
3. US FDA. Applying Human Factors and Usability Engineering to Medical Devices. FDA guidance (PDF)
4. US FDA. Modeling and simulation at FDA. https://www.fda.gov/science-research/about-science-research-fda/modeling-simulation-fda
5. US FDA. Cybersecurity in medical devices: quality system considerations and content of premarket submissions. https://www.fda.gov/regulatory-information/search-fda-guidance-documents/cybersecurity-medical-devices-quality-management-system-considerations-and-content-premarket
6. US FDA. Quality Management System Regulation (QMSR). https://www.fda.gov/medical-devices/postmarket-requirements-devices/quality-management-system-regulation-qmsr