Heart Transplants — NCD 112 | CMS Coverage Update

CMS modified NCD 112 governing Medicare heart transplant coverage, effective March 7, 2026. Here's what billing teams at transplant facilities need to know.

The Centers for Medicare & Medicaid Services updated National Coverage Determination NCD 112, the policy governing Medicare coverage of cardiac transplantation. This modification touches facility approval requirements, multi-hospital arrangements, pediatric program criteria, and follow-up care coverage. The policy does not list specific CPT or HCPCS codes — but if your facility bills for heart transplant services under Medicare, this coverage policy affects your reimbursement and your documentation requirements directly.

---

Quick-Reference Table

Field	Detail Copy
Payer	CMS (Centers for Medicare & Medicaid Services)
Policy	Heart Transplants
Policy Code	NCD 112
Change Type	Modified
Effective Date	March 7, 2026
Impact Level	High
Specialties Affected	Cardiac Surgery, Cardiology, Pathology, Transplant Programs, Pediatric Cardiac Surgery
Key Action	Audit your facility's CMS approval status and multi-hospital arrangement documentation before March 7, 2026

---

CMS Heart Transplant Coverage Criteria and Medical Necessity Requirements 2026

The core rule under NCD 112 hasn't changed in spirit, but the updated language tightens how CMS evaluates facility eligibility. Medicare covers cardiac transplantation only when performed at a facility that CMS has approved as meeting the institutional criteria in CMS Ruling 87-1.

If your facility isn't on that approved list, the claim denial risk isn't theoretical — it's automatic. Coverage is conditional on facility-level approval, not just medical necessity at the patient level. Your medical director and compliance officer should confirm your facility's current approval status before the effective date of March 7, 2026.

The medical necessity determination for the patient comes after the facility clears that threshold. Follow-up care resulting from a covered transplant is also covered, as long as the services are otherwise reasonable and necessary under Medicare guidelines. That's a meaningful coverage policy protection — it extends to post-discharge follow-up even when patients received a noncovered transplant, provided the specific follow-up services themselves meet Medicare's medical necessity standards.

The policy points billing teams to the Medicare Benefit Policy Manual, Chapter 16, Section 180 for follow-up care exclusions. Review that section now if your team handles post-transplant billing. Immunosuppressive drugs are governed separately under the Medicare Claims Processing Manual, Chapter 17, Sections 80.3.1 and beyond — don't fold drug reimbursement questions into this NCD without checking those references.

---

CMS Heart Transplant Multi-Hospital and Exception Criteria Under NCD 112

This is where NCD 112 gets complicated — and where most billing teams have the most exposure.

CMS allows exceptions to the standard facility criteria in limited cases, but the bar is high. The policy is explicit: no exceptions for facilities whose transplant programs have been in existence for less than two years. If your program launched after March 7, 2024, don't plan on qualifying under an exception route. That two-year minimum is a hard stop.

Consortium arrangements are not approved for Medicare heart transplant reimbursement. Full stop. If your facility has been operating under a consortium model and billing Medicare for heart transplants, that's a serious compliance exposure point. Talk to your compliance officer today — not after the effective date.

There is a narrow pathway for multi-hospital arrangements, but it's not a consortium. CMS will consider applications from facilities where multiple hospitals share common control or operate under a formal affiliation through an organization like a university or legally constituted medical research institute. The conditions are specific and all must be met:

• The hospitals must share the same transplant team personnel — cardiac transplant surgeons, cardiologists, and pathologists must practice across all hospitals.
• The same organ procurement organization, immunology services, and tissue-typing services must serve all hospitals.
• Each hospital must submit individual and pooled experience and survival data using the Kaplan-Meier method.
• All hospitals must otherwise meet the full Medicare criteria for heart transplant programs.

The Kaplan-Meier submission requirement is a documentation detail your quality and compliance teams need to own — not just your billing team. If that data isn't being tracked and formatted correctly, your facility's approval status is at risk.

---

CMS Pediatric Heart Transplant Coverage Criteria 2026

Pediatric hospitals get a separate pathway under NCD 112, and it's worth understanding precisely.

Medicare covers cardiac transplantation for its beneficiaries at a pediatric hospital if CMS approves the hospital's application. The program must be operated jointly with another CMS-approved facility. The two programs must share the same transplant surgeons and the same quality assurance structure — that means the same oversight committee, the same patient protocol, and the same patient selection criteria.

The pediatric hospital must also show it can provide specialized facilities, services, and personnel specific to pediatric heart transplant patients. "Specialized" isn't decoration here — CMS expects documentation that the facility is genuinely equipped for the pediatric population, not just adjacent to an adult program.

If you work at a pediatric hospital that performs heart transplants and bills Medicare, confirm that the joint program documentation is current and that your quality assurance program documentation is aligned with the adult partner facility. A gap in any of those three criteria puts the coverage policy determination at risk for your facility.

---

CMS Heart Transplant Exclusions and Non-Covered Indications

NCD 112 doesn't list a blanket set of clinical exclusions for individual patients, but it establishes facility-level non-coverage that functions the same way operationally.

The clearest exclusion: consortium arrangements. If your facility is part of a consortium — as opposed to a formal multi-hospital affiliation under common control — Medicare will not reimburse heart transplant services. Billing under a consortium structure is a claim denial waiting to happen.

New programs under two years old are excluded from exception consideration entirely. If your program falls in that window, don't submit under an exception pathway — the application will not be approved.

Follow-up care after a noncovered transplant sits in a gray zone. CMS covers those follow-up services if they're individually reasonable and necessary. But the transplant procedure itself is not retroactively covered. Make sure your team doesn't bundle follow-up billing in a way that implies coverage for the underlying noncovered transplant.

---

Coverage Indications at a Glance

---

CMS Heart Transplant Billing Guidelines and Action Items 2026

Copy Action Items

---

CPT, HCPCS, and ICD-10 Codes for Heart Transplants Under NCD 112

The policy data for NCD 112 does not list specific CPT, HCPCS, or ICD-10 codes. This is consistent with how CMS structures facility-level NCDs — the coverage determination governs institutional eligibility, not individual code-level billing.

For specific procedure code guidance on heart transplant billing, check with your Medicare Administrative Contractor. MAC-level local coverage determinations or billing articles may provide code-level specificity that NCD 112 itself does not. Your coding team should already have the relevant procedure codes for cardiac transplantation, but the coverage policy question under NCD 112 is about whether your facility can bill them at all — not which codes to use.

If you're unsure which codes your MAC expects on heart transplant claims, pull your contractor's published billing guidance and reconcile it with your current charge capture. Don't assume NCD 112's silence on codes means there's no code-level requirement at the MAC level.

---