ICD-10 code I76: Septic arterial embolism

Key Takeaways

ICD-10 code I76 (Septic arterial embolism) is a billable, specific ICD-10-CM code valid for FY2026 HIPAA-covered claim submissions.

I76 is always an additional code: the underlying infection (endocarditis, bacteremia, sepsis) must be sequenced first as the principal diagnosis.

Documentation must explicitly name the infected embolus, its arterial location, and the causative infection or coding will be unsupported and claims denied.

Pabau’s claims management software helps practices structure ICD-10 coding workflows and reduce claim rejections tied to sequencing errors.

ICD-10 code I76: Definition, billable status, and FY2026 validity

ICD-10 code I76 encodes septic arterial embolism, a serious vascular complication in which infected material travels through the bloodstream and occludes an artery. The condition sits within the I70-I79 block of the ICD-10-CM system maintained by CMS, covering diseases of arteries, arterioles, and capillaries.

For coders managing medical billing compliance, knowing whether a code is billable and currently valid is the first checkpoint before submission.

I76 is a billable and specific ICD-10-CM code. It became effective on October 1, 2025 as part of the FY2026 edition. The code is valid for submission on HIPAA-covered transactions, meaning payers will accept it when the documentation supports the diagnosis. The table below summarizes the key reference data coders need at the point of coding.

Code details at a glance

Clinical information: What causes septic arterial embolism

Septic arterial embolism occurs when infected material breaks off from a primary infection site and travels through the arterial system until it lodges and obstructs blood flow. Unlike bland emboli, the infected fragment carries bacteria or fungi, which can seed the arterial wall and surrounding tissue.

Coders need enough clinical context to assign I76 correctly and verify that the underlying infection is documented. According to the WHO ICD-10 classification, septic embolism as a vascular complication requires the originating infectious process to be the focus of treatment. Common etiologies include:

• Infective endocarditis: Infected vegetations on heart valves (commonly linked to I33.0) are the most frequent source. Fragments dislodge and travel to peripheral or coronary arteries.
• Bacteremia from IV drug use: Intravenous drug use introduces organisms directly into the venous system; right-sided endocarditis then seeds the arterial circulation.
• Central venous catheter infection: Infected thrombus around a catheter tip can embolize when the catheter is manipulated or removed, a risk that IV therapy practices should track closely in catheter-site documentation.
• Osteomyelitis or septic arthritis: Adjacent vascular involvement can generate infected embolic material in severe cases.

The specific underlying infection drives both the clinical and coding workup. A GP practice is often where that infection is first documented, well before any cardiology or infectious disease referral, so capturing it accurately at that visit prevents coding errors downstream.

Approximate synonyms and related terms for ICD-10 code I76

Physicians and coders use several equivalent terms in clinical notes. Any of the following in the medical record points toward I76 when the arterial involvement is confirmed:

• Septic embolism
• Infected embolus
• Septic arterial occlusion
• Bacterial arterial embolism
• Mycotic embolism (when caused by fungal organisms)
• Septicemic embolism

Coders querying a physician should use these terms when clarifying documentation. Searching the AAPC ICD-10-CM code lookup with any of these variants will return I76 as the appropriate code.

Note that septic pulmonary embolism is a distinct and differently coded condition. Pulmonary septic emboli are coded under the pulmonary embolism category (I26), not I76, which is specific to arterial involvement.

Includes and excludes notes

Understanding the includes and excludes notes prevents upcoding and claim edits. I76 carries the following notations per the CDC/NCHS ICD-10-CM tabular list:

The Excludes2 note is particularly important for cardiology and critical care coders. If a patient has both arterial and pulmonary septic emboli, both I76 and the appropriate I26 code can appear on the claim. This is not a conflict; it reflects separate anatomical events arising from the same infection.

Coding guidelines and sequencing rules for I76

Sequencing errors are the primary driver of I76-related claim denials. The code carries an explicit “code first” instruction, meaning it functions as an additional code in every encounter. No clinical scenario permits I76 to be the principal diagnosis.

Follow this sequencing framework for every I76 encounter, consistent with ICD-10-CM Official Guidelines Chapter 1 (Infectious and Parasitic Diseases) and Chapter 9 (Circulatory System), as published by the Centers for Medicare and Medicaid Services:

1. Identify the underlying infection. The Tabular List’s “code first” note names infective endocarditis (I33.0) and lung abscess (J85.-) as the default examples. Sepsis (A41.x), bacteremia (A49.9), or a specific organism code (e.g., A41.01 for MSSA sepsis) are also common underlying causes in practice. Whichever infection is documented becomes the principal diagnosis.
2. Confirm arterial involvement and note the specific site. The record must state that an embolus of infectious origin has lodged in an artery, and name the site (e.g., femoral, popliteal, mesenteric) whenever it’s known – that site drives the additional code assigned in step 5.
3. Assign the infection code first. Place the infectious etiology code in the principal diagnosis field. Do not leave this field blank or default to a symptom code.
4. Assign I76 as an additional diagnosis. Add ICD-10 code I76 in a secondary diagnosis field. It reports the vascular complication of the primary infectious process.
5. Assign the site-specific I74.- code alongside I76. The Tabular List’s “use additional code” instruction requires a code from category I74.- whenever the arterial site is documented – it supplements I76, it does not replace it.
6. Add any relevant organ-specific codes. If the septic embolus causes a downstream complication (e.g., ischemic stroke, limb ischemia), code those conditions separately in additional fields per the relevant ICD-10-CM chapter guidelines.

Documentation requirements for accurate I76 coding

A clean claim for I76 depends on four documentation elements. Missing any one of them creates a basis for denial or a clinical validity audit. Coders working with digital intake forms and structured clinical records can flag incomplete documentation before claims are submitted rather than after.

• Named infection: The record must identify the infectious source (organism, infection type, or anatomical site of origin). “Sepsis” without further detail will support A41.9 but may not fully substantiate the causation chain for I76.
• Causal relationship: Language connecting the infection to the arterial embolism is critical. Phrases such as “septic embolism from infective endocarditis” or “infected thrombus embolizing to the femoral artery” provide the causal link needed.
• Arterial location: I76 has no site-specific sub-codes of its own, but the Tabular List’s “use additional code” note means a documented arterial site should drive assignment of the matching I74.- code alongside I76, not just “strengthen specificity.”
• Treatment focus: Documentation should confirm that the infection, not the embolism in isolation, is the condition chiefly responsible for the encounter. This supports the “code first” sequencing instruction.

Practices that track HIPAA security rule requirements alongside documentation completeness reduce their audit exposure significantly. Incomplete records are a dual liability: they create coding risk and leave the legal health record incomplete.

Keep ICD-10 coding accurate across every encounter

Pabau's claims management and clinical documentation tools help practices capture the documentation needed for complex codes like I76, reducing denials and rework on infectious disease and vascular coding.

Book a demo

Common coding errors and how to avoid claim denials

Practices with strong coding compliance processes catch these errors at the documentation review stage rather than at the remittance stage. Building a pre-submission checklist that mirrors the five errors above removes most I76 denial risk.

Related ICD-10 codes

I76 appears on claims alongside several related codes, either as co-diagnoses (coding both conditions when they genuinely coexist) or as the underlying infection code that must be sequenced first. The table below covers the most commonly paired codes, drawn from the ICD-10-CM code reference and standard cardiology coding guidance.

For coding scenarios involving other circulatory system diagnoses, coders can cross-reference Pabau’s guide to I15.2. The same sequencing principles covered here apply outside the circulatory system too, as shown in the M60.9 coding guide.

How Pabau supports accurate ICD-10 coding in clinical practice

No code reference page replaces a documentation-first workflow. The most common source of I76 denials is not coder error – it is incomplete physician documentation that reaches the coding desk without the causal language needed to justify the code. Pabau’s claims management software is built to solve that problem by keeping documentation and billing in the same structured workflow.

In clinical settings where I76 applies, Pabau’s AI-powered clinical documentation captures structured consultation notes that flag diagnostic terms and treatment relationships at the point of care. This reduces the post-encounter query burden on coders.

Practices focused on HIPAA-compliant documentation workflows can configure structured note templates that prompt physicians for the specific causal language I76 requires. The result is a cleaner record before the claim is built, rather than a physician query after the denial.

For practices managing complex infectious disease or cardiology coding, clinical documentation tools that integrate with billing workflows reduce the handoff errors that create sequencing mistakes. Pabau’s EHR integration for billing accuracy connects documentation fields directly to claim generation, so the principal diagnosis and additional codes are populated from the clinical record rather than re-entered manually.

Conclusion

ICD-10 code I76 is a billable, specific FY2026 code for septic arterial embolism. It will only survive payer scrutiny when the underlying infection is named, sequenced first, and the causal relationship between that infection and the arterial embolism is documented explicitly. Sequencing errors and missing documentation are the two failure points that drive the majority of denials on this code.

Pabau’s claims management and documentation platform helps practices build the documentation habits that keep complex codes like I76 off the denial queue. To see how Pabau structures ICD-10 workflows for infectious disease and cardiology encounters, book a demo.

Continue your research

Need a simple way to track patient medications alongside complex diagnoses? Daily medication chart template gives practices a free, structured format for logging dosing changes.

Wondering how drug administration codes pair with a primary diagnosis? Pabau’s guide to J0640 walks through billing leucovorin calcium injections alongside the correct diagnosis code.

Need to sequence anesthesia codes correctly alongside a diagnosis? Pabau’s guide to 01991 covers billing anesthesia for diagnostic and therapeutic nerve block procedures.

Frequently asked questions