eduKateSG · Why Science?
Read clinical-study permission without confusing it with market approval
Use FDA IDE resources through significant-risk, nonsignificant-risk and exempt studies, sponsor and investigator duties, IRB review, applications, 30-day decisions, conditions, supplements and early feasibility studies.
A medical device often needs human clinical evidence before a regulator can decide whether it should reach the market. The Investigational Device Exemption, or IDE, creates a controlled route for collecting that evidence.
The first science skill is classification: identify whether the investigation is significant risk, nonsignificant risk or exempt, then follow the correct FDA and IRB route. The second is language: permission to study is not permission to sell.
Did you know? For a significant-risk device study, FDA and an IRB generally must approve the investigation before it begins. Nonsignificant-risk studies use abbreviated IDE requirements and normally proceed through IRB review without a separate FDA IDE application.
This guide supports regulatory and research literacy. It does not provide clinical, legal or study-specific advice.
Chapter index
Chapters 1–9: study risk, roles and participant safeguards
- 1. An IDE permits investigational use
- 2. Study permission is not marketing authorization
- 3. Risk is assigned to the investigation
- 4. Significant-risk studies need two approvals
- 5. Nonsignificant-risk studies follow abbreviated requirements
- 6. Some investigations are exempt
- 7. The sponsor owns core responsibilities
- 8. Investigators protect participants at the site
- 9. The IRB protects rights and welfare
Chapters 10–17: application content, FDA decisions, changes and reports
- 10. The application joins evidence and operations
- 11. FDA assigns an IDE number and receipt date
- 12. The 30-day rule needs exact wording
- 13. Conditional approval is not unrestricted approval
- 14. Supplements document important changes
- 15. Unanticipated adverse device effects trigger duties
- 16. Early feasibility studies answer early questions
- 17. A strong IDE receipt keeps roles and dates
An Investigational Device Exemption becomes understandable when study risk, sponsor, protocol, IRB review and FDA decision remain connected. An Investigational Device Exemption allows an investigational device to be used in a clinical study to collect safety and effectiveness data under applicable controls. This helps students separate permission to investigate from permission to market.
Try this
Evidence question: Which official record or guidance supports the point about an ide permits investigational use? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the identifier, date, source and one limit for an ide permits investigational use. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for an ide permits investigational use, its identifier or version context, and one limit that must remain visible.
CHAPTER 2 OF 17 · Classify the investigation
2. Study permission is not marketing authorization
Clinical study permission is a route for collecting evidence, not a finding that a device is safe and effective for marketing. IDE approval permits a clinical investigation to proceed; it does not clear or approve the device for commercial distribution. It also keeps the roles of FDA, the IRB, sponsor and investigator visible.
Try this
Evidence question: Which official record or guidance supports the point about study permission is not marketing authorization? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the identifier, date, source and one limit for study permission is not marketing authorization. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for study permission is not marketing authorization, its identifier or version context, and one limit that must remain visible.
CHAPTER 3 OF 17 · Classify the investigation
3. Risk is assigned to the investigation
The IDE framework applies different controls to significant-risk, nonsignificant-risk and exempt investigations. Significant-risk and nonsignificant-risk determinations concern the proposed study and device use, so the same device can require contextual analysis. The IDE number and protocol create a repeatable evidence route.
Try this
Evidence question: Which official record or guidance supports the point about risk is assigned to the investigation? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the identifier, date, source and one limit for risk is assigned to the investigation. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for risk is assigned to the investigation, its identifier or version context, and one limit that must remain visible.
CHAPTER 4 OF 17 · Classify the investigation
4. Significant-risk studies need two approvals
Dates and approval conditions matter because a study can change through supplements and reports. A significant-risk device study generally requires an FDA-approved IDE and Institutional Review Board approval before the investigation begins. Participant decisions still depend on informed consent and qualified clinical oversight.
Try this
Evidence question: Which official record or guidance supports the point about significant-risk studies need two approvals? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the identifier, date, source and one limit for significant-risk studies need two approvals. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for significant-risk studies need two approvals, its identifier or version context, and one limit that must remain visible.
CHAPTER 5 OF 17 · Build the application
5. Nonsignificant-risk studies follow abbreviated requirements
An Investigational Device Exemption becomes understandable when study risk, sponsor, protocol, IRB review and FDA decision remain connected. A nonsignificant-risk study generally proceeds through IRB review under abbreviated IDE requirements without a separate IDE application to FDA. This helps students separate permission to investigate from permission to market.
Try this
Evidence question: Which official record or guidance supports the point about nonsignificant-risk studies follow abbreviated requirements? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the identifier, date, source and one limit for nonsignificant-risk studies follow abbreviated requirements. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for nonsignificant-risk studies follow abbreviated requirements, its identifier or version context, and one limit that must remain visible.
Clinical study permission is a route for collecting evidence, not a finding that a device is safe and effective for marketing. Diagnostic and other investigations may be exempt from parts of the IDE regulation when the regulatory criteria are met; exemption should be documented, not assumed. It also keeps the roles of FDA, the IRB, sponsor and investigator visible.
Try this
Evidence question: Which official record or guidance supports the point about some investigations are exempt? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the identifier, date, source and one limit for some investigations are exempt. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for some investigations are exempt, its identifier or version context, and one limit that must remain visible.
The IDE framework applies different controls to significant-risk, nonsignificant-risk and exempt investigations. Sponsors select qualified investigators, provide the investigational plan, monitor the study, control device distribution and maintain required records and reports. The IDE number and protocol create a repeatable evidence route.
Try this
Evidence question: Which official record or guidance supports the point about the sponsor owns core responsibilities? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the identifier, date, source and one limit for the sponsor owns core responsibilities. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for the sponsor owns core responsibilities, its identifier or version context, and one limit that must remain visible.
CHAPTER 8 OF 17 · Build the application
8. Investigators protect participants at the site
Dates and approval conditions matter because a study can change through supplements and reports. Clinical investigators follow the plan and consent process, supervise device use, protect subjects, report required events and maintain study records. Participant decisions still depend on informed consent and qualified clinical oversight.
Try this
Evidence question: Which official record or guidance supports the point about investigators protect participants at the site? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the identifier, date, source and one limit for investigators protect participants at the site. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for investigators protect participants at the site, its identifier or version context, and one limit that must remain visible.
An Investigational Device Exemption becomes understandable when study risk, sponsor, protocol, IRB review and FDA decision remain connected. The IRB reviews study risk, consent and safeguards, and can approve, require changes to or disapprove the investigation at an institution. This helps students separate permission to investigate from permission to market.
Try this
Evidence question: Which official record or guidance supports the point about the irb protects rights and welfare? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the identifier, date, source and one limit for the irb protects rights and welfare. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for the irb protects rights and welfare, its identifier or version context, and one limit that must remain visible.
CHAPTER 10 OF 17 · Read the decision
10. The application joins evidence and operations
Clinical study permission is a route for collecting evidence, not a finding that a device is safe and effective for marketing. A complete IDE application describes the sponsor, report of prior investigations, investigational plan, manufacturing information, monitoring, labeling and informed-consent materials. It also keeps the roles of FDA, the IRB, sponsor and investigator visible.
Try this
Evidence question: Which official record or guidance supports the point about the application joins evidence and operations? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the identifier, date, source and one limit for the application joins evidence and operations. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for the application joins evidence and operations, its identifier or version context, and one limit that must remain visible.
The IDE framework applies different controls to significant-risk, nonsignificant-risk and exempt investigations. The acknowledgement identifies the application and starts the review timeline, giving later amendments, supplements and reports a common anchor. The IDE number and protocol create a repeatable evidence route.
Try this
Evidence question: Which official record or guidance supports the point about fda assigns an ide number and receipt date? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the identifier, date, source and one limit for fda assigns an ide number and receipt date. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for fda assigns an ide number and receipt date, its identifier or version context, and one limit that must remain visible.
Dates and approval conditions matter because a study can change through supplements and reports. An IDE is considered approved 30 days after FDA receives it unless FDA earlier communicates approval, approval with conditions or disapproval. Participant decisions still depend on informed consent and qualified clinical oversight.
Try this
Evidence question: Which official record or guidance supports the point about the 30-day rule needs exact wording? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the identifier, date, source and one limit for the 30-day rule needs exact wording. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for the 30-day rule needs exact wording, its identifier or version context, and one limit that must remain visible.
CHAPTER 13 OF 17 · Follow study conduct
13. Conditional approval is not unrestricted approval
An Investigational Device Exemption becomes understandable when study risk, sponsor, protocol, IRB review and FDA decision remain connected. FDA may allow a study to begin under stated conditions while requiring identified issues to be addressed within the decision framework. This helps students separate permission to investigate from permission to market.
Try this
Evidence question: Which official record or guidance supports the point about conditional approval is not unrestricted approval? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the identifier, date, source and one limit for conditional approval is not unrestricted approval. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for conditional approval is not unrestricted approval, its identifier or version context, and one limit that must remain visible.
Clinical study permission is a route for collecting evidence, not a finding that a device is safe and effective for marketing. Changes to the protocol, device, manufacturing, investigators or study conduct can require prior approval or notice depending on the change and regulation. It also keeps the roles of FDA, the IRB, sponsor and investigator visible.
Try this
Evidence question: Which official record or guidance supports the point about supplements document important changes? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the identifier, date, source and one limit for supplements document important changes. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for supplements document important changes, its identifier or version context, and one limit that must remain visible.
CHAPTER 15 OF 17 · Follow study conduct
15. Unanticipated adverse device effects trigger duties
The IDE framework applies different controls to significant-risk, nonsignificant-risk and exempt investigations. Sponsors and investigators have prompt evaluation, reporting and risk-response obligations when an unanticipated adverse device effect occurs. The IDE number and protocol create a repeatable evidence route.
Try this
Evidence question: Which official record or guidance supports the point about unanticipated adverse device effects trigger duties? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the identifier, date, source and one limit for unanticipated adverse device effects trigger duties. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for unanticipated adverse device effects trigger duties, its identifier or version context, and one limit that must remain visible.
CHAPTER 16 OF 17 · Follow study conduct
16. Early feasibility studies answer early questions
Dates and approval conditions matter because a study can change through supplements and reports. An early feasibility study of a significant-risk device can provide proof-of-principle and initial clinical-safety information while design is still developing. Participant decisions still depend on informed consent and qualified clinical oversight.
Try this
Evidence question: Which official record or guidance supports the point about early feasibility studies answer early questions? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the identifier, date, source and one limit for early feasibility studies answer early questions. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for early feasibility studies answer early questions, its identifier or version context, and one limit that must remain visible.
CHAPTER 17 OF 17 · Follow study conduct
17. A strong IDE receipt keeps roles and dates
An Investigational Device Exemption becomes understandable when study risk, sponsor, protocol, IRB review and FDA decision remain connected. The most useful research note records the device, intended use, study risk, sponsor, protocol version, sites, IRB status, FDA decision, conditions, supplements and access date. This helps students separate permission to investigate from permission to market.
Try this
Evidence question: Which official record or guidance supports the point about a strong ide receipt keeps roles and dates? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the identifier, date, source and one limit for a strong ide receipt keeps roles and dates. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for a strong ide receipt keeps roles and dates, its identifier or version context, and one limit that must remain visible.
Contents · Previous chapter · Continue at the Science Learning Hub
An IDE claim becomes reliable when study risk, participant protection and FDA status stay together
The IDE route connects a clinical question to a controlled investigation. It teaches learners to identify which body made which decision and what that decision actually permits.
Save the IDE number, receipt date, sponsor, device, intended use, risk determination, protocol version, IRB status, FDA decision, approval conditions, supplements, safety reports and access date.
| Reading object | What it can support | Question to keep visible |
|---|---|---|
| Study risk | Determines the IDE and review route | Who made the determination? |
| IDE application | Presents evidence and a controlled study plan | Which protocol version? |
| FDA decision | Approval, approval with conditions or disapproval | What may begin? |
| IRB review | Protects participants at each institution | Is approval current? |
Sources and next reading
Substantive resource claims in this article were checked against the primary pages below. A structured record is a route into evidence; it does not by itself prove a scientific conclusion. Recheck the live record, evidence labels and release context before using it in assessed work or research.
For a classroom enquiry, save a short research receipt containing the question, search terms, selected object, exact identifier, version, access date and the evidence boundary you observed. Add the file or page that supports each statement. This small routine turns browsing into accountable science learning and gives a teacher, classmate or future analyst a route they can independently follow.
Before sharing the conclusion, ask another reader to retrace the route without verbal hints. If they reach a different version, file or interpretation, improve the receipt and narrow the claim. Reproducibility begins with this practical check. It teaches careful reading, supports fair collaboration and keeps uncertainty visible while evidence moves from an online service into notes, analysis and a final explanation.
A useful final review separates five questions. What object was found? Which organisation or repository maintains it? What exact evidence was inspected? Which statement does that evidence support? What remains uncertain? Answer each question in one sentence, then connect every answer to a visible field, file or source page. This review catches common mistakes: citing a collection when a file supplied the value, treating the newest release as the analysed release, confusing permission with scientific suitability, or turning a discovery count into a conclusion. It also gives students a calm way to improve work. A missing detail becomes a next research step instead of an invitation to guess. When the route is complete, the final explanation can stay simple because the identifiers, dates, versions, limitations and supporting evidence are already organised underneath it.
Primary sources
- FDA Investigational Device Exemption overview — accessed 25 October 2026.
- FDA IDE Approval Process — accessed 25 October 2026.
- FDA IDE Application — accessed 25 October 2026.
- FDA IDE Responsibilities — accessed 25 October 2026.
- FDA Early Feasibility Studies Guidance — accessed 25 October 2026.