med-device-eu

Installation
SKILL.md

EU and UK Device Software Guidance (MDCG and MHRA)

Sources: MDCG 2019-11 rev.1 (June 2025), MDCG 2020-6 (April 2020), MDCG 2020-13 (July 2020), MDCG 2020-7 (April 2020), MDCG 2020-8 (April 2020), and MHRA Medical devices: software applications (2023-07-01) with its stand-alone software guidance | Licence: per-document, see LICENSE | Chapters: 8

When to use

Prerequisites: none: plain Markdown; no MCP server, API key, or licence tier needed at runtime.

Use this pack for questions about software in and around medical devices on the EU and UK side: whether an app or stand-alone package qualifies as a device or an IVD and which risk class applies, what clinical evidence a legacy device needs under the MDR, how a notified body documents its assessment of a clinical evaluation, and what a post-market clinical follow-up plan commits to and how the evaluation report closes it. Both readings are taught: the MDCG guidance route for the EU and the MHRA guidance route for Great Britain.

How to Use This Skill

  • Without arguments: read the Core Frameworks below, covering the two-sided qualification question, the clinical-evidence standard for legacy devices and its assessment, and the plan-and-report loop for post-market clinical follow-up.
  • With a topic: use the Topic Index to find the chapter, then ask directly (e.g. "is this symptom checker a device in the UK", "what class is this dosing software", "what does the PMCF plan have to promise").
  • With a chapter: ch01 is the landing chapter for "which regime applies"; ch02-ch03 qualification and classification; ch04-ch05 clinical evidence and its assessment; ch06-ch07 PMCF plan and report; ch08 UK obligations after qualification.

Core Frameworks & Mental Models

SaMD qualification: one question, two readings (ch02 MDCG; ch03 and ch08 MHRA)

Qualification asks whether software is a device at all, and this pack teaches both readings. The EU route (ch02) runs the MDCG five-step decision: is it software, does it touch an Annex XVI product or drive or influence a hardware device, does it act on data beyond storage, archival, communication, simple search, or lossless compression, is that action for an individual patient's benefit, and does it carry a medical purpose of its own. Classification then follows Rule 11 of Annex VIII: class IIa for information used in diagnostic or therapeutic decisions, rising to IIb or III as the harm from wrong information rises; IIa to IIb for physiological monitoring; class I for everything else. The UK route (ch03) reads medical purpose from labelling, app-store text, and other claims, keeps a verifiability discretion for calculators the intended user can easily check, and draws the decision-support line by whether software reproduces a paper path or produces a diagnosis, prognosis, or individual risk figure. Once software qualifies on the GB market, the obligations follow (ch08): UKCA marking, a classification route, registration with the MHRA, essential requirements, and post-market duties. The mental model: both readings share an ancestor, so the medical-purpose test is similar; the divergences are in the details, and they bite hardest on calculators and decision support.

Installs
1
GitHub Stars
56
First Seen
Nov 5, 2026