Developing a medical product requires more than an innovative idea. Companies must consider product design, safety, performance, testing, and regulatory requirements before bringing a medical device to the U.S. market. Understanding the U.S. Food and Drug Administration (FDA) regulatory process early can help medical product developers reduce delays, manage development costs, and build products that meet regulatory expectations.
For startups and established companies alike, the FDA process can seem complicated. However, with proper planning, a clear development strategy, and the right engineering expertise, companies can navigate the process more effectively.
At SunMan Engineering, medical product development involves turning concepts into practical, functional products through engineering design, prototyping, testing, and technical problem-solving. Under the leadership of Allen Nejah, SunMan Engineering supports product development efforts by helping companies address engineering challenges throughout the development process.
This guide explains the key steps involved in preparing a medical device for the U.S. market and highlights how engineering decisions can influence regulatory readiness.
The first step in medical product development is clearly defining what the product will do, who will use it, and what medical need it is intended to address.
Developers should establish:
These details help guide product design and determine which regulatory requirements may apply.
For example, an electronic monitoring device, a diagnostic instrument, and an implantable medical device may have very different safety requirements and regulatory pathways.
Defining the intended use early helps engineers establish appropriate design requirements and reduces the risk of expensive changes later in development.
Before investing heavily in product development, companies should determine how the FDA classifies their medical device and which regulatory pathway applies.
The FDA generally classifies medical devices into three categories based on their risk and the level of regulatory control needed to provide reasonable assurance of safety and effectiveness.
Class I: Low-Risk Devices
Class I devices are generally subject to general controls, which may include requirements related to labeling, registration, and manufacturing quality. Some Class I devices are exempt from certain premarket requirements, subject to applicable limitations.
Class II: Moderate-Risk Devices
Class II devices are subject to general controls and, where applicable, special controls. Many require a premarket notification submission, commonly called a 510(k), although some are exempt.
Class III: High-Risk Devices
Class III devices generally require Premarket Approval (PMA). These devices often support or sustain life, are implanted in the body, or present a greater potential risk. A PMA requires scientific evidence supporting the device’s safety and effectiveness for its intended use.
For certain novel, low-to-moderate-risk devices without an appropriate legally marketed predicate, the FDA’s De Novo pathway may be an option.
The main pathways differ:
Not every medical device requires the same type of FDA submission, and some devices are exempt from premarket review. The appropriate pathway should be confirmed based on the product’s characteristics and applicable FDA requirements.
Identifying the correct pathway early helps companies estimate testing needs, development timelines, and regulatory costs.
Once the product concept and regulatory strategy are established, the engineering team can begin developing a design that meets the product’s functional, safety, and performance requirements.
Medical product development may involve several engineering disciplines, including:
For electronic medical devices, these activities must be coordinated carefully. A change to a circuit, component, enclosure, or software function can affect performance, reliability, usability, or safety.
Engineers should also consider relevant standards and regulatory requirements during the design process rather than waiting until the product is nearly complete.
At SunMan Engineering, multidisciplinary product development expertise can help companies evaluate technical requirements, identify design challenges, and develop functional prototypes that support the next stages of medical product development.
Design controls help ensure that a medical device is developed according to defined requirements and that its design is evaluated and documented throughout development.
The FDA’s Quality Management System Regulation (QMSR), which became effective on February 2, 2026, incorporates ISO 13485:2016 by reference into the applicable medical device quality management framework.
Manufacturers should determine which quality system requirements apply to their device and activities. Regulatory responsibilities depend on factors such as the company’s role in development and manufacturing.
Important design and quality activities may include:
Design Inputs: Documenting what the product must do, including its intended use, performance, safety, and applicable regulatory requirements.
Design Outputs: Creating specifications, drawings, schematics, software documentation, and other information needed to build the product.
Design Reviews: Evaluating the design at planned stages to identify problems and confirm that development is progressing appropriately.
Design Verification: Confirming that design outputs meet the specified design inputs.
Design Validation: Confirming that the finished design meets user needs and intended uses under defined conditions.
Risk Management: Identifying potential hazards, evaluating risks, and implementing appropriate controls.
Design Change Management: Reviewing and documenting changes to ensure they do not introduce unacceptable risks or compromise product performance.
These activities help create a documented development process and provide evidence that the product has been designed and evaluated systematically.
For engineering teams, effective documentation is just as important as building a working prototype. A product may perform well during a demonstration but still require additional testing, documentation, or design improvements before it is ready for regulatory review.
Before a medical device is ready for clinical investigation or a marketing submission, developers generally need to evaluate its design and performance through appropriate testing.
Depending on the device, testing may include:
Not every test applies to every medical device. The testing strategy should be based on the product’s intended use, design, materials, risks, and applicable regulatory requirements.
Prototype testing is particularly valuable because it helps identify problems before the design is finalized.
For example, an electronic medical device may experience overheating, electrical interference, unreliable sensor readings, or inconsistent performance under certain operating conditions. Identifying these issues early allows engineers to investigate the root cause and improve the design before moving forward.
SunMan Engineering’s product development capabilities can support the engineering activities involved in prototype development, testing, and technical refinement. The specific testing and documentation needed for FDA submission should be established with the appropriate regulatory and testing specialists.
Some medical devices require clinical data to support their safety and effectiveness or to address specific questions that cannot be answered adequately through nonclinical testing.
Clinical requirements depend on the device, its intended use, its risk profile, the available scientific evidence, and the applicable regulatory pathway.
If a clinical investigation is needed, developers must establish an appropriate study plan and determine which regulatory requirements apply.
For certain significant-risk device investigations, an Investigational Device Exemption (IDE) and Institutional Review Board (IRB) approval are required before the study begins. Other investigations may follow different requirements, depending on their risk and circumstances.
Clinical investigations may evaluate:
Clinical studies can require substantial time, funding, and coordination. Therefore, companies should consider potential clinical evidence requirements early in the development process.
Engineering teams may also need to refine prototypes based on findings from preliminary testing or permitted clinical investigations. Any design changes should be evaluated and documented appropriately.
After completing the required development activities and gathering sufficient supporting evidence, the company can prepare the appropriate FDA marketing submission.
The content depends on the regulatory pathway.
A 510(k) submission typically includes information supporting substantial equivalence to a legally marketed predicate device, along with applicable performance testing, device descriptions, and labeling.
A De Novo request includes information supporting the classification and regulatory controls appropriate for a novel, low-to-moderate-risk device.
A PMA generally requires more extensive scientific evidence supporting safety and effectiveness, which may include nonclinical and clinical data, manufacturing information, and other required documentation.
A submission may include:
The FDA reviews submissions according to the requirements of the relevant pathway. Reviewers may request additional information or clarification before reaching a decision.
A well-organized submission supported by complete, consistent documentation can help the review process proceed more efficiently. However, submission preparation does not guarantee clearance or approval.
Submitting an application does not always mean the product is immediately ready for the market.
During the review process, the FDA may identify missing information, ask technical questions, or request additional evidence.
Companies should be prepared to respond with clear explanations and appropriate supporting documentation.
For example, reviewers may need clarification about:
In some cases, additional testing or design changes may be necessary.
Maintaining organized engineering records throughout development makes it easier to locate test results, explain design decisions, and respond to questions. It can also reduce the difficulty of reconstructing technical information late in the process.
Depending on the pathway, the FDA may issue a clearance, approval, or another regulatory decision. These terms are not interchangeable: 510(k) devices are generally cleared, De Novo requests are granted, and PMA applications are approved.
Companies should not market a device until the applicable regulatory requirements have been satisfied.
FDA clearance or approval is an important milestone, but it is not the end of medical product development.
Companies must also ensure that their manufacturing processes, documentation, labeling, and quality systems meet applicable requirements.
Before launch, developers should consider:
For companies transitioning from prototype development to manufacturing, design transfer is particularly important. The design must be documented clearly enough for the manufacturing team to produce the device consistently.
Supply chain planning also matters. Component substitutions, manufacturing changes, and production delays can affect product quality and launch schedules. Changes should be assessed for their technical and regulatory implications before implementation.
A coordinated approach between engineering, regulatory, quality, and manufacturing teams helps companies move from a successful prototype to a reliable commercial product.
Medical device responsibilities continue after a product reaches the market.
Manufacturers may have ongoing obligations involving quality management, complaint handling, medical device reporting, corrections and removals, and other postmarket requirements.
Postmarket monitoring helps companies identify problems that may not have been apparent during initial testing.
Information from customers, healthcare professionals, service teams, and product performance data can help identify opportunities for corrective action or product improvement.
When changes are needed, companies should evaluate their impact on safety, performance, documentation, and regulatory status before implementation.
A strong postmarket process supports long-term product reliability and helps companies maintain compliance as products evolve.
The FDA regulatory process and the engineering development process are closely connected. Design decisions made during the early stages can influence testing requirements, documentation needs, manufacturing readiness, and the overall development schedule.
Engineering support can help medical product companies:
Allen Nejah and the team at SunMan Engineering understand the importance of combining technical problem-solving with a structured product development approach. By addressing engineering challenges early, companies can establish a stronger technical foundation for testing, regulatory preparation, and eventual manufacturing.
It is important to recognize that engineering development services do not replace specialized regulatory advice, independent laboratory testing, or FDA review. Medical product developers should work with qualified regulatory professionals to confirm the specific requirements applicable to their products.
Several challenges can create unnecessary delays and additional costs.
Designing a product without first understanding its intended use and likely regulatory pathway can lead to expensive redesigns.
Missing design specifications, test reports, or records of design changes can make it harder to demonstrate that a product meets its requirements.
A prototype that works in a limited demonstration may not perform reliably under all expected operating conditions.
When engineering, quality, regulatory, and manufacturing teams work independently, important requirements can be overlooked.
Testing, regulatory submissions, clinical investigations, and manufacturing preparation can require significant resources. Planning for these activities early helps companies make better development decisions.
Postmarket responsibilities and ongoing quality requirements must also be considered as part of the product lifecycle.
Addressing these challenges early can help companies build a more predictable and effective medical product development process.
Understanding the FDA approval process is essential for companies developing medical devices for the U.S. market. From defining the intended use and determining the regulatory pathway to testing prototypes, preparing submissions, and establishing manufacturing processes, every stage contributes to a product’s readiness.
Successful medical product development requires close coordination between engineering, regulatory, quality, and manufacturing teams. Planning for these requirements early can help companies reduce avoidable delays, manage development costs, and address technical challenges before they become more difficult to resolve.
At SunMan Engineering, Allen Nejah and the engineering team support product development through multidisciplinary engineering expertise, prototyping, and technical problem-solving. For companies developing medical technologies, a well-planned engineering process can provide a stronger foundation for regulatory preparation and long-term product success.
Developing a medical device? Contact SunMan Engineering to discuss your product development needs and explore how engineering support can help move your concept toward a functional, production-ready design.
What our clients say
Established in 1990, SunMan Engineering has engaged and assisted over 1550 leading technology companies in successfully completing over 1664 product development projects to date.