TeamDME! FAQ:  B 17 Error Codes
Up

ANSI code B17 means one of the following:

1) No CMN on file at all
2) CMN incomplete (usually section B questions unanswered)
3) Initial, recertification or revised CMN not on file

Since B17 does not specify exactly what's wrong, suppliers must
search for every possibility. CAUTION: Claims receiving B17 denials
ARE NOT ELIGIBLE for appeals.

STEP 1 - Prevent B17 denials by inspecting claims before submitting it
to the DMERC:
1) Is the correct CMN type (initial, recertification or revision)
being sent?
2) Are all CMN sections completed?
    Author's Note:  When filling out a CMN, a field that is a black box is required.  A field that is gray is optional, unless otherwise necessary.
3) Does the date in Section A overlap that of a CMN already on
file at the DMERC?
4) Is the CMN accompanying the FIRST claim that will be affected?
    Author's Note:  in TeamDME!, the initial order/claim will carry the CMN to Medicare.

STEP 2 - Inspect your electronic billing software!
1) Does your software require an extra step to transmit a CMN (e.g. hit "enter" after the CMN fields have been filled)?
    Author's Note:  TeamDME! requires either a C or R in the sending field, but hitting ENTER is not necessary.
2) Were the CMN fields completed at the time of the transmission?  Run an output data report to see what transmitted.
3) Does the software allow for an implied decimal when test results are entered for Oxygen CMN? For example, if a saturation level is 55, it may need to be entered as 550, so it will be transmitted as 55.0, not .55 or 5.5 - which results in an invalid score and B17 denial.
    Author's Note:  TeamDME! correctly send the flow rate percentage as a 3-digit number.  Ex: If you entered a 5 for 5%, the system will send 500 to Medicare.

Contact your software vendor for more information.

To expedite research, it may be helpful to transmit claims with CMN's
in a separate batch.

STEP 3 - Read you CMN Reject Report!


The CMN reject report follows the front-end report, and lists claims whose CMN's were rejected (meaning they are not in the CMN system). CMN's will be listed with a four-digit code and explanation for the rejection.

Be sure to make a list of the affected claims and track their progress in claims status inquiry (CSI). They will be processed against the CMN already on file. If the CMN is valid, the CMN will be paid. If the CMN is invalid or missing the claim will deny B17.

CAUTION: Even id the claim is paid, the CMN on file may soon expire - and subsequent claims may be denied B17.

STEP 4 - Review the CMN for errors!

A CMN may be rejected because:
1) You entered the wrong date and/or CMN type (e.g. meant to send a revised CMN, but sent a recertification CMN).
2) You tried to send a corrected CMN because the CMN on file contains errors.
3) Another supplier provided the same or similar equipment.

STEP 5 - Contact Provider Assistance to see if customer service Assistance (CSA) can resolve the problem - r if you want a review.

If you need to correct information on a CMN that is already on file, you must file an appeal on the claim on which the CMN was originally submitted.  NOT THE ONE THAT DENIED B17(not eligible for appeal).

CMN REJECT REPORT CODES AND EXPLANATIONS:

3030 - SUBMITTED CMN IS AN EXACT DUPLICATE OF CMN ALREADY ON FILE.
3031 - SUBMITTED CMN INITIAL DATE IS EARLIER THAN THE END DATE OF THE CMN ALREADY ON FILE.
3032 - SUBMITTED RECERTIFICATION OR REVISED CMN THAT IS AN EXACT DUPLICATE OF RECERT OR REVISED CMN ALREADY EXISTS.
3047 - SUBMITTED RECERTIFICATION CMN WHOSE INITIAL DATE IS NOT EQUAL TO THE INITIAL DATE OF THE CMN ALREADY ON FILE FOR THE SAME CODE.
3048 - SUBMITTED RECERTIFICATION CMN FOR A CMN THAT HAS BEEN PLACE IN A DISCONTINUED STATUS BY THE DMERC.
3052 - SUBMITTED REVISED CMN FOR AN INITIAL CMN THAT HAS BEEN CLOSED.


Questions or comments regarding the website should be directed to the TeamDME! webmaster.

Last updated: October 21, 2002
Copyright © 2002 Spectrum Software, Inc. All rights reserved