+ HEALTH — Background Anxiety is one of the most prevalent mental health concerns among college students worldwide, yet…− CLIMATE — Data-driven modeling in wastewater treatment is increasingly constrained by the reality of small, high-dimens…− ENTERTAINMENT — The Oscar-winning director Christopher Nolan believes the kind of movies he makes – big-budget action films s…− POLICY — *** After Richard Tice posted a picture of an apparent Reform campaign event on Sunday, experts and social me…+ CLIMATE — At first, the stoat looks like a faint smudge in the distance. But, as it jumps closer, its sleek body is ide…− SCIENCE — The race to get artificial intelligence to market has raised the risk of a Hindenburg-style disaster that sha…− SCIENCE — Elon Musk’s aerospace company SpaceX has acquired his artificial intelligence business xAI, in a $1.25tn (£91…− BUSINESS — How will we be fed? That’s the biggest question not seriously being addressed amid all this talk about whethe…
TruaceTracing the truth around AIMonday, July 13, 2026
Subscribe
TRV-2026-0047Version 2 · Retracted

Written 2026-07-13 00:40:03 UTC · current record

Reason for this version

Model backfill: source did not support a publishable AI-impact claim

Canonical text (the exact bytes fingerprinted)

TRUVACE RECORD VERSION
record: TRV-2026-0047
version: 2
kind: retracted
reason: Model backfill: source did not support a publishable AI-impact claim
timestamp: 2026-07-13T00:40:03.935934Z
status: archived
lens: p_space
sector: health
headline: Evolut r transcatheter aortic valve: FDA injury report involving AI
dek: The FDA received a injury report involving Evolut r transcatheter aortic valve, made by Medtronic mexico s. de r.l. de cv. It was reported that 7 months following the implant of a transcatheter aortic valve, leaflet thickening was identified via computed tomography angiogram (cta) that was further analyzed via a non-medtronic artificial intelligence (ai)-powered simulation. the patient is being evaluated for a transcatheter valve-in-valve procedure.
gain_title: (none)
problem_title: An FDA adverse-event report linked Evolut r transcatheter aortic valve to an AI-related injury; the report requires investigation and does not by itself establish causality.
trace_subject: (none)
gain_reading: (none)
problem_reading: An FDA adverse-event report linked Evolut r transcatheter aortic valve to an AI-related injury; the report requires investigation and does not by itself establish causality.
quick_read: The FDA received a injury report involving Evolut r transcatheter aortic valve, made by Medtronic mexico s. de r.l. de cv. It was reported that 7 months following the implant of a transcatheter aortic valve, leaflet thickening was identified via computed tomography angiogram (cta) that was further analyzed via a non-medtronic artificial intelligence (ai)-powered simulation. the patient is being evaluated for a transcatheter valve-in-valve procedure.
limitation: FDA adverse-event reports can be incomplete, duplicated, or unverified and do not establish that a device caused the reported outcome.
tag: Evidence-backed problem
key_points: Device: Evolut r transcatheter aortic valve; manufacturer: Medtronic mexico s. de r.l. de cv. | FDA report type: Injury. | An adverse-event report is a safety signal, not proof that the device caused the event.
rundown: It was reported that 7 months following the implant of a transcatheter aortic valve, leaflet thickening was identified via computed tomography angiogram (cta) that was further analyzed via a non-medtronic artificial intelligence (ai)-powered simulation. the patient is being evaluated for a transcatheter valve-in-valve procedure.

The report is part of FDA’s MAUDE surveillance data. It should be read as a signal for follow-up, not a clinical conclusion or a verified incidence rate.
sources:
- government | FDA MAUDE report 24706346 | https://api.fda.gov/device/event.json?search=mdr_report_key%3A%2224706346%22&sort=date_received%3Adesc&limit=1 | 2026-03-26
prev: 85ef2873895dc0fd8935816a596bb55305af1aaed6b77e81db7c4726f5ef2660
sha256
57677deb2aecc26d18f84248a162c8feb5c9c64cbe2bef0bc95c09699ef57073
previous
85ef2873895dc0fd8935816a596bb55305af1aaed6b77e81db7c4726f5ef2660
Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-0047 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.