Clinical Research
A clinical protocol is both a scientific document and a regulatory instrument. It must satisfy the IRB, comply with 21 CFR Part 812, and produce data structured to answer the specific questions FDA will ask during the review of your submission.
Develop Your ProtocolProtocol Architecture
Medical device protocols have distinct requirements compared to pharmaceutical trials. FDA's guidance on IDE applications and clinical investigations identifies device-specific elements that a drug protocol would never contain: device description and accountability procedures, operator training requirements and experience criteria, specific device handling and implantation or application procedures, and often a learning curve rationale for when per-protocol data collection begins. These elements are not optional; missing them from a protocol submitted in an IDE application will generate FDA information requests that delay study start.
Device protocols also carry the obligation to define the investigational plan comprehensively under 21 CFR 812.25. The investigational plan section of an IDE application includes the protocol, risk analysis, monitoring procedures, and the manufacturing and labeling plan. A protocol that is written without awareness of how it will be incorporated into the IDE application requires downstream revision — we write device protocols from the outset with the IDE structure in mind.
Inclusion and exclusion criteria determine who is actually enrolled in the trial and, consequently, the generalizability of the study results to the labeled intended-use population. Criteria that are too restrictive produce a trial population that doesn't reflect real-world use — a concern FDA will raise during PMA review if the indicated population is broader than the studied population. Criteria that are too permissive create safety risks and confounders that complicate the analysis.
We develop I/E criteria in consultation with clinical advisors and regulatory strategy, cross-referenced against the intended use statement and any relevant FDA guidance on the device type. Eligibility criteria are also a site feasibility tool: criteria that make sense scientifically but make enrollment practically impossible at real-world sites will generate protocol amendments mid-study — which require FDA and IRB approval, cause enrollment delays, and add cost.
The IRB submission package includes more than the protocol. Depending on the IRB, it includes the informed consent form (ICF), investigator brochure or device description, case report form samples, recruitment materials, and the sponsor's contact information. ICF development requires balancing FDA's plain-language requirements (45 CFR 46.116) with the disclosure obligations under 21 CFR 50 — particularly for significant-risk devices where the risk disclosure section of the ICF will be closely reviewed.
Protocol amendments require re-submission to both FDA (for approved IDEs) and the IRB. We manage the amendment calendar to ensure that scientific amendments are batched where possible to reduce IRB submission burden, and that administrative amendments that require expedited IRB review are distinguished from those requiring full board review.
Get Started
A protocol that satisfies the IRB but fails to produce FDA-acceptable data is a costly mistake. We write protocols designed to survive the scrutiny of both the institutional and regulatory review process.