HCPCS code A4216: Sterile water, saline and/or dextrose diluent/flush

Key Takeaways

HCPCS code A4216 describes sterile water, saline and/or dextrose diluent/flush, 10 ml – a Level II HCPCS supply code under the DME/medical supplies category.

A4216 is covered by Medicare as a DME supply. Fee schedule rates vary by MAC jurisdiction and are updated annually by CMS.

The code appears on the ESRD bundled payment list, which affects billing separately for dialysis patients – always verify current bundle status before submitting claims.

Pabau’s claims management software helps practices apply correct HCPCS Level II supply codes, modifiers, and supporting diagnosis codes to reduce denials.

HCPCS code A4216: Definition and code attributes

HCPCS code A4216 is a Level II supply code for sterile water, saline and/or dextrose diluent/flush, billed in 10 ml units under the DME/medical supplies category. It carries its own coverage logic, bundling rules, and modifier requirements, distinct from a procedure code’s billing logic. This reference covers every billing dimension of A4216, from Medicare coverage to modifiers, supporting ICD-10 codes, and the crosswalk to related codes.

Official long description: Sterile water, saline and/or dextrose, diluent/flush, 10 ml. The code is maintained by CMS as part of the HCPCS Level II alphanumeric code set. According to CMS, HIPAA-compliant electronic claim submissions require valid HCPCS Level II codes for all covered supplies, so accurate code selection affects compliance as well as revenue.

Medicare coverage and fee schedule for HCPCS code A4216

Medicare covers A4216 as a DME supply under the DMEPOS (Durable Medical Equipment, Prosthetics, Orthotics and Supplies) fee schedule. Coverage is subject to applicable Local Coverage Determinations (LCDs) issued by the relevant Medicare Administrative Contractor (MAC) for the beneficiary’s state. Always verify active LCD status before billing, as MAC policies update independently of the national fee schedule.

2026 Fee schedule rates

The 2026 HCPCS A4216 fee schedule rates are set by CMS and administered through the CMS fee schedule lookup. National average payment figures reflect the allowed amount before geographic adjustments. MAC-level rates incorporate locality pricing factors, so practices in high-cost regions may receive higher reimbursements than the national average. Commercial payer rates are negotiated separately and can differ substantially from Medicare benchmarks.

ESRD bundling note: A4216 has been confirmed on ESRD bundled payment lists, meaning it is typically not separately billable for end-stage renal disease patients under the ESRD Prospective Payment System. Verify current bundle inclusion against the CMS ESRD PPS documentation before each billing cycle. Incorrect separate billing for bundled services triggers recoupment risk. Practices managing complex renal patients benefit from claims management software that flags bundling conflicts before submission.

Billing guidelines for HCPCS A4216

Supply code billing has tighter unit-of-service rules than procedure codes. For A4216, each unit represents 10 ml. Submit units reflecting the quantity dispensed, not a rounded estimate. Over-billing units – even by one – creates an audit exposure that outweighs any revenue gain.

Applicable modifiers

Modifier selection for A4216 depends on the supply context and payer requirements. The table below reflects commonly applicable modifiers. Always verify with the relevant MAC LCD and payer policy before submitting, as modifier rules are updated periodically by CMS. You can search current HCPCS modifier guidance through the AAPC Codify HCPCS lookup.

ICD-10 codes supporting medical necessity for A4216

Medicare and most commercial payers require a supporting diagnosis code to establish medical necessity for supply claims. The diagnosis code must be active, specific enough to justify the supply, and documented in the patient record. The following conditions commonly appear on A4216 claims:

ICD-10 code selection must reflect the documented clinical reason for the supply – not simply a code that “fits.” J44.1, for example, supports nebulizer diluent claims only when the documentation specifies an acute exacerbation. Specificity matters: a non-specific code where a more specific option exists can trigger a medical necessity denial. Document the primary diagnosis, treatment plan, and the clinical rationale for using a sterile diluent or flush in the patient record before billing.

Documentation requirements

Documentation for A4216 claims must support both the supply itself and its clinical necessity. The standard audit trail for DME supply claims includes:

• A written order or prescription from the treating clinician specifying the supply type and quantity
• A diagnosis that supports the need for a sterile diluent or flush (linked to an active ICD-10 code)
• Evidence that the patient is using, or will use, the associated equipment requiring the flush (e.g., nebulizer, infusion pump, catheter)
• Date of service and quantity dispensed, matching the units billed on the claim
• Any applicable ABN (Advance Beneficiary Notice) if coverage is uncertain

The treating physician’s order must be on file before – not after – the supply is dispensed. Retroactive orders are a common audit finding and typically result in full recoupment. Using digital forms for intake and consent workflows can support the documentation chain, with timestamped records that are audit-ready from the point of care. For a broader look at medical records management, medical forms best practices outlines the key compliance checkpoints.

Clinical use cases for A4216

A4216 covers 10 ml units of sterile water, saline, or dextrose used as a diluent or flush. The clinical context determines which substance is appropriate and how billing should be structured, and GP practices billing nebulizer treatments apply it differently than a DME supplier billing a flush kit.

• Nebulizer diluent: Sterile saline or water used to dilute bronchodilator medications for patients with COPD or asthma on DME nebulizers. Each 10 ml unit billed must correspond to usage.
• Medication dilution (home infusion): Dextrose or saline used to dilute medications administered via infusion pump in a home setting. Units must reflect the dispensed quantity per the treatment order.
• Wound irrigation: Sterile saline used to irrigate wound sites during DME-supported wound care. Document wound stage, site, and frequency of irrigation.
• Catheter flush: Sterile saline or water used to maintain patency of indwelling catheters, often billed alongside A4311 for the catheter itself. Frequency and quantity must match the physician’s care plan.
• IV therapy preparation: In IV therapy clinic settings, sterile water or saline serves as a diluent for custom infusion preparations. Practices running IV therapy clinic software often track supply usage by patient session for accurate per-unit billing.

The key billing principle across all use cases: bill units of A4216 equal to the 10 ml increments dispensed. Rounding up to a convenient number or billing a “standard amount” without supply-level tracking creates billing inaccuracy.

Reduce HCPCS billing errors with Pabau

Pabau's claims management tools help DME suppliers and clinical practices track supply codes, apply modifiers correctly, and submit cleaner HCPCS claims – so you spend less time on denials and more time on patient care.

Book a demo

Common billing errors and how to avoid them

A4216 denials cluster around a small number of recurring mistakes. Understanding the pattern is the fastest way to reduce denial rates. The following errors are commonly reported by medical billers and coders working with DME supply codes:

Related HCPCS codes

A4216 sits within a series of adjacent supply codes covering sterile water, saline, and related flush supplies in different volumes and formulations. Choosing the wrong code from this group is a common and avoidable billing error. The PGM HCPCS lookup tool provides free current-year descriptions for all A-series codes. Use the comparison table below to confirm you are billing the correct code for the actual supply dispensed.

The critical distinction between A4216 and A4217 comes up frequently in billing reviews. A4216 covers the 10 ml unit. Billing multiple A4216 units when a 500 ml container was dispensed is technically inaccurate – use A4217. For IV therapy practices and DME suppliers, accurate code selection by volume is a basic audit checkpoint. Practices using EHR integration to link supply records with billing workflows can automate volume-to-code matching, reducing this type of error at the point of entry.

How Pabau supports HCPCS billing for supply codes

Billing HCPCS Level II supply codes accurately requires more than knowing the code description. It requires a workflow that captures the right supply quantity at the point of care, links it to a documented diagnosis, and flags modifier requirements before the claim leaves the practice. Manual processes at any of these steps create denial risk.

Pabau’s claims management software is built for practices that need to track DME supply usage alongside clinical workflows – not as a separate back-office task. Supply quantities recorded during patient encounters feed directly into claim preparation, so what was dispensed and what gets billed stay aligned. Modifier fields are built into the claim workflow, so billers see the relevant options at claim creation rather than catching omissions in a post-submission review.

For practices managing patient data security alongside billing compliance, Pabau maintains HIPAA-aligned data handling across all billing records. The practice management platform integrates scheduling, clinical documentation, and billing into one system – so the order that justifies the supply claim is in the same record as the claim itself. That integrated audit trail is what MAC auditors look for when reviewing DME supply claims.

Code history and crosswalk

A4216 has maintained a consistent description and active status across recent fiscal years. CMS reviews HCPCS Level II codes annually and publishes updates effective January 1 each year. Code descriptions, coverage status, and fee schedule rates can all change at the annual update. The NLM Clinical Table API provides programmatic access to current HCPCS Level II code descriptions for practices that maintain automated code reference tools.

No predecessor code crosswalk is required for A4216 – it is a long-standing code without a recent ICD-9-era equivalent to map from. For practices running coding software that pulls historical crosswalk data, A4216 should appear as a direct-match code with no substitution or transition flag. The same volume-versus-code precision comes up with A4244, a comparable DME antiseptic supply code, and with drug codes like J7326, where the billed unit has to match what was used.

Conclusion

HCPCS code A4216 is a simple code description with complex billing implications. The ESRD bundling rules, unit-of-service precision, modifier requirements, and documentation chain each create separate denial pathways for practices that treat it as a routine supply entry.

Practices that reduce A4216 denials consistently share one characteristic: their supply billing is integrated with clinical documentation, not handled as a separate back-office process. Pabau’s claims management tools bring those workflows together, giving billers the data they need at claim creation rather than during a post-denial review. To see how it works in your setting, book a demo with the Pabau team.

Continue your research

Need to manage billing compliance across your whole practice? Claims management software in Pabau centralizes HCPCS code entry, modifier application, and claim tracking in one integrated workflow.

Running an IV therapy clinic and billing supply codes regularly? IV therapy EMR software from Pabau tracks supply usage per session so your per-unit billing matches what was dispensed.

Want tighter documentation before a MAC audit? Medical forms best practices covers the documentation standards that support DME supply claims through payer review.

Frequently asked questions