Documenting a Dilemma: Inherent vs. Event vs. Effect

To link, or not to link: that is the question for physician documentation

Since the adoption of the ICD-10 code set, clinical documentation integrity specialists (CDISs) have experienced an ongoing dilemma of capturing complication codes with regard to adverse drug events versus ‘known’ or ‘inherent’ side effects.

At our organization, CDISs ask our physicians to add linking verbiage to their documentation for accuracy, which in turn, has a negative impact on their publicly reported scores with complications, and other data. For example, hypokalemia, due to ‘diuretic,’ has a T501x5A code added. Unfortunately, CDISs are caught in the middle. Our clinical documentation integrity (CDI) department is driven by accuracy and truth, however, publicly reported data from ICD-10 codes may indirectly harm our organization and physicians with reportable scores by attributing side effects as something ‘bad’ or ‘unintended consequence.’ 

The accuracy of documenting linkage has an indirect consequence to represent negatively our organization and physicians and the excellent care they provide when these links are made. In turn, it is not our intention to complicate matters for our coding professionals to suggest they not follow their guidelines to capture these diagnoses when linked.

With surgical procedures, the coding guidelines address ‘inherency’ and require the documentation of the surgeon to designate something as a complication or inherent to procedure.  Coding guidelines also direct the coder to query if the documentation is vague.  Should the same criteria apply when it comes to known side effects of medication, where the desired effect may also include known side effects, but the benefit supersedes the harm?  Should we require the physician to deem an ‘adverse drug effect’ as a known side effect when most occasions, it is common occurrence?  Should we ask the physician to ‘exclude’ the linking verbiage? Should they enter ‘as expected’ or should they simply avoid addressing these issues? 

Coding guidelines specify that to justify a coding a complication, it must be clinically evaluated, diagnostically tested, and therapeutically treated; the complication must also result in an extended length of stay in the hospital necessitating increased resources related to care. The condition should not be part of routine care or the routine outcome of an expected procedure.  When it comes to surgery, coders should clarify that there was a complication prior to assigning a complication code. The physician must agree and must document that the condition is a complication.

Should the same criteria apply when it comes to known side effects of medication, where desired effect may also include known side effects, but the benefit supersedes the harm?  Should we require the physician to deem an ‘adverse drug effect’ as a known side effect when most occasions, it is a common occurrence?  Should we ask the physician to ‘exclude’ the linking verbiage? Should they enter ‘as expected’ or should they simply avoid addressing these issues? 

CDISs are caught in between, because we seek truth and accuracy.  However, as clinicians, we do not necessarily consider side effects with the same measurement as ‘catastrophic’ events.  

It is my belief that side effects should have an algorithm or require further clarification as to whether they are inherent or actual severe consequences that resulted in unexpected, untoward events that caused harm and increased both therapeutic measurements and length of stay (LOS).  Most patients who receive diuretics or steroids in the inpatient setting require monitoring and potassium supplements, or insulin for that matter.  It is unfortunate that during hospitalization, this may require capturing an adverse drug event code in the process. 

The same issue is true of addressing ‘leukocytosis’ likely due to steroids while acknowledging that another disease process is going on that may not be infectious. It is through further assessment and lab testing that differential diagnoses may be ruled out.  Should we discourage the physician to address these other issues?

I wonder what other CDI/Coders are experiencing, and if anyone has suggestions?

It is my hope that the utilization of ICD-10 codes for adverse drug events would be reported as they were intended, and that as clinicians, we can differentiate what is considered an ‘adverse’ event versus an inherent side effect, which would be monitored in an inpatient hospital setting along with excellent care.


Program Note:

Listen to Sharon Savinsky report on this topic today on Talk Ten Tuesdays, 10 a.m. EST.

Comment on this article

Facebook
Twitter
LinkedIn

Related Stories

Be Thankful We Can Code That!

Be Thankful We Can Code That!

With Thanksgiving later this week, now is a good time to revisit some codes and coding guidance for which we are thankful for.  Perhaps the

Read More

Leave a Reply

Please log in to your account to comment on this article.

Featured Webcasts

Mastering Principal Diagnosis: Coding Precision, Medical Necessity, and Quality Impact

Mastering Principal Diagnosis: Coding Precision, Medical Necessity, and Quality Impact

Accurately determining the principal diagnosis is critical for compliant billing, appropriate reimbursement, and valid quality reporting — yet it remains one of the most subjective and error-prone areas in inpatient coding. In this expert-led session, Cheryl Ericson, RN, MS, CCDS, CDIP, demystifies the complexities of principal diagnosis assignment, bridging the gap between coding rules and clinical reality. Learn how to strengthen your organization’s coding accuracy, reduce denials, and ensure your documentation supports true medical necessity.

December 3, 2025

Proactive Denial Management: Data-Driven Strategies to Prevent Revenue Loss

Denials continue to delay reimbursement, increase administrative burden, and threaten financial stability across healthcare organizations. This essential webcast tackles the root causes—rising payer scrutiny, fragmented workflows, inconsistent documentation, and underused analytics—and offers proven, data-driven strategies to prevent and overturn denials. Attendees will gain practical tools to strengthen documentation and coding accuracy, engage clinicians effectively, and leverage predictive analytics and AI to identify risks before they impact revenue. Through real-world case examples and actionable guidance, this session empowers coding, CDI, and revenue cycle professionals to shift from reactive appeals to proactive denial prevention and revenue protection.

November 25, 2025
Sepsis: Bridging the Clinical Documentation and Coding Gap to Reduce Denials

Sepsis: Bridging the Clinical Documentation and Coding Gap to Reduce Denials

Sepsis remains one of the most frequently denied and contested diagnoses, creating costly revenue loss and compliance risks. In this webcast, Angela Comfort, DBA, MBA, RHIA, CDIP, CCS, CCS-P, provides practical, real-world strategies to align documentation with coding guidelines, reconcile Sepsis-2 and Sepsis-3 definitions, and apply compliant queries. You’ll learn how to identify and address documentation gaps, strengthen provider engagement, and defend diagnoses against payer scrutiny—equipping you to protect reimbursement, improve SOI/ROM capture, and reduce audit vulnerability in this high-risk area.

September 24, 2025

Trending News

Featured Webcasts

Surviving Federal Audits for Inpatient Rehab Facility Services

Surviving Federal Audits for Inpatient Rehab Facility Services

Federal auditors are zeroing in on Inpatient Rehabilitation Facility (IRF) and hospital rehab unit services, with OIG and CERT audits leading to millions in penalties—often due to documentation and administrative errors, not quality of care. Join compliance expert Michael Calahan, PA, MBA, to learn the five clinical “pillars” of IRF-PPS admissions, key documentation requirements, and real-life case lessons to help protect your revenue.

November 13, 2025
E/M Services Under Intensive Federal Scrutiny: Navigating Split/Shared, Incident-to & Critical Care Compliance in 2025-2026

E/M Services Under Intensive Federal Scrutiny: Navigating Split/Shared, Incident-to & Critical Care Compliance in 2025-2026

During this essential RACmonitor webcast Michael Calahan, PA, MBA Certified Compliance Officer, will clarify the rules, dispel common misconceptions, and equip you with practical strategies to code, document, and bill high-risk split/shared, incident-to & critical care E/M services with confidence. Don’t let audit risks or revenue losses catch your organization off guard — learn exactly what federal auditors are looking for and how to ensure your documentation and reporting stand up to scrutiny.

August 26, 2025

Trending News

Prepare for the 2025 CMS IPPS Final Rule with ICD10monitor’s IPPSPalooza! Click HERE to learn more

Get 15% OFF on all educational webcasts at ICD10monitor with code JULYFOURTH24 until July 4, 2024—start learning today!

CYBER WEEK IS HERE! Don’t miss your chance to get 20% off now until Dec. 1 with code CYBER25

CYBER WEEK IS HERE! Don’t miss your chance to get 20% off now until Dec. 2 with code CYBER24