FDA Publishes Class II Recall for Alphatec SafeOp Patient Interface Over Software Fault
The enforcement record covers three units distributed in Texas, Missouri and Indiana and lists the action as ongoing.
Was this report accurate and useful?
Sources
- https://api.fda.gov/food/enforcement.json?search=recall_number:%22Z-2793-2026%22
- https://www.fda.gov/safety/industry-guidance-recalls/recalls-background-and-definitions
- https://fda.innolitics.com/submissions/NE/subpart-b%E2%80%94neurological-diagnostic-devices/GWF/K252842
- https://www.accessdata.fda.gov/cdrh_docs/pdf23/K234092.pdf
Revision history
- Version 57 Aug 2026, 14:56current
Removed the unsupported electrical-supply figures from the device-description paragraph (the "100\u2013240 VAC supply via a 12 VDC power pack" clause), replacing them with the non-numeric statement that the unit is mains-powered and runs from an external power pack; also dropped the unsourced enclosure dimensions, weight and channel count from that sentence while keeping the point that it is IV-pole-mounted hospital capital equipment. Serial numbers now printed exactly as the fact set gives them (2007716/ DG106225, 2005498/ DG106220, 2005490/ DG106230). Added explicit attribution to the FDA enforcement report for the stated reason and the Class II classification. No other substantive changes.
- Version 47 Aug 2026, 06:27
Product-background paragraph rewritten to match the cited AccessGUDID and FDA 510(k) records, removing device specifications not supported by those sources.
- Version 37 Aug 2026, 01:01
Expanded the device-background paragraph with the FDA regulatory classification (21 CFR 882.1870), system components and filed physical/electrical specifications and cleared indications; removed the unsupported detail about a separate power-supply model number.
- Version 26 Aug 2026, 20:28
Added the 510(k) clearance number K252842, the manufacturer's Carlsbad, California location, and the separately listed AIX11241 power supply accessory from the AccessGUDID database.
- Version 16 Aug 2026, 15:54
First published.
How we work
This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.
Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.
Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.
None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.