HCPCS code P9072 – Pathogen-reduced or bacterial-tested pheresis platelets

Key takeaways

HCPCS code P9072 was deleted on January 1, 2018, and belongs only on claims for earlier dates of service.

It covered pheresis platelets that were either pathogen reduced or rapid bacterial tested, billed one unit per unit transfused.

Pathogen-reduced platelets now bill as P9073, while bacterial-tested units take their base pheresis code plus P9100.

Platelets bill under revenue code 0384 on the institutional claim, not revenue code 0390.

The blood bank’s processing record, not the transfusion order, decides which platelet code applies.

HCPCS code P9072 is a retired code for safety-treated platelets

HCPCS code P9072 described one unit of pheresis platelets that was pathogen reduced or rapid bacterial tested before transfusion. CMS deleted it on January 1, 2018. So it’s still the right code for older dates of service, and the wrong one for any claim since.

The code sat in the P-series of HCPCS Level II, the range for pathology and laboratory services. That range includes the blood products a blood bank supplies.

Its official descriptor reads: Platelets, pheresis, pathogen reduced or rapid bacterial tested, each unit.

Its neighbors cover irradiated, leukocyte-reduced, and CMV-negative platelets. Each one names the processing applied to the unit. You can browse the whole family in our HCPCS procedure codes library.

P9072 covered two kinds of pheresis platelet unit

Two conditions had to be true. The platelets came from a single donor by apheresis, and they went through one of two safety steps.

• Pathogen-reduced platelets: Units treated with pathogen reduction technology (PRT), such as the INTERCEPT Blood System. It uses amotosalen and UVA light to inactivate pathogens in the platelet concentrate.
• Rapid bacterial tested platelets: Units checked with a rapid assay before transfusion. The Verax Platelet PGD test was the most common choice.
• Single-donor collection: Both types had to come from one donor by apheresis. Pooled platelets from several whole-blood donations were coded separately.
• Per-unit billing: The descriptor says “each unit.” A patient who received two units needed two units of P9072 on the claim.

Notice what the claim never showed. It didn’t say which safety step the blood bank used, because both routes shared one code. That blind spot is exactly what CMS fixed in 2018.

Several platelet products never qualified for P9072

If a unit missed either condition above, P9072 was the wrong code. These are the mix-ups billing teams ran into most.

• Pooled random donor platelets: These combine several whole-blood platelet concentrates. They take other P-series codes, even when the pool was pathogen reduced.
• Leukocyte-reduced-only pheresis platelets: Leukoreduction alone doesn’t qualify. Use P9035 for these units instead.
• Irradiated pheresis platelets: Irradiation isn’t pathogen reduction. Irradiated units have their own codes, such as P9036.
• Physician office transfusions: Hospital outpatient departments bill most blood product P-codes under OPPS. Office billing for infusion products follows a different payment route.
• Any date of service from January 1, 2018: The code no longer exists, so the payer rejects the line as invalid.

CMS deleted P9072 on January 1, 2018, and split its job in two

CMS removed P9072 in its January 2018 HCPCS update. The reason was simple. One code described two different safety methods, and payers couldn’t tell them apart.

AHA Coding Clinic for HCPCS covered the change in its first-quarter 2018 issue, reference H181015. The guidance is titled “New and deleted HCPCS codes for pathogen-reduced platelets and pathogen testing for platelets.”

Under it, P9073 took over pathogen-reduced platelets. Meanwhile, P9100 replaced Q9987 as the code for pathogen testing of platelets.

For historical claims and audits, keep three points in mind:

• A late or corrected claim dated before January 1, 2018 keeps P9072, as long as it was right at the time.
• Before you rebill, match the date of service against the HCPCS file in force that quarter.
• P9072 on a claim dated January 1, 2018 or later usually comes back with claim adjustment reason code (CARC) 181. That code means the procedure code was invalid on the date of service.

Replacement codes for P9072 depend on what the blood bank did

There’s no single replacement for P9072. P9073 is the only product code that succeeded it, and it covers pathogen-reduced units only.

Rapid bacterial tested platelets never got a product code of their own. Instead, you bill the base pheresis platelet code, plus P9100 for the test.

The date of service settles the first question, and the blood bank record settles the second. The diagram below puts both steps side by side.

Always confirm the code against the HCPCS file for the date of service. The AAPC HCPCS code lookup and the CMS HCPCS overview both show current and past code status. Check one of them before you rebill.

Pathogen reduction and bacterial testing are coded differently

Treating the two methods as interchangeable causes most platelet coding errors. They happen at different points in the unit’s life. The blood bank also records them in different places.

Here’s how that plays out on a claim. Say a patient receives two INTERCEPT-treated units on March 4, 2025. The claim carries P9073 with two units.

Now change one detail. The two units were leukocyte reduced and passed a Verax PGD test instead. This time the claim carries P9035 for two units, plus P9100 to report the testing.

A coder who only sees “platelet transfusion” in the chart will likely default to a generic pheresis code. The fix is a query to the blood bank’s laboratory information system (LIS). If your facility transfuses often, build that query into your regular compliance audit.

Neighboring platelet codes differ by one processing step

P9072 sat among several pheresis platelet codes. After using the deleted code itself, picking the wrong neighbor is the next most common error.

The rule is simple in principle. List every step the blood bank applied, then find the code whose descriptor names exactly those steps. The PGM Billing HCPCS lookup tool lets you confirm a descriptor in seconds before you submit.

How a P9072 claim moved through Medicare OPPS

While P9072 was active, hospital outpatient departments billed it under the Outpatient Prospective Payment System (OPPS).

The code went on the institutional claim, the UB-04 or 837I. It paired with revenue code 0384, blood platelets. Revenue code 0390 is for blood storage and processing, a different category.

Here’s the path one unit took from order to payment:

1. The physician orders platelets and states the clinical reason.
2. The blood bank issues the unit and records its processing, such as PRT or a PGD test.
3. Nursing records the transfusion, with start and end times.
4. Charge capture turns the transfused unit into a claim line with the HCPCS code, revenue code, and units.
5. The 837I goes to the Medicare administrative contractor, where code-validity and unit edits run.
6. The remittance advice comes back as paid, adjusted, or denied.

A few payment rules applied during the code’s active period:

• APC assignment: P9072 was assigned to an Ambulatory Payment Classification (APC) for blood and blood products. Payment followed the APC rate, not a fee schedule.
• Medical necessity: Payers expected a physician order that supported the transfusion. A missing indication was an easy reason to deny the line.
• Prior authorization: Most payers didn’t require it for P9072 itself. Some did for elective transfusions, so check the payer’s policy for the date of service.

Working an appeal on an old P9072 claim? Start with the OPPS final rule for that year and the Medicare Claims Processing Manual, Chapter 4. After that, the remittance advice from the original claim period is your best record of what the payer did.

Five records support every billed platelet unit

Missing records were the top reason P9072 claims failed after clinical review. When you audit a historical claim, confirm each billed unit has all five of these:

• Physician transfusion order: Signed, and naming the product type and clinical reason. A generic order for “platelets” invites questions in a post-payment audit.
• Blood bank issue slip: Shows the unit number, product type, processing method, and time of issue. It’s the main source for choosing the P-series code.
• Pathogen reduction label (PRT units): The bag label or certificate showing the unit went through a recognized PRT system.
• Rapid bacterial test result (PGD units): The result slip, with the lot number, test date, negative result, and the technician’s name.
• Transfusion administration record: Nursing notes confirming the unit went in, with start time, end time, and vital signs. Never bill a unit that was issued but not transfused.

Keep these records linked to the patient’s encounter rather than spread across departments. Then an auditor’s request takes minutes, not a week of chasing the lab.

Most P9072 denials came from five avoidable errors

P9072 claims tended to fail in the same five ways. Its successor codes carry most of the same risks, so the table still applies to platelet claims today.

Denials on a deleted code are the easiest ones to prevent. A short pre-bill review of code validity, records, and administration catches most of them.

Run this checklist before you submit a platelet claim

• The date of service falls inside the code’s active period.
• The blood bank record names the processing step for every unit.
• The code’s descriptor matches those steps exactly.
• Units billed equal units transfused, not units issued.
• Each platelet line carries revenue code 0384.
• The physician order says why the patient needs platelets.

If your team already works from a clean claim checklist, add these six lines to it.

How Pabau keeps billing codes current and claims traceable

Many billing teams still check codes against a downloaded HCPCS file and a spreadsheet of past denials. That holds up until a code changes and nobody updates the sheet.

Practice management software like Pabau keeps coding inside the patient record instead. Its claims management software includes CPT and HCPCS lookup libraries, refreshed with official code releases. Claim forms pre-fill from the service already recorded. Pabau also checks that required claim fields are complete before you can send.

In the US, claims go out through Claim.MD, with real-time eligibility checks, claim status tracking, and remittance posting. So when a line comes back with an invalid-code denial, the remittance, the record, and the resubmission sit in one place.

Keep billing codes current and claims traceable

Pabau’s claims management pulls codes from lookup libraries refreshed with official releases. It pre-fills claims from the patient record and tracks each claim through to remittance.

Book a demo

Conclusion

Treat P9072 as a date-of-service question first. If the transfusion happened before January 1, 2018, the code stands, and your job is proving the unit with the blood bank record. If it happened later, the code is gone.

From that point, the processing record decides between P9073 and a base code plus P9100. Querying the blood bank on every platelet claim slows billing a little. Skipping the query costs far more when the claim comes back with CARC 181 or fails an audit.

Book a demo to see how Pabau keeps code lookups current and ties every claim to the record behind it, from order to remittance.

Continue your research

Billing a pathogen-reduced unit today? HCPCS code P9073 covers the product code that replaced P9072 for pathogen-reduced pheresis platelets.

Need to understand how denial codes are structured? Denial codes in medical billing explains the CARC and RARC framework used on remittance advices for blood product claims.

Working through a payer’s remittance on a rejected transfusion claim? Electronic remittance advice covers how to read and act on 835 transaction data to resolve HCPCS billing disputes.

Looking to reduce upstream coding errors before they reach the payer? Clean claim submission outlines the pre-bill checks that keep blood product claims out of the denial queue.

Frequently asked questions