Your product appears on the PDAC list. You are not cleared to bill. You are at the starting line and what you do with that result in the next sixty seconds determines whether your claim survives a RAC audit two years from now.
The PDAC Product Classification List (PCL) is the authoritative database of HCPCS codes and products that have been through Palmetto GBA’s coding verification process. Most billing teams know it exists. Very few know how to read what it actually shows them. This guide covers how the list is organized, how to search it correctly, and most critically how to interpret the results table column by column, including a worked knee brace example that shows exactly where a common misread happens and what it costs. If you are starting from scratch and need to understand what PDAC approval means for Medicare billing before touching the list, read that first.
What the PDAC Product Classification List Actually Is
The PCL is not a list of products approved for Medicare reimbursement. Most billing guides treat it that way. That framing is the source of more claim errors than any single coding mistake.
The PCL is a record of products that have completed PDAC’s coding verification process meaning Palmetto GBA has confirmed which HCPCS code a specific product maps to. Coverage determination is an entirely separate question, answered by Local Coverage Determinations, medical necessity criteria, and the patient’s clinical documentation. A product can sit on the PCL with a verified status and still be denied if the physician’s notes do not support medical necessity. Coding verification and coverage are not the same thing. Treating them as the same thing is how providers end up with post-payment recoupment on claims they thought were clean.
Palmetto GBA maintains the PCL under its national contract with CMS. The list updates monthly new verifications are added, code crosswalks are published, and status changes appear. Most billing teams check a product once when they first add it to their catalog and never look again. That single gap creates the audit exposure that shows up years later.
One more terminology distinction worth locking in: PDAC is the contractor. DMECS the Durable Medical Equipment Coding System is the interface you use to search the PCL. Billing staff use both terms interchangeably. That habit causes real confusion when a compliance question comes up and no one can agree on which database was searched or which result was read.
How the PCL Is Organized Before You Search Anything
The PCL supports three search paths: manufacturer name, product or model name, or HCPCS code. The right path depends on what you already know.
Billing coordinators typically start with the HCPCS code they have a code on a prescription or CMN and need to know which products are verified for it. Purchasing managers more often search by product name or manufacturer when evaluating a new supplier. Compliance staff auditing an existing product line usually work backwards from a model number to confirm the code assignment is still current.
Before running any search, one structural distinction matters.
Mandatory vs. Non-Mandatory Coding Verification
Not every HCPCS code requires PDAC verification before billing. The PCL covers products in both mandatory and non-mandatory categories and the rules are not the same for both.
L-coded orthotic braces knee braces, ankle braces, hip braces, spinal orthotics fall under mandatory coding verification. If a product is billed under an L-code and it does not appear on the PCL with a verified status for that exact code, the claim is non-compliant. There is no workaround, no good-faith exception, no grace period.
Other product categories have PDAC verification available without it being a hard billing requirement. If your product mix includes any L-coded orthotics which covers the majority of DME providers working with orthopedic practices, chiropractors, or home health agencies mandatory verification is the category that governs everything you do. (Verify the current full list of mandatory categories at dmepdac.com before adding any new product line to your billing workflow.)
How to Search the PDAC Product Classification List
This section covers getting into the PCL and running a search. For a full walkthrough of the DMECS interface — including the tool’s structure, the PDAC vs. DMECS distinction, and how to interpret results across different code types — the guide on how to use the DMECS lookup tool covers that in detail.
- Go to com and open the DMECS application.
- Select “Product Classification List.” Do not select “Code Verification Request” that is a manufacturer-facing submission workflow, not a provider verification tool.
- Enter your search term. A model number is the most reliable input because it targets a specific SKU. Manufacturer name and product name searches return broader result sets that require more filtering and carry more room for error.
- Review the results table. This is where most billing teams stop reading carefully. This is where most misreads happen.
- Confirm the HCPCS code in the result matches the code on your claim exactly. Not approximately. Not in the same code family. Character for character.
How to Read the Results Table Column by Column
Every PCL result returns the same set of fields. Here is what each one tells you and what to do with it.
Manufacturer. The company that submitted the product for PDAC coding review. If the manufacturer in the result does not match the manufacturer on your packing slip, you are looking at a different product. Do not assume close enough.
Product Name / Model Number. This is the unit of approval — and it is the column that decides audits. PDAC verifies specific products at the SKU level. Not categories. Not product lines. Not brands. Two products from the same manufacturer, with nearly identical names, can carry different HCPCS codes. If the model number in the PCL result does not match the model number on your delivery documentation exactly — including any alphanumeric suffix — you do not have verification for that shipment. This is the column billing staff skim. It is the column RAC auditors read first.
HCPCS Code. The code PDAC assigned through the verification process. This must match the code on your claim. A result showing L1832 when you are billing L1833 is not a near-miss. It is a miscoded claim.
Approval Status. Whether the verification is current, inactive, or transitioned. The four statuses you will encounter are covered below.
Effective Date. When the coding determination was made. A product verified several years ago may have been affected by a subsequent code update or crosswalk. The effective date tells you where to start looking for whether anything has changed.
Notes / Restrictions. This column carries prior authorization flags, code-specific limitations, and crosswalk notices. It is frequently empty. When it is not empty, it is not administrative filler — it is a billing condition. Read it every time.
Background Check
DSHS requires an IdentoGO fingerprint background check for many applicants. Whether this applies to your specific ownership structure depends on the details of your application. Call DSHS at 512-834-6727 and confirm before you submit this is a five minute call that prevents a three week delay.
What Each Approval Status Means
Verified. PDAC has confirmed this product maps to this HCPCS code. For mandatory categories, this is the only status that clears a product for billing.
Crosswalked. The original code has been retired or replaced. The product has been transitioned to a new code. Billing the pre-crosswalk code after the crosswalk has been published is a claim error — regardless of whether your supplier flagged the change. The crosswalk entry references the new code, but you must re-verify the product under that new code before filing another claim.
Not Listed. The product has either not been submitted for coding verification or was submitted and not verified for this code. For mandatory categories, this ends the conversation. You cannot bill the code.
Pending. A verification request is in process. You cannot bill under this code until a verified status is returned. Pending is not close enough.
(Confirm the exact status terminology displayed in the current DMECS interface before building any internal billing procedures around this language — Palmetto GBA updates the tool periodically.)
Worked Example Reading a Knee Brace L-Code Entry
Here is a scenario that plays out in billing departments more often than anyone tracks.
A billing coordinator is processing orders for a knee brace her clinic recently started ordering from a new supplier. The prescription carries L1833 a knee orthosis, rigid, without joints, prefabricated. She opens DMECS, searches by product name, and finds a result. The product appears in the list. She reads “verified” somewhere in the row, marks it confirmed, and moves on.
What she did not check: the HCPCS code column shows L1832, not L1833. The supplier’s product was verified for a different code a custom-fabricated knee orthosis with different documentation requirements and a different reimbursement rate. The brace looks identical. The codes are not interchangeable. Every claim filed under L1833 for that product is miscoded.
This error will not surface at submission. It will not surface at the first post-payment review. When it surfaces — during a RAC audit, when the auditor pulls the DMECS record and compares it against the claims the result is recoupment on every affected claim, plus interest, plus a flag for expanded review of the provider’s L-code billing history.
A correct read of that same search looks like this: the results table returns the manufacturer name matching the packing slip, the model number matching the product suffix exactly, the HCPCS code showing L1833, status showing Verified, effective date current, and the notes column empty. That is cleared to bill. Any variation from that picture requires a call to the supplier before the claim goes out not after.
One more scenario worth walking through: the results table shows a crosswalk notice. The product was originally verified for L1833, but a code update transitioned it. The crosswalk entry references the new code. If you have been billing L1833 since before the crosswalk was published and your supplier never flagged the change you have been filing incorrect claims since the publication date. That date is timestamped in the monthly update listing and is fully visible to any auditor running a retrospective review.
What Most Billing Teams Get Wrong About the PDAC List
The most expensive assumption in DME billing is straightforward: if a supplier sells a product under an L-code, it must be verified for that code.
Suppliers have no regulatory obligation to disclose PDAC status proactively. The verification burden sits entirely with the billing provider. A supplier can list a product in their catalog under L1833, ship it to your patient, and provide a delivery confirmation — and none of that constitutes PDAC verification. The verification lives in DMECS. Only the billing provider is responsible for checking it before the claim is filed.
The second assumption that costs providers money: verification is permanent. It is not. Codes are crosswalked. Products are recategorized. A product your billing team verified eighteen months ago may be assigned to a different code today. The monthly PCL Update Listing is where those changes are published — and it is the resource almost no billing department outside of dedicated compliance teams reviews on any regular schedule.
Here is the hard version of this: if your supplier cannot produce a PDAC verification letter for a specific model number on request, that is not a documentation gap you can work around. That is a compliance risk sitting on every claim you have filed for that product. The billing and audit consequences of using non-PDAC-approved products go well beyond claim denial — into post-payment recoupment, expanded audit scope, and in documented cases, exclusion referrals.
How to Use the Monthly PCL Update Listing
The DMECS Update Listing is published monthly at dmepdac.com. It records every change made to the PCL during the prior period: new verifications, crosswalked codes, status changes, and products removed from the list.
Most providers treat PDAC verification as a one-time step in supplier onboarding. A defensible compliance posture treats it as an ongoing monitoring function. Any billing coordinator responsible for L-coded products should review the update listing each month for every code category in their active billing mix. This takes less time than disputing a single recoupment.
For purchasing managers evaluating a new supplier’s catalog: check the update listing for the relevant HCPCS codes in the month before placing your first order. A product verified when your supplier printed their catalog may have been crosswalked since. Catching that before the first shipment costs nothing. Catching it after twelve months of billing costs considerably more.
Who This Is For
This verification workflow is built for you if:
- You are a billing coordinator or purchasing manager at a licensed DME provider
- You are adding new orthopedic brace SKUs to your active product offering
- You are onboarding a new supplier and need to confirm their catalog before the first order ships
- You are preparing documentation ahead of a RAC audit or post-payment review
This is not the right fit if:
- You are purchasing equipment for personal use
- You are an ecommerce seller without Medicare enrollment
- You are looking for wholesale pricing to stock your own inventory without a DME license
What Happens When You Partner With Ava Medical Supply
Every product in Ava’s catalog is verified at the SKU level before it is made available to our partners. Not the manufacturer’s category. Not the product line. The specific model number being ordered. PDAC verification letters are available on request for any product in our catalog and our team flags code updates and crosswalks so you are not discovering them during an audit.
When you reach out, here is what happens:
- We verify your DME license and NPI typically within one business day
- We onboard your practice to our ordering portal two to three business days
- You place your first order we ship direct to your patient with full delivery documentation included
Most providers are placing their first order within one week. No minimum order quantities. No long-term contracts. If you have compliance questions before your first order, our team answers them before you commit to anything.
Frequently Asked Questions
The PDAC Product Classification List (PCL) is a database maintained by Palmetto GBA that records the HCPCS codes assigned to specific DME products through PDAC’s coding verification process. It is the authoritative reference for confirming that a product has been coded correctly before billing Medicare but it is a coding record, not a coverage determination. A product can be on the list and still be denied if medical necessity documentation does not support the claim.
Access the PCL through the DMECS application at dmepdac.com. Search by manufacturer name, product model number, or HCPCS code. Model number searches return the most specific results and reduce the risk of pulling a result for a similarly named but differently coded product. Once results appear, confirm the HCPCS code column not just the product name matches what you are billing.
For mandatory code categories which includes all L-coded orthotic braces a product that does not appear on the PCL with a verified status cannot be billed under that code. It either has not been submitted for coding verification or was submitted and not approved. Contact your supplier before filing any claims for that product. Do not assume the supplier’s catalog listing under an L-code constitutes verification.
No. PDAC coding verification confirms the correct HCPCS code for a product. Medicare coverage is determined separately by Local Coverage Determinations, medical necessity criteria, and the patient’s clinical record. Verification and coverage are two different checks. Both must pass for a claim to hold up.
The PCL is updated monthly. New verifications, code crosswalks, and status changes are published in the DMECS Update Listing at dmepdac.com. Reviewing this listing monthly for your active code categories is the most straightforward way to catch code changes before they affect live claims.
The PCL is a provider-facing lookup you use it to confirm whether a product has already been verified for a specific code. A Code Verification Request is a manufacturer-facing submission it is how a manufacturer asks PDAC to review and assign a code to a new product. Providers verify. Manufacturers submit. These are separate workflows inside DMECS and serve entirely different purposes.
Ready to Order PDAC-Approved Products Without Managing Verification Yourself?
What Happens When You Contact Ava
If you are a licensed DME provider ready to offer compliant, PDAC-approved equipment without carrying the supplier verification burden on your own — Ava Medical Supply was built for exactly this.
Every product we supply comes with SKU-level PDAC verification, HIPAA-compliant direct-to-patient shipping, and complete delivery documentation on every order. You focus on your patients. We handle the compliance infrastructure behind the shipment.
No minimum orders. No long-term contracts. Questions about PDAC compliance or state licensing requirements before your first order? Our team answers those before you commit to anything.
