ICD code Y62.2 – Sterile precaution failure during dialysis or perfusion

Key takeaways

Y62.2 is a billable ICD-10-CM external cause code for a sterile precaution failure during kidney dialysis or other perfusion.

It is never the principal diagnosis, so the complication it caused, such as T82.7XXA or T85.71XA, is listed first.

A sterile break during an IV infusion or a blood transfusion belongs to Y62.1, not Y62.2.

A dialysis complication with no documented misadventure takes Y84.1 instead of Y62.2.

The provider must document the breach, the dialysis or perfusion procedure, and the link to the complication.

ICD-10 code Y62.2 flags a sterile break during dialysis

ICD-10 code Y62.2 is the billable ICD-10-CM code for failure of sterile precautions during kidney dialysis and other perfusion. It is an external cause code, so it explains how a complication happened rather than naming the complication. The code is valid for the current fiscal year in the CDC/NCHS ICD-10-CM browser tool.

Both halves of the descriptor need support in the record. “Failure of sterile precautions” means a documented break in aseptic technique, such as an unscrubbed catheter hub or a touch-contaminated connection. “Kidney dialysis and other perfusion” limits the code to hemodialysis, peritoneal dialysis, and other perfusion procedures.

The tabular list gives no examples of “other perfusion,” and the Alphabetic Index simply sends “perfusion” to Y62.2. The procedure named in the provider’s note therefore decides the code.

Y62.2 sits in the misadventure block

The table below collects the reference data for Y62.2. Check it against the current tabular list before you submit a claim, because the code set updates every October 1.

The procedure picks the Y62 code

Category Y62 splits sterile precaution failures by the procedure that was underway. Dialysis patients make the wrong sibling easy to pick, because they often have several procedures in one week. The table maps every code in the category.

Timing is what separates the dialysis codes. A breach during the dialysis session itself points to Y62.2. A breach while a dialysis catheter was being placed reads as a catheterization under Y62.6, and one during fistula surgery reads as Y62.0. Confirm the procedure in the provider’s note rather than inferring it from the patient’s diagnosis.

An injection or a vaccination given in the unit falls under Y62.3 instead. The decision path below follows a documented breach to its code.

Y62.9 is a last resort. When the record clearly describes a dialysis session, assigning Y62.9 is a specificity error that invites audit questions.

Where Y62.2 shows up in a dialysis unit

Y62.2 applies when three facts are documented together. The provider records a sterile precaution failure, the failure happened during dialysis or another perfusion procedure, and a resulting complication is coded first.

Typical scenarios that meet that bar:

• A hemodialysis nurse connects a tunneled catheter without scrubbing the hub, and the patient develops a catheter infection. The provider links the two, so the infection codes come first and Y62.2 follows.
• A patient on peritoneal dialysis has a touch contamination during an in-center exchange and develops peritonitis. The provider documents the break, so T85.71XA and the peritonitis code precede Y62.2.
• A technician cannulates an arteriovenous graft without completing the skin prep, and the access site becomes infected. The provider ties the infection to that session, which supports T82.7XXA with Y62.2.

An infection found days later with no documented breach does not qualify. When dialysis caused a complication but no misadventure is recorded, Y84.1 describes it instead. Coders cannot infer a sterile failure from lab results or clinical signs alone.

The complication code always goes first

Because Y62.2 is an external cause code, it always follows a code for the condition it caused. These are the codes most often sequenced ahead of it, with their official descriptors from the tabular list.

Each T-code above carries a “use additional code” note, so the specific infection, such as sepsis or peritonitis, is coded as well. Y62.2 then closes the sequence.

The Alphabetic Index sends infection of a vascular dialysis catheter to T82.7, while T80.211A covers central line bloodstream infections. AHA Coding Clinic has addressed hemodialysis central line infections more than once, so check its latest advice before choosing.

Four sequencing rules decide the claim

Section I.C.20 of the ICD-10-CM Official Guidelines governs external cause codes, including Y62.2. Four rules matter on a dialysis claim:

1. Never a principal diagnosis. External cause codes cannot be the first-listed code, and a claim that lists Y62.2 first will be rejected.
2. The complication comes first. The infection or other complication code leads, and Y62.2 follows as an additional code.
3. The provider documents the link. A complication of care needs a documented cause-and-effect relationship, and coders do not infer it.
4. Reporting may be voluntary. There is no national requirement to report external cause codes, but state mandates and payer policies can require them.

The CMS ICD-10-CM Official Guidelines are updated every fiscal year. Use the edition that matches the date of service.

Three notes make Y62.2 stick

A Y62.2 claim holds up on audit when the record shows three things. Missing any one gives the payer grounds to question the code.

• An explicit statement of the sterile failure. A nursing entry such as “hub not scrubbed before connection” starts the trail. The provider responsible for the encounter must confirm the failure in their own note.
• The procedure and access type. The note should name the session and the access, such as “during hemodialysis via tunneled right IJ catheter.” That detail is what separates Y62.2 from Y62.1 and Y62.6.
• A causal link to the complication. The provider connects the breach to the coded condition. A positive blood culture with no note attributing it to the breach does not support Y62.2.

Clinical documentation integrity teams should direct Y62.2 queries to the attending provider, not the nursing staff. Building medical billing compliance into the note itself avoids a costly appeal later.

Y84.1 is the code people confuse with Y62.2

The Y62-Y69 block covers misadventures, which means something went wrong during the care. A misadventure the record never specifies goes to Y69. Two neighboring blocks look similar but describe different events.

• Y62.2 vs. Y84.1. Y84.1 is kidney dialysis as the cause of an abnormal reaction or later complication, without mention of misadventure at the time of the procedure. Use it when the record shows no breach.
• Y62.2 vs. Y70-Y82. These codes cover medical devices associated with adverse incidents. A catheter that cracks or fails is a device problem, not a sterile precaution failure.
• Y62.2 with T82.7, T85.71, or T80.21. These are not alternatives. The T-code names the complication, and Y62.2 names its cause.

The tabular notes enforce these lines. The Y62-Y69 block carries an Excludes1 note for Y83-Y84, so Y62.2 and Y84.1 are never coded together for the same event. Y70-Y82 sits under an Excludes2 note, so a device code can be added when a separate device failure also occurred.

Denials usually trace back to sequencing

Most payers, Medicare included, do not pay on external cause codes, so Y62.2 rarely changes the payment amount. Its value is in quality reporting and adverse event tracking. Incorrect use still generates denials and audit flags. The medical billing denial codes on the remittance show which edit fired.

The most common triggers involving Y62.2:

1. Y62.2 in the principal position. Claim edits flag this first. Move the complication code to position one.
2. No complication code. Y62.2 cannot stand alone. Without a T-code or infection code ahead of it, the claim has no diagnosis to support.
3. The wrong Y62 code. Coding an IV antibiotic breach as Y62.2 instead of Y62.1 is a specificity error that audits catch.
4. A missing link statement. The record shows an infection but never ties it to a breach, so the payer cannot validate the code.
5. Y62.2 used where Y84.1 fits. A dialysis complication with no recorded misadventure does not support a sterile-failure code.

Denial management workflows that check sequencing before submission cut rework on these claims. Pairing that with a clean claim checklist keeps external cause codes from tripping edits.

ICD-9 code E872.2 was the direct predecessor

Legacy records and retrospective studies may still carry the ICD-9-CM version. E872.2 used the same wording, “Failure of sterile precautions during kidney dialysis and other perfusion.” Its neighbors followed the same pattern, with E872.0 for surgical operations and E872.1 for infusion or transfusion.

For mapping work, check the general equivalence mappings through the ResDAC guide to ICD codes in Medicare files or the CMS GEM archive. ICD-9 E-codes have not been valid on claims since October 1, 2015.

How Pabau keeps dialysis complication claims clean

In many practices, the breach note sits in a nursing record while the infection is coded weeks later from a hospital summary. The coder then has to reconstruct the link, and the claim waits on a query.

Pabau, the practice management platform we build, keeps the session note, the provider’s assessment, and the claim in one patient record. Custom medical forms can prompt for the access type and any break in technique during the visit. When the claim is built, the coder sees the documentation that supports Y62.2.

Claims go out through our Claim.MD integration, so clearinghouse rejections reach the billing team before the payer does. The result is fewer resubmissions and a cleaner adverse event record.

Document the breach and bill it right

Pabau links session notes, provider documentation, and claims in one record, so external cause codes like Y62.2 go out with the evidence that supports them.

Book a demo

Conclusion

Y62.2 earns its place on a claim only when the record proves a sterile break during dialysis or perfusion. Treat the procedure as the deciding fact. If the line was infusing a drug, use Y62.1, and if no breach was recorded, use Y84.1.

The trade-off is effort at the bedside. A run sheet that asks about aseptic technique costs seconds, while a retrospective query costs days.

Claims management software that keeps notes and claims together makes that easier to sustain. Book a demo to see how Pabau helps your team document complications and send clean claims the first time.

Continue your research

Need a structured approach to clean claim submission? Medical billing fundamentals covers the end-to-end cycle from charge capture through payment posting.

Want to understand how remittance data feeds denial management? Electronic remittance advice explains how 835 ERA files carry CARC denial reason codes back to your billing team.

Looking for a deeper dive on clearinghouse claim validation? Claim.MD clearinghouse outlines how real-time eligibility and claim edits reduce rework before submission.

Coding a sterile breach during a vaccination instead? ICD-10 code Y62.3 covers failures of sterile precautions during an injection or immunization.

Is the misadventure in the record unspecified? ICD-10 code Y69 explains when an unspecified misadventure during care is the right external cause code.

Frequently asked questions