|
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!
|
|
Questions or comments regarding the website should be directed to the TeamDME!
webmaster.
Last updated: October 21, 2002
|