Rimsys Announces Rimsys AI. Smarter, Faster, and Built for Medtech!

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Man and woman looking at a laptop screen together in an office setting.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
eBooks

The beginner's guide to the FDA De Novo classification process

April 3, 2026

4 min read

This article is an excerpt from The beginner's guide to the FDA De Novo classification process ebook.

Contents

Introduction

Congratulations, you have successfully developed a new medical device! Now you need to take it to market. Normally in the United States this would mean completing a 510(k) submission. However, the 510(k) relies on “substantial equivalence”—a comparison to a similar device already on the market (also called a predicate device) to assess the risk profile of the new device. What if your device is totally new, and there isn’t a similar device to compare it to? Enter the FDA De Novo process. The De Novo process provides a pathway to market for novel devices with a low to medium risk profile.

What does De Novo mean?

According to the Merriman-Webster dictionary, de novo is a Latin word meaning “as if for the first time; or anew.” Perfectly fitting that the FDA uses this term “De Novo” to describe market approval requests for new medical devices or technology where there is no comparable predicate device on the market.

Chatper 1: What is an FDA De Novo request?

The Food and Drug Administration Modernization Act of 1996 provided the FDA with the authority to create the De Novo Classification Process. It's a process that uses a risk-based strategy for a new, novel kind of medical device, in vitro diagnostic, or medical software solution whose type has previously not been identified and/or classified. It’s a process by which a novel medical device can be classified as a Class I or Class II device, instead of being automatically classified as Class III, which may not be appropriate. Before the implementation of the De Novo process in 1997, all the “not substantially equivalent” (NSE) products were required to be initially classified as a Class III device. But for a lot of devices, this risk class didn’t really make sense. The De Novo process provides a pathway for more accurate classifications of novel, lower-risk devices.

October, 2021, the FDA released a final guidance document "De Novo Classification Process (Evaluation of Automatic Class III Designation)" to provide guidance to the requester (also known as the manufacturer) and the FDA on the process for the submission and review of a De Novo Classification Request under section 513(f)(2) of the Federal Food, Drug, and Cosmetic Act (the FD&C Act). This process provides a pathway to an initial Class I or Class II risk classification for medical devices for which general controls or general and special controls, provide a reasonable assurance of safety and effectiveness, but for which there is no legally marketed predicate device. This guidance document replaced the "New Section 513(f)(2) – Evaluation of Automatic Class III Designation, Guidance for Industry and CDRH Staff" document, dated February 19, 1998.

Consistent with the final rule, the FDA updated the guidance documents below to provide recommendations for submitting De Novo requests, as well as criteria and procedures for accepting, withdrawing, reviewing, and making decisions on De Novo requests, effective January 3, 2022.

The 510(k) and the De Novo processes are similar in that they are both pathways to market for medical devices with low to moderate risk, which is Class I and Class II. The biggest difference between the two is that the 510(k) heavily relies on the concept of "substantial equivalence" to an existing medical device. You must prove this to get the clearance of your 510(k) submission. In the De Novo process, there isn’t a product currently on the market that is “substantially equivalent” to yours, so it’s like starting with a clean slate. For more on the 510(k) process, see our Beginner’s Guide to the 510(k) ebook.

A result of the De Novo process to be aware of is that a successful submission will lead to a new predicate device type that someone else can reference to bring their product to market through the 510(k) process. You’ve done all the work, so now it’s available for anyone to use to provide "substantial equivalence".

De Novo history/timeline

1997 Congress enacted a De Novo classification process to help limit the unnecessary use of FDA and industry resources on devices for which general controls (or general and special controls) would provide a reasonable assurance of safety and effectiveness because a predicate device could not be identified.
1998 Initial De Novo Guidance Document was released.
2012 Congress simplified the De Novo Guidance Document into a 2-step process:
1. The requestor may submit a De Novo request directly.
2. The FDA would then decide whether to classify the device from Class III to Class II or Class I for the new classification and regulation.
2014 A draft was created of the De Novo Guidance Document to propose policy and procedures to implement the changes to the De Novo program from FDASIA (The Food and Drug Administration Safety and Innovation Act) of 2012..
2016 Congress further simplified the De Novo process by not requiring a 30-day submission turnaround after receiving an NSE (non-substantially equivalent) determination.
2017 The final Guidance (De Novo Program Guidance) Recommendations was issued.
2018 The FDA proposed a new rule to implement a De Novo Classification Process and define the scope of regulatory procedures when classifying and reclassifying medical devices.
2019 The final De Novo Program Guidance document was made public in September.
2021 The FDA issued a final ruling on the De Novo classification rule in October for implementing a classification process.

Preparing a De Novo request

1. Do your research! Be sure to complete all the necessary research prior to your submission. You want to be sure that your device is not substantially equivalent to an existing device. Resources to review include:

  • The Center for Devices and Radiological Health (CDRH)
  • U.S. FDA Device Classification Database
  • Device Classification Under Section 513(f)(2)(De Novo)

2. A De Novo request can be submitted with or without a preceding 510(k). There are two options for when you can submit a De Novo request:

Option A: After receiving a not substantially equivalent (NSE) determination (that is, no predicate, new intended use, or different technological characteristics that raise different questions of safety and effectiveness) in response to a 510(k) submission.

Option B: If you’ve determined, after extensive research, that there is no legally marketed device on which to base a determination of substantial equivalence.

3. Be sure all fees are paid to the FDA in advance of submitting a De Novo request. The FDA’s fiscal year begins in October and runs through the following September. Fees have increased each year since they were introduced, but the FDA’s percentage of reviews completed within the 150-day window has increased as well.

Fiscal year De Novo requests received % of requests completed in 150 days User fee Small business fee
2018 56 50% $93,229 $23,307
2019 61 55% $96,644 $24,161
2020 69 60% $102,299 $25,575
2021 63 65% $109,697 $27,424
2022 70% $112,457 $28,114

A business that is qualified and certified as a “small business” is eligible for a substantial reduction in most of the FDA user fees, including De Novo. The CDRH is responsible for the Small Business Program that determines whether a business is qualified. 

Medical Device User Fee Amendments (MDUFA) guidance documents can provide more detailed information about all FDA user fees.

4. The initial request process serves only to determine if the De Novo request is administratively acceptable based upon the Acceptance Checklist. The initial acceptance is followed by substantive review which will determine the final risk classification of your device.

5. A Pre-Submission (Pre-Sub) is a formal written request for feedback from the FDA that is provided in formal written form, and then followed by a meeting. Although a Pre-Sub is not required prior to a De Novo request, it can be extremely helpful to receive early feedback, especially for devices that have not previously been reviewed under a 510(k). If you think you would like to submit a pre-sub first, there are suggested guidelines for submission you should consider:

  • Describe your rationale for a Class I or Class II classification for your device.
  • Provide the search results of FDA public databases and other resources used to determine that no legally marketed device and no classification for the same device type exists.
  • Provide a list of regulations and/or product codes that may be relevant.
  • Provide a rationale for why the subject device does not fit within and/or is different from any identified classification regulations, based on available information.
  • Identify each health risk associated with the device and the reason for each risk.
  • Briefly describe any ongoing and/or planned protocols/studies that need to be completed in order to collect the necessary data to establish the device’s risk profile.
  • Provide information regarding the safety and effectiveness of the device. Cite the types of valid scientific evidence you anticipate providing in your De Novo request, including types of data/studies relating to the device’s safety and effectiveness.
  • Briefly describe any ongoing and/or planned protocols/studies that need to be completed to collect the necessary safety and effectiveness data.
  • Provide protocols for non-clinical and clinical studies (if applicable), including how they will address the risks you anticipate and targeted performance levels that will demonstrate that general controls or general and special controls are sufficient to provide reasonable assurance of safety and effectiveness.
  • Share any proposed mitigation measure(s)/control(s) for each risk, based on the best available information at the time of the submission. Highlight which mitigations are general controls and which are special controls and provide details on each.
  • Include any other risks that may be applicable, in addition to those identified in the Pre-Sub, given the indications for use for the device.
  • If applicable, provide any controls that should be considered to provide a reasonable assurance of safety and effectiveness for the device.
  • Provide any non-clinical study protocols that are sufficient to allow the collection of data from which conclusions about device safety and/or effectiveness can be drawn. These protocols should address whether the identified level of concern is the appropriate level of concern for the device software, and if any additional biocompatibility and/or sterility testing is required.
  • If clinical data is needed, provide information to show that the proposed study design and selected control groups are appropriate?

6. The FDA will attempt to review the De Novo request submission within 15 calendar days of receipt of the request to make a determination that the submission is declined or accepted for review. If they are unable to complete the review within the 15 days, your submission will automatically move to “accepted for review” status. https://www.fda.gov/regulatory-information/search-fda-guidance-documents/de-novo-classification-process-evaluation-automatic-class-iii-designation

7. There are times when the FDA will refund your application fee. They have created a guidance document “User Fees and Refunds for De Novo Classification Requests” for the purpose of identifying:

  1. the types of De Novo requests subject to user fees
  2. exceptions to user fees
  3. the actions that may result in refunds of user fees that have been paid

When is a De Novo request subject to a user fee?

De Novo request submission type De Novo fee required
Original De Novo request Yes
Additional information for a De Novo request that has not yet been accepted No
Additional information for a pending De Novo request No
De Novo request intended solely for pediatric population No
De Novo request for a device for which the previous De Novo request was declined Yes

When will the FDA refund a De Novo user fee?

FDA determination or submitter action FDA refund?
I qualify for a fee exception provided by section 738(a)(2)(B)(v) of the FD&C act. Yes
FDA declines my De Novo request. No
I withdraw my De Novo request after acceptance for review. No
FDA considers my De Novo request to be withdrawn after acceptance for review. No
I fail to submit a valid eCopy before my original De Novo request is accepted for review. Yes, upon request
I fail to submit a valid eCopy for a De Novo amendment or supplement. No
FDA determines my submission does not meet the acceptance criteria during review. Yes, upon request

What fee must be paid for a new device submission following a De Novo “decline” determination?

Submission type Is a fee required?
New De Novo request. Yes. You must pay the applicable fee for a De Novo request.
510(k) Yes. You must pay the applicable fee for a 510(k).
Reclassification petition No
PMA Yes. You must pay the applicable fee for a PMA.
HDE No

Chatper 2: Contents of a De Novo request

To continue reading this eBook including a detailed walk-through of all the Traditional 510(k) components, submission requirements and timelines, and an overview of the other 510(k) forms including the Abbreviated 510(k) and the Special 510(k), please register to download the full version.

Webinars

A medtech imperative: better regulatory information management

April 3, 2026

Case Studies

Global dental adhesives manufacturer reduces essential principles & GSPR maintenance by 99%

April 3, 2026

eBooks

The RIM buyer's guide for medtech companies

April 3, 2026

Webinars

Integrate your regulatory stack for outsized results

April 3, 2026

eBooks

The ultimate guide to the medical device single audit program (MDSAP)

April 3, 2026

4 min read

This article is an excerpt from The ultimate guide to the medical device single audit program (MDSAP) ebook.

Table of contents

What is MDSAP?

The Medical Device Single Audit Program (MDSAP) was designed and developed to allow a single audit of a medical device manufacturer to be applied to all country markets whose regulatory authorities are members of the program. The MDSAP provides efficient and thorough coverage of the standard requirements for medical device manufacturer quality management systems, and requirements for regulatory purposes (ISO 13485:2016). In addition, there are specific requirements of each medical device regulatory authority participating in the MDSAP that must be met:

  • Conformity Assessment Procedures of the Australian Therapeutic Goods (Medical Devices) Regulations (TG(MD)R Sch3)
  • Brazilian Good Manufacturing Practices (RDC ANVISA 16)
  • Medical Device Regulations of Health Canada (ISO 13485:2003)
  • Japan Ordinance on Standards for Manufacturing Control and Quality Control of Medical Devices and In Vitro Diagnostic Reagents (MHLW Ministerial Ordinance No 169)
  • Quality System Regulation (21 CFR Part 820), and specific requirements of medical device regulatory authorities participating in the MDSAP program.

This means that a report from a single MDSAP audit of a medical device manufacturer would be accepted as a substitute for routine inspections by all the member Regulatory Authorities (RAs) across the world. There are currently five participating Regulatory Authorities (RA) representing the following countries: Australia, Brazil, Canada, Japan and the USA.

In April, 2021, the RAs released an “Audit Approach” document (MDSAP AU P0002.006) that combines the formerly separate MDSAP Audit Model and Process Companion documents into a single guidance document. It includes guidance for assessing the conformity of each process and includes an audit sequence, instructions for auditing each specific process, and identifies links that highlight the interactions between the processes.

History of MDSAP

In March 2012 the US FDA announced that they had approved a final pilot guidance document “Guidance for Industry, Third Parties and Food and Drug Administration Staff: Medical Device ISO 13485:2003 Voluntary Audit Report Submission Pilot Program.” This allowed the owner or operator of a medical device manufacturing facility to be removed from FDA’s routine inspection work plan for 1 year upon completing a ISO 13485:2003 audit. This guidance document went into effect in June 2012, and was intended as an interim measure while a single audit program was being developed.

This pilot program was not very successful and few companies signed up because they did not see any advantage in participating. The manufacturer had to pay for a third party to inspect their facilities, generate a report, and share the inspection results back to the FDA. Many companies were reluctant to contract “someone else” to perform their inspection when they could easily wait for the FDA to conduct an inspection for free.

During its inaugural meeting in Singapore in 2012, the International Medical Device Regulators Forum (IMDRF) appointed a working group to develop a set of documents for a harmonized third-party auditor system. Hence, the “Medical Device Single Audit Program” (MDSAP) was formed. The concept was similar to the FDA’s original idea of creating a third-party auditor to help reduce their workload of performing regulatory audits of medical device manufacturers’ quality management systems. This new approach would consist of a single audit that would review regulatory QMS compliance, conducted by a third-party, who would later be called an Auditing Organization (AO).

From January 2014 to December 2016, five countries participated in a Medical Device Single Audit Program Pilot. In June 2017, a report was generated summarizing the outcomes of prospective “proof- of-concept” criteria established to confirm the success of the program. The outcomes are documented in the final MDSAP Pilot Report and recommended that the program become fully active and open to any manufacturer who requested this type of audit.

2012 Jan: Initiation of the pre-pilot project
2014 Jan: Announcement of the MDSAP Pilot project
Aug: Mid-Pilot Report
2015 Nov: 1st GMP Certificate delivered by ANVISA, using MDSAP audit report
Dec: Health Canada publish transition plan to replace CMDCAS by MDSAP
2016 Jan: 1st Canadian device license supported by an MDSAP certificate
Dec: Review of MDSAP Pilot project
2017 Jan: Auditing Organizations other than CMDCAS registrars can apply
July: Final Pilot Report concludes that the plan objectives met performance targets
2019 Jan: MDSAP replaces CMDCAS
2020 Implementation

Who is responsible for the MDSAP?

The governing body of the MDSAP is the Regulatory Authority Council (RAC), which is composed of two senior managers (and a few other staff members) from each participating RA. They are responsible for executive planning, strategic priorities, setting policy, and making decisions on behalf of the MDSAP International Consortium. The RAC also reviews and approves documents, procedures, work instructions, and more. The mission of the MDSAP International Consortium is to jointly leverage regulatory resources to manage an efficient, effective, and sustainable single audit program focused on the oversight of medical device manufacturers on a global scale.

Other international partners that are involved in the MDSAP include:

MDSAP Observers:

  • European Union (EU)
  • United Kingdom’s Medicines and Healthcare products Regulatory Agency (MHRA)
  • The World Health Organization (WHO) Prequalification of In Vitro Diagnostics (IVDs) Program

MDSAP Affiliate Members:

  • Argentina’s National Administration of Drugs, Foods and Medical Devices (ANMAT)
  • Republic of Korea’s Ministry of Food and Drug Safety
  • Singapore’s Health Sciences Authority (HSA)

The observers and affiliate members are not the same as the participating member RA’s. The observers simply observe and/or contribute to RAC activities. Affiliate members, on the other hand, are interested in engaging in the MDSAP program and are subject to certain rules. They are only given access to a certain level of information about the manufacturers, audit dates, and information in audit reports.

They are also invited to attend sessions that are open to members, observers, and affiliates only.

Audits can also be conducted by MDSAP participating RAs at any time and for various reasons including:

  • "For Cause" due to information obtained by the regulatory authority
  • as a follow up to findings from a previous audit
  • to confirm the effective implementation of the MDSAP requirements

The purpose of audits conducted by the RAs is to ensure appropriate oversight of the AOs MDSAP auditing activities. The AOs are appointed by the RAs and a list of the currently approved AO’s is published on the FDA website. Most AOs offer a broad range of management system certification services, beyond just medical devices. Manufacturers should verify that prospective AOs are clearly trained and perform MDSAP audits of medical devices.

AOs have the final word as to whether a manufacturer has met the requirements for the MDSAP during the execution of the audit and generation of the associated reports summarizing the results. MSDAP RAC participating RAs have the final decision regarding all development, implementation, maintenance, and expansion activities associated with the program.

Although an unannounced visit by an AO is rare, it can happen in circumstances where high-grade nonconformities have been detected.

How does an MDSAP audit work?

To continue reading this eBook including a detailed look at the MDSAP audit process and grading, pros and cons of the approach, and how to get started please register to download the full version.

Blogs

Is a medical device accessory a medical device?

By

James Gianoutsos

September 9, 2020

4 min read

Rimsys’ own James Gianoutsos recently contributed an article on www.meddeviceonline.com discussing FDA’s guidance document describing accessories and classification pathways.

On Dec. 20, 2017, the FDA issued Medical Device Accessories – Describing Accessories and Classification Pathways: Guidance for Industry and Food and Drug Administration Staff, which applies to the Center for Devices and Radiological Health (CDRH) and Center for Biologics Evaluation and Research (CBER) for combination products.

The guidance document offers welcomed clarity on the role of an “accessory” and its regulatory relationship to its parent device. As always, guidance documents are not legally enforceable; rather, they describe the Agency’s current thinking on a topic and should be viewed only as recommendations, unless specific regulatory or statutory requirements are cited.

The guidance explains which devices FDA generally considers “accessories” and describes the processes under Section 513(f)(6) of the Federal Food, Drug, and Cosmetic Act (FD&C Act) to allow requests for risk- and regulatory control-based classification of accessories. In other words, it specifically details what is and is not an accessory, as well as the regulatory routes to classification.

The updated guidance was derived from an August 2017 amendment to section 513(f) of the FD&C Act (FDA Reauthorization Act of 2017 (Pub. L. 115-52)) to state that “the Secretary shall … classify an accessory under [section 513] based on the risks of the accessory when used as intended and the level of regulatory controls necessary to provide a reasonable assurance of safety and effectiveness of the accessory, notwithstanding the classification of any other device with which such accessory is intended to be used.”

The amendment allows for some accessories to have a lower risk profile than that of their parent device and, therefore, may warrant being regulated in a lower class. As classifications for accessories are now risk-based, it provides manufacturers with regulatory flexibility to loosen some of the regulatory burdens on accessories that may not have the same risk profile as their parent devices.

For example, an accessory to a class III parent device may pose lower risk that could be mitigated through general controls, or a combination of general and special controls, and thus could be regulated as class I or class II. A common example of this would be a ventilation system (parent device) with a face mask (accessory).

Additionally, the guidance details the applicable definitions within Section IV: Definitions:

  • Accessory — “A finished device that is intended to support, supplement, and/or augment the performance of one or more parent devices.”
  • Component (21 CFR 820.3(c)) — “[A]ny raw material, substance, piece, part, software, firmware, labeling, or assembly which is intended to be included as part of the finished, packaged, and labeled device.”
  • Finished Device (21 CFR 820.3(l)) — “[A]ny device or accessory to any device that is suitable for use or capable of functioning, whether or not it is packaged, labeled, or sterilized.”
  • Parent Device — “A finished device whose performance is supported, supplemented, and/or augmented by one or more accessories.”

Accessory classification policy

The risks of an accessory are the risks it presents when used with the corresponding parent device as intended. To classify an accessory, FDA addresses the following two questions:

  1. Is the article an accessory? This can be answered by determining the intended use of the accessory. Is it intended for use with one or more parent devices, and does it support, supplement, and/or augment the performance of one or more parent devices?
  2. What is the risk of the accessory when used as intended with the parent device(s), and what regulatory controls are necessary to provide a reasonable assurance of its safety and effectiveness? This can be answered by providing a detailed risk assessment, outlining the potential hazards and reasonable regulatory and quality controls necessary to assure the accessory’s safety and effectiveness.

Individual accessories may be classified pursuant to the same regulation as a corresponding parent device, when appropriate, or be regulated independently.

Once an accessory has been classified, there is another consideration manufacturers need to decide: the Unique Device Identifier (UDI) rule. Not only does your parent device need to have a UDI, but any and all accessories each need to be assigned a UDI.

As 21 CFR 801 Labeling, Subpart B, Section 801.20(a) states: “(1) The label of every medical device shall bear a unique device identifier (UDI) that meets the requirements of this subpart and part 830 of this chapter,” and “(2) Every device package shall bear a UDI that meets the requirements of this subpart and part 830 of this chapter.”

Further, 21 CFR 830 UDI, Subpart A, Section 830.3 defines “finished device” and “device package” as follows:

  • Finished device* means any device or accessory to any device that is suitable for use or capable of functioning.
  • Device package means a package that contains a fixed quantity of a particular version or model of a device.

*Note that, although “medical device” and “finished device” are not consistent terminology used within the chapters, the terms are one and the same.

In short, any sellable finished device must bear a UDI, either on the device itself, on the device package, or both. Components to the finished device (i.e., service components and spare parts kits) are not considered accessories, and therefore are not required to bear a UDI.

What does this ultimately mean for manufacturers?

If there was any confusion as to whether a specific accessory is classified as a medical device, it has now been clarified, or at least partially clarified, depending on your specific situation. If there is still confusion among your engineering and regulatory teams, FDA recommends contacting them, via the accessory classification process outlined in the guidance, to classify the accessory appropriately. FDA will treat each accessory classification request as a Q-Submission. Requests may be for a new accessory type (new classification), an existing accessory type (reclassification), or classification of a new accessory type through the de novo process.

A gap analysis should be performed to identify a thorough and complete list of your current and future accessories to determine applicability to the guidance document. Justification also should be documented, should an accessory not apply to the guidance document. Additionally, internal procedures and the process associated with assigning UDIs may need to be updated to ensure there are no compliance gaps.

MedTech
Blogs

Podcast – Streamlining the MDSAP device marketing authorization and facility registration process

By

James Gianoutsos

August 23, 2020

4 min read

I had the opportunity to sit down with Jon Speer, Founder & VP of QA/RA at Greenlight Guru to record a podcast to discuss streamlining the MDSAP Marketing Authorization & Facility Registration Process.

If you are not familiar with this topic, you need to hear this.

We discuss:

  • Why your regulatory team may be perceived as a bottleneck and why it is important everyone needs to be on the same page about when the product can be released.
  • The connection between marketing authorization and facility registration required for various countries – United States, European Union, or elsewhere.
  • The need to get organized, get better systems in place, and stay compliant when an auditor comes through your door or when you plan to sell into markets.
  • Why small and large companies need to get organized now (i.e. small companies have too much information to maintain, organize, and track while large companies may have resources but suffer from miscommunication and disjointed processes.)
  • The need to not be complacent and not be afraid to change systems. Rimsys was created to help regulatory professionals successfully and efficiently handle documentation.

You can hear the podcast below or at the Greenlight Guru blog.

MedTech
I agree to the privacy policy including to Rimsys using my contact details to contact me for marketing purposes.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Hand holding smartphone showing email app with 12 unread messages notification.