Why Most Ethics Committee Applications Get Rejected First Round

Written by HATEM RABEH, MD, MSc Ing

Your Clinical Evaluation Expert And Partner

in
S

I see this pattern repeatedly. Teams spend months preparing their clinical investigation plan, finalizing their device documentation, and coordinating with investigators. Then they approach the ethics committee application as the last box to check before starting enrollment.

The result? Rejection. Requests for clarification. Delays that push back the entire investigation timeline.

The problem is not incomplete documentation. The problem is a misunderstanding of what ethics committees examine and why their evaluation differs fundamentally from Notified Body review.

What Ethics Committees Actually Evaluate

Under MDR Article 62 and the Medical Device Coordination Group guidance, ethics committees assess whether the clinical investigation protects subject rights, safety, and welfare. This sounds obvious until you see how applications actually fail.

Ethics committees do not verify regulatory compliance in the way Notified Bodies do. They evaluate whether you have thought through the human impact of your investigation at every decision point.

When I review rejected applications, the deficiency is rarely missing documents. It is the absence of reasoning that shows genuine consideration of subject protection.

This distinction matters because it changes what belongs in your application narrative.

The Common Structure That Fails

Most applications I see follow this structure: device description, intended purpose, clinical background, investigation design, risk analysis summary, informed consent form.

Everything is there. Everything is technically correct. And yet the application creates no confidence that anyone thought critically about subject vulnerability.

Here is what happens: the device description lists technical specifications but does not explain what the subject will actually experience. The investigation design presents the protocol but does not explain why this design minimizes subject burden. The risk analysis references the device risk management file but does not address risks specific to investigation participation.

The ethics committee reads this and asks: does this team understand what they are asking subjects to undergo?

This creates the first rejection cycle. The committee sends questions. The sponsor provides more technical detail. The committee asks again because their actual concern was never addressed.

Subject Experience As Organizing Principle

When I prepare ethics committee applications now, I organize every section around a simple question: what will the subject experience and why is this justified?

Device description becomes: what will happen when this device is used on the subject? How will it feel? What will they see, hear, or sense? What restrictions or requirements will this create in their daily life during the investigation?

Investigation design becomes: why is this design the minimum necessary to answer the clinical question? What alternatives were considered that might reduce subject burden? Where does the protocol require more than standard care and how is that justified by the knowledge gained?

Risk analysis becomes: what specific risks does investigation participation add beyond the risks of using the device in normal practice? How will these risks be monitored? What are the stopping rules if risks materialize?

This is not about adding sections. This is about reframing existing content so the ethics committee can evaluate what they are mandated to evaluate.

Informed Consent As Litmus Test

The informed consent form reveals whether your team genuinely understands what subjects face.

I have seen consent forms that describe device mechanisms in engineering language. Forms that list every possible adverse event from the risk management file without explaining which risks are theoretical versus likely. Forms that bury the investigation’s experimental nature in regulatory language about conformity assessment.

The ethics committee reads the consent form and immediately knows whether the application team thought from the subject perspective.

A strong consent form explains in plain language what participation means practically: how many visits, what happens at each visit, what measurements or procedures are performed, what the subject must do or avoid, how long participation lasts, what compensation or care is provided if harm occurs.

It explains the uncertainty honestly: what is already known about the device, what this investigation will determine, what alternatives exist including the choice not to participate.

It presents risks in context: what risks exist from the device itself, what additional risks come from being in an investigation, how these compare to risks the subject already faces from their condition.

This is why I draft the consent form early in application preparation, not at the end. It forces clear thinking about what we are actually asking subjects to accept.

Vulnerable Populations And Proportionality

Under MDR Article 62, specific protections apply when investigations involve incapacitated subjects, minors, pregnant or breastfeeding women, or other vulnerable groups. These requirements exist in the regulation.

What the regulation does not fully convey is the ethics committee’s assessment of proportionality.

When your investigation includes vulnerable subjects, the committee evaluates whether inclusion is scientifically necessary or merely convenient. Whether the knowledge gained is proportional to the additional protection challenges. Whether safeguards are specific to the vulnerability rather than generic.

I reviewed an application last year where the protocol included elderly subjects with mild cognitive impairment. The application stated that these subjects could be included because they could provide informed consent with assistance from family members.

Technically correct under MDR Article 64. Completely insufficient for ethics committee review.

The committee wanted to know: why is this population necessary for the investigation objectives? How will you assess whether each individual subject can genuinely understand the investigation? What happens if a subject’s cognitive function declines during the investigation? How will you monitor for coercion from family members who want to be helpful?

The application had not addressed these questions because the team viewed vulnerable populations through a compliance lens rather than an ethics lens.

This creates extended review cycles because the fundamental question of proportionality must be answered before the committee can assess adequacy of safeguards.

Risk-Benefit In Investigation Context

Every clinical investigation application includes risk-benefit assessment. Most fail to make the assessment specific to investigation participation.

The typical application presents device risks from the risk management file and device benefits from the intended purpose. Then it concludes that benefits outweigh risks.

This assessment is relevant for device use generally. It is insufficient for investigation participation specifically.

The ethics committee evaluates a different question: do the benefits of generating clinical evidence through this investigation justify the risks and burdens of investigation participation for these subjects?

This is not the same question. The subject may receive no direct benefit from participation. The investigation procedures may add burden beyond normal device use. The knowledge gained benefits future patients, not current subjects.

A rigorous risk-benefit assessment for investigation participation addresses: what direct benefits might subjects receive from participation versus standard care? What risks and burdens are added specifically by investigation procedures like additional visits, measurements, or restrictions? How does the knowledge gained justify these investigation-specific burdens?

When investigations offer no direct benefit to subjects—for example, studies in healthy volunteers or equivalence studies where the comparator is already proven—the assessment must explicitly acknowledge this and explain why subject participation is still ethical.

The justification comes from minimization of risk and burden, quality of informed consent, and importance of the knowledge gained. But these elements must be stated clearly, not implied.

Data Protection And Subject Privacy

Under GDPR and MDR requirements, clinical investigations must protect subject data. Ethics committees evaluate whether your data protection approach is adequate.

Most applications include generic statements about pseudonymization, access controls, and data security. These statements are necessary but insufficient.

What ethics committees examine is whether your data protection approach is proportional to the sensitivity of data collected and whether subjects genuinely understand what will happen to their data.

I see applications where the protocol collects genetic data, mental health information, or sensitive personal history, but the data protection section describes only technical security measures.

The ethics committee asks: who will have access to sensitive data? How long will identifiable data be retained? Will data be shared with other researchers or commercial partners? Can subjects withdraw their data after participation ends?

These questions reflect genuine subject concerns that must be addressed in the informed consent and data protection sections of your application.

Applications that treat data protection as purely technical compliance miss what ethics committees evaluate about subject autonomy and privacy protection.

Investigator Qualification And Site Capability

Ethics committees assess whether investigators and sites can actually conduct the investigation safely and effectively.

Applications typically include investigator CVs and facility descriptions. These documents prove qualifications exist. They do not demonstrate that qualifications match investigation requirements.

What the committee evaluates is whether this specific investigator at this specific site has the capability, experience, and resources to manage this specific investigation’s challenges.

For complex devices or vulnerable populations, the committee looks for evidence of relevant experience, not just general credentials. For investigations requiring specialized monitoring or intervention, they look for facility capabilities and support staff, not just investigator qualifications.

When I prepare applications now, I include a brief narrative explaining why each investigator is well-suited to this investigation specifically. What relevant experience do they have? What similar studies have they conducted? What support resources are available?

This narrative takes two paragraphs. It answers the question before the committee asks it.

Insurance And Compensation For Harm

MDR Article 69 requires insurance or financial provisions covering investigator and sponsor liability for injury or death resulting from investigation participation.

Applications must demonstrate that adequate coverage exists. Most applications attach insurance certificates and consider the requirement met.

Ethics committees evaluate whether the coverage is actually adequate for the investigation’s risk profile and whether subjects understand what compensation they can expect if harm occurs.

The informed consent must explain in clear terms: what types of harm are covered? What process do subjects follow to claim compensation? What happens if harm appears after the investigation ends?

Generic statements about insurance existence do not answer these subject-centered questions.

I have seen applications rejected because the insurance certificate indicated coverage limits that seemed inadequate for the device’s risk profile, or because the consent form stated only that “insurance exists” without explaining the compensation process.

The solution is not complex. State coverage limits. Explain what types of harm are covered. Describe the claims process. Include this information in both the application narrative and the informed consent.

What Changes After First Submission

Even well-prepared applications usually receive requests for clarification or minor modifications after first submission. This is normal.

What distinguishes productive review cycles from extended delays is how you respond to ethics committee questions.

When the committee asks for clarification, they are usually signaling that your application did not demonstrate adequate consideration of a specific aspect of subject protection.

The effective response addresses the underlying concern, not just the surface question.

If the committee asks about monitoring frequency, they may be concerned about how you will detect emerging safety issues. Respond by explaining your monitoring strategy and decision rules, not just by increasing visit frequency.

If they ask about subject selection criteria, they may be concerned about whether inclusion criteria adequately protect vulnerable subjects or whether exclusion criteria are unnecessarily restrictive. Respond by explaining the reasoning behind your criteria and how they balance subject protection with investigation objectives.

I review ethics committee responses regularly. The responses that succeed address the question and the concern behind it. The responses that prolong review cycles answer only the literal question asked.

Integration With Regulatory Submission

Ethics committee approval and Notified Body authorization are parallel requirements under MDR. They evaluate different aspects of investigation acceptability.

Some teams prepare separate documents for each submission. This creates unnecessary work and risks inconsistency.

The effective approach is to maintain single source documents for protocol, investigator’s brochure, and informed consent, then prepare submission-specific cover letters and summary documents that frame these materials for each reviewer’s focus.

For ethics committees, the cover letter emphasizes subject protection reasoning. For Notified Bodies, the cover letter emphasizes regulatory compliance demonstration.

The underlying documents remain consistent. The framing changes to match each reviewer’s mandate.

This approach reduces preparation time and eliminates the risk of submitting different protocol versions to different reviewers.

When committees and Notified Bodies identify issues, the single source approach ensures that corrections are consistent across both submissions.

The Mindset That Prevents Rejection

Applications succeed when they demonstrate that the investigation team thinks continuously about subject protection, not just about regulatory compliance.

This mindset appears in how you explain design choices, describe risks, present informed consent, and respond to committee questions.

Ethics committees can tell within the first few pages whether an application comes from a team that considered subject perspective at every decision point or from a team that treated ethics review as regulatory formality.

The difference is not about being more cautious or more detailed. The difference is about reasoning from subject experience rather than regulatory requirement.

When you describe device function, think about what the subject will experience. When you explain investigation design, think about what you are asking subjects to accept. When you assess risks, think about what subjects fear and what reassurance they need.

This subject-centered reasoning is what ethics committees look for. When they find it in your application, review proceeds smoothly. When they do not find it, you enter revision cycles.

This is why I start application preparation by writing from the subject perspective first, then adding regulatory references second. The reasoning must be genuine and visible throughout the application.

When ethics committees see this reasoning, they can evaluate what they are mandated to evaluate: whether the investigation adequately protects subject rights, safety, and welfare.

When they do not see this reasoning, they cannot make that evaluation, regardless of how complete your documentation appears.

The applications that succeed first round are the applications where subject protection reasoning is woven into every section, not added as a separate chapter.

Peace,
Hatem
Clinical Evaluation Expert for Medical Devices
Follow me for more insights and practical advice.