2.2 Provider Documentation Source Hierarchy and Authorship

The chart is evidence, not a scavenger hunt

A common abstraction error is treating every phrase in the record as equally codeable. Health records contain patient statements, triage impressions, nursing observations, copied problem lists, diagnostic test findings, consultant opinions, operative descriptions, and final attending diagnoses. CCS-level coding requires a hierarchy. The coder asks who documented the statement, what role that author has, whether the statement is final or provisional, and whether official guidance allows that source to establish the data element.

Provider documentation generally drives diagnosis coding. Providers include physicians and other qualified practitioners who are legally accountable for diagnosing and treating the patient within their scope. A nurse may document shortness of breath, oxygen saturation, wound drainage, or patient-reported home medication use. Those observations are important clinical indicators, but they usually do not independently establish a diagnosis such as acute respiratory failure, postoperative infection, or long-term insulin use unless the applicable coding rules allow the data element from that source.

The source hierarchy is not a rigid page order. The best source depends on the coding question. For principal diagnosis selection in an inpatient record, the discharge summary, final progress notes, operative reports, and the full course of care are critical because the diagnosis is selected after study. For a procedure code, the operative report or procedure note normally outranks a brief discharge summary mention because it contains approach, body part, device, objective, and technique.

For a pathology-dependent diagnosis, the pathology report may supply essential test results, but many code assignments still require provider interpretation or incorporation into the final diagnosis.

Practical source hierarchy

Authorship matters because the coder is not the clinician. If the ED provider documents probable pneumonia and the inpatient attending later documents acute systolic heart failure after study, the inpatient coder cannot ignore the final attending diagnosis just because pneumonia was the first impression. If a consultant documents malnutrition and the attending never addresses it, facility policy and payer expectations may require the diagnosis to be adopted by the attending or otherwise clearly documented by a provider responsible for the patient's care. The coder should not manufacture agreement from silence.

Conflicting documentation requires a disciplined response. A progress note may say acute kidney injury resolved, while the discharge summary lists chronic kidney disease only. An operative report may state excisional debridement in the body of the note while the title says irrigation and debridement. A radiology report may identify a fracture while the provider assessment lists sprain. In each case, the coder compares source strength, timing, clinical indicators, and whether the conflict affects code assignment. If the record remains unclear, a compliant query is appropriate.

Conflict resolution checklist

• Identify the exact conflicting terms, not just the general topic.
• Determine whether the conflict affects code assignment, sequencing, DRG, APC, quality reporting, medical necessity, or modifier use.
• Compare authorship: attending, operating surgeon, consultant, ED provider, resident, ancillary clinician, or automated import.
• Compare timing: initial impression, intraoperative finding, final diagnosis, amended report, discharge summary, or late addendum.
• Compare clinical indicators: treatment, monitoring, test results, medications, procedures, response, and discharge plan.
• Query when the documentation remains ambiguous, inconsistent, incomplete, or clinically unsupported for the code being considered.

A compliant query does not ask the provider to agree with a desired code. It presents relevant clinical indicators and asks for clarification using neutral options, including an option such as unable to determine when appropriate. The coder may ask whether a documented condition was ruled in, ruled out, clinically insignificant, or better described by another diagnosis, but the query should not lead the provider toward the highest-paying or most severe answer.

Ancillary documentation still matters. Laboratory values can support a query for acute blood loss anemia when the provider documents postoperative anemia without specificity and the patient received transfusion. Medication administration records can support whether insulin, antibiotics, anticoagulants, or thrombolytics were actually given. Nursing notes may show wound care intensity, oxygen delivery, intake and output, neuro checks, or patient education. These details help prove that a condition was evaluated, monitored, or treated, but they are not a substitute for required provider diagnosis language.

Copy-forward documentation is another CCS trap. A problem list may carry history of sepsis for months. A medication list may include metformin even if the patient is admitted for appendicitis and diabetes is not addressed. A templated review of systems may deny chest pain while the assessment says unstable angina. The coder must distinguish active provider assessment from stale imported text. When copied content conflicts with current care, the coder should rely on current, authenticated, clinically coherent documentation or query when needed.

The record also contains signatures, amendments, and authentication. Unsigned or unauthenticated notes may not meet facility or payer requirements for final code support. Late entries and addenda can be valid when properly authenticated and clinically coherent, but the coder should understand facility policy and payer rules. A final signed operative report added after an initial brief op note may clarify root operation, device, and approach. The key is not speed. The key is defensible authorship tied to the exact code element being abstracted.