arckit-uk-mdr-classification

Determine medical device classification and conformity assessment pathways under UK MDR 2002 and EU MDR 2017/745.

Updated Jul 24, 2026
One-click install
npx skills add https://github.com/tractorjuice/arckit-kimi --skill arckit-uk-mdr-classification
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arckit-uk-mdr-classification
Source: https://github.com/tractorjuice/arckit-kimi/tree/main/skills/arckit-uk-mdr-classification
Command: npx skills add https://github.com/tractorjuice/arckit-kimi --skill arckit-uk-mdr-classification

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill automates the complex, high-stakes process of determining medical device classification for software-as-a-medical-device (SaMD) and AI-as-a-medical-device (AIaMD) under UK and EU regulatory frameworks.

Core Features & Use Cases

  • Regulatory Classification: Determines classification (Class I-III) under UK MDR 2002 and EU MDR 2017/745.
  • Compliance Mapping: Identifies required conformity assessment routes, marking pathways (UKCA/CE), and post-market obligations.
  • Use Case: A digital health startup needs to verify if their new diagnostic algorithm requires Notified Body involvement for market access in the UK and Northern Ireland.

Quick Start

Invoke the arckit-uk-mdr-classification skill to generate a full regulatory assessment for the current project.

Frequently Asked Questions about arckit-uk-mdr-classification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I classify software as a medical device under UK MDR and EU MDR?

Medical device classification for software-as-a-medical-device is determined by evaluating the intended use statement against UK MDR 2002 and EU MDR 2017/745 rules to assign a risk class from I to III.

How do I know if my AI diagnostic software needs a Notified Body for UKCA or CE marking?

Determining conformity assessment pathways for AI-as-a-medical-device involves mapping the assigned risk classification to required UKCA or CE marking routes, which dictates whether Notified Body involvement is required for market access.

What is the conformity assessment process for SaMD under MHRA regulations?

The conformity assessment process for software-as-a-medical-device under MHRA regulations integrates project-specific intended use statements with authoritative guidance to identify classification, marking pathways, and post-market obligations.

Does my clinical diagnostic software require regulatory compliance under EU MDR 2017/745?

Clinical diagnostic software intended for therapeutic or diagnostic purposes requires regulatory compliance evaluation under EU MDR 2017/745 to determine its medical device classification and applicable conformity assessment route.

Can I use my intended use statement to determine medical device classification for my digital health product?

Intended use statements provide the foundational inputs for medical device classification, allowing the regulatory assessment to evaluate specific clinical purposes against UK and EU frameworks to produce a comprehensive compliance result.

What are the limitations of automated medical device regulatory classification for SaMD?

Automated medical device regulatory classification for SaMD relies entirely on the accuracy of the provided intended use statement and authoritative MHRA and EU guidance, requiring manual verification for complex clinical edge cases.