CCC common mistakes
CCC · Understand the traps and how to avoid them.
Assigning the primary diagnosis from the reason for the visit stated on the intake form without confirming it against the provider's documented final assessment in the record.
Candidates treat the chief complaint or referral reason as the definitive diagnosis, so they code a suspected or rule-out condition as confirmed. This happens because intake paperwork is read first and feels authoritative.
What to do instead
Before assigning any diagnosis code, locate the provider's assessment/impression and code only conditions the provider documents as established; treat 'rule out', 'probable', and 'suspected' as not coded in outpatient settings.
Coding each component of a composite or bundled service separately instead of selecting the single code that fully describes the documented procedure.
Candidates index each keyword they see in the operative note and pick a code per keyword, missing the combination code or the bundling instruction that absorbs the components.
What to do instead
Read the entire operative/procedure note first, then check the tabular list for combination codes and 'includes'/'excludes' notes before finalizing; verify with the index that no single code captures the whole service.
Choosing a code at the category level (three characters) when the classification requires additional characters to be valid.
Candidates stop at the first code that matches the term and do not verify the code's required length or specificity in the tabular list.
What to do instead
Always cross-check the selected code in the tabular list for 'code is invalid without 4th/5th/6th character' notes and select the most specific valid code supported by documentation.
Assuming a laterality, episode, or encounter designator based on the patient's dominant side or the current visit type without documented support.
Candidates fill mandatory character slots with a plausible default (e.g., right side, initial encounter) rather than the documented value, because the field is required and they want a complete code.
What to do instead
Treat every required character as a documentation query point: confirm laterality and encounter/episode status in the note; if not documented, query rather than default.
Mixing terminology from different body systems or using a lay synonym as if it were the formal anatomical term when selecting a code.
Candidates rely on everyday meanings of words (e.g., 'stomach' for any abdominal pain, or confusing similar-sounding structures) instead of precise anatomical definitions.
What to do instead
Map each documented term to its formal anatomical definition and location before indexing; when a term is ambiguous, use the note's context (site, approach, specimen) to disambiguate.
Applying an inpatient-only or facility-specific guideline to an outpatient claim, or vice versa, because the setting was not identified first.
Candidates memorize rules without anchoring them to place of service, so they apply the wrong coding conventions to the scenario.
What to do instead
Begin each case by identifying the care setting (inpatient, outpatient, physician office) and then apply only the guideline set that governs that setting.
Selecting a code based on the reimbursement amount or 'what pays best' rather than on documented clinical facts.
Candidates under time pressure reverse-engineer the answer from the highest-paying option, which conflicts with coding from documentation.
What to do instead
Code strictly from the documented clinical facts first, then use payment knowledge only to verify the code is plausible; never let payment drive code selection.
Ignoring payer-specific or medical-necessity edits and modifiers when a service could be denied as bundled or not covered.
Candidates focus only on the procedure code and skip the compliance layer (NCCI edits, medical necessity, modifier justification).
What to do instead
After code selection, perform a compliance check: confirm medical necessity is documented, check bundling edits, and apply a modifier only when documentation supports it.
Accepting a record as complete without verifying that required elements (authentication, timeliness, required data fields) are present and consistent.
Candidates equate a long note with a complete record and do not check for missing signatures, dates, or internal contradictions.
What to do instead
Apply a checklist: confirm authentication, date/time, required data elements, and internal consistency; flag deficiencies rather than coding around them.
Disclosing or using protected health information beyond the minimum necessary, or coding from records accessed without a valid purpose.
Candidates treat privacy as a background concern and do not connect minimum-necessary and authorization rules to the coding workflow.
What to do instead
Before accessing or sharing records, confirm a valid purpose and limit use to the minimum necessary; verify authorization for any non-treatment disclosure.