RRegscribe
← Knowledge base

ISO 14155:2020 (Medical Device Clinical Investigations / GCP)

Good Clinical Practice for clinical investigations of medical devices.

ISO 14155:2020 Audit-Readiness Rubric — Clinical Investigation of Medical Devices (GCP)

What this is: Clinical investigation of medical devices for human subjects — Good clinical practice. The device-specific counterpart to Regscribe's existing EMA GCP inspection framework (drug trials). Relevant wherever a customer runs a pre-market clinical investigation, a Post-Market Clinical Follow-up (PMCF) study, or any other device clinical investigation under EU MDR Article 62 or Article 82, or under an FDA Investigational Device Exemption (IDE, 21 CFR Part 812).

Sourcing note: ISO 14155's full clause/annex text is copyrighted and sold by ISO (the standard runs 90+ pages across 10 clauses and 10 annexes; iso.org sells it, no free preview was fetched this session). No verbatim clause text is used below — this is structure and paraphrase built from secondary sources cross-checked across multiple independent providers: Greenlight Guru's "Ultimate Guide" and CIP/SAE guides, Johner Institute's DIN EN ISO 14155 blog and MDR clinical-investigations blog, Qualio's overview, CCMO (Dutch national ethics-review body) investigator guidance pages, IntuitionLabs' ISO 14155-vs-ICH-GCP comparison, and ClinicalLeader's ISO 14155 primer. Where a source could not be fetched cleanly (two PDF fetches — a Drexel University investigator-guidance PDF and the European Commission's MDCG 2024-5 guidance PDF — returned corrupted/binary content this session and were not used) that gap is flagged explicitly rather than filled with guessed content. eCFR.gov's own pages for 21 CFR 812 redirected to a bot-block page (unblock.federalregister.gov) and were not followed per this session's fetch policy; the FDA IDE (21 CFR 812) material below is therefore sourced from search-result snippets that explicitly quote the regulatory text (e.g. §812.150 UADE timelines), not a direct primary-source fetch — flagged as weaker sourcing than a clean eCFR read, worth a follow-up direct fetch before production use.

One item surfaced by two independent secondary sources but could not be corroborated and is explicitly not relied upon below: references to an "ISO 14155:2021" version number (Johner Institute) and to "the 2026 edition" of ISO 14155 introducing Clinical Events Committees / an estimand framework (IntuitionLabs). ISO's own catalog record (iso.org/standard/71690.html, seen in search results) identifies the current published edition as ISO 14155:2020 with no superseding edition confirmed. Treat any "2021" or "2026 edition" reference as likely error/speculation in the secondary source, not fact, until independently verified against iso.org directly.


Rubric legend

Each row: Requirement (plain language) → Citation → Evidence that demonstrates compliance → Common failure pattern


Part A — Structure and scope of ISO 14155:2020

The standard is organized as 10 clauses plus annexes. Clauses 1–3 (Scope, Normative references — including ISO 14971 — and Terms/definitions) are reference-only, not independently auditable. Clauses 4–10 are the substantive requirements, confirmed convergently across Greenlight Guru, Johner Institute, and Qualio:

ClauseTitleContent
4Good Clinical Practice (GCP) principlesSummarizes the standard's underlying GCP principles; sources note this section was revised in 2020 to align more closely with ICH E6(R2)'s GCP principles
5Ethical considerationsEthics committee (EC)/IRB communication, informed consent, vulnerable populations, subject information, prohibition on improper inducement, precedence of subject rights/safety/well-being over scientific/sponsor interest, alignment with the current Declaration of Helsinki
6Clinical investigation planningInvestigational device requirements, trial design, site selection, essential documentation, risk management activities (§6.2), design justification (§6.3)
7Clinical investigation conductPractical implementation, adverse event/device deficiency documentation and reporting, monitoring, subject confidentiality, risk assessment for potentially unacceptable risk (§7.4.4), document/data control (§7.8), electronic clinical data system validation (§7.8.3)
8Suspension, termination and close-outStudy closure procedures, Clinical Investigation Report content, risk (re-)evaluation, document retention
9Responsibilities of the sponsorOverall accountability for planning/conduct even when activities are contracted out; clinical quality management integrated into the manufacturer-sponsor's existing QMS (ISO 13485 tie-in); quality assurance/quality control
10Responsibilities of the principal investigatorDay-to-day management per the CIP; data integrity; safeguarding subject rights/safety/well-being

Normative annexes (i.e., these carry requirements, not just guidance): Annex A — Clinical Investigation Plan (CIP) content, 18 sections (A.1–A.18); Annex B — Investigator's Brochure (IB) minimum content; a Clinical Investigation Report content annex; and an essential-documents annex. Informative annexes (guidance, not mandatory content): Case Report Form (CRF) guidance, an adverse-event categorization annex (commonly cited as "Annex F"), an ethics-committee-responsibilities annex ("Annex G"), an ISO 14971 risk-management-application annex ("Annex H"), a clinical-development-stage/applicability annex ("Annex I" — covers pre-market, PMCF, and both interventional and observational investigation types, explicitly rebutting the misconception that "the device is already CE-marked, so the standard doesn't apply"), and a clinical-investigation-audit-guidance annex ("Annex J"). Flag: the specific letter-to-content mapping for the informative annexes (F/G/H/I/J) is consistent across the two sources that enumerated it (Greenlight Guru, Qualio) but was not independently verified against the standard itself — treat annex letters as reasonably confident, annex numbering exhaustiveness (i.e., whether there are exactly 10 annexes, A–J, with nothing skipped or renumbered) as unconfirmed.

#RequirementCitationEvidenceCommon failure pattern
1GCP principles (broadly aligned with ICH E6(R2)) must underpin the entire investigation — subject rights/safety/well-being take precedence over the interests of science and the sponsor.ISO 14155:2020, Clause 4–5Written GCP-compliance statement in the CIP; training records showing site staff trained on GCP principles specific to this investigationSites/CROs applying a generic drug-trial GCP training package without device-specific adaptation (covered in Part F below)
2A risk management process must be applied and documented throughout the entire clinical investigation lifecycle (not just at design), explicitly linked to ISO 14971.ISO 14155:2020, §6.2, Annex HRisk management plan/file for the investigation, cross-referenced to the device's ISO 14971 risk management file; evidence risk file was updated as the investigation progressed, not only at initiationRisk file created once at study start and never revisited as adverse events/device deficiencies accumulate during conduct — structurally the same gap flagged for the device QMS risk file in Regscribe's ISO 13485 rubric (§7.1)
3The investigation's applicability and required rigor differ by clinical development stage and investigation type (first-in-human/feasibility vs. pivotal vs. PMCF; interventional vs. observational) — a CE-marked device is not automatically outside scope.ISO 14155:2020, Annex IDocumented rationale in the CIP for which investigation-type category applies and why, referencing the device's current regulatory/certification statusSponsors treating a PMCF study on an already-CE-marked device as exempt from CIP/monitoring rigor because "the device is already approved"

Part B — Clinical Investigation Plan (CIP) requirements (Annex A)

Annex A is confirmed (Greenlight Guru) to run 18 sections (A.1–A.18) across roughly 9 pages. The section-by-section content below was recovered for A.1 through A.8, A.13, and A.14 from a direct fetch of Greenlight Guru's CIP guide; content for A.9–A.12 and A.15–A.18 was not recoverable this session (not found in any successfully-fetched source) and is not guessed — flagged as a gap below rather than filled with invented section titles. Based on the general shape of comparable CIP/protocol standards and the topics ISO 14155 clauses 5–8 must feed into, A.9–A.18 almost certainly cover items such as safety/AE definitions and reporting procedures in more detail, deviation handling, publication policy, and administrative/signature pages, but this is inference, not a confirmed source-backed list — do not present it to a customer as verified.

#RequirementCitationEvidenceCommon failure pattern
4The CIP must contain general/administrative information: title, reference number, sponsor details and funding source, principal/coordinating investigator and site identification, and a synopsis (inclusion/exclusion criteria, subject count, duration, follow-up, objectives, endpoints).ISO 14155:2020, Annex A.1Approved, version-controlled CIP with all A.1 elements present and internally consistent with the synopsisSynopsis figures (subject count, duration) drifting out of sync with the detailed body text after protocol amendments
5The CIP must describe the investigational device: intended purpose/indications for use, target patient population, manufacturer, model/type and software version, device traceability procedures, and comparator device details if applicable.ISO 14155:2020, Annex A.2Device description section cross-referenced to the current IFU and Medical Device File (ISO 13485 §4.2.3 tie-in)Device description referencing an outdated device/software version after an in-study design change
6The CIP must provide scientific/design justification: rationale grounded in the clinical evaluation's conclusions, an evaluation of preclinical testing and any prior clinical investigations, evaluation of relevant clinical data, and description of the clinical development stage.ISO 14155:2020, Annex A.3Design-justification section citing specific preclinical reports/prior investigation IDs, not just general statementsJustification section written as generic boilerplate not traceable to the specific device's own preclinical/clinical evidence package
7The CIP must present anticipated clinical benefits, anticipated adverse effects, and participation risks, plus risk control/mitigation measures integrated with the device's ISO 14971 risk management file.ISO 14155:2020, Annex A.4Benefit-risk section with explicit cross-reference to risk management file entries and mitigation controlsBenefit-risk analysis performed once pre-study with no linkage shown to the live risk management file
8The CIP must state objectives and hypotheses: purpose and performance claims under investigation, primary/secondary objectives, study framework (superiority/non-inferiority/equivalence), and scientific justification for chosen effect sizes/margins.ISO 14155:2020, Annex A.5Objectives section with a stated, justified statistical framework and margin, not just "device will be shown safe and effective"Non-inferiority margin stated without a documented scientific/clinical justification for that specific margin
9The CIP must define study design: randomization/blinding/group structure and control rationale (A.6.1); device exposure and concomitant medications/devices (A.6.2); subject selection and withdrawal criteria (A.6.3); investigation procedures (A.6.4); and the monitoring plan, including source data access/verification (A.6.5).ISO 14155:2020, Annex A.6.1–A.6.5CIP design section covering all five sub-elements; separately, an approved monitoring plan document consistent with A.6.5Monitoring plan referenced in the CIP but not actually produced/approved as a standalone document, or inconsistent with what's described in A.6.5
10The CIP must define the statistical design and analysis: analysis populations, descriptive statistics for baseline/treatment/safety/endpoints, analytical procedures, confidence intervals, significance levels/testing strategy, and sample size calculation with justification.ISO 14155:2020, Annex A.7Statistical analysis plan (SAP), either embedded in the CIP or as a referenced standalone document, with a documented sample-size calculationSample size stated without a traceable calculation/assumptions (effect size, variance, power) behind the number
11The CIP must define data management: CRF tracking procedures, data review/database cleaning process, electronic data system verification/validation, and data security procedures.ISO 14155:2020, Annex A.8Data management plan; validation records for the EDC/eCRF system used (see also §7.8.3 below)Data management plan referencing a generic EDC vendor validation certificate rather than validation specific to this study's build/configuration
12The CIP must define the informed consent process: general consent procedures, protocol for communicating new information to subjects that could affect their willingness to continue, and eConsent procedures if used.ISO 14155:2020, Annex A.13Approved informed consent form (ICF) version(s), consent-process SOP, and (if applicable) eConsent platform validationICF not re-consented/updated when new safety information (e.g. a newly identified device deficiency pattern) emerges mid-study
13The CIP must define adverse event and device deficiency identification and reporting procedures, distinguishing AE/ADE/SAE/SADE/device-deficiency categories and specifying reporting protocols/timelines consistent with Clause 7 and the sponsor/investigator responsibility clauses.ISO 14155:2020, Annex A.14AE/device-deficiency reporting procedure embedded in or referenced by the CIP, with defined internal timelines that are at least as strict as applicable regulatory timelines (see Part D)CIP states generic "report promptly" language without defined day-counts, leaving investigators to guess at the applicable regulatory deadline

Gap, flagged explicitly: Annex A.9–A.12 and A.15–A.18 content was not recovered from any source successfully fetched this session. Recommend a follow-up pass specifically targeting a legally-obtained copy of ISO 14155:2020 (e.g. via a paid ANSI/AAMI or BSI purchase) before treating the CIP rubric section as complete — roughly 8 of 18 Annex A sections are undocumented above.


Part C — Investigator's Brochure (IB) requirements (Annex B)

Confirmed convergently (Greenlight Guru, CCMO, Qualio) that Annex B is normative and specifies minimum IB content. The IB's purpose is to give the principal investigator and site team sufficient safety/performance data to justify human exposure to the investigational device and to justify the investigation proposed in the CIP.

#RequirementCitationEvidenceCommon failure pattern
14The IB must carry clear administrative identification: investigational device name, document reference number, version, date, sponsor's and manufacturer's contact details, a confidentiality statement, revision history summary, and table of contents.ISO 14155:2020, Annex BCurrent, version-controlled IB with all identification elements presentIB circulating at sites in an outdated version with no visible revision history, so site staff can't confirm they hold the current safety information
15The IB must summarize preclinical testing performed on the device, with an evaluation of results justifying human use.ISO 14155:2020, Annex BIB preclinical-testing section citing specific test reports/results, not summary assertions onlyPreclinical section describing tests performed without stating results/conclusions, leaving the investigator unable to independently judge justification for human exposure
16The IB must summarize existing clinical data relevant to the investigational device, available at the time of application.ISO 14155:2020, Annex BIB clinical-data section referencing prior investigation IDs/publications, cross-checked against the CIP's Annex A.3 design-justification section for consistencyIB and CIP citing inconsistent sets of prior clinical evidence (a cross-document consistency check Regscribe should score explicitly)
17The IB must address risk management of the investigational device, consistent with the ISO 14971 risk management file (per Annex H's explicit tie between ISO 14971 and the clinical investigation process).ISO 14155:2020, Annex B, Annex HIB risk section referencing the device's risk management file/known-risk listIB's stated known-risk list omitting risks that are already logged in the device's ISO 14971 risk management file
18The IB must include regulatory and other references relevant to the device and investigation.ISO 14155:2020, Annex BReference list/bibliography section in the IBN/A — thin sub-requirement, rarely a standalone finding on its own
19For investigations falling under MDR Article 74(1) (PMCF-type studies on a CE-marked device used within its approved intended purpose), the device's Instructions for Use (IFU) may substitute for a full IB.EU MDR Art. 74(1) (cross-referenced by ISO 14155:2020 Annex B per CCMO guidance)Documented determination of which pathway applies (full IB vs. IFU-only) with rationaleApplying the IFU-only shortcut to a study that in fact falls outside the device's approved intended purpose, when a full IB was actually required

Sourcing caveat: the European Commission's MDCG 2024-5 guidance document on IB content (referenced by multiple sources as the current EU interpretive guidance layered on top of Annex B) was fetched this session but returned corrupted/binary PDF content and could not be read — its specific content expectations are not reflected above. Recommend a follow-up direct fetch or manual download from health.ec.europa.eu before treating IB scoring as complete against current EU expectations, since MDCG guidance is where regulators typically add prescriptive detail beyond the ISO text.


Part D — Adverse event / device deficiency reporting (and how it differs from drug-trial AE reporting)

Definitions, confirmed convergently (Greenlight Guru's SAE guide, IntuitionLabs comparison, general search-result convergence):

  • Adverse Event (AE): any untoward medical occurrence, unintended disease/injury, or untoward clinical sign in a subject, user, or other person — whether or not related to the device, whether anticipated or unanticipated.
  • Serious Adverse Event (SAE): an AE resulting in death, life-threatening illness, permanent impairment, hospitalization (or prolongation), or fetal distress/congenital abnormality.
  • Adverse Device Effect (ADE): an AE related to use of the investigational device, including events from inadequate instructions, device malfunction, or use error.
  • Serious Adverse Device Effect (SADE): an ADE meeting SAE severity criteria; sub-categorized as Anticipated (ASADE) or Unanticipated (USADE) depending on whether it was already identified in the pre-study risk assessment.
  • Device Deficiency: inadequacy of the device regarding identity, quality, durability, reliability, usability, safety, or performance — includes malfunctions, use errors, and inadequate labelling. Per ISO 14155:2020 §7.4.2 (cross-referenced to §9.2.5 and §10.8), a device deficiency that did not lead to an AE but could have led to a SADE must still be reported — this is the key device-specific reporting trigger with no direct drug-trial equivalent.
#RequirementCitationEvidenceCommon failure pattern
20Investigators must document all AEs in a timely manner throughout the investigation, assess causality, and report SAEs and device deficiencies that could have led to a SADE to the sponsor, the ethics committee, and (per CIP-defined timelines) regulators.ISO 14155:2020, §7.4.2, §9.2.5, §10.8AE log with causality assessment field completed for every entry; sponsor/EC notification records timestamped against event-awareness datesAE causality field left blank or defaulted to "unrelated" without documented rationale — a data-integrity-adjacent finding analogous to the "human error" CAPA gap flagged in Regscribe's ISO 13485 rubric
21Sponsors must classify AEs, evaluate ongoing safety, and report SAEs/SADEs to ethics committees and regulatory authorities within the timeframes defined by the CIP and applicable jurisdictional regulation, and report to any Data Monitoring Committee per written procedure.ISO 14155:2020, §7.4, §9.2.5Sponsor safety-evaluation procedure; SAE/SADE notification log showing dates-to-regulator against CIP-defined deadlinesSponsor-side safety evaluation performed but not documented as feeding back into an updated risk assessment (§7.4.4)
22Under the US FDA IDE pathway (21 CFR 812), investigators must report any Unanticipated Adverse Device Effect (UADE) to the sponsor and reviewing IRB as soon as possible, and no later than 10 working days after first learning of the effect (search-result-sourced convention for death/serious injury is faster reporting; not independently confirmed against the primary eCFR text this session — flag before citing as a hard deadline). Sponsors evaluating a UADE must report results to FDA, all reviewing IRBs, and all participating investigators within 10 working days of first notice.21 CFR 812.150(a)(1) [investigator], 812.150(b)(1) [sponsor] — sourced from search-result snippets quoting eCFR text; eCFR.gov itself redirected to a bot-block page this session and was not directly fetchedUADE report with date-of-awareness and date-of-notification fields, demonstrating the ≤10-working-day window was metUADE reported to the sponsor within window, but sponsor's onward evaluation/notification to FDA and all sites slips past its own 10-working-day clock — a two-stage timeline that's easy to satisfy at the first hop and miss at the second
23Key structural difference from drug-trial AE reporting (per IntuitionLabs' comparison, cross-referenced against the general shape of ICH E6/EMA GCP pharmacovigilance which Regscribe's existing EMA GCP rubric already covers): device trials add a device deficiency reporting category with no drug-trial equivalent (malfunctions/use errors/labelling inadequacies that could have caused harm, reported even absent an actual AE), whereas drug trials center on Suspected Unexpected Serious Adverse Reactions (SUSARs) tied to pharmacological/toxicological causality — a fundamentally different causality question (did the substance cause this reaction, vs. did the device malfunction or get used incorrectly).ISO 14155:2020 vs. ICH E6(R2)/EU CTR pharmacovigilance framework (comparison synthesized from IntuitionLabs; drug-side framework detail should be cross-checked against Regscribe's existing EMA GCP rubric rather than re-derived here)For Regscribe's data model: a distinct device_deficiency_log evidence type, separate from (but cross-referenced to) the adverse_event_log/SAE_log evidence type shared conceptually with the drug-trial rubricDevice sponsors reusing a drug-trial AE reporting template that has no field for "device deficiency without associated AE," silently dropping a device-specific reporting obligation

Part E — Documents / evidence needed for audit readiness

Compiled from the clause/annex mapping above, cross-checked for internal consistency against the CIP/IB annex content in Parts B–C:

  • Trial-design/authorization documents: approved Clinical Investigation Plan (CIP) and all amendments; ethics committee (EC)/IRB approval letters and continuing-review records; national competent authority authorization or notification records (EU MDR Art. 62/70 authorization, or Art. 82/74 notification, as applicable); FDA IDE approval (if a significant-risk device study under 21 CFR 812) or IRB-only approval (if non-significant-risk).
  • Device-specific documentation: Investigator's Brochure (current version, with revision history); Medical Device File / device technical documentation cross-reference (ISO 13485 §4.2.3 tie-in); device shipping/traceability logs; device accountability records (receipt, use, return/destruction per subject/site); device labelling used in the investigation; instructions for use (IFU) provided to sites.
  • Site/investigator agreements: signed investigator agreements defining responsibilities; investigator CVs/qualifications and delegation-of-authority logs; site initiation/training records (device-specific, not generic GCP training only).
  • Subject-level documents: signed/dated informed consent forms (ICFs) — including any re-consent triggered by new safety information; case report forms (CRFs) with source-data-verification evidence; subject screening/enrollment logs; withdrawal/discontinuation records with reasons.
  • Safety documents: AE/ADE/SAE/SADE log with causality assessments; device deficiency log (including deficiencies that did not cause an AE but could have caused a SADE); UADE reports (US IDE studies) with date-of-awareness vs. date-of-notification fields; sponsor safety evaluations and any resulting CIP/risk-file amendments; Data Monitoring Committee records if applicable.
  • Monitoring documents: monitoring plan (risk-based, per §A.6.5); monitoring visit reports; source data verification records; centralized-monitoring records where used in place of/alongside on-site visits.
  • Quality/data-integrity documents: data management plan; EDC/eCRF system validation records specific to the study build (§7.8.3); audit trail exports; deviation/protocol-non-compliance log with root-cause/CAPA where applicable.
  • Close-out documents: Clinical Investigation Report (per the normative report-content annex); final device accountability reconciliation; document retention confirmation; any suspension/termination rationale and notifications, if applicable.

Part F — Common failure patterns

Sourcing caveat, stated up front: no source located this session provides a named, quantified deficiency database specific to device clinical investigations the way MHRA's published GMP/GDP deficiency-trend PDFs anchor Regscribe's GMP/GDP rubric. FDA's own Bioresearch Monitoring (BIMO) program inspects clinical investigators, sponsors, IRBs, and CROs across drug, biologic, and device studies together, and the one detailed secondary source fetched this session (Goodwin Law's BIMO violations summary) explicitly does not break its findings out by device vs. drug — it states devices are part of the ~79% "drug, biologic, or medical device" inspection population without device-specific statistics. The patterns below are therefore a mix of (a) general BIMO/clinical-investigator findings that are directly applicable to device studies since the same regulations (21 CFR Parts 50, 56, 812) govern them, and (b) device-specific structural gaps called out by ISO 14155 secondary-source commentary. Flagged as qualitative, not a quantified named database, consistent with how Regscribe's ISO 13485 rubric already flags this same class of gap.

  1. Informed consent deficiencies — missing signatures, use of outdated ICF versions, enrollment before consent is properly obtained. Applies identically to device and drug studies under 21 CFR Part 50. (FDA BIMO general finding, Goodwin Law summary; FIU IRB warning-letter compendium referenced but not readable this session — flagged)
  2. Failure to follow the investigational plan / CIP — protocol deviations not properly captured, evaluated, or reported; this is FDA's #1-cited BIMO finding category across investigator inspections generally. (Goodwin Law, FDA BIMO)
  3. Inadequate case history / study records — incomplete or inaccurate CRFs and source documentation. (Goodwin Law, FDA BIMO)
  4. Device accountability gaps — the device-specific analogue of drug accountability findings: incomplete receipt/use/disposition records for the investigational device, weaker device traceability than the standard's Annex A.2/CIP requirement calls for.
  5. Safety reporting failures — AEs/device deficiencies not reported, or not reported within the CIP-defined or regulatory timeline; this is the category where the two-stage UADE clock (investigator→sponsor, then sponsor→FDA/IRBs/sites, Part D above) is most likely to slip at the second hop. (Goodwin Law, FDA BIMO; UADE-specific structure per 21 CFR 812.150)
  6. Sponsor monitoring/oversight gaps — FDA's stated expectation is that sponsors detect and correct site-level non-compliance through monitoring; lack of supervision over sub-investigators/coordinators is cited as a recurring root cause. (Goodwin Law, FDA BIMO)
  7. Device-specific training gaps — organizations applying generic GCP training to device trial staff without device-specific operation/deficiency-recognition training; flagged by ISO 14155 secondary-source commentary (ClinicalLeader primer) as a frequently-overlooked compliance gap distinct from drug-trial GCP training.
  8. Risk file / CIP drift — risk management file and CIP not kept current as the investigation surfaces new device deficiencies or AEs, mirroring the same "risk file frozen at initial approval" pattern already flagged in Regscribe's ISO 13485 rubric (§7.1) — this is a structural risk that recurs across the device-QMS and device-clinical-investigation rubrics because both trace back to the same ISO 14971 risk management file.
  9. IB/CIP evidence-base inconsistency — the Investigator's Brochure's clinical-data summary and the CIP's design-justification section (Annex A.3) citing different or inconsistent sets of prior evidence — a cross-document consistency check that plays directly to Regscribe's document-comparison capability.

Part G — FDA IDE (21 CFR Part 812) overlay — how it layers on ISO 14155

Analogous to how Regscribe's ISO 13485 rubric documents the FDA QMSR incorporation of ISO 13485 by reference, ISO 14155 is not itself a binding US regulation — it is a voluntary, internationally-recognized standard that EU MDR treats as a harmonized standard, while FDA does not legally mandate ISO 14155 for IDE studies but expects GCP-consistent conduct and separately regulates the same activities directly through 21 CFR Part 812 (device studies), Part 50 (informed consent), and Part 56 (IRBs). Per the IntuitionLabs comparison (single-sourced, not independently cross-checked this session), where ISO 14155 and FDA regulations differ, the more stringent requirement is expected to apply — flagged as a claim worth verifying against FDA's own IDE guidance before it is presented to a customer as settled FDA policy.

Practical implication for Regscribe's positioning: a device sponsor running a global (EU + US) clinical investigation needs a CIP built to ISO 14155 Annex A that is also consistent with 21 CFR 812's investigational plan requirements (812.25) and reporting timelines (812.150) — directly analogous to the "Evidence Type" layer already recommended in the GMP/GDP rubric's Part C. A single ISO 14155-anchored gap analysis, with a bounded FDA-IDE overlay module for US-specific items (UADE 10-working-day dual-stage reporting, Form FDA 1572-equivalent site agreements, IRB-specific significant-risk/non-significant-risk determinations), should serve both EU/international and US-market device-trial customers from largely the same evidence base.


Gaps / follow-ups

  1. ISO 14155:2020 Annex A, sections A.9–A.12 and A.15–A.18 (roughly 8 of 18 CIP sections) were not recoverable from any source successfully fetched this session — flagged explicitly in Part B rather than filled with invented content. Needs a legally-obtained copy of the standard (ANSI/AAMI or BSI purchase) for completeness.
  2. MDCG 2024-5 (EU guidance specifically on Investigator's Brochure content) returned corrupted/binary PDF content on fetch and could not be read — flagged in Part C. This is the document EU regulators use to add prescriptive detail beyond Annex B's minimum, so it matters for EU-market scoring accuracy.
  3. 21 CFR 812.150 (UADE reporting) primary text was not directly fetched — eCFR.gov redirected to a bot-block page this session. The 10-working-day timelines in Part D/row 22 are sourced from search-result snippets quoting the regulation, not a direct read. Recommend a follow-up fetch via federalregister.gov's eCFR mirror or a manual read.
  4. No named, quantified device-clinical-investigation deficiency database (FDA BIMO device-specific breakout, or EU Notified Body/competent-authority clinical-investigation inspection findings) was located this session — flagged in Part F, consistent with the same class of gap already flagged in Regscribe's ISO 13485 rubric. Worth a follow-up pass on FDA's Form 483/Warning Letter database filtered to device clinical investigators specifically (as opposed to drug/biologic), and/or individual EU competent authorities' (BfArM, MHRA-equivalent-for-devices) published inspection findings if any exist.
  5. Annex letter-to-content mapping (F–J) for the informative annexes (adverse event categorization, ethics committee guidance, ISO 14971 application, applicability/development-stage guidance, audit guidance) is confirmed only by two convergent secondary sources (Greenlight Guru, Qualio), not independently verified against the standard — flagged in Part A.
  6. "ISO 14155:2021" and "2026 edition" references found in two secondary sources were explicitly not incorporated into this rubric as fact — flagged in the top-level sourcing note. If Regscribe later confirms via iso.org that a new edition has actually been published or is imminent, this entire rubric should be revisited against the new edition/DIS text.
  7. Relationship to Regscribe's existing EMA GCP (drug-trial) rubric — Part D above synthesizes the SUSAR-vs-device-deficiency distinction from a single comparison source (IntuitionLabs) rather than re-deriving the drug-trial side from Regscribe's own EMA GCP rubric directly. Recommend a follow-up pass that opens the EMA GCP rubric file itself and does a clause-by-clause reconciliation (the way the GMP/GDP rubric's Part C reconciles Annex 11 against Part 11), rather than relying on a third-party's characterization of both frameworks.
  8. Certification/inspection process mechanics (who inspects device clinical investigations — national competent authorities under MDR, FDA BIMO under IDE, both — and what a typical inspection scope/duration looks like) was not separately researched this session beyond what's captured in Parts D/F/G. Flagged as a possible follow-up if Regscribe wants an "inspection readiness" section analogous to the ISO 13485 rubric's certification-process section.