Structured production of EU MDR technical documentation
End-to-end generation of Annex II/III technical documentation — evidence-grounded, section-by-section, with every claim classified and traceable to its regulatory source.
From empty workspace to finalized documentation
Each workspace is an isolated, per-product environment — evidence, drafts, and approvals never cross between products.
54 templates across 8 documentation categories
Covering the full scope of MDR Annex II and Annex III requirements.
8 categories covering the full scope of MDR Annex II and Annex III.
What makes this a documentation engine, not a text generator
The mechanisms that separate structured regulatory production from general AI output.
Claim Classification & Traceability
Every generated sentence is classified as Normative, Derived, or Descriptive. Normative and derived claims are mapped to a persistent claim-evidence registry — a claim without a traceable evidence link is a system error. Normative claims without a source reference are blocked from generation.
187 Cross-Section Dependency Rules
54 templates are connected by 187 rules: 44 must-match (identical data required), 71 cross-reference (one section must cite another), and 72 logical alignment rules. A sterilization method stated differently across sections is caught automatically.
526-Entry Regulatory Knowledge Graph
The system draws from a structured reference database spanning EU MDR 2017/745 articles, ISO standards (13485, 14971, 10993 family, 62304, 60601), IEC, ASTM, and MDCG guidance documents. This graph drives cross-referencing during section generation, standard version validation, and evidence-to-requirement mapping.
Human-in-the-Loop by Design
Draft → Edit → Approve → Finalize. Human approval is a hard gate — the system cannot approve any section itself. Every generation event, edit, and approval is logged. This is an architectural decision, not a temporary constraint.
Workspace-Scoped Assistant
The assistant operates strictly within the active workspace — it only draws from that product's uploaded documents, never from other workspaces or general knowledge. Answers include source document, section, and page references, with confidence scoring (High/Medium/Low) per response.
Finalization Validation Gate
Before finalization, the system validates the entire document set. Sterilization contradictions, SAL mismatches, and unresolved critical placeholders block completion. Non-critical gaps produce advisory warnings without blocking.
Additional mechanisms include stale product data detection via hash comparison, cross-reference truncation alerts, zero-shot generation warnings for sections without uploaded evidence, and atomic state writes with full audit trail persistence.
"Structured documentation, not generated text."
Evidence-grounded. Deterministic where it matters. Human-approved at every gate.
Get Notified
TD Workspace is currently in limited access. Leave your details to be notified when it becomes available.
Get Notified