HIM 360 Module 4 Project One Example

Reviewed by Delia Ravenscroft, MSN, RN

This HIM 360 Module 4 Project One sample investigates whether a hospital's poor mortality score reflects its care or its coding. It is written for SNHU HIM 360 (HIM-360), where the opening project for BS Health Information Management students turns coding rules on the data behind quality rankings. The composite 480-bed academic medical center's risk-adjusted mortality ratio of 1.14 suggests more deaths than expected. The project explains how the ratio is calculated, reviews 120 inpatient deaths against the full record for missing diagnoses, present-on-admission errors, status codes and principal diagnosis problems, estimates the ratio after correction and separates documentation problems from cases that deserve clinical peer review. It closes with recommendations and limits.

CourseHIM 360 Coding and Classifications Systems II
ModuleModule 4
Paper typeundergraduate project reviewing coded data behind a hospital mortality ratio
LengthAbout 1,040 words, 6 pages
FormatAPA 7 student paper
SchoolSouthern New Hampshire University
ProgramBS Health Information Management
UpdatedSeptember 2026

Free sample paper for HIM 360 Module 4

1

Project One: Care Problem or Data Problem? A Mortality Coding Review at Juniper Health

[Student Name]

Southern New Hampshire University

HIM 360: Coding and Classifications Systems II

Project One

[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.

What this page is doingThe title states the question the review sets out to answer.
2

Project One: Care Problem or Data Problem? A Mortality Coding Review at Juniper Health

Juniper Health's risk-adjusted mortality ratio of 1.14 means that 14% more patients died than a statistical model predicted for patients with the same recorded characteristics. The ratio affects public rankings, referrals and the board's confidence in clinical quality. Before leaders act on it, they need to know how much reflects care and how much reflects incomplete or inaccurate data. This project answers that question for the past twelve months.

What this page is doingThe introduction explains the stakes and the question.
3

How the Ratio Works

A mortality ratio divides observed deaths by expected deaths. Expected deaths come from a model that estimates each patient's risk of dying from age, sex, the principal diagnosis, secondary conditions present on admission and sometimes procedures and status codes. Pine et al. (2007) showed that models become considerably more accurate when present-on-admission indicators separate conditions patients arrived with from those that developed later. The model can only count what is coded: a condition missing from the claim, or wrongly marked as hospital-acquired, lowers expected deaths and raises the ratio.

What this page is doingThe calculation and its dependence on coded data are explained.
4

Review Methods

Two reviewers, a credentialed coder and a documentation integrity nurse, independently examined all 120 inpatient deaths from the past year. For each case they read physician notes, nursing and dietitian documentation, consults, laboratory results and orders, then compared findings with the final codes. They looked for clinically supported conditions not coded, present-on-admission indicators that conflicted with the record, missing do-not-resuscitate and palliative care codes and principal diagnosis selection errors. Disagreements were resolved by the coding manager.

What this page is doingThe review methods are described.
5

Finding 1: Conditions Documented but Not Coded

In 37 of 120 deaths, 31%, reviewers found at least one clinically significant condition documented by nurses, dietitians or consultants but not stated by the attending physician in a way coders could use. The most common were severe malnutrition identified by dietitians, chronic respiratory failure on home oxygen and encephalopathy described by neurology consultants. Official guidelines allow some details, such as pressure injury stage and body mass index, to be coded from other clinicians' documentation, but the underlying diagnosis must come from a provider. These gaps require physician documentation, not coding changes.

What this page is doingUndocumented conditions are quantified.
6

Finding 2: Present-on-Admission Errors

Among 1,064 secondary diagnoses in the 120 records, 96, or 9%, carried present-on-admission indicators that conflicted with the record, most often conditions marked N or U when emergency department notes showed them on arrival. Meddings et al. (2010) found that documentation and coding problems kept hospital-acquired catheter infections from being captured accurately; the reverse problem appears here, with conditions present at arrival wrongly counted as hospital-acquired, which lowers expected risk and can create false hospital-acquired condition flags.

What this page is doingPresent-on-admission errors are quantified with research.
7

Finding 3: Missing Status Codes

Of 86 patients with a documented do-not-resuscitate order, 15, or 17%, lacked Z66, do not resuscitate. Of 72 patients who received palliative care consultation, 16, or 22%, lacked Z51.5, encounter for palliative care. Several risk models use these codes, and their absence makes deaths among patients who chose comfort care appear unexpected.

Table 1. Review Findings, 120 Deaths

FindingCountShare
Deaths with a documented but uncoded significant condition37 of 12031%
Secondary diagnoses with conflicting POA indicator96 of 1,0649%
DNR documented but Z66 missing15 of 8617%
Palliative consult but Z51.5 missing16 of 7222%
Principal diagnosis selection error4 of 1203%

Note. Review by the author's team; disagreements resolved by the coding manager.

What this page is doingMissing status codes are quantified, and Table 1 summarizes all findings.
8

Finding 4: Principal Diagnosis Selection

In four cases, reviewers judged the principal diagnosis inconsistent with guidelines, for example a symptom sequenced first when a definitive diagnosis was documented. Principal diagnosis drives the risk model's baseline, so even a few errors matter. All four were reviewed with the coders involved and corrected.

What this page is doingPrincipal diagnosis errors are described.
9

What the Ratio Might Be

The analytics team reran the risk model after applying corrections that were supported by existing documentation: fixing present-on-admission indicators, adding missing Z66 and Z51.5 codes and correcting the four principal diagnoses. The ratio fell from 1.14 to about 1.07. Adding the uncoded conditions would require physician documentation and cannot be done retroactively without a compliant query; modeling them hypothetically suggested a further drop to about 1.03. Even under the most favorable assumptions, the ratio stays above 1.0.

What this page is doingThe recalculated ratio is reported with caveats.
10

Separating Data From Care

Because the ratio remains above expected, not all of the gap is a data problem. Reviewers flagged six deaths with possible care concerns, such as delayed recognition of deterioration, for referral to physician peer review. Rosen et al. (2012) found that safety indicators based on coded data often misclassify events, which is why chart review, not codes alone, should drive clinical conclusions. The review's purpose was accuracy, and accuracy revealed both documentation gaps and cases that deserve clinical attention.

What this page is doingCare concerns are separated from data problems.
11

What Physicians Said

The team shared de-identified examples with the hospitalist and critical care groups. Physicians were surprised that a dietitian's malnutrition assessment could not be coded unless they documented the diagnosis themselves, and several said they had assumed the dietitian note was enough. Others noted that do-not-resuscitate orders were entered as orders but rarely restated in notes. Their reactions suggest that simple education and templates could close many gaps, and that physicians support accuracy when they understand how the data are used.

What this page is doingPhysician responses to the findings are described.
12

Recommendations

Four actions follow. Route every inpatient death to a documentation integrity review before final coding, checking status codes, present-on-admission indicators and principal diagnosis. Train physicians on documenting conditions identified by dietitians and consultants, especially malnutrition and chronic respiratory failure, when they agree with the finding. Build a nursing flowsheet prompt that alerts the attending when a dietitian documents severe malnutrition. And refer care concerns identified in reviews to peer review routinely.

What this page is doingRecommendations are made.
13

Limitations

The review examined only deaths, so it cannot show whether survivors' records have similar gaps that would also raise expected risk. The recalculated ratio used the hospital's internal replica of the ranking model, which may differ from the official version. And reviewers' judgments about clinical significance involve some subjectivity, reduced but not eliminated by dual review. O'Malley et al. (2005) noted that measuring coding accuracy requires attention to such sources of error in the review process itself.

What this page is doingLimitations are acknowledged.
14

Conclusion

About half of Juniper Health's excess mortality ratio appears to reflect correctable data problems: conflicting present-on-admission indicators, missing status codes and undocumented conditions. The rest points to cases worth clinical review. Accurate coding does not erase quality problems; it lets the organization see them clearly.

What this page is doingThe conclusion summarizes.
15

References

Meddings, J., Saint, S., & McMahon, L. F. (2010). Hospital-acquired catheter-associated urinary tract infection: Documentation and coding issues may reduce financial impact of Medicare's new payment policy. Infection Control & Hospital Epidemiology, 31(6), 627-633. https://doi.org/10.1086/652523

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

Pine, M., Jordan, H. S., Elixhauser, A., Fry, D. E., Hoaglin, D. C., Jones, B., Meimban, R., Warner, D., & Gonzales, J. (2007). Enhancement of claims data to improve risk adjustment of hospital mortality. JAMA, 297(1), 71-76. https://doi.org/10.1001/jama.297.1.71

Rosen, A. K., Itani, K. M. F., Cevasco, M., Kaafarani, H. M. A., Hanchate, A., Shin, M., Shwartz, M., Loveland, S., Chen, Q., & Borzecki, A. (2012). Validating the patient safety indicators in the Veterans Health Administration: Do they accurately identify true safety events? Medical Care, 50(1), 74-85. https://doi.org/10.1097/MLR.0b013e3182293edf

What the HIM 360 Module 4 instructions ask for

HIM 360 Project One usually asks you to review coded data behind a quality measure, severity score or payment outcome and explain what you find. Plan on 1,500 to 1,900 words with tables and at least four peer-reviewed sources in APA 7. Explain how the measure uses coded data, describe your review method, quantify findings by category and estimate their effect where you can. Separate data problems from possible care problems, recommend compliant fixes and acknowledge the limits of your sample and methods. State the sample size, the review period and who performed the second review, because graders judge a project's findings by the strength of the method that produced them.

How this HIM 360 Module 4 project one example is built

The project explains how a mortality ratio depends on coded conditions and present-on-admission indicators, citing Pine and colleagues. Dual review of 120 deaths finds uncoded conditions in 31%, conflicting POA indicators on 9% of secondary diagnoses, missing Z66 in 17% and Z51.5 in 22% and four principal diagnosis errors, with Meddings and colleagues framing POA problems. Corrections lower the ratio from 1.14 to about 1.07, six cases go to peer review in light of Rosen and colleagues and recommendations and limitations drawing on O'Malley and colleagues follow. The project's tables show each category of error with its count and share, so a reader can see which corrections move the ratio most and which reflect genuine documentation gaps rather than coding mistakes.

Where the HIM 360 Module 4 rubric puts the points

Coded data review projects in HIM 360 are commonly graded on accurate explanation of the measure, sound review methods, clear quantification of findings, compliant corrections, separation of data from care issues, practical recommendations and APA 7 mechanics. The strongest projects correct only what the record supports, model hypothetical changes transparently and refer possible care problems rather than explaining them away. Graders reward dual review, clear tables and honest limitations. Credit also goes to projects that report how many records were reviewed, how disagreements between reviewers were settled and why the corrected ratio is an estimate rather than a final figure.

HIM 360 Module 4 help: the mistakes that cost points

These projects lose points when they treat a quality measure as something to improve by coding more, add diagnoses not documented by providers, skip present-on-admission accuracy or ignore the possibility of real care problems. Another frequent gap is failing to explain how the measure uses codes. Explain the measure, review systematically, quantify, correct compliantly, separate data from care and state limits. If your prompt focuses on a different measure, such as a readmission or safety indicator, send it with your HIM 360 notes. Include the measure's specification or your facility's report if you have them, and the project can model corrections with the same categories, tables and referral rules used in this Juniper Health sample.

Get HIM 360 Module 4 written to your instructions

Forward the HIM 360 Project One instructions and the measure or data you are reviewing. Expect a project that explains how the measure uses codes, reviews records systematically, quantifies findings, applies only compliant corrections and separates data problems from possible care issues, within 24 to 48 hours, free the first time. The paper above is an original model document written by our desk, not a submitted student paper and not an official Southern New Hampshire University document.

More HIM 360 papers and related BS Health Information Management samples

HIM 360 Module 4 questions, answered

Where can I find a free HIM 360 Module 4 Project One sample?

HIM 360 Project One appears in full: 120 deaths reviewed for missing diagnoses, POA errors and status codes behind a mortality ratio.

What is a risk-adjusted mortality ratio?

Observed deaths divided by the deaths a model expected given patients' coded characteristics; above 1.0 means more deaths than expected.

Why do Z66 and Z51.5 matter in mortality reviews?

They record do-not-resuscitate status and palliative care, which some risk models use to set expected mortality.

Can coders add diagnoses documented only by dietitians or nurses?

Some details, like pressure injury stage and BMI, may come from other clinicians, but the diagnosis itself must be documented by a provider.

Does a better mortality ratio after coding review mean care is fine?

Not necessarily; remaining excess deaths and flagged cases may still indicate care problems needing peer review.