Laboratory Values and Test Results for Medical Coders

Laboratory results are woven throughout clinical documentation, and while coders do not interpret labs the way a clinician does, understanding what a lab value represents — and what counts as abnormal — is essential for following the clinical reasoning behind a diagnosis. A physician’s assessment often references specific lab findings as justification for a diagnosis, and recognizing those values helps a coder confirm that the documented diagnosis is supported and that no additional, unaddressed abnormal finding has been left uncoded. This guide walks through the lab panels coders encounter most frequently, what their components measure, and how lab data connects to diagnosis coding. For the underlying disease mechanisms these values reflect, see Pathophysiology for Medical Coders, and for the shorthand these results are often recorded in, see Medical Abbreviations Coders Must Know.

Why Lab Value Literacy Matters for Coding

Lab results function as supporting evidence within the medical record. A diagnosis of anemia, for example, is expected to be accompanied by a low hemoglobin or hematocrit value; a diagnosis of acute kidney injury is expected to be accompanied by an elevated creatinine or a falling glomerular filtration rate. When a coder recognizes these expected value ranges, two things become possible: confirming that a documented diagnosis is clinically supported, and noticing when an abnormal lab result appears in the chart without a corresponding diagnosis, which may indicate a condition the provider evaluated but did not explicitly state — a pattern that generally warrants a provider query rather than independent coding from the lab value alone, since coders cannot diagnose from lab data independently.

Consider a discharge summary that lists a potassium level of 6.2 mEq/L (well above the normal range) but the assessment section never mentions hyperkalemia. A coder who does not recognize that 6.2 is a critically elevated potassium value would simply pass over the number. A coder who does recognize it will notice the gap between the lab data and the documented diagnosis list, and know to query the provider rather than either ignoring the finding or coding hyperkalemia without physician documentation to support it.

Complete Blood Count (CBC)

The complete blood count is one of the most frequently ordered lab panels and measures the cellular components of blood.

A low hemoglobin and hematocrit together generally support a diagnosis of anemia, and the degree of reduction often corresponds to documentation of anemia severity, which can affect code specificity. An elevated white blood cell count is one of the criteria clinicians use when evaluating a patient for sepsis, discussed further in Sepsis Coding Guidelines.

Basic and Comprehensive Metabolic Panels (BMP/CMP)

The metabolic panel measures electrolytes, kidney function, and (in the comprehensive version) liver enzymes.

Creatinine and eGFR are the values most directly tied to the chronic kidney disease staging framework described in Renal and Urinary System Anatomy — a falling eGFR corresponds to advancing CKD stage, which affects code selection within the N18 category.

Lipid Panel

Liver Function Tests (LFTs)

Thyroid Panel

TSH typically moves in the opposite direction of the thyroid hormones themselves, since it reflects the pituitary gland’s response to thyroid hormone levels — a detail covered in more depth in Endocrine System and Diabetes Coding.

Diabetes-Related Values

The A1c value is particularly important because it reflects sustained glucose control rather than a single moment in time, which is why it is used both to diagnose diabetes and to determine whether a patient’s diabetes is well-controlled or poorly controlled for documentation purposes.

Urinalysis (UA)

Cardiac and Coagulation Markers

Beyond the routine panels above, two additional categories of lab values appear frequently in emergency and inpatient documentation.

Troponin in particular is worth recognizing on sight: a rising troponin level in a patient with chest pain is one of the defining pieces of evidence a provider uses to confirm a myocardial infarction rather than a lesser diagnosis such as unstable angina, and the distinction materially changes which diagnosis code is appropriate.

Inflammatory and Infection Markers

These markers are useful precisely because they are broad rather than specific — an elevated CRP or ESR tells a clinician that an inflammatory process is present, but not which one. Coders should expect these values to appear alongside a more specific diagnosis rather than standing in as a diagnosis on their own, since “elevated CRP” alone does not identify a codable condition without additional documentation clarifying its cause. Procalcitonin’s greater specificity for bacterial infection makes it a value increasingly documented when a provider is deciding whether antibiotic therapy is warranted, which can appear in the same clinical picture as the sepsis workup discussed below.

Reading Trends, Not Just Single Values

A single lab value in isolation tells only part of the story. Clinicians — and by extension, coders reading their documentation — often care as much about the trend of a value over time as its single reading. A creatinine that has climbed steadily over several inpatient days points toward acute kidney injury developing during the admission, while a creatinine that is elevated but stable across multiple prior visits is more consistent with chronic kidney disease. Recognizing whether documentation is describing a single abnormal snapshot or a meaningful trend helps a coder correctly distinguish between an acute condition, a chronic condition, or an acute process layered on top of a chronic one — a distinction that frequently changes which combination of codes applies.

Critical Values and Sepsis Indicators

Certain lab findings are flagged by laboratories as “critical values” because they represent results requiring immediate clinical attention. Coders encountering critical value notations in a chart should expect to see a corresponding clinical response documented — treatment, closer monitoring, or transfer of care — since a critical, unaddressed value in isolation is not something a coder should code independently.

Lactate is a particularly important value in the context of sepsis: an elevated serum lactate reflects tissue hypoperfusion and is one of the clinical markers used to help identify septic shock, alongside persistent hypotension. Coders working with sepsis documentation benefit from recognizing elevated lactate and elevated white blood cell count together as findings that typically accompany — and support — a sepsis or septic shock diagnosis.

How the CPC Exam Tests Lab Value Knowledge

Pattern 1 — Connecting Lab Values to Diagnosis Severity

The scenario presents a lab value alongside a diagnosis and asks you to recognize what severity or stage that value corresponds to, such as a specific creatinine or eGFR level indicating a particular CKD stage.

Pattern 2 — Recognizing Supporting Evidence for a Diagnosis

Questions may present a set of lab findings and ask you to identify which diagnosis they support, testing your ability to connect abnormal values to their corresponding clinical condition.

Pattern 3 — Distinguishing Similar Lab Panels

The exam may test whether you can distinguish between similarly named panels or values, such as a basic versus comprehensive metabolic panel, or hemoglobin versus hemoglobin A1c.

Pattern 4 — Recognizing When a Lab Value Alone Is Not Codable

A scenario may present an abnormal lab value without an accompanying documented diagnosis, testing whether you understand that coders generally cannot assign a diagnosis code based on a lab value alone without provider documentation connecting the two.

Common Mistakes

Coding a diagnosis directly from an abnormal lab value. Coders generally cannot diagnose a condition from a lab result alone; the diagnosis must be documented by the provider, even when the underlying lab value clearly supports it.

Confusing similarly named values. Hemoglobin and hemoglobin A1c measure very different things despite the similar name — one reflects current oxygen-carrying capacity, the other reflects average blood sugar over months. Confusing these can lead to significant coding errors.

Overlooking severity indicators tied to lab values. Many conditions have codes that vary by severity, and severity is often determined by lab values (such as CKD stage by eGFR). Missing the lab value can mean missing the correct level of code specificity.

Assuming all abnormal values require additional coding. Not every abnormal lab result rises to the level of a reportable condition; clinical significance and provider documentation both matter, not just an out-of-range number.

Missing the connection between critical values and clinical response. When a critical value appears in documentation, look for the corresponding clinical action taken, since that response often clarifies the full diagnostic picture.

Frequently Asked Questions