HCPCS Code A4246: Betadine or pHisoHex solution, per pint

Key Takeaways

HCPCS Code A4246 describes Betadine or pHisoHex solution, per pint, under HCPCS Level II A-series medical and surgical supply codes (A4000-A4999).

Medicare may cover A4246 for DME suppliers and home health agencies, but coverage depends on medical necessity documentation and applicable Local Coverage Determinations.

Common billing errors include submitting without a supporting ICD-10 diagnosis code and failing to document the specific product and quantity supplied.

Pabau’s claims management software helps wound care and DME-adjacent practices track supply codes, attach documentation, and reduce claim denials.

HCPCS Code A4246 covers Betadine or pHisoHex antiseptic solution, billed per pint under the HCPCS Level II A-series medical and surgical supply codes (A4000-A4999). DME suppliers and home health agencies use it to bill Medicare Part B DMEPOS and commercial payers for wound care and post-surgical antiseptic cleansing supplies.

This reference covers the code’s official description, Medicare coverage rules and 2025-2026 fee schedule ranges, the documentation a claim needs to survive an audit, the ICD-10 codes it pairs with, and how to tell A4246 apart from the adjacent A4245, A4247, and A4248 supply codes.

HCPCS Code A4246: Definition and code description

The code sits within the HCPCS Level II A-series supply codes, which the Centers for Medicare and Medicaid Services (CMS) maintains for billing durable medical equipment, prosthetics, orthotics, and supplies (DMEPOS). Most HCPCS code lookups see A4246 applied in wound care and antiseptic supply contexts by DME suppliers and home health agencies.

The unit of measure for A4246 is per pint. That matters for billing: submitting the wrong quantity unit is a common denial trigger. One pint equals 473 mL; claims billed in milliliters or ounces will not map cleanly to the code descriptor and may require additional documentation to resolve.

What products are covered under HCPCS Code A4246?

A4246 covers two distinct antiseptic solutions: Betadine and pHisoHex. These are not interchangeable from a pharmacological standpoint, but CMS has grouped them under a single supply code because both are liquid antiseptic solutions dispensed per pint for wound care, dermatology, or surgical skin preparation.

• Betadine (povidone-iodine solution): A broad-spectrum antiseptic used for pre-operative skin preparation, wound cleaning, and infection prevention. Povidone-iodine formulations at standard concentrations (typically 7.5-10%) are the products most commonly billed under A4246 in skin clinic and wound care settings.
• pHisoHex (hexachlorophene detergent solution): A bacteriostatic skin cleanser used historically for surgical scrubbing and neonatal care. Its use has declined due to neurotoxicity concerns with excessive exposure, but it remains a billable product under A4246 when medically indicated and supplied per pint.

Not every antiseptic liquid qualifies. Betadine scrub (a detergent formulation) is different from Betadine solution, and some payers treat them differently. Document the specific product, concentration, and formulation in the patient record to support the claim. Substituting an alternative antiseptic and billing A4246 without confirming it meets the descriptor is a common compliance risk, per CMS DMEPOS coverage guidance.

Medicare coverage and reimbursement for HCPCS Code A4246

Medicare may cover A4246 for DMEPOS-certified suppliers and home health agencies when the supply is medically necessary and supported by a qualifying diagnosis. Coverage is not automatic. Whether A4246 is reimbursable in a specific case depends on the applicable Medicare Administrative Contractor (MAC) Local Coverage Determination (LCD) for the jurisdiction.

Practices and suppliers billing Medicare under DMEPOS must maintain a strong compliance posture to pass MAC audits. Coverage denials for A4246 most often occur when medical necessity is not clearly established in the written order or when the diagnosis code attached to the claim does not support antiseptic wound care supply use.

2025-2026 Fee schedule rates

Medicare fee schedule allowable amounts for A4246 vary by locality. CMS publishes annual DMEPOS fee schedule files; the rates below represent general 2025-2026 national ranges. Always verify the current rate for your MAC jurisdiction via the CMS fee schedule tool before submitting claims.

Rates change annually. Never use prior-year fee schedule data as the basis for current claims. The PGM HCPCS lookup tool provides a free searchable database based on current CMS data, which is useful for quick rate verification before submitting DMEPOS claims.

Documentation requirements for billing A4246

Medicare requires documented medical necessity for every DMEPOS supply claim, including A4246. Missing or incomplete documentation is the most common reason for claim denial and post-payment audit recoupment. Using structured medical documentation forms significantly reduces the risk of claims being rejected on documentation grounds.

• Written order or prescription: A signed order from the treating physician or authorized prescriber specifying the product (Betadine or pHisoHex solution), quantity (per pint), and clinical indication.
• Diagnosis documentation: The patient record must support the ICD-10 diagnosis code submitted with the claim. The diagnosis must be consistent with the need for an antiseptic wound care supply.
• Medical necessity statement: Documentation explaining why the specific antiseptic solution is required, particularly if a less expensive alternative could serve the same purpose.
• Delivery confirmation: Proof that the supply reached the patient, such as a delivery receipt or dispensing record, required by DMEPOS billing rules.
• Supplier accreditation: The billing entity must hold valid DMEPOS supplier accreditation through a CMS-approved accreditation organization at the time of supply.

Maintaining HIPAA-compliant documentation practices across all supply records is a prerequisite. Payer audits for DMEPOS supply codes regularly request the full documentation file, including the original written order and any supporting clinical notes. Missing any of these documents can convert a clean claim into a recoupment demand.

Reduce claim denials with better documentation workflows

Pabau helps wound care and DME-adjacent practices capture supply orders, attach clinical notes, and submit complete HCPCS claims, so your billing team spends less time chasing missing documentation.

Book a demo

Billing guidelines and claim submission for HCPCS Code A4246

Claim submission for A4246 follows standard DMEPOS billing rules. Most errors happen at two points: incorrect unit reporting and missing diagnosis linkage. Using claims management software with HCPCS code validation helps catch these errors before claims leave the practice.

1. Confirm DMEPOS supplier status: Only CMS-enrolled DMEPOS suppliers can bill A4246 to Medicare. Verify your enrollment is active and your accreditation is current before submitting.
2. Identify the correct quantity: Bill in pints as supplied. Do not bundle multiple pints into a single unit claim; bill the exact quantity dispensed.
3. Attach an ICD-10 diagnosis code: The claim must include at least one ICD-10-CM code supporting the medical necessity of the antiseptic supply. See the ICD-10 crosswalk section below for commonly paired codes.
4. Use the correct claim form: Medicare DMEPOS claims typically submit on the CMS-1500 form (for professional/supplier claims). Verify your MAC’s specific requirements.
5. Check for LCD applicability: Search the CMS Medicare Coverage Database for any LCD issued by your MAC that covers wound care supply codes. Some MACs have specific criteria that narrow coverage for antiseptic solutions.
6. Submit with complete documentation: Attach or retain all supporting documents. Do not submit without the written order and delivery confirmation.

Commercial payers handle A4246 differently. Some include it in home health benefit coverage; others require prior authorization. Check your payer contracts and use the AAPC HCPCS code lookup for code-level payer policy notes. Effective patient data security tools also ensure that supply records and documentation stored for audit purposes are properly protected.

ICD-10 diagnosis codes commonly billed with HCPCS Code A4246

The ICD-10 codes below represent diagnoses most frequently paired with A4246 in wound care and antiseptic supply contexts. These pairings are guidance only. Payers may deny claims if the submitted diagnosis does not support the clinical need for the specific supply. Always verify the diagnosis is documented in the clinical record before selecting these codes.

Use the NLM clinical terminology resources to cross-reference ICD-10 codes when the primary diagnosis falls outside common wound care categories. For complex wound presentations, some MACs require the most specific available ICD-10 code rather than an unspecified “not elsewhere classified” (NEC) code.

Related HCPCS codes: A4245, A4247, and A4248

Accurate code selection depends on understanding which adjacent A-series codes describe which products. Using A4246 when another code more precisely describes the supplied item is a common coding error. The table below compares the four adjacent codes in this supply category, and A4245 has its own dedicated billing guide for closer reference.

The most common mistake in this code set is using A4246 when the patient received Betadine swabs rather than Betadine solution. Swabs belong under A4247. If the supplied item came pre-saturated in individual applicator packaging, A4247 is the correct code regardless of the active ingredient being povidone-iodine.

How Pabau supports HCPCS A4246 billing workflows

Practices and DME suppliers that provide wound care products alongside clinical services often struggle to maintain the documentation trail that DMEPOS claims require. A written order, delivery record, clinical justification note, and an ICD-10 diagnosis code all need to be present and linked before a claim can go out cleanly.

Practice management software like Pabau helps practices build that documentation trail at the point of care.

When a clinician notes that Betadine solution was supplied during a wound care visit, Pabau captures the supply detail, links it to the patient record, and supports the code selection workflow, so what the clinical team documents matches what the billing team submits.

For practices managing ongoing wound care patients, digital intake forms in Pabau ensure each visit captures the supply quantity, product used, and supervising clinician, exactly the data fields that auditors look for when reviewing A4246 claims. The inventory management software also tracks stock levels of antiseptic supplies, so billing quantities match dispensing records without manual reconciliation.

Practices operating under compliance management frameworks benefit from Pabau’s audit trail capabilities, which record who documented what and when. This is particularly useful for DMEPOS suppliers who face retrospective audit requests from MACs. Pabau’s practice management platform centralizes supply, clinical, and billing records so nothing gets lost between departments.

Continue your research

Also billing adhesive remover wipes for the same dressing change? A4456 is the code DME suppliers use for that supply.

Securing a dressing with waterproof tape instead of solution? A4452 covers that separate supply category.

Supplying a support garment or strap alongside DME? A4467 is the billing code for that item.

Also billing plaster cast supplies for the same patient? A4580 has its own billing guide.

Conclusion

Most A4246 claim denials trace back to the same root cause: documentation that does not clearly connect the antiseptic solution supplied to a specific diagnosed wound care need. Getting that link right, from written order through delivery confirmation and ICD-10 diagnosis, keeps claims clean and audits manageable.

Pabau’s claims management and digital documentation tools help wound care and DME-adjacent practices build that connection at the point of service, not as a retroactive paperwork exercise. To see how Pabau handles supply code documentation workflows, book a demo with the team.

Frequently asked questions