Documentation before code selection

Where you are

Medical language helps you understand a record. Coding begins when you turn that understanding into a supported, verifiable selection. Before opening an index, identify the encounter, the diagnosis evidence and the service actually performed. A familiar code is not a substitute for this reading step.

Keep an abstraction worksheet beside your books. It should help you find the facts quickly without becoming a second, rewritten chart. Use short entries and preserve the words that affect coding: site, side, certainty, time course, extent and relevant relationships.

Start with the encounter

Record the service date and setting first. Then identify whose service you are coding and what the task asks you to report. A physician's professional service, a facility service and an inpatient diagnosis exercise do not necessarily use the same rules or code sets.

For this course's diagnosis examples, check whether the encounter is outpatient before applying the outpatient certainty rules. The official ICD-10-CM guidelines distinguish outpatient reporting from inpatient diagnosis reporting. Do not transfer the inpatient rule for uncertain diagnoses into an office encounter. [icd-guidelines, II.H; IV.H]

The service date also determines which edition or effective update applies. Write it at the top of the worksheet rather than relying on today's date or the year printed on a nearby book. The course provides dates so you can practice making that distinction deliberately.

Identify the reason and established assessment

CMS documentation guidance describes a record that supports the reason for the encounter, relevant history and findings, assessment, and plan. Reported services must be supported by the record; the amount of text alone does not establish a higher service level. [em-cms, pages 21–22]

Separate the patient's reason for seeking care from the clinician's finalized assessment. They may be the same, or the evaluation may establish a more specific condition. A patient's concern about cancer does not itself establish cancer. A test order does not itself establish the diagnosis being investigated.

Your worksheet can use two fields: reason for encounter and established assessment. Add an uncertainty field when needed. This lets you retain the clinical story without treating every phrase as an equally certain diagnosis.

Keep meaningful qualifiers

Anatomical detail may include an organ, region, side, tissue layer or a named structure. Other qualifiers may identify acuity, stage, a complication or another distinction used by the classification. Preserve what is documented and check which details the candidate entry requires.

Do not maximize specificity by guessing. Use the highest specificity supported by the available documentation and the classification's instructions. The official outpatient guidance addresses the level of detail in coding, while the general instructions require verification of a candidate in the Tabular List. [icd-guidelines, IV.F; I.B.1]

Try a short exercise: write “left wrist pain” and then remove left. What information disappeared? Now replace wrist with hand. What information changed? These are different abstraction errors, even before you choose a code.

Separate diagnoses from services

A diagnosis describes the condition or reason associated with care. A service describes work performed. An assessment of a skin lesion does not establish that it was removed. A discussion of a future test does not establish that the test occurred today.

For a procedure report, record the target, action, approach and extent. Add other details required by the relevant section. For E/M work, use its applicable selection rules rather than deciding a level from the length of the note. CMS explicitly cautions against using documentation volume to choose the service level. [em-cms, page 22]

Use two columns on the worksheet: diagnosis evidence and service evidence. A detail can help explain both, but the two columns answer different questions. The first asks what is established; the second asks what was done.

Missing information requires a deliberate response

When a required detail is absent, stop and identify the exact gap. Do not add a diagnosis, side, complication or procedure detail to complete a candidate you prefer. Review the available record and follow the appropriate clarification process when necessary.

A useful clarification request identifies the relevant documented facts and the missing or conflicting point without steering the clinician toward a more profitable answer. Give the clinician room to exercise independent judgment. The August 2026 ACDIS/AHIMA brief applies across care settings and replaces earlier versions. This course uses fictional requests to teach the habit; an employer's compliant query policy and applicable professional standards govern real workflows. [compliant-query-2026, sections I, II and VIII]

Write a practice request for an operative report that names a paired structure but gives conflicting sides in its heading and body. Ask the responsible clinician to clarify the actual side. Do not decide that the heading must be correct simply because it appears first.

Coding and payment answer different questions

A supported code selection does not guarantee coverage or payment. Payer requirements may involve the site of service, medical necessity, benefit rules or other conditions. CMS describes these considerations for Medicare documentation and claims review. [em-cms, pages 21–22]

Keep the general classification question separate from a payer-specific requirement. When you later study Michigan Medicaid, label those rules as Michigan Medicaid rules. Do not rewrite a payer's coverage limitation as though it changes the general meaning of a diagnosis or procedure.

In your notebook, add a payer check only after you have identified the supported service and diagnosis. Record the policy source and effective date when a question requires that layer of analysis.

Worked record: planned work and present evidence

Original fictional office excerpt, September 4, 2026: an adult is seen for left wrist pain. The clinician evaluates the complaint and documents left wrist pain, with a possible tendon condition still under consideration. Imaging is ordered for a later appointment. No imaging interpretation or procedure report is included for today's encounter.

Write the encounter date and outpatient setting. Record the supported symptom and side. Place the possible tendon condition in the uncertainty field. Put the future imaging in the plan field, not the completed-service field.

For diagnosis selection, apply the outpatient certainty rule and investigate the supported symptom. Verify the candidate's complete requirements in the Tabular List. [icd-guidelines, IV.D; IV.H; I.B.1]

This excerpt does not supply enough information to choose an E/M level or report a completed imaging service. That limit is part of the answer. A sound abstraction can identify what remains unavailable instead of filling every worksheet box with an invented conclusion.

Compare two flawed abstractions

Abstraction A says: “Confirmed tendon disease; imaging completed.” It turns uncertainty into certainty and a plan into performed work. Those are two unsupported additions.

Abstraction B says: “Pain, side unknown.” It correctly preserves a symptom but discards the documented left side and wrist site. It loses available specificity.

Your corrected abstraction should preserve the present evidence and its limits. Explain why it is more useful than either alternative before opening a code book. This is the habit that will make later searches faster and more reliable.

Book drill

Find the outpatient certainty instruction in the official ICD-10-CM guidelines. Then locate the rule requiring verification of an index candidate in the Tabular List. Write each section reference beside the point in the worksheet where it matters.

Use the wrist-pain example to investigate a candidate. List any required detail that the record supports and any that remains absent. Keep procedure and E/M selection for a complete service record with the relevant rules available.

Common traps

Do not start with a favorite code. Do not treat every chart phrase as a confirmed diagnosis. Do not convert a planned service into completed work. Do not drop available side or site information. Do not assume that a longer note automatically supports a higher service level or that a code guarantees payment.

Practice

1. Which two facts should appear at the top of the abstraction worksheet?

2. Why should the possible tendon condition remain separate from the established symptom?

3. What prevents reporting the planned imaging as completed work in the example?

Compare your reasoning

1. The service date and care setting, along with the reporting task and responsible service. 2. The outpatient assessment has not established that disease. 3. The excerpt documents an order for later imaging and no completed imaging service for today.

Checkpoint

Produce a short abstraction of the worked record. Identify one certainty rule, one specificity issue and one performed-service boundary. Explain the missing information that prevents a complete service-level selection, then proceed to formal diagnosis navigation.

Sources

1. CMS — Evaluation and Management Services MLN006764. May 2026. Accessed 2026-09-10.
2. CDC/NCHS and CMS — ICD-10-CM April 1 2026 Guidelines. FY2026 April. Accessed 2026-09-10.
3. ACDIS and AHIMA — Guidelines for Achieving a Compliant Query Practice: 2026 Update. August 2026. Accessed 2026-09-10.