Reviewed May 23, 2026

JC, JD, JE modifiers — legacy drug-billing reference

Last reviewed: May 23, 2026 · Source: CMS HCPCS Level II modifier file · Methodology

Scope note. This page exists for audit completeness and historical reference, not as a billing tool. JC, JD, and JE are largely legacy. In the overwhelming majority of current specialty drug claims you should not append any of them — use the current modifier set (JW/JZ, JG/TB, RT/LT, KX) instead. The narrow exceptions are documented below.

Quick Answer

What do the JC, JD, and JE modifiers mean and do they still apply?

JC, JD, and JE are older HCPCS Level II modifiers originally associated with skin-substitute application context (JC, JD) and certain ESRD/dialysis-drug administration nuance (JE). Their operational use on contemporary specialty drug claims is essentially nil. They remain in the published CMS HCPCS modifier file, so they can be appended by legacy practice-management or vendor systems, but no current waste, 340B, laterality, or medical-necessity rule is built around them. Treat them as audit-reference codes: recognize them when they appear on historic claim files, and rework current claims using JW/JZ, JG/TB, RT/LT, or KX as appropriate.

About the JC, JD, and JE modifiers

The JC and JD modifiers were originally introduced as part of the HCPCS J-series to flag specific application methods for skin-substitute and related biologic products — for example, a sheet-graft application versus a meshed application, in contexts that were narrower than the broader CPT codes for wound care could capture on their own. JE has historically been associated with ESRD-related drug administration in dialysis settings under certain MAC interpretations. None of the three was ever a general-purpose specialty-drug modifier in the way that JW (drug discarded), JG (340B acquisition), or RT/LT (laterality) function today.

Over multiple HCPCS quarterly update cycles, the descriptors for JC and JD have been narrowed or superseded by more specific CPT application codes and site-of-service identifiers. JE has remained published with a narrow descriptor and continues to be referenced in a small number of MAC LCDs covering dialysis-bundled drug administration. The practical result for a biller working a contemporary specialty drug claim is that these three modifiers function as legacy references rather than as active coding tools. Cross-walks published by AAPC and the AHA Coding Clinic for HCPCS consistently route current claims away from JC, JD, and JE toward the current modifier vocabulary.

Authority for HCPCS Level II modifier definitions is the CMS HCPCS Annual File and the quarterly HCPCS updates; payer-specific operational use is governed by MAC LCDs and commercial medical-policy bulletins. CMS has not issued a blanket deprecation transmittal for any of the three modifiers, which is part of why they continue to surface on legacy claim files.

When (if ever) to use JC, JD, or JE

Decision tree — legacy modifier on a current claim
  1. Does the active LCD or commercial medical-policy bulletin for the HCPCS code explicitly name JC, JD, or JE as required? If no, stop. Do not append any of the three to the current claim.
  2. If yes, which modifier and for which code? JE in a small number of ESRD-bundled drug contexts is the most common surface. JC or JD generally point to skin-substitute or related biologic application contexts that fall outside the typical specialty-drug-billing scope this reference cluster covers.
  3. Confirm with the LCD's coding-guidance section, not the broader HCPCS modifier file. Cite the LCD identifier and the revision date in the claim audit trail.
  4. If the original coding intent maps to a current modifier, use that instead. JW/JZ for vial waste, JG/TB for 340B, RT/LT or eye-anatomic for laterality, KX for medical-necessity attestation.

In practice, the only routine current use for any of these three on a specialty-drug-adjacent claim is JE on ESRD-bundled drug lines billed under MAC jurisdictions whose LCDs continue to call for it. Even that is narrow and changing — verify against the active LCD on every billing cycle rather than building it into a default template. For JC and JD, current claims should almost never carry either modifier; if a vendor system is inserting one, treat that as a system-configuration bug to fix at the source.

When NOT to use JC, JD, or JE

Use one of these legacy modifiers only when…

  • The active MAC LCD for the HCPCS code being billed explicitly names the modifier as required (most common: JE in a narrow ESRD-bundled drug context)
  • A commercial payer's current medical-policy bulletin explicitly names the modifier for the product on the line
  • You have cited the LCD or bulletin identifier and revision date in the claim audit trail

Do not append JC, JD, or JE when…

  • You are billing a current specialty drug J-code under Medicare Part B and no active LCD calls for it
  • The original coding intent is single-dose vial waste — use JW or JZ instead
  • The original coding intent is 340B-acquired drug — use JG or TB instead
  • The original coding intent is laterality (eye, limb, side) — use RT, LT, or the eye-anatomic modifiers
  • The original coding intent is medical-necessity attestation against an LCD — use KX
  • The modifier is being auto-inserted by a legacy practice-management or vendor system — fix the configuration at the source
  • You found one of these on a historic claim and are tempted to carry it forward into the current rework — do not

The dominant operational risk with JC, JD, and JE is not a high-volume denial pattern (current payers tend to ignore them silently) but the audit-trail noise they introduce. A claim history with stray legacy modifiers complicates post-payment audit responses, RAC defense, and biosimilar mandate compliance reviews, because the auditor must reconcile the legacy code against current policy. Cleaning legacy modifiers out of templates and vendor defaults is higher-value than chasing payer-side denials for them.

Per-payer requirements

No major payer requires JC, JD, or JE as a default modifier on contemporary specialty drug claims. The table below summarizes the practical posture each payer takes when one of these modifiers appears on a current claim or carries over from a legacy claim file.

Payer Required on current specialty drug claims? Notes
Medicare (Part B) No, with narrow MAC LCD exceptions (most commonly JE in ESRD contexts) Modifiers remain published in the HCPCS Level II modifier file. CMS has not deprecated them via blanket transmittal. Operational use is governed by the active MAC LCD, not the modifier file. Check the LCD coding-guidance section before either appending or omitting.
UnitedHealthcare No Current UHC commercial and Medicare Advantage medical-policy bulletins for specialty drugs do not call for JC, JD, or JE. UHC adjudication tends to silently ignore them when appended in error; the OptumRx infused-meds prior-auth workflow does not key on any of them.
Aetna (CVS Health) No Aetna medical-policy bulletins for oncology and infusion drugs do not reference these modifiers. CVS Specialty dispensing reports do not generate or expect them. Aetna processes ignore stray legacy modifiers without explicit denial.
Cigna / Express Scripts No Cigna commercial and Accredo network claims do not require any of the three. Stray legacy modifiers are silently dropped at adjudication; they do not appear on Accredo dispensing reports for current biologics.
Humana No, with the same narrow MAC LCD ESRD-context caveat for JE on the Medicare Advantage side Humana MA largely follows the MAC LCD posture for ESRD-bundled drug claims; check the operative LCD for the jurisdiction. Humana commercial does not require any of the three on specialty drug claims.

Across the major payers the consistent pattern is silent ignore at adjudication and audit-trail noise downstream. Operationally, the highest-leverage action is removing JC, JD, and JE from any default modifier list or vendor-side claim template, rather than re-defending or appealing individual claim-line outcomes.

Worked examples

Historic claim — legacy JC appended to an infusion line J-code · legacy claim format audit reference
Scenario
Reviewer pulls a 2018 infusion-clinic claim file as part of a routine pre-audit cleanup and finds JC appended to an oncology biologic line.
Context
The vendor's older modifier-default list included JC in a position the system filled when no other waste modifier was selected.
Current intent
Single-dose vial waste was actually present, but the original claim used JC instead of a structured JW waste line.
Historic line: [J-code] × [units] — JC  (legacy artifact, no current operational meaning)
Document and move on. The historic claim adjudicated under the rules in effect at the time and does not need to be reopened solely because of the legacy modifier. The lesson is operational: fix the vendor template so JC does not auto-fill on current claims, and ensure ongoing single-dose vial waste is structured as a separate JW line per IOM Pub 100-04 Chapter 17 §40.
Current claim — same scenario, modern modifier structure J-code · current claim format use current modifiers instead
Scenario
Same drug, same single-dose vial waste scenario, billed today.
Vials drawn
Total billing units of the single-dose container(s) opened
Administered
Patient dose in integer billing units
Discarded
Vial-total minus administered, in integer billing units
Line 1: [J-code] × [administered units] — (no waste modifier)
Line 2: [J-code] × [discarded units] — JW — drug discarded
Two clean lines, JW on the waste line, JC nowhere on the claim. The current convention captures the same clinical reality (a single-dose vial with leftover drug discarded) using the modifier that actually feeds the CMS quarterly manufacturer-refund calculation. JC carries no equivalent operational meaning on the current claim and is omitted entirely.
ESRD-bundled context — JE per active MAC LCD ESRD drug HCPCS · jurisdiction-specific verify against active LCD
Scenario
Dialysis facility billing an ESRD-bundled drug under a MAC LCD whose coding-guidance section names JE.
Required check
Pull the active LCD revision; confirm JE appears in the coding-guidance section next to the HCPCS code on the line.
Line: [ESRD drug HCPCS] × [units] — JE  (per LCD [identifier], revised [date])
Append JE only because the LCD explicitly says to. Cite the LCD identifier and revision date in the claim audit trail. If the LCD is silent on JE for this code, omit it. This is the single narrow scenario where any of the three legacy modifiers retains current operational use, and even here the rule comes from a specific MAC LCD rather than from a generally applicable CMS transmittal.

Common denials and how to fix them

PatternWhat it meansFix / cleanup language
Stray JC, JD, or JE on a current claim (silent ignore, audit-trail noise) The legacy modifier was carried forward from a vendor default or a copied-from-historic-claim template. Most payers will adjudicate the line on the underlying J-code without explicit denial, but the modifier sits in the claim record as audit-trail noise. Fix the vendor template so the modifier does not auto-insert. On open claims, strip the legacy modifier and confirm any current waste, 340B, laterality, or LCD-attestation requirements are reflected via JW/JZ, JG/TB, RT/LT or eye-anatomic, and KX as applicable. Audit-trail note: “Removed legacy JC/JD/JE modifier with no current operational basis under active LCD and CMS HCPCS guidance.”
Legacy modifier in place of a current modifier (effective denial of the intended coding) Example: JC was appended where the underlying scenario was actually single-dose vial waste. The claim adjudicates without the JW reporting that should have happened, which under-reports waste data into the CMS manufacturer-refund calculation and may trigger downstream audit attention. Rework the claim using the current modifier (JW on a separate discarded-units line; JZ on the administered line if no waste). Appeal language: “The corrected claim restructures the line(s) per CMS IOM Pub 100-04 Chapter 17 §40, replacing legacy modifier [JC/JD/JE] with the current waste reporting required for single-dose container drug.”
Audit request citing legacy modifier on a historic claim A RAC or payer post-payment audit notice references the legacy modifier on a closed claim, typically as part of a broader documentation request rather than as a standalone basis for recoupment. Respond with the original chart documentation supporting the line as billed and a short note that the modifier reflects HCPCS guidance in effect at the time of billing. If the audit cites a specific current rule, point to the operative date and the contemporaneous LCD or transmittal rather than re-defending against current policy.
JE absent from an ESRD-bundled drug claim where the active MAC LCD requires it Narrow jurisdictional pattern. The LCD's coding-guidance section names JE for the ESRD drug on the line, the claim omitted it, the line denies or down-codes. Resubmit with JE appended and cite the LCD identifier and revision date. Appeal language: “Per [MAC LCD identifier], revised [date], modifier JE is required on [HCPCS code] in the ESRD-bundled drug administration context. The corrected claim appends JE per the operative LCD coding-guidance section.”

Frequently asked questions

Are JC, JD, and JE still used on current Medicare claims?

Largely no. JC, JD, and JE remain published in the CMS HCPCS modifier file but their original use cases (skin-substitute application method, certain biologic preservation states, and ESRD-related drug administration context) have either been superseded by site-of-service codes, anatomic modifiers, or product-specific HCPCS codes. Most current specialty drug claims do not need any of these modifiers. The most common contemporary surface for any of the three is JE in a small number of ESRD-related dialysis drug contexts where a specific MAC LCD continues to call for it.

I see JC on an older claim file — what does it most likely mean?

On historic claims, JC was associated with skin-substitute application by sheet graft or similar method, distinct from injection or topical use. In a specialty drug context it almost never applied; if you see it on an old infusion claim, it is most often a data-entry artifact or a vendor system that inserted it from a stale modifier list. Re-read the original chart against the FDA labeling for the product billed before treating the old claim as authoritative.

Should I add JC, JD, or JE to current claims?

No, not by default. Build current claims using the current modifier set (JW/JZ for single-dose vial waste, JG/TB for 340B, RT/LT or eye-anatomic modifiers for laterality, KX for medical-necessity attestation). Add JC, JD, or JE only when the specific MAC LCD or payer policy you are billing under explicitly directs it for the HCPCS code on the line. Defaulting one of these onto a current claim risks either silent payer ignore or an audit flag.

Has CMS officially deprecated JC, JD, or JE?

CMS has not issued a blanket deprecation transmittal removing these from the HCPCS modifier file, but the operative descriptors have been narrowed over multiple HCPCS update cycles and most cross-walks to current modifier sets quietly drop them. The practical posture for billers is: treat them as legacy unless a current LCD, NCD, or payer medical-policy bulletin you are billing under explicitly lists one as required.

Is JE used in any drug-billing context today?

JE has retained a narrow association with ESRD-related drug administration in certain MAC jurisdictions and dialysis-specific guidance. If you bill ESRD-bundled or composite-rate adjacent claims, check the active LCD for your MAC before either adding or omitting JE — the few residual use cases are jurisdiction-specific and change quietly. Outside of ESRD, JE is not part of the current specialty-drug modifier vocabulary.

What modifier should I use instead of JC, JD, or JE on a current specialty drug claim?

It depends on what you were trying to communicate. For discarded single-dose vial drug: JW (waste) or JZ (no waste). For 340B-acquired drug under Medicare Part B: JG or TB depending on hospital type. For laterality on ophthalmic injections: RT, LT, or the per-eye anatomic modifiers. For medical-necessity attestation against an LCD: KX. None of these three legacy modifiers carry an operational meaning on a current J-code claim that one of the modifiers above does not handle more cleanly.

Could a MAC LCD still require JC, JD, or JE on a specific code?

Yes, in narrow cases. MACs occasionally retain older modifier requirements in LCDs that have not been refreshed since the modifier set evolved. The rule of thumb: if the LCD you are billing under explicitly lists one of these modifiers next to the HCPCS code you are reporting, comply with the LCD; if the LCD is silent, do not add the modifier. Always check the LCD's last revised date and its specific “Coding Guidance” section rather than relying on the broader HCPCS modifier file.

If I find JC, JD, or JE on a paid historic claim, do I need to do anything?

No corrective action is needed on a paid, closed historic claim solely because it carries a legacy modifier — payment posted under the rules in effect at the time. Document the encounter for audit completeness, and if the modifier appears on an open or recently denied claim, rework it under the current modifier set rather than re-defending the legacy code.

Sources

All sources are publicly available federal publications or paraphrased from trade-association educational materials. The methodology by which we resolve source disagreements is described in the Methodology.

Editorial review & sourcing
Reviewed by
CareCost Estimate editorial team (Pending SME review)
Last reviewed
May 23, 2026
Update triggers
CMS HCPCS modifier file revision, MAC LCD revision touching ESRD-bundled drug administration, reader-reported correction.
Independence
CareCost Estimate accepts no compensation from drug manufacturers, payers, or PBMs. Full statement on the Advertising Disclosure.
Spotted an error?
Email editorial@carecostestimate.com. Confirmed corrections normally ship within five business days and are recorded in the public change log.