HIM 540 Module 4 Coding and Compliance Short Paper Example

Same Patients, Different Codes: Governing Coded Data Across Tidewater Crossing's Four Hospitals

[Student Name]

Southern New Hampshire University

HIM 540: Health Information Governance

Module Four Short Paper

[Instructor Name]

[Date]

The organization, setting and figures below are a composite written as a model document. No real employer, client, colleague or patient is described.

Same Patients, Different Codes: Governing Coded Data Across Tidewater Crossing's Four Hospitals

When Tidewater Crossing Health's analytics team compared coded diagnoses across its four hospitals, sepsis stood out. At the largest hospital, 9.4% of adult inpatients carried a sepsis diagnosis; at the smallest, 4.6%. Patient populations differ, but not by that much. The review traced most of the difference to coding and documentation practice: each hospital's clinical documentation and coding teams validated sepsis against a different clinical definition. Coded data like these feed payment, public quality measures, mortality comparisons and research. This paper argues that coding practice is a data governance issue and proposes how the system should govern it.

Why Coded Data Need Governance

Codes were designed for billing, but they now carry much more. They determine diagnosis-related group payments, risk adjustment and the denominators of quality measures, and researchers use them to count disease. O'Malley et al. (2005) showed that coding accuracy depends on every step between the patient's encounter and the final code, including how clinicians document and how coders interpret. When four hospitals take different steps, the system produces data that look comparable but are not. Data governance exists to make shared data mean the same thing everywhere, and coded data are among the most widely used shared data a hospital produces.

The Sepsis Problem

Sepsis shows why definitions matter. The Third International Consensus Definitions, known as Sepsis-3, recast sepsis around organ failure: an infection counts as sepsis when the body's own response to it damages organs badly enough to put the patient's life at risk, displacing earlier criteria that relied on signs of systemic inflammation (Singer et al., 2016). Some payers and hospitals validate sepsis diagnoses against Sepsis-3, others against the older criteria, and federal quality reporting has used definitions of its own. At Tidewater Crossing, the flagship hospital's documentation team queries physicians when older criteria are met, while the smallest hospital accepts sepsis only when organ dysfunction consistent with Sepsis-3 is documented. Both approaches can be defended; using both in one system cannot.

Claims-based counts can also mislead over time. Rhee et al. (2017) compared sepsis identified from clinical data in hundreds of hospitals with sepsis identified from claims and found that claims suggested rising incidence while clinical data showed relatively stable rates, a gap consistent with changes in coding practice rather than in disease. A system that compares its hospitals or tracks its own trends from codes alone may be measuring coding behavior.

Consequences of Inconsistent Coding

The inconsistency matters in several ways. Payment differs, because sepsis as a principal or secondary diagnosis can change the diagnosis-related group. Quality comparisons mislead, because mortality among sepsis patients looks better at a hospital that codes milder cases as sepsis. Compliance exposure grows, since payers increasingly deny sepsis claims on clinical validation grounds and auditors may view aggressive capture as overcoding. And system reports to the board combine incompatible numbers, as the readmission example in Module One already showed for another measure.

What Governance Should Decide

The data governance committee, with the clinical domain steward and the coding leadership of all four hospitals, will recommend four standards to the council. First, one coding policy manual for the system, built on official coding guidelines, replacing four local manuals. Second, one clinical validation standard for high-impact diagnoses such as sepsis, malnutrition and acute respiratory failure, developed with physician leaders and applied the same way at every hospital. Third, one query policy that follows compliant query practice, so that physicians receive the same kinds of questions everywhere. Fourth, one audit program that samples all hospitals equally, measures accuracy for principal and secondary diagnoses and reports results by hospital so variation is visible.

Choosing the Clinical Validation Standard

The choice of sepsis standard will be difficult because it changes payment and reported quality. Governance should make it on clinical and compliance grounds, not financial ones. The recommendation is to validate sepsis against Sepsis-3 organ dysfunction, which reflects current clinical consensus and matches the criteria many payers use when reviewing claims, while continuing to report the federal quality measure using its own specified definition. The committee will document this reasoning and estimate the effect on each hospital's reported sepsis rate before adoption, so leaders are not surprised when the flagship's rate falls.

Bringing Physicians Along

Coding standards depend on documentation, and documentation depends on physicians. The new clinical validation standard will be presented to each hospital's medical staff by physician advisors, not by coders, with examples showing what a note must contain for sepsis to be coded under the system standard: the source of infection, the organ dysfunction and how it relates to the infection. Physicians who trained at different hospitals learned different habits, and some will see the change as a reduction in their patients' documented severity. Explaining that the goal is consistency and defensibility, not lower severity, and showing how payer denials fall when documentation is clear, will help win acceptance.

Testing the Standard First

Before adoption, the committee will apply the proposed standard retrospectively to 200 recent sepsis cases from each hospital, recording how many would still meet the definition and how coding and payment would change. This test will reveal the effect on each hospital before any leader sees a surprising drop, and it will show where documentation, rather than coding, needs to improve.

Measures

Table 1 lists the measures the committee will track.

Table 1. Coded Data Governance Measures

Note. Measures proposed by the author for the data governance committee; composite data.

Conclusion

Coded data are shared data, and shared data need shared definitions. Tidewater Crossing's twofold sepsis difference shows what happens when four hospitals code the same condition four ways. One coding manual, one clinical validation standard, one query policy and one audit program, decided through governance on clinical and compliance grounds, would make the system's coded data mean the same thing wherever they come from.

References

O'Malley, K. J., Cook, K. F., Price, M. D., Wildes, K. R., Hurdle, J. F., & Ashton, C. M. (2005). Measuring diagnoses: ICD code accuracy. Health Services Research, 40(5, Pt. 2), 1620-1639. https://doi.org/10.1111/j.1475-6773.2005.00444.x

Rhee, C., Dantes, R., Epstein, L., Murphy, D. J., Seymour, C. W., Iwashyna, T. J., Kadri, S. S., Angus, D. C., Danner, R. L., Fiore, A. E., Jernigan, J. A., Martin, G. S., Septimus, E., Warren, D. K., Karcz, A., Chan, C., Menchaca, J. T., Wang, R., Gruber, S., & Klompas, M. (2017). Incidence and trends of sepsis in US hospitals using clinical vs claims data, 2009-2014. JAMA, 318(13), 1241-1249. https://doi.org/10.1001/jama.2017.13836

Singer, M., Deutschman, C. S., Seymour, C. W., Shankar-Hari, M., Annane, D., Bauer, M., Bellomo, R., Bernard, G. R., Chiche, J.-D., Coopersmith, C. M., Hotchkiss, R. S., Levy, M. M., Marshall, J. C., Martin, G. S., Opal, S. M., Rubenfeld, G. D., van der Poll, T., Vincent, J.-L., & Angus, D. C. (2016). The Third International Consensus Definitions for Sepsis and Septic Shock (Sepsis-3). JAMA, 315(8), 801-810. https://doi.org/10.1001/jama.2016.0287