---
title: "EU MDR for AI Software-as-a-Medical-Device — When AI Voice Crosses the Line in 2026"
description: "Some AI voice and chat agents are software-as-a-medical-device under EU MDR (2017/745). Here is how Rule 11 classification, IEC 62304, and the AI Act interact for healthcare voice in 2026."
canonical: https://callsphere.ai/blog/vw5f-eu-mdr-ai-software-medical-device-samd-2026
category: "AI Strategy"
tags: ["EU MDR", "SaMD", "IEC 62304", "Rule 11", "Healthcare AI"]
author: "CallSphere Team"
published: 2026-03-19T00:00:00.000Z
updated: 2026-05-07T16:29:55.788Z
---

# EU MDR for AI Software-as-a-Medical-Device — When AI Voice Crosses the Line in 2026

> Some AI voice and chat agents are software-as-a-medical-device under EU MDR (2017/745). Here is how Rule 11 classification, IEC 62304, and the AI Act interact for healthcare voice in 2026.

> Most AI voice agents are not medical devices. The ones that triage symptoms, monitor adherence, or output a treatment recommendation can be — and EU MDR Rule 11 plus the AI Act now apply in tandem.

## What the rule says

Regulation (EU) 2017/745 (MDR) governs medical devices on the EU market. Software qualifies as a medical device when it is intended for diagnosis, prevention, monitoring, prediction, prognosis, treatment, or alleviation of disease or injury. Rule 11 of MDR Annex VIII is the headline classification rule for software: it is at least Class IIa, Class IIb if it can drive decisions about diagnosis or therapy of serious conditions, and Class III where errors could cause life-threatening consequences. Class IIa, IIb, and III all require a Notified Body conformity assessment.

The technical baselines are well-established: ISO 13485 for the quality system, IEC 62304 for software lifecycle, ISO 14971 for risk management, ISO 15223-1 for symbols, IEC 82304-1 for health software safety, and IEC 62366-1 for usability. The AI Act layers on top: AI-enabled SaMD is automatically a high-risk AI system under Annex III, and from August 2, 2027 the AI Act fully applies to AI safety components of MDR/IVDR products requiring third-party conformity assessment.

## What AI voice/chat must do

Step one is the qualification call: is the AI voice or chat doing something with medical purpose? Reminders, scheduling, payment IVR, and benefits navigation are not. Symptom triage, sepsis screening, suicide-risk assessment with clinical action, and titration coaching often are. Step two is classification: most clinically active SaMD lands at IIa or IIb under Rule 11.

Once in scope: ISO 13485 quality system, IEC 62304 software-lifecycle artifacts (development plan, requirements, architecture, unit/integration/system test, problem reports, configuration management), ISO 14971 risk file with intended-use scope, hazard analysis, and benefit/risk acceptability, clinical evaluation under MDCG 2020-1 and MDCG 2020-6, post-market clinical follow-up, and the matching AI Act Annex IV technical documentation. Notified Body audit, CE marking, EUDAMED registration, and a Person Responsible for Regulatory Compliance (PRRC) follow.

## CallSphere compliance posture

For non-SaMD use cases — appointment booking, intake, eligibility, billing — CallSphere serves as a HIPAA and SOC 2 aligned voice and chat platform with 37 agents, 90+ tools, 115+ DB tables, 6 verticals, 50+ businesses, and a 4.8/5 rating. The Healthcare Voice Agent's 14 tools include intake, scheduling, insurance check, refill nudges, and crisis routing — none of which by themselves cross into MDR scope when implemented as routing and operations rather than diagnosis or therapy. The encrypted PostgreSQL `healthcare_voice` database, full post-call analytics, sentiment, lead score, AI summary, and audit trail map cleanly to ISO 14971 risk evidence and IEC 62304 traceability if a customer chooses to bring SaMD use cases inside its own quality system. Behavioral-health deployments anchor at [/lp/behavioral-health](/lp/behavioral-health) and explicitly route crisis events to licensed humans rather than offering clinical diagnoses. Pricing $149 / $499 / $1,499; [14-day trial](/trial); 22% affiliate. Industry hubs at [/industries/healthcare](/industries/healthcare) and [/industries/behavioral-health](/industries/behavioral-health).

```mermaid
flowchart LR
A[AI Voice Use Case] --> B{Medical\nPurpose?}
B -- No --> C[Out of MDR]
B -- Yes --> D[Rule 11\nClassify]
D --> E[ISO 13485 QMS]
E --> F[IEC 62304 SLC]
F --> G[ISO 14971 Risk]
G --> H[Notified Body]
H --> I[CE + EUDAMED]
I --> J[AI Act\nAnnex IV]
```

## Compliance checklist

1. Run a written qualification decision for every AI feature with a clinical clinician sign-off.
2. Apply Rule 11; document the classification rationale.
3. Establish ISO 13485 if you are a manufacturer; ride a customer's QMS only with contractual basis.
4. Build IEC 62304 software-lifecycle artifacts from day one, not at audit time.
5. Maintain an ISO 14971 risk file with hazards specific to AI — hallucination, drift, prompt-injection.
6. Plan clinical evaluation per MDCG 2020-1 and MDCG 2020-6.
7. Stand up post-market clinical follow-up with explicit data feedback into model retraining.
8. Add the AI Act Annex IV technical file and Article 9 risk-management system on top of the MDR risk file.
9. Designate a PRRC who can sign off.
10. Register in EUDAMED before market placement.

## FAQ

**Is appointment scheduling SaMD?**
No. Operational software without medical purpose is out of scope.

**Does CE under the old MDD still count?**
Legacy MDD certificates expire on the published transition timeline; renew under MDR.

**Can we use a generic LLM as the inference engine?**
Yes, but it becomes part of the medical device and inherits all obligations.

**Does the AI Act replace MDR?**
No. They stack. Comply with both.

## Sources

- Regulation (EU) 2017/745 (MDR): [https://eur-lex.europa.eu/eli/reg/2017/745/oj](https://eur-lex.europa.eu/eli/reg/2017/745/oj)
- MDCG 2019-11 — Qualification and Classification of Software: [https://health.ec.europa.eu/system/files/2020-09/md_mdcg_2019_11_guidance_qualification_classification_software_en_0.pdf](https://health.ec.europa.eu/system/files/2020-09/md_mdcg_2019_11_guidance_qualification_classification_software_en_0.pdf)
- MDCG 2020-1 — Clinical Evaluation Software MDR: [https://health.ec.europa.eu/system/files/2020-09/md_mdcg_2020_1_guidance_clinic_eva_md_software_en_0.pdf](https://health.ec.europa.eu/system/files/2020-09/md_mdcg_2020_1_guidance_clinic_eva_md_software_en_0.pdf)
- IEC 62304 — Medical device software lifecycle: [https://www.iso.org/standard/38421.html](https://www.iso.org/standard/38421.html)
- EU AI Act Regulation 2024/1689: [https://eur-lex.europa.eu/eli/reg/2024/1689/oj](https://eur-lex.europa.eu/eli/reg/2024/1689/oj)

---

Source: https://callsphere.ai/blog/vw5f-eu-mdr-ai-software-medical-device-samd-2026