HCPCS code C1839 – Artificial iris implant

Key takeaways

HCPCS Code C1839 reports an iris prosthesis, the artificial iris implant, on hospital outpatient department and ASC claims only.

C1839 covers the device alone, so it is billed alongside CPT 0616T, 0617T or 0618T, chosen by the lens work done during surgery.

Every C1839 claim needs the device invoice or UDI in the record, and a missing one is the most common reason for denial.

Pass-through or packaged payment for C1839 is set each year in the CMS OPPS final rule, so check the current addendum before quoting a rate.

Pabau’s claims management software keeps device documentation, modifiers and claim status for each C1839 claim in one place.

What HCPCS Code C1839 covers

HCPCS Code C1839 is the CMS code for an iris prosthesis, an artificial iris implanted when a patient’s iris is missing or damaged. Its official descriptor is simply “Iris prosthesis,” unchanged since the code took effect on January 1, 2020.

CMS created the code for the CustomFlex ArtificialIris, which the FDA approved in May 2018 for congenital aniridia and acquired iris defects. C1839 belongs to the C-series of HCPCS Level II codes, the temporary codes CMS maintains for hospital outpatient and ASC billing.

CMS reviews C-codes through the annual Outpatient Prospective Payment System (OPPS) final rule and quarterly updates. The quarterly files on the CMS HCPCS overview page list each C-code’s descriptor and payment status.

C1839 reports the device only. The surgery goes on the same claim under one of three CPT Category III codes, effective July 1, 2020:

• 0616T: iris prosthesis inserted without removing the crystalline lens or intraocular lens (IOL), and without inserting an IOL.
• 0617T: iris prosthesis inserted with removal of the crystalline lens and insertion of an IOL.
• 0618T: iris prosthesis inserted with secondary IOL placement or an IOL exchange.

Approved billing settings: ASC and hospital outpatient

C-codes like C1839 are setting-restricted. They appear only on claims from ASCs and HOPDs, two outpatient settings that CMS pays under separate but related payment systems.

The Outpatient Code Editor (OCE) flags claims when C-codes appear in the wrong billing context. An OCE edit doesn’t always mean an automatic denial, but it does trigger manual review and adds weeks to adjudication.

Submitting C1839 on a claim type the OCE doesn’t accept for C-codes is one of the easiest ASC billing errors to prevent.

Medicare coverage and C1839 reimbursement

Medicare covers C1839 under OPPS when the iris implant procedure is covered and medical necessity is documented. How CMS pays for the device depends on its pass-through status in the current OPPS final rule. C1839 entered pass-through status when it took effect in January 2020.

• Pass-through status (if applicable): CMS grants pass-through payment to new devices for about three years. During that window, the device is paid separately from the procedure at a rate tied to cost data. The status shows as a payment indicator in the OPPS addendum and the Outpatient Code Editor specification.
• Packaged payment: Once pass-through status expires, the device cost is packaged into the Ambulatory Payment Classification (APC) for the procedure. No separate line-item payment is made for the device code itself.
• ASC separate payment: In the ASC setting, certain device-intensive procedures qualify for separate device payment. Whether C1839 gets it in a given year depends on the ASC covered surgical procedures list. The paired procedure has to appear there with a device-intensive designation.
• MAC jurisdiction variability: Local Coverage Determinations (LCDs) from Medicare Administrative Contractors (MACs) can affect coverage of the iris implant procedure. That, in turn, decides whether C1839 is payable. Check your MAC’s LCD database before assuming national coverage applies.

Reimbursement rates for C1839 change year to year. Pull the current OPPS or ASC fee schedule from CMS at the start of each calendar year instead of carrying old figures forward. Quoting a dollar amount without the CMS addendum and year behind it is a common compliance risk in billing documentation.

Documentation requirements for HCPCS Code C1839

A C1839 claim without complete supporting documentation will deny. The record has to establish both the procedure and the device, and tie them to a covered diagnosis.

Pabau’s claims management software lets billing teams attach and track device documentation against the procedure claim. That lowers the chance of a clean claim being held for a missing file.

• Operative note: Must identify the procedure, the surgeon, the date, the facility and the device implanted. Generic “device placed” language isn’t enough. The note must name the iris prosthesis or refer to an attached implant log.
• Device invoice or purchase order: CMS and most commercial payers require evidence that the billed device is the device actually used. An invoice showing the device name, lot number and unit cost satisfies this in most MAC jurisdictions.
• Unique Device Identifier (UDI): FDA regulations require UDI capture for implantable devices. For Medicare billing, the UDI should appear in the medical record. Some MACs have begun requiring UDI documentation as a condition of payment for implant codes.
• Implant log: ASCs are required to maintain an implant log as part of CMS Conditions for Coverage. The log entry for the procedure should match the device described in the operative note and on the claim.
• ICD-10-CM diagnosis code: At least one diagnosis code must establish medical necessity for both the procedure and the device. The diagnosis section below covers the codes that commonly support C1839.

Put together, a complete C1839 claim pairs the right procedure code with the device line and its paperwork, as the diagram below shows.

Diagnosis codes that support C1839

ICD-10-CM codes must reflect the condition that makes the iris implant medically necessary. For C1839, that is the iris defect itself. Congenital aniridia is coded Q13.1, and a congenital iris coloboma is coded Q13.0. Diagnosis codes on C1839 claims typically fall into one of these categories:

Always map diagnosis codes to the current ICD-10-CM fiscal year. A code deleted or revised this year creates a claim-level edit, and not every clearinghouse catches it before submission. Review the medical billing workflow for your facility to confirm where ICD-10 validation happens in your claim build.

Prior authorization requirements

Medicare fee-for-service doesn’t require prior authorization for most implant device codes at the national level. Medicare Advantage plans and commercial payers frequently do. Several commercial payers publish a dedicated iris prosthesis coverage policy with their own medical necessity criteria.

• Medicare fee-for-service: No blanket prior authorization requirement applies to C1839, but check the current LCD for the iris implant procedure with your MAC. Some procedures that use implant device codes fall under CMS’s HOPD prior authorization program.
• Medicare Advantage: Each MA plan sets its own prior authorization rules. Contact the plan’s provider relations line or check its online authorization lookup tool before scheduling.
• Commercial payers: Most commercial payers require prior authorization for implantable devices above their internal cost threshold. Submit clinical notes, the proposed ICD-10 diagnosis and the operative plan with the request.
• Urgent or emergency procedures: When a procedure can’t wait for prior authorization, document the clinical urgency in the record. Notify the payer within 24 to 48 hours under the plan’s concurrent review policy, then submit a retrospective authorization request. Keep the urgency documentation attached to the claim file.

Payer policies update quarterly, and a procedure that didn’t need prior authorization last year may need it now. Build a payer-authorization check into your annual charge master review, so the list stays accurate. Your medical billing compliance process should include a periodic check of each payer’s prior authorization schedule.

Modifiers used with C1839

Modifiers explain the circumstances of a claim and prevent automatic denials from bundling or bilateral edits. These are the modifiers most often applied with implant device codes in the ASC and HOPD setting:

Incorrect modifier use is one of the faster routes to a Medicare audit. Apply a modifier only when the clinical scenario matches its definition, and confirm the record supports every modifier on the claim. On a clean claim for C1839, each modifier should make sense from the operative note alone.

Adjacent codes frequently confused with C1839

C1839 often shares a claim, and sometimes a surgery, with other eye and device codes. Picking the wrong one is easy when you work from memory instead of the current CMS descriptor file. These are the codes most often confused with C1839:

An iris-supported lens and an iris prosthesis sound alike but describe different devices, so check the operative note before choosing between C1839 and V2631.

When the right code is still unclear, compare descriptors side by side in the AAPC HCPCS code lookup or the PGM Billing HCPCS tool. Then confirm against the CMS source file, which wins whenever a commercial lookup tool lags behind a quarterly update.

Common denial reasons and how to avoid them

C1839 denials follow recognizable patterns, and most trace back to missing documentation rather than coding errors. These are the four denial types billing teams see most often on C-code device claims:

Appeals and reconsideration process

When Medicare denies a C1839 claim, redetermination is the first formal appeal level. Acting quickly and systematically gives the best chance of reversal without escalating to higher appeal tiers.

1. Request a remittance advice (RA): Identify the specific CARC and RARC denial codes on the RA. They tell you exactly what the MAC cited as the reason, which determines your appeal strategy.
2. Gather supporting documentation: Pull the operative note, device invoice, UDI record and any prior authorization confirmation. Attach the LCD or NCD policy language that supports coverage.
3. File a redetermination within 120 days: Submit the request in writing, or through the MAC’s online portal, within 120 days of the initial denial. Include a cover letter citing the specific policy language that supports the claim.
4. Escalate if denied again: A second denial moves the claim to reconsideration, handled by a Qualified Independent Contractor (QIC). Timelines and documentation requirements are more formal at this stage.
5. Track appeal status: Use your MAC’s provider portal to monitor redetermination status, because untracked appeals often lapse past their deadline. Our guide to denial management in healthcare covers the full appeal ladder for Medicare facility claims.

How Pabau keeps C1839 device claims clean

Many ASC and HOPD billing teams build a C1839 claim from three places. The operative note sits in the clinical record, the device invoice sits with purchasing, and the claim lives in a clearinghouse. Each handoff is a chance for the invoice or UDI to go missing.

Pabau keeps treatment notes, patient records and claims in one system. Your team attaches the device documentation to the procedure claim, applies the RT or LT modifier and follows the claim’s status without switching between tools.

That means fewer claims held for a missing file, and less time spent rebuilding a record when a payer asks for proof of the implant.

Keep C1839 claims clean from day one

Pabau’s claims management tools help outpatient billing teams attach device documentation, apply the right modifiers, and track claim status without switching between systems. See how it works for ASC and HOPD workflows.

Book a demo

Conclusion

C1839 is one of the easier device codes to get right. Its descriptor names a single device, and it pairs with just three CPT codes. Payment depends on the paperwork that travels with it.

So move the checks to the front of the process. Confirm the setting, match the lens work to 0616T, 0617T or 0618T, and attach the invoice or UDI before the claim leaves. That takes a few minutes per claim, far less than the redetermination it prevents.

Book a demo to see how Pabau keeps device documentation and claim status together for your outpatient billing team.

Continue your research

Need to understand how denials get resolved at the claim level? Denial codes in medical billing breaks down CARC and RARC codes and how to respond to each.

Not sure whether a device has its own code? HCPCS Code C1889 explains when the not-otherwise-classified device code applies.

Curious how the broader revenue cycle connects to device billing? Revenue cycle management explained maps every stage from patient registration through payment posting.

Frequently asked questions