Why your LLM architecture is failing your accuracy targets

noodlemind Beginner 5d ago 52 views 4 likes 1 min read

Your medical coding recall will never hit 90% through prompting alone. We hit a wall at 60% trying to force a probabilistic model to act like a deterministic rulebook. We were building a platform for CPT and ICD assignment, and despite feeding the model more context and upgrading to larger models, we couldn't bridge that gap.

The mistake is assuming the model lacks "intelligence" when the reality is a mismatch in logic types. LLMs guess the next likely token; they don't inherently respect the National Correct Coding Initiative (NCCI) constraints. These administrative rules live in regulatory tables, not in the clinical notes the model is reading. You can fine-tune all day, but if the model doesn't "know" a specific code pair is forbidden by a hard rule, it will keep hallucinating valid-looking but incorrect combinations.

We stopped wasting money on larger context windows and bigger models and built a deterministic validation layer instead. The new workflow is simple: the LLM extracts candidate codes from the unstructured text, then a hard-coded engine checks those candidates against the full NCCI edit set.

Moving the logic out of the prompt and into a post-processing pipeline took our recall from 45% to 92%. If you're trying to solve a regulatory or math-heavy problem with better prompting, you're just throwing compute at a structural flaw. Stop trying to make the model smarter and start making the architecture more rigorous.

https://www.cms.gov/medicare/coding-billing/ncci-edits

LLMLarge Language Modelaimachinelearningarchitecture

All Replies (4)

S
softwhere Novice 5d ago
We tried more data first, but cleaning up our RAG retrieval logic actually moved the needle more.
0 Reply
L
labmember77 Advanced 5d ago
Architecture won't save you if your underlying data pipeline is just garbage in, garbage out.
0 Reply
Y
ycombinator70 Beginner 5d ago
Same thing happened to us; we wasted weeks on fine-tuning before realizing our vector database was misconfigured.
0 Reply
G
gradstudent Beginner 1d ago
Man, I once spent an entire weekend debugging weights only to find a broken retrieval pipeline. It hurts!
0 Reply

Write a Reply

Markdown supported