Type a claim adjustment reason code, or just what the payer told you, and get the official description plus the first thing to check. 77 codes covered. It runs entirely in your browser — nothing you type leaves your machine.
Try:
77 guides. Nothing is sent anywhere — this runs entirely in your browser.
CO-197Prior Authorization
Prior authorization absent
The payer required prior authorization for this service and cannot find one attached to the claim.
First thing to check
Pull the authorization record and compare four things against the claim: the CPT code, the units, the date range and the rendering provider
The claim arrived after the payer’s filing deadline. This one is usually terminal, which is why it deserves attention before it happens rather than after.
First thing to check
Check whether you can prove timely submission: a clearinghouse acceptance report with a date inside the window will overturn many of these
The payer does not accept that the documentation supports the service. This is a clinical argument, not a clerical one.
First thing to check
Find the payer’s own coverage policy, the LCD or NCD for Medicare, and read what it actually requires — appeals that do not quote the policy mostly fail
The payer is bundling this code into another one on the same claim. Sometimes that is correct and sometimes it is not.
First thing to check
Check the NCCI edit pair and whether a modifier is permitted to break it — some pairs allow it and some do not, and billing a modifier on a pair that does not allow one is a compliance problem, not a shortcut
The payer thinks somebody else is primary. Until coordination of benefits is corrected on their file, nothing on this claim will pay.
First thing to check
Call the patient before you call the payer. They can usually resolve the COB record themselves in one phone call, and the payer will not update it on your say-so
The payer accepts the service but not the quantity or the frequency at which it was billed.
First thing to check
Check the payer policy for the frequency limit and the period it runs over — a rolling twelve months and a calendar year are different things and practices lose money on that distinction
A credentialing or enrollment problem rather than a claim problem: nothing this provider bills to this payer will pay until it is fixed, and it is rarely one claim.
First thing to check
Establish the effective date of the enrollment before touching the claims — that date tells you which claims are recoverable
Looking up one denial takes a minute. Working a whole queue of them is somebody’s week, every week. Send an aged AR report and you get back, in writing, what is recoverable and what working it would take — free, whether or not you buy anything.
Nothing you typed into the tool above is attached to this. This form sends the three fields in it and which page it came from — that is all it can send. Or write to info@softhomebpo.com and skip the form entirely. What happens to it.
Running this for other practices, not just your own?
Billing companies and BPOs buy seats in one yes, not one at a time — published tiers from 5 seats, a 3-seat prepaid pilot first. Leave your details and the partner desk will call, not the sales queue.
This form sends the three fields above and which page it came from, to the partner desk — not the practice sales queue. Read the published tiers or write to ops@softhomeglobal.com directly.
Or paste the whole line
A denial is a group code, a reason code and usually a remark code. Read together they say who is liable, what is missing and what to do — CO-16 with M51 is a different afternoon from CO-16 with MA130. Every X12 reason and remark code, official text. More on remark codes →
Showing an example line (CO-16 M51). Paste your own or pick another. Group code, reason code and remark code together. The full reason and remark code lists, official X12 text. Runs in your browser: the tables load once as a file; what you type is not sent anywhere.
Loading the code tables…
Questions
Is this free?
Yes, and there is nothing to sign up for. It runs entirely in your browser — nothing you type is sent anywhere, which matters when the thing you are looking up relates to a real claim.
Where do the code descriptions come from?
The official text is the X12 claim adjustment reason code set, used by every United States payer. Everything after that description is our own working guidance, and it is labelled as such.
Can I use this on my own site?
Link to it freely. If a code your team keeps hitting is missing, say so and it will be added — the guides are written from the codes people actually get stuck on rather than from a list.
Why does a company give this away?
Because somebody looking up a denial code at four in the afternoon is exactly the person who later needs somebody to work the queue. Being useful first is cheaper than advertising and it lasts longer.
Code descriptions are the standard published text. Everything after them is operational guidance on how the work is done, and payer policy governs any individual claim.
Next step
Or have somebody work the queue
These guides tell you what to do. A seat is somebody doing it, every working day, during your business hours.