CBCS common mistakes
CBCS · Understand the traps and how to avoid them.
Reading only the 'active' status on an eligibility response and answering the question as if coverage is confirmed for the date of service, without comparing the plan's effective and termination dates to that date.
Eligibility portals and 271 responses display a coverage span plus an active/inactive flag; candidates scan the flag and stop, and also forget mid-month terminations, retroactive reinstatements, and plan changes that take effect on the first of a month.
What to do instead
For every eligibility item, state the date of service first, then check that it falls inside the effective/termination window, and note the specific plan and payer ID that applies on that date. Memorize that eligibility answers are date-specific, not account-specific.
Treating a referral and a prior authorization as the same requirement, or assuming an authorization approved for a number of visits covers an unlimited number of encounters.
The two terms are used loosely in practice and both involve payer permission, so candidates substitute one for the other; they also overlook that authorizations carry unit, date-range, and provider limits, and that retro-authorization windows are short or nonexistent.
What to do instead
Define each separately in your notes: a referral is a PCP/gatekeeper approval to obtain specialist care; a prior authorization is a payer determination of medical necessity for a specific service, code, quantity, and date range. On questions, ask which of the four limits (units, dates, code, provider) the scenario is testing.
Assigning an E/M level by counting history, exam, and medical decision-making elements on a visit dated 2021 or later for office/outpatient codes, instead of using the current framework in effect.
Older study habits and legacy documentation templates reinforce the 1995/1997 element-counting method, and candidates do not check which code set and date the question uses.
What to do instead
Before leveling any E/M service, identify the code family and the date, then apply only the framework in force for that family and date. Practice by leveling the same note under the current office/outpatient framework and noting exactly which element drove the level.
Assigning an uncertain diagnosis such as 'probable,' 'suspected,' or 'rule out' as the primary diagnosis on an outpatient claim, or defaulting to an unspecified code when the record documents the specificity.
Inpatient coding rules permit coding of uncertain diagnoses at discharge, and candidates carry that rule across settings; unspecified codes also feel 'safer' when the note is thin.
What to do instead
Fix the setting rule: uncertain diagnoses are not coded for outpatient/physician reporting - code the signs, symptoms, or reason for the encounter instead. For specificity, read the documentation one more time for laterality, chronicity, site, and severity before choosing unspecified.
Ignoring National Correct Coding Initiative edits and modifier rules, then answering that both codes on a claim will be paid as submitted when one should be bundled, or appending modifier 59 reflexively to override an edit.
Candidates memorize that modifiers 'unbundle' codes without learning that an override requires documented, distinct service, and they do not check whether the edit is modifier-eligible at all.
What to do instead
For every multiple-code claim, ask three questions: is there an NCCI edit, is the edit modifier-eligible, and does the documentation support a distinct service? Use the specific X-modifier that describes the separation rather than a blanket 59.
Answering a clean-claim question without checking the four data elements that generate the most front-end rejections: billing provider NPI/TIN pairing, rendering provider NPI, patient/payer identifiers, and timely filing measured from the correct date.
Candidates focus on the clinical story of the scenario and skip the administrative scrub, and they assume timely filing runs from the date of service rather than from the appropriate first-billing or remittance date for the payer.
What to do instead
Build a fixed pre-submission checklist you mentally recite on every claims item: provider identifiers, patient and payer identifiers, coding linkage, and filing deadline basis. Verify payer-specific filing rules rather than assuming a uniform window.
Recording the full charge as accounts receivable and posting only the insurance payment, leaving the contractual adjustment unposted, so the account shows a large patient balance.
Adjustments require a separate posting step and knowledge of the fee schedule or contracted rate; candidates conflate 'patient responsibility' with 'unpaid balance' and forget that allowed amount minus paid equals contractual plus patient portion.
What to do instead
Work every payment problem in the same order: charge, allowed amount, payer payment, contractual adjustment, then patient responsibility. Confirm that charge minus adjustment minus payment nets to the correct patient balance before answering.
Leaving credit balances and aged denials open instead of identifying refund obligations and working the account through the appeal or write-off decision.
Candidates treat a zero or negative balance as 'done' and do not distinguish a true overpayment from an unapplied patient payment, and they underestimate how short payer appeal windows are compared with filing limits.
What to do instead
On any account with a credit balance, determine the source of the credit and whether a refund or a takeback applies. On denials, calendar the appeal deadline on the remittance date, not the date you notice the denial, and document the appeal or write-off decision in the account notes.
Treating a statutorily excluded service as one that needs an Advance Beneficiary Notice, or billing a patient for a service that was denied as not medically necessary without a valid notice obtained before the service.
Candidates lump all denials into 'non-covered' and do not separate services that Medicare never covers (no ABN needed, but a voluntary notice may be used) from services that are covered but may be denied as not medically necessary in this instance (ABN required).
What to do instead
Classify the service first: statutorily excluded versus covered-but-may-be-denied. Only the second category requires an ABN, and it must be signed before the service is furnished with the reason and estimated cost stated.
Releasing protected health information to an employer, family member, or business associate based on verbal permission or a general consent form, or sending more records than the request requires.
Candidates conflate consent for treatment, payment, and operations with authorization for other disclosures, and they overlook that business associates require a written agreement while the minimum-necessary standard limits the scope of what is sent.
What to do instead
For each disclosure question, identify the purpose first: treatment/payment/operations permits use without authorization; anything else requires a valid authorization with the core elements. Then apply minimum necessary to decide what portion of the record is released, and check for a business associate agreement where a vendor is involved.