Review · before submission

EU MDR gap assessment for medical software technical documentation

Find out what needs fixing before your Notified Body sees it. In this gap assessment (often called a gap analysis) I review your existing technical file against EU MDR Annexes I, II and III and the relevant standards, and give you a prioritised action plan.

Price
About €3,000
Delivery
1–4 weeks, depending on scope
Frameworks
EU MDR · UK MDR 2002
Format
Remote document review and debrief call

When it is worth doing

  • Three to six months before a planned Notified Body submission
  • After inheriting documentation from a previous consultant or supplier
  • When moving an MDD technical file to EU MDR
  • After acquiring a company with CE-marked products
  • Before responding to a major non-conformity from a Notified Body
  • Before entering a new market such as the UK, Singapore or Malaysia

Why review first

Gaps in technical documentation turn into Notified Body questions and non-conformities, and each round of questions costs time and, often, additional assessment fees. Many of these gaps are predictable. An independent review before submission lets you fix them on your own schedule.

This service reviews documents; it does not include writing new ones. If the review shows larger gaps, the remediation can follow as technical writing (€35 per hour), as part of EU MDR consulting or as a QMS implementation.

What you get

Deliverables

  • Gap analysis report — section by section, each requirement rated Compliant, Partially compliant or Non-compliant
  • Severity rating for each finding — Critical, Major or Minor
  • Specific remediation guidance — what to add or change, not only what is missing
  • Prioritised action plan — what to fix first, with effort estimates
  • Requirements checklist mapped to Annexes I, II and III
  • 1-hour debrief call with me to walk through the findings
  • Optional re-review after remediation

Severity scale

CriticalLikely to lead to a major non-conformity from the Notified Body
MajorLikely to lead to a Notified Body question
MinorImprovement recommended

The rating is my professional judgement of the likely outcome; the Notified Body makes its own assessment.

Illustrative excerpt of a report →

How I check software traceability: worked example and template →

What I review

A substantive check of whether the content meets what the regulation and the standards require, not only whether a section exists.

Technical documentation (Annex II)

  • Device description and specification — intended purpose, indications, contraindications, patient population, users, variants
  • Design and manufacturing information — design stages, architecture, change control
  • GSPR checklist (Annex I) — applicability, justification and evidence
  • Software documentation (IEC 62304) — safety classification, architecture, process evidence, V&V traceability
  • Risk management file (ISO 14971:2019) — plan, analysis, evaluation, controls, residual risk, benefit-risk
  • Usability engineering (IEC 62366-1) — use specification, formative and summative evaluation
  • Cybersecurity — security risk management, vulnerability handling, patching (MDCG 2019-16)
  • Clinical evaluation — MDCG 2020-1 approach for software, literature method, sufficiency of clinical data, benefit-risk conclusion
  • Labelling and instructions for use — Annex I, Chapter III, Section 23

Post-market documentation (Annex III) and related documents

  • Post-market surveillance plan — data sources, methods, review frequency, thresholds
  • PMCF plan — or the justification for not needing one
  • PSUR — structure and update frequency: at least every two years for Class IIa, at least annually for Class IIb and III
  • Summary of safety and clinical performance (SSCP) — where required: implantable and Class III devices (Article 32)

Gaps I often find in software files

  • Clinical evaluation written to MDD-era expectations, without a documented literature search method
  • IEC 62304 claimed without evidence: no safety class rationale, architecture or traceability
  • Risk management still on the 2007 edition of ISO 14971
  • Generic PMS plan without data sources or thresholds
  • Intended purpose too broad to support the classification

What to send

  • Intended purpose and device description
  • Classification rationale and GSPR checklist
  • Software documentation: development plan, requirements, architecture, verification and validation records
  • Risk management file and usability engineering file
  • Clinical evaluation plan and report
  • Labelling and instructions for use
  • PMS plan, PMCF plan or justification, PSUR if available

Missing documents are fine — the review will list them. We agree before the start how you share files, for example a read-only folder in your own storage.

How it runs

  1. Scope and price

    A short call and a look at the document list. The price, about €3,000, is confirmed in writing before the review starts.

  2. Review

    1–4 weeks, depending on the scope and size of the documentation.

  3. Report and debrief

    The report, then a one-hour call to go through the findings and the action plan.

Price

About €3,000, confirmed in writing before the review starts. The review covers your current QMS and documentation against the applicable standards, so that the scope and budget of any further work rest on evidence. The exact price depends mainly on the size of the documentation, the device class and the number of software items. Fees are in EUR, excluding applicable taxes.

Related case · documentation review

AI-assisted dental X-ray software

Technical documentation from three suppliers reviewed and brought together into one file for UKCA and EU MDR.

Read the case →

Questions about the EU MDR gap assessment

A structured expert review of your existing technical documentation against the EU MDR requirements in Annexes I, II and III and the applicable standards. Each requirement is checked for completeness and substance, and the gaps are rated by severity with a prioritised action plan, before the Notified Body’s review.

Ideally three to six months before your planned Notified Body submission, so you can close critical gaps without moving your date. It is also useful after inheriting documentation, after an acquisition, or after a major non-conformity.

Yes. Besides EU MDR, I can review against the UK Medical Devices Regulations 2002 and against the documentation needed for Singapore and Malaysia submissions, and show which parts of your technical file serve several markets and which need market-specific additions.

Not within this service — it covers the review and the action plan. The remediation can follow as technical writing at €35 per hour, single documents from €100, or as part of EU MDR consulting or a QMS implementation.

No one can promise that. The review lowers the risk of predictable findings; the Notified Body makes its own assessment and may ask questions the review did not anticipate.

About €3,000 for a typical medical software technical file, confirmed in writing before the review starts. The price depends mainly on the size of the documentation, the device class and the number of software items. The review takes 1–4 weeks; fees are in EUR, excluding applicable taxes.

Know your gaps before the Notified Body does

About €3,000 · confirmed before the review starts · 1–4 weeks, depending on scope.

Request a gap analysis