Video: Technical Documentation for Medical Devices | Duration: 3587s | Summary: Technical Documentation for Medical Devices | Chapters: Welcome and Introduction (21.055s), Speaker Introduction (121.84s), NSF Introduction (248.695s), Service Offerings Overview (372s), Keynote Structure Overview (597.61s), EU MDR Requirements (668.785s), Documentation Types Overview (811.175s), Documentation Challenges (1066.98s), Documentation Benefits (1455.3s), Regulatory Documentation Requirements (1774.495s), Language Requirements (1883.665s), Technical Documentation Requirements (2071.78s), Documentation Evolution (2234.195s), Technical Documentation Structure (2366.225s), Device Generations Comparison (2492.715s), Manufacturing Process Documentation (2664.07s), Verification and Validation (2776.07s), European Market Requirements (2918.62s), MDR Documentation Requirements (3027.345s), Top Five Challenges (3101.68s), Closing & Resources (3452.355s)
Transcript for "Technical Documentation for Medical Devices": Hello, everyone. For all of you who are already in the keynote, We are still giving the other, persons which want to attend the keynote a couple of minutes, maybe one, two minutes, and then we will start directly into the topic. Alright. I think we can start slowly. So welcome everyone who is already attending, to today's NSF keynote for technical documentation will focus or according to EU MDR and their challenges. For those of you who have attended some of our keynotes before, let me tell you, the keynote will be recorded. So you will also have the possibility to to watch the keynotes afterwards or to to share the recording with colleagues from your end. Before I start and go into detail, I will also present will give you a short summary of myself and also about NSF as we usually do so that you know who's speaking here today and why are we speaking today, which experience do we bring with us. So let's directly start with the first slide, which is about myself. So, I'm your host today. My name is Andre Fomalotky. I'm working as manager for medical device consulting at NSF. At NSF, yeah, manager of medical device consulting, this case means I'm bringing lots of experience with myself in the field of medical devices. At NSF, I'm working as a team lead for a team which is focusing on the creation of technical documentation. And that's also the reason why myself why I'm holding the keynote here today. Myself, I studied biomedical engineering, and I started working in the field of medical devices in 2010. And when I joined the medical device industry, I was first of all, I was working in industry. And during all of that time, on the very early beginning, I was working in regulatory affairs for international registrations, or international registration purposes, of course, with which also contained focus markets, but also in quality management. During this time, I was working in the implant industry for manufacturers of active medical devices. And the other half of my career, I was spending as a consultant where I had the possibility and to learn lots about different fields in medical device industry, lots of different kind of manufacturers, and lots of technical documentation, and how technical documentation might look like. Besides of my topic and my expertise in the field of technical documentation, I'm also speaker for various topics and for for the performance, for example, of daily trainings, like medical device regulation, obviously technical documentation itself. We are offering a daily training for this topic, but also labeling or software, for example. Especially in the field of labeling, during my career in the industry, I was getting lots of information of, UDI aspects, for example, which might also be interesting for, some persons as well. Alright. Some sentences also to NSF. Who is NSF? So our basic, mission is to improve human and planet health. So NSF is not existing since, only a couple of years. We are existing since 1944 and have been founded in Ann Arbor in Michigan. We are also our headquarters located today, or since back then. Myself, NSF is working in about 25 countries, more than 25 countries. Myself, I am located in Hamburg in Germany. I'm working in an office, yeah, with approximately 50 experts working in quality and regulatory and clinical affairs consulting. And, as you can see here on the world map, we are nearly located in every part of this world. Our colleagues are speaking more than 20 different languages. Also, in our offices, we are covering more than 20, native speakers. Also, colleagues which are native Mandarin speakers, for for example, registration purposes for the Chinese market as well. Myself or where I'm working in, as I already have mentioned, I'm working in the field of medical devices. This belongs to one of the core industries of, NSF is covering. It's life science. Besides medical devices, we are also taking care of, clients for pharmaceuticals, IBDs, combination of products. But lots of our core business is also made in the field of food and nutrition and water. But I think today, we are concentrating on the life science part. Yeah. Since all or I think lots of you are also located in the life science, I will give you also I will outline with further examples what we are doing and what we are also talking today. As consultants in the field of medical devices, we're not only answering questions for our clients, we are also creating, as you can imagine, technical documentation. My team and myself, we are not only creating a summary of technical documentation, but also the different subsets of technical documentation, like risk assessments, PMS, usability files, software files. Everything you will need for registration purposes for, let me say, international registrations, also covering US market, Chinese market, European market. But also, for example, I want to mention that I want to point out that we are performing training for training purposes. For example, in order to, yeah, to to keep up your training program and to support our or the manufacturers, the clients we are working with. Also, lots of clients are coming to us because they, are facing some challenges, not only towards a technical documentation, but also, for example, quality related ones when it comes to audits. This is something we have also teams available in order to support you. The next slide I'm I'm showing here is typically also something I'm using to explain our clients what we are covering, when it comes to our services. But for today's keynote, I want to describe it as part of a technical documentation. We are typically explaining it here like or we are telling our clients we are working with that this is the product life cycle we are covering. Basically, from a to zed, we can help and support our clients with all aspects, like, coming from regulatory affairs, clinical affairs, quality management, but also everything in between. When you look at the different stages here, stage one, for example, regulatory affairs. Yeah. When it comes to strategies, we're working together with with with startup companies, for example. We see to find a way to bring the medical devices to the market. But also, for example, we are helping them with design and development issues when it comes to documentation. As you also will see on the next slides when we jump on the into the content of this keynote, there are certain aspects also design and development teams need to consider when it comes to technical documentation or working together with regulatory affairs teams towards registration purposes. Also, manufacturing. Yeah. I told you I was working half of my career in in in the industry. There was nearly no day when I wasn't in the manufacturing, yeah, which was a very practical part of my my career, talking with those persons, directly manufacturing medical devices. But it gave me also lots of insights and necessary insights in order to prepare submission procedures. When it comes, for example, to auxiliary tools for the manufacturing, which is very often requested from notified bodies or authorities, or liquids you're using, your devices are coming into contact. So lots of those stages, but also considering validation verification activities. This is something we as also as consultant are supporting our clients with. And last but not least, I want to mention and point out post market surveillance activities. Yeah. With market launch, you're not done. Yeah. You need to follow-up. Yeah. Post market surveillance, post market clinical follow-up, that's one of the stages, one of the parts related to technical documentation we need to submit, for our registration purposes and also to keep up to date, keep alive our technical documentation. Alright. I just wanted to use this as a kind of a start before we jump into the specific details for today. So So the next forty to fifty minutes, I'm telling you a little bit of, yeah, as I already said, about the focus market for this, keynote, the the European Union. But also, I will tell something about The US market, for example, as well. And for those of you who have seen me, for example, attending in this keynote before, we did it in the past for the for the German market as well, also in German. Today, there will be talk hopefully, some new aspects, which you haven't heard before. Yeah. Because I'm also concentrating, we'll tell let you know some, yeah, differences to other markets as well. So I hope there's something new for everyone. So we have four parts for today. First of all, I would like to point out daily challenges we all have with technical documentation. And the first one, the first major aspect all of you need to know is, especially for the European Union, where does the term technical documentation is used at first? Or where does it come from? Where does the requirement come from? Where's their origin? I'm not sure how many persons today I hear from The US regions. Typically, there are lots of. Yeah. For those of them, I would like to point out, in Europe, we are working with a regulation twenty seventeen seven o five, which is called also EU MDR, EU medical device regulation, yeah, in short. This regulation, gives gives us lots of information also towards technical documentation, how to work with, what is content, and so on. And this is also something I would like to start with here. One of the first articles here is article number 10. It already mentions the term of technical documentation, but not as kind of a definition. There's also another article, article number two, which which contains lots of definitions related to medical device industry and and for the, which is necessary to understand the medical device regulation. But technical documentation is not explained there. But in article 10, we have the first time it is mentioned, and it tells you and says technical documentation other than custom made or manufacturers of medical devices, devices other than custom made devices shall draw up and keep up to date technical documentation. Yeah. So that's very important and a very important requirement we have already. Draw up and keep up to date. That is not something what is mentioned in the QMSR, for example. Yeah. And the reason is also mentioned, to allow the conformity of a device with the requirements of a regulation to be assessed. So the conformity needs to be understood. And it also tells us, and that's the next next sentence, it shall include the elements set out in annex two and annex three. So this paragraph here, this article here, directly tells us where we need to look at when we want to understand what we need to set up for our technical documentation. Yeah? It means for all of you, maybe some kind of homework afterwards, if you haven't worked with medical device regulation, this topic is new to you, look at the medical device regulation from a European Union. Annex two and Annex three is not very long, but it will tell you which elements you will need for setting up technical documentation. But in the next slides, we will also talk about some of those examples or I will also show you some of some examples. One of the daily problems, I had in the past when I was younger and was very fresh, as a regulatory affairs manager working in industry, it was related to synonyms and relationships because I was working together with r and d, with product management, regulatory affairs show. I was working in there. I was I had my first contacts with notified bodies or authorities. Everyone was talking about different types of documentation. And for me, I needed to find a way to distinguish between them and to understand them. And I today, I want to give you a short summary of how it differs from each other and which terms are widely used. First of all, that's an important one. And, yeah, that's a bucket for everything. Let me say or name it like this. It's a design history file or a design and development file, how it is named in the ISO thirteen forty five. That's the summary, that's the assumption of everything. Yeah? All documents, all versions, especially coming from design and development team. For example, when we talk about drawings, drawings of your medical devices, we are naming and talking about all the different versions. For example, if your medical device is today in version number 10 or the drawing is in version number 10, Yeah. The Medicare or the design history file and design development file contains all 10 different versions. Yeah. So that you also can see what has happened in the past, where have the changes been, and so on. Then there's also the wording of device master record or medical device file, how it is also called device or standard. That one covers only the latest document version. Very important to understand when you're talking to each departments in your company. Latest version means, in this case, we are only talking about, when we are still staying or still talking about medical device drawings, only about version 10. Yeah? But further, resources describe also manufacturing information, like processes, auxiliaries, as I have mentioned before. This is some additional thing related to design history files. Then we have also I'm looking now to the European, yeah, area. We have, for example, stat files, which I kind of mentioned in the medical device regulation. But, also, when we look further for international to international countries, we're talking about, stat files, table of content files, yeah, which are regulated, for example, by the IMDRF, which was formerly the Global Harmonization Task Force. And that the IMF has brought up some guidance documents for manufacturers for international purposes. But that that one also covers, for example, postmark surveillance documentation, clinical evaluations. I hope everyone of you have heard it. Unfortunately, we cannot talk about this today in detail, since this is something specific for for the European market, for example. And other documents, for example, free sales certificates or whatever, what you will need for certain submissions or registrations in specific countries. So different types of documents or technical documentations or documentations you will hear, related, or depending on whom you're talking with. Further, there are there's in Germany, I told you before I'm located in Germany, people are using here also other word wordings like. Yeah. You see there national and specific languages as well and wordings for those type of documents. But also for there are something like device history records, medical device, or best record you need to distinguish. That one typically does not belong to technical documentation for registration purposes and not part of design and development. Yeah. That's why I I, I brought it to the right hand side of the slide, and it's easily understood. But, anyway, that's kind of different types of documents you will see, you will need to understand. Besides of those synonyms, there are other aspects we need to think about. For example, we have lots of different requirements, regulatory requirements in the in the entire market. Look into The US region or European region or or or Asian market. Every market has its own specifics. Yeah. For example, in Europe, I already told you before, the European market on the on the slightly swift synonyms, there's something like a clinical eva eva evaiation report, which is regulated towards or using guidances, published in Europe. Looking at The US market, there's tons of guidance documentation available for US market reasons. And, also, the entire approach when we're register when we're registering a medical device in The US region is completely different to a European market. US is working with so called predicate devices, means you always need to have a medical device by hand, which is already in the market. That's different in Europe. In Europe, notified bodies are checking the documents all the your documents completely, let me say, from scratch. They're looking at it as so without taking into consideration any predicate devices. Yeah. We are also using something like similar devices, equivalent devices, which is very important for us here in Europe. But the approach for registration purposes is different. So documentation up to date notes. That was one of the first aspects I mentioned and requirements from article 10. Documentation must be up to date. You need to find a way how to set it up, a process behind it, how you can have your documentation up to date, which is not as easy as it sounds because manufacturers are different, and all manufacturers are working with different types of docu or tools. Some manufacturers are still working in paper format. I hope not. Yeah. But could be the case. It's not forbidden. There are others working with servers using Word files, PDFs, whatever. Others are working with tools where you can upload your documents. Now so this is everything you can, for example, also for for up to dateness, you need to describe and processes when you want to sell your devices here in Europe. One major aspects I very often get is the scope and level of detail I need to present documents, especially related to technical documentation. Sure. And that also differs. Yeah. That's a maybe, let me say, cultural differences also when you're looking at Europe, US, or international markets. That differs. Yeah. I see with the focus markets are very highly regulated. They want to see lots of details. Also, in the annex two and annex three, they are requesting lots of details. That's often not the case for international markets. So, missing or incorrect documentation. One of the major problems we have also need to face daily. Sure. There's something missing. Could be the case that a notified body or authority is requesting something from your end, and you haven't regarded it or considered it during the creation of the documentation. But could also be the case you are buying from whomever, other companies, medical devices. And in terms of due diligence, there's something missing missing, and documents are outdated historically, have not been created, something is missing, simply missing or incorrect, can also be inconsistent. Or colleagues left the company. You're missing information here. Yeah. Could also be the case that this is some of your daily challenges. At least I made the experience that this could be happen. Integration of different data sources. Yeah. Inconsistencies can happen here. When I'm talking, for example, about, intended users, it could be the case that someone is changing an intended use, which has not been reflected in your technical documentation. That is a misalignment and might lead or will lead to a nonconformity. Linguistic and cultural differences could happen during submission processes that you are struggling with it. Also, when working with other facilities from your company, could be the case. But also, with authorities, for example. My team, we are covering at the moment approximately the registration of medical devices in 120 countries worldwide. We build up a network with different stakeholders in all those different countries, and, also, we are contact in contact with authorities. And lots of the co authorities, when we were starting contacting them, in English, for example, they did not reply at all because they are assuming you are contacting them and they're in their mother tongue. That's one of the problems we we were facing in the last months, to be honest. And also there's lots of linguistic and cultural differences on which might lead to problems for you. Missing company awareness. Something I've seen ten years ago. So, especially when I'm talking about, the transition from MDD. So our former, director directory, which was, yeah, before medical device regulation was was enforced, there was a transition from MDD to MDR. And when this happened, we got lots more roots here in Europe. And the problem was that lots of the colleagues I was working with, they did not have the same same understanding as the regulatory affairs or quality management team. So they were speaking different languages, if if you want to say it like this. And both were all different sides had different intentions. That was not good for the, for the team in very lots of cases. And I think today, it's lots of better because, typically, companies are aware of the requirements, and they do know why we are doing all of this in order to make medical devices more safe for the for the user and patient. But this was a problem years ago. Yeah. But when we are facing off the this and we're getting rid of rid of all those daily challenges, there's lots of benefits we will also have with technical documentation, good technical documentation to name it here. We will have detailed product description in place, which you will see later on. We'll also have benefit, advantages for lots of other different topics. We will have proof of compliance with regulatory compliance. Sure. There are lots of different regulatory requirements, but also, standard requirements we will have and we will see and are facing during the course of technical documentation. But one of the benefits is we have a summary thereof. Yeah? We can see and we can point out that we're fulfilling these requirements. We can show the authorities, notify bodies to whomever who who will need it. Evaluation of product design. We will have evidences that the product design is working. Yeah? Means, basically, we're taking care of that. We get all the evidences we will need. For example, once come when it comes to usability, we need to prepare a usability file for our medical device in order to show that the Medicare device's usability is working. Also, the technique behind it, that the specifications and the characteristics of the device are working, towards the intended use. Documentation of a product specification. We will have everything in one place. Yeah. We will document it. We will have an overview what is necessary in order to, to have a working and safe product. Yes. We will have a list of specifications we can cover during risk management and so on. Quality assurance. For technical documentation reasons, authorities and notified bodies are asking for quality assurance, What characteristics are tested in the end, for example, during your quality assurance? This is also something what is audited typically during your QMS audits. With that, you will ensure that the major aspects, the critical aspects of the device, are considered and are tested before you're sending out your devices. Warning some precautions are important for the user, for the patient. Whoever is using the device, you know, can also be someone during the transportation. We will ensure with technical documentation actively that we have signs, instructions ready. Maintenance and service and disposal, especially disposal. So that's the next point, number seven. Disposal in Europe, that is, that is a a an a requirement, a direct requirement, which came up with medical device regulation. It has been part of requirements in Europe under MDD, but it's now mentioned in NX one within the GSPRs, general safety and performance requirements. We need to take care of a disposal process. I'm not sure if that is described in The US, but I think it's not. But it is in Europe. So if you want to sell your devices here, you need to describe how you're taking care of this and and how your device can be disposed when the life is ended of it. Proof of safety and performance as mentioned. So, in 1994 and also, yeah, 1994 when the NED came out and went into force, there was a so called essential requirements checklist, which manufacturers needed to prepare in order to show that basic safety and performance requirements are fulfilled. Those have been extended and been made larger. We have lots more requirements in the n x one now we need to fulfill. Basically, still in the format of a checklist, but we can directly show to our notified body authority that we're doing it and giving them direct evidences in order to also facilitate them for third parties to evaluate your evidences and to see that what you're providing to them then that the safety and performance is given. Further, of course, we will need it for market assessment. I don't think I need to I need to elaborate it, for any further. We have a more efficient assessment by authorities notified bodies. The better your technical documentation, the faster you will run through audits. Definitely. That is also my experience in the past. Yeah. The better your medical device, technical documentation is, the better everyone else will understand it and the better your result will be and the registration purpose. Last but not least, something I already have mentioned besides, for for example, for onboardings. When you have new colleagues joining your regulatory or product management team, when you have a technical documentation, a good one, then you will have, in the end, a good document available in order to have a perfect onboarding for for your colleagues, yeah, to to get into the new devices they need to to cover. So I think that one's pretty fast. User friendly training instructions, manual to support users is pretty obvious that we will have that. And traceability and history. Yeah. Also, when someone is leaving, some of your colleagues might leave leave in the future. You will have a good technical documentation ready. The better it is, the better. You will also be prepared for future reasons. And there's maybe tons more you can think about later on. Alright. Let's move on. I would like to talk about, in the second part, about regulatory requirements, direct requirements for the purpose of submissions and registrations in Europe Europe. And I would like to to show you where those are in the medical device regulation. So this one is an excerpt of what I've already have shown to you. Just as a short short summary, you need to draw up and keep up to date technical documentation. However you're doing and whatever system you're using, this is something you need to consider, on on your own. But my recommendation would be to describe it within your processes. We have a requirement in article 10 also, related to the retention period of technical documentation. The MDR tells you gives us a requirement to keep technical documentation, including declarations of conformity, copies of relevant certificates, for example, when you are medical device class three manufacturer and receive certificates by your notified bodies, you need to keep them at least ten years after the last device has been placed in the market. Fifteen years for implants. That is something what has been also, expanded. Yeah. Under NED, it was, I think, it was five and ten years. Now it's ten to fifteen. Yeah. So it's longer now. We are living in a digital time. I think it's not a big problem nowadays, but it has been earlier because, also, when I started in 2010, I was working for manufacturer with tons of paper technical documentation were existing without any digital versions. Now so that has been a problem in the past, and I'm pretty sure today is not as the problem is not that existing as it was before, but this is something you need to consider. Also, when it comes to languages, in case you want to sell and want to register your devices in in Europe, you need to work together with a notified body. As a manufacturer, you are free in choosing with which notified body you want to work with. You can choose any notified body from any countries, any member states of European Union. As I told you, for example, we are at the moment, we are also working, we are working with manufacturers worldwide, but also for for registration purpose. And we are located in Germany. We are also, for example, working together with, with a TUV Polska from Poland. It's not a problem. You can do that. You're free in in choosing your notified body. The thing you need to consider here is, every member state could require, also related to your technical documentation, a different language. Therefore, my recommendation before you are deciding for a specific, notified party, talk to them. Ask them which language do they like to prefer, which do they want. Also, when I'm looking into international markets, yeah, Vietnam and so, lots of those countries are requiring labeling information in Vietnamese. So in in Vietnam, for example. But others will also require other languages. Yeah? This is something we also consider during lots of our international registration we have performed. Years ago, when we when we transition from MDD to MDR happened, lots of the clients, I was taking care of, they asked me, yeah, what language considerations do I need to to, to regard. And up to that time, there was nothing. That's why I'm telling it here. Today, there is something. And I just wanted to show you there is a document available. It's kind of it's a it's a guidance document, which you need to use, but which is officially published by European Union. It's called MDR language requirements for manufacturers. It's now in revision number three from last, from August 2025, so last year. And it gives you for the specific type of documents. Like like you can see here in the different columns above, yeah, like label eye, view, implant card, declaration of conformity, and so on. You see there's written which language is is accepted by which member state. So, of course, the entire document covers all the different member states. And you can see here also some for example, Austria is basically is accepting German. Yeah. For for example, for labeling an IFU material, also, for professional users, for example, English. This is something you can consider here, and you can point on when it comes to best practice. And you need to constantly watch this document when it's revised. Yeah. For example, the reason number three update from last year is now covering also new information towards Portugal. So this is I assume we also in future will be updated frequently. So next requirement, article 52 from the MDR. This requirement, you will see more frequently. Also, that one is the first sentence in annex number two and annex number three of the entire regulation. Says technical documentation and, if applicable, the summary thereof to be drawn up by the manufacturer shall be presented in a clear, organized, readily searchable, and unambiguous manner. That that sentence, that requirement caused lots of, misunderstandings, lots of challenges for for the different manufacturers because it wasn't nowhere described what clear, organized, readily, searchable, and unambiguous means. I will, yeah, I will summarize this it it here. Today, it means your documents should be ready, OCR scanned as as PDF or Word files, so you can search in between and have it easy have digital documents ready. That will facilitate notify bodies and authorities to have a fast and sufficient review. But I received questions back then. Yeah. Is hard copy still possible? Can we make our own table of contents? Whatever. So lots of questions I have been asked here. As mentioned before, we are living in the digital world, and this is something you should also consider. So this slide will give you a summary of the different requirements we have talked about. Lots of those aren't new to you. But when you look at at the at the medical device regulation as a whole, you will find, for example, like, above article 27, that's mentioned you need to prepare with your technical documentation a list of all UDIs. This is not a requirement, for example, for, for The US market. We are working together as NSF in the medical device sector with companies manufacturing every year millions of devices in some instances. An Excel spreadsheet can't cover all the UEIs we are talking about here. There must be a process behind it. Yeah. When you're a manufacturer and of of CTs or MRIs or whatever, you are not your your your volume will won't be very high. But for those with with disposables and whatever, the volume could rise pretty high, especially when you're a global player. So this is something you need to think about. This is a mandatory requirement from article 27. To be fair and honest, I've never seen a notified party asking for it, but I'd like to to point it out so that you are able to consider this in future. So what content is expected? So, basically, I want to to start with historically with a historical slide, a little bit historical slide here. What you can see here on the left hand side, in the left column, is a table of contents which has been described in, in a guidance document, which has been formally been published by the GHTF. I think about that was twin 2004 or something like this, wrong about. The right hand side, the right column gives you, in contrast, the table of contents for technical documentation coming from annex two of a medical device regulation. So our recent regulation here in Europe. What you can see here is basically that the different elements you are seeing from a document from 2004 or 2002, whatever it was, twenty years ago, and our today's regulation aren't that different. We have, for example, chapter number one. Every time a device description, which hasn't been changed that much, if you would if you have done it before, right. And essential requirements or principal checklist, that's where the similarity here is at the general safety and performance requirements, so checklist of performance and safety requirements. Design and manufacturing information, that one has also on both sides. Yeah. Also labeling information. But on the in the right column, pardon, is what you can see on the on the left column is what you can see on the left on the on the right column, under chapter number two, information to be supplied by the manufacturer. So there's lots of equivalencies here compared former documents and today's documents, but the accent is different. And, also, the knowledge about the reviewers and manufacturers and the level of detail, the level of scope I have brought up earlier on one of our first slides. That is what is also from my experience and also what my gut feeling tells me every time, what has changed in the past, that people have a different focus developed in the last decades. So as mentioned, when you familiarize yourself with Annex two for technical documentation within the MDR, you will find all the different contents. I have also in one of the following slides as a snapshot of how it looks like. But it contains all the different documentation you will need basically for your medical devices. And number three contains PMS of a requirement to prepare a PMS plan and PMS report or also called for higher classes of medical devices, periodic safety and update reports with different extents, which is also described in the medical device regulation. But this document here is something which is not, used for registration purposes, for example, in US market. The US market doesn't know Absa. They maybe will know, but they are not requiring it for or they are not requesting it for submission issues, submissions in The US market when talking about five ten k's or PMA's, whatever. So a specific European document. How does it look like? So, basically, here, that is, the table of contents, what is presented in annex number two. What we typically do, and that's one of my recommendations, I added a section zero, a table of contents and summary about the manufacturer, purpose of this technical documentation, regulatory status. It's not mandatory. It's not requested by by the per per regulation, but this is something you will need for for your notified body and also whomever to understand why you're doing a specific type of, registration. Yeah. If it's is it a new version of your device? Yeah. Is it your mark is it has has your device already been marketed and so on. So that's, therefore, my recommendation to add this section here. But when we are looking at the device description and specifications, including variants and accessories, there are also some challenges nowadays. For example, that that one is also an excerpt from from the n x two, and it tells you need to provide reference to previous and similar generations of a device, which covers under a and b an an overview of a previous generation or generations of a device produced by a manufacturer and an overview of identified similar devices available available on the union or international markets where such devices exist. The interesting facts are here when we're talking about number a. Lots of their persons I was talking in the past or clients I was was helping, they asked, they had a very specific question. What is the generation of a medical device? It's not defined. Some say, yeah, your medical device changes with every design change, but what is pretty pretty unusual, yeah, but might be the case. Others say it's when you're expanding your intended use and your intended use is growing or as you're adding something, adding claims, whatever. And then you're talking about maybe a new generation. But that's that is something I want to point it out that it has not been hasn't haven't been defined. And that is still something what challenges manufacturers nowadays. Also, what is very interesting, Anna b, that international markets are now considered when we are talking about similar devices. When you're looking at The US market, for example, The US wants to see from your end when you are submitting a five ten k, for example, they want to to have within the submission dossier, or the technical documentation, a so called description of predicate device, a device which is already cleared in The US market. That's a word which is used in The US region. The US is using for this reason also public available databases as well. Yeah. In The US, in Europe, there's also constantly under development the database, which also will facilitate the same. But this is something what is very unique for US market with a predicate device, also the wording. You will only hear it in The US region, predicate device. In the the European market, it has been expanded. The view has been expanded to international markets as well. This does not necessarily mean you can't argue in The US region with any international devices. That's that's not true. I have also when I prepared five ten k's in the past, in some instances, when FDA wants to see data on that your device is functioning, for example, and you haven't had you you don't have any data for The US region, whatever, then you can also argue with with other markets as well depending on the volume you have already sold. That's possible, basically. And FDA, as mentioned, is also agreeing that and when it's reasonable. Design and manufacturing information. Pretty interesting what has happened here in the past. The regulation tells that that complete information and specifications, including the manufacturing processes and the validation, the edge events, the continuous monitoring, and the final product testing is necessary. Data shall be fully included in the technical documentation. That was a huge challenge for manufacturers years ago, also nowadays. Because, first of all, when you have when your medical devices are, or you're working together with suppliers, you need to get some information from them. Yeah. You need to have an agreement and lots of cases here. But when this requirement came out, lots of manufacturers, also manufacturers I was working with, they did not have a clue which edge events they were using for the manufacturing of the devices. So and especially in terms of cleaning validations, it's very important to know that, to know and to understand if the the entire material, what you're using for manufacturing, can be cleaned from your devices. That's also what I mean meant with, missing company awareness. So when when I was and I tell told you I was working lots of also with manufacturers or with with persons from manufacturing. When I was asking which glue or adjuvant you're using for manufacturing of your of your medical of a medical device you're using, they said, every day, something different. What is available? That has changed, especially, yeah, not only in in Europe. I know that behavior also from from the from The USA. They direct you, but they want to see that you are using processes which are static, not changing, not dynamic every day. Yeah. This is something what has, from my understanding, not changed, but, has developed in Europe as well with a more for higher focus. Product verification and validation. I just want to give you also some examples here. Results of tests, engineering, laboratory, simulated use, animal tests, evaluation of published literature, and so on needs to be part of your technical documentation. Detailed information regarding test design, complete test or study protocols, method of data analysis, in addition to data summaries and test conclusions. I was very often asked which test do I need to submit for registration purposes. I get the same questions for other markets as well. Yeah. And to be honest, it's same for all the markets. Every test you will need to show safety and performance of your medical device is necessary, needs to be submitted completely. Protocols, reports, plans, whatever. This is something you need to to to bring into your technical documentation to understand that the GSPRs or essential requirements, whatever you are working with for whichever market, is fulfilled. What I think definitely can say here also when talking about MDR, USA international markets, when covering one of those focus markets, doesn't matter if it's USA, European Union, China. With those markets, you are covering 90% of technical documentation you will need for other aspects as well, roughly. Yeah. But the most important part is in the end verification, validation, and that's also the most challenging one when it comes for within the registrations to deviations. When I'm preparing something like this for The US market, something I really like to use is we offer by the FDA to perform a submission what is it called? Sorry. I forgot the name. And a meeting in advance with FDA offering you to answer questions, and that one is for free free of any charge. And within these meetings, you can clarify the extent of technical documentation verification evidences you will need for submission issues. And this is something what should be taken as an opportunity in order to clarify the extent of verification documents. So other aspects. Also, some unique ones for Europe. Our colleagues here from from The USA should know. If you intend to submit your devices in the European market, besides of the documents I already mentioned, like clinical evaluation report, post market surveillance documents, there's other things which are very specific, like, and this is unique for the European market, like a basic UDI DI. I think worldwide, there are more than twenty twenty countries at the moment developing any specific UDI databases. But the basic UDI is specifically for Europe, which is for a different group or which is for a group of medical devices with same characteristics. It's also regulated. There's a specific MDCG guidance document in Europe available describing those different aspects and characteristics you need to fulfill for a specific basic UBI to bring devices into that group. But also general safety and performance requirements, chapter number four, You need to take care of this list, yeah, specific for Europe. Yeah. This is something you do not need to to submit for The US region, for example. Last but not least, I just want to point out also product verification validation because we haven't seen it here and, means also evidences in terms of software software design. Now this is typically something what is placed here. Don't forget it. But also cybersecurity. Yeah. You need in all the different markets, we are talking about USA is our role model here role model here. Yeah. You need cyber document cybersecurity documentation ready. We have also guidance documents. It's MDCG twenty nineteen dash 16 talking about cybersecurity requirements, but you need to take care of that as well. And it's constantly growing also with requirements here in Europe, New Tours, cybersecurity. Alright. Just to give you an example or some examples how the MDR looks like. I think everyone, yeah, hearing my keynote should know how it practically looks like. This is just some snip snaps snippets from from the regulation. You can see here a snippet from the or screenshot from general safety and performance requirements. It's pretty much in a bullet bullet point form. Everything you can read here. So the requirements. And it's pretty from my understanding, it's it's it's very precisely described what you need to consider here. The first paragraph might be a little bit different, difficult when it comes to risk management. Yeah. But for this reason, for example, that's the ISO fourteen nine seven one, typically manufacturers manufacturers are familiar with. This is a snippet from the annex number two for technical documentation. That one is pretty clear. You can move through the entire list like as Excel spreadsheet and covering or trying to cover or checking like a checklist if you are covering with your technical documentation these aspects mentioned here. Same with Annex number three. Top five challenges and their solution. For this topic, I will since it's pretty late already, and an hour is nearly gone, I will, yeah, pretty pretty I will roughly move forward. But some challenges and some major aspects where I have the feeling or we have the feeling. This is some some concern which is still present today. I just want to bring out and point on. I just mentioned a minute ago, cybersecurity is very, very important nowadays, not only in The US. Yeah. As I I said, The US is a role model here. Yeah. Because lots of cybersecurities activity started in The US when it comes to technical documentation. It's also in the European Union Union already, and it's it's getting strict more more and more strict. There are guidance documents and standards available. Basically, what you need to have ready when you have a medical device containing software and interfaces to networks, whatever. Also, when it does not communicate with anything, you should at least have a rationale ready why cybersecurity is not applicable. You need to have something ready in order to, yeah, to explain your cybersecurity activities. Noncompliance with ISO forty nine seven one risk management documentation. It's kind of an evergreen. Yeah. I don't know what this is this is something what what constantly is is is on our bucket list and it's constantly something our, clients are struggling with. Although the ISO standard is, yeah, is is is is pretty old. Let me say it like this. But problem here is, that there are very often inconsistencies. For example, I told you a little bit in the beginning, I'm also in the expert panel of labeling. What I am typically doing is, for example, when I'm checking technical documentation, which we also do for our clients as well in so called gap assessments, I I'm looking at labeling documentation. So, for example, product label or instruction for use, and then checking it with a risk management. When I see in the product labeling, there's, for example, specific signs. Yeah? Safety signs, warning signs, whatever. And I don't see any any, risk which has been described alongside with those signs. Then there's an inconsistency you need to cover. Now, also, risk management typically contains 10 different steps to move through. And also good wording, which is described by ISO standards, something where we very often frequently see, that risk management has not been probably used. Now this is something our clients are, yeah, typically facing as a challenge. Inadequate Biological Evaluation is also kind of an evergreen. The ISO standard has updated, by the way, this year. But what I very often see is I mean, in Europe, we are also using a document called, which which is requested during submissions, biological evaluation plan, biological evaluation report. Also, within those documents, we are covering rationales which biological tests are performed. The ISO standard contained, contains, a spreadsheet based on contact type, contact duration, which type of testing you need to perform. This rationale needs to be placed in the technical documentation so that the reader, the the auditor, or inspector understands what type of test you want to perform need to perform. We have very often, we see there's a lack in those tests available Very often because, the creator did not think about the specific, yeah, spreadsheet from the ISO standard. It did not think about the different contact types, durations, whatever, in order to specify which tests are necessary. So there's very often something missing. And let me say it like this. I I I had once the case that, for example, genotoxic testing was missing. That can take that typically takes four to six months to perform this. So during a a registration post process, this is quite challenging to keep timelines, especially when we're talking, for example, about five ten k's where you have, one hundred and eighty days for for answering all the questions by FDA. Also, missing PMS documentation. Yeah. When it comes to to, sales data, for example, complaint data, whatever. So this is constantly something it's not one of the gaps we have the feeling which is pretty hard to close. Yeah. Typically, clients, or manufacturers have the data ready, but it's not bundled or summarized as it must be. But but still something I want to point out here. And last but not least, and one of the major still one of the major is clinical evaluation not meeting MDR requirements, especially when it comes to clinical data. Lots of manufacturers before submission, they did not think enough about the existing clinical data or did not evaluate in in in in-depth, if their clinical evaluation is reasonable and all the aspects of a medical device can be covered. Yeah. So this is something we very often also see from from end of notified bodies, that they they are writing deviations here, which can cause lots of challenges, yeah, leading also to the performance of clinical studies in order to to generate data, which might take some lots of time and, can be very difficult. Alright. We have also published in the past. If you will if you like what you hear today. Yeah. So that's related to the top five technical document, technical documentation challenges. That's a flyer we have published. You will have also in the past, in the, in the following, you have we have the the possibility to download the the presentation of today. But, using the QR code here, you will also be directly directed to the, to the to the to the white paper we have published. We have also if you like what you hear and you are maybe at the moment, you are facing some challenges and you need some advice, we have also published flyers for our services. If you want to contact us, I had my contact details on the very first slide. With my contact details, there's a possibility also to contact me contact me afterwards if you have some specific request or you want to talk to me or some colleagues from other expert Spanish we have internally. Yeah. But we have also flyers available if you want to go into deeper deeper detail and understand what services which service we can offer to you. You are free to watch them. Alright. And last but not least, we will also have I think it's next week. We will have another or the next keynote coming up. If you haven't registered for our keynotes, here's the link You can use also using the QR code for registration of upcoming follow-up, following keynotes, from NSF. Thanks, everyone. So we will be glad if you would follow us using our social media, so LinkedIn, or give us a call afterwards. So if anyone has questions, I'm happy to receive them. Unfortunately, we do not have the time today, but I would promise I'm going to answer all the questions you will have afterwards. But I would I would also be happy if you would simply contact me directly using my contact details. You're all welcome. So thanks a lot for everyone attending today's keynote, and I hope you had fun and learned something new. Thanks a lot. Have a great rest of the day. Bye bye.