Coding reviews are generally conducted to identify coding errors, omissions, and compliance concerns. However, a thorough coding review can reveal much more. It can uncover opportunities for greater coding specificity, identify gaps in provider documentation, and bring attention to clinical information that may have been overlooked during the original coding process. In some cases, these findings may also affect Diagnosis-Related Group (DRG) assignment.
The challenge is that a medical record may contain clinical information supporting a more specific diagnosis or procedure code, but that information may not be readily apparent, may reside in an unexpected location within the electronic health record (EHR), or may require additional provider clarification before it can be used for coding.
The following are examples of opportunities identified through coding reviews that illustrate why looking beyond coding errors can be valuable.
Opportunities for Greater Coding Specificity
Wound Documentation: More Than Just a “Wound”
Wounds are a frequent source of insufficient documentation and missed coding specificity. The simple term “wound” provides little information about the underlying condition, and often results in an unspecified code or the need for clarification.
Accurate wound coding requires documentation of the specific anatomical location, wound type, and underlying etiology, whenever possible. Wounds may be classified as pressure injuries, non-pressure chronic ulcers, venous stasis ulcers, or traumatic wounds, each with different coding requirements.
For pressure ulcers, documentation of the stage is essential for assigning the most specific code. Non-pressure chronic ulcers require documentation of severity, such as whether the ulcer involves breakdown of the skin or exposure/necrosis of deeper tissues, including fat, muscle, or bone.
Frequently, a wound care nurse has assessed the patient and documented the wound’s location, characteristics, measurements, and stage or severity. However, this information may not be reflected in the treating physician’s documentation.
An important distinction is that official coding guidelines permit certain details, including pressure ulcer stage and non-pressure chronic ulcer depth, to be obtained from documentation by qualified clinicians other than the patient’s provider. The diagnosis and the site itself generally must be established by the appropriate provider.
This creates an opportunity for clinical documentation integrity (CDI) specialists and coders to recognize that a wound care evaluation has been performed, review the available documentation, and determine whether additional provider clarification is necessary.
It also provides an opportunity to educate physicians about documenting wound etiology, and the importance of incorporating relevant findings from wound care assessments into their clinical documentation.
Deep Vein Thrombosis: Identifying the Specific Vessel
Another frequently overlooked opportunity involves the documentation of deep vein thrombosis (DVT).
A physician may document simply that the patient has DVT, without identifying the affected vessel. However, a lower-extremity venous Doppler ultrasound report may provide much greater anatomical specificity.
For example, the report may identify thrombosis involving the femoral, popliteal, or tibial veins: information that could support assignment of a more specific diagnosis code.
Coders should review the diagnostic report carefully and determine whether the documented findings support additional specificity under applicable coding guidelines. If the physician’s diagnosis is unclear or conflicts with the diagnostic interpretation, clarification may be necessary.
The important lesson is that coders should not overlook the clinical information contained in other reports simply because the treating physician’s progress note uses a more general diagnosis.
Amputation Procedures: Determining the Level
Amputation procedures provide another example in which anatomical specificity is essential for accurate coding.
Under ICD-10-PCS, the Detachment root operation requires selection of the appropriate body part and qualifier to identify the level of amputation. Depending on the anatomical site, qualifiers may distinguish between high, mid, and low levels.
Operative reports sometimes describe the amputation using measurements from anatomical landmarks, rather than terminology that directly corresponds to ICD-10-PCS definitions.
For example, the surgeon may document that a lower-leg amputation was performed “3 cm below the tibial tuberosity.” Although this provides a physical measurement, it may not clearly establish whether the detachment occurred at the high, mid, or low level, as defined by ICD-10-PCS.
When the operative documentation does not permit a definitive determination, a physician query may be required.
This example illustrates how documentation can be clinically meaningful, yet still lack the specific information necessary for accurate procedure code assignment.
Missed Opportunities That May Affect DRG Assignment
While greater coding specificity is important, certain documentation deficiencies can have a more direct effect on DRG assignment. These opportunities may involve secondary diagnoses, diagnosis sequencing, or inpatient procedure coding.
Preexisting Conditions That Continue to Receive Treatment
A condition does not have to develop during hospitalization to qualify as a reportable secondary diagnosis.
Patients frequently enter the hospital with preexisting conditions that continue to require treatment, evaluation, monitoring, or other clinical management during the admission.
For example, a patient may be admitted for one condition while receiving active treatment for another significant diagnosis that existed before admission. If the secondary diagnosis meets inpatient reporting criteria, it may be coded, even though it was not the principal reason for hospitalization.
Some of these diagnoses may qualify as complications or comorbidities (CCs) or major complications or comorbidities (MCCs), potentially affecting DRG assignment.
A thorough coding review should therefore consider not only conditions that developed during the hospitalization, but also preexisting conditions that were clinically significant and managed during the stay.
The opportunity is not to code every condition appearing in the patient’s history, but to identify those that meet the criteria for reporting and may have been overlooked.
Drainage and Repair Procedures: Depth Matters
Procedure coding represents another potential source of missed DRG opportunities, particularly when the operative or procedural documentation lacks sufficient detail regarding the depth of the procedure.
For drainage procedures, the specific anatomical site and body part involved may determine the appropriate ICD-10-PCS code. For repair procedures, the structures involved and the nature of the work performed may influence selection of the appropriate root operation and body part.
Consider a patient who sustains a traumatic wound that is sutured in the emergency department before inpatient admission.
The documentation may describe the procedure simply as a laceration repair. However, additional details may reveal that the repair involved subcutaneous tissue or deeper structures.
Depending on the circumstances, those details could change the inpatient procedure code and potentially affect DRG assignment.
An important consideration is that the procedure must meet applicable inpatient procedure reporting criteria. Not every emergency department repair or minor procedure will affect DRG assignment.
The broader lesson is that the anatomical depth and nature of the procedure should be evaluated, rather than assuming that all wound repairs or drainage procedures are equivalent.
Diabetes With Skin Complications: Recognizing Relationships and Sequencing
Patients with diabetes frequently develop skin and soft-tissue conditions, including cellulitis.
When a diabetic patient is admitted with cellulitis or another skin complication, the relationship between diabetes and the condition may have important coding implications.
Certain conditions are presumed to be related to diabetes under ICD-10-CM’s “with” convention when they are linked in the Alphabetic Index or Tabular List, unless the documentation clearly establishes that the conditions are unrelated. Other relationships may require provider clarification.
Correctly identifying a diabetic complication can influence code assignment and sequencing – and, depending on the circumstances, may affect DRG assignment.
CDI specialists and coders should review these cases carefully, ensuring that the clinical documentation supports the diagnoses and that the applicable coding conventions and sequencing instructions are followed.
This is particularly important when the patient’s skin condition is the focus of the hospitalization, but diabetes is also being actively managed.
Traumatic Versus Pathological Fractures: Understanding the Cause
Fracture documentation presents another opportunity for greater specificity and potentially different DRG assignment.
A fracture may be traumatic, resulting from an injury, or pathological, occurring in bone weakened by an underlying disease process.
Pathological fractures may be associated with osteoporosis, neoplasms, or other conditions affecting bone integrity.
Documentation that merely states “fracture” may not provide sufficient information to establish the appropriate classification. Even when a fall or other minor trauma is documented, the underlying clinical circumstances may warrant further evaluation.
CDI specialists should identify situations in which clinical findings suggest that clarification of the fracture’s underlying cause may be appropriate.
The physician’s documentation should establish whether the fracture is traumatic or pathological – and, when pathological, identify the underlying condition.
Because the classification of the fracture influences diagnosis code selection and may affect sequencing and DRG assignment, this distinction deserves careful attention during coding reviews.
Postoperative Conditions: Complication or Expected Outcome?
Not every condition that arises after surgery represents a postoperative complication.
Patients may experience findings or conditions that are expected consequences of a surgical procedure or part of the normal postoperative course. Other conditions may represent clinically significant complications requiring additional treatment, monitoring, or intervention.
For example, postoperative anemia, respiratory insufficiency, or other conditions may be documented following surgery without clearly establishing whether they represent expected postoperative changes or complications of care.
The fact that a condition developed after surgery does not by itself establish a cause-and-effect relationship or justify coding it as a complication.
Coding guidelines require documentation supporting the relationship between the condition and the care or procedure, as well as its clinical significance, unless the classification provides other instructions.
When the documentation is unclear, CDI specialists may need to query the provider to clarify the relationship and determine the appropriate classification.
This distinction is particularly important because the assignment of a postoperative complication code may affect DRG assignment, reported quality measures, and assessments of patient outcomes.
Looking Beyond the Codes
These examples illustrate an important point: a coding review can identify opportunities that extend well beyond correcting coding errors.
In some cases, the original coder may have assigned the correct code, based on the information available in the record. However, more complete documentation or careful review of additional clinical information could have supported a more specific code – or an entirely different coding outcome.
These findings also provide valuable opportunities for physician education, CDI improvement, coding education, and EHR workflow refinement.
When the same documentation deficiencies occur repeatedly, healthcare organizations should consider whether the problem reflects an individual documentation practice or a broader system issue. For example, EHR templates may not prompt physicians to identify wound etiology, document amputation levels, or distinguish expected postoperative conditions from complications.
Addressing such issues can improve documentation at the point of care, rather than relying entirely on retrospective queries and coding reviews.
Ultimately, the objective is not simply to increase reimbursement. It is to ensure that coded data accurately reflects the patient’s clinical conditions, the services provided, and the resources required to deliver care.
The next time a coding review identifies no significant coding errors, it may be worth asking a different question:
Were the codes correct, or were there codes that could have been?

















