TruaceTracing the truth around AITuesday, August 25, 2026
TRV-2026-0877Certified recordPeer-reviewed

From accuracy to service: deciding what artificial intelligence outputs may do in veterinary diagnostic laboratories

Artificial intelligence (AI) tools are entering veterinary diagnostic laboratory service, but reported model accuracy does not determine what the laboratory staff should allow an output to do. This Commentary defines service entry as the point at which an AI output is allowed to influence case triage, interpretation, a draft report, or result release. Before that point, the laboratory staff should first decide whether the submitted specimen can support the question being asked. They should then document 7 decisi…

Health · P Space — documented harm · certified 2026-08-25 · v1 · article view · machine-readable

Current reading — problem

The same canine lymphoma cytology AI performed less favorably on B-cell versus T-cell classification, prompting concern that allowing outputs to influence reports without pathologist review and without assessing whether the specimen supports the claim could lead to unsupported clinical claims.

What this doesn’t fix

Performance varies by clinical claim and specimen information content; Romanowsky-stained cytology images may not support B-cell versus T-cell classification, and interpretive outputs should not reach clients without pathologist review.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0877, v1: “From accuracy to service: deciding what artificial intelligence outputs may do in veterinary diagnostic laboratories.” Truvace, 2026-08-25. /record/TRV-2026-0877 (accessed at citation time). sha256 a2a995f468efc5cf

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv1a2a995f468ef

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-0877 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.