510(k)

FDA pre-market notification submission for medical devices.

How to pass the FDA Refusal to Accept (RTA) Screening Process

This article helps you understand how to pass the FDA Refusal to Accept (RTA) screening process 510k submissions – updated April 2022.

Refusal to Accept How to pass the FDA Refusal to Accept (RTA) Screening Process

What is an RTA Checklist?

The “RTA” in RTA Checklist stands for Refuse to Accept. The FDA uses this tool to determine if your 510(k) submissions will be accepted or not for a substantive review. Accepted, not approved because this is simply a verification that the required information is included in your submission. As stated in the 2022 FDA guidance document for the FDA’s Refuse to Accept Policy for 510(k)s “a minimum threshold of acceptability and should be accepted for substantive review.”(Ref.1). That does a nice job summarizing the RTA checklist. It is a tool used to help assess whether or not your submission contains the required information to continue with a more thorough review of the contents of the submission itself. 

What does the Refusal to Accept (RTA) policy apply to?

The Refusal to Accept (RTA) policy applies to all 510k submissions. The RTA checklist or more checklists apply specifically to each 510(k) submission type:

  • Traditional 510k
  • Abbreviated 510k
  • Special 510k

There is a different RTA checklist for each submission type. The checklists are in the Refuse to Accept Policy for 510(k)s guidance document. Specifically, in the PDF document that the FDA reissued in April 2022, the checklists can be found in the following areas:

  • Traditional 510k – Appendix A.
  • Abbreviated 510k – Appendix B.
  • Special 510k – Appendix C.

Note that the title of the checklist refers to an ‘acceptance checklist.’ It is not called the RTA checklist until you get to the footer of the page. It is also listed as an acceptance checklist on the FDA website. The best way to think of the process is as preliminary screening by the FDA. 

What does the FDA look at during the Refusal to Accept (RTA) screening process?

During the screening process, the assigned RTA screener will review the 510k submission and try to identify all of the requirements listed in the applicable RTA checklist. The person screening your submission is required to answer “yes,” “no,” or “n/a” to the questions in the checklist. This person must also enter the document and the page where the information can be found in the submission. Finally, if an element required by the refusal to accept (RTA) checklist cannot be found, then the screener adds a comment at the end of that section in the checklist. The comment will state what your deficiency is and it may even identify a guidance document that can help you address the issue. If you are missing requirements, you will receive an email from the RTA screener with the completed RTA checklist attached. We call this an “RTA Hold” letter. If your submission is not rejected, then your 510k is administratively complete, and you will receive an automated email indicating that your submission was accepted and the substantive review will begin.

Refusal to Accept (RTA) Time Frame

As stated in the guidance document, the Refusal to Accept policy includes “an early review against specific acceptance criteria and to inform the submitter within the first 15 calendar days after receipt of the submission if the submission is administratively complete, or if not, to identify the missing element(s).” (Ref. 1). If the assigned screening person is unable to complete the process within 15 calendar days, then you will receive an automated email stating that they were unable to complete the RTA checklist within 15 calendar days, and your submission is automatically moved to the substantive review stage of the 510k review process.

Taking the time to perform your gap analysis before submitting could avoid a simple error. For example, if you forget to include the signed Truthful and Accuracy Statement in your submission, it could take 15 days to be notified of that missing element. The person screening your submission could email you to provide this missing element in an interactive review to avoid placing your submission on hold. Still, they are not required to give you a chance to provide this interactively by email. If you do receive an RTA Hold letter, you might be able to correct missing elements on the same day, but the 510k review clock is automatically reset when your 510k is placed on RTA Hold. When you respond to an RTA Hold letter, there will be another 15-day refusal to accept (RTA) screening of your submission.

What do you do with the information in the comments of the RTA checklist?

The RTA checklist is the criteria that your submission is being evaluated against. Suppose your submission has deficiencies during the initial review against the RTA Checklist. In that case, the FDA will refuse to accept it, and the substantive review will not begin until those deficiencies have been corrected. Since the FDA does not hide what they are looking for or how they will evaluate your submission, use that to your advantage. Assuming that you have correctly determined the type of 510k submission you have, perform a gap analysis of your submission against the RTA checklist. Either perform these actions in-house or hire an outside consultant to do them for you, but make sure you don’t try to check your own work because you will miss something. 

Scope of the FDA Refusal to Accept Guidance Document

The scope of the FDA guidance document is provided for the benefit of the FDA personnel reviewing your submission and not specifically for the 510k submitter. It also provides a loose framework for systematically and consistently reviewing submissions. This ensures all submissions receive equal, nonbiased treatment. There are some things that this guidance document does not address or alter by its own admission. One is the “substantial equivalence decision-making process once the submission has been accepted for review.” Refusing to accept (RTA) guidance also does not address FDA user fees. Other guidance documents address those issues.

What are the most common reasons for FDA refusal of your 510k submission?

Although there are dozens of reasons (43 to be exact) why the FDA could reject your submission in the 35-page RTA checklist, most of the refusals (~80%) result from a small percentage (~20%) of reasons. The most common is that your submission is poorly organized. Either you did not provide a table of contents, your submission is not organized in accordance with the sections outlined in the guidance, or the pages of your submission are not properly numbered. When trying to review a 1,200-page submission, poor organization is extremely irritating and wastes the reviewer’s time. If it were my decision, I would refuse to complete the entire checklist until you gave me a properly organized submission.

The second most common reason for refusal is submitting a device description that is inadequate. The FDA needs more detail than most companies provide for the device description because they need to understand the differences between your device and the predicate device. This includes much more than just the indications for use. Who are the intended patients and users? What is the intended environment of use? What are the materials for patient-contacting components? What is the source of power for your device? Which design features does your device include when compared to the predicate? What is the user interface for your device? Which accessory devices are needed with your device? You can even make the mistake of being inconsistent in your submission by not repeating the content in the device description in other sections of the 510k submission. It is important to duplicate certain content verbatim in other documents, such as the 510k summary, the executive summary, the substantial equivalence comparison, and the instructions for use. Paraphrasing and summarizing certain information will not work.

The third most common reason for refusal of your submission is likely related to software validation documentation. In addition to complying with the recognized IEC 62304 standard, you must also comply with the five software guidance documents published by the FDA. The FDA and 3rd-party reviewers use an 11-item checklist based on the 2005 FDA guidance document on software validation documentation. In addition, if your device has any of the following five elements, your submission must also comply with the two FDA guidance documents on cybersecurity:

  1. Cloud communication
  2. Network connection (active or not)
  3. Wireless communication in any form
  4. USB/serial ports/removable media
  5. Software upgrades (this includes patches)

Finally, biocompatibility is the one testing section of your 510k submission that is most likely to result in refusal to accept by the FDA out of the seven sections requiring testing reports. There are several reasons why biocompatibility results in more refusals than the other six testing sections. First, the FDA requirements go above and beyond the ISO 10993-1 standard requirements. Second, the FDA requires that you submit full testing reports for biocompatibility, while you can submit summaries for other sections (e.g., sterilization validation). Third, many submitters try to provide a rationale for why testing is not required for their device. Still, the FDA has very stringent requirements for the use of a biological risk assessment or a biocompatibility certification statement in lieu of testing.

Do you have to follow the RTA checklist exactly?

You can, but you are also not bound by it. Like all guidance documents, they “contain nonbinding recommendations”. The checklist is released as part of a guidance document, so it is a guidance and not a regulatory requirement. That being said, if your submission is missing an element in the checklist, your 510k submission will be considered administratively incomplete unless you provide a clear explanation as to why the checklist element does not apply to your submission or you explain how you meet the 510k submission requirement in another way.

Medical devices vary wildly, and there is no one size fits all approach. The FDA recognizes that and includes some wiggle room that gives them some discretion in reviewing submissions. However, 100% of the 3,500+ submissions received each year are screened using the refusal to accept (RTA) checklist, and the screening person’s job is to verify that your submission meets the criteria. As it says in the guidance document:  

“The purpose of the 510(k) acceptance review is to assess whether a submission is administratively complete, in that it includes all of the information necessary for FDA to conduct a substantive review. Therefore, the submission should not be accepted and should receive an RTA designation if one or more of the items noted as RTA items in the checklist are not present and no explanation is provided for the omission(s). However, during the RTA review, FDA staff has the discretion to determine whether missing checklist items are needed to ensure that the submission is administratively complete to allow the submission to be accepted. FDA staff also has the discretion to request missing checklist items interactively from submitters during the RTA review. Interaction during the RTA review is dependent on the FDA staff’s determination that outstanding issues are appropriate for interactive review and that adequate time is available for the submitter to provide supporting information and for FDA staff to assess responses. If one or more items noted as RTA items on the Acceptance Checklist are not present, FDA staff conducting the acceptance review should obtain management concurrence and notify the designated 510(k), contact person, electronically that the submission has not been accepted. “ (Ref. 1).

The portion above notes that explanations may be provided for omitted portions of the submission. So, the answer to the question is that no, you do not have to follow the RTA checklist exactly. However, if you should purposefully omit a section you should provide an explanation and your rationale justifying why the omission is appropriate for your individual device and 510(k) submission. Again, just because you have included an alternative approach or justification does not automatically mean it will be accepted. The FDA personnel who are conducting the acceptance review will judge whether or not your deviation is acceptable.

What if your 510k submission is refused?

If your submission is refused, you will be provided with a copy of the completed RTA checklist, and each of the deficiencies you must address will be highlighted. Sometimes, there will be an attachment to the checklist that has additional issues that are not in the RTA checklist, but the reviewer thinks you may need to address them later. You might also see comments that are not highlighted. These are suggestions from the reviewer that you may or may not choose to address.

There is a 180-day timeline for response to an RTA Hold letter. The response must be submitted to the CDRH Document Control Center (DCC) as an eCopy, and the response must be received within 180 days. If the response is not received within 180 days, your submission will be automatically withdrawn on the 181st day. Your response may not be piecemeal. You must address all of the issues in the RTA checklist or your submission will be placed on RTA Hold again (i.e., RTA2). If you are not sure how to organize your response, a previous blog posting and YouTube video address this topic directly.

About the Author

20190531 005146 150x150 How to pass the FDA Refusal to Accept (RTA) Screening ProcessMatthew Walker – QMS, Risk Management, Usability Testing, Cybersecurity

Matthew came to us with a regulatory background focused on OSHA and NFPA regulations when he was a Firefighter/EMT. Since we kidnapped him from his other career, he has worked in medical device quality systems and technical/medical writing and is a Lead Auditor. Matthew has updated all of our procedures and is currently a student in Champlain College’s Cybersecurity and Digital Forensics program. We are proud to say he is also a Golden Keys and Phi Theta Kappa Honor Society member! Matthew participates in our audit team and is passionate about risk management and human factors engineering. Always the mad scientist, Matthew pairs his professional life in regulatory affairs with hobbies in the culinary arts, as he also holds a Butchers/Meat Cutters certificate from Vermont Technical College.

Email: Matthew@FDAeCopy.com

Connect on Linkedin: http://www.linkedin.com/in/matthew-walker-214718101/

How to pass the FDA Refusal to Accept (RTA) Screening Process Read More »

Additional Information Request is different from an RTA

A poor RTA response will cause a two-week delay, but an additional information request only gets one chance to avoid the dreaded NSE letter.

An Additional Information Request (i.e. AI Request) is typically received just before the 60th day in a 90-day 510k review, while a Refusal to Accept (RTA) Hold is typically received on the 15th day. If your response to your first RTA Hold (i.e. RTA1) is inadequate, the reviewer will issue another RTA Hold letter (i.e. RTA2) and your 510(k) review clock will be reset to 0 days. You will have another 180-days to respond to RTA2, and issues identified in an RTA Hold are usually easy to address. Most RTA Hold issues also have one or more guidance documents that are available to help you to obtain an RTA Accept letter. You can always request a submission-in-review (SIR) meeting to clarify what information the reviewer needs to address the RTA deficiencies too. If you want to learn more about responding to an RTA Hold, please read last week’s blog. The rest of this article is specific to responding to requests for additional information.

What happens after 60 days during a 510k review?

On the 60th day of the 510k review clock, or a few days prior to the 60th day, the lead reviewer must determine if they need to issue an Additional Information (AI) Request. The alternative to an AI Request is for the lead reviewer to issue a letter indicating that you have entered the Interactive Review Phase. This only happens if the reviewer believes they can make a decision regarding substantial equivalence in the next 30 days. If the decision is to issue an Interactive Review Letter, then the lead reviewer believes that only minor issues remain and there is only the need for interactive email responses between the lead reviewer and the submitter. An interactive review is the ideal outcome of the substantive review process but it rarely happens.

If you receive an Additional Information Request, what are your options?

The AI letter will indicate that you have 10 days to request a clarification meeting with the reviewer. The wording of this section of the AI letter is provided below:

“FDA is offering a teleconference within 10 calendar days from the date on this letter to address any clarification questions you may have to pertain to the deficiencies. If you are interested in a teleconference, please provide (1) proposed dates and (2) a list of your clarification questions via email at least 48 hours before the teleconference to the lead reviewer assigned to your submission. We would like to emphasize that the purpose of the meeting is to address specific clarification questions. The teleconference is not intended for the review of new information, test methods, or data; these types of questions could be better addressed via a Submission Issue Q-Submission (Q-Sub). For additional information regarding Q-Subs, please refer to the Guidance for Industry and FDA Staff on Medical Devices: Requests for Feedback and Meetings for Medical Device Submissions at https://www.fda.gov/media/114034/download.”

If you wait too long to request the teleconference, then FDA will require you to submit a formal pre-sub request or “Submission in Review” (SIR) meeting request. If you request a SIR meeting within 60 days of receiving an AI Request, the FDA will schedule a SIR meeting with you within three weeks of receiving the request–assuming resources are available. If you wait longer than 60 days to request the SIR meeting, then the FDA will default to their normal target of 60-75 days for scheduling a pre-sub meeting. For example, if you submit your SIR meeting request on day 75, and the FDA takes 75 days to schedule the meeting, you will be granted your SIR meeting at 150 days and you will only have 30 days remaining to respond to the AI Request before your submission is automatically withdrawn.

Therefore, it is important to request a clarification meeting immediately after you receive the AI Request. While you are waiting for your clarification meeting, you should immediately begin preparing any draft testing protocols that you want the FDA to provide feedback on during a SIR meeting. Then after you have the clarification meeting, you should submit your SIR meeting request and include any draft testing protocols you have prepared. This may include a statistical sampling rationale, a proposed statistical analysis method, a summative usability testing protocol, or a draft protocol for some additional benchtop performance testing. The FDA can review examples of preliminary data, a protocol, or a proposed method of analysis. The FDA cannot, however, provide a determination of substantial equivalence.

The Most Common Mistakes in Responding to an Additional Information Request

Most companies make the mistake of asking the lead review if they provide specific additional information, “Will this be sufficient to obtain 510(k) clearance?” Unfortunately, the FDA is not able to provide that answer until the company has submitted the additional information and the FDA review team has had time to review it thoroughly. This is done only when the submitter delivers an FDA eCopy to the Document Control Center at CDRH, and the review team is able to review the information. This new information is assigned a supplement number (e.g. S001), and it will typically require three weeks to review the information. Then the lead reviewer may request minor modifications to the labeling, instructions for use, or the 510k summary. This request is an interactive request, and the submitter must respond within a very short period (e.g. 48 hours), and the wording of the request may be “Please provide the above information by no later than COB tomorrow.”

FYI: “COB” means “close of business.” Wow. The FDA loves acronyms.

Best Practices in Responding to an Additional Information Request

If you receive an AI request on a Friday afternoon, 58 days after your initial submission, you should immediately request a clarification teleconference with the FDA reviewer for the following week. The only exception is if you only have minor deficiencies that you feel are completely understood. During the days leading up to the clarification teleconference, your team should send a list of clarification questions to the lead reviewer and begin drafting a response memo with a planned response to each deficiency. After the clarification meeting, you will have approximately 6-7 weeks to submit a SIR meeting request. However, you should not wait that long. Your team should make every effort to submit your SIR meeting request within 2-3 weeks. If the FDA takes 3 weeks to schedule your meeting, then you will have used approximately 6 weeks of your 26 weeks to respond to the AI Request.

In your SIR meeting request, you should always try to provide examples or sample calculations to make sure the FDA review team understands what you are proposing to submit in your supplement. For example, the FDA reviewers do not have enough time to review your entire use-related risk analysis (URRA) in a SIR meeting request. However, you can provide an example of how you plan to document a couple of use-related risks. Then you can show how these risks would translate into critical tasks. Finally, you could provide a draft summative usability testing protocol for FDA feedback. The FDA review team doesn’t have enough time available to review much more. You will only have one hour for your SIR meeting.

How to Prepare Your Response

In section “V” of the FDA guidance on deficiency responses, the FDA recommends that you restate the issue identified by the reviewer in your response. Next, your response should include one of the following:

  1. the information or data requested, or
  2. an explanation of why the issue is not relevant, or
  3. alternate information with an explanation of why the information you are providing addresses the issue.

Before you respond to an AI Request, you should look up any FDA guidance documents referenced in the AI Hold letter to make sure that you address each requirement in the applicable FDA guidance document(s).

The most important technique to learn when you are responding to regulators is to organize your response in a tabular format that is numbered in exactly the same order that the request was made. Typically there will also be sub-parts to certain issues. In that case, you should duplicate the numbers and/or letters of each sub-part and segregate each sub-part in a different row of the table. Personally, I like to alternate the color of the font I use in the table to make it even more obvious which information is a restatement of the reviewer’s comment and which information is the company’s response to the AI Request.

Why you don’t get a second chance to respond to an AI Request

Once you respond to an AI Request, and the DCC receives your FDA eCopy, the FDA review clock will then resume the countdown to 90 days. In our example above, you received the AIR Request on the 58th day. The FDA must review everything you submitted and make a final substantial equivalence decision before the 83rd day because they still need to submit their recommendations to senior management in their branch. If any changes to the labeling, instructions for use, or the 510k are required, you should receive those requests several days before (i.e. 76-83 days). You can respond to interactive requests via email, and then the final SE decision will be made. If you do not respond to all of the deficiencies in the AI Request, the FDA reviewer will not have enough time to request that you address the remaining gaps and finish their review. Therefore, an incomplete AI Response will certainly result in a non-substantial equivalence (NSE) letter.

If you need to respond to an additional information request from the FDA reviewer, we can review your planned response to identify potential gaps. If you need help please use our calendly app to schedule a call with a member of our team.

About the Author

Rob Packard 150x150 Additional Information Request is different from an RTA

Robert Packard is a regulatory consultant with 25+ years of experience in the medical device, pharmaceutical, and biotechnology industries. He is a graduate of UConn in Chemical Engineering. Robert was a senior manager at several medical device companies—including the President/CEO of a laparoscopic imaging company. His Quality Management System expertise covers all aspects of developing, training, implementing, and maintaining ISO 13485 and ISO 14971 certification. From 2009-2012, he was a lead auditor and instructor for one of the largest Notified Bodies. Robert’s specialty is regulatory submissions for high-risk medical devices, such as implants and drug/device combination products for CE marking applications, Canadian medical device applications, and 510(k) submissions. The most favorite part of his job is training others. He can be reached via phone 802.258.1881 or email. You can also follow him on Google+LinkedIn or Twitter.

Additional Information Request is different from an RTA Read More »

What are the secrets to success in responding to an FDA RTA Hold?

When an FDA reviewer places your 510k on RTA Hold, there are secrets you can learn to improve your chances of a successful response.

Test your knowledge about the FDA RTA Hold process

Did you know that approximately 50% of 510(k) submissions are placed on RTA Hold? Did you know that you can be placed on RTA Hold multiple times for the same submission? Did you know that the 90-day review clock is reset to “0” when you submit your response? Do you know how to respond to the FDA when the reviewer is incorrect? Did you know that you can avoid the RTA screening process for any 510(k) submission if you use the correct template? Every year there are more than 1,000 submissions placed on RTA Hold, but did you know there is an FDA guidance specifically telling you how to respond to deficiencies? You can learn the secrets to responding to an FDA RTA Hold just by reading this article.

What is an FDA RTA Hold?

When the FDA receives a Traditional 510k submission FDA eCopy, the eCopy is uploaded to the FDA system within hours of the submission being received. If the eCopy does not meet the eCopy format requirements, then the submission will be placed upon eCopy Hold. The official correspondent will receive an automated email indicating that the submission is on eCopy Hold, and the submitter will be asked to correct the submission format to meet the eCopy submission requirements and provide a replacement eCopy. If the FDA user fee has not cleared, then the submission will be placed on User Fee Hold. It is possible to be placed on eCopy Hold and User Fee Hold at the same time.

If your eCopy is accepted, then a reviewer is assigned to screen your submission for compliance with the FDA Refusal to Accept (RTA) policy. The reviewer has 14 days to complete this review, and on the 15th day the reviewer must do one of three things: 1) issue a RTA Hold letter to the submitter, 2) issue an RTA Acceptance letter to the submitter, or 3) issue a letter that states the RTA screening was not completed on-time and the submission was automatically accepted. If your receive an RTA Hold letter, it will be via email from the reviewer and the RTA Checklist will be attached. In the checklist, there will some items highlighted in yellow and deficiencies will be noted in those sections. The reviewer may add additional comments to the checklist, but you are only required to respond to the highlighted sections. The process that the reviewer follows for RTA screening is defined in the FDA guidance for the Refusal to Accept process, and the guidance includes a checklist for traditional, abbreviated, and special 510k submissions. Some companies will fill in these checklists themselves and submit a copy of the checklist with the 510k submission. This is intended to help the reviewer identify where all of the requirements in the RTA checklist can be found. Third-party reviewers require that the company complete the RTA checklist and provide it to them with the eCopy.

How many times can you be placed on hold for the same submission?

Technically there is no limit to the number of times a submission can be placed on RTA Hold, and our firm has seen a few submissions placed on RTA Hold twice in a row. The first RTA Hold is referred to as RTA1, and the response to that RTA Hold is referred to as the first supplement (i.e. K123456/S001). If a second RTA Hold is issued, that hold is RTA2, and the response to that RTA Hold is referred to as the second supplement (i.e. K123456/S002). A response to an eCopy Hold is referred to as an amendment (i.e. K123456/A001).

What happens to the 90-day review clock when you are placed on RTA Hold?

When the FDA reviewer places your submission on RTA Hold, the 90-day review clock is automatically reset. Therefore, even if you respond to an RTA Hold on the same day you receive the RTA Hold, and your submission is received the next day, the “real” review timeline is now 106 days instead of 90. If your submission is placed on RTA Hold twice, then the “real” review timeline is now 122 days instead of 90. If the lead reviewer of your 510k requests additional information, this is referred to as an “AI Request.” We will address this in a future blog, but an AI Request does not reset the review timeline. The AI Request, however, will increase the review timeline. Although we rarely have an RTA Hold, we almost always have an AI Request. This is why our average submission is approximately 125 days (i.e. ~30 days are required to respond to the AI Request.

How should you respond if the FDA reviewer is incorrect?

The average 510(k) submission has grown over time from 300 pages to more than 1,200 pages, but the FDA review “clock” is still 90 days and the RTA screening is limited to 15 days. Therefore, it is not reasonable for you to expect the reviewer to understand and absorb every detail of your submission. If the reviewer can’t find the information they are looking for quickly, the reviewer may state that they could not find the information in the submission or that you did not provide it. If the information is found in the submission, you should provide a reference to the section of the submission, including the document and page number, in your RTA response. You may even choose to quote the information in your response memo if it is brief.

Other times the reviewer may not understand why certain information is not relevant to your submission. In this case, you should restate why the information requested is not relevant. You may want to review relevant FDA guidance documents that explain how to justify why information is not required.  For example, if you did not provide biocompatibility testing reports for some of the endpoints that are identified in ISO 10993-1:2018, then you should either provide a detailed biological risk assessment in accordance with the FDA guidance on the use of ISO 10993-1, or you should provide a biocompatibility certification statement.

If you are not sure why the FDA reviewer stated the information you provided is not acceptable, you might try calling or emailing the reviewer to ask for clarification. If you do this, be respectful of their time and be brief. You should identify who you are (you must be the official submission correspondent to speak with the reviewer), you should identify which submission you are contacting the reviewer about (they are working on many simultaneously), you should restate the issue identified by the reviewer (it may have been an issue of another member of the review team), and then you should indicate where the information can be found in the submission. If they believe this addresses the issue, then they will instruct you to provide that information in an RTA response. If the information does not address the issue, usually they will explain why. Your chances of receiving an email response are also better than speaking to the person on the phone–especially during the Covid-19 pandemic.

FDA eSTAR submissions are not subjected to the RTA screening process

When you use the FDA eSTAR submission instead of creating an eCopy, your submission should already meet all of the RTA screening requirements. The eSTAR includes automation to validate that the submission is administratively complete and therefore the reviewer does not need to do an RTA screening of an eSTAR submission. Therefore, most companies should realize a shorter overall 510k clearance timelines, because they will only have an AI Request and the review clock will not be reset.

Does the FDA offer any guidance on how to respond to deficiencies?

When the FDA writes deficiencies, the reviewer is supposed to follow the FDA guidance for deficiency content and format. However, the RTA checklist deficiencies typically are shorter and may not be as clear as a deficiency in additional information (AI) requests or non-substantial equivalence (NSE) letters. The first part of the deficiency is a reference to the information that was provided by the submitter (i.e. section, page number, or table). In an RTA checklist, each deficiency is provided in the comments section at the end of the section of the checklist. Therefore, if you have a deficiency related to your device description, the deficiency will be written at the end of the device description section of the RTA checklist. The comment will be highlighted in yellow, and there will be a checkbox next to the specific checklist item indicating that the requirement was not met. In the far-right column of the checklist, there will be a reference to the page of the submission where the deficiency can be found.

In the comment there reviewer should explain why the current information does not meet the requirement of the RTA checklist. The reviewer should also clarify the relevance of the deficiency with regard to the substantial equivalence determination. For the example of a deficiency related to your device description, usually, the issue is that your submission has inconsistencies between the various submissions or there is insufficient detail about your device. At the end of the comment, the reviewer should provide an explicit request for the information needed to address the RTA Hold.

In section “V” of the FDA guidance on deficiency responses, the FDA recommends that you restate the issue identified by the reviewer in your response. Next, your response should include one of the following:

  1. the information or data requested, or
  2. an explanation of why the issue is not relevant, or
  3. alternate information with an explanation of why the information you are providing addresses the issue.

Before you respond to an RTA Hold, you should look up any FDA guidance documents referenced in the RTA Checklist to make sure that you address each requirement in the applicable FDA guidance document(s).

The most important technique to learn when you are responding to regulators is to organize your response in a tabular format that is numbered in exactly the same order that the request was made. Typically there will also be sub-parts to certain issues. In that case, you should duplicate the numbers and/or letters of each sub-part and segregate each sub-part in a different row of the table. Personally, I like to alternate the color of the font I use in the table to make it even more obvious which information is a restatement of the reviewer’s comment and which information is the company’s response to the RTA Hold.

Regardless of how well your response is organized, you must respond within 180 days. On the 181st day, your submission will be automatically withdrawn. The agency has granted extensions of an additional 180 days during the Covid-19 pandemic, but that will end and you should verify if you can obtain an extension from the reviewer rather than assume that this will happen. If the 180th day is on a weekend or US holiday, the Document Control Center (DCC) at the FDA will not receive your submission until the next business day. Therefore, you will need to ship your submission earlier to ensure the delivery is received on time. Since most companies are shipping their RTA response via FedEx or UPS to the FDA, you also will want to make sure you take into account customs clearance for international shipments and local holidays where you are. If you are shipping from the UK, for example, you can’t expect FedEx to ship on a British holiday. If you need help with printing and shipping your RTA response, Medical Device Academy offers an eCopy print and ship service for $99/eCopy (including the overnight FedEx fee).

If your 510k submission was placed on RTA Hold by the FDA, we can help you respond to the deficiencies identified by the FDA reviewer. We can also review your planned response to identify potential gaps. If you need help please use our calendly app to schedule a call with a member of our team.

About the Author

Rob Packard 150x150 What are the secrets to success in responding to an FDA RTA Hold?

Robert Packard is a regulatory consultant with 25+ years of experience in the medical device, pharmaceutical, and biotechnology industries. He is a graduate of UConn in Chemical Engineering. Robert was a senior manager at several medical device companies—including the President/CEO of a laparoscopic imaging company. His Quality Management System expertise covers all aspects of developing, training, implementing, and maintaining ISO 13485 and ISO 14971 certification. From 2009-2012, he was a lead auditor and instructor for one of the largest Notified Bodies. Robert’s specialty is regulatory submissions for high-risk medical devices, such as implants and drug/device combination products for CE marking applications, Canadian medical device applications, and 510(k) submissions. The most favorite part of his job is training others. He can be reached via phone 802.258.1881 or email. You can also follow him on Google+LinkedIn or Twitter.

What are the secrets to success in responding to an FDA RTA Hold? Read More »

Before 510k clearance, 10 quality tasks you need to prevent unexpected delays

The US FDA does not require that 100% of your quality system be implemented before 510k clearance, but these 10 activities need to be done.

The form above allows you to register for a live webinar we are hosting on Friday, May 21, 2021 @ 1 pm EDT. The webinar will share the 510k project management lessons learned by our team since 2016. In addition to 510k project management, MedTech companies also need to implement their quality system in parallel with their regulatory submissions. Some people say that you need to implement your quality system before you submit your 510k. That is not an FDA requirement, but you do have quality system activities that need to be done before you will have all of the technical documentation you need to submit a 510k. This article describes 10 quality tasks you need to prevent unexpected delays.

Design & Risk Management Planning

Design & Risk Management Planning is your 1st priority because you want to identify all of the major activities that need to be completed in your design and risk management processes and which activities are critical path items. Otherwise, you will have unexpected delays. You can and should add details to the plan as you go, but items 2-9 listed below should be included in that initial plan–along with your design and risk management activities.

Risk Management Activities are Needed Before 510k Clearance

Risk Management is your 2nd priority because it’s an input to almost everything else listed below – this includes hazard identification, creating a use-related risk analysis (URRA), and identifying cybersecurity risks if you have software/firmware. Reference: ISO 14971:2019 Medical devices — Application of risk management to medical devices. Cybersecurity depending on the device should evaluate security as an overlapping but separate area from risk management. (Reference AAMI TIR57: 2016 Principles For Medical Device Security – Risk Management.)

Formative Usability Testing

Formative Usability Testing is your 3rd priority because this helps you evaluate your device design while it’s still evolving. Formative testing helps you identify opportunities for improvement, provides confirmation that your design is moving in the right direction, and identifies potential use errors while there is still time to implement effective risk controls such as alarms and other safety features. References:

Software Validation is Needed Before 510k Clearance

Software Validation is your 4th priority because it must precede electrical safety testing for electromedical devices and most companies underestimate the time required to document software validation in accordance with IEC 62304:2006 / AMD 1:2015 and the FDA’s five guidance documents:

Supplier Qualification is Needed Before 510k Clearance

Supplier qualification is your 5th priority because you do not want to order all of your prototype parts for the initial testing parts and then find out that the supplier is not capable of supporting you commercially. If you have to switch suppliers you might be forced to repeat biocompatibility testing and other design verification testing due to changes in the manufacturing process. Implementation of a supplier qualification process before 510k clearance is needed.

Label & IFU Requirements Specifications

Label requirements and instructions for use requirements specifications is your 6th priority because you cannot perform electrical safety testing or design validation (including summative usability testing) of your device without labeling and instructions. These requirements are the design inputs for information provided to the user and these must be controlled under design controls rather than document control.

Packaging Specifications

Packaging specifications is the 7th priority you should implement before 510k clearance because the packaging is needed to maintain sterility, to ensure product stability, and to protect the product from shipping. Companies are also frequently surprised by the long lead times associated with ordering custom packaging and you may not have the budget to validate sub-optimal “stock” packaging for your 510(k) submission and then repeat the validation for the optimized packaging later.

Quality System Implementation

Quality system implementation is the 8th priority for implementation before 510k clearance because you will need a fully functional quality system by the time your 510(k) is cleared. Quality system implementation typically takes 6+ months while the 510(k) review should take 4 months or less. Quality system implementation includes writing 25+ procedures, reviewing and approving those procedures, training your employees, and actually using those procedures to begin generating quality system records. For companies that are pursuing Canadian Licensing or CE Marking, the quality system must be fully implemented and certified before the regulatory submission is possible. (Quality System Requirements for the U.S. FDA are outlined within 21 CFR 820-Quality System Regulation)

Summative Usability Testing

Summative usability testing should happen after Design Freeze or you risk having to backtrack in your design process if this validation test reveals a need for device changes. The FDA’s 2016 Usability Guidance explicitly defines this validation testing as just a portion of overall design validation. (Reference Applying Human Factors and Usability Engineering to Medical Devices Guidance for Industry and Food and Drug Administration Staff (2016))

Apply for Small Business Status Before 510k Clearance

Application for small business status should be the 10th priority for implementation before 510k clearance because this can save your company $16,000+ but it requires that you submit your application at least 60 days before you need to pay the 510(k) user fee.

About the Author

20190531 005146 150x150 Before 510k clearance, 10 quality tasks you need to prevent unexpected delaysMatthew Walker – QMS, Risk Management, Usability Testing, Cybersecurity

Matthew came to us with a regulatory background that focused on OSHA and NFPA regulations when he was a Firefighter/EMT. Since we kidnapped him from his other career, he now works in Medical Device Quality Management Systems, Technical/Medical Writing and is a Lead Auditor. He is currently a student in the Champlain College’s Cybersecurity and Digital Forensics program, and we are proud to say that he is also a member of both the Golden Keys and Phi Theta Kappa Honor Societies! Matthew participates as a member of our audit team and has a passion for risk management and human factors engineering. Always the mad scientist, Matthew pairs his professional life in regulatory affairs with hobbies in the culinary arts as he also holds a Butchers/Meat Cutters certificate from Vermont Technical College.

Email: matthew@fdaestar.com

Connect on Linkedin: http://www.linkedin.com/in/matthew-walker-214718101/

Before 510k clearance, 10 quality tasks you need to prevent unexpected delays Read More »

NSE letter: A CAPA plan for your 510k process

Cry, complain, call the reviewer…you might feel a little better, but you received an NSE letter, and tomorrow you still can’t sell your device.

NSE Letter NSE letter: A CAPA plan for your 510k process

Instead, try approaching an NSE letter like a CAPA investigation. What is the issue? The FDA determined that your device is not substantially equivalent to the predicate you selected. What is the root cause? There are four (4) possible root causes.

NSE Letter Cause #1: You failed to verify that the predicate is a legally marketed device.

If your predicate device is not legally marketed, you need to select a new predicate and resubmit. However, it is doubtful that your device would pass the refusal to accept the (RTA) screening process if the predicate was not legally marketed. If your predicate was not registered and listed with the FDA (check using this link), then you should have submitted a pre-sub request to determine if the agency has any problem with using the device you chose as a predicate. This is an essential question if the manufacturer is no longer in business, and the product is no longer for sale.

NSE Letter Cause #2: You failed to evaluate the substantial equivalence of your device’s intended use with the predicate.

The intended use of your predicate device is documented for every potential predicate since February 1992 on FDA Form 3881–which you can download along with the 510k clearance letter for the predicate. There is also an intended use documented for every device category in the applicable regulation for that device. This intended use is more generic than FDA Form 3881, but both are applicable. The FDA Form 3881 you submit for your device must be equivalent. I recommend a point-by-point comparison with regard to the following elements: 1) OTC vs. prescription use, 2) user, 3) patient population, 4) illness or medical condition, 5) duration of use, 6) environment of use and 7) target part of the body. Any difference can raise new issues of risk and may result in an NSE decision. However, the FDA typically will work with the company to modify the wording of FDA Form 3881 to ensure the intended use is equivalent or to make sure you provide clinical evidence to address the differences. In my pre-submission requests, I include a comparison document for the intended use to ensure that the FDA is aware of any differences in the intended use.

Cause #3: You failed to convince the FDA that technological differences do not raise different questions of safety and effectiveness.

Unless your device is identical in every way to the predicate device, you will have to persuade the FDA that differences do not raise questions of safety and effectiveness. At the beginning of the 510(k) process, it is helpful to document technological differences systematically. Specifically, this should include: 1) materials, 2) design, 3) energy source, and 4) other features. For each difference, you must justify why the difference does not raise different issues, or you must provide data to prove it. It is also possible that you were not aware of questions of safety and performance raised by technological differences. To avoid this problem, you can submit a detailed device description and draft labeling to the FDA in a pre-sub meeting request. If you ask questions about differences in a pre-sub meeting, you can avoid an NSE letter.

Cause #4: You failed to provide data demonstrating equivalence.

For each difference, you should determine an objective method for demonstrating that the difference is equivalent in safety and performance to the predicate. Your test method can be proposed to the FDA in a pre-sub request before testing. The FDA sees more than 3,000 companies propose testing methods to demonstrate equivalence each year. They have more experience than you do. Ask them in a pre-sub before you test anything. There may be a better test method, or you might need to adjust your test method. Sometimes results are unclear, but there might be another test you can perform to demonstrate equivalence, and then you can resubmit your 510k. Possibly you were unaware of the need to perform a test, and you were unable to complete a test within the 180 days the FDA allowed for submitting additional information. The good news is you now have all the time you need.

What is similar between all four causes of the NSE letter?

In all four root causes identified above, you could benefit greatly from the pre-sub meeting. Now you have an NSE letter, and you know which of the four reasons why your submission did not result in 510(k) clearance. However, the correction to your NSE letter may not be clear. Therefore, you should consider requesting a pre-sub meeting as quickly as you can. Most companies choose not to submit a pre-sub meeting request because they don’t want to wait 60-75 days. However, sometimes pre-sub meetings are scheduled sooner. In addition, 60-75 days is not as costly as receiving a second NSE letter.

Prevent a future NSE letter by requesting a pre-sub meeting

Regardless of your corrections for the current NSE letter, you should prevent future occurrences by planning to submit a pre-sub meeting request for every submission. I try to help clients gather all the information they need without a pre-sub meeting, but each new 510k reminds me why a pre-sub meeting is so valuable. You always learn something that helps you with the preparation of your 510k.

Help with Pre-sub meeting requests

The FDA published a guidance document for pre-sub meeting requests. If you need additional help, there is a webinar on this topic.

NSE letter: A CAPA plan for your 510k process Read More »

eCopy Guidance is Finally Updated by FDA

This blog summarizes the changes in FDA policy, released on April 27, 2020, as a new eCopy guidance for device manufacturers.

eCopy statement screen capture eCopy Guidance is Finally Updated by FDA

The date of the guidance above was updated, but the changes to the guidance do not represent any changes in policy. It is an update of contact information and a note regarding eCopies for EUA requests. In August 2016, I had a frustrating week where I had three (3) different submissions placed on eCopy hold by the FDA, three (3) separate times, for a total of nine (9) eCopy hold in the same week. That resulted in an extra $175 of FedEx charges and wasted six (6) USB flash drives. The biggest problem was the submission delay experienced by each client that week, which wasn’t very comfortable. This terrible, no good, dreadful week ultimately resulted in our company creating a new productized service–preparing FDA eCopies for clients and competitor consultants. We also became international experts on the FDA eCopy guidance. If my experience was this painful, there must be other people experiencing the same problem, or many people would experience this problem as soon as they tried to submit their next filing with the FDA.

For about 18 months, we helped many companies prepare FDA eCopy submissions, but then there was a government shutdown, and the FDA unofficially changed its policy. A printed paper copy of pre-submissions, 510ks, and De Novo classification requests would no longer be required. You only needed to print a paper copy of your cover letter and include an electronic copy on a CD, DVD, or USB flash drive. Despite this policy change, many clients still requested the printed copy because the FDA legislation was not yet changed, and there was no updated guidance. We explained to each client that the policy had changed, and only two clients asked us to print the paper copy anyway.

In October of 2018, the unofficial policy became official, but there was still no updated FDA eCopy guidance for us to share with clients. This situation frequency resulted in questions from clients about how they should phrase the “eCopy Statement” in their submission cover letter. The eCopy guidance that was current in 2018 stated that you should include the following phrase in your cover letter: “This submission includes an eCopy and a paper copy. The eCopy is an exact duplicate of the paper copy.” However, the paper copy consisted only of the cover letter, and the rest of the submission was solely provided in electronic format.

The FDA released a new pilot version of the eSubmitter software to help companies prepare 510(k) submissions and to streamline the FDA review of submissions in 2018. However, even electronic submissions prepared with eSubmitter must be sent by courier or mail to the FDA Document Center. In 2019, the FDA mentioned that they would be releasing new guidance documents regarding electronic submissions. Still, we were also told that the FDA has no near-term plans to enable companies to submit pre-submissions, 510ks, or De Novo classification requests to the FDA via an electronic submissions gateway (ESG).

Finally, on December 16, 2019, the FDA released a new eCopy guidance. The eCopy guidance was updated again on April 27, 2020, but the changes are updated to include emails, updated webpages, and a note regarding EUA requests.

July 2022 Update for the FDA eCopy process

The FDA created a Customer Collaboration Portal (CCP) for medical device manufacturers. Originally, the portal’s purpose was to provide a place where submitters can track the status of their submissions and verify the deadlines for each stage of the submission review process. Last week, on July 19, the FDA emailed all active FDA CPP account holders that they can upload both FDA eCopy and FDA eSTAR files to the portal 100% electronically. Since our consulting team sends out submissions daily, everyone on the team was able to test the new process. If you have a CCP account, you no longer need to ship submissions via FedEx to the Document Control Center (DCC).

What DID NOT change in the new eCopy guidance?

The file name requirements are identical. You can still organize your submission in volume structure or document-only structure. You are still limited to PDF file sizes of 50 MB. The eCopy will still be problematic for the FDA to upload if your submission exceeds 1 GB. You still need to ship your eCopy to the FDA Document Center unless you submit it to CBER instead of CDRH. You can and should continue to use the eCopy validation software module provided by the FDA to ensure that your eCopy will properly upload. The guidance barely changed in length; it’s just a few pages shorter now.

What DID change in the new eCopy guidance?

Only two things changed in the new guidance. First, there is no mention of an eCopy statement anywhere. Second, you must submit a cover letter in paper format (replaced by Zip file to FDA CCP), but it does not need to be included in the electronic format (that’s only recommended).

The “new” eCopy process is not any easier than the process we have used since February 2018. However, we did update our cover letter template. If you would like a copy, please register for our FDA eCopy webinar.

Should you create your own eCopies, or should you outsource?

If my job was Director of Regulatory Affairs (or a similar position), I would outsource. Regulatory managers in companies are swamped with trying to remain compliant with new and revised medical device regulations and changes to applicable standards.

Does it take one hour to create an eCopy?

No, we can prepare, validate, and upload an FDA eCopy in less than 15 minutes. This is only possible because we do this almost every day. On the last business day before the end of the FDA fiscal year (September 30), we average four (4) submissions on that day alone. We know exactly what to do, we know how to fix all of the most common errors, we know our validation software module is up-to-date, and we never run out of USB flash drives (replaced by Zip files to FDA CCP).

How long could it take you to create an eCopy?

If you haven’t done an eCopy in that past year, it could easily take you all day to create an eCopy. You have to read the new eCopy guidance document. You must format your submission according to the rules and proofread 100% of the folder and file names. You need to find a new flash drive. You need to save the submission on your USB flash drive. You need to run the eCopy validation software module.

Or you could just outsource your eCopy problems.  

eCopy Guidance is Finally Updated by FDA Read More »

Alternate 510k Pathway – Safety and Performance Based Pathway

Today the FDA released a press release announcing plans to implement an alternate 510k pathway called the “Safety and Performance Based Pathway.”

Alternate 510k Pathway Safety and Performance Based Pathway Alternate 510k Pathway   Safety and Performance Based Pathway

What is the current 510k pathway for clearance of medical devices?

The current version of the 510k pathway is defined in a guidance document on a substantial equivalence that was released on July 28, 2014. The pathway involves six questions that an FDA reviewer must answer before it can be determined whether a new device is equivalent to an existing device that is legally marketed in the USA. These are the six questions:

  1. Is the predicate device legally marketed?
  2. Do the devices have the same intended use?
  3. Do the devices have the same technological characteristics?
  4. Do different technological characteristics raise different questions of safety and effectiveness?
  5. Are the methods of evaluating new/different characteristics acceptable?
  6. Does the data demonstrate substantial equivalence?

Five (5) ways the FDA strengthened the current 510k pathway

Today the FDA released an 8-page presentation summarizing five (5) ways that the FDA strengthened the current 510k pathway during the past several years. The five ways are:

  1. Increased expectations for the content of a 510k submission
  2. Implementation of the refusal to Accept (RTA) policy
  3. Improved consistency and thoroughness of the 510k review process
  4. Elimination of the 510k pathway for Class III devices
  5. Eliminated the use of > 1,000 unsafe devices as legal predicates

You may have been complaining that 510k requirements seem to change constantly. Now you have proof that the changes to the 510k pathway are part of a strategic plan implemented over the past decade. Lawyers may argue that the resulting regulations go well beyond the intent of the original 510k legislation. This is completely true. The cumulative effect of implementing dozens of 510k guidance documents is that the official interpretation of the 510k section of the Food and Drug Act now has little resemblance to the original legal intent.

The original intent of the 510k legislation was to allow competitors to copy an existing device that is legally marketed in the USA. Cumulative changes to a device that existed in 1976, eventually result in a completely new device. The word “equivalent” has been perverted to such an extent that thousands of devices now exist that do not even remotely resemble devices from 1976. The FDA recognized this around 2007, and the US device regulations began to “strengthen.”  

What is the basis for the Alternate 510k Pathway?

The basis for the alternate 510k pathway is the submission of data that is safety and performance-based instead of comparison to an older predicate. In addition, the new pathway will enable you to make comparative claims by demonstrating that the new subject device meets or exceeds the safety and performance criteria. There is also a goal to use the pathway as a potential method of harmonizing the US medical device regulatory process with other global medical device regulations. The new process, combined with improved post-market surveillance, will complement the FDA’s work on NEST by allowing the FDA to rapidly require the implementation of risk controls to address identified safety issues.

What is the expected timeline for the implementation of the Alternate 510k Pathway?

The alternate 510k pathway has been in development for quite some time. Jeff Shuren first announced the plan to create the alternate 510k pathway at AdvaMed’s MedTech conference in San Jose, California, in September 2017. On Monday, December 11, 2017, the FDA announced that draft guidance would be released in Q1 of 2018. On April 12, 2018, the FDA finally released the draft guidance for public comment.

The FDA intends to release final guidance for the new alternate 510k pathway in early 2019. This pathway will initially be limited to “well-understood device types”–probably as a 510k pilot program. You can expect this new pathway to be released in a similar way to the Special 510k expansion pilot and the Quik 510k pilot. That final guidance will be released, and the pilot will begin immediately after the release of the guidance.

Is this new process likely to require significant changes to future 510k submissions?

The phrase “significant changes” is subjective, but if you look at the current 20 required sections of a 510(k) submission, there is only one section that would be required to change for the new alternate 510k pathway. Specifically, section 12 is currently used for a substantial equivalence comparison. This section would not be applicable under the alternate 510k pathway. Under the alternate 510k pathway, you can expect the FDA to require at least a summary of the safety and performance data to be submitted for approval of the subject device.

Another change you can expect is that all devices submitted under the alternate 510k pathway will be required to have a benefit-risk analysis in accordance with the corresponding FDA guidance. This new guidance was released on September 25, 2018, as a draft. However, a benefit-risk analysis is required for De Novo applications, CE Marking applications, and, logically, the FDA will also require this for 510k submissions that do not rely upon equivalence to the predicate device.

More Information on the Medical Device Safety Action Plan

The FDA created a webpage on its site, providing information about the Medical Device Safety Action Plan. The page includes several hyperlinks to documents with more information. Below are a few of the relevant links:

The FDA also indicated that a new guidance for De Novo applications would be released in a couple of weeks. Please subscribe to our blog, and you will receive notification of a blog in response to that guidance when it is released.

Alternate 510k Pathway – Safety and Performance Based Pathway Read More »

Quik 510k Pilot – Explanation of Quik 510k Pilot

There are 38 product classification codes that the FDA selected for the Quik 510k Pilot program to evaluate version 3 of the eSubmitter software.

510k Quik Pilot Product Codes 1 Quik 510k Pilot   Explanation of Quik 510k Pilot

What are the three (3) advantages of the new Quik 510k pilot program?

There are three (3) advantages of using the eSubmitter software as part of the Quik 510k pilot.  The first advantage of using the eSubmitter software is that the refusal to accept (RTA) process will be eliminated. This change is enormous because nearly 50% of submissions are rejected during the RTA screening process. The hope is that the eSubmitter software will prevent companies from submitting submissions that are missing required content, and therefore the RTA process will not be needed. However, we have seen many submissions placed on hold for technicalities rather than sub-standard submissions. Consequently, it will be fascinating to see the FDA reported outcomes from the Quik 510k pilot.

The second advantage of using the eSubmitter software is that the reviews will be interactive. This means that reviewers are not expected to have any additional information (AI) requests. This also means that submitters will need to respond to questions from reviewers quickly. For example, I have received a call on Friday afternoon after 5:00 pm EDT asking if I could revise to document and email that document to the reviewer by Monday morning. This is an extreme example, but 48-72 hours is typical for a required turn-around during interactive reviews.

The third advantage of using the eSubmitter software is that the FDA is targeting completion of their 510k review within 60 days. This 30-day reduction may seem huge, but the FDA already cut 15 days off its review timeline by eliminating the RTA screening. Second, the FDA picked 38 product classification codes that should not have difficulty reviewing in 60 days. Not all product classifications have the same amount of testing data required, and I do not expect the FDA to be able to review all product classification codes in 60 days–even with eSubmitter.

Although the Quik 510k pilot mentioned that submissions would be zipped, eSubmitter is also designed for electronic submissions through an electronic submissions gateway (ESG). An ESG has the added advantage that you will not need to ship your submission via FedEx. This advantage will gain you only a maximum of 24 hours, but I wish I had those 24 hours last week. Every year, in the last week of September, all the small businesses with small business qualifications try to submit their 510k before the end of the fiscal year (i.e., September 30). This year I had four clients that were in this position. One was unable to get the data they needed to complete their submission before September 30. The other three were making last-minute changes up until the afternoon of Thursday, September 27. One of those submissions was extremely challenging because the submission included video files that exceeded 1GB in total. Therefore, I called CDRH’s eCopy Program Coordinators at 240-402-3717. They were accommodating. They said that it would be best to provide two identical eCopies or to save the MISC FILES and STATISTICAL DATA folders on a separate flash drive. The reason for this is that very large submissions can take days to upload into the CDRH database. Therefore, the picture below shows you what my final solution was for the three submissions this week. The De Novo submission had to be split.

20180927 121031 Quik 510k Pilot   Explanation of Quik 510k Pilot

What our firm has done to take advantage of the Quik 510k pilot

If you have a product with any of the 38 product classification codes listed above, and you need to submit a 510k in the next six months, you are very fortunate. The FDA will prioritize your submission, and you are likely to be able to get your device cleared in 60 days or less. Our firm is very anxious to take part in this pilot because the FDA intends to require the eSubmitter software for all submissions in the future, and we expect other product classification codes to be added to the pilot over time. We process dozens of 510k submissions each year, and mastering the nuances of the software is critical to our continued success. I already downloaded the software and installed it onto my computer. I also created a complete submission as a test. eSubmitter saved several hours in the preparation of a 510(k) from the typical 40 hours the process takes. Therefore, I expect the implementation of new eSubmitter software to a triple win for the FDA, clients, and our firm. I plan to request that the FDA add De Novo submissions next to this pilot. The reason is that De Novo submissions typically have more content, and the content is more variable. I think this would be an extremely challenging test for eSubmitter, and the relatively small volume of De Novo submissions would limit the impact upon FDA resources.

Changes to eCopy Requirements in 2018

In 2017, the FDA indicated that eSubmitter software was going to be revised, and it would be approximately two years before companies would be able to submit a 510k electronically to the FDA. Until then, companies must ship an electronic eCopy and a paper copy to the FDA Document Control Center (DCC). The eCopy guidance states, “An eCopy is accompanied by a paper copy of the signed cover letter and the complete paper submission.” However, the FDA’s eCopy guidance has not been updated since December 3, 2015. There are some unofficial changes to the policy, and the FDA no longer requires the complete paper submission. Instead, you can submit an eCopy accompanied by a paper copy of the signed cover letter.

Before February 2018, we would print 1,000+ pages for each 510k submission, pack two 3” three-ring binders in 12”x12”x6” ULine boxes and ship the box to the FDA overnight via FedEx. We typically would charge $400 for this eCopy service. After the unofficial policy change, all of our 510k submissions consist of a paper copy of the cover letter and an eCopy on a USB flash drive. We only charge $150 for the FDA eCopy service, and 100% of our eCopy submissions have been uploaded without problems this year.

What is the difference between creating an eCopy and submitting it with eSubmitter (cited from FDA website)?

There are four differences between eSubmitter and eCopies:

  1. An eSubmission package contains PDF attachments and XML file types. The XML files are intended for CDRH IT systems to process the application. Reviewers will not see these XML files. 
  2. The parts of the eCopy guidance that describe the structure of a 510(k) submission will not apply to the Quik Review Program Pilot.
  3. An eSubmission is organized according to the layout of the template, which places administrative documents (e.g., Form 3674, the 510(k) Summary, the Truthful and Accurate statement) at the end of the submission because their applicability is determined based on the answers to questions in the body of the template (e.g., Form 3674 is only required if the applicant indicates clinical data are included).
  4. Electronic signatures are used in the submission (e.g., on the Truthful and Accurate statement), rather than physical signatures.

eSubmitter Template Options

For device 510k submissions, the FDA’s eSubmitter gives you three options:

  1. Template Version 1.3, for In Vitro Diagnostic 510k submissions to CDRH only, allows you to create a 510k submission and the eSubmitter software will package your submission in a specially formatted zip folder that you can save to a compact disc (CD), digital video disc (DVD) or flash drive. Then you must print a paper copy of your signed cover letter and ship the eCopy created by eSubmitter with your paper copy of the cover letter to the FDA DCC.
  2. Template Version 1.2.1, for Non-In Vitro Diagnostic 510k submissions that are among the 1,000+ other product classifications not included in the Quik 510k pilot (CDRH: Medical Device eCopies), you can create a 510k submission and the eSubmitter software will package your submission in a folder for you. You can then copy the contents of that folder to a compact disc (CD), digital video disc (DVD), or flash drive. Then you must print a paper copy of your signed cover letter and ship the eCopy created by eSubmitter with your paper copy of the cover letter to the FDA DCC.
  3. Template Version 3.2, for Non-In Vitro Diagnostic 510k submissions that are among the 38 product classification codes that are listed above for the Quik 510k pilot program. This allows you to create a 510k submission, and the eSubmitter software will package your submission in a specially formatted zip folder that you can save to a compact disc (CD), digital video disc (DVD), or flash drive. Then you must print a paper copy of your signed cover letter and ship the eCopy created by eSubmitter with your paper copy of the cover letter to the FDA DCC. This template is unique to the Quik 510k pilot program. There is a red bar that appears at the top of the screen:

“This template should only be used to construct a submission if you are submitting it as part of the Quick Review Pilot. All others may use the content of this template as a reference to aid in constructing an eCopy. If you are not part of the Quick Review Pilot, do not construct a submission with this template, it will be rejected.”

When you create your eCopy, then you will need to create a volume-based or non-volume based submission in accordance with the eCopy guidance. The volume folders and/or files are saved to a compact disc (CD), digital video disc (DVD), or flash drive. Then you must print a paper copy of your signed cover letter and ship the eCopy you created with your paper copy of the cover letter to the FDA DCC.

Warning Symbol Quik 510k Pilot   Explanation of Quik 510k PilotWarning: If you are using Windows 10, and you save your eCopy or eSubmitter zip folder on a flash drive, Windows 10 will automatically create a hidden system folder titled “System Information Volume.”  This folder is created as a security feature to enable you to recover accidentally deleted content. However, this folder results in an error when the FDA attempts to upload your submission automatically. Therefore, you must remove this hidden system folder. Instructions for this can be found on our website page about eCopy hidden system files.

Quik 510k Pilot – Explanation of Quik 510k Pilot Read More »

Biocompatibility testing questions answered in pre-submission requests

This article is a copy of my responses to someone that submitted biocompatibility testing questions in preparation for a 510k pre-submission webinar.

510k pre submission webinar February 22 for LinkedIn.jpg 1024x459 Biocompatibility testing questions answered in pre submission requests

Can you please answer the following questions related to biocompatibility for a 510k pre-submission meeting request?

This was the request by a person that registered for a 510k pre-submission webinar that was recorded in February 2018. The person asked some great questions that are very similar to other clients I work with. They also requested the biocompatibility testing questions in a way that did not divulge any confidential information–other than to indicate they live in Germany. Therefore, I am sharing my email response with you. Please register for this webinar and submit your questions. Questions are entered in an open text box, and you have room to ask multiple questions.

Biocompatibility testing question #1: Does the FDA now already ask for the AET (Analytical evaluation threshold) for chemical analyses?

This is exactly the type of biocompatibility testing questions you should be asking in a 510k pre-submission meeting. If you ask, “What biocompatibility testing is required for a 510k?” You will only receive a reference to the FDA guidance for biocompatibility. A better approach is to ask a biocompatibility testing lab to provide a Biological Evaluation Plan (BEP). Then you can submit your plan as part of the 510k pre-submission meeting request and include this question regarding the section of the BEP where you explain how you intend to perform chemical characterization of your device and how you intend to determine whether the materials represent risks related to sub-acute toxicity and sub-chronic toxicity endpoints.

Biocompatibility testing question #2: How can I avoid time-consuming genotoxicity studies for FDA?

Typically if you perform the “Big 3” (i.e., cytotoxicity, irritation, and sensitization), and then you perform chemical characterization, you are often able to prepare a Biological Evaluation Report to explain why there are no identified compounds in the chemical characterization that would warrant performing the genotoxicity studies. This is also often true for acute toxicity testing and sub-chronic toxicity testing. This often saves > $10K. To verify the FDA will accept this approach, you will typically provide a biological evaluation plan (BEP) as part of your pre-submission request. Your biocompatibility testing questions should specifically reference your BEP.

Question #3: And how can I face FDA with a cytotoxic wound dressing but which passed irritation, sensitization, genotox, and pyrogenicity tests?

I had a product that contained aluminum. Aluminum is cytotoxic to the cell line that is used in the cytotoxicity testing. However, aluminum does not have a high level of toxicity for the route of administration for that product. You should identify the reason why your product is cytotoxic and then explain why the device is no toxic for the intended use and duration of contact. This would normally be part of that BEP mentioned above.

Biocompatibility testing question #4: Which genotoxicity tests are state of the art for the FDA?

There are three ways to determine that. One is to look in the recognized standards database on the FDA website. The second is to review the FDA guidance on biocompatibility and application of ISO 10993-1. Finally, you can ask the FDA about the suitability of another test you want to perform during a pre-sub. If they prefer a different test, they will say so in an email response, and they are available for discussion by conference call during the pre-sub meeting to clarify their response.
I did not answer this question outright, because biocompatibility requirements change over time. This is also true for other verification testing standards. In fact, for one 510k project, I had seven different standards change just before submission. During a pre-submission meeting, the FDA should make you aware of coming changes to these tests. Also, better biocompatibility testing labs are aware of the changes before they are implemented. This is because the lab managers participate in the committees that revise and update international standards.

Will the meeting be recorded since I live in Germany?

Yes, all of my webinars are recorded. You will receive an email with a link for downloading the recording within 24 hours of completing the original live webinar or at the time of purchase if you are purchasing one of our previously recorded webinars. You can also schedule calls with me as a follow-up using the following link: http://calendly.com/13485cert/30min.

Biocompatibility testing questions answered in pre-submission requests Read More »

Risk Management Requirements – 510k vs DHF

What are the differences between 510k risk management requirements and risk management requirements for your Design History File (DHF)?

Risk management requirements integration with design

Last week I presented a free webinar on how to combine risk management with design controls when planning to submit a 510k. Many questions were asking what the design control and risk management requirements are for a 510k.

What are the 510k design control requirements?

There is no specific part of the regulations stating what the 510k design control requirements are. However, some aspects of the DHF are required as 510k design control documentation, but not necessarily in the exact form as maintained in the DHF. For example, Design Inputs and Design Outputs are presented as applicable recognized standards and design specifications, while others will remain precisely the same (i.e., verification and validation test reports).

What are the Risk Management Requirements in a 510k?

For 510k submissions, the only risk management requirements are the inclusion of risk documentation for devices containing software of at least moderate level risk. There are some exceptions to this as well, though, based on a few special control guidance documents—especially when the submission type is an abbreviated 510k. This is article identifies which of the DHF and RMF elements are 510k design control requirements and 510k risk management requirements.

Quality system requirements for design controls

Design Controls are identified in 21 CFR 820.30. Every manufacturer of any Class II or Class III devices and certain Class I devices (Class I devices with software, tracheobronchial suction catheters, surgeon gloves, protective restraints, radionuclide applicators, radionuclide teletherapy devices) need to control design per this regulation. The requirement for a Design History File is item j) and states:

“Each manufacturer shall establish and maintain a DHF for each type of device. The DHF shall contain or reference the records necessary to demonstrate that the design was developed following the approved design plan and the requirements of this part.”

The “requirements of this part” refer to the other bullets in 21 CFR 820.30 which can be summarized as:

a) Establish and maintain procedures to control the design of a device.

b) Design and Development Planning – Each manufacturer shall establish a plan that describes the design and development activities and defines responsibilities for implementation.

c) Design Inputs – Manufacturers need to ensure design requirements relating to a device are appropriate and address the intended use of the device.

d) Design Outputs – Design outputs need to be documented in terms that allow an adequate evaluation of conformance to design input requirements. Design outputs that are essential for the proper functioning of the device should be identified.

e) Design Review – Formal documented reviews of design results should be planned and conducted at appropriate stages of device development.

f) Design Verification – Design verification confirms that the design output meets the design input requirements.

g) Design Validation – Design validation shall be performed under defined operating conditions on initial production units or their equivalents. It shall ensure that devices conform to defined user needs and meet the intended use of the device.

h) Design Transfer – Design transfer documentation shall ensure that the device design is correctly translated into production specifications.

i) Design Changes – changes should be identified, documented, validated/verified, reviewed, and approved before their implementation.

The Design History File is intended to be a repository of the records required to demonstrate compliance with your design plan and design control procedures. While companies are required to create and maintain this documentation according to the FDA regulation, not all of the documentation will be reviewed as part of the 510k. The following table compares the elements that comprise a DHF with the 510k design control requirements.

DHF Element 510k Design Control Requirements
Design Plan Not Required
User Needs & Design Inputs

Declaration of Conformity

User needs are design requirements that require design validation (e.g., adequacy of user training, and safety/performance of the device for the indications for use). Some design inputs will appear in the form of standards in the FDA eSTAR template. If you are declaring conformity with these standards, a Declaration of Conformity is automatically created in the FDA eSTAR template.

Design Outputs

Device Description (Section 11)

The Device Description lists the specifications of the device, and your Design Outputs document will help populate the Device Description. This can include drawings, pictures, or written specifications that describe your device.

Labeling

Proposed Labeling (Section 13)

The labeling is usually considered part of the Design Outputs within the DHF and is included specifically in the labeling section of the 510(k) submission. This includes both the Instructions for Use and any Package Labeling.

Verification and Validation Protocols

Not Required

You do not have to include the protocols, but the reviewer may ask to see them if they have any questions when reviewing the reports.

Verification and Validation Reports

Sterilization (Section 14)

Biocompatibility (Section 15)

Software (Section 16)

Electrical Safety and EMC (Section 17)

Bench Performance Testing (Section 18)

Animal Performance Testing (Section 19)

Clinical Performance Testing (Section 20)

Of course, not all of these sections will be applicable to every device. Still, you should include all relevant validation test reports within your submission in the appropriate part of the 510k. Typically, each of these sections will have a cover sheet that outlines the reports that are included within the section, and then you can just include the report from the DHF in its entirety behind the cover sheet in that section.

Process Validation Only required for sterilization validation typically, but there are exceptions for novel materials and coatings
Work Instructions Not Required for 510k
Design Review Meeting Minutes Not Required for 510k
Design Trace Matrix Only required for software
Risk Management File Sometimes – See Risk Management File Table Below
Post-Market Surveillance Plan Not Required, but a few exceptions for high-risk devices
Clinical Data Summary Required only if used to demonstrate safety and efficacy
Regulatory Approval It Will result from 510k Clearance, so nothing is to be included in the 510k submission.

510k Risk Management Requirements

Regarding the FDA regulations for risk management, there is a requirement under the Design Validation section of 21 CFR 820.30 that states:

“Design validation shall include software validation and risk analysis, where appropriate.”

For FDA compliance and CE Marking, both recognize ISO 14971 as the standard for risk management. FDA recognizes ISO 14971:2007 whereas EN ISO 14971:2012 is the European National version for CE Marking. Rob Packard wrote an article describing the contents of the risk management file as well as the specific differences in the requirements between the FDA and CE Marking with regard to ISO 14971.

For your 510k submission, the FDA only requires risk management documentation to be included if the product contains software, and the risk is at least a level of “moderate concern”. There are some other cases when risk management is required by special controls guidance documents, but even when it is required, you only have to submit your risk analysis. The table below describes the risk management requirements in greater detail.

RMF Element 510k Risk Management Requirement
Risk Management Plan Not Required
Hazard Identification

510ks with Software Only (Section 16)

Hazard Identification is only required for devices that have a software component. It is not required for most other devices.

Risk Assessment

510(k)s with Software (Section 16)

Certain Special Controls Guidance

The Risk Assessment is only required to be included in your device contains software, or if a special controls guidance document specifically requires a risk assessment. It is not required for other 510ks.

Risk Control Option Analysis Software and Certain Special Controls Guidance
Risk Control Verification and Validation

Sterilization (Section 14)

Biocompatibility (Section 15)

Software (Section 16)

Electrical Safety and EMC (Section 17)

Bench Performance Testing (Section 18)

Animal Performance Testing (Section 19)

Clinical Performance Testing (Section 20)

This will not be any additional or special documentation specific to Risk Management and was already included in the DHF breakdown above. Still, the verification and validation also relate to risk management in ensuring that the risks have been adequately mitigated.

Risk-Benefit Analysis

Not Required for 510(k)

Risk-Benefit analyses are only required for De Novo applications, Humanitarian Device Exemptions, and PMAs.

Informing Users and Patients of the Risks

Labeling (Section 13)

Part of the risk management will appear in the Labeling section of the 510k as warnings, contraindications, and precautions within the Instructions for Use and Package Labeling.

Risk Management Report Not Required

Special Controls Guidance Documents with Risk Management Requirements

Your first step in preparing your 510k submission is to search the FDA Guidance Document Database to determine if there is an applicable guidance document for your device. You can read another blog we wrote to explain Special Controls Guidance documents, and how to determine if one applies to your device. The following list provides examples of Class II Special Controls Guidance documents that require risk analysis to be included within the 510k:

When there are 510k risk management requirements, the special controls guidance document will typically state, “We recommend that the summary report contain:

An identification of the Risk Analysis method(s) used to assess the risk profile in general as well as the specific device’s design and the results of this analysis. (Refer to Section 6 for the risks to health generally associated with the use of this device that the FDA has identified.)

Discussion of the device characteristics that address the risks identified in this class II special controls guidance document, as well as any additional risks identified in your risk analysis.”

The special controls guidance will also identify risks to health that have been identified for products of that type, which you should be sure to include in your risk analysis as appropriate.

More Information on Design Control and Risk Management Requirements

Hopefully, you are now able to determine which elements of your DHF are 510k design control requirements and which elements of your RMF are 510k risk management requirements. If you would like more information about how to implement design controls and risk management within your product development process, please consider registering for one of our training webinars:

If you need any further information or specific assistance with your 510k submission, please feel free to send me an email at mary@fdaecopy.com or schedule a call with our principal consultant, Rob Packard. He can answer any of your medical device regulatory questions.


Click here to schedule a 15 minute call 300x62 Risk Management Requirements   510k vs DHF

Risk Management Requirements – 510k vs DHF Read More »

Scroll to Top