Coding vs. Clinical Validation

Understanding Distinct Roles, Responsibilities, and Qualifications in Healthcare Documentation

Two critical functions are often misunderstood or conflated: medical coding and clinical validation. While both are essential to accurate documentation, appropriate reimbursement, and regulatory compliance, they are fundamentally different disciplines that require distinct skill sets, credentials, and areas of expertise. Confusing these roles—or allowing one professional to perform both functions without proper qualifications—can expose healthcare organizations to significant compliance risk, audit vulnerability, and potential fraud and abuse liability.

Medical Coding Role, Responsibilities, and Scope
A medical coder’s job is to accurately translate what the physician has documented into the appropriate codes. Coders are bound by a core principle: they may only code what is documented. They do not interpret clinical findings, draw clinical conclusions, or make determinations about whether a diagnosis is clinically present. Their role is to read the documentation and assign codes that reflect exactly what the provider has written. They apply official coding guidelines (ICD-10-CM Official Guidelines, AHA Coding Clinics, CPT Assistant); select diagnoses, and procedure codes and query physicians when documentation is incomplete, ambiguous, or conflicting—without leading the provider toward a specific answer.

Most coders hold credentials such as: CPC (Certified Professional Coder), CCS (Certified Coding Specialist),  or  CIC (Certified Inpatient Coder). These credentials are earned through examination and require demonstrated knowledge of anatomy, physiology, pathophysiology, pharmacology, coding guidelines, and medical terminology. However, coders  do not hold clinical licensure and have not received training in clinical decision-making or the interpretation of physiologic data.

Clinical Validation: Role, Responsibilities, and Scope

Clinical validation is the process of reviewing the medical record to determine whether a documented diagnosis is supported by the clinical evidence. It answers a fundamentally different question than coding: not “Has the physician documented this diagnosis?” but rather “Does this patient actually have this condition based on clinical criteria, signs, symptoms, test results, and treatment?”

Clinical validation is a clinical function, not a coding function. It requires someone with the training to interpret clinical data, understand disease pathophysiology, evaluate the appropriateness of diagnostic criteria, and make judgments about whether documentation accurately reflects the patient’s clinical condition.

A clinical validator reviews the entire medical record—not just the physician’s attestation or the final diagnosis—and evaluates whether the clinical evidence supports the coded or documented condition. This involves examining laboratory values, vital signs, imaging results, medication records, nursing notes, consult reports, and the overall clinical picture.

Clinical validation requires a clinical license and advanced clinical training. The professional performing clinical validation must be able to interpret clinical data independently, apply diagnostic criteria, and make clinical judgments. This is not a function that can be delegated to someone without clinical training, regardless of their coding expertise.

Professionals who perform clinical validation typically hold one or more of the following:

Registered Nurse (RN), CCDS (Certified Clinical Documentation Specialist, ACDIS) or CDIP (Clinical Documentation Improvement Practitioner, AHIMA), a physician, an Advanced Practice Provider (NP or PA), and a pharmacist (PharmD).

The key requirement is clinical licensure and the ability to make independent clinical judgments based on a review of clinical data. A credential in coding alone does not confer this ability, regardless of how experienced or knowledgeable the coder may be.

The Coder’s Role in HCC
In HCC coding, the coder reviews encounter documentation and assigns ICD-10-CM codes that capture the patient’s active, chronic, and significant conditions, not just the reason for the visit. Coders must ensure that all chronic conditions being managed or monitored are coded to the highest level of specificity, and that HCC-eligible diagnoses are captured when they are documented by the provider. However, the coder’s role in HCC is identical to their role elsewhere: they code what is documented.

HCC Coding and Clinical Validation
HCC programs are at high-risk area for overcoding—either through assumption coding, upcoding, or the submission of diagnoses that are not genuinely supported by the clinical record. This is where clinical validation becomes critically important. A clinical validator reviews whether the condition that has been coded (or is being considered for coding) actually meets the clinical criteria for that diagnosis, independent of what the physician may have written. This is not the coder’s job, and it requires clinical expertise that coders are not trained to apply.

DRG Determination: The Coder’s Role and the Clinical Validator’s Role

Diagnosis-Related Groups (DRGs) are the classification system used under the Medicare Inpatient Prospective Payment System (IPPS) to determine hospital reimbursement for inpatient admissions. Each DRG carries a specific relative weight that, combined with the hospital’s base rate, determines the payment for a given hospitalization. The DRG is driven by the coded diagnoses and procedures—specifically, the principal diagnosis, major comorbidities and complications (MCCs), comorbidities and complications (CCs), and significant procedures.

What the Coder Does in DRG Assignment
A coder with inpatient expertise must understand DRG logic, know which diagnoses qualify as MCCs and CCs, understand the impact of OR procedures on DRG assignment, and ensure that all conditions that meet the criteria for secondary diagnosis coding are captured. Experienced inpatient coders often hold the CCS or CIC credential, which specifically tests inpatient coding knowledge.

However—and this is the critical point—the coder can only assign codes for diagnoses and procedures that are documented by the provider. The coder determines which codes to assign; the DRG is then a product of those codes. The coder does not determine whether a diagnosis is clinically present.

What the Clinical Validator Does in DRG Determination
A clinical validator—in the context of DRG work, often a CDI specialist or physician advisor—reviews the coded record to assess whether the diagnoses driving the DRG are clinically supported. This is particularly important for diagnoses that serve as MCCs or CCs, which can shift the DRG to a significantly higher-paying group.

This is especially relevant in the context of payer denials and RAC (Recovery Audit Contractor) audits, where reviewers—who are typically clinicians—evaluate whether documented diagnoses are clinically supported. A diagnosis that was coded accurately (because the physician documented it) but is not clinically defensible can result in DRG downgrades, recoupment, and compliance exposure.

Common conditions that are subject to clinical validation in the DRG context include: sepsis and severe sepsis (and whether the clinical criteria, such as qSOFA or SIRS criteria plus suspected infection, are documented and clinically supported); encephalopathy and its type (metabolic, toxic, hypoxic); malnutrition and its severity; acute respiratory failure; acute kidney injury; pressure injuries and their staging; and protein-calorie malnutrition.

The Physician Query Process
Some may argue that a coder can simply query the physician when they believe documentation doesn’t support a code—and that this solves the clinical determination problem. While physician queries are indeed an appropriate tool for both coders and CDI specialists when documentation is ambiguous or incomplete, they are not a substitute for clinical validation. A query asks the provider to clarify their documentation; it does not independently assess whether a diagnosis is clinically present. Moreover, a query written by someone without clinical training may be leading, incomplete, or clinically inappropriate, which is a compliance risk. Clinical validators are trained to write queries that are compliant, non-leading, and clinically grounded.

The Collaborative Model: Coders and Clinical Validators Working Together

The most effective and compliant documentation integrity programs use coders and clinical validators as collaborative partners, not interchangeable roles. In a typical inpatient CDI program, clinical documentation specialists (CDSs) who are clinicians—review records concurrently during the patient stay, identifying documentation opportunities and querying providers in real time. After discharge, coders assign the final codes based on the completed record. Post-coding, a physician advisor or CDI specialist may perform a retrospective clinical validation review, particularly for high-risk diagnoses, DRG outliers, or cases flagged for payer scrutiny.

This model ensures that clinical determinations are made by clinicians, coding determinations are made by coders, and both functions are performed by professionals with the appropriate training and authority. It also provides a defensible compliance structure: if a payer or auditor questions a diagnosis, the organization can demonstrate that the code was assigned based on documented provider attestation, that the documentation was reviewed for clinical support by a licensed clinician, and that appropriate queries were issued when needed.

Conclusion

The distinction between coding and clinical validation is a fundamental division of professional responsibility rooted in scope of practice, training, accountability, and compliance. Coders bring essential expertise in translating documentation into codes and navigating the complex landscape of coding guidelines, DRG logic, and HCC risk adjustment. Clinical validators bring clinical expertise in evaluating whether that documentation is accurate, complete, and supported by the evidence in the record.

Neither function can substitute for the other. Organizations that rely on coders to perform clinical validation—or that fail to establish robust clinical validation programs—are exposed to audit risk, compliance vulnerability, and potential liability. Conversely, organizations that invest in qualified clinical validators working alongside skilled coders create a documentation integrity infrastructure that is both accurate and defensible.

As payer scrutiny intensifies, RAC audit activity increases, and value-based payment models place greater weight on coded diagnoses, the importance of getting these roles right has never been greater.