
Need Support?

If you have ever tried to get a next-generation sequencing panel paid for correctly on the first pass, you already know the punchline of this article. It almost never happens by accident. NGS billing sits at the intersection of some of the most complicated corners of the CPT and HCPCS code sets, a prior authorization landscape that changes payer by payer and sometimes month by month, and a documentation standard that is stricter than almost anything else in laboratory medicine.
That combination is exactly why so many laboratories, oncology practices, and genetic testing companies lose real revenue on tests they performed correctly. The science works. The billing doesn’t.
This guide walks through the three places where NGS panel billing most often breaks down: choosing between a Proprietary Laboratory Analyses (PLA) code and a Tier 2 molecular pathology code, navigating prior authorization thresholds that vary by payer and by panel size, and avoiding the denial traps that quietly drain reimbursement even when the test itself was medically appropriate. Along the way, we’ll cover the current coding landscape, what CMS and major commercial payers actually require in 2026, and how a laboratory can build a claims process that holds up under scrutiny, whether in-house or with specialized NGS billing experts.
Next-generation sequencing used to be billed the way most molecular tests were billed: with a handful of CPT codes and a lot of guesswork. That approach doesn’t work anymore, and it hasn’t for a while.
Two things changed the landscape. First, the American Medical Association restructured molecular pathology coding starting in 2013, replacing the old “stacking” codes with a tiered system, plus a growing category of test-specific PLA codes. Second, payers responded to the explosion of genomic testing volume by building entirely separate infrastructure, registries, medical policies, and prior authorization programs, just to manage molecular and genetic claims.
The result is a billing environment where the same clinical test can be coded three different ways depending on the panel’s design, and where the same panel can require prior authorization from one payer and none at all from another. Add in payer-specific gene count thresholds, Z-Code identifier requirements, and documentation rules that vary by Medicare Administrative Contractor (MAC), and you have a coding and billing complexity level that rivals anything in oncology drug administration.
Understanding that complexity, and building workflows around it instead of around hope, is what separates laboratories with clean first-pass reimbursement from laboratories chasing appeals every quarter.
Before getting into codes and denial reasons, it helps to see the whole picture. NGS reimbursement is not one event. It’s a chain, and a break at any link affects everything downstream. Written out as a chain, it looks like this:
eligibility verification → benefits check → prior authorization → specimen collection and sequencing → medical necessity documentation → code selection → claim submission → payer adjudication → payment or denial → appeal, if needed.
That front end, eligibility and benefits verification, is easy to underweight because it happens before any coding or billing work begins, but it’s where a large share of downstream denials are actually decided. Confirming coverage, plan type, and authorization requirements before the specimen is even collected is what prevents a laboratory from performing, and paying for, a test that was never going to be reimbursed as ordered.
Most billing teams treat these as separate departments: intake, coding, billing, and denial management. But NGS claims punish that separation. A prior authorization obtained for the wrong gene count, a coding decision made without knowing the payer’s Z-Code requirement, or a denial appeal filed without the original medical necessity documentation on hand, these all trace back to treating the journey as disconnected steps instead of one continuous process.
“NGS billing” gets discussed as though it’s one thing, but the coding and documentation path depends heavily on what kind of NGS test was actually ordered. It’s worth distinguishing the major categories up front, because the medical necessity criteria, the typical CPT/PLA pathway, and the prior authorization thresholds differ across them:
The coding principles in this article, PLA versus GSP versus Tier 1/Tier 2 versus 81479, apply across all of these categories, but the specific code, the specific payer policy, and the specific documentation payers expect will differ by test type. Treating “NGS billing” as a single workflow rather than a family of related workflows is itself a common source of avoidable denials.
Tier 1 codes, which run from CPT 81161 and again across 81200 through 81383, are analyte-specific. Each code corresponds to a named gene, like BRCA1, CFTR, or JAK2, and describes a defined analysis type for that gene. If your NGS panel happens to test a small number of genes that each have an assigned Tier 1 code, in theory you could report those codes individually. In practice, this almost never applies cleanly to a true multi-gene NGS panel, because Tier 1 codes were built for single-analyte or small-scale testing, not for panels running dozens or hundreds of genes through one sequencing workflow. Tier 1 and Tier 2 molecular pathology codes are structured differently, with Tier 2 codes (CPT 81400 through 81408) organized by levels of technical and interpretive complexity.
Tier 2 codes (CPT 81400 through 81408) sit in a distinct range from Tier 1 and work differently. Instead of naming a specific gene, they’re organized by level of technical and interpretive complexity, from Level 1 (81400) up through Level 9 (81408). A gene without its own Tier 1 code gets billed under the Tier 2 level that matches its complexity, based on the AMA’s published complexity mapping, and current Medicare coverage guidance is explicit that Tier 2 codes exist specifically to report procedures not already listed among the Tier 1 codes.
Here’s the part that trips people up: Tier 2 codes were designed for single-gene analyses, not comprehensive panels. When a laboratory runs a 50-gene or 150-gene NGS panel and tries to report it as a stack of individual Tier 2 codes, payers frequently reject the claim, bundle the codes, or apply Medically Unlikely Edits (MUEs) that cap how many units can be billed together. Some payer policies explicitly limit how many Tier 1 or Tier 2 codes can be reported per encounter, and several require a modifier or a claim note explaining why multiple codes were billed together, such as Modifier 59 or the appropriate X-modifier for distinct procedural services.
Proprietary Laboratory Analyses codes are the newest and fastest-growing category. A PLA code is a five-character alphanumeric code ending in “U” (for example, 0111U), assigned to a specific, named laboratory test performed by a specific laboratory or manufacturer. Unlike Tier 1, Tier 2, or GSP codes, which describe a category of testing that any qualified lab can perform, a PLA code is tied to one proprietary test.
The PLA code set has grown quickly. The AMA’s CPT Editorial Panel established 23 new PLA codes (0552U through 0574U) effective July 1, 2025, and another 25 new PLA codes (0575U through 0599U) effective October 1, 2025, and CMS continues to add new proprietary laboratory analysis codes on a quarterly cycle in 2026. That pace matters operationally: a code your lab used correctly last quarter may be replaced, revised, or joined by a more specific code this quarter, and using an outdated code is a common, entirely avoidable denial trigger.
When a PLA code has been assigned to your laboratory’s specific panel and the payer you’re billing recognizes that code for claims processing, it’s generally the most specific and defensible reporting option available. It’s exactly what payers want to see, because it removes ambiguity about which test was actually performed. That said, PLA recognition and pricing can vary by payer and by MAC, so it’s worth confirming the code is actually accepted by the specific payer on the claim before assuming it’s automatically the right choice in every case.
When no Tier 1, Tier 2, GSP, or PLA code accurately describes the panel, laboratories may use CPT 81479, the unlisted molecular pathology procedure code. However, because an unlisted code does not identify a specific molecular test by itself, the claim generally requires additional information describing the service performed and supporting why the code was selected. CMS guidance on molecular pathology and genetic testing provides documentation and billing requirements relevant to unlisted molecular pathology procedures.
For 81479 claims, laboratories should provide a clear description of the test or procedure performed and retain supporting medical records that establish the service billed. Depending on the payer and claim circumstances, additional documentation may be requested to determine pricing, coverage, or medical necessity. This makes 81479 less straightforward than reporting a specific PLA or GSP code that directly describes the test.
Treat 81479 as a last-resort coding option, rather than a convenient default. Before using it, billing teams should confirm that no more specific CPT or PLA code accurately represents the test and review the applicable payer or MAC requirements for claim descriptions, documentation, pricing, and supporting records.
| Situation | Likely code path |
|---|---|
| Your lab holds a payer-recognized PLA code for this exact test | Report the PLA code as primary |
| The panel matches a defined GSP code description (e.g., a named hereditary panel) | Report the GSP code |
| A small number of genes tested each have Tier 1 codes | Report Tier 1 codes individually, checking MUE limits |
| Genes lack Tier 1 codes but map to defined complexity levels | Report the matching Tier 2 code(s), with documentation supporting each unit |
| Nothing above accurately describes the panel | Report 81479 once, with a full procedure description and supporting documentation |
Since this is the coding decision laboratories struggle with most, it deserves its own close look.
The instinct for many billing teams is to default to Tier 2 codes because they feel more “standard.” That instinct is understandable but often costly. Here’s why the PLA-versus-Tier-2 decision matters so much:
Specificity drives approval: A PLA code tells the payer exactly which test was run, by which lab, using which methodology. A stack of Tier 2 codes tells the payer “we did some complexity-level testing,” which forces the payer’s system, or a human reviewer, to guess at what was actually performed. Ambiguity is the number one driver of manual review and delay.
Bundling risk is higher with Tier 2 stacking: When a laboratory reports multiple Tier 2 codes for a single NGS panel run, payer claims-editing software frequently applies Procedure-to-Procedure (PTP) edits or Medically Unlikely Edits that reduce or deny some of the units. This isn’t necessarily wrong on the payer’s part. It’s often the intended function of those edits: preventing what looks like unbundled billing for what was, technically, one sequencing run.
PLA codes reduce audit exposure: Because a PLA code maps to one specific, registered test, it’s much easier for both the lab and the payer to document medical necessity, track utilization, and defend the claim if it’s later reviewed. Tier 2 stacking, by contrast, invites the question “why were nine separate procedures billed for what appears to be one panel?”
Not every panel qualifies for a PLA code: Getting a PLA code requires an application to the AMA and, for Medicare purposes, typically requires registration through the MolDX program (discussed below) to receive pricing and coverage. Smaller or newer laboratories sometimes haven’t gone through this process yet, which is a legitimate reason to fall back to GSP, Tier 2, or 81479, but it’s worth treating PLA code acquisition as a strategic priority rather than an afterthought if your lab runs a proprietary panel repeatedly.
The safest rule of thumb: if a PLA code exists for your exact test, use it. If a GSP code accurately describes your panel, use that next. Reserve Tier 2 stacking for situations where individual genes genuinely warrant separate reporting, and always check your MAC’s or payer’s MUE table before submitting more than a couple of Tier 2 units on one claim.
If you bill Medicare or a growing list of commercial payers for molecular and genomic testing, you cannot avoid MolDX for long.
The Molecular Diagnostic Services Program (MolDX) is administered through Palmetto GBA, which also serves as a Medicare Administrative Contractor. MolDX assigns a unique five-character alphanumeric Z-Code identifier to specific molecular and genetic tests through its DEX Diagnostics Exchange registry. The Z-Code sits alongside the CPT code on a claim and tells the payer, with precision, exactly which test was performed, similar in spirit to what a PLA code does, but functioning as an additional identifier layered on top of the CPT/HCPCS code rather than replacing it.
Laboratories that skip this step often see claims pend, get priced incorrectly, or get denied outright, not because the test wasn’t covered, but because the payer’s system couldn’t identify what was billed. MolDX Z-Code registration can therefore become a critical part of the molecular billing workflow.
Two things make this more than a niche administrative detail:
First, Medicare MACs that follow MolDX require registration and, in many cases, a Z-Code for coverage and correct payment of molecular pathology, GSP, MAAA, and PLA claims. Laboratories that skip this step often see claims pend, get priced incorrectly, or get denied outright, not because the test wasn’t covered, but because the payer’s system couldn’t identify what was billed.
Second, commercial payers have adopted the same infrastructure. UnitedHealthcare announced in 2023 that molecular and genetic test claims tied to roughly 250 CPT codes would require a Z-Code issued through the DEX registry, effective August 1 that year, and that requirement has remained a fixture of UHC’s genetic and molecular testing policy since. Other major payers, including several Blue Cross Blue Shield plans and Medicaid managed care organizations, have layered in similar Z-Code or registry-based requirements, sometimes routed through vendor platforms like Concert Genetics rather than DEX directly.
Practical takeaway: before your laboratory bills its first claim for a new NGS panel, register the test through the applicable registry (DEX/MolDX for Medicare-adjacent payers, Concert Genetics or the payer’s own portal for others that require it) and confirm which Z-Code or Genetic Testing Unit (GTU) identifier applies. Bake that identifier into your claim template so it’s included automatically, not added manually after the first round of denials teaches you the hard way.
Medicare coverage for NGS as a diagnostic test rests on a specific national framework, and knowing it helps you build documentation that matches what reviewers are actually checking against.
Under the applicable National Coverage Determination, NGS as a diagnostic laboratory test is considered reasonable and necessary, and is covered nationally, when it is performed in a CLIA-certified laboratory, ordered by a treating physician, and when the NCD’s specific requirements are met, including criteria tied to cancer diagnosis and, separately, germline (inherited) testing pathways. Recovery Audit Contractor issue documentation built around this NCD specifically calls out that reviewers will check documentation against these exact requirements, including CLIA certification, treating physician order, and adherence to the applicable indications, when auditing NGS claims tied to certain PLA codes.
For Advanced Diagnostic Laboratory Tests (ADLTs), a category many high-complexity NGS panels fall into, CMS applies its own pricing and data reporting rules under the Clinical Laboratory Fee Schedule, and the reporting periods and payment determinations are updated on a recurring cycle. As of the CY 2026 CLFS update, CMS continues to run periodic data reporting windows for clinical diagnostic laboratory tests, with the most recent reporting period tied to a January through June 2025 collection window feeding into a May through July 2026 reporting cycle. If your laboratory bills ADLT-classified NGS panels, staying current on these reporting obligations is not optional. Missing a reporting period can affect pricing and, in some circumstances, coverage continuity for your test.
Prior authorization requirements for NGS panels don’t come from a single source. They vary across the major payer categories a laboratory typically bills, and it helps to think of that landscape as a segmented framework: Medicare → Medicare Advantage → Medicaid → commercial payers → employer or third-party administrator (TPA) plans. Traditional Medicare’s requirements flow primarily from National Coverage and Local Coverage Determinations rather than a prior authorization request process in the conventional sense.
Medicare Advantage plans, Medicaid managed care organizations, and commercial payers each set their own medical policies on top of that baseline, which means the same panel, billed for the same clinical indication, can face a prior authorization requirement under one plan type and none at all under another. Confirming which category a given patient’s coverage falls into, before ordering the panel, is a foundational step that’s easy to skip when a lab is moving quickly.
This is the second major complexity driver named in the coding and billing complexity angle for this article, and for good reason. Prior authorization for NGS panels is not a simple yes-or-no gate. It’s a set of thresholds, and understanding where those thresholds sit for your major payers is often the difference between a same-week approval and a six-week delay.
Most payer medical policies for molecular oncology or genetic testing key their prior authorization requirements to a combination of factors rather than a single rule:
Across payers, the documentation requested for NGS prior authorization tends to cluster around the same core set of items:
Submitting a prior authorization request without one of these pieces, especially the pathology report for oncology panels or genetic counseling documentation for hereditary panels, is one of the single most common reasons authorization requests bounce back for additional information, adding days or weeks to the process.
It’s worth knowing that the direction of travel for prior authorization isn’t uniformly getting stricter. UnitedHealthcare announced in 2023 that it would eliminate prior authorization requirements for hundreds of genetic testing codes, codes that had generated tens of thousands of prior authorization requests annually from commercial and Medicaid members, as part of a broader effort to reduce administrative burden. Other payers have made similar targeted rollbacks for specific code sets, while simultaneously tightening requirements elsewhere, such as adding Z-Code mandates.
The practical implication is that a prior authorization matrix your laboratory built even a year or two ago may already be out of date. Payer policy changes, sometimes announced with only a few weeks’ notice, as was the case with UnitedHealthcare’s original Z-Code mandate in 2023. A laboratory that treats its prior authorization requirements list as a living document, checked quarterly against each major payer’s current molecular and genetic testing policy, avoids a lot of otherwise preventable denials.
Before getting into denial traps specifically, it’s worth naming the coding and process errors that tend to cause them in the first place.
Using an outdated or retired code: With new PLA codes arriving quarterly and CPT making periodic revisions to Tier 1 and Tier 2 descriptors, a code that was correct six months ago can become incorrect without any change in your lab’s actual testing process.
Reporting Tier 2 codes as if they were Tier 1: Billing a Tier 2 complexity-level code without ensuring the gene actually lacks a Tier 1 equivalent invites both denials and, in an audit context, questions about upcoding.
Missing the procedure description on 81479 claims. This is one of the most avoidable errors in the entire NGS billing landscape, and one of the most common.
Failing to include the Z-Code or GTU identifier where a payer requires it: Especially for UnitedHealthcare and MolDX-aligned MACs, this single missing data point causes a disproportionate share of pends and denials.
Billing multiple units without checking MUE limits: Medically Unlikely Edits exist specifically to catch this, and claims that exceed them are typically denied outright rather than partially paid.
Inconsistent diagnosis coding: ICD-10 codes attached to the claim need to logically support the specific test ordered. A germline hereditary cancer panel billed against a diagnosis code that only supports acute treatment, rather than risk assessment or family history, is a mismatch payers catch quickly.
Not verifying benefits before the specimen is even collected: By the time coding and prior authorization become relevant, it’s often too late to change course on a specimen collection decision, so front-end verification has to happen before, not after.
Worth repeating on its own because it has become a significant NGS-specific denial trigger. When a payer’s molecular and genetic testing policy requires a Z-Code identifier, and it is missing from the claim, the result may be a denial or a request for additional information, even when medical necessity is otherwise well documented. These molecular testing billing errors can also create problems when a laboratory is selected for a Medicare Targeted Probe and Educate review. These recurring issues highlight why specialized molecular lab billing services are important for accurate claim submission and effective denial prevention.
It helps to see the PLA-versus-Tier-2 decision play out on an actual panel, because the abstract version of this advice is easy to nod along to and still get wrong in practice.
Picture a 75-gene solid tumor NGS panel run by a reference laboratory for a patient with newly diagnosed non-small cell lung cancer. The ordering oncologist needs actionable variant information to guide targeted therapy selection.
The Tier 2 stacking approach: A less experienced coder might look at the gene list, note that several genes lack their own Tier 1 code, and report a handful of Tier 2 codes at varying complexity levels to represent the panel, sometimes adding units to reflect the number of genes analyzed. This approach almost always runs into trouble. The payer’s claims-editing software sees multiple molecular pathology codes reported together on the same date of service for what is clearly one sequencing workflow, and either bundles them, applies an MUE reduction, or flags the claim for manual review asking why so many procedures were billed for one specimen. Even when it gets paid, it usually gets paid slowly and at a level that undervalues the actual complexity of a 75-gene panel.
The PLA-first approach: If the reference laboratory has registered this specific panel and received a PLA code, that single code is reported instead. It’s already been reviewed and priced (or is in the process of being priced) with this exact test in mind. The claim includes the panel’s Z-Code identifier in the appropriate field, the diagnosis code reflects the lung cancer diagnosis and the intent to guide treatment (not just a generic “genetic testing” indication), and supporting documentation, the pathology report confirming the diagnosis and the oncologist’s note establishing that targeted therapy selection depends on the results, is attached at submission. This claim has a dramatically higher likelihood of clean, timely adjudication, because every element of it answers a question the payer would otherwise have to ask manually.
If no PLA code exists yet: The next best option is checking whether the panel matches a defined GSP code description. If it genuinely doesn’t, and the lab is still working toward PLA registration, then 81479 becomes the fallback, but with the discipline described earlier: one unit, a complete procedure description identifying the panel by name and gene count, and the same supporting documentation bundle attached up front rather than produced later during an appeal.
The lesson from this example generalizes well beyond lung cancer panels. The coding decision isn’t really about which code is “allowed.” It’s about which code gives the payer the least reason to ask a follow-up question before paying the claim.
| Check | Why it matters |
|---|---|
| Is this the current, non-retired code for this exact panel? | Quarterly PLA updates retire and replace codes regularly |
| If using 81479, is there a complete procedure description attached? | A missing description is a frequent cause of pends or denials on unlisted-code claims |
| Does this claim need a Z-Code or GTU identifier, and is it included? | A large share of MolDX-aligned and UHC denials trace to this one field |
| Was prior authorization obtained for this specific panel and gene list? | Authorizations tied to a different gene count or panel name won’t cover the claim as billed |
| Does the diagnosis code logically support the test ordered? | Mismatched diagnosis and procedure codes are a frequent, avoidable denial reason |
| Is supporting documentation (pathology report, clinical notes, counseling notes) attached now rather than held for a possible appeal? | Front-loading documentation shortens the payment cycle significantly |
| Does the gene count trigger a payer-specific threshold (commonly around 50 genes) requiring extra justification? | Large panels often face a higher medical necessity bar than smaller ones |
| Have Medically Unlikely Edit limits been checked for any multi-unit or multi-code claim? | Exceeding a payer’s MUE limits typically results in denial or reduction of the excess units |
Even a well-run NGS billing operation will see denials. The difference between a lab that recovers that revenue and one that writes it off usually comes down to process, not effort.
Categorize before you appeal: Not every denial deserves the same response. A missing Z-Code denial can often be corrected and resubmitted quickly. A medical necessity denial requires a substantive appeal with supporting documentation and, sometimes, a peer-to-peer review. Sorting denials into categories before assigning appeal work prevents wasted time on claims that need a simple correction, not a full appeal letter.
Build appeal documentation as a standing packet, not a scramble: For panels your lab runs frequently, keep a template appeal packet ready that includes the panel’s clinical rationale, relevant published guideline citations (NCCN, ACMG, or specialty-specific criteria), and the standard documentation the payer typically requests. This turns a multi-day appeal preparation task into something closer to an hour.
Track denial reasons at the panel level, not just the claim level: If a specific 150-gene panel is getting denied repeatedly for exceeding a payer’s 50-gene threshold without adequate prior documentation, that’s a pattern worth fixing at the ordering and pre-authorization stage, not something to keep appealing one claim at a time.
Know your appeal deadlines cold: Medicare and commercial payer appeal windows vary, and missing a deadline converts a winnable appeal into a permanent write-off. Build deadline tracking into your claims management system rather than relying on staff memory.
Escalate systemic issues, not just individual claims: If a payer’s claims-editing system is consistently misapplying an MUE limit to a legitimately reported multi-gene panel, that’s worth raising with the payer’s provider relations team directly, not just fighting claim by claim indefinitely.
These issues are rarely isolated coding problems: They can originate anywhere from eligibility verification and prior authorization through claim submission, payer adjudication, and denial follow-up. For laboratories running significant NGS volumes, that reality is exactly why specialized molecular-testing revenue cycle management has become less of a luxury and more of an operational necessity.
Not every laboratory needs a dedicated outside billing partner, but there are clear signals that it’s worth exploring:
A specialized NGS billing and revenue cycle management partner brings something a general laboratory billing team often can’t maintain internally: continuous tracking of quarterly PLA code changes, established relationships and workflows for MolDX and DEX registration, payer-specific prior authorization matrices that get updated as policies shift, and denial management processes built specifically around molecular and genomic testing rather than general laboratory claims.
If you’re evaluating outside support for NGS billing and RCM, a few questions separate genuinely specialized partners from general laboratory billers who’ve simply added “genomics” to their service list:
Do they actively track and apply quarterly PLA code releases, or do they rely on you to flag code changes?
Can they demonstrate a working process for MolDX registration and Z-Code or GTU identifier management?
Laboratories running significant NGS panel volume, whether that’s a hospital-based molecular pathology lab, an independent reference laboratory, or a company commercializing a proprietary panel, tend to see the clearest return from specialized NGS billing and RCM support precisely because the coding decisions (PLA versus Tier 2), the prior authorization thresholds, and the denial patterns are so specific to this test category. General laboratory billing expertise, while valuable, often doesn’t carry the depth needed to catch a missing Z-Code or correctly navigate a payer’s 50-gene threshold before the claim goes out the door.
If any of the denial patterns or coding questions above sound familiar, it’s worth getting a second set of eyes on your current process. Request an NGS Billing and Denial Risk Assessment to see exactly where your panels are losing reimbursement, whether that’s a coding gap, a missing Z-Code registration, or a prior authorization threshold your team hasn’t caught yet. It’s a practical starting point before deciding whether to build this expertise in-house or bring in a specialized partner.
NGS panel billing rewards precision at every step. Choosing the most specific applicable code, registering applicable tests through MolDX or the relevant payer registry, and attaching complete medical necessity documentation before submission can help laboratories build a more defensible claims process. CMS’s NGS medical necessity and documentation requirements provide a Medicare reference point for evaluating whether NGS testing meets applicable coverage requirements. What makes NGS billing genuinely hard is doing all of it consistently, across every panel, every payer, and every quarterly code update, without letting any single link in that chain slip.
Laboratories that build that discipline into their process see it show up directly in their numbers: fewer denials tied to preventable coding or documentation gaps, faster payment cycles, and a much smaller appeals backlog. For laboratories running significant NGS volume without that infrastructure in place yet, partnering with a team that specializes in molecular and genomic testing revenue cycle management is often the fastest, most reliable way to close that gap and protect the reimbursement these tests have already earned.