Skip to main content
Leanabl Logo

Regulatory Approval · Technical File (STED/DHF) Gap Analysis

Eliminate DHF traceability and IMDRF STED deficiencies before official submission.

A defensible technical file is an engineered evidence graph, not a folder of PDFs. We audit your Design History File (DHF), IMDRF STED / EU MDR GSPR / FDA eSTAR structure, ISO 14971 risk traceability, and V&V reports before reviewers see them.

Domain Expertise

Deep regulatory authority across every medical device domain

SaMD · AI Digital Health

IEC 62304 & IEC 82304-1 Software Lifecycle · FDA PCCP & Good Machine Learning Practice

Multi-demographic dataset bias control and statistical validation design for Sensitivity, Specificity, and ROC-AUC

Active Devices · Robotics

IEC 60601-1 Ed. 3.2 & IEC 60601-1-2 Ed. 4.1 · IEC 60601-2-XX Particular Standards

Essential Performance definition and worst-case test matrix optimization across FDA, EU Notified Bodies, and MDSAP

Implants · Biomaterials

ISO 10993-1:2018 & ISO 10993-18 E&L · ISO 11135 / 11137 Sterilization & ISO 11607

Biological evaluation plans (BEP), ISO 10993-18 chemical characterization, and toxicological risk assessment (TRA)

In Vitro Diagnostics (IVD)

EU IVDR 2017/746 & FDA IVD Guidance · CLSI EP Guidelines (EP05, EP06, EP12, EP17, EP25)

CLSI-compliant Limit of Detection (LoD), precision, cross-reactivity, interference, and lot-to-lot reproducibility protocols

Proprietary Data & Precedent Validation

EU MDR GSPR · FDA eSTAR · IMDRF STED Multi-Regime Checklist Cross-Scan

100% Pre-Submission Detection of FDA RTA/AI & Notified Body Non-Conformity Triggers

Engineered 4-Stage Workflow

4-Stage Audit Pipeline from DHF Indexing to Actionable Remediation Roadmap

Step 01 / 04Stage Gate & Output

Complete DHF, STED, Risk File & Test Report Inventory Indexed

Incomplete baseline data or misclassified regulatory pathways are the primary drivers of multi-month submission delays. Gate 01 locks the device scope, predicate/standard mapping, and full document inventory before authoring begins.

Verification Baseline

Device description, intended use, existing test reports, and QMS document index

Gate Sign-Off Output

Confirmed classification matrix and locked submission master inventory

Agentic Automation & Platform Integration

Close DHF Gaps Directly Inside Leanabl PLM Traceability & eQMS Document Control

Automated Detection of Unverified Specs & Unmitigated Hazards

Flags any Design Input lacking a linked V&V protocol/report or any ISO 14971 hazard missing verification of risk control effectiveness.

@Document Control— Run "Automated Detection of Unverified Specs & Unmitigated Hazards" across our Technical File (STED/DHF) Gap Analysis records and call out the highest-priority compliance findings first.

I'll inspect the linked quality and dossier records against target regulatory standards, then report actionable findings with verified outputs.

Thought for 4.2s · Explored Document Control records & 14 regulatory clauses

P1 · Verified Agent Output· Complete DHF, STED, Risk File & Test Report Inventory Indexed

Flags any Design Input lacking a linked V&V protocol/report or any ISO 14971 hazard missing verification of risk control effectiveness. Full document lifecycle with version control

Standard Edition Transition & Gap Impact Tracking

Automatically identifies which DHF/STED sections require updates when FDA Consensus or EU Harmonized Standards are revised.

@Requirements Management— Run "Standard Edition Transition & Gap Impact Tracking" across our Technical File (STED/DHF) Gap Analysis records and call out the highest-priority compliance findings first.

I'll inspect the linked quality and dossier records against target regulatory standards, then report actionable findings with verified outputs.

Thought for 4.3s · Explored Requirements Management records & 14 regulatory clauses

P1 · Verified Agent Output· Single-Source Master Dossier to Multi-Region Submission Export

Maintains one remediated technical baseline that feeds both FDA eSTAR and EU MDR/IVDR technical documentation packages. Traceability from specification to verification

Service Specification

Service Scope & Final Deliverables

Scope

We verify end-to-end traceability, standard edition compliance, and evidentiary sufficiency across your technical dossier.

  • Line-by-line audit against EU MDR/IVDR GSPR checklists, FDA eSTAR templates, and IMDRF STED structure
  • Bi-directional traceability verification across Design Inputs, Design Outputs, V&V reports, and ISO 14971:2019 Risk Management
  • Consensus standard edition currency and test report completeness audit (IEC 60601, ISO 10993, IEC 62304, IEC 62366-1)
  • Critical review of Clinical Evaluation Reports (CER), Performance Evaluation Reports (PER), and SE justifications
  • Severity classification (Showstopper / Major / Minor) of gaps that trigger FDA RTA/AI holds or Notified Body non-conformities

Deliverables

Precision audit outputs that give your R&D and RA teams a clear checklist to achieve submission readiness.

  • Clause-by-Clause IMDRF STED / EU MDR GSPR / FDA eSTAR Gap Analysis Matrix
  • Prioritized Deficiency Risk Register (Showstopper / Major / Minor)
  • Harmonized Standard Edition & Test Report Sufficiency Audit Report
  • Design Control & ISO 14971 Risk Traceability Discrepancy Log
  • Step-by-Step Technical File Remediation Plan & Timeline
Technical File (STED/DHF) Gap Analysis — Service Scope & Final Deliverables
CategoryItem / MilestoneSpecification & Deliverable
ScopeScope 1Line-by-line audit against EU MDR/IVDR GSPR checklists, FDA eSTAR templates, and IMDRF STED structure
ScopeScope 2Bi-directional traceability verification across Design Inputs, Design Outputs, V&V reports, and ISO 14971:2019 Risk Management
ScopeScope 3Consensus standard edition currency and test report completeness audit (IEC 60601, ISO 10993, IEC 62304, IEC 62366-1)
ScopeScope 4Critical review of Clinical Evaluation Reports (CER), Performance Evaluation Reports (PER), and SE justifications
ScopeScope 5Severity classification (Showstopper / Major / Minor) of gaps that trigger FDA RTA/AI holds or Notified Body non-conformities
WorkflowStage 1: DHF, STED & Test Report Inventory IntakeIngest and index your current technical files, risk management files, bench test reports, and clinical documentation.
WorkflowStage 2: Clause-by-Clause GSPR, eSTAR & Standard AuditCross-examine every claim, specification, and test protocol against current harmonized standards and reviewer checklists.
WorkflowStage 3: Gap Severity Triage & Justification EngineeringSeparate gaps solvable via written engineering justification from those requiring targeted supplemental bench testing.
WorkflowStage 4: Redline Gap Matrix & Remediation Roadmap DeliveryDeliver an itemized remediation plan with document-level redline guidance, timelines, and resource estimates.
DeliverablesDeliverable 1Clause-by-Clause IMDRF STED / EU MDR GSPR / FDA eSTAR Gap Analysis Matrix
DeliverablesDeliverable 2Prioritized Deficiency Risk Register (Showstopper / Major / Minor)
DeliverablesDeliverable 3Harmonized Standard Edition & Test Report Sufficiency Audit Report
DeliverablesDeliverable 4Design Control & ISO 14971 Risk Traceability Discrepancy Log
DeliverablesDeliverable 5Step-by-Step Technical File Remediation Plan & Timeline

FAQ (Frequently Asked Questions)

Do we need to translate the entire technical file for this analysis?
No. We usually review the original source documents first. Translation requirements are confirmed as part of the target-market module and are scoped separately if needed.
What if our biocompatibility or electrical safety test reports are several years old?
We assess report age, applied standards, scope, lab suitability, and whether a rationale may be defensible. If re-testing is likely, we flag it with priority and dependency.
Does this analysis cover Cybersecurity and Usability?
Yes, when relevant. Connected devices, SaMD, AI-enabled devices, and devices with user-interface risk are reviewed for software, cybersecurity, and usability documentation gaps.
If you find gaps, can you help us fill them?
Yes. Remediation is scoped as a separate project after the gap analysis, so the follow-on work is based on a clear list of gaps, owners, evidence needs, and priorities.
How does Leanabl handle agency Additional Information (AI) requests or Notified Body deficiency letters during Technical File (STED/DHF) Gap Analysis?
Upon receiving any deficiency notice from FDA, an EU Notified Body, or an international review authority, our engineers dissect the reviewer’s finding against harmonized ISO/IEC clauses and clearance precedents. We separate items resolvable via technical justification from those requiring supplementary bench data, author the formal response dossier, and drive reviewer alignment through closure.
Can we structure one master DHF / IMDRF STED and test campaign to cover FDA, EU MDR, and APAC markets simultaneously?
Yes—that is the core advantage of our universal lifecycle engineering model. By harmonizing FDA eSTAR requirements, EU MDR Annex II/III GSPR checklists, IMDRF STED templates, and multi-country IECEE CB National Deviations before testing or authoring begins, we eliminate redundant laboratory campaigns and prevent region-by-region dossier rewrites.
We have a lean internal RA/QA team—how much bandwidth is required from our R&D engineers?
Our workflow is designed to protect your R&D velocity. Once your team provides baseline engineering inputs (specifications, BOM, architecture diagrams) during Stage 1 intake, Leanabl executes the heavy lifting: standard clause mapping, ISO 14971 risk traceability, regulatory authoring, and laboratory coordination. Your team only reviews and signs off at structured stage gates.
What happens if our hardware, firmware, or software changes during or after the engagement?
We immediately perform a multi-regime regulatory change impact assessment (covering FDA 510(k) modification guidance, EU MDR MDCG 2020-3 significant change criteria, and ISO 13485 design control) to determine whether a formal submission or internal Letter-to-File / QMS update is required. Because deliverables are modularized in our platform, only affected sections require updating.

Find the gaps before the reviewer does.

Use a bounded technical-file review to decide what can be reused, what must be justified, and what needs remediation before the full submission project begins.