DEV Community

Priya Nair
Priya Nair

Posted on

Germany’s 2026 medtech squeeze: EUDAMED plus HTA — what I’m telling my product teams

If you work in EU regulatory affairs for Class IIa/IIb devices, you have probably felt the temperature rise this year. For me — four years into managing MDR Technical Files, notified‑body interactions, and PMCF plans — 2026 has the feel of two new fires to keep alight at once: the continuing reality of EUDAMED (still imperfect, still mandatory for many workflows) and a national-level HTA push in Germany that materially changes what “sufficient clinical evidence” looks like for market access and reimbursement.

I’ll be blunt: MDR 2017/745 already set a high bar (Annex II and Annex XIV are never far from my keyboard). Germany’s HTA requirements in 2026 are not a replacement of MDR obligations — they are an additional, parallel expectation focused on comparative benefit and real‑world outcomes. In practice this means more targeted data collection, new dossier sections, and tighter timelines for evidence generation.

What I’m actually seeing in audits and NB meetings

  • Notified bodies are increasingly asking for explicit connections between PMCF, clinical evaluation, and health‑outcome metrics. They quote Annex XIV for PMCF scope; HTA bodies want resource‑use and comparator data.
  • EUDAMED remains central for device and actor registration. The UDI/Device module quirks still trip teams — when registry entries, certificates, and actor roles disagree, audits get longer.
  • Manufacturers selling into Germany can expect payers and HTA assessors to demand:
    • clearly defined comparators in clinical evidence,
    • patient‑relevant endpoints (e.g. PROMs) rather than surrogate markers alone,
    • real‑world evidence tied to utilisation and cost outcomes.
  • Language and submission packaging matter. Germany’s HTA reviewers will not accept a Technical File alone; they want a HTA‑style dossier aligned to national templates.

To be fair, some of this was predictable: MDR emphasises clinical follow‑up (Annex XIV) and post‑market surveillance (PMS) obligations; Germany’s HTA programme is just pressing the “value” angle harder. Granted, the outcome is better patient reassurance — but for small medtech teams it’s operationally heavier.

Immediate actions I’ve put in motion (practical, tested)

If your notified‑body audit or German market access is within 6–12 months, these are the things I tell product owners to prioritise:

  • Map your evidence stack
    • Link clinical data, PMCF plans, and risk management records in one view (Annex II traceability).
    • Identify where you have PROMs, where you have only surrogate endpoints, and where HTA comparators are missing.
  • Adapt PMCF to HTA needs
    • Update PMCF protocols to include patient‑relevant outcomes and usable resource‑use data (hospital stay, device‑related procedures).
    • Timebox prospective follow‑up to generate comparator‑aligned datasets where feasible.
  • Prepare a HTA appendix for your CER
    • Add a concise section that speaks directly to comparative effectiveness, limitations, and health‑economic implications.
  • Fortify your EUDAMED entries
    • Reconcile device identifiers, certificates, and actor registrations before HTA dossiers reference them.
  • Assign an HTA point person
    • One owner to shepherd translations, national templates, and payer engagement reduces “do‑it‑all” stress for RA.

Why your eQMS matters now (and what features I actually use)

I’m not doing this by spreadsheet any more. An eQMS that offers connected workflow and traceability is not a luxury; it is a compliance tool.

What I rely on:

  • Traceability between requirements, risk controls, clinical evidence, and PMCF tasks (so an auditor can follow one claim from risk analysis to data).
  • PMCF and PSUR workflows that surface gaps and link to CAPAs — automated CAPAs (or at least AI‑assisted suggestions) help prioritise actions when evidence is insufficient.
  • Change impact mapping visible when a PMCF protocol changes and the CER, IFU, and labeling need updates.
  • Reviewability: documented review steps for HTA‑specific dossier sections.

To be clear: this is controlled assistance, not magic. The system helps me find the documents and highlights where clinical evidence doesn’t meet HTA expectations; I still write the scientific narrative.

What this means for small medtech teams

  • Timeline risk increases. Expect extra rounds of questions from HTA assessors that require new analyses or additional collection in PMCF. Factor that into your product launch timing.
  • Budget pressure on post‑market surveillance. PMCF designed for MDR compliance may not automatically satisfy HTA endpoints — you may need supplementary studies or registries.
  • Strategic choices matter. For some low‑risk devices, you may decide reimbursement pursuit vs private‑market niche sales is a business decision, not just a regulatory one.

Quick checklist for the next 3 months

  • Assign HTA owner and update org chart to show responsibilities.
  • Review PMCF protocols against patient‑relevant outcomes and comparators.
  • Reconcile EUDAMED device/actor/UDI entries and certificate links.
  • Run a traceability audit: risk management ↔ clinical evidence ↔ labeling.

I’m still refining how much HTA-specific material belongs in the CER versus a separate HTA dossier. In practice, we keep the CER tight to MDR requirements (Annex XIV) and prepare HTA appendices that the assessor can accept as supplementary material — but that’s a team decision based on notified‑body preferences and market strategy.

What are other RA leads doing to balance MDR CER duties with Germany’s HTA expectations? Are you keeping HTA content inside the Technical File or managing it as a parallel dossier?

Top comments (0)