Skip to main content

Atomic fact-checking makes medical RAG checkable fact by fact. Document-level provenance still leaves evidence behind: structural amnesia in AI healthcare

Atomic fact-checking makes medical RAG checkable fact by fact. Document-level provenance still leaves evidence behind.

It is a clear case of structural amnesia in AI healthcare: facts move, and their record stays behind. That tension sits at the center of a useful new paper, and it is worth unpacking, because the gap it leaves open is the one that matters most when a clinical claim is examined.

What moved

In Atomic Fact-Checking in Retrieval-Augmented Medical Q&A, Vladika et al. (JMIR, DOI 10.2196/92090) take a medical question-answering system and do something sensible. They split the answer into atomic facts, verify each one against a medical-guideline knowledge base, correct the claims that come back FALSE, and trace facts to the supporting chunks.

The authors report gains of up to 50% in answer improvement and 80% in hallucination detection, strongest on real tumor-board questions.

This is good work. Making a medical answer checkable fact by fact is a real step toward explainability. It is also not proof that attestation travels when facts leave a signed lab report or SOAP note. The diligence ask is an attestation record per fact, not a citation to a guideline PDF.

Honest cuts

When research like this lands, it gets repackaged into sales claims fast. Here are five we expect to hear, and the plain answer to each.

"We cited the guideline PDF, so provenance is done." No. Buyers need the guideline ID, the version, and a durable span pointer per fact.

"Atomic fact-checking proves Part 11 travel." No. The signature stays on the source document when facts leave into RAG or summaries.

"TRUE or FALSE from the model is attestation." No. Model capacity stays model until a named person or authority stands behind the fact.

"Trace-to-chunk equals evidence infrastructure." No. A UI backtrace without versioned identity and accountability is theater.

"ScientixAI validates clinical RAG." No. We make evidence objects reconstructable. We do not replace clinician judgment.

The problem with this move

We call it structural amnesia.

Lab reports and encounter notes pack many endpoints under one signed document. The signature attaches to the document as a whole. That works while the document stays whole.

Medical RAG does not keep documents whole. It extracts. When a single fact leaves into a RAG answer or a tumor-board summary, the signature stays behind. The fact travels on its own, and AI can rewrite that orphan fact with no one accountable for the new version.

Fact-level checking against a guideline tells you whether the fact agrees with the guideline. It does not tell you who stood behind the original measurement, which version of the source it came from, or whether anyone with authority ever attested to the fact in its new form. Those are the questions that come up later, when a clinical decision is examined and someone must answer for it.

What we are

ScientixAI builds evidence infrastructure your AI and reviewers call, not another medical chatbot. It works across the systems you already run.

We do not validate clinical RAG or speak for FDA acceptance. Defensible AI starts with evidence that can answer for itself. We make the evidence object accountable per fact: what it is, where it came from, which version, and who stands behind it. This is the thesis we have argued before as provenance is non-negotiable.

Why now

Fact-level reliability is now visible. Papers like this one show that you can break an answer apart and check every piece.

Most stacks still ship document-level citations. Medical RAG widens extraction without widening accountability. Every new pipeline that pulls facts out of signed records multiplies the number of facts that can lose their attestation along the way.

The architecture chosen this year decides whether each fact arrives with an attestation record, or as an orphan no one can stand behind.

Trust is never the input, evidence is. Let's build evidence infrastructure together.

Become a design partner

We are choosing a small number of design partners to build defensible AI together. Design partners set the order of the roadmap and get evidence infrastructure inside their own boundary while it is being built.

Start the conversation

Subscribe via RSS