An fda deficiency letter can slow a submission just when your team expects movement. It can affect launch planning, testing budgets, clinical work, software evidence, cybersecurity documentation, labeling updates, and quality records in one review cycle.
The term can also be confusing. The FDA does not use a single deficiency letter across every product pathway. In medical device reviews, deficiency language usually points to additional information the FDA needs before it can decide on a marketing application. In 510(k) and De Novo submissions, teams may hear it called an Additional Information request, AI request, AI letter, or deficiency letter. Drug applications use a different process, where a Complete Response Letter identifies deficiencies after the FDA reviews an NDA or ANDA.
This guide breaks down what the letter means, how it differs from other FDA actions, why it happens, and how your team can respond without creating another review delay.
What Is an FDA Deficiency Letter?
An FDA deficiency letter means the FDA needs more information before it can finish the review. The letter may point to missing data, unclear test results, weak explanations, incomplete documents, or claims that are not fully supported. The FDA is asking the applicant to fix those gaps and send a proper response.
The name of the letter can change based on the product and the review type. In medical device submissions, the FDA uses deficiency language when it needs more information to decide on a marketing application.
For a 510(k), this usually comes as an Additional Information request. The FDA may send it when the submission does not give enough evidence to show substantial equivalence. For a De Novo request, the FDA can place the review on hold if the questions cannot be solved through interactive review. The requester has 180 calendar days from the date of the Additional Information letter to send a complete response.
Drug applications use different wording. For an NDA or ANDA, the FDA sends a Complete Response Letter when it has finished the review but cannot approve the application as submitted. Under 21 CFR 314.110, the letter explains the specific deficiencies FDA found.
FDA Deficiency Letter vs RTA Hold vs CRL vs Form 483 vs Warning Letter
FDA sends different types of letters for different problems. The name of the letter tells you where the issue came from and how serious the response needs to be. An FDA510(k) Additional Information request is part of the review. A Form 483 comes from an inspection. A Warning Letter is an enforcement. Treating them the same can lead to the wrong response.
| FDA communication | Where you see it | Plain meaning | What happens next | What to send back |
| FDA deficiency letter | Often used in device reviews, the | FDA needs more information before it can finish the review | The review can slow down | Clear answers, updated files, proof for each point |
| 510(k) Additional Information request | During 510(k) reviewThe | FDA cannot decide on substantial equivalence yet | The review clock stops | Answers in the same order as the FDA’s questions. Test reports. Revised sections. Clear references |
| RTA hold | Before full 510(k) review startsThe | FDA found basic missing items | The file may not move into full review | Missing forms, Required sections, Checklist items, Basic file corrections |
| PMA major deficiency letter | During PMA review | FDA found major issues that block approval | The review can take much longer | Clinical data, Safety details, Manufacturing information, Design records |
| Complete Response Letter | NDA or ANDA review | FDA reviewed the application, but cannot approve it yet | Approval stops until the problems are fixed | Safety fixes, Efficacy support, CMC updates, Labeling or manufacturing changes |
| Form 483 | FDA inspection | An inspector saw possible problems | FDA may follow up if the reply is weak | Corrections made, Dates, Responsible owners, Proof of fixes |
| Warning Letter | FDA enforcement | FDA found serious rule violations | The issue becomes public | Correction plan, Compliance fixes, Written commitments, Proof that the problem is being handled |
In a 510(k), timing makes the difference clear. An RTA hold comes early, when the FDA checks whether the submission is complete enough to review. An Additional Information request comes later, after the FDA has started reviewing the details and needs more evidence to answer its own review questions.
Form 483s and Warning Letters are separate from normal premarket review. They usually come from inspection findings or compliance problems, not from a reviewer asking for more information about a submission.
Facing an FDA deficiency letter? Contact Qualysec for expert support with regulatory documentation, cybersecurity evidence, and response preparation to help move your submission forward with confidence.
What Happens After You Receive an FDA Deficiency Letter?
1. The review timeline may pause
For a 510(k), an Additional Information request usually stops the review clock. It starts again once a complete response is received.
The submitter generally has 180 calendar days from the AI request date to reply. That time can go fast if the response is needed:
- New or repeated testing
- Updated reports
- Software input
- Cybersecurity evidence
- Quality records
- Clinical review
- Leadership approval
Calendar days keep moving even when the review clock is paused. Treat the letter as a response project from day one. Assign owners, collect evidence early, check every answer against the original question, and send one complete response.
2. The response deadline can shape the full project plan
The 180-day window can look generous at first. It is not always enough once the work begins.
A simple document gap can move fast if the records already exist. For example, a missing SBOM can be added quickly when the software inventory is clean, current, and tied to the right product version.
Other issues take longer. A missing usability validation study can require:
- A protocol
- Participant recruitment
- Test sessions
- Data review
- Report writing
- Internal approval
The same problem can happen with updated labeling, cybersecurity fixes, validation work, clinical analysis, or CMC updates.
3. FDA may request clarification or supporting evidence, not just new documents
A deficiency does not always mean the product needs redesign. Sometimes the reviewer can see the information, but the link between the claim, test, standard, and conclusion is not clear enough.
The response may need:
- Clearer rationale
- Stronger mapping between sections
- Complete test reports
- Documented acceptance criteria
- Version-controlled attachments
- An explanation of why a chosen standard fits the product
This is common in technical FDA submissions. A team may have the right evidence but still receive questions if the file does not show how that evidence supports the decision. The response needs to make that connection easy to follow.
4. The company needs a single response owner
Assign one regulatory owner for the full response. This person manages the response matrix, deadlines, evidence, references, and file versions.
Other teams can add input, but the final reply needs one review before submission. Scattered answers can create conflicts. One section names one software version. Another file names a different one. The reviewer needs one clean response with matching evidence.
Common Reasons FDA Sends Deficiency Letters
1. Predicate device comparison is weak
A weak predicate comparison is a common reason for a 510(k) deficiency. The reviewer needs to see why the new device is substantially equivalent to a legally marketed device. If that link is unclear, the review slows down.
Common problems include:
- Vague predicate selection
- Unclear intended use comparison
- Missing technology comparison
- Material differences with no explanation
- Incomplete energy source details
- Software functions that do not match
- Different patient population
- New risks with no support
- “Same function” claims without evidence
A strong response needs a clear comparison table. It should cover intended use, indications, design, materials, software, operating conditions, patient contact, risk controls, performance testing, and labeling. Every difference needs an explanation. The response has to show why the difference does not change safety or effectiveness.
2. Performance testing does not support the claim
Test data can trigger a deficiency when it does not answer the reviewer’s question. A report that says “passed” is not enough if the submission does not show what was tested, why it was tested, and how the result supports the device claim.
The request can involve different types of evidence, such as:
- Bench testing
- Electrical safety
- EMC results
- Software validation
- Sterilization data
- Shelf life studies
- Packaging validation
- Biocompatibility results
- Cybersecurity testing
- Usability studies
- Animal data
- Clinical evidence
- Analytical performance data
A strong response gives the reviewer the full trail. It includes the protocol, sample size, acceptance criteria, test conditions, deviations, results, conclusion, and the standard used. The goal is simple. Do not only state that the test passed. Show that the test was suitable for the claim and that the result supports the question raised in the letter.
3. Labeling goes further than the evidence
Labeling can lead to a deficiency when it promises more than the data supports. The device can perform well, but the label still creates a review issue if it overstates use, benefit, accuracy, safety, or performance.
Common problem areas include:
- Indications
- Warnings
- Contraindications
- User instructions
- Patient claims
- Marketing language
- training requirements
- Operating limits
- Performance statements
The response needs to show what changed and what remains supported. Include redlined labeling, clean labeling, a claim support table, and exact references to the data behind each retained claim.
4. Software documentation lacks traceability
Software review problems usually start when the documents do not speak to each other. A submission can include requirements, architecture, hazard analysis, verification, validation, SOUP details, anomaly records, update controls, cybersecurity notes, and labeling, but still leave the reviewer guessing.
The reviewer needs to follow the path from a software requirement to the related hazard, risk control, test result, validation evidence, unresolved anomaly review, and user instruction. If one part of that chain is missing, the response becomes harder to trust.
Version control also matters. The software version in the test report needs to match the version used in the risk file, architecture document, cybersecurity section, and labeling. Even a small mismatch can raise questions.
5. Cybersecurity documentation is missing or too shallow
Cybersecurity can no longer be treated as a small technical appendix for connected medical devices. If the device uses software, network access, cloud services, APIs, wireless communication, or remote updates, the review will look for a clear security story.
Section 524B applies to cyber device premarket submissions. Sponsors need to include information that shows how the device meets cybersecurity requirements. Current guidance also explains what kind of cybersecurity content belongs in a premarket file.
Deficiencies can come from a missing risk management file, a weak threat model, an incomplete SBOM, a loose update plan, poor vulnerability handling, weak authentication, encryption claims without proof, missing secure setup instructions, no end-of-support policy, or cyber risks that are not tied back to patient safety.
The response has to close the exact gap. If the SBOM is incomplete, fix the inventory. If the threat model is thin, rebuild the attack paths and controls. If the update plan is unclear, show how patches will be tested, approved, and delivered.
6. Biocompatibility or material justification is incomplete
Biocompatibility questions usually come up when the submission does not clearly show what touches the patient and for how long. Reviewers can ask about contact type, contact duration, body contact category, final finished device testing, coatings, adhesives, colorants, cleaning agents, manufacturing residues, supplier changes, or the reason for relying on older data.
The response needs to remove any doubt around the material story. State the patient contact category, explain the test endpoints, name the standard used, describe the material formulation, and connect the testing to the final finished device. If prior data is used, the bridging rationale needs to explain why that data still applies after any material, supplier, process, or design change.
7. Human factors validation does not cover real use risk
A study can miss the point if it tests the wrong users, tasks, settings, or training level. The response needs to match the intended use, not just show that a study was completed.
Cover the use-related risk analysis, critical tasks, representative users, simulated use conditions, training assumptions, observed use errors, close calls, root cause analysis, and residual risk. If users made mistakes during testing, explain what happened and what changed after review. The answer needs to show that the remaining risks are understood and controlled.
8. Sterilization, reprocessing, packaging or shelf life evidence is insufficient
A device does not only need to pass testing in a fresh state. It has to hold up through storage, shipping, handling, use, and reuse, where applicable.
For sterile devices, the file needs proof that the sterile barrier stays intact until the labeled expiry date. That proof usually comes from aging data, packaging integrity checks, microbial barrier evidence, and transport simulation.
Reusable devices need a different set of records. Cleaning validation, residue limits, reprocessing instructions, and reuse cycle data have to show that the device can be safely prepared for the next user. If the letter questions this area, the response needs to point directly to the missing proof and close that exact gap.
9. Clinical or nonclinical evidence does not answer FDA’s review question
Clinical data can still fall short if it does not match the claimed use. The issue might be the study design, endpoint choice, statistical method, patient group, follow-up period, comparator, subgroup analysis, or the link between the data and the intended use.
Nonclinical evidence has the same problem when the model does not fit the question. An animal study, bench study, or analytical test needs to show why the result matters for the device, drug, or biologic under review.
For NDA, ANDA, and biologic submissions, a Complete Response Letter can point to safety, efficacy, clinical, CMC, manufacturing, labeling, or facility issues. The response has to answer the exact review concern, not just restate that the study was completed.
10. CMC or manufacturing gaps block approval
Good clinical results do not fix a weak production file. FDA still has to see that the product can be made the same way each time, tested properly, stored safely, and released with the right controls.
CMC questions can involve analytical methods, process validation, stability data, batch records, facility readiness, manufacturing controls, specifications, contamination controls, or inspection issues that remain open. This does not always point to a clinical failure. It means the approval cannot move ahead until the manufacturing record is complete and clear.
11. Submission formatting or administrative issues create avoidable friction
Small file errors can delay a review before the technical questions even begin. Common issues include:
- Missing forms
- Inconsistent device names
- Outdated standards
- Mismatched version numbers
- Missing signatures
- Unclear attachment names
- Poor cross-references
- Wrong submission type
- Incomplete eSTAR fields
For medical device submissions, eSTAR uses structured templates. If an eSTAR file does not pass technical screening, the submission can go on hold. A replacement eSTAR must be sent within 180 days, or the file can be treated as withdrawn.
Contact Qualysec today to strengthen your FDA submission readiness.
Contact Qualysec today to strengthen your FDA submission
Real FDA Deficiency Letter Examples and What They Teach Submission Teams
Example 1: Corcept Therapeutics relacorilant CRL, efficacy, and liver safety concerns
Corcept Therapeutics received a corrected Complete Response Letter for relacorilant, its proposed treatment for patients with Cushing’s syndrome-related hypertension. The corrected letter said the main clinical trial did not show a meaningful difference from placebo. It also raised liver safety concerns, including probable drug-induced liver injury in four patients.
The lesson is clear. A response cannot depend on broad claims about clinical promise when the agency questions both efficacy and safety. The company would need a deeper clinical analysis, a stronger safety review, possible labeling changes, and a clearer benefit-risk case. This type of CRL is not a simple document gap. It questions whether the submitted evidence supports approval.
Example 2: Capricor Therapeutics deramiocel CRL, effectiveness, and CMC review issues
Capricor Therapeutics received a Complete Response Letter for deramiocel, its cell therapy candidate for cardiomyopathy linked to Duchenne muscular dystrophy. The letter said the BLA did not meet the legal requirement for substantial evidence of effectiveness and that more clinical data were needed.
The letter also referenced open CMC items. Capricor said it had already sent materials for many of those points, but they were not reviewed before the CRL was issued because of timing. The company also said the review clock would restart after resubmission and that it could request a Type A meeting.
This example shows how one CRL can involve two separate tracks. The clinical team has to answer the effectiveness concern. The CMC team has to make the manufacturing record complete and review-ready. Treating both as one general response can leave gaps.
Example 3: Grace Therapeutics GTx 104 CRL, packaging, toxicology, and manufacturing concerns
Grace Therapeutics received a Complete Response Letter for GTx 104, an intravenous nimodipine formulation for aneurysmal subarachnoid hemorrhage. The company said the letter cited open CMC and nonclinical items, with no request for added clinical data.
The cited issues involved leachables data for product packaging, toxicology risk assessments, and manufacturing deficiencies at the contract manufacturing organization. That makes this a useful example for teams working with drug containers, packaging systems, suppliers, and outsourced manufacturing.
The main lesson is practical. Approval can stall because of the container, the manufacturing site, or the safety support behind materials in contact with the product. A response has to close those production and toxicology gaps, not only defend the treatment concept.
How to Respond to an FDA Deficiency Letter Effectively
Step 1: Read the letter by discipline before drafting the response
Start by sorting each deficiency into the right workstream. Use categories such as regulatory, clinical, nonclinical, bench testing, software, cybersecurity, labeling, usability, quality, manufacturing, statistics, or CMC.
Then mark what each item needs:
- Clarification only
- Document revision
- New analysis
- New testing
- Design change
- labeling change
- cybersecurity fix
- Agency clarification before response
Each item needs one owner and one reviewer. One regulatory lead still controls the full package, so the final response reads as one submission, not separate team notes joined together.
Step 2: Identify the real question behind each deficiency
Do not answer only the words on the page. Find the review question behind them. Each deficiency usually tells you four things:
- What was reviewed
- Why was it not enough
- What is being requested
- How the answer affects the decision
For example, a cybersecurity comment about update integrity is not just asking for an update procedure. The real question is whether a failed or malicious update could affect device safety, performance, or patient use.
Once the real question is clear, the response becomes easier to write. The answer can focus on the risk, the control, the evidence, and the exact document that supports it.
Step 3: Decide whether FDA clarification is needed
Do not rush into a costly response when the request itself is unclear. First, check whether the question fits the product, the submission type, and the evidence already provided.
A SaMD team could receive wireless testing questions because the wrong eSTAR field was selected. Another team could receive a clinical data request when targeted nonclinical testing can address the same concern.
In cases like these, clarification can save weeks of work. Ask what evidence the reviewer expects, confirm the scope, and document the discussion before building the response package.
Step 4: Build a response matrix
Put every deficiency into one working matrix. Use columns for:
- Deficiency number
- Request summary
- Owner
- Response type
- Evidence required
- Attachment name
- Source document
- Change made
- Completion status
- Due date
- Reviewer concern
This keeps the response from turning into scattered answers. It also shows leadership which items need lab work, new reports, product changes, outside cybersecurity input, or extra review before submission.
Step 5: Answer in FDA’s order
Keep the response in the same order as the letter. Start with a direct answer, then give the proof. Do not make the reviewer hunt through a large attachment for the main point.
Use a simple format for each item:
- FDA deficiency number
- FDA request summary
- Direct response
- Evidence submitted
- Documents revised
- Attachment references
- Rationale for why the response resolves the concern
The answer needs to stand on its own. Attachments support the response, but they do not replace it.
Step 6: Make every document change traceable
Show every change clearly. Include version numbers, dates, redlines where useful, clean final copies, attachment names, and a short change summary. If the risk file, labeling, SBOM, software report, test protocol, IFU, or CMC section changed, state what changed and why.
Do not hide updates inside attachments. Make the change easy to find and easy to review.
Step 7: Include complete evidence, not promises
Send finished evidence, not future plans. A partial answer can waste the response window and lead to another review cycle.
For testing items, the response needs the protocol, acceptance criteria, test conditions, deviations, final results, conclusion, and a clear note on how the test answers the request. For cybersecurity items, broad assurance statements are not enough. Include actual artifacts such as the threat model, SBOM, vulnerability assessment, patching plan, secure update process, and postmarket monitoring process where relevant.
Step 8: Use alternate approaches only with strong rationale
An applicant does not always have to provide the exact information requested if another route answers the review concern better.FDA guidance encourages a least burdensome approach allows applicants to explain why a request is not relevant or to propose another approach.
Examples include:
- Using nonclinical testing to answer a specific safety concern
- Submitting a declaration of conformity to a recognized standard
- Explaining why a test does not apply to the final finished device
The rationale still needs to show how the alternate evidence supports the review decision.
Step 9: Run an internal contradiction check
Before submission, compare the response against the original file, labeling, risk analysis, software records, cybersecurity files, test reports, IFU, clinical evidence, and CMC sections.
Look for conflicts such as:
- Device name mismatch
- Software version mismatch
- Risk control is missing from the test report
- Labeling a claim with no data behind it
- SBOM version that does not match the release version
- Cybersecurity control is missing from the architecture file
Fix these before the response goes back. A contradiction can create a new question even when the main answer is correct.
Step 10: Submit through the correct channel
Submission rules depend on the pathway, file type, and current workflow. For device submissions, eSTAR and the CDRH Portal can matter depending on the submission type.
FDA describes eSTAR as an interactive PDF template that helps applicants prepare medical device submissions. It does not replace the need to follow the exact instructions in the letter.
Avoid one-size-fits-all filing advice. Check the FDA letter, submission type, current portal requirements, and guidance from regulatory counsel or an experienced consultant before sending the response.
Not sure if your cybersecurity documentation meets FDA expectations? Schedule a meeting with Qualysec for expert guidance.
FDA Deficiency Response Matrix Template
A response matrix keeps the work organized from the first review of the letter to the final submission. It helps the team track ownership, evidence, document updates, and final review without losing the link to each FDA question.
| Matrix field | What to include | Why it matters |
| Deficiency number | FDA’s item number | Keeps the response aligned with the letter |
| FDA request summary | Short restatement of the concern | Confirms the team understands the question |
| Owner | Regulatory, software, cybersecurity, clinical, quality, CMC, or labeling lead | Prevents unclear responsibility |
| Evidence needed | Test report, protocol, SBOM, labeling, risk file, or CMC data | Shows what the team must collect or create |
| Response status | Drafting, testing, reviewing, or completing | Helps control deadlines |
| Revised document | File name, version, and date | Creates a clear change trail |
| Attachment location | Exact attachment name and section | Helps the reviewer find the proof quickly |
| Rationale | Why does the answer resolve the concern | Prevents a document dump with no clear explanation |
| Final reviewer | Regulatory lead or subject matter reviewer | Adds one last quality check before submission |
Use this matrix as the working control file. Every answer, attachment, and document change needs to match the same deficiency number, so the final response reads as one organized package.
Drug and Biologics Deficiencies: How Complete Response Letters Differ
Drug and biologic teams sometimes use “deficiency letter” when they mean a Complete Response Letter. The meaning is not the same as a 510(k) Additional Information request.
Under 21 CFR 314.110, a Complete Response Letter describes the specific deficiencies found in an application or abbreviated application, except for certain cases noted in the regulation. In simple terms, the review is complete, but the application cannot be approved in its current form.
1. Safety or efficacy concerns
A CRL can question whether the clinical evidence supports approval. Issues can include weak efficacy results, safety signals, trial design problems, endpoint concerns, incomplete analysis, short follow-up, subgroup uncertainty, or benefit-risk questions.
2. CMC and manufacturing deficiencies
CMC issues can block approval even when the clinical story is not the main problem. Common concerns include process validation, facility readiness, analytical methods, stability, specifications, batch data, contamination controls, comparability, and manufacturing records.
3. Labeling and risk management issues
The proposed label also matters. A CRL can question the indication, dosage, warnings, contraindications, instructions, patient group, REMS considerations, or how risks are explained to prescribers and patients for effective risk management.
4. Resubmission planning
After a CRL, the team needs a clear resubmission plan. That can involve a Type A meeting, new studies, CMC remediation, labeling edits, facility work, or a formal resubmission strategy. The exact path depends on the letter, the product, and the review division.
Response Errors That Can Trigger Another FDA Review Cycle
1. Sending broad claims without evidence
A response loses strength when it says “testing passed,” “risk is acceptable,” or “the device is secure” without showing the data behind it. Each claim needs proof, such as test results, risk analysis, validation records, cybersecurity artifacts, or a clear reference to the exact document section.
2. Revised files with no change explanation
Updated documents help only when the reviewer can see what changed. Redlines, version numbers, dates, file names, and a short change summary make the review easier. Hidden edits create extra work and can lead to more questions.
3. Missing one part of a detailed request
Some deficiencies ask for several items in one question. If the request asks for protocol, acceptance criteria, deviations, results, and rationale, the response needs all five. A strong answer follows the full request, not just the easiest part.
4. Treating cybersecurity like an IT note
For cyber devices, cybersecurity evidence needs real depth. The response has to cover risk management, architecture, SBOM, vulnerability handling, update controls, labeling, and patient safety impact. A short statement about secure design will not carry the response.
5. Creating conflicts across the file
Contradictions can weaken an otherwise good answer. One software version in the SBOM and another in validation reports creates doubt. A labeling claim that is not supported by testing creates another gap. A risk control listed in the hazard file but missing from verification records can reopen the question.
6. Skipping the exact wording of the request
A team can disagree with a request or propose another route, but the answer still has to face the concern directly. If the letter asks for a specific risk, test, standard, or rationale, the response needs to speak to that point before adding extra context.
How Qualysec Helps Teams Address Cybersecurity Deficiency Risks
Cybersecurity-related deficiency letters can point to missing threat models, weak SBOM support, unclear vulnerability handling, poor update controls, or security claims that are not tied to patient safety.
For connected devices, SaMD, APIs, cloud platforms, IoT systems, and patient-facing software, policy documents alone are not enough. Teams need tested evidence that shows where risks exist, what was fixed, and how controls were verified.
Qualysec supports this work through human-led AI Penetration Testing. Its three-part testing model combines manual testing, AI agents, and automated scanners to find business logic issues, known vulnerabilities, attack paths, and system-level weaknesses.
The final report can help technical teams plan remediation with severity ratings, reproduction steps, fix guidance, executive summaries, retesting support, and consultation calls. Teams preparing cybersecurity evidence or correcting a cyber-related FDA response can speak with Qualysec to assess gaps before resubmission.
Conclusion
An FDA deficiency letter does not need a rushed reply. It needs a careful match between the question asked and the proof submitted. Strong teams slow down long enough to sort the letter by pathway, assign the right owners, check the evidence, and remove contradictions before resubmission. That discipline matters across device, drug, biologic, and cyber product reviews.
For connected devices, SaMD, APIs, cloud systems, and IoT products, FDA cybersecurity can shape the review as much as other technical evidence. Clear testing, verified controls, and well-documented remediation give reviewers a cleaner file to assess and give the company a stronger response package.
Schedule a meeting with Qualysec today to discuss your FDA cybersecurity and compliance requirements.
Consult with our cybersecurity experts
Discuss your unique security requirements and discover how we can help your business.
FAQs
Q.What is a deficiency letter from the FDA?
It is a formal notice that the application still has gaps FDA wants addressed. The concern can relate to testing, labeling, clinical data, software, cybersecurity, manufacturing, or another part of the submission.
Q.What is the purpose of a deficiency letter?
The letter gives the applicant a clear list of issues that need attention. It helps the review team ask for the missing proof, correction, explanation, or revised file needed before the application can move ahead.
Q.Is a CRL a rejection?
No. A Complete Response Letter means the application is not approvable in its current state. The sponsor can still work on the issues listed in the letter and come back with a resubmission strategy.
Q.How long does FDA approval usually take?
The timeline depends on the product type and review route. A 510(k) review does not follow the same timing as a PMA, De Novo request, NDA, ANDA, or BLA. Extra questions, clock stops, inspections, new testing, and resubmissions can extend the process.
0 Comments