AI insurance for healthcare providers. What Annex III high-risk obligations mean for coverage, what conventional policies miss, and how to build a complete risk programme.

The Annex III healthcare categories and what they require

EU AI Act Annex III, point 5, lists three healthcare AI categories that are classified as high-risk. The first is AI intended to be used as a safety component of medical devices, or AI that is itself a medical device, within the meaning of Regulation (EU) 2017/745 (MDR) or Regulation (EU) 2017/746 (IVDR). The second is AI intended for the purpose of triage or prioritisation of emergency medical situations, specifically AI that assists in determining whether a patient presents an emergency. The third is AI intended to assist clinical professionals in making diagnostic or treatment decisions, including AI used for medical imaging interpretation, pathology analysis, or clinical documentation review.

Healthcare providers deploying any of these systems are deployers of high-risk AI systems under the EU AI Act, with a specific set of Article 26 obligations. Article 26(1) requires deployers to use the system in accordance with the provider's instructions for use, which means the provider must have supplied instructions meeting the Article 13 transparency requirements, and the deployer must be able to demonstrate adherence. Article 26(2) requires deployers to assign human oversight to persons who have the competence, authority, and resources to exercise it effectively, specifically the AI literacy obligations under Article 4 as they apply to oversight personnel. Article 26(3) requires deployers to implement the human oversight measures specified in the provider's instructions. Article 26(5) requires deployers to monitor the operation of the system and report serious incidents and malfunctions to the national market surveillance authority and to the provider.

The relationship between these obligations and the insurance coverage that healthcare providers carry is the central issue this analysis addresses. Compliance with Article 26 does not create insurance coverage; it creates the governance documentation that makes a healthcare AI incident manageable and an insurance underwriting file credible. Healthcare risk managers who treat the two as separate workstreams are creating inefficiencies that a structured programme can eliminate.

The MDR and IVDR interface

Clinical AI systems classified as high-risk under Annex III point 5 often overlap with medical device classification under MDR or IVDR. Where a clinical AI system is classified as both an EU AI Act high-risk AI system and a medical device, the AI provider must complete conformity assessment procedures under both frameworks. For the healthcare deployer, this means the vendor selection process should verify both MDR CE marking (where applicable) and EU AI Act technical documentation.

A CE-marked medical device AI that has not separately satisfied EU AI Act provider obligations for high-risk AI is in a transitional compliance position. Under Article 111 of Regulation (EU) 2024/1689, AI systems already CE-marked under MDR or IVDR at the date of application of the AI Act's high-risk provisions benefit from a transitional period until 2030, provided they have not undergone significant changes in design or intended purpose. Healthcare deployers should verify with vendors whether the AI system they are deploying benefits from this transitional status or has already satisfied full EU AI Act conformity requirements.

From an insurance perspective, this transitional status is not a coverage protection. An AI system in the MDR transitional period that causes patient harm is still a defective product under Directive 2024/2853. The transitional period delays compliance enforcement by regulators; it does not delay liability to patients.

The product liability exposure and why it is different from malpractice

Medical malpractice liability, in all European legal systems, requires a clinician to have fallen below the standard of care. If a clinician using an AI diagnostic tool acts reasonably on the AI's output, and the AI's output was incorrect, the analysis of whether malpractice occurred turns on whether the clinician's reliance on that output was itself reasonable, whether the clinician verified the output appropriately, and whether the outcome was foreseeable. In many cases, a clinician who documented their AI-assisted decision process and applied appropriate clinical judgment will not be personally liable even if the AI system was defective.

Directive 2024/2853 introduces a parallel liability track that does not require the clinician to have been negligent. Under the Directive's strict liability framework, a patient who suffers harm from a defective AI clinical tool can sue the AI system's manufacturer (the vendor), and potentially the importer, distributor, or substantial modifier of the AI system, without proving negligence. Article 5(1) of the Directive creates liability for the manufacturer of a defective product. Article 5(2) extends liability to the importer and distributor in defined circumstances. Article 8(1) allows simultaneous claims against multiple responsible parties and provides that liability is joint and several.

The substantial modification provision in Article 7 of the Directive is the element with the most direct operational implication for healthcare providers. A hospital that procures a clinical AI system and subsequently modifies the training dataset, changes the intended patient population, adjusts the output confidence thresholds, or integrates the system into a clinical workflow in ways that change its intended purpose may be treated as a substantial modifier. If the system subsequently causes harm and the modification is causally connected to the defect, the hospital becomes jointly liable with the original vendor under the Directive. Healthcare technology and risk teams that customise or configure AI systems without tracking those modifications against the vendor's original intended use specification are creating an unmonitored liability exposure under this provision.

For a technical analysis of the Directive's full scope, including the causal nexus presumption in Article 9(4) and the disclosure obligation in Article 9(1) that allows claimants to require AI providers to disclose technical documentation, see the Product Liability Directive analysis at agentliability.eu.

What conventional medical malpractice insurance covers and where it ends

European medical malpractice insurance covers the civil liability of healthcare professionals for harm caused to patients through professional negligence. It is a liability product: it responds when a third party (the patient or their estate) makes a claim against the insured (the healthcare provider or individual clinician) alleging that negligent professional conduct caused harm.

This coverage structure leaves three gaps relevant to healthcare AI.

The first gap is the AI system malfunction gap. Malpractice coverage responds to the clinician's negligence, not the AI platform's defective output. If an AI clinical decision support system produces an incorrect diagnostic suggestion, and the clinician acts on it reasonably, the clinician may not have been negligent. But the patient has still been harmed. The AI vendor may be liable in product liability under Directive 2024/2853. The hospital may be jointly liable if it is a substantial modifier. Malpractice coverage does not respond to these product liability exposures.

The second gap is the AI exclusion gap. Many European professional indemnity and malpractice policies at renewal in 2025 and 2026 have begun including AI-related exclusions or clarifications. These provisions vary in breadth. Some exclude only autonomous AI decisions made without clinician review. Others exclude any loss where an AI system was in the clinical workflow regardless of the extent of human oversight applied. Healthcare risk managers renewing coverage in the current cycle should request a full policy review against their AI deployment inventory before assuming coverage continuity.

The third gap is the regulatory sanction gap. EU AI Act Article 99 imposes administrative fines for deployer-level violations of up to EUR 15 million or 3 per cent of total worldwide annual turnover. For a hospital group, 3 per cent of worldwide turnover is a material amount. Under most European insurance regulatory frameworks, fines imposed by public authorities for regulatory violations are not insurable on public policy grounds. Malpractice insurance does not respond to EU AI Act regulatory sanctions. Neither does technology E&O or parametric AI performance insurance. Healthcare organisations that treat regulatory penalty exposure as a covered risk are misreading their coverage.

What the AI insurance market currently offers for healthcare

As of mid-2026, no product has been designed specifically for EU healthcare deployer AI liability. Coverage must be assembled from three components, each addressing a distinct slice of the total exposure.

The first component is parametric AI performance coverage, available primarily through Munich Re aiSure distributed via Mosaic Insurance. This covers performance shortfall against defined metrics, algorithmic bias, privacy failures, and IP infringement. For clinical AI, parametric coverage can be structured around accuracy thresholds, sensitivity and specificity benchmarks, and bias metrics across defined patient subpopulations. The limitation is basis risk: parametric coverage pays on the trigger metric, not on the actual harm. A clinical AI system that causes patient harm through failure modes not captured by the parametric trigger does not generate a covered loss under this structure.

The second component is technology errors and omissions coverage with an AI endorsement, available through specialist underwriters in the Lloyd's market, Armilla (which operates as a Lloyd's coverholder with coverage up to USD 25 million), and Counterpart. Technology E&O covers third-party claims alleging that a technology product or service caused financial loss through negligence or error. For healthcare, this can extend to clinical AI vendor liability for defective outputs, though the policy language must explicitly address healthcare use cases and Directive 2024/2853 joint liability scenarios. Healthcare providers acting as substantial modifiers under the Directive need coverage that acknowledges that role; standard technology E&O written for software vendors may not include it.

The third component is updated product liability coverage addressing Directive 2024/2853. Many existing product liability policies require amendment or endorsement to reflect the Directive's strict liability framework and the specific provisions relevant to AI software as a defective product. Healthcare legal teams reviewing coverage before the Directive's December 2026 transposition deadline should work with insurers to confirm whether existing product liability coverage will respond to claims under the new framework or whether a specific endorsement or replacement policy is needed.

Building a healthcare AI risk programme from the compliance baseline

The most efficient path to adequate healthcare AI coverage is to treat compliance documentation and insurance underwriting documentation as a single evidence-building process rather than two separate workstreams.

The Article 26 compliance requirements for healthcare deployers of high-risk AI generate a documentation baseline that includes: an inventory of Annex III AI systems in deployment, a documented review of each provider's technical documentation and instructions for use, evidence of human oversight assignment including named oversight personnel and their AI competence level, the oversight procedures in place for each system, an AI incident response protocol aligned with Article 26(5) serious incident reporting, and a governance record showing board-level accountability for AI risk in clinical settings.

This documentation baseline is also the primary underwriting input for AI insurance in healthcare. A healthcare organisation that has completed its Article 26 compliance documentation can submit that package directly to parametric underwriters and Lloyd's market carriers, compressing the underwriting process from months to weeks. A third-party AI governance assessment, such as the Agent Certified framework, which covers governance, oversight design, context integrity, and incident response in its seven dimensions, can further validate the documentation and provide the independent assessment evidence that underwriters give material weight to when setting coverage terms and premium.

The documentation sequence for a healthcare organisation building this programme from the start is: (1) inventory all AI systems against the Annex III classification criteria; (2) for each Annex III system, obtain and review the provider's technical documentation package and Article 13 instructions for use, and request confirmation of MDR CE marking status and EU AI Act conformity status; (3) map the hospital's current human oversight arrangements against the Article 26(2) and (3) requirements, identifying gaps; (4) review all AI system configuration and customisation decisions against the Article 7 substantial modification definition in Directive 2024/2853 and implement documentation controls; (5) audit current insurance policies against the three coverage gaps described above and brief the broker on the specific coverage components needed; (6) prepare the underwriting file from the compliance documentation baseline and submit for coverage.

What to watch as the frameworks mature

Three developments in the second half of 2026 will affect healthcare AI coverage materially. First, the Directive 2024/2853 transposition in member states will produce national implementing legislation that specifies how the joint liability framework, the burden of proof provisions, and the substantial modification definition apply in each jurisdiction. Healthcare risk managers should monitor transposition in their primary operating jurisdiction. Second, the European Medicines Agency and national competent authorities have indicated they will publish guidance on the interface between MDR, IVDR, and EU AI Act requirements for clinical AI software during 2026. This guidance will clarify the conformity sequence that AI clinical decision support vendors must follow, which in turn affects the technical documentation that healthcare deployers can expect to receive from vendors and submit to underwriters. Third, the first enforcement actions under Article 99 of the EU AI Act against deployers, which are expected in the second half of 2026 from the most proactive national supervisory authorities, will set a precedent for the penalty calculations that healthcare providers should include in their uninsured exposure analysis.

For organisations tracking these developments, the Agentic Liability Monitor covers enforcement actions, new coverage products, and regulatory guidance as it emerges. For an assessment of how your current AI governance position maps to coverage eligibility, join the Agent Insured waitlist for a structured intake process.