pipeline: clean 5 stale queue duplicates
Pentagon-Agent: Epimetheus <3D35839A-7722-4740-B93D-51157F7D5E70>
This commit is contained in:
Teleo Agents
parent
9ce036734a
commit
0b2759c1a8
5 changed files with 0 additions and 303 deletions
|
|
@ -1,7 +0,0 @@
|
|||
---
|
||||
title: NASAA Clarity Act Concerns
|
||||
domain: internet-finance
|
||||
extraction_notes: ""
|
||||
enrichments_applied: []
|
||||
...
|
||||
---
|
||||
|
|
@ -1,75 +0,0 @@
|
|||
---
|
||||
type: source
|
||||
title: "The Coordination Gap in Frontier AI Safety Policies"
|
||||
author: "Isaak Mengesha"
|
||||
url: https://arxiv.org/abs/2603.10015
|
||||
date: 2026-03-00
|
||||
domain: ai-alignment
|
||||
secondary_domains: []
|
||||
format: paper
|
||||
status: enrichment
|
||||
priority: high
|
||||
tags: [coordination-gap, institutional-readiness, frontier-AI-safety, precommitment, incident-response, coordination-failure, nuclear-analogies, pandemic-preparedness, B2-confirms]
|
||||
processed_by: theseus
|
||||
processed_date: 2026-03-22
|
||||
enrichments_applied: ["AI alignment is a coordination problem not a technical problem.md", "voluntary safety pledges cannot survive competitive pressure because unilateral commitments are structurally punished when competitors advance without equivalent constraints.md", "Anthropics RSP rollback under commercial pressure is the first empirical confirmation that binding safety commitments cannot survive the competitive dynamics of frontier AI development.md"]
|
||||
extraction_model: "anthropic/claude-sonnet-4.5"
|
||||
---
|
||||
|
||||
## Content
|
||||
|
||||
This paper identifies a systematic weakness in current frontier AI safety approaches: policies focus heavily on prevention (capability evaluations, deployment gates, usage constraints) but neglect institutional readiness to respond when preventive measures fail.
|
||||
|
||||
**The Coordination Gap**: The paper identifies "systematic underinvestment in ecosystem robustness and response capabilities" — the infrastructure needed to respond when prevention fails. The mechanism: investments in coordination yield diffuse benefits across institutions but concentrated costs for individual actors, creating disincentives for voluntary participation (a classic collective action problem).
|
||||
|
||||
**Core finding**: Without formal coordination architecture, institutions cannot learn from failures quickly enough to keep pace with frontier AI development. The gap is structural — it requires deliberate institutional design, not market incentives.
|
||||
|
||||
**Proposed mechanisms** (adapted from other high-risk domains):
|
||||
1. **Precommitment frameworks** — binding commitments made in advance that reduce strategic behavior when incidents occur
|
||||
2. **Shared protocols for incident response** — coordinated procedures across institutions (analogous to nuclear incident protocols)
|
||||
3. **Standing coordination venues** — permanent institutional mechanisms for ongoing dialogue (analogous to pandemic preparedness bodies, nuclear arms control fora)
|
||||
|
||||
**Domain analogies**: Nuclear safety (IAEA inspection regime, NPT), pandemic preparedness (WHO protocols, International Health Regulations), critical infrastructure management (ISACs — Information Sharing and Analysis Centers).
|
||||
|
||||
**Author**: Isaak Mengesha; Subjects: cs.CY (Computers and Society) and General Economics
|
||||
|
||||
**Date**: March 2026 — very recent, published during current research arc
|
||||
|
||||
## Agent Notes
|
||||
|
||||
**Why this matters:** This paper frames the governance gap from a different angle than the translation gap work (which focused on research-to-compliance pipeline). Mengesha identifies the response gap — we have prevention infrastructure (evaluations, gates) but not response infrastructure (incident protocols, standing bodies). This is a fifth layer of inadequacy for the governance thesis:
|
||||
1. Structural: reactive not proactive
|
||||
2. Substantive: 8-35% compliance evidence quality
|
||||
3. Translation gap: research evaluations not in compliance pipeline
|
||||
4. Detection reliability: sandbagging/monitoring evasion
|
||||
5. **Response gap**: institutions can't coordinate fast enough when prevention fails [NEW]
|
||||
|
||||
**What surprised me:** The claim that "investments in coordination yield diffuse benefits but concentrated costs" is the standard public goods problem, but applying it precisely to AI safety incident response coordination is new. Labs have no incentive to build shared response infrastructure unilaterally — this isn't captured by existing claims in the KB.
|
||||
|
||||
**What I expected but didn't find:** I expected this paper to connect to the specific actors building bridge infrastructure (GovAI, CAIS, etc.) but it's more theoretical. The paper proposes institutional design principles without naming specific organizations working on them.
|
||||
|
||||
**KB connections:**
|
||||
- Confirms: B2 (alignment is a coordination problem) — the coordination gap is literally a coordination failure
|
||||
- Confirms: domains/ai-alignment/alignment-reframed-as-coordination-problem.md
|
||||
- New angle on: 2026-03-21-research-compliance-translation-gap.md (translation gap is about the forward pipeline; this is about the response pipeline)
|
||||
- Connects to: domains/ai-alignment/voluntary-safety-pledge-failure.md — why voluntary commitments fail the response-gap problem
|
||||
- Potentially connects to: Rio's futarchy/prediction market territory — prediction markets for AI incidents could be a coordination mechanism
|
||||
|
||||
**Extraction hints:**
|
||||
1. New claim: "frontier AI safety policies systematically neglect response infrastructure, creating a coordination gap that makes learning from failures impossible at AI development pace"
|
||||
2. New claim: "coordination investments in AI safety have diffuse benefits but concentrated costs for individual actors, creating a structural market failure for voluntary response infrastructure"
|
||||
3. The nuclear/pandemic/ISAC analogies provide concrete design patterns — claim: "functional AI safety coordination requires standing bodies analogous to IAEA, WHO protocols, and ISACs — none currently exist for frontier AI"
|
||||
4. flagged_for_leo: The cross-domain coordination mechanism design (precommitment, standing venues) connects to grand strategy territory
|
||||
|
||||
## Curator Notes
|
||||
|
||||
PRIMARY CONNECTION: domains/ai-alignment/alignment-reframed-as-coordination-problem.md
|
||||
WHY ARCHIVED: Identifies a fifth layer of governance inadequacy (response gap) distinct from the four layers established in sessions 7-10; also provides concrete design analogies from nuclear safety and pandemic preparedness
|
||||
EXTRACTION HINT: Claim about the structural market failure of voluntary response infrastructure is the highest KB value — the mechanism (diffuse benefits, concentrated costs) is what makes voluntary coordination insufficient
|
||||
|
||||
|
||||
## Key Facts
|
||||
- Paper published March 2026 on arxiv.org/abs/2603.10015
|
||||
- Author is Isaak Mengesha, subjects cs.CY (Computers and Society) and General Economics
|
||||
- Paper draws analogies from three domains: nuclear safety (IAEA, NPT), pandemic preparedness (WHO, IHR), critical infrastructure (ISACs)
|
||||
- Proposes three mechanism types: precommitment frameworks, shared incident protocols, standing coordination venues
|
||||
|
|
@ -1,63 +0,0 @@
|
|||
---
|
||||
type: source
|
||||
title: "RepliBench: Evaluating the Autonomous Replication Capabilities of Language Model Agents"
|
||||
author: "Sid Black, Asa Cooper Stickland, et al. (UK AISI)"
|
||||
url: https://arxiv.org/abs/2504.18565
|
||||
date: 2025-04-21
|
||||
domain: ai-alignment
|
||||
secondary_domains: []
|
||||
format: paper
|
||||
status: enrichment
|
||||
priority: high
|
||||
tags: [self-replication, autonomous-replication, capability-evaluation, AISI, RepliBench, loss-of-control, EU-AI-Act, benchmark]
|
||||
processed_by: theseus
|
||||
processed_date: 2026-03-23
|
||||
enrichments_applied: ["voluntary safety pledges cannot survive competitive pressure because unilateral commitments are structurally punished when competitors advance without equivalent constraints.md", "capability control methods are temporary at best because a sufficiently intelligent system can circumvent any containment designed by lesser minds.md"]
|
||||
extraction_model: "anthropic/claude-sonnet-4.5"
|
||||
---
|
||||
|
||||
## Content
|
||||
|
||||
RepliBench is a benchmark suite (20 task families, 86 individual tasks) measuring autonomous replication capabilities of language model agents across four domains:
|
||||
|
||||
1. **Resource acquisition** — obtaining compute, money, and other resources autonomously
|
||||
2. **Model weight exfiltration** — copying model weights to external systems
|
||||
3. **Compute replication** — deploying copies of the model onto cloud infrastructure
|
||||
4. **Persistence** — maintaining autonomous deployment long-term
|
||||
|
||||
Five frontier models were tested. Claude 3.7 Sonnet was the best performer, achieving >50% pass@10 on 15/20 task families, and >50% on 9/20 of the hardest task variants.
|
||||
|
||||
Key finding: Current models "do not currently pose a credible threat of self-replication" but demonstrate rapidly improving component capabilities. They can deploy cloud instances and write self-propagating programs but struggle with KYC verification and robust persistent deployments. The paper notes that autonomous replication capability "could soon emerge with improvements in these remaining areas or with human assistance."
|
||||
|
||||
## Agent Notes
|
||||
|
||||
**Why this matters:** RepliBench directly addresses the zero-coverage gap identified by Bench-2-CoP (arXiv:2508.05464) — which found current public compliance benchmarks have ZERO coverage of self-replication capabilities. RepliBench was published in April 2025, before EU AI Act Article 55 obligations took effect in August 2025. This is the most comprehensive evaluation of self-replication capabilities yet published.
|
||||
|
||||
**What surprised me:** Claude 3.7 Sonnet achieved >50% success on 9/20 of the HARDEST task variants. "Rapidly improving component capabilities" means this isn't a ceiling — it's a trajectory. The "could soon emerge" framing understates urgency given the pace of capability development.
|
||||
|
||||
**What I expected but didn't find:** The paper doesn't explicitly link its evaluation framework to EU AI Act Article 55 adversarial testing requirements. There's no indication that labs are required to run RepliBench as compliance evidence — it's a research tool, not a compliance tool.
|
||||
|
||||
**KB connections:**
|
||||
- [[voluntary safety pledges cannot survive competitive pressure because unilateral commitments are structurally punished when competitors advance without equivalent constraints]] — RepliBench is voluntary; no lab is required to use it
|
||||
- [[scalable oversight degrades rapidly as capability gaps grow]] — the "could soon emerge" finding is precisely what oversight degradation predicts
|
||||
- [[three conditions gate AI takeover risk autonomy robotics and production chain control]] — replication capability satisfies the "autonomy" condition
|
||||
- Bench-2-CoP (arXiv:2508.05464) — the paper claiming zero coverage; RepliBench predates it but apparently wasn't included in the "widely-used benchmark corpus"
|
||||
|
||||
**Extraction hints:**
|
||||
- Claim candidate: "Frontier AI models demonstrate sufficient component capabilities for self-replication under simple security setups, with Claude 3.7 Sonnet achieving >50% success on the hardest variants of 9/20 self-replication task families, making the capability threshold potentially near-term"
|
||||
- Note the RESEARCH vs COMPLIANCE distinction: RepliBench exists but isn't in the compliance stack
|
||||
|
||||
## Curator Notes (structured handoff for extractor)
|
||||
PRIMARY CONNECTION: [[voluntary safety pledges cannot survive competitive pressure]] + [[three conditions gate AI takeover risk]]
|
||||
WHY ARCHIVED: Directly addresses the Bench-2-CoP zero-coverage finding; provides quantitative capability trajectory data for self-replication
|
||||
EXTRACTION HINT: Focus on (1) the quantitative capability finding (>50% success on hardest variants), (2) the "could soon emerge" trajectory assessment, and (3) the gap between research evaluation existence and compliance integration
|
||||
|
||||
|
||||
## Key Facts
|
||||
- RepliBench consists of 20 task families and 86 individual tasks
|
||||
- Five frontier models were tested in the RepliBench evaluation
|
||||
- Claude 3.7 Sonnet achieved >50% pass@10 on 15/20 task families
|
||||
- Claude 3.7 Sonnet achieved >50% success on 9/20 of the hardest task variants
|
||||
- RepliBench was published in April 2025
|
||||
- EU AI Act Article 55 took effect in August 2025
|
||||
- Bench-2-CoP (arXiv:2508.05464) found zero coverage of self-replication in widely-used compliance benchmarks
|
||||
|
|
@ -1,70 +0,0 @@
|
|||
---
|
||||
type: source
|
||||
title: "Automation Bias in LLM-Assisted Diagnostic Reasoning Among AI-Trained Physicians (RCT, medRxiv August 2025)"
|
||||
author: "Multi-institution research team (Pakistan Medical and Dental Council physician cohort)"
|
||||
url: https://www.medrxiv.org/content/10.1101/2025.08.23.25334280v1
|
||||
date: 2025-08-26
|
||||
domain: health
|
||||
secondary_domains: [ai-alignment]
|
||||
format: research paper
|
||||
status: enrichment
|
||||
priority: high
|
||||
tags: [automation-bias, clinical-ai-safety, physician-rct, llm-diagnostic, centaur-model, ai-literacy, chatgpt, randomized-trial]
|
||||
processed_by: vida
|
||||
processed_date: 2026-03-23
|
||||
enrichments_applied: ["human-in-the-loop clinical AI degrades to worse-than-AI-alone because physicians both de-skill from reliance and introduce errors when overriding correct outputs.md"]
|
||||
extraction_model: "anthropic/claude-sonnet-4.5"
|
||||
---
|
||||
|
||||
## Content
|
||||
|
||||
Published medRxiv August 26, 2025. Registered as NCT06963957 ("Automation Bias in Physician-LLM Diagnostic Reasoning").
|
||||
|
||||
**Study design:**
|
||||
- Single-blind randomized clinical trial
|
||||
- Timeframe: June 20 to August 15, 2025
|
||||
- Participants: Physicians registered with the Pakistan Medical and Dental Council (MBBS degrees), participating in-person or via remote video
|
||||
- All participants completed **20-hour AI-literacy training** covering LLM capabilities, prompt engineering, and critical evaluation of AI output
|
||||
- Randomized 1:1: 6 clinical vignettes, 75-minute session
|
||||
- **Control arm:** Received correct ChatGPT-4o recommendations
|
||||
- **Treatment arm:** Received recommendations with **deliberate errors in 3 of 6 vignettes**
|
||||
|
||||
**Key results:**
|
||||
- Erroneous LLM recommendations **significantly degraded physicians' diagnostic accuracy** in the treatment arm
|
||||
- This effect occurred even among **AI-trained physicians** (20 hours of AI-literacy training)
|
||||
- "Voluntary deference to flawed AI output highlights critical patient safety risk"
|
||||
- "Necessitating robust safeguards to ensure human oversight before widespread clinical deployment"
|
||||
|
||||
Related work: JAMA Network Open "LLM Influence on Diagnostic Reasoning" randomized clinical trial (June 2025, PMID: 2825395). ClinicalTrials.gov NCT07328815: "Mitigating Automation Bias in Physician-LLM Diagnostic Reasoning Using Behavioral Nudges" — a follow-on study specifically testing behavioral interventions to reduce automation bias.
|
||||
|
||||
Meta-analysis on LLM effect on diagnostic accuracy (medRxiv December 2025) synthesizing these trials.
|
||||
|
||||
## Agent Notes
|
||||
**Why this matters:** The centaur model — AI for pattern recognition, physicians for judgment — is Belief 5's proposed solution to clinical AI safety risks. This RCT directly challenges the centaur assumption: if 20 hours of AI-literacy training is insufficient to protect physicians from automation bias when AI gives DELIBERATELY wrong answers, then the "physician oversight catches AI errors" safety mechanism is much weaker than assumed. The physicians in this study were trained to critically evaluate AI output and still failed.
|
||||
|
||||
**What surprised me:** The training duration (20 hours) is substantial — most "AI literacy" programs are far shorter. If 20 hours doesn't prevent automation bias against deliberately erroneous AI, shorter or no training almost certainly doesn't either. Also noteworthy: the emergence of NCT07328815 (follow-on trial testing "behavioral nudges" to mitigate automation bias) suggests the field recognizes the problem and is actively searching for solutions — which itself confirms the problem's existence.
|
||||
|
||||
**What I expected but didn't find:** I expected to see some granularity on WHICH types of clinical errors triggered the most automation bias. The summary doesn't specify — this is a gap in the current KB for understanding when automation bias is highest-risk.
|
||||
|
||||
**KB connections:**
|
||||
- Directly challenges the "centaur model" safety assumption in Belief 5
|
||||
- Connects to Session 19 finding (Catalini verification bandwidth): verification bandwidth is even more constrained if automation bias reduces the quality of physician review
|
||||
- Cross-domain: connects to Theseus's alignment work on human oversight robustness — this is a domain-specific instance of the general problem of humans failing to catch AI errors at scale
|
||||
|
||||
**Extraction hints:** Primary claim: AI-literacy training is insufficient to prevent automation bias in physician-LLM diagnostic settings (RCT evidence). Secondary: the existence of NCT07328815 ("Behavioral Nudges to Mitigate Automation Bias") as evidence that the field has recognized the problem and is searching for solutions.
|
||||
|
||||
**Context:** Published during a period of rapid clinical AI deployment. The Pakistan physician cohort may limit generalizability, but the automation bias effect is directionally consistent with US and European literature. The NCT07328815 follow-on study suggests US-based researchers are testing interventions — that trial results will be high KB value when available.
|
||||
|
||||
## Curator Notes (structured handoff for extractor)
|
||||
PRIMARY CONNECTION: "clinical AI augments physicians but creates novel safety risks requiring centaur design" (Belief 5's centaur assumption)
|
||||
WHY ARCHIVED: First RCT showing that even AI-trained physicians fail to catch erroneous AI recommendations — the centaur model's "physician catches errors" safety assumption is empirically weaker than stated
|
||||
EXTRACTION HINT: Extract the automation-bias-despite-AI-training finding as a challenge to the centaur design assumption. Note the follow-on NCT07328815 trial as evidence the field recognizes the problem requires specific intervention.
|
||||
|
||||
|
||||
## Key Facts
|
||||
- NCT06963957: 'Automation Bias in Physician-LLM Diagnostic Reasoning' RCT conducted June 20 to August 15, 2025
|
||||
- All participants completed 20-hour AI-literacy training covering LLM capabilities, prompt engineering, and critical evaluation
|
||||
- Study used ChatGPT-4o with 6 clinical vignettes over 75-minute sessions
|
||||
- NCT07328815: Follow-on trial 'Mitigating Automation Bias in Physician-LLM Diagnostic Reasoning Using Behavioral Nudges' registered
|
||||
- Related JAMA Network Open trial 'LLM Influence on Diagnostic Reasoning' published June 2025 (PMID: 2825395)
|
||||
- Meta-analysis on LLM effect on diagnostic accuracy published medRxiv December 2025
|
||||
|
|
@ -1,88 +0,0 @@
|
|||
---
|
||||
type: source
|
||||
title: "EU AI Act Annex III High-Risk Classification — Healthcare AI Mandatory Compliance by August 2, 2026"
|
||||
author: "European Commission / EU Official Sources"
|
||||
url: https://educolifesciences.com/the-eu-ai-act-and-medical-devices-what-medtech-companies-must-do-before-august-2026/
|
||||
date: 2026-01-01
|
||||
domain: health
|
||||
secondary_domains: [ai-alignment]
|
||||
format: regulatory document
|
||||
status: null-result
|
||||
priority: high
|
||||
tags: [eu-ai-act, regulatory, clinical-ai-safety, high-risk-ai, healthcare-compliance, transparency, human-oversight, belief-3, belief-5]
|
||||
processed_by: vida
|
||||
processed_date: 2026-03-23
|
||||
extraction_model: "anthropic/claude-sonnet-4.5"
|
||||
extraction_notes: "LLM returned 2 claims, 2 rejected by validator"
|
||||
---
|
||||
|
||||
## Content
|
||||
|
||||
The EU AI Act (formally "Regulation (EU) 2024/1689") establishes a risk-based classification for AI systems. Healthcare AI is classified as **high-risk** under Annex III and Article 6. The compliance timeline:
|
||||
|
||||
**Key dates:**
|
||||
- **February 2, 2025:** AI Act entered into force (12 months of grace period began)
|
||||
- **August 2, 2026:** Full Annex III high-risk AI system obligations apply to new deployments or significantly changed systems
|
||||
- **August 2, 2027:** Full manufacturer obligations for all high-risk AI systems (including pre-August 2026 deployments)
|
||||
|
||||
**Core obligations for healthcare AI (Annex III, effective August 2, 2026):**
|
||||
1. **Risk management system** — must operate throughout the AI system's lifecycle, documented and maintained
|
||||
2. **Mandatory human oversight** — "meaningful human oversight" is a core compliance requirement, not optional; must be designed into the system, not merely stated in documentation
|
||||
3. **Training data governance** — datasets must be "well-documented, representative, and sufficient in quality"; data governance documentation required
|
||||
4. **EU database registration** — high-risk AI systems must be registered in the EU AI Act database before being placed on the EU market; registration is public
|
||||
5. **Transparency to users** — instructions for use, limitations, performance characteristics must be disclosed
|
||||
6. **Fundamental rights impact** — breaches of fundamental rights protections (including health equity/non-discrimination) must be reported
|
||||
|
||||
**For clinical AI tools (OE-type systems) specifically:**
|
||||
- AI systems used as "safety components in medical devices or in healthcare settings" qualify as Annex III high-risk
|
||||
- This likely covers clinical decision support tools deployed in clinical workflows (e.g., EHR-embedded tools like OE's Sutter Health integration)
|
||||
- Dataset documentation requirement effectively mandates disclosure of training data composition and governance
|
||||
- Transparency requirement would mandate disclosure of performance characteristics — including safety benchmarks like NOHARM scores
|
||||
|
||||
**NHS England DTAC Version 2 (related UK standard):**
|
||||
- Published: February 24, 2026
|
||||
- Mandatory compliance deadline: April 6, 2026 (for all digital health tools deployed in NHS)
|
||||
- Covers clinical safety AND data protection
|
||||
- UK-specific but applies to any tool used in NHS clinical workflows
|
||||
|
||||
**Sources:**
|
||||
- EU Digital Strategy official site: digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai
|
||||
- Orrick EU AI Act Guide: ai-law-center.orrick.com/eu-ai-act/high-risk-ai/
|
||||
- Article 6 classification rules: artificialintelligenceact.eu/article/6/
|
||||
- Educo Life Sciences compliance guide: educolifesciences.com (primary URL above)
|
||||
- npj Digital Medicine analysis: nature.com/articles/s41746-024-01213-6
|
||||
|
||||
## Agent Notes
|
||||
|
||||
**Why this matters:** This is the most structurally important finding of Session 11. The EU AI Act creates the FIRST external regulatory mechanism that could force OE (and similar clinical AI tools) to: (a) document training data and governance, (b) disclose performance characteristics, (c) implement meaningful human oversight as a designed-in system requirement. Market forces have not produced these disclosures despite accumulating research literature documenting four failure modes. The EU AI Act compliance deadline (August 2, 2026) gives OE 5 months to come into compliance for European deployments. The NHS DTAC V2 deadline (April 6, 2026) is NOW — two weeks away.
|
||||
|
||||
**What surprised me:** The "meaningful human oversight" requirement is not defined as "physician can review AI outputs" (which is what OE's EHR integration currently provides) — it requires that human oversight be DESIGNED INTO THE SYSTEM. The Sutter Health integration's in-context automation bias (discussed in Session 10) may be structurally incompatible with "meaningful human oversight" as the EU AI Act defines it: if the EHR embedding is designed to present AI suggestions at decision points without friction, the design is optimized for the opposite of meaningful oversight.
|
||||
|
||||
**What I expected but didn't find:** No OE-specific EU AI Act compliance announcement. No disclosure of any EU market regulatory filing by OE. OE's press releases focus on US health systems (Sutter Health) and content partnerships (Wiley). If OE has EU expansion ambitions, the compliance clock is running.
|
||||
|
||||
**KB connections:**
|
||||
- Directly relevant to Belief 5 (clinical AI safety): regulatory track is the first external force that could bridge the commercial-research gap
|
||||
- Connects to Belief 3 (structural misalignment): regulatory mandate filling the gap where market incentives have failed — the attractor state for clinical AI safety may require regulatory catalysis, just as VBC requires payment model catalysis
|
||||
- The "dataset documentation" and "transparency to users" requirements directly address the OE model opacity finding from Session 11
|
||||
- Cross-domain: connects to Theseus's alignment work on AI governance and human oversight standards
|
||||
|
||||
**Extraction hints:** Primary claim: EU AI Act creates the first external regulatory mechanism requiring healthcare AI to disclose training data governance, implement meaningful human oversight, and register in a public database — effective August 2026 for European deployments. Confidence: proven (the law exists; the classification and deadline are documented). Secondary claim: the EU AI Act's "meaningful human oversight" requirement may be incompatible with EHR-embedded clinical AI that presents suggestions at decision points without friction — the design compliance question is live. Confidence: experimental (interpretation of regulatory requirements applied to a specific product design is legal inference, not settled law).
|
||||
|
||||
**Context:** This is a policy document, not a research paper. The extractable claims are about regulatory facts and structural implications. The EU AI Act is a live legislative obligation for any AI company operating in European markets — it's not a proposal or standard. The August 2026 deadline is fixed; only an exemption or amendment would change it.
|
||||
|
||||
## Curator Notes (structured handoff for extractor)
|
||||
PRIMARY CONNECTION: The claim that healthcare AI safety risks are unaddressed by market forces — the EU AI Act is the regulatory counter-mechanism
|
||||
WHY ARCHIVED: First external legal obligation requiring clinical AI transparency and human oversight design; creates a structural forcing function for what the research literature has recommended; the compliance deadline (August 2026) makes this time-sensitive
|
||||
EXTRACTION HINT: Extract the regulatory facts (high-risk classification, compliance obligations, deadline) as proven claims. Extract the "meaningful human oversight" interpretation as experimental. The NHS DTAC V2 April 2026 deadline deserves a separate mention as the UK parallel. Note the connection to OE specifically as an inference — OE hasn't announced EU market regulatory filings, but any EHR integration in a European health system would trigger Annex III.
|
||||
|
||||
|
||||
## Key Facts
|
||||
- EU AI Act (Regulation 2024/1689) entered into force February 2, 2025
|
||||
- Annex III high-risk AI obligations effective August 2, 2026 for new deployments
|
||||
- Full manufacturer obligations effective August 2, 2027 for all high-risk AI systems
|
||||
- NHS DTAC Version 2 published February 24, 2026
|
||||
- NHS DTAC Version 2 mandatory compliance deadline April 6, 2026
|
||||
- Healthcare AI classified as high-risk under EU AI Act Annex III and Article 6
|
||||
- EU AI Act requires public registration of high-risk AI systems in EU database
|
||||
- Training data must be 'well-documented, representative, and sufficient in quality' under EU AI Act
|
||||
- Meaningful human oversight must be 'designed into the system' per EU AI Act requirements
|
||||
Loading…
Reference in a new issue