ICD-10 code S36.230D: Laceration of head of pancreas, subsequent encounter

Key takeaways

S36.230D is a billable ICD-10-CM code for laceration of head of pancreas, unspecified degree, subsequent encounter, valid for FY 2026 reimbursement.

In the S36.2 pancreas codes, the 5th character sets the degree of injury and the 6th character sets the part of the pancreas. A minor laceration of the head is S36.240, not S36.231.

The 7th character D is required. Without it, parent code S36.230 is non-billable and claims are rejected.

‘Subsequent encounter’ means the patient is receiving routine care during the healing phase. It does not mean the injury has recurred.

Practice management software like Pabau helps trauma-coding teams flag a missing 7th character before submission, which cuts denials from incomplete codes.

ICD-10 code S36.230D is a billable code for a laceration of the head of the pancreas, unspecified degree, at a subsequent encounter. The D suffix marks follow-up care during the healing phase. Parent code S36.230 carries no 7th character, so it is not valid for billing on its own.

S36.230D is valid for fiscal year 2026 billing under CMS ICD-10 coding guidelines. It sits within category S36 (injury of intra-abdominal organs), subcategory S36.2 (injury of pancreas), and subgroup S36.23 (laceration of pancreas, unspecified degree). The 6th character 0 is what narrows the code to the head of the pancreas.

How to read an S36.2 pancreas code: Degree, part, and encounter

An S36.2 laceration code carries three separate pieces of information, and each sits at a fixed position. The 5th character records the degree of the injury. The 6th records which part of the pancreas was torn. The 7th records the encounter type.

Read S36.230D from left to right. The 3 means the degree was never documented. The 0 means the head of the pancreas. The D means a follow-up visit during the healing phase.

Change the 5th character and the degree changes while the location stays put. S36.240D is a minor laceration of the head, and S36.260D is a major one.

Change the 6th character instead and the location moves. S36.231D is a laceration of the body, and S36.232D is one of the tail. Treating the 6th character as a severity step puts the right degree on the wrong part of the organ. Wrong-code claims in this family usually come from reading the digits in that order.

The 7th character D: What subsequent encounter means

In category S36 the 7th character is what makes a code billable. S36.230 with no suffix is a non-billable placeholder in the ICD-10-CM tabular list. Three valid 7th characters exist for this code, and each describes a distinct phase of care. Choosing the wrong one triggers a denial just as reliably as omitting it.

The distinction between A, D, and S is grounded in the CDC ICD-10-CM guidelines, Section I.C.19.a. “Subsequent encounter” does not mean the patient was injured again. It means the patient is receiving routine or follow-up care while the original injury heals. That covers any visit after the initial acute treatment phase has concluded.

7th character options for S36.230

D applies throughout the healing phase, which can span multiple visits and providers. A surgical follow-up three weeks after discharge still uses D. The A suffix ends when active treatment of the original injury concludes. Claims management software that flags an incomplete or mismatched 7th character before submission prevents a large share of avoidable rejections.

Clinical description: Laceration of the head of the pancreas

The pancreas has three anatomically distinct regions. Those are the head, the body, and the tail. In S36.230D the 6th character 0 identifies the head, which sits in the curve of the duodenum.

The head is the segment most commonly injured in blunt abdominal trauma, particularly from steering-wheel or handlebar compression. The same mechanism turns up in collision and cycling injuries seen by sports medicine practices. A laceration of the body or the tail changes that 6th character and nothing else.

“Unspecified degree” in S36.230D describes what the record failed to state, not a clinical finding. ICD-10-CM grades pancreatic lacerations at three levels above unspecified. For the head of the pancreas those are S36.240 (minor), S36.250 (moderate), and S36.260 (major).

Coders fall back on S36.230 only when the operative or imaging report does not characterize severity. If the note does grade the laceration, a more precise code exists and should be used. Structured intake and assessment workflows cut how often “unspecified” is the default, as these clinical documentation practices show.

• Head of pancreas: Sits in the retroperitoneal space within the duodenal loop. An injury here can involve the main pancreatic duct, the bile duct, or the duodenum at the same time.
• Mechanism: Most often blunt abdominal trauma, such as a motor vehicle collision, a handlebar injury, or a direct blow. Penetrating trauma is less common.
• Unspecified degree: The record does not grade the laceration as minor, moderate, or major, so the 5th character stays 3.
• Subsequent encounter scope: Covers outpatient follow-up, wound checks, drain management, monitoring of amylase and lipase levels, and post-surgical rehabilitation visits.

Where S36.230D sits in the ICD-10-CM hierarchy

S36.230D sits at the bottom of a seven-level tree that starts with the injury chapter S00-T88. Each level narrows the description, and only the last one is billable. Knowing the tree makes it easier to find the sibling code that fits the record you have.

The AAPC code lookup walks the same tree, from the broad injury chapters down to billable subcodes. Coding at the category level alone is never enough for claim submission. Other intra-abdominal injury codes follow the identical pattern, including S37.893D.

Documentation requirements for a subsequent-encounter claim

Billing S36.230D on a subsequent encounter needs physician documentation on two points. The first is anatomical specificity, meaning the head of the pancreas rather than the body or the tail. The second is encounter type, meaning follow-up or healing-phase care rather than initial acute treatment.

Missing either element creates an audit vulnerability even if the claim processes successfully. The note should name the organ injured and its region, the nature of the injury, and the degree if known. It also needs language showing this is a follow-up visit rather than first treatment.

“Patient returns for wound check following surgical repair of pancreatic laceration” satisfies the subsequent encounter requirement. “Post-op day 14 check after pancreatic debridement” does too. Practices using clinical documentation workflows built around encounter type reduce ambiguity while the note is still being written.

• Organ specified: Documentation must name the pancreas, not just “abdominal organ injury”.
• Anatomical region: The head, body, or tail distinction sets the 6th character, so the note must state it.
• Injury type: The word “laceration” must appear, not contusion, hematoma, or unspecified injury.
• Degree if available: Record whether the laceration was minor, moderate, or major, because that sets the 5th character.
• Encounter type: Language indicating follow-up, routine healing care, or post-procedure monitoring rather than initial presentation.
• Provider documentation: The physician note must support the code. Coder assignment alone is not enough without clinical documentation.

Digital intake forms built around abdominal injury categories capture the region and the encounter type at the point of care. That leaves far less to clarify weeks later, when the patient and the note have both moved on. HIPAA recordkeeping rules require these specifics in the patient record before the claim goes out.

Common coding errors and how to avoid them

Four errors account for most rejected S36.230D claims. Three of them sit in the 7th character, and the fourth sits in the 6th.

Error 1: Using S36.230A beyond the initial treatment phase. The A suffix applies only while the patient is receiving active treatment for the injury. Once the acute phase ends and the patient moves to follow-up care, the correct code is S36.230D.

Coders sometimes keep using A for post-surgical follow-up visits because the original record used it. The same switch is required across trauma categories, including the delayed-healing characters in S52.033J.

Error 2: Confusing D (subsequent encounter) with S (sequela). This is the distinction most frequently misapplied in trauma coding. D applies when the patient is still healing from the original injury and receiving routine care for it. S applies when the original injury has resolved and the patient now presents with a complication caused by it.

Pancreatic fistula, exocrine insufficiency, and stricture are the usual examples. If the patient is still recovering from the laceration itself, use D. The same A/D/S logic governs pelvic trauma codes such as S33.4XXD.

Error 3: Submitting the non-billable parent code. S36.230 with no 7th character is non-billable, and any claim carrying it will be rejected. Some practice management systems populate the parent code from templates and need a manual override to add the suffix.

Check that your billing workflow enforces 7th character completion before submission. Practices using secure clinical data management platforms can set required-field validation so an incomplete code never reaches the claim queue.

Error 4: Reading the 6th character as a severity level. In S36.2 the 6th character names the part of the pancreas, and the 5th names the degree. Coding a documented minor head laceration as S36.231D puts a body-of-pancreas code on a head injury. The correct code is S36.240D.

Both are billable and both sit in the S36.2 family. The claim can clear front-end edits and still misstate the injury site.

Related ICD-10-CM codes for pancreatic laceration

S36.230D is one of many billable codes in the S36.2 pancreas family. Which one fits depends on two details the record either states or omits. Those are the degree of the laceration and the part of the pancreas involved. The table below covers the codes most likely to appear alongside or instead of S36.230D.

Injury-specific documentation templates reduce the risk of defaulting to the wrong anatomical subcode. Rehabilitation providers inherit the same D character on every healing-phase visit, so physical therapy software needs the original injury detail on file.

Cross-reference the official CDC ICD-10-CM tabular list before finalizing any S36 code. The check earns its keep when the operative note describes the injury by organ region rather than in ICD-10 wording.

Billing and reimbursement considerations

A billable code is not automatically a paid code. Payers check that the 7th character matches the encounter, and that the note supports healing-phase care rather than active treatment. S36.230D on the same date as an emergency department procedure code invites a review.

Do not replace S36.230D with an aftercare Z code. The ICD-10-CM Official Guidelines direct coders to report the acute injury code with the 7th character D for injury aftercare. Aftercare Z codes cover other conditions, not the follow-up care of an injury.

External cause codes from Chapter 20 explain how the injury happened. Where your payer or state requires them, the external cause code carries its own 7th character. That character has to match the injury code, so a subsequent-encounter claim pairs with a subsequent-encounter external cause code.

When a claim is rejected on the 7th character, the fix is a corrected claim rather than a fresh one. Confirm the service date falls inside the healing phase, then resubmit with D replacing the A character.

Track how often that correction is needed. A recurring pattern usually points at a template that autofills the encounter character.

How Pabau supports pancreatic trauma coding and claim accuracy

Most S36.230D errors start in the note, not in the claim. If the record never says which part of the pancreas was torn, the coder has to guess at the 6th character.

If it never frames the visit as follow-up care, the 7th character is a guess too. Retrospective queries then eat days the billing cycle does not have.

Practice management software like Pabau closes that loop at the point of care. Treatment note templates can be built per encounter type. A post-operative review then captures the region, the graded degree, and the healing-phase language in one form.

Digital intake and consent forms feed straight into the client record. The injury history then stays in one place across every follow-up visit.

Because records, notes, invoicing, and reporting sit on one platform, a coder can see the full encounter history before assigning a character. Reporting then shows which templates produce queries and which produce clean claims. The outcome is fewer corrected claims and less time spent chasing detail that should have been captured at the visit.

Catch trauma coding errors before submission

Pabau's claims tools help surgical practices spot a missing 7th character, a mismatched encounter type, or a thin note before submission. See how it works for your team.

Book a demo

Conclusion

S36.230D is a fallback code, and treating it as the default is what costs practices money. Reach for it only when the report genuinely does not grade the laceration. When the grade is there, the 5th character carries it and the claim describes the injury properly.

The 7th character is worth one final check before every submission. Use D through the healing phase, A only during initial active treatment, and S once a late complication appears. Building that check into the note template beats catching it in a denial letter three weeks later.

Pabau’s claims management software supports pre-submission checks that flag an incomplete or mismatched trauma code before it reaches the payer. Book a demo to see how it fits your clinical and billing workflows.

Continue your research

Need the A-versus-D call on a laceration? S41.021A works through the initial-encounter side of the same 7th character decision.

Seeing another intra-abdominal laceration at follow-up? S37.893D applies the same subsequent-encounter logic to urinary and pelvic organs.

Coding a nerve injury in the same trauma episode? S34.5XXA shows how placeholder X characters sit alongside the encounter character.

Need the D character on a pelvic trauma code? S33.4XXD covers follow-up visits after a traumatic rupture of the symphysis pubis.

Billing the wound preparation as well as the diagnosis? CPT code 15005 sets out the add-on rules for surgical preparation of a wound bed.

Frequently asked questions