Structured regulatory assessment
for EU MDR 2017/745 technical files
Upload your documentation, receive a block by block assessment with finding level verdicts, regulatory traceability, and cross document consistency verification in hours.
End-to-end processing sequence
Three principles govern the module: the system structures the assessment while the reviewer owns every decision; partial coverage is treated as zero coverage; and every output carries its regulatory reference. The audit follows this sequence:
13 evaluation blocks across the full regulatory scope
Core blocks run on every audit. Conditional blocks activate automatically based on the verified device profile.
Conditional blocks are activated based on the device profile declared by the user at audit initiation.
What makes this an audit, not a checklist
The mechanisms that bring the assessment closer to a real conformity review.
Adequacy, Not Existence
The system doesn't check whether a section exists. It evaluates whether the content addresses all required endpoints for this device type, contact duration, and nature of body contact.
Verified Device Profile
The TDAR block extracts a 20+ field device profile directly from the uploaded documents. Downstream blocks measure consistency against what the files actually state — not what the user declared.
Session Memory
Critical outputs from upstream blocks — the residual risk list from RAU, claimed performance from CER — are carried forward as structured context into downstream evaluations.
Plausibility Concerns
The model can flag regulatory-knowledge-based concerns even when document evidence alone doesn't support a formal Finding. The reviewer can convert any plausibility concern into a Finding.
Reviewer Authority at Every Step
Every system output remains draft until the reviewer confirms. Answers can be edited, findings added or removed, verdicts changed — all before the block is locked.
Cumulative Context
Each question is evaluated with full visibility of all preceding verdicts and assessments. The model sees and builds on its previous answers — coherent, non-contradictory progression.
Additional mechanisms include a 4-layer N/A determination model, cross-document consistency checks, and question-level re-run capability. The underlying model is constrained to retrieved document content — it cannot reference external knowledge or generate claims beyond what the evidence base contains. Every output is verified against source location, and remains draft until the reviewer confirms.
What the simulation produces
Three structured deliverables at the end of every completed audit.
Findings Report
Each finding includes a description, the regulatory reference it's measured against, and the source document location. Structured for direct use — no additional interpretation needed.
Populated Question List
Every question receives a verdict — Conforming, Finding, N/A with reasoning, Requires Human Assessment, or Technical Failure. The complete list serves as the detailed audit record.
Audit Summary Report
A structured cover document with scope definition, documents reviewed, finding counts, and technical notes. Factual fields only — no system-generated narrative.
Beyond detection: structured resolution
The same engine is used to evaluate how findings are closed. Each identified non-conformity can be carried into a structured resolution workflow — recording the corrective action, the linked evidence, and the affected sections against the original finding and its regulatory reference.
"The system structures and accelerates the pre-assessment — so that when the reviewer applies final judgment, the material has already been systematically interrogated."
Designed from a regulatory assessment perspective — not a software product team.