Search now understands plain language, not just codes
Billing and coding staff don't always think in code numbers. A biller who needs the fee for a knee replacement usually knows it as "knee replacement," not as 27447. Until now, our search box wanted the code, an exact code prefix, or something close to the official code description — anything else came back empty, and the reader had to go look the code up somewhere else first.
What changed
Search now finds the right code from how people actually describe it: a plain-language phrase, a common abbreviation, or a term with a typo. Short, colloquial queries that used to return nothing now return the correct match, and near-miss spellings resolve the same way a clean search would. The goal is the same one the fee lookup itself is built for — get the right answer without asking the reader to already know the system's vocabulary.
We also tightened how search handles queries where the right answer isn't a ranked list at all. If a query names something outside our covered set of codes, or asks for a modifier rather than a procedure, search says so and points toward the right place instead of guessing with a page of loosely related results. A confident wrong answer is worse than an honest "not here."
Why this matters for the workflow
A fee lookup only helps if the reader can find the code in the first place. A billing team pulling together an appeal, checking a fee before a visit, or auditing a contract rarely starts from the code number — they start from what the patient or the claim describes. Every extra step between that plain-language starting point and the right code page is a place the workflow stalls, and a search box that only understands official terminology pushes that lookup burden back onto the person who has the least time for it. Closing that gap is a search improvement, but the motivation behind it is the same one behind the rate engine itself: give the reader the correct, checkable answer with as little friction as possible.
A concrete example
Type "CBC" and search now returns the complete blood count code directly, the same way it already did for the formal procedure name. "EKG" resolves to the electrocardiogram code the same way. These are exactly the kind of everyday shorthand a coding team uses out loud and types into a search box without a second thought, and search now recognizes it across the corpus rather than only recognizing the official terminology CMS publishes.
Try it
The fee lookup should work the way a billing team actually talks, not just the way CMS writes. Try a plain-language search and see how it handles the terms your team actually uses.