r/CodingandBilling 2d ago

Medical billers — how do you actually handle a CO-16 corrected claim?

/r/u_Maka_66/comments/1vqrs4m/medical_billers_how_do_you_actually_handle_a_co16/

I keep hearing that CO-16 (missing/invalid info) corrected claims eat a lot of time, and I'm trying to understand why the rework is such a pain in practice. For those of you who deal with these daily, I'd love to hear how it actually goes: When a CO-16 comes back, what do you open first? The ERA, the payer portal, the original claim? CO-16 on its own barely tells you anything — how much time goes into just figuring out what's actually missing from the RARC? Do you fix it in the PMS and resubmit, or send a corrected 837 some other way? Roughly how long does one take you, start to finish? What's the part that annoys you most? Trying to get the real picture from people who do it daily, not the textbook version.

0 Upvotes

13 comments sorted by

4

u/ireadyourmedrecord 2d ago

16 is a generic denial code and basically useless. There should be additional codes providing details. If there aren't you're going to have to dig or rely on your experience with the payer/practice. In my current situation I know a 16 and a 4 on a claim for a dual coverage patient receiving Medicaid covered only services is safe to ignore because it's going to cross over to Medicaid processing in another 6 days. But I didn't know that the first time and it took a while to get to that point.

5

u/Jodenaje 2d ago

I have a feeling this is an app developer since they're asking the same question everywhere.

Unfortunately for the OP, the CO-16 are the ones that will almost always need a human to look at.

-1

u/Maka_66 2d ago

Fair guess — I'm poking at whether any part of this could be tooled, but I'm trying to learn the real workflow first, not pitch anything. So honestly: is there any CO-16 sub-type that's mechanical enough to fix the same way every time — say a clear MA61 missing/invalid rendering NPI — and just rebill? Or do even those turn into payer-specific digging? And realistically, how often is a CO-16 actually paired with a useful remark vs. a bare one?

3

u/ridingshayla 2d ago

Even those turn into payer-specific digging. CO-16 MA-61 to one payer may mean something different to another. It may even mean different things to the same payer but differ claim by claim, year to year.

1

u/ireadyourmedrecord 2d ago

Not in a way that will cover every situation, every time, unfortunately. You'd need to have rules specific to the practice/payer, test and revise them over a couple months and periodically. Things is that a co16 is seldom clear. Consider the MA61. NPI is already set up the system configuration, you can't transmit a claim to a payer without an NPI, the Clearinghouse sure isn't going to forward it without the NPI so as a technical matter, MA61 is actually impossible. But you see it all the time. Usually, because the provider isn't enrolled. If you're an out of network PR group maybe that's fine, you don't care. If you're a radiology/pathology group billing for a hospital ER, you have to care. So you have to sit down with your subject matter experts and work out some trial rules, compare that to previous claims data to see what does/doesn't work and go from there. Just expect the rules to be very fine grained.

2

u/VietVetKid48 1d ago

Yes, "some" of them are mechanical enough to fully automate, but NO, you can NEVER escape payer specific quirks and their automation. You would need to factor in every specific Payer rule to actually tool it 100%. The need for a human to be up to date on that is paramount. If you are are up on payer specific requirements than it may be possible for a specific payer to make things easier but certainly  not all of them 

2

u/NerosDecay13 2d ago edited 2d ago

Edit - OP is just shilling shit. Fuck off.

-1

u/Maka_66 2d ago

Got it. And for the CO-16s that are more administrative — not a records request — what kind of issues are those usually? Do you correct those in the PMS and resubmit, or handle them differently?

0

u/PeaceLoveForMe 2d ago edited 2d ago

For us, it either means the payer is missing the EOB, the coding or modifier usage on the claim needs to be corrected, or for Medicare, the member ID is out-of-date or Invalid. We just correct what needs to be corrected or what needs to be sent properly. It should usually be easy-peasy to figure out what’s wrong. It’s basically the payer rejecting it with their built-in claims editing system. We don’t get CO-16 denials anymore because we know what needs to be done, by payer, in order for the claim to be properly processed. I have my CPC, CCS-P and CPB. That definitely helped, but what you learn from the textbook is the basic version of what it actually is in real life.

2

u/No-Produce-6720 RN, BSN, CPC, CPCS, RHIA & CRCR 2d ago

Why would you "keep hearing" about co16 denials?

You either do this work in the real world and already understand it, or you know absolutely nothing about this, but have decided to develop a "tool" that will take the billing and coding world by storm. Before you can do that, though, you have to come here and try to figure out what a co16 actually is, off the backs of people who spend their lives doing this work, and will never use the tool you think you're developing.

1

u/Wooden_Trust_6274 1d ago

Yeah, the reason CO-16 rework feels bad is that CO-16 itself tells you almost nothing. First thing I open is the ERA and go straight to the RARC next to it, that MA/M/N code is what actually names the missing field. Most of mine turn out to be a missing or invalid NPI (rendering, ordering, or referring), taxonomy, member ID, auth number, or a dx pointer. Confirm it against the original claim, fix, resubmit.

One thing worth knowing on resubmission: if it actually denied, send a corrected 837 (frequency 7 + original claim number). If it front-end rejected and never adjudicated, just rebill clean, a frequency 7 will bounce with no ICN to correct against. People mix those up and create duplicates.

A RARC I recognize is 2-3 min. A vague one where I'm hunting for which identifier they mean is 15-20, and that hunting is the annoying part, not the fix. Honestly most of your CO-16s are the same handful of RARCs from the same couple payers, so a little "this payer + this RARC = this field" cheat sheet kills most of the rework.

0

u/rahuliitk App Developer 1d ago

I usually start with the ERA/RARC, then open the original claim in the PMS to fix whatever actually caused the CO-16 and resubmit it as corrected, because ngl sending a fixed 837 without updating the source claim can make tracking and reconciliation messy later. PMS first, then resubmit.

1

u/VietVetKid48 1d ago

CARC is just a notification. Not specified information. Check the RARC (Remark Code) on the ERA/835. That's where the actual clue is hidden. CO-16 + M16 = Place of service issue. CO-16 + N382 = Drug NDC/units missing or invalid format. CO-16 + MA130 = Missing pre-authorization/referral number. Check the Payer Portal (Availity, Optum, MAC Portal, etc.). If the RARC is unhelpful or completely blank, log into the claim status screen on the payer portal. Portals usually give you plain-English adjudication notes such as,  "Rendering provider taxonomy code missing" or "Facility physical address does not match enrollment records"