Medical Device Submissions: Why Integration Across Disciplines Determines Success

Preparing a robust and compliant medical device submission file has become increasingly complex. Regulatory expectations continue to evolve, technologies are becoming more innovative, and notified bodies are placing greater emphasis on internal consistency and cross-disciplinary alignment. Over the past year, we have seen first-hand how an integrated, multidisciplinary approachcan either enable a smooth and efficient approval process or, when missing, lead to delays, additional costs, and avoidable findings.

Why a Multidisciplinary Approach Is No Longer Optional

To effectively support innovative medtech companies in developing their product and preparing a successful submission, close collaboration across multiple disciplines is essential. Each discipline operates under its own standards and regulatory expectations, including:

  • Technical documentation, including the Risk Management File (ISO14971) and bench testing (e.g. IEC60601-1)
  • Usability engineering, building a complete and compliant Usability Engineering File (IEC62366)
  • Clinical evaluation, consisting of the Clinical Evaluation Plan and Report in line with applicable MDCG guidance
  • Biological safety, including the Biological Evaluation Plan and Report (ISO10993-1)

In theory, each of these activities could be performed in isolation and later combined, particularly in the EU framework where the clinical evaluation ultimately justifies the acceptability of the device’s benefit-risk profile against the state of the art. In practice, however, this approach rarely works well.

Medical device development and regulatory submission are inherently iterative. Design decisions affect risk management, usability insights influence clinical justification, biological safety considerations interact with materials and processing changes, and all of these must be reflected consistently across the full technical documentation. This requires continuous interaction, regular alignment, and a shared understanding of the trade-offsbetween the involved disciplines.

This challenge becomes even more pronounced when working with novel technologies or relatively inexperienced teams, or when responsibilities are split across multiple external parties with limited coordination.

Hard learned Lessons from Practice

Case 1: Integrated Technical, Usability, and Clinical Support With Fragmented Biocompatibility Input

For one recent client, we were brought in relatively late, after most development was already done, to complete the technical file, including closing usability gaps and finalizing the clinical evaluation. Biological evaluation and re-sterilization validation had already been outsourced to a large full-service provider.

Within our scope, technical, usability, and clinical activities were fully integrated within a single team and contract. This allowed us to quickly align updates across the Risk Management File, Usability Engineering File, and Clinical Evaluation as new insights emerged.

The collaboration with biocompatibility and sterilization validation was more challenging. The initial Biological Evaluation Plan concluded that the device did not need to contact the patient to function but there might be accidental transientpatient contact and that no materials were inherently suspect, yet it still recommended cytotoxicity testing “to be safe.” Based on the overall risk profile, we were able to push back and avoid unnecessary testing, preventing avoidable costs for the client.

More critically, internal misalignment within the biocompatibility provider resulted in the Biological Evaluation Report explicitly excluding the impact of re-sterilization, contrary to the requirements of ISO 10993-1. While this can be addressed elsewhere in the documentation, the corresponding justification was missing in the re-sterilization report written by another team in the same company. In the end, this resulted in questions during notified body review that were addressable but could have been prevented.

Despite these issues, the integrated approach across risk management, usability, and clinical evaluation proved highly effective. The technical file review was closed after a single round of questions, with no findings related to inconsistencies between these core elements. From submission to approval, the process took less than three months.

Case 2: Technical and Clinical Support Split Across Separate Consultancies

In another case, we supported a client only on the technical side, including risk management, requirements definition, and verification. This was a legacy product with a long market history under the MDD, but with limited existing technical documentation. A separate consultancy had already been contracted to perform the clinical evaluation.

The client’s internal team was small and inexperienced, and we had no direct interaction with the clinical consultancy. It was unclear what technical or risk management information was shared, and we were not involved in the final consistency review prior to submission.

The notified body feedback focused on insufficient discussion of risk management, usability, and bench testing within the clinical evaluation. This outcome was frustrating for all parties involved and highlights a common issue: even highly competent clinical experts cannot produce a robust and compliant clinical evaluation if they lack the right technical inputs or if those inputs are not aligned. This is common with inexperienced development teams, since they don’t know what questions to ask and input to provide.

Case 3: Fully Integrated Support With a Closely Aligned Biocompatibility Partner

For a third client, we have been involved from the outset, providing integrated technical, usability, and clinical support. For biological evaluation, we worked closely with our preferred biological evaluation partner, Chorley Consulting Ltd: a smaller team of seasoned biocomp experts that can create independent and objective biological evaluation plans and reports. If needed they can also arrange the testing, but they are not incentivized to recommend unnecessary laboratory work.

The device is a surgically invasive product involving multiple materials and processing chemicals. Because we were deeply involved in the technical design and risk management for the product while at the same time we understood which inputs are for the biological evaluation. This allowed us to initiate the Biological Evaluation Plan at the right moment and collaborate proactively with the biocomp experts to ensure the right inputs were in place.

Our preferred way of working is to take ownership of the full regulatory narrative, even when external experts are involved. By understanding what each discipline needs from the others, we ensure efficient collaboration, minimize unnecessary costs, reduce regulatory risk, and support smooth and predictable approvals.

Conclusion: Integration Drives Better Outcomes

These examples illustrate a clear pattern. Successful medical device submissions are rarely the result of isolated excellence in individual disciplines.They depend on strong multidisciplinary collaboration, shared accountability, and a holistic understanding of how technical, usability, clinical, and biological considerations interact.

For medtech companies, especially those developing innovative technologies, investing in an integrated, multidisciplinary support model is not just a regulatory necessity. It is a strategic choice that directly impacts timelines, costs, and the likelihood of a successful approval.

Erik 02

Erik van Dijk

Managing Partner

Don’t hesitate to ask us your questions.

Drop an e-mail or contact us via LinkedIn

This website uses cookies to ensure you get the best experience on our website. If you want to get more information about this, please view our privacy policy page.