ICD-10 code T82.532A: Leakage of artificial heart, initial encounter

Found our content helpful?

Key takeaways

ICD-10 code T82.532A describes leakage of an artificial heart at the initial encounter, and it is billable under the 2026 ICD-10-CM edition.

The 7th character ‘A’ marks the initial encounter. Use T82.532D for subsequent encounters and T82.532S for sequela, because the wrong character is the top denial reason on this code.

Documentation must name the artificial heart device, confirm leakage as the complication, and reflect the encounter stage.

T82.531x is not an alternative to T82.532A. It covers leakage of a surgically created arteriovenous shunt.

Practice management software like Pabau checks ICD-10 codes against built-in catalogs before a claim goes out, so format errors surface early.

ICD-10 code T82.532A is the billable ICD-10-CM diagnosis code for leakage of an artificial heart, initial encounter. It is valid for submission under the 2026 ICD-10-CM edition, effective October 1, 2025.

The code sits in the T82 category, which covers complications of cardiac and vascular prosthetic devices, implants, and grafts. It is POA exempt. To use it, the documentation has to name the device and identify leakage as the complication. It also has to show this is the first active treatment encounter.

ICD-10 code T82.532A: Definition and billable status

ICD-10 code T82.532A is defined in the ICD-10-CM tabular list as “Leakage of artificial heart, initial encounter.” It is billable and specific, so it carries enough detail to go on a claim for reimbursement. The CDC/NCHS ICD-10-CM web tool confirms it as valid for the 2026 fiscal year, effective October 1, 2025.

The table below summarizes every key property at a glance.

How the 7th character decides between A, D and S

The 7th character in T82.532A designates the encounter type, and picking the wrong one is the most common reason this code is denied. The CMS ICD-10-CM guidelines define three valid 7th characters for the T82.532 subcategory.

For cardiology coders, the working rule is short. Use T82.532A whenever the provider is actively managing the leakage for the first time. Once the patient moves to routine monitoring or wound care, T82.532D applies. T82.532S is reserved for residual effects documented after the acute problem has resolved.

Ambiguous encounter language is the usual culprit. A note reading “follow-up for artificial heart” never says whether treatment is still ongoing, so the coder has to query the physician. That query delays the claim. Naming the encounter stage in the note removes the delay.

Where T82.532A sits in the ICD-10-CM hierarchy

T82.532A belongs to a defined parent-child hierarchy within ICD-10-CM. Following that hierarchy helps coders reach adjacent ICD-10-CM codes quickly, and confirms they have selected the most specific code available.

• Chapter 19: Injury, poisoning, and certain other consequences of external causes (S00-T88)
• Block T80-T88: Complications of surgical and medical care, not elsewhere classified
• Category T82: Complications of cardiac and vascular prosthetic devices, implants and grafts
• Subcategory T82.5: Mechanical complication of other cardiac and vascular devices and implants
• Subcategory T82.53: Leakage of other cardiac and vascular devices and implants
• Code T82.532: Leakage of artificial heart
• Code T82.532A: Leakage of artificial heart, initial encounter

The hierarchy clarifies one point. T82.532 codes describe leakage of an artificial heart, not other cardiac prosthetics. Do not use T82.532A for leakage of a prosthetic cardiac valve, which has its own subcategory. It also does not cover other device failures such as breakdown or displacement.

What leakage of an artificial heart means clinically

Leakage of an artificial heart is a mechanical complication in which fluid escapes from the device or its connections. That escape can compromise device function or the surrounding tissue. ICD-10 code T82.532A captures it at the first active treatment encounter.

Devices coded under T82.532 include total artificial hearts (TAH) and certain ventricular assist devices (VADs), including left ventricular assist devices (LVADs).

The note should name the specific device, because different implanted cardiac support devices can follow distinct coding pathways depending on the complication. Verify which device is implanted before you settle on the final code.

Clinically, leakage differs from the other mechanical complications in the T82 category:

• Leakage (T82.532x): fluid escaping from the device or its connections
• Breakdown (T82.512x): the device stops functioning mechanically
• Displacement (T82.522x): the device shifts from its intended position
• Obstruction (T82.592x): flow through the device is blocked

Each distinction matters because each has its own subcategory. A note documenting leakage supports T82.532A. A note documenting device malfunction without naming the type needs a physician query first.

The complication subtype and the encounter stage are the only two choices the code needs. The chart below runs through both in order.

T82.532A vs. related mechanical complication codes

Coders frequently need to separate T82.532A from adjacent codes in the T82.53 subcategory, and from the encounter variants T82.532D and T82.532S. The comparison table below is the quickest way to make those distinctions.

T82.531x and T82.532x look close on the page, but they describe different devices. Miss the distinction and the claim can deny on a specificity edit.

When the operative or cardiology note names the implanted device, that language maps straight to the correct subcategory. Recurring denials on these codes almost always trace back to thin device detail in the source documentation.

Approximate synonyms for T82.532A

The clinical terms below map to T82.532A. Any of them in the operative report or physician note can support the code, provided the encounter type matches the 7th character.

• Leakage of artificial heart
• Artificial heart device leakage
• Prosthetic heart device leakage, initial encounter
• Mechanical complication, leakage, total artificial heart
• TAH leakage, initial encounter
• LVAD leakage (when the LVAD is coded within T82.532 parameters)

Coding guidelines and documentation requirements for T82.532A

The ICD-10-CM Official Guidelines for Coding and Reporting govern how T82 codes are selected and sequenced.

They are co-published by CMS and the National Center for Health Statistics (NCHS). Every diagnosis submitted on a claim must be supported by the medical record, and T82.532A is no exception.

When to use T82.532A: Clinical scenarios

T82.532A applies when three conditions are present in the documentation. An artificial heart or equivalent cardiac assist device is implanted. Leakage is named as the complication. And the encounter is the first active treatment visit for that complication.

• A patient with a total artificial heart presents to the cardiology practice with fluid accumulating around the device. This is the first visit to evaluate and treat the leakage
• A patient with an implanted cardiac assist device is admitted for surgical revision because of device leakage. The inpatient admission is coded at the initial encounter
• An emergency department encounter for acute onset leakage from an artificial heart, with active management started during that visit

T82.532A does not apply when the complication is a different mechanical failure, such as breakdown, displacement, or obstruction.

It also does not apply when the leaking device is a different cardiac or vascular implant. Nor does it apply when the encounter is a follow-up after active treatment has been rendered.

Additional codes to report alongside T82.532A

ICD-10-CM tabular instructions for the T82 category may call for additional codes. Check the full tabular entry for any “Use additional code” or “Code also” note. For cardiac device complication codes, these additional code types come up most often.

• External cause code: report a cause code from the Y83 range for the surgical procedure behind the complication, where the tabular list instructs it
• Underlying condition: report the cardiac condition that led to the implant, such as cardiomyopathy, following the sequencing guidelines
• Status code Z95.811 or similar: a heart assist device status code can document that the implant is present. Verify it in the current tabular list

Sequencing on inpatient claims works like this. Report T82.532A as the principal diagnosis when the leakage is the condition primarily responsible for the admission. On outpatient visits, the code should reflect the condition treated or managed at that encounter.

How a T82.532A claim reaches the payer

Getting T82.532A onto a clean claim takes more than the right diagnosis code. That workflow starts with eligibility verification and the right procedure-code pairing. It ends at a clearinghouse that validates code combinations before they reach the payer.

For cardiology teams billing complex device complications, knowing how a medical claims clearinghouse processes these claims shows where denials start.

When a T82.532A claim comes back denied, read the reason code on the remittance advice. It tells you whether the problem is the diagnosis code, the encounter character, or the procedure pairing.

Compliance considerations for T82.532A claims

T82.532A is POA exempt, which changes inpatient hospital reporting. Present-on-admission exempt codes are excluded from the standard POA indicator requirement under CMS inpatient prospective payment system (IPPS) rules. Complications of devices and implants are recognized as hospital-acquired conditions that may not be present at admission.

Verify the current CMS POA exempt list each fiscal year, because exempt status can change with the annual update.

For outpatient and professional claims, POA status does not apply. The documentation still has to support the diagnosis. Payers running post-payment audits on T82-category claims look for physician documentation that names the device, describes the complication, and supports the encounter type coded.

The American Hospital Association (AHA) Coding Clinic is the official advisory resource for complex ICD-10-CM coding questions. When documentation on an artificial heart leakage case is ambiguous, check AHA Coding Clinic guidance or query the attending physician first. Coding ambiguous documentation anyway creates audit exposure.

How Pabau catches T82.532A errors before the payer does

Most coding teams find a T82.532A problem after the payer has already found it. The denial lands, someone pulls the note, and the encounter character or the device detail turns out to be the cause. Weeks of float have gone by.

Practice management software like Pabau moves that check to the front of the process. Claims carrying T82.532A run through real-time eligibility checks and are validated against built-in CPT and ICD-10 catalogs before submission. Pabau connects to Claim.MD, our US clearinghouse partner, which reaches thousands of US payers.

Denials that do come back are tracked by payer inside Pabau’s medical claims management tools, so patterns surface instead of repeating. Appeals route with the supporting documentation already attached to the patient record, so nobody rebuilds the case from scratch.

Clean up cardiac device complication coding

Pabau validates ICD-10 codes like T82.532A against built-in catalogs before the claim reaches the payer. Real-time eligibility and denial tracking sit in the same platform.

Book a demo

Conclusion

T82.532A is narrow by design. It holds only when the device is an artificial heart, the complication is leakage, and the encounter is the first round of active treatment. Change any one of those and the code changes with it.

Most of the work sits in the note that has to support the code, not in the tabular list. A physician query before submission costs far less than an appeal afterwards, and it takes a fraction of the time.

Pabau’s Claim.MD integration validates ICD-10 code combinations before they reach the payer, so format problems surface at submission rather than after a denial. Book a demo to see how the workflow handles complex cardiac device codes.

Continue your research

Need guidance on US claims clearinghouse workflows for cardiac codes? Medical claims clearinghouse explained covers how clearinghouses validate ICD-10 codes before payer submission.

Working through a denial on a T82 code? Denial codes in medical billing breaks down the most common CARC reason codes and how to respond.

Preparing for a clean claim on complex cardiac billing? What makes a clean claim outlines the submission requirements that prevent front-end rejections on diagnosis codes like T82.532A.

Reading the payer response on a rejected T82.532A claim? Electronic remittance advice explained shows where the payer states why a diagnosis code was rejected.

Denials on cardiac device codes piling up? Denial management in healthcare sets out a process for working denials back through documentation and appeals.

Frequently asked questions