EU MDR for AI Software-as-a-Medical-Device — When AI Voice Crosses the Line in 2026
By Sagar Shankaran, Founder of CallSphere
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.
Key takeaways
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.
Hear it before you finish reading
Talk to a live CallSphere AI voice agent for healthcare in your browser — 60 seconds, no signup.
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
Explore a live demo and compare current plans to find the right fit for your business.
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
- Run a written qualification decision for every AI feature with a clinical clinician sign-off.
- Apply Rule 11; document the classification rationale.
- Establish ISO 13485 if you are a manufacturer; ride a customer's QMS only with contractual basis.
- Build IEC 62304 software-lifecycle artifacts from day one, not at audit time.
- Maintain an ISO 14971 risk file with hazards specific to AI — hallucination, drift, prompt-injection.
- Plan clinical evaluation per MDCG 2020-1 and MDCG 2020-6.
- Stand up post-market clinical follow-up with explicit data feedback into model retraining.
- Add the AI Act Annex IV technical file and Article 9 risk-management system on top of the MDR risk file.
- Designate a PRRC who can sign off.
- Register in EUDAMED before market placement.
FAQ
Is appointment scheduling SaMD? No. Operational software without medical purpose is out of scope.
Still reading? Stop comparing — try CallSphere live.
See the healthcare AI agent handle a real call — complete, industry-specific, and live in your browser. No signup.
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
- 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
- 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
- IEC 62304 — Medical device software lifecycle: https://www.iso.org/standard/38421.html
- EU AI Act Regulation 2024/1689: https://eur-lex.europa.eu/eli/reg/2024/1689/oj

Written by
Sagar Shankaran· Founder, CallSphere
LinkedInSagar Shankaran is the founder of CallSphere, where he builds production AI voice and chat agents deployed across healthcare, hospitality, real estate, and home services. He writes about agentic AI, LLM engineering, and shipping voice agents that handle real calls in production.
Try CallSphere AI Voice Agents
See how AI voice agents work for your industry. Live demo available -- no signup required.