HCPCS code P9022 – Washed red blood cells, one unit

Key takeaways

HCPCS code P9022 covers one unit of washed red blood cells, billed as a single line per unit transfused.

Washing strips plasma proteins, so payers expect an indication such as IgA deficiency, a severe allergic reaction, PNH, or neonatal transfusion.

Payers ask for two documents most often, a physician order naming washed RBCs and the blood bank record confirming the wash.

P9022 pays for washing only, so irradiation, leukoreduction, and deglycerolization each carry their own P-series code.

Practice management software like Pabau connects clinical documentation to billing workflows, so the record behind a code travels with the claim.

HCPCS code P9022 pays for one washed unit of red blood cells

HCPCS code P9022 covers red blood cells, washed, each unit. It is a Level II code maintained by the Centers for Medicare and Medicaid Services (CMS). The code sits in the P-series, which covers pathology and laboratory products. One washed unit equals one billed line.

The code reports the product, not the act of giving it. P9022 also sits in the same block as the other blood product codes, running from P9021 through P9039.

The AAPC HCPCS code lookup confirms P9022 as an active, non-deleted code. P-series codes are reviewed every year, so check the current CMS HCPCS update file before you bill.

Why a unit gets washed, and what the chart has to say

Washing is reserved for patients who react to plasma. Washed red blood cells are packed RBCs rinsed with isotonic saline to remove residual plasma, platelets, and white cell debris. The process cuts plasma protein content by roughly 99%.

Standards from the Association for the Advancement of Blood and Biotherapies (AABB) point to five situations where washed RBCs are clinically indicated:

• IgA deficiency with anti-IgA antibodies. Patients who lack IgA and carry anti-IgA antibodies face anaphylaxis risk from plasma IgA. Washing removes the triggering protein.
• Severe allergic or anaphylactic transfusion reactions. Washing is the next clinical step after a documented severe reaction to plasma proteins, once premedication has already failed.
• Paroxysmal nocturnal hemoglobinuria (PNH). Plasma components can worsen complement activation in PNH. Washed RBCs lower the complement load, though protocols vary by institution.
• Neonatal transfusion. Intrauterine and neonatal exchange transfusions use washed products to limit the hyperkalemia risk carried by stored blood.
• Recurrent febrile non-hemolytic reactions. Some patients keep reacting to leukoreduced products, and washing becomes the additional step.

Whichever reason applies, the chart has to name it. A payer reading the claim sees only the diagnosis and the order, so the indication is what turns a washed unit into a payable line.

P9021 or P9022 comes down to what the blood bank did

Pick the code from the processing step, not from the patient. P9021 covers red blood cells, each unit, with no additional processing. P9022 covers the same base product after saline washing by the blood bank. If the unit was not washed, P9021 is correct.

Billing P9021 on a unit the blood bank washed costs the hospital money. The facility absorbs a processing step it performed and never charged for. Repeat that pattern often enough and it also invites a compliance review.

P9022 stops at washing, so other processing needs its own code

P9022 covers the washing step and nothing else. Irradiation, leukoreduction, CMV-negative selection, and antigen-negative selection all fall outside it. Each of those steps may carry its own P-series code when it is performed.

Check these adjacent codes before you default to P9022:

P9038 is the code when irradiation is the only step performed. For a unit that was both washed and irradiated, check current CMS guidance and your payer policy.

Some payers allow both codes on one unit and some treat one as inclusive of the other. Our other HCPCS code guides break down the neighboring P-series entries in the same detail.

Two documents decide whether a P9022 claim survives

Missing paperwork is the top denial trigger for P9022. Payer audits flag the same two records again and again. One is a physician order that says “washed.” The other is a blood bank processing record confirming the wash.

• Physician order. Must specify “washed red blood cells” or “washed RBCs.” A generic order for packed RBCs does not support P9022, and the order should reference the clinical indication.
• Clinical indication in the medical record. The diagnosis or reaction history that justifies washing belongs in the chart before the transfusion date. Payers routinely reject documentation added afterward.
• Blood bank processing record. The blood bank documents the wash, the saline volume, and the unit identifier. This record is separate from the administration record.
• Transfusion administration record. Captures who gave the product, the time, vital signs, and any reaction. Required for every blood product claim.
• Patient consent. A signed transfusion consent belongs in the chart, per institutional policy and most payer requirements.

Notice that four of the five records are created by someone other than the biller. That is the whole problem with P9022. The claim is assembled from a lab system, a chart, and a charge master, and it only holds together when those three agree.

Medicare pays P9022 through OPPS, not a physician fee schedule

Payment depends on the care setting. Hospital outpatient departments are paid under the Outpatient Prospective Payment System (OPPS), where blood products are assigned to Ambulatory Payment Classification (APC) groups. The APC that covers washed RBCs reflects the processing cost that P9021 does not carry.

Inpatient claims work differently. Blood product costs are generally bundled into the Diagnosis-Related Group (DRG) payment, so they are not separately billable there.

Confirm your facility’s cost reporting approach with the revenue cycle team. For current outpatient rates, pull the OPPS Addendum B file, which lists the APC rate for every payable code.

Commercial payers vary widely. Some mirror the Medicare OPPS rates. Others pay cost-based or negotiated amounts tied to what the hospital spends on acquiring and processing blood.

Review each contracted payer’s blood product schedule once a year, because the washed-versus-unwashed differential is not recognized uniformly.

Prior authorization stays rare until the transfusion is elective

Medicare requires no prior authorization for inpatient blood product transfusions under standard DRG payment. Most acute hospital outpatient transfusions escape it too. Commercial payers are far less consistent.

Three situations are the ones that usually trigger a commercial authorization requirement:

• Elective outpatient transfusions booked in advance, rather than emergent inpatient use
• Ambulatory infusion center settings, where some plans authorize the administration separately from the product
• High-cost courses of care, such as a patient needing multiple washed units across several visits for chronic hemolytic anemia

Send the clinical documentation with the request when authorization is needed. That means the confirmed diagnosis, the order specifying washed RBCs, and any prior transfusion reaction records. Lab confirmation of IgA deficiency belongs in the packet too.

Why P9022 claims get denied, and how to fix each one

P9022 rejections cluster around a short list of root causes. Reading the pattern before you submit beats appealing afterward, and the table below pairs each cause with the fix that clears it.

Sorting rejections by claim adjustment reason code (CARC) turns single denials into a pattern you can act on. A run of CARC 50 denials points at medical necessity, which usually means the washing indication never reached the chart. CARC 197 points at a missing authorization.

CARC 4 is worth reading carefully, because it reports a modifier problem rather than a wrong code choice. Structured denial management workflows make those groupings visible quarterly instead of annually.

How a P9022 claim moves, from order to payment

Follow one washed unit through the building and the failure points become obvious. Each stage below creates a record, and the claim only survives if that record reaches the next stage.

Two stages deserve extra attention. Stage three is where a default charge master mapping quietly sends every red cell unit to P9021. Stage five is where an underpaid line gets written off instead of appealed, because nobody compared the paid amount to the washed rate.

Run this check before you submit a washed RBC claim

Five checks catch almost every P9022 problem while the claim is still yours to fix:

• One line per unit. Two washed units on the same date need two P9022 lines. Most payers process a single unit per line and deny the rest as duplicates.
• Order language matches the code. Read the order back. If it says “washed RBCs,” P9022 is right. If it says “PRBCs,” the claim needs the order corrected, not the code forced.
• Processing codes map correctly. Where a blood bank LIS assigns processing codes, washing should map to P9022, irradiation to P9038, and standard issue to P9021. Re-verify the mapping each year.
• Date of service is the transfusion date. The blood bank may wash a unit hours ahead. Bill the administration date, not the processing date.
• Payer bundling rules checked. Some payers roll blood product costs into per-diem or DRG payments even where CMS allows separate billing.

Teams building their own charge capture rules can pull descriptors from the NLM HCPCS Level II API. It is free, and it updates with the annual file.

How Pabau keeps the clinical record and the claim in one system

Most billing teams work across at least two systems. The documentation that justifies a code lives in one. The claim that uses it is built in another. Those two only meet when a payer sends something back. That is the handoff P9022 exposes, and it is the same handoff that costs private practices money on far more routine codes.

Practice management software like Pabau closes that distance by keeping patient records, treatment notes, invoices, and claims software for practices in one place. When a charge is raised, the note behind it is already on the same patient record. Nobody has to reconstruct the supporting documentation weeks later.

For a practice, the payoff is fewer claims held up while somebody hunts for a record. Coding decisions still belong to your coders and your clinical teams. What changes is how quickly the evidence behind each decision can be found and sent.

Keep documentation and claims in one system

Pabau connects clinical documentation to billing workflows, so the record supporting a charge sits with the claim that uses it. See how practices submit cleaner claims without chasing paperwork between systems.

Book a demo

Conclusion

P9022 is an easy code to bill and an easy one to lose. The washing happened, the product was given, and the money still disappears because the order said “RBCs” or the processing record never left the lab. Neither of those is a coding problem.

So fix the two handoffs rather than the code sheet. Get the ordering physicians writing “washed,” and get the blood bank’s processing entry into the billing system automatically. Do that and the appeals queue thins out on its own.

The wider lesson holds well beyond blood products. Claims fail where records are handed between systems, so the fewer handoffs you keep, the fewer denials you work. Book a demo to see how Pabau keeps documentation and claim submission on one record.

Continue your research

Need to understand denial patterns across blood product codes? Denial management in healthcare covers how to categorize and resolve systematic claim rejections by CARC code.

Want to tighten your pre-submission claim review? Clean claim submission outlines the checks that cut first-pass denial rates across every code type.

Looking for a primer on where blood product billing sits in the revenue cycle? What is revenue cycle management explains the path from charge capture to payment posting.

Frequently asked questions