Your biller flags a wound care claim that came back with zero allowed dollars on one line. The visit was documented, the nurse spent fifteen minutes on it, and the payer paid the E/M but not the debridement. Nine times out of ten in that scenario, the line in question is 97602 — and the denial is not an error. The 97602 CPT code description covers non-selective debridement performed per session, and under most payer rules that service is packaged rather than separately paid. This guide is for the administrator, biller, or compliance lead who has to explain that to a clinician, fix the workflow, and then deal with the part nobody talks about: the wound photographs.

What the 97602 CPT Code Description Actually Says

CPT 97602 describes removal of devitalized tissue from wound(s), non-selective debridement, without anesthesia — examples in the code text include wet-to-moist dressings, enzymatic agents, and abrasion. The descriptor bundles in topical application(s), wound assessment, and instruction for ongoing care. It is billed per session.

Three operational facts fall out of that descriptor, and they drive everything downstream:

  • Per session, not per wound. Four wounds treated in one encounter is still one unit. Your charge capture screen should make it impossible to enter a quantity greater than one.
  • No surface area component. Unlike the selective debridement codes, the 97602 CPT code description contains no square-centimeter measurement and no add-on code for additional area.
  • Anesthesia excluded. The descriptor specifies "without anesthesia," which is one of the boundaries clinicians use when distinguishing this family from other debridement families.

Note what the descriptor does not do: it does not tell you which code fits a given patient. Code selection follows the documented clinical work — depth, tissue type, technique, instrumentation — and that determination belongs to the treating clinician, not to your billing queue.

Per Session Means One Unit — Build the Edit

If your charge entry allows units above one on this code, you will eventually submit a claim with three units on it, and you will eventually have to refund it. Ask your EHR administrator or billing vendor to hard-cap the units field. That is a fifteen-minute configuration change that removes a recurring overpayment risk.

Why 97602 Usually Produces No Separate Payment Line

Under the Medicare Physician Fee Schedule, 97602 has historically carried a bundled status — meaning payment is subsumed into another service and no separate amount is allowed when a physician or other practitioner bills it. Hospital outpatient departments and other settings apply their own packaging logic. Commercial payers often mirror Medicare, but not universally.

Do not take that on faith from a blog post, including this one. Pull the current relative value file and payment status indicator yourself from the CMS Physician Fee Schedule and confirm the current-year status for every code your wound care service line touches. Status indicators change; your fee schedule build should be re-verified each January.

The practical consequence: reporting 97602 is frequently about documenting that the service occurred — for encounter records, for utilization data, for medical necessity support of the visit as a whole — rather than about generating revenue. Your clinicians need to hear that framed correctly. "It doesn't pay" invites people to stop documenting it. "It doesn't pay separately, and it still has to be in the record" is the message.

Who Is Allowed to Report It in Your Practice

Assign this explicitly. Depending on setting and payer, the service may be furnished by a physician, an advanced practice provider, a nurse under supervision arrangements, or a therapist under a therapy plan of care. Each of those paths carries different supervision, plan-of-care, and modifier obligations. Write the local rule down, name the supervising provider, and review it annually — do not let it live in one biller's memory.

The Documentation Elements Your Template Should Force

Because the descriptor references wound assessment, topical application, and patient instruction, a note that omits those elements is thin. Your template should require, at minimum:

  1. Wound identification and location — enough specificity that a records reviewer can match note to image to order.
  2. Tissue characteristics before and after — described by the clinician, in the clinician's words.
  3. Technique used — the descriptor's examples (wet-to-moist, enzymatic, abrasion) are examples, not a checklist; the note should say what was actually done.
  4. Instruction provided for ongoing care, and to whom — patient, caregiver, home health nurse.
  5. Time or session boundaries, if your payer contracts require them.
  6. Who performed the service and who supervised.

Then audit ten charts a quarter against that list. Ten charts is small enough that someone will actually do it and large enough to surface a pattern.

Wound Photographs Are PHI, and They Are Where Practices Leak

Here is the part that turns a billing article into a compliance article. Wound care generates images. Images with a date, a body location, and a patient identifier are protected health information — full stop. If a clinician relied on that image to make or document a care decision, it also sits inside your designated record set.

Ask three questions this week:

  • What device captures wound photos in your practice?
  • Where does the image land first — an EHR capture module, or a camera roll?
  • How does it get from wherever it lands into the chart, and is it deleted from the intermediate location?

In most small and mid-sized practices, the honest answer to question two is "a personal phone." That creates a shadow archive: hundreds of identifiable clinical images on a device you do not control, backed up to a consumer cloud account you have no agreement with, surviving the employee's departure.

The Text Message Habit

A nurse photographs a wound and texts it to the physician for guidance. Operationally sensible. From a Security Rule standpoint, you have just transmitted ePHI over a channel with no access controls, no audit trail, no retention control, and a copy resting on two devices indefinitely.

You do not fix this with a memo. You fix it by giving staff a sanctioned capture path that is faster than the phone camera, then enforcing it. If your EHR has a mobile capture app that writes directly to the encounter, deploy it, train on it, and turn on the audit log. If it does not, that is a real gap to raise with the vendor at renewal.

Every Vendor That Touches Wound Data Needs a Written Agreement

Map the hand-offs behind a single wound care encounter. In a typical practice the list runs longer than people expect:

  • The EHR host or cloud infrastructure provider
  • Your billing company or revenue cycle vendor
  • A wound imaging or measurement application, if you use one
  • A telehealth or remote wound review platform
  • The scanning and shredding contractor handling paper wound logs
  • A product manufacturer's "reimbursement support" line, if it reviews your charts to advise on coding
  • Any consultant performing coding audits on your wound care service line

Each of those is creating, receiving, maintaining, or transmitting PHI on your behalf. Each one needs a business associate agreement in place before the first record moves. HHS publishes sample business associate agreement provisions that establish the required floor — permitted uses, safeguards, subcontractor flow-down, breach notification timing, and return or destruction at termination.

The gap is almost never the EHR, which arrives with a BAA in the contract packet. The gap is the small stuff: the imaging app someone downloaded, the audit consultant retained for one project, the courier. If you are staring at a vendor list with holes in it, generate a signature-ready Business Associate Agreement through the six-step wizard — it exports to PDF and DOCX, it is a one-time purchase with no subscription, and it closes the gap in an afternoon instead of a quarter.

Who Does Not Need a BAA

Do not paper the wrong relationships. A home health agency or skilled nursing facility receiving wound records to continue treatment is a covered entity in its own right; that is a treatment disclosure, not a business associate arrangement. Same for the surgeon you refer to. Sending a BAA to a treating provider signals that your program does not understand the rule.

The 30-Day Clock When a Patient Asks for Wound Photos

Wound care patients request their images more often than you might guess — for second opinions, for disability claims, for litigation. Under the HIPAA right of access, you have 30 calendar days from the request, with one 30-day extension available if you notify the individual in writing of the reason and the new date.

Three details your records staff should have memorized:

  • If the images are readily producible in the form the patient requests — say, a digital file rather than printed pages — you must produce them that way.
  • Fees must be reasonable and cost-based. Search and retrieval labor is not chargeable.
  • Images stored outside the EHR still count if they are part of the designated record set. "It's on the nurse's phone" is not a legal answer; it is an admission.

The OCR right of access guidance is the authority to keep bookmarked at the front desk. Right-of-access enforcement has been a sustained OCR priority for years, and the fact patterns are almost always mundane: a request that sat in a shared inbox, an unreturned voicemail, a fee that included staff time.

A 30-Day Cleanup for Your Wound Care Service Line

Week one. Pull the current-year status indicator for 97602 and every adjacent debridement code from the CMS fee schedule. Correct your charge master. Cap units at one.

Week two. Audit ten wound care charts against the documentation elements above. Report findings to the clinicians as a template problem, not a personal one.

Week three. Inventory image capture. Ask every clinical staff member, individually, where wound photos currently live. Expect surprises. Establish the sanctioned path and set a deletion deadline for everything else.

Week four. Reconcile your vendor list against your BAA file. Anything on the list without a signed agreement gets one or gets cut off. Document the review date — auditors care as much about the cadence as the paperwork.

None of this is about the code itself. The 97602 CPT code description is four lines of text; you can memorize it in a minute. The operational risk sits in what surrounds it — the photographs, the hand-offs, the requests, and the vendors nobody wrote down.

Next Step

Start with the vendor list, because it is the item with legal exposure and no clinical judgment required. Pull your wound care hand-offs into a single sheet, identify which relationships are business associate relationships, and produce the missing agreements in one sitting — six steps, PDF and DOCX export, one-time purchase. If your broader documentation set is also overdue, automated risk analysis and policy generation covers the rest of the file your next auditor will ask for.