DEEP DIVE
📄 The 3 documents BCBS wants before it pays your midlevels

The EOB says "missing modifier." The modifier isn't the problem.

We're seeing a wave of NP and PA claims bounce off BCBS NC and BCBS SC with a remark code that points straight at a specific modifier. The natural reflex is to grab the AS modifier and resubmit. That's the wrong fix, and it can turn a cash-flow problem into a compliance one. When your midlevel is the primary biller on the claim, the denial isn't really about coding at all. It's about what the payer has on file for that provider. 

We've watched payers roll out changes like this before, testing a tighter rule in one or two state plans before taking it wider. A smaller market is a low-risk place to see how practices respond and tune the denial logic, and once it holds up there it tends to spread. 

What AS actually means

Modifier AS has one job. The official HCPCS descriptor reads "Physician assistant, nurse practitioner, or clinical nurse specialist services for assistant at surgery," per Moda Health's assistant-at-surgery policy, which quotes the CMS descriptor. It flags that an NP or PA scrubbed in and assisted a surgeon on a procedure that allows an assistant. That's the whole scope of the modifier. 

So when your midlevel performed the service as the primary, rendering provider and you append AS, you've described a role they didn't play. HCPCS descriptors govern correct use, and the CMS HCPCS Level II framework doesn't leave room to repurpose an assistant-at-surgery modifier as a "midlevel did this" flag. Putting AS on a primary service is a role mismatch, and on a post-payment audit it reads as a miscoded claim and an invitation to recoup.

Worth a quick clarification, because the two get confused: SA is not AS. Modifier SA marks a nurse practitioner rendering a service in collaboration with a physician. It's payer and Medicaid-specific, it isn't in the CMS national HCPCS file, and Medicare doesn't recognize it for payment. SA flags collaboration, not surgical assistance, so it won't cure a credentialing gap any more than AS will.

The stakes here aren't trivial, because midlevels carry real procedure volume in derm. A JAAD analysis found NPs and PAs independently billed 11.51% of dermatologic procedures, more than four million in total, with injections, simple repairs, and biopsies leading the list. A run of midlevel denials hits a measurable slice of the practice's collections.

Why a credentialing gap shows up as a coding remark

This is the part most billing teams miss, and it's why the AS reflex is so common. When a claim comes in under a midlevel's own NPI for a service the payer hasn't fully tied to that provider's credentialing record, the adjudication system doesn't always return a clean "provider not authorized for this service" message. It often kicks back a generic modifier or coverage remark, because the edit that failed lives upstream of the coding logic. The remark code describes the symptom the system surfaced, not the gap that triggered it. A biller reading "missing modifier" reasonably reaches for a modifier, and the real issue, sitting in provider enrollment, never gets touched.

The distinction that trips people up is the difference between two separate "on file" concepts. State boards in NC and SC require written practice agreements for NPs and supervisory arrangements for PAs. In NC, an NP's collaborative practice agreement is generally kept on-site and available for board inspection rather than continuously filed with the boards. That's "on file" with the state. It is not the same as the payer having the midlevel's scope and agreement records loaded against their enrollment. The denial is about the payer's file, not the board's. Your midlevel can be fully compliant with the state and still get bounced by BCBS because the plan's credentialing record doesn't yet reflect the scope of what they're billing.

Our credentialing team is tracking this on both BCBS NC and BCBS SC right now. Neither state issues a standalone "dermatology scope" form, so there's no single document to drop in. The procedure scope is defined by the collaborative or supervisory agreement plus documented training and competency, and what the payer needs is that picture connected to the midlevel's enrollment under their own NPI. NC and SC state both also have a scope of practice dictated by the state. Midlevels can apply for a modified scope of practice to be approved by the state. This often entails dermatologic surgeries and repairs and should be on file as well.

Takeaways

  1. Pull the agreement. Confirm the NP's collaborative practice agreement or the PA's supervising-physician agreement exists, is current, and complies with NC or SC law. This is document one, and it's the foundation the other two rest on.

  1. Confirm the scope covers what you're billing. Check that the board-recognized scope, the agreement plus documented training and competency, actually covers the specific dermatologic procedures on the denied claims. There's no separate derm scope form, so the agreement and competency records have to do that work.

  1. Verify the payer's enrollment record, then resubmit. Confirm the midlevel's individual BCBS enrollment under their own NPI reflects that scope. Submit or update it through the provider enrollment portal, or hand it to your external credentialer if they own that step. Once it's on file, send the denied claims back for reprocessing and watch the timely-filing windows so aged claims don't fall off.

Bottom line: NC and SC are separate Blue plans, which is what makes this worth watching. Two independent BCBS entities tightening midlevel scope documentation at the same time looks less like one plan's quirk and more like a direction of travel. We're seeing it in two states today, and patterns like this rarely stay contained to two.

What did you think of today's edition?

Login or Subscribe to participate

UPCOMING EVENTS + REMINDERS
📆 Mark your calendars:

  1. AAD 2026 Innovation Academy — July 16-19, 2026 (New York, NY). The American Academy of Dermatology's summer meeting, with hands-on sessions on coding, documentation, and practice management. Details at AAD Meetings & Education.

    2. ICD-10-CM FY2027 code set takes effect — October 1, 2026. New diagnosis codes go live each October 1, so summer is when to review the posted FY2027 files and update your EHR, superbills, and coder training. Posted at CDC/NCHS ICD-10-CM.

    3. CY2027 Medicare Physician Fee Schedule proposed rule — expected July 2026. CMS issues the next-year payment proposed rule each summer, opening a roughly 60-day comment window that affects dermatology RVUs and the conversion factor. Track it at the CMS Physician Fee Schedule.

    4. MIPS 2026 mid-year check-in — ongoing through summer 2026. The performance year is underway, so verify eligibility and reporting method and run a mid-year MIPS pull. Check your status at QPP / MIPS Overview.

Until next week,
The Practice Layer, powered by Clarity RCM

Built by the people who do this every day.

Clarity RCM manages revenue cycle for 200+ dermatology practices across 42 states. It's all we do. See how we work.

Reply

Avatar

or to participate

Keep Reading