HCPCS Level II Basics

Before You Start

This page is for learners who have already met CPT and now need its sibling code set, and for billing and supply-chain readers who see these codes on claims, supply orders, and remittances. Read CPT Basics — Recommended — first, because HCPCS Level II is defined partly by what CPT does not describe; the "not in CPT" boundary is easier to hold once you know what CPT reports. Needing that prerequisite first is normal, not a setback.

This works as a first lesson and as an update refresher. If you are returning after time away, jump to "Update cadence and the freshness habit" and "Payer variation," which are the sections that go stale in memory.

Difficulty: Beginner to intermediate. The code set is public and simple to describe, so the concepts come quickly. The real lesson is a discipline: coverage and reporting rules live with the payer and the current official file, not in your memory, and even experienced professionals verify rather than recall. If you want a term while reading, use the Glossary — Definition.

What this is and why it matters

HCPCS Level II is the code set you reach for when what happened was not a service CPT describes, but an item, a supply, a drug given a certain way, a piece of equipment, or a transport. This page teaches what that code set is for, how it is organized at a high level, how it differs from CPT, and the three ideas that make it different to study: coverage varies by payer, medical necessity is a coverage concept and not something a coder creates, and the code set changes on a published schedule.

The specific failures this page is built to prevent are the two that learners import most often. The first is memorizing codes from an old list and trusting them; the code set is revised on a schedule, so an old code can be a claim error. The second is treating one payer's coverage rule as a universal fact; coverage, accepted codes, required modifiers, and documentation all differ by payer. Because this code set sits where documentation, payer policy, and medical necessity meet, both errors turn into denials and compliance exposure fast. So this page teaches categories and the verification habit, not a list.

What you will be able to do

• Explain what HCPCS Level II reports and distinguish it from CPT conceptually — CPT is mostly services and procedures, HCPCS Level II is mostly items, supplies, equipment, drugs, and certain services not in CPT.
• Describe the code set's general form and who maintains it, with attribution and a verification pointer.
• Recognize the major categories at a recognition level and give one fictional example concept for each.
• Explain why coverage and reporting rules for the same item can differ by payer, and what a professional verifies.
• Explain medical necessity as a coverage concept tied to documentation and payer policy, without stating any payer's criteria.
• Say why the update cadence makes old lists unreliable and what to check before relying on a code.

The simple version

Picture two lists that hang side by side. One is the class schedule — it says which lessons happened. The other is the supply and equipment list — it says what materials, equipment, and special services were provided: crutches, a wheelchair rental, an injected medication, a ride to the building. Both describe the same day, but they answer different questions.

In coding, the schedule is CPT and the supply-and-equipment list is HCPCS Level II. CPT mostly reports the services and procedures that were performed. HCPCS Level II mostly reports the things and certain services that go with care — a durable medical equipment item (reusable equipment such as a walker), a supply (a consumable such as a dressing), a drug given by injection, an ambulance transport. A payer is whoever is being asked to pay — a health plan or a government program. Medical necessity is that payer's decision that an item was reasonable and needed for the documented condition.

The analogy has limits, and the limits are the lesson. A school simply buys whatever is on its list. Healthcare does not: each payer decides which items it will cover and under what documented need, so the same item can be handled differently by two payers. And the list itself is not fixed — it is revised on a schedule, with items added, changed, and removed. So what you take from this page is the categories and the verification habit, never a list of codes to memorize.

What HCPCS Level II is for

HCPCS stands for the Healthcare Common Procedure Coding System. It is a two-level system, and the two levels are the first thing to get straight because their names overlap and cause a common confusion.

• Level I is CPT, maintained by the American Medical Association (AMA). It reports most professional services and procedures.
• Level II is HCPCS Level II, maintained by the Centers for Medicare & Medicaid Services (CMS). It reports items, supplies, drugs and biologicals given in certain ways, durable medical equipment, prosthetics and orthotics, transportation such as ambulance services, and certain other services that CPT does not describe.

So "HCPCS and CPT are the same thing" is a half-truth worth correcting: CPT is HCPCS Level I, but when people say "HCPCS Level II" they mean the separate CMS-maintained set. Throughout this page, "HCPCS Level II" always means that second level; the resource writes the level out on purpose so the two are never blurred.

Text alternative: CPT is the AMA-maintained Level I that mostly reports services; HCPCS Level II is the CMS-maintained set that mostly reports items, supplies, equipment, drugs, and transportation. The forms and maintenance differ, and both must be verified against their controlling source.

The general form is worth stating and no more: a HCPCS Level II code is a letter followed by digits, and the codes are grouped into sections by type. That is the structural shape, not a map — this page names no code values and pairs no letter with a category, because the exact structure and its contents are what you verify against the current official file, not what you memorize here. Confirm the maintenance, the two-level structure, and the general form against the current CMS HCPCS Level II pages.

The major categories — recognition level

The goal here is recognition, not assignment: enough to know roughly what a claim line is about, not enough to code it. Learn the categories as concepts, each with one fictional example described in words. None of these examples is a code, and none is a descriptor.

Text alternative: five recognition-level categories — reusable equipment, consumables, drugs and biologicals given certain ways, transportation, and temporary or other services — each shown with a fictional example described in words rather than a code. Prosthetics and orthotics are among the item types this code set also reports.

Two cautions belong with this table. First, the "temporary code" idea is not a throwaway: a temporary code is a valid code, used until it is replaced, and it is replaced on a schedule — so "temporary" means watch-for-changes, not ignore. Second, the categories themselves are what you verify against the current official index; category wording and contents change, so treat this table as a map of concepts and check the current file for what actually falls where.

Recall check: without looking back, name the five recognition-level categories, and give one everyday item or service that would fit each. Then say why "temporary" does not mean "ignorable."

Payer variation — the central lesson

This is the section the rest of the page is built to deliver, so slow down here. For the same item, four things can differ from one payer to the next: whether the item is covered at all, which code the payer accepts, whether a modifier is required, and what documentation the payer expects. A rule you learned in one course, or at one job, or from one plan, is a rule for that payer — it is not a fact about the code set.

Consider one fictional item — a home mobility device rental for Patient A. Health Plan Y has its own policy for when it covers that rental and what it wants on file. Health Plan Z, looking at the identical item, has a different policy. Neither policy is printed here, because the point is not the rule; the point is that there are two different rules, and only the specific payer's current policy tells you which one applies. Generalizing from Health Plan Y to Health Plan Z is exactly how a denial — or a compliance problem — begins.

Government-program policy adds another layer. Federal programs publish their own coverage policies under specific names — coverage determinations — and those are identified by name for verification only; a commercial payer's policy is a separate thing again. So the professional habit is narrow and strict: verify the specific payer's current policy for the specific item, and never carry one payer's answer to another.

Stop and Verify: This detail can depend on a current rule, code year, payer, employer, setting, or document. Check the controlling official source and the applicable policy before acting. For coverage and reporting of a HCPCS Level II item, that means the specific payer's current policy and the current official code file — not a remembered rule and not another payer's policy.

For the discipline behind this — how to tell which source controls which kind of question — see the learner source-literacy section of the Source Verification Standards — Standard.

Medical necessity — a coverage concept, not a coding trick

Medical necessity sounds clinical, and that is the trap. In this context it is a coverage term: it is the payer's determination that an item or service was reasonable and needed for the documented condition, under that payer's policy. The determination rests on documentation — including the diagnosis reported, which is where this connects to ICD-10-CM Basics — Helpful refresher. Diagnosis reporting supports medical necessity; it does not manufacture it.

Here is the distinction that keeps a professional safe. Take a fictional equipment order for Patient A. In the first version, the provider's documentation records the condition and the need, and the order and delivery are on file; the item's necessity is supported. In the second version, the same item is ordered but the documentation does not support the need. The professional's job in the second case is not to find a way to make it covered — it is to recognize the gap and follow the process: check the current file, check the payer's policy, confirm what the documentation actually supports, and route the question rather than reshaping it. Choosing or changing codes to create the appearance of necessity is not a coding technique; it is a fraud, waste, and abuse (FWA) concern.

Stop and Verify: This detail can depend on a current rule, code year, payer, employer, setting, or document. Check the controlling official source and the applicable policy before acting. Whether a documented need meets a payer's medical-necessity standard is the payer's determination under its current policy — not something read off the code or decided by the coder.

If a scenario ever pressures you to "pick the diagnosis that gets it covered," the compliant response is the same every time: pause, verify against the payer's policy and the documentation, follow policy, document, and escalate. See HIPAA and Compliance — Related — for the fraud, waste, and abuse framing this rests on.

Documentation for items and equipment — concept only

Items and equipment carry different documentation logic than a performed service, which is why "supplies and equipment are coded like procedures" misleads. Payers may expect things such as an order, provider documentation of the need, and proof that the item was delivered — and for equipment, the rental-versus-purchase situation can matter. Those are types of documentation, named here as concepts.

What this page will not do is list any payer's requirements, because they vary by payer and by item and they change. The professional habit is to check the specific payer's current policy for the specific item, every time, rather than working from a remembered list. Treat this section as "know that documentation requirements exist and vary," not "here is the checklist."

Update cadence and the freshness habit

The code set is updated on a published schedule, and some parts of it change more often than others — with regular releases across the year and periodic additions, revisions, and deletions (verify the current cadence). Codes are added, revised, and deleted; temporary codes are replaced. This is why an old list is unreliable: a code that was valid last year may have been revised or deleted, and a temporary code you remember may already have a replacement.

So the habit is simple and non-negotiable: a code found on an old list, a vendor sheet, or in memory is checked against the current official file before anyone relies on it. References and encoders have to be current too — an out-of-date encoder is just an old list in software. This page deliberately prints no update dates or file versions, because those go stale between reviews; instead it points you at the current CMS file. For where to find current official material, see Official Resources and Study Tools — Official resource.

Here is the freshness habit as the checklist a professional runs before relying on a HCPCS Level II code — the same order every time:

1. Current official file — is this code in the current CMS file, in its current form?
2. Payer policy — does the specific payer cover this item, and does it accept this code?
3. Documentation — does the documentation support the item and its need?
4. Modifier requirement — does the payer require a modifier for this circumstance?

Text alternative: before relying on a HCPCS Level II code, check it against the current official file, then the specific payer's policy, then the documentation, then any modifier requirement — in that order.

Recall check: name the four steps of the pre-use checklist in order, and say which step catches an old-list code.

Where modifiers come in

Modifiers are the next lesson, and this section is the hand-off. A modifier is a short add-on that reports a documented circumstance about a code — for example, aspects of an equipment rental versus purchase, or anatomic and other context (concept only; no values here). Modifiers attach to HCPCS Level II codes just as they attach to CPT codes, and HCPCS Level II has its own modifiers in addition to the CPT modifiers. As with everything else on this page, payer requirements for modifiers vary, so whether a modifier is expected is a payer-policy question.

The framing to carry into the next lesson is the one that keeps modifiers honest: a modifier reports a circumstance the documentation supports; it is never a way to get something paid. Continue to Modifiers — Next lesson — which builds on both CPT and HCPCS Level II.

What billing roles need from this page

If you are on the billing side, you meet these codes on claims, supply orders, and remittances, and your job with them is recognize-and-verify, not assign. Recognize which category a claim line is about. Check coverage with the specific payer rather than assuming it. Route coding questions — which code, which modifier — to the coders. And the bright line that applies to everyone: never add or change a code to make an item "covered." For where the two roles divide, see Medical Biller vs. Medical Coder — Related.

Understand, memorize, look up, verify

Text alternative: understand the concepts and the reasons; memorize only the stable structure and the verify-with-payer rule; look up every code and payer-specific rule; verify structure and updates with CMS and coverage with the specific payer.

Common misconceptions

Check yourself

• Say what HCPCS Level II reports and how it differs from CPT, in one or two sentences.
• Sort these fictional claim-line concepts into categories: a rented home mobility device; a package of dressings; an injected medication; an ambulance transport. For each, say item or service.
• State, in one sentence, why the same item can be handled differently by Health Plan Y and Health Plan Z.
• Explain medical necessity as the payer's determination, and say what makes "pick the diagnosis that gets it covered" a compliance problem.
• Name the four steps of the pre-use checklist in order.

Teach it back: explain to a coworker why the same piece of equipment can be handled differently by two payers. Include one distinction (HCPCS Level II versus CPT), one professional-context point (verify with the specific payer), and one thing you would check in the current official file.

Ready to move on?

• I can say what HCPCS Level II reports and why it exists beside CPT.
• I can place a fictional claim-line concept into a category and say whether it is an item or a service.
• I know coverage and reporting rules are payer-specific, and where to verify them.
• I can explain medical necessity as the payer's determination, supported by documentation, not created by code choice.
• I check the current official file before trusting any code.

This page does not qualify anyone to assign codes, determine coverage, or submit claims; it teaches concepts and verification habits only.

If you got something wrong

If two ideas stay tangled — item versus service, coverage versus code — put them side by side and compare before more practice.

In the profession

Coders, billers, durable-medical-equipment suppliers' staff, pharmacy and infusion billing staff, and ambulance billing staff all use this code set, and they use it differently. What controls real work is the same short list every time: payer policy, official coverage determinations, employer policy, and the current official file. Billing roles recognize categories and verify coverage; nobody changes a code to obtain coverage.

In certification

HCPCS Level II is a domain in professional coding credentials and a daily-work area for billing credentials, because supply, equipment, drug, and transportation claims are where billing staff meet it. For the billing-side view — recognizing categories on claims and verifying coverage with the payer inside a claims-lifecycle model — see the CBCS Certification Review — Certification connection. For the professional-coding view, where this code set sits beside CPT in the foundations sequence, see the CPC Certification Review — Certification connection. Domains are cited as broad public-outline areas only; verify each outline. This page does not align to any exam.

In careers

Job postings phrase this as "HCPCS coding," "DME billing," "infusion billing," or "supply charge capture." This page gives you the concepts; real proficiency requires the current official file, the payer policies you work with, and employer training. No employment outcome is implied. For orientation, see Medical Biller vs. Medical Coder — Career connection.

For continuing learning

Returning learners refresh the categories and the payer-variation principle first, then check what changed: the current update files, any category changes, and the specific payer policies they work with. A six-month return needs the update-cadence and payer-variation sections; a years-away return needs the full page, then Modifiers — Next lesson. This resource provides no approved continuing-education credit or renewal credit.

Study options

• 5-Minute Review: what HCPCS Level II reports versus CPT, and the verify-with-payer rule.
• 15-Minute Study: the categories plus payer variation.
• Full Lesson: every section — medical necessity, documentation types, update cadence, the modifiers hand-off, and the billing-role boundary.
• Refresher or Deep Dive: read the current update files against the official CMS source; the coverage-determination concept is the optional deeper reading.

If you remember only five things: HCPCS Level II reports items, supplies, drugs, equipment, and certain services not in CPT; the categories are a recognition map, not a code list; coverage and reporting rules vary by payer, so you verify; medical necessity is the payer's documented-need determination, never made by code choice; and you check the current official file before trusting any code.

Check the source yourself

Not every source that mentions a HCPCS Level II item controls what happens on a real claim. The current official CMS file controls what a code is and whether it exists in its current form. The specific payer's current policy controls whether that payer covers the item and how it wants it reported. A vendor's cheat sheet, a forum answer, or another payer's policy may raise a useful question, but none of them controls the answer you can act on.

Freshness note: the code set is periodically updated (verify the current cadence); payer policy is context-dependent and frequently updated; the underlying concepts on this page are stable.

Source challenge: you need to know whether a fictional item is covered for Patient A under Health Plan Y, and how to report it. You have four sources: Health Plan Y's current coverage policy, a vendor's cheat sheet, a forum answer, and Health Plan Z's policy. Which one controls the answer you can act on, which are acceptable only as leads to verify, and why? Point yourself to Official Resources and Study Tools — Official resource — for the current official material.

Frequently asked questions

What is the difference between HCPCS and CPT?

HCPCS is a two-level system. Level I is CPT, maintained by the AMA, which mostly reports services and procedures. Level II is the separate set maintained by CMS, which reports items, supplies, drugs and biologicals given in certain ways, equipment, transportation, and certain other services not in CPT. When people say "HCPCS Level II," they mean the second level.

What does HCPCS Level II cover?

At a recognition level: durable medical equipment, supplies, drugs and biologicals reported in certain circumstances, transportation such as ambulance services, and certain temporary and other services — including prosthetics and orthotics among the item types. It covers the things and certain services that go with care, rather than the performed services CPT reports.

Do all payers accept the same HCPCS Level II codes?

No. Coverage, which code a payer accepts, whether a modifier is required, and what documentation is expected can all differ by payer. Verify the specific payer's current policy, and do not carry one payer's rule to another.

What is medical necessity?

It is a coverage concept: the payer's determination that an item or service was reasonable and needed for the documented condition, under the payer's policy. Documentation supports it. A coder or biller does not create medical necessity by choosing codes.

How often do HCPCS Level II codes change?

On a published schedule, with some parts updated more often than others and codes added, revised, and deleted (verify the current cadence). Because of that cadence, an old list is unreliable; check the current official file before relying on any code.

Where to go next

• Recommended next: Modifiers — Next lesson.
• If you struggled: CPT Basics — Remediation — "CPT vs. HCPCS Level II" section, then retry the classification prompts here.
• If you already know this: Modifiers — Next lesson — and its payer-variation section.
• If your goal is billing: Medical Biller vs. Medical Coder — Career connection, then HIPAA and Compliance — Related.
• If your goal is coding: Modifiers — Next lesson, then the practice sets.

Sources to verify before relying on this page

• CMS official HCPCS Level II pages and the current code files — control the maintenance, two-level structure, general code form, category, update-cadence, and temporary-code statements.
• CMS official coverage-determination resources — control the coverage-determination concept statement and the names used for identification only.
• AMA official CPT information — controls the statement that CPT is HCPCS Level I and is maintained by the AMA.
• HHS-OIG or CMS fraud, waste, and abuse educational materials — control the FWA framing used for the medical-necessity concept.