EU · Regulation (EU) 2017/745

EU MDR consulting for medical software

I lead the regulatory workstream inside your team — from qualification and classification to a technical file your Notified Body can assess, and support through its questions and audits.

Price
€10,000–25,000 fixed fee
My part takes
Typically 6–9 months to Notified Body submission (Class IIa)
Device classes
Class I, IIa, IIb software
Work format
Remote or on-site, inside your team

The Notified Body’s assessment is a separate phase with its own timeline and fees. I am not a Notified Body, and nobody can guarantee a certificate or a date.

Who this is for

  • Founders and CTOs of SaMD and AI medical software companies preparing for CE marking
  • Teams with a product in development and no in-house regulatory lead
  • QA/RA leads who need an experienced second pair of hands before submission
  • Manufacturers moving a legacy MDD device to EU MDR

EU MDR for software in short

Software is a medical device if the manufacturer intends it for a medical purpose listed in Article 2(1) of the MDR. MDCG 2019-11 (Rev.1, June 2025) explains how to decide this for software. Only then does Rule 11 in Annex VIII set the class: software that provides information used for diagnostic or therapeutic decisions is at least Class IIa.

For Class IIa and higher, a Notified Body assesses your quality management system and technical documentation before you can CE-mark the device. Class I software without a measuring function is self-declared by the manufacturer.

Start with the guide Is your software a medical device under EU MDR?

What’s included

Your project is run by me personally, from kick-off to the Notified Body’s decision. No hand-over to junior consultants.

Technical and regulatory documents

  • Qualification and Rule 11 classification — written justification based on intended purpose, indications and contraindications
  • Technical documentation (Annexes II and III) — structure and content, including the GSPR checklist
  • Clinical evaluation — plan and report following MDCG 2020-1 for medical device software, with your clinical experts
  • Risk management file (ISO 14971) — plan, analysis, evaluation, controls, residual risk and benefit-risk
  • Software lifecycle documentation (IEC 62304) — development plan, architecture, verification and validation, maintenance
  • Usability engineering file (IEC 62366-1) — use specification, formative and summative evaluation
  • Cybersecurity documentation — security risk management, vulnerability handling and patch process (MDCG 2019-16)
  • EU declaration of conformity — drafted and checked before you sign it

Process and audit support

  • Regulatory strategy session — classification, conformity assessment route and Notified Body requirements
  • Notified Body selection — shortlisting designated bodies whose scope covers your device, and preparing your requests for quotes
  • Pre-submission review — a simulated Notified Body review to find gaps before you submit
  • Audit support — remote or on-site, with answers to the Notified Body’s questions during review
  • Non-conformity responses — drafting and tracking responses to audit findings
  • Post-market set-up — PMS plan, PSUR structure, PMCF plan and vigilance procedure
  • Obligations after certification — EUDAMED registration and the manufacturer’s ongoing duties under Article 10
  • EU AI Act overlap — what an AI-based device will need in addition to MDR, and when
Smaller first step

Regulatory strategy & classification

If you are still deciding whether your software is a medical device, which class it falls into and what the route will cost, you can start with this package on its own. It is also the first stage of every EU MDR project.

You send your input, for example the intended purpose, a description of the software and its components, and your target markets. I review the system, its components, the registration pathway and the applicable regulations, then run a focused workshop with concrete recommendations: whether the software qualifies as a medical device, its likely class under Rule 11, the conformity assessment route, the standards and guidance that apply, and the main evidence gaps.

Price: €1,000 for the analysis of your input and a 1.5-hour workshop, or €200 for the 1.5-hour workshop only. Fees are in EUR, excluding applicable taxes.

Request a strategy call

Stages and timing

A typical Class IIa project. The first four stages are the preparation I lead; the fifth is the Notified Body’s assessment.

  1. Weeks 1–4

    Gap analysis and regulatory strategy

    Review of your documentation, software architecture and QMS. Classification under Rule 11, conformity assessment route and Notified Body requirements. Deliverable: written regulatory strategy.

  2. Months 2–3

    QMS alignment and documentation structure

    Your ISO 13485 QMS aligned with MDR requirements. Technical documentation structure per Annex II. Risk management file and software lifecycle documentation started.

  3. Months 3–6

    Technical documentation

    All sections completed with your team: device description, design information, GSPR checklist, clinical evaluation, risk management, software documentation, labelling and post-market documents.

  4. Months 6–9

    Pre-submission review and application

    A simulated Notified Body review, fixes, and the application package for your Notified Body.

  5. Notified Body timeline

    Assessment by the Notified Body

    Document review and QMS audit, questions and non-conformities, and the certificate decision. I support your team throughout; the duration depends on the Notified Body and on the questions raised.

How long Notified Bodies take. In the European Commission’s survey of Notified Bodies (published July 2026, data to 28 February 2026), 65% of applications reached a signed written agreement within two months. From written agreement to certificate, 51% of Notified Bodies reported 13–18 months for QMS and product certification, 31% reported 19–24 months and 10% more than 24 months. That is why I recommend contacting Notified Bodies early. How to plan the full timeline.

Who does what

The exact split is written into the proposal. This is the usual one.

Responsibilities in an EU MDR project
ActivityYour teamMeNotified Body
Intended purpose and classificationDecides, signs offDrafts rationaleReviews
Software design, code and testingDoes the workDefines evidence needed, reviewsSamples and assesses
Technical documentationProvides content, approvesStructures, writes, reviewsAssesses
Clinical evaluationClinical input and data, approvalPlans and draftsAssesses
Testing by third parties (e.g. penetration tests)Contracts and paysSpecifies, reviews reportsAssesses evidence
Audit and questionsAnswers as manufacturerPrepares team, drafts responsesAudits, asks, decides
Declaration of conformity, CE marking, PRRCResponsibleDrafts and checks—

What I need from your team

  • A product owner who can decide on intended purpose and scope
  • Access to your backlog, repositories or design documents, and test results
  • Developer and tester time to produce evidence, usually in your normal sprints
  • Clinical expertise for the clinical evaluation, in-house or external
  • A named person who approves documents and signs as manufacturer

Not included

  • Notified Body fees, which you pay to the Notified Body directly
  • Testing by laboratories, clinical investigations and translations
  • Acting as your PRRC (Article 15) or EU authorised representative (Article 11)
  • Writing your software or running your tests

Already have documentation and only need a review? See the technical documentation gap analysis.

Price

A fixed fee between €10,000 and €25,000, set in a written proposal after the free call. It depends on:

  • the device class and the number of software functions in scope;
  • how much documentation already exists and in what state;
  • how mature your quality management system is;
  • the clinical evidence strategy, for example whether new clinical data are needed.

Notified Body fees are separate. Under Article 50 of the MDR, Notified Bodies must make their standard fees publicly available, so ask two or three for quotes early. All budget components.

Related case · EU MDR Class IIa

Haemodialysis patient management SaMD

ISO 13485 QMS built from scratch and the development partner’s documentation aligned with EU MDR.

Read the case →
AI medical software

EU MDR and the EU AI Act

An AI-based medical device that needs a Notified Body under MDR is a high-risk AI system under the AI Act (Regulation (EU) 2024/1689). After Regulation (EU) 2026/1744, these obligations apply from 2 August 2028. The Notified Body will assess them together with MDR, so plan the extra evidence now within your normal technical documentation work.

One set of evidence

Risk management, data governance, human oversight and performance evidence overlap between MDR and the AI Act. I map what serves both and what is new.

Change control for models

Retraining and model updates need a documented way to decide whether a change is significant and what evidence it requires before release.

AI technical documentation

Description of training and test data, validation results, performance metrics and the information users need to interpret outputs.

Guide: EU AI Act and EU MDR for AI medical devices →

Guide: EN 18286, the AI Act QMS standard, and ISO 13485 →

Questions about EU MDR consulting

It does if it is a medical device: software the manufacturer intends for a medical purpose listed in Article 2(1) of the MDR, such as diagnosis, monitoring, prediction or treatment of disease. MDCG 2019-11 Rev.1 explains how to decide. If it qualifies, Rule 11 sets its class, and you need CE marking before placing it on the EU market.

Plan two phases. My preparation workstream for a Class IIa SaMD typically takes 6–9 months to a submission-ready technical file, depending on your starting point. Then the Notified Body’s assessment: in the European Commission’s 2026 survey, 51% of Notified Bodies reported 13–18 months from written agreement to certificate for QMS and product certification, and 41% reported longer. Class I software without a measuring function does not need a Notified Body.

For Class IIa, IIb and III, yes. Class I devices are self-declared by the manufacturer, unless they are sterile, have a measuring function or are reusable surgical instruments. Under Rule 11, most software that informs clinical decisions is Class IIa or higher. Classification is the first thing I check in every project.

My fee is €10,000–25,000, fixed in a proposal after the free call, depending on device class, documentation complexity and QMS maturity. Notified Body fees are separate: each Notified Body must publish its standard fees, and quotes depend on the device and the assessment route. No hourly billing on fixed-scope work.

Yes. I have worked on AI-based diagnostic software, including image analysis. Typical topics: algorithm validation, clinical evaluation with AI performance metrics, change control for model updates, explainability and user information, and preparing for the AI Act obligations that apply to MDR devices from 2 August 2028.

Yes. Regulation (EU) 2023/607 extended the validity of MDD certificates until 31 December 2027 or 31 December 2028, depending on the device, but only where the manufacturer met its conditions: an MDR quality system and an application to a Notified Body by 26 May 2024, and a written agreement by 26 September 2024. The transition means updating the technical documentation to Annexes II and III, updating the clinical evaluation, and extending the QMS to cover MDR post-market obligations. MDD to MDR transition.

No. The certificate decision belongs to the Notified Body, and the manufacturer is responsible for the device. What I commit to is the agreed scope: the deliverables and support written in the proposal.

Discuss your EU MDR route

A free 30-minute call: we look at your software, the likely class and route, and what needs to happen before submission.

Request a free call