Locating Relevant Documentation

Abstraction is not reading the whole chart and copying every interesting phrase. It is locating the documentation that supports the claim. On the CBCS exam, the question may give a short note, an encounter summary, an operative excerpt, or selected facts. The candidate must decide which facts are relevant to coding and billing. In real practice, the relevant facts often live in different parts of the record. The registration record supports patient demographics and insurance. The order or referral may support why a service was requested. The chief complaint states why the patient presented.

Key Concepts

The history of present illness explains symptoms and context. The review of systems and physical exam may add findings. The assessment and plan usually contain the provider's diagnostic conclusion and treatment decision. The procedure note or operative report describes what was done. Diagnostic reports provide test findings. Medication administration records and supply records can support separately billable drugs or supplies when rules permit. For diagnosis coding, the provider's assessment, impression, final diagnosis, discharge diagnosis, or signed progress note usually carries the most weight.

A coder should not code a condition only because it appears in a problem list, past history, or copied template unless the record supports that it affected the encounter according to applicable rules. Chronic conditions may be coded when they are assessed, treated, monitored, affect care, or are otherwise documented as relevant to the encounter. Past history codes may be appropriate when a resolved condition has ongoing relevance, such as a history of malignancy or prior surgery, but a past condition is not the same as an active condition.

CBCS candidates should look for terms that show status: active, chronic, history of, resolved, postoperative, current, recurrent, or screening. Procedure coding requires a different reading pattern. The title of an operative report is useful but not enough. The body of the report documents the approach, anatomical site, extent, devices, complications, and whether the planned service was completed.

A note titled colonoscopy with biopsy should be checked for whether the scope reached the intended area, whether a lesion was biopsied, whether a polyp was removed by snare, and whether the procedure was diagnostic or therapeutic.

Workflow and Documentation

A surgery note may include multiple procedures, but not every step is separately reportable. Some steps are inherent in the main service. The CBCS candidate does not need to memorize all bundling edits, but should understand that coding uses the documented service and the applicable code set instructions, not just the heading. Lab and imaging documentation can be tricky. A radiology report may say infiltrate suspicious for pneumonia, but diagnosis coding generally relies on the provider's diagnostic statement in outpatient settings.

A lab result may show elevated glucose, but the coder should not diagnose diabetes unless the provider documents diabetes. However, abnormal findings can be coded when they are the reason for a service or are documented as findings, depending on the encounter. The practical rule is to separate clinical data from provider interpretation. Coders report what the provider documents and what coding rules allow; they do not independently diagnose from test values. Relevant documentation also supports medical necessity.

A diagnosis code should explain why the service was reasonable and necessary for that patient on that date.

If a patient receives a strep test, the note should support sore throat, fever, exposure, tonsillar findings, or another medically relevant reason. If a patient receives a screening colonoscopy, the diagnosis support differs from a diagnostic colonoscopy for rectal bleeding. If a provider orders durable medical equipment, the record should support the condition, functional limitation, and need for the item. Place of service and telehealth documentation also matter because the same clinical service can be billed differently depending on where and how it occurred. Conflicts must be handled carefully.

Exam Application

One note may say left knee pain while another says right knee pain. An order may request a CT abdomen, while the report says CT abdomen and pelvis. A diagnosis list may include asthma, but the assessment addresses acute bronchitis only. A coder should not guess. In practice, follow facility policy, check whether later authenticated documentation resolves the conflict, and query the provider when needed. For the CBCS exam, choose the answer that relies on the clearest signed provider documentation and avoids unsupported inference.

Efficient chart review follows a sequence: identify the encounter type, identify the reason for visit, find the provider's final assessment, locate procedure details, confirm site and laterality, note complications or external causes if relevant, check payer or Medicare requirements when supplied, and match diagnoses to services for medical necessity.

High-Yield Checkpoints

• Code selection depends on the record source: provider assessment, operative report, order, diagnostic result, medication record, and discharge documentation may each contribute different facts.
• The chief complaint explains the reason for the encounter, but the final supported diagnosis may be found in the assessment, impression, or plan.
• Procedure coding often depends on the operative note or service report because it documents what was actually performed.
• Diagnostic test results are usually not enough by themselves to code a diagnosis unless the provider interprets and documents the condition, subject to applicable setting rules.
• A coder should reconcile conflicting documentation by following facility policy and seeking clarification rather than selecting the most convenient code.