| Course | HI253 Medical Coding I |
|---|---|
| Unit | Unit 4 |
| Paper type | Case coding set |
| Length | About 860 words, 6 pages double-spaced |
| Format | APA 7 student paper |
| School | Purdue University Global |
| Program | BS in Health Information Management |
| Updated | October 2026 |
Free sample paper for HI253 Unit 4
Every Character Earned From the Record: A Unit 4 Case Coding Set Carrying Eight Composite Scenarios to the Last Character the Documentation Supports, With the Phrase Behind Each One
[Student Name]
Purdue University Global
HI253: Medical Coding I
Unit 4 Case Coding Set
[Instructor Name]
[Date]
The scenarios are composite; the code entries and the sources cited are real and follow the FY 2026 ICD-10-CM.
Ground Rules Applied
Two guideline principles govern every answer. Codes are reported to the highest number of characters available, and a code missing a required character is invalid. Equally, a coder may not add detail the documentation does not contain; specificity has to be earned from the record (National Center for Health Statistics, 2025). For injuries, the seventh character describes the phase of care. A marks active treatment, D marks a subsequent encounter during healing and S marks a sequela; a visit to check healing after treatment is complete is D even if it is the first time that clinician has seen the patient.
Scenario 1
A composite 15-year-old fell from a skateboard three weeks ago and had a closed reduction of a Colles fracture of the right radius in the emergency department. Today's orthopedic visit is a cast check; X-rays show routine healing. Code: S52.531D, seven characters. S52.53 identifies a Colles fracture; the sixth character 1 comes from "right radius"; the seventh character D comes from "cast check" and "routine healing" after active treatment ended.
Scenario 2
A composite 62-year-old with type 2 diabetes is seen for follow-up. The physician writes that the diabetes has damaged the kidneys, records chronic kidney disease at stage 3b, and lowers the metformin dose because of the reduced filtration. Codes: E11.22, five characters, from "type 2 diabetes" and the statement that it damaged the kidneys; and N18.32, five characters, from "stage 3b," because the tabular entry at E11.22 asks for a second code naming the stage. The combination code captures the cause; the second code captures the stage. Neither alone carries what the physician wrote.
Scenario 3
A composite patient at 32 weeks of gestation has new blood pressure readings above 140/90 on two visits, no proteinuria and no history of hypertension. The obstetrician diagnoses gestational hypertension, a diagnosis reserved for blood pressure that first rises in the second half of pregnancy with no protein in the urine and no signs of preeclampsia (American College of Obstetricians and Gynecologists, 2020). Codes: O13.3, four characters, gestational hypertension without significant proteinuria, third trimester; the final character comes from "32 weeks," which falls in the third trimester. Z3A.32, five characters, from the same phrase, reports the weeks of gestation.
Scenario 4
A composite 70-year-old reports two years of worsening pain in the left knee. The physician diagnoses primary osteoarthritis of the left knee; the right knee is normal. Code: M17.12, five characters. M17.1 identifies unilateral primary osteoarthritis of the knee, and the final character 2 comes from "left knee."
Scenario 5
A composite cook cut the right index finger on a knife at work today. There is no foreign body and the nail is not involved; the wound is closed with sutures. Code: S61.210A, seven characters. S61.21 identifies a laceration without foreign body of a finger without damage to nail; the sixth character 0 comes from "right index finger"; A comes from active treatment today. External cause codes may also be required where the section's instructions put them in scope.
Scenario 6
A composite 4-year-old has two days of ear pain and fever. The pediatrician documents acute suppurative otitis media of the right ear, tympanic membrane bulging but intact, first episode. Code: H66.001, six characters, acute suppurative otitis media without spontaneous rupture of ear drum, right ear; "intact" supplies the without-rupture element and "right ear" the final character. The fever is integral to the diagnosis and is not coded separately.
Scenario 7
A composite 34-year-old with mild persistent asthma presents with wheezing after a cold. The physician documents mild persistent asthma with acute exacerbation and prescribes a short course of oral steroids. Code: J45.31, five characters, from "mild persistent" and "with acute exacerbation."
Scenario 8, the Thin Record
A composite urgent care note reads: "Ankle pain after a misstep, X-ray negative, ice and rest advised." No side is recorded, and no diagnosis beyond pain is given. Code: M25.579, pain in unspecified ankle and joints of unspecified foot. This is the correct answer for the note as written, because the record does not say which ankle. A query to the provider asking which ankle was examined would allow M25.571 or M25.572. Choosing a side to make the code look complete would be an error, not an improvement.
Summary of Character Counts
Of the ten codes assigned, one has four characters, five have five, two have six and two have seven. Each length is the length the record supports, and the thin record shows that a shorter, unspecified code can be the right one. Studies of coding accuracy find that lost specificity is one of the most common kinds of disagreement between coders and reviewers, which is why each character above is tied to a phrase (O'Malley et al., 2005).
References
American College of Obstetricians and Gynecologists. (2020). Gestational hypertension and preeclampsia (ACOG Practice Bulletin No. 222). Obstetrics & Gynecology, 135(6), e237-e260. https://doi.org/10.1097/AOG.0000000000003891
National Center for Health Statistics. (2025). ICD-10-CM official guidelines for coding and reporting FY 2026. Centers for Disease Control and Prevention.
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(5p2), 1620-1639. https://doi.org/10.1111/j.1475-6773.2005.00444.x
HI253 Unit 4 instructions, in plain terms
The fourth unit typically gives five to ten short scenarios and asks for each code carried to its full character length. You are expected to read each note for site, side, episode of care, stage, trimester or cause and to explain which phrase justified each added character. Fractures and injuries often appear because the seventh character for initial, subsequent or sequela encounters trips up new coders. Some prompts include a scenario where the documentation is incomplete and ask what the coder should do. Others want combination codes and any additional codes a tabular note requires. Most instructors expect a brief rationale under every code rather than a bare list, and a citation to the current guidelines. A few sections ask for a character count or a short summary at the end.
How this HI253 Unit 4 example is built
The set opens with ground rules: report all the detail the record documents and none it does not, and treat the seventh character as a phase of care rather than a date. Each of the eight scenarios then follows the same pattern of note, code, character count and supporting phrase. Scenario 2 carries a highlighted line explaining why one code captures the cause and a second captures the stage. Injury scenarios show placeholders and seventh characters, and the pregnancy scenario shows the trimester taken from the weeks of gestation. Scenario 8 is labeled the thin record and explains why choosing a side to complete the code would be an error. A closing summary tallies the code lengths and ties lost specificity to published accuracy findings.
Reading the HI253 Unit 4 grading rubric
Rubrics here are usually row by row, with points for the correct code and further points for the rationale that ties characters to the record. Full credit tends to require the right seventh character and any placeholder, because an incomplete code is invalid regardless of how close it is. Instructors also reward combination codes used where the classification provides them and second codes added when a note calls for one. The thin scenario, if your set has one, is often weighted heavily, since it tests whether a student will stop rather than invent. Clear explanations and consistent formatting carry a smaller share, as does an APA reference to the current guidelines. Answers that list codes without any reasoning commonly lose a third or more of the available points.
HI253 Unit 4 help from the desk
The seventh character is where this unit costs the most points: students mark a cast check as an initial encounter because it is the patient's first visit to that provider. Others leave out the placeholder X and submit a code that will not validate. A third error runs the other way, adding laterality or a stage that the note never mentioned in order to make the code longer. Missing the second code that a tabular note requires, such as a stage after a combination code, also costs credit. Brief rationales that only restate the code description earn little. We can code your own scenarios with the phrase behind each character and a note wherever the record falls short. Send the scenarios, the edition your course uses and the format your instructor expects.
Get an HI253 Unit 4 example written to your instructions
Scenarios differ from section to section, so share yours from Unit 4, the instructions, the rubric and the edition year of the code set. If some scenarios carry more weight than others, say which. The set returns with a character count and a supporting phrase beside every answer, ready in 24-48h, and the first custom sample is free. The paper above is an original model document written by our desk, not a submitted student paper and not an official Purdue University Global document.
More HI253 papers and BS in Health Information Management samples
- HI253 Unit 1: Discussion Post
- HI253 Unit 2: Index and Tabular Exercise
- HI253 Unit 3: Convention Application
- HI253 Unit 5: Chapter Specific Problem Set
- HI253 Unit 6: Sequencing Exercise
- HI253 Unit 7: Physician Query Letter
- HI253 Unit 8: Seminar Reflection
- HI253 Unit 9: Coding Accuracy Review
- HI253 Unit 10: Full Record Coding Case
- HI230 Unit 4: Occupancy Rate Worksheet
- HI215 Unit 4: Claim Form Exercise
- HI150 Unit 4: Master Patient Index Exercise
- HI135 Unit 4: Privacy Notice Comparison
HI253 Unit 4 questions, answered
Why does a cast check use a different seventh character than the day of injury?
Because the character describes the phase of care, not the calendar. The day of reduction is active treatment. A later visit to check healing is a subsequent encounter even if it is the first time that particular provider has seen the patient. The sample defines this before the injury scenarios because many wrong answers on this unit trace back to it.
Is a longer code always a better code?
Only when the record supports every character. Specificity means reporting all the detail the documentation provides, and inventing detail to fill a position is an error in the other direction. The thin scenario in this set exists to show that limit. Its answer is correct precisely because it stops where the note stops, and a query is named as the route to anything more.
Do scenarios in this unit ever need more than one code?
Often. Combination codes cover some pairs of conditions in a single entry, but a tabular note may still require a second code for detail the combination leaves out, such as a stage or an organism. External cause codes may also be expected on injury scenarios in some sections, and the instructions usually say whether they are in scope for your set.
Where can I find a free HI253 Unit 4 sample paper?
The finished Unit 4 case coding set is on this page. Eight composite scenarios are coded to full length, each with its character count and supporting phrase, including one thin record.
What should I do when a scenario does not give enough detail for a full code?
Code what the record supports, which may be an unspecified entry, and state that a query to the provider would be needed for more. Inventing a side or stage to complete the code is marked as an error.