September 16, 2026
September 11, 2026
August 2026 – Initially published on LinkedIn and expanded for the website
BSI, one of the leading European notified bodies for medical devices, has published an update of its best practice guidelines for MDR technical documentation submission now including a dedicated section on devices incorporating artificial intelligence or machine learning. A useful reference document that clarifies what evaluators concretely expect when reviewing a technical file.
A subject that affects a wide range of profiles
Technical documentation remains one of the most frequent pain points for manufacturers targeting the European market. Through my missions, I have supported very different profiles on this subject:
These situations share a common thread: gaps in technical documentation that, if not identified early, generate additional delays, unexpected costs, and a postponement of patient access to the clinical solutions concerned.
The most frequently identified gaps
Among the errors observed in the field, several come up regularly:
Class I device manufacturers are equally concerned
MDR technical documentation is not only relevant for manufacturers whose file is assessed by a notified body as part of the conformity assessment process. Class I device manufacturers who self-certify, have equally good reason to draw on these best practices.
Regular reviews of technical documentation make it possible to verify that it is properly aligned with the design and development process and with change management, and that it accurately reflects the current state of the product. It is an essential readiness in the event of an inspection by a competent authority.
This consideration takes on an additional dimension for manufacturers with large product ranges and multiple similar references. Building a technical documentation architecture that is compliant, optimised and agile — meaning easy to update following a change, a corrective action, a vigilance event or a post-market surveillance update — is an investment that facilitates every interaction with authorities and every evolution of the file over time. BSI’s guidelines provide a useful framework in this context for formalising this architecture effectively, without compromising compliance and while maintaining the traceability required.
→ Would you like to verify the robustness of your technical documentation or identify the adjustments needed before a submission or audit? The One Health Compliance Project Audit is designed for exactly this: a structured analysis of your file, a prioritised action plan, and concrete recommendations to move forward.
Sandra Dejean, PharmD – Founder of One Health Compliance
References: