HCPCS code C1773: Insertable retrieval device billing guide

Key takeaways

HCPCS code C1773 describes an insertable retrieval device used to recover fractured medical devices, such as a broken guide wire or a catheter fragment.

Only hospital outpatient departments and ambulatory surgery centers bill C1773, and payment runs through Medicare OPPS.

Check the current OPPS Addendum B before you submit, because a packaged device earns no separate payment.

Documentation has to name the fractured component, identify the device, and give the clinical reason retrieval was needed.

Practice management software like Pabau keeps treatment notes, device details, and claims in one record, so nothing has to be reconstructed later.

HCPCS code C1773 covers a retrieval device, insertable, used to retrieve fractured medical devices. That parenthetical is the whole boundary of the code.

Something broke inside a vessel, and a device went in after it. That is the only story C1773 tells. Report it for a routine snare case and the claim comes back.

The code itself is the easy part. Setting, payment status, and the procedure note are what decide whether the line gets paid.

C1773 covers one device in one scenario

The full descriptor reads “Retrieval device, insertable (used to retrieve fractured medical devices).” Nothing else qualifies, and the parenthetical is what separates C1773 from every other snare or grasping device in the series.

C1773 is a Level II HCPCS code maintained by the Centers for Medicare and Medicaid Services, known as CMS. It sits in the assorted devices, implants, and systems range, C1760–C2615. That range exists for outpatient facility billing, not for physician professional services.

Code tables shorten the descriptor to “Ret dev, insertable.” Cath lab and interventional radiology coders usually meet that abbreviation first, so keep the long version within reach when you are choosing between neighboring codes.

When the code applies, and when it doesn’t

C1773 applies the moment a device is inserted to retrieve hardware that has already fractured. A guide wire snaps during a cardiac catheterization. A catheter tip embolizes to a pulmonary vessel. A port catheter breaks in an oncology patient. In each case, someone has to go in and get the fragment back.

The device is usually a snare or a grasping catheter, passed through a sheath and steered under fluoroscopy. C1773 pays for that device. The retrieval itself is reported separately, with its own CPT code.

Scenarios that commonly support the code include the following.

• Retrieval of a fractured guide wire fragment from a coronary or peripheral vessel
• Recovery of a broken catheter tip that has embolized to the pulmonary artery
• Removal of a dislodged intravascular filter component
• Capture of a fractured pacemaker lead conductor during lead revision
• Retrieval of a broken port-catheter fragment in an oncology patient

AAPC’s HCPCS Level II reference places this device category in interventional radiology, cardiology, and vascular surgery. Teams that place and maintain long-term venous access, including infusion centers, meet the same broken hardware in their own patients.

Now the other half. A standard snare used in a planned procedure is not C1773, even though the device looks identical. Confirm with the physician that something fractured first. Coding a routine case as a retrieval invites a denial, and sometimes an audit flag.

What Medicare pays for C1773 in 2026

There is no single national dollar figure to quote. C1773 is paid under OPPS, so what you see depends on the device’s status for the year and on your geographic wage index.

CMS sets outpatient device payment each year in the OPPS final rule, then publishes the detail in the OPPS addenda. Confirm the current treatment against the CMS hospital outpatient PPS pages for your MAC jurisdiction, since rates move annually and vary by locality.

Two payment routes are possible. Device cost is often packaged into the Ambulatory Payment Classification, or APC, for the primary procedure. Some devices carry pass-through status instead and are paid separately for a limited period. Addendum B tells you which one applies.

Commercial coverage is a separate conversation. Plans set their own device policies, so never carry an OPPS rule across to a commercial contract without checking. Some MAC jurisdictions also publish Local Coverage Determinations, known as LCDs, that add medical necessity conditions.

How the charge reaches the claim

A device code rarely starts life with the coder. It starts in the procedure room, and it passes through four sets of hands before anyone submits anything.

1. The team records the device as it is opened, against the case, in the supply system.
2. The chargemaster maps that item to a revenue code and to C1773, then posts the charge to the account.
3. The physician dictates the procedure note, naming the fractured component and the device used to retrieve it.
4. Coding reconciles the note against the posted charges and adds the CPT code for the retrieval.
5. Billing confirms the device’s OPPS status for the year, then releases the outpatient claim.

Most C1773 problems trace back to step one or step three. A device nobody recorded never reaches the claim at all. A note that says only “snare used” leaves the coder guessing about what fractured.

The handoffs are also where data gets re-keyed. Where the clinical system and the billing system are joined up, that risk drops, which is one practical argument for EHR integration in procedural settings.

Coverage turns on medical necessity

Medicare covers C1773 when the record shows the retrieval was clinically necessary and the encounter happened in an eligible setting. Coverage is not automatic. The device also has to be an insertable retrieval device, not a diagnostic or therapeutic tool used for something else.

Four things decide the outcome for most billing teams.

• Medical necessity: the retrieval has to be clinically required, not elective or exploratory
• Setting: only HOPDs and ASCs may report C1773, and physician offices may not
• MAC jurisdiction: LCDs differ by contractor, so read the policy that governs your region
• Payer rules: commercial plans are not bound by OPPS and may deny or require prior authorization

Billing rules that keep the claim clean

Putting the code on the claim is the last step, not the first. Three rules cover almost every C1773 line, and a fourth list covers the errors that undo them.

Only facilities bill C1773

C1773 is a facility-side device code. Hospital outpatient departments and Medicare-certified ASCs report it. Practices billing under the Physician Fee Schedule do not report device codes for devices the facility supplied.

Pair the device with a procedure code

C1773 goes on the claim alongside the CPT code for the retrieval itself, usually a foreign body retrieval code from the vascular intervention range. The device code carries the supply. The procedure code carries the service. A claim with one and not the other is incomplete.

Edits from the National Correct Coding Initiative can apply when a device code meets certain procedure codes. Run that check before submission rather than after a bundling denial.

One unit per device

Report one unit of C1773 for each insertable retrieval device used. If a first device failed and a second went in, both can be reported. Each one needs its own line in the note, though, and its own device details.

The mistakes that cost the most

• Reporting C1773 for a standard snare or basket catheter used in a planned procedure
• Billing C1773 from a physician office, which is not an eligible setting for this code
• Leaving the clinical indication out of the note, so the payer sees no medical necessity
• Expecting separate payment for a device that Addendum B shows as packaged this year

Documentation a reviewer will accept

Thin documentation is the shortest route to a denied C1773 claim. A reviewer needs to see that a fractured device was retrieved, not simply that a retrieval device appeared in the case. That distinction is what medical necessity review turns on.

A complete file for C1773 carries five elements.

• Procedure note: states the indication, names the fractured component, and confirms the device went in to retrieve it
• Device identification: device name, manufacturer, and lot or catalog number
• Imaging or fluoroscopy report: confirms the foreign body was there and that retrieval succeeded
• Encounter details: date of service, attending physician, patient identifiers, and the CPT procedure code
• Medical necessity statement: explains why retrieval was needed at this encounter

Paper and part-digital workflows tend to lose one of the five, usually the device details. Capturing them on a structured form at the point of care closes that off. That is much of the practical case for digital clinical forms in procedural settings.

Run this check before you submit

Five questions catch most of what goes wrong with this code.

• Does the note name the fractured component, and not only the retrieval?
• Is the device identified by name, manufacturer, and lot or catalog number?
• Does the claim carry the CPT procedure code as well as C1773?
• Have you checked this year’s status for the device in Addendum B?
• Did the encounter happen in a hospital outpatient department or an ASC?

Five yes answers, and the line is ready to go. One no, and fixing it now is far cheaper than appealing later.

How C1773 differs from the codes around it

Neighboring codes in the C-series describe other pieces of the same case, which is exactly why they get mixed up. The table below sets out the ones coders meet most often alongside C1773.

Other codes in the range cover the rest of the access story. A steerable guiding sheath falls under C1766, and the device used to close the access site afterwards is C1760. Reading them together is the quickest way to see where one code stops and the next one starts.

What to re-check each quarter

C1773 has been stable through recent CMS updates, and no descriptor change or termination has been published for 2026. Stability is not permanence, though. CMS releases HCPCS Level II changes quarterly and reviews the C-series in the annual OPPS rulemaking cycle.

Codes in this range really do disappear. C1720 was terminated years ago, and billers were pointed to replacement codes. Verify effective dates in the current CMS quarterly file rather than in a third-party database, which can lag behind the official release.

How Pabau keeps device details and claims together

In a lot of outpatient teams the note lives in one system, the device record in another, and the claim in a third. Details get re-keyed at every handoff. That is where device codes quietly fall apart.

Practice management software like Pabau brings clinical records, documents, and billing into one patient record. Structured intake and consent forms capture the detail during the visit. Whoever builds the claim then reads what the clinician wrote, not a summary of it.

Pabau’s claims management software then checks the fields an insurer needs before anything goes out. Membership numbers and authorization codes have to be complete, and the send option stays disabled until they are. A status dashboard shows where each claim sits after that.

The record side is handled by compliance management. Role-based access decides who can open a chart, audit trails record who changed what, and treatment notes and photos are timestamped as they are created.

So when a payer asks who documented a procedure and when, the answer is already there. Procedure-led teams already work this way, from IV therapy practices to busy outpatient departments.

Keep device details and claims in one record

Pabau brings treatment notes, documents, and billing into a single patient record. Claims are checked for the fields your insurer needs before the send option unlocks.

Book a demo

Conclusion

C1773 is a narrow code with a narrow test. Something fractured, and a device went in to get it out. Put that in the note and most of the billing follows on its own.

What trips teams up is procedural rather than clinical. A device nobody recorded, a status indicator nobody checked, a setting that was never eligible. All three are cheaper to catch on the way out than to argue about in an appeal.

If your notes, device details, and claims live in three different places, that check is manual every single time. Book a demo to see how Pabau holds them in one record for outpatient billing teams.

Continue your research

Billing another device code from the same range? C1727 works through the same OPPS questions for a balloon tissue dissector.

Need the rules for an implantable device instead? C1789 covers documentation and payment for an implanted prosthesis.

Wondering how pass-through payment works in practice? C1756 explains it alongside UB-04 reporting for a catheter code.

Billing consumable supplies as well as devices? A4207 shows how supply codes are handled differently from facility device codes.

Tightening up records before an audit? HIPAA compliance for medical offices covers the documentation and security habits behind clean claims.

Frequently asked questions