FDA Records Class III Recall of 18 Lidolog Kits Over Barcode Labeling Issue
An FDA enforcement report dated July 29, 2026 lists an ongoing recall by Asclemed USA Inc. of 18 kits distributed in Tennessee, after a label wrap covered the barcode.
Was this report accurate and useful?
Sources
- https://api.fda.gov/food/enforcement.json?search=recall_number:%22D-0713-2026%22
- https://www.fda.gov/safety/industry-guidance-recalls/recalls-background-and-definitions
- https://dailymed.nlm.nih.gov/dailymed/drugInfo.cfm?setid=069e145d-7992-4f56-9fcb-20782ecc2d53
- https://dailymed.nlm.nih.gov/dailymed/fda/fdaDrugXsl.cfm?setid=0c0790ec-effd-4d8a-9874-8ca0b31e54d0
- https://dailymed.nlm.nih.gov/dailymed/lookup.cfm?setid=858f3faa-e56e-51f9-e053-2a91aa0aa721
- https://ndclist.com/ndc/76420-760/package/76420-760-01
Revision history
- Version 67 Aug 2026, 13:35current
Added headline and dek; body unchanged from v5.
- Version 57 Aug 2026, 10:44
Removed product-description figures and marketing-status claims not present in the supplied reference data; tightened attribution of the composition details to DailyMed and the NDC Directory.
- Version 47 Aug 2026, 06:16
Added headline and dek, plus a sourced paragraph from DailyMed explaining what a Lidolog Kit is and who handles it.
- Version 37 Aug 2026, 01:12
Removed the DailyMed/USP product-background and distribution-channel paragraphs, which were not supported by the supplied fact set, and restored the FDA record's exact product wording.
- Version 26 Aug 2026, 20:44
Corrected the product background to match the labeling records — removed unsupported kit component sizes and marketing-category detail, added the vial's composition and how the kit is distributed.
- Version 16 Aug 2026, 16:13
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.