Explainer
Where the coding rules come from
Every rule that decides a code can be traced to the source it came from. Here is what those sources are, and what is deliberately not one of them.
Coding advice is worth exactly as much as its source. So every rule in Mesio that influences a code records where it came from, in a list that is maintained rather than assumed.
What counts as a source
Four kinds, and they do different jobs.
- The official code set, licensed. This is where code descriptors come from, and a code cannot be produced by Mesio unless its descriptor is in that licensed set.
- Published clinical classification, which is where the periodontal criteria come from rather than from anyone's house style.
- Carriers' own published processing policies, for how plans actually behave.
- Licensed coding guidance from a practicing advisor, used with permission.
Each rule records which of these it rests on and why. Where a source is still being acquired, the rules depending on it are marked provisional, with a note that they should be verified before being relied on in a denial.
What is deliberately not a source
Mesio does not copy, paraphrase or ingest a commercial coding reference. The rules are derived from primary material and expressed in Mesio's own words.
That is more work than the alternative, and it is the difference between advice you can trace and advice somebody transcribed from a book.
A dentist and a coder signed off
The clinical rules were reviewed and signed off by a practicing dentist and a credentialed coder, rather than being written by engineers and shipped. Where that review has not happened, the rule says so.
What Mesio does not claim
Being precise here, because coding advice is where software oversteps.
Mesio does not tell you a claim will be denied. Where a rule reflects how plans typically behave rather than how a specific plan behaves, it says most plans and asks you to check. Your patient's contract is the authority, and Mesio does not have it.
A quiet ledger is not evidence. Where Mesio checks history against frequency limits, it says according to the chart, because work done elsewhere and never recorded looks identical to work never done.
Why this matters to you
Two reasons. If a coding decision is ever challenged, you can find out what it was based on rather than being told the software decided. And it means the product cannot quietly drift into folklore, which is what happens when nobody records why a rule exists.