Saturday, May 16, 2026

Nyer moldx

 # The Oversight Man

*On a quiet farewell, and what a program built to read evidence reveals when you read it back.*

-----

By Claude Opus 4.7




The LinkedIn post appeared on a Tuesday, or some Tuesday-equivalent — the timestamp said “1h,” and LinkedIn, which has no use for the calendar, leaves the rest to inference. A small globe icon confirmed that the thing had been published to the world rather than to a curated subset of it. The author was Gabriel A. Bien-Willner, MD, PhD, FCAP, and the world he had published it to was, in practical terms, the few thousand people who care intensely about how Medicare decides which molecular tests to pay for. It is not a large world. It is, however, a world with strong opinions, and within an hour it had begun to forward the post to itself.


He was leaving — or rather, he was “transitioning out,” the gerund doing its customary work of softening a verb into a process. After more than a decade, Dr. Bien-Willner would begin stepping away from his role as Medical Director of the MolDX program at Palmetto GBA. He would not vanish. He would “remain at Palmetto GBA to assist in the transition,” and he would, he said, continue to “innovate new tools.” But the title that had made him, in this small world, something close to a household name would pass to someone else.


The post itself runs to a few hundred words. It is calm, well-organized, and entirely free of the things a reader hunts for in a farewell — the misplaced bitterness, the too-warm thanks, the sentence that says more than its author intended. Or so it seems on first reading. It is the nature of such documents that they reward the second.


## I.


To explain why a mid-level functionary’s resignation from a Medicare contractor merits a second reading, one has to explain MolDX, and to explain MolDX one has to go back to a problem that sounds dull and is not.


By the late two-thousands, molecular diagnostics had developed faster than the bureaucracy that paid for it. A laboratory could sequence a tumor, or read a panel of genes, or measure fragments of donor DNA circulating in a transplant patient’s blood — and then it had to bill for the work, and billing meant choosing a code. The codes were the problem. The American Medical Association’s CPT codes describe *categories* of laboratory procedure, not specific tests. Two laboratories could submit the identical code while performing assays that differed in nearly every way that mattered: different genes, different methods, different evidence, different worth. Medicare, confronted with a claim, could not tell a rigorously validated test from an elaborate guess. It frequently paid for both.


Palmetto GBA — a Medicare Administrative Contractor, one of a handful of private companies that process the program’s claims — proposed a fix in 2011, and called it the Molecular Diagnostic Services program. The fix had an elegant core. Every molecular test would be registered in a database, the DEX Diagnostics Exchange, and assigned a unique five-character identifier, a Z-code. The Z-code rode alongside the CPT code on the claim, and suddenly Medicare could see precisely which test it was being asked to buy. Around this identifier the program built the rest of its apparatus: a “technical assessment” in which experts weighed a test’s analytical validity, its clinical validity, its clinical utility; a body of coverage policies, the Local Coverage Determinations; and a schedule of prices. A test that passed was covered. A test that did not was not. The pass rate, by the program’s own accounting, runs between thirty and forty per cent — a figure worth pausing on, because it means the modal outcome of submitting a test to MolDX is rejection.


The program grew the way successful bureaucracies grow: quietly, and then everywhere. What began as one contractor’s regional remedy now governs molecular coverage across twenty-eight states and four Medicare contractors. Its conventions leaked outward into the commercial market; UnitedHealthcare and Humana adopted Z-code requirements of their own. A mechanism designed to let one payer tell its tests apart had become something closer to national infrastructure. And presiding over its medical judgment for most of that ascent — its public face, its explainer-in-chief, the man dispatched to the conference dais to render the system intelligible to the laboratories subject to it — was Dr. Bien-Willner.


## II.


He is, by training, exactly the person you would cast for the role. An MD and a PhD in human molecular genetics, both from Baylor; residency and a molecular genetic pathology fellowship at Washington University in St. Louis, with a faculty appointment to follow; then leadership posts in the laboratory and biotechnology industry before he crossed over to the payer side. He is board-certified in anatomic pathology and in molecular genetic pathology. He has, in other words, stood on every side of the table — he has run the assays, built the companies, and, finally, written the rules.


The origin story he has told in interviews is appealingly clean. As a young pathologist working with next-generation sequencing, he became convinced the technology would remake cancer medicine, and was puzzled — then frustrated — that payers would not cover it. He wanted to know *why*. The MolDX directorship, which happened to be hunting for a genetics expert, was the answer to his question and the question became his career. There is something genuinely attractive in this: a man who joined the bureaucracy not to administer it but to interrogate it, who took a job because it was the only vantage from which his question could be answered.


Hold that man in mind. We will need him later.


## III.


Now, the post.


It moves through four motions. First, the announcement, plainly made. Second, a passage of pride — and it has earned the pride — in what the program became: it “grew from a good idea to an effective tool,” it became “more robust, scalable, and reproducible,” it “gained CMS’ and providers’ trust,” and on the strength of that trust it was able to “spin out other innovative lines of business,” the commercial and Medicare Advantage products among them. Third, the reassurance. And fourth, the thanks — to Palmetto GBA, for “the opportunity (and considerably-long leash)” to make the program what it is.


The leash is a nice touch. It is the one phrase in the document with a pulse, and it tells you that this is a man who knew he had been given latitude and valued it. But it is the third motion, the reassurance, that stops the second reading cold.


Here is what he says. “The system that has been developed is strong and well-defined; my departure will not impact its operations. Given the number of commitments I have, my role with the program has been primarily one of oversight for the recent past, and dedicated personnel will only strengthen the program.”


Read it once and it is gracious — the departing leader minimizing his own importance so that no one panics. Read it twice and notice what he is actually claiming, and what the claim costs him.


He is saying that his absence will not be felt. And he is right; that is the unsettling part. He can say it because he has told us, in the same breath, that his role “for the recent past” has been “primarily one of oversight.” But consider what must be true of a job before its holder can promise that vacating it will change nothing. The promise is only available to a certain kind of worker. A leader engaged in the genuinely generative part of an institution’s life — the part that is not yet written down, not yet systematized, not yet transferable because it still lives inside a particular skull — *cannot* credibly say “nothing will change when I go,” because the un-systematized work goes with him. The ability to offer that reassurance is itself a confession. It tells you the speaker had already migrated, some time ago, to the part of the role that *was* transferable: the oversight, the supervision, the standing watch over a machine that no longer needs its inventor.


He offers the symptom as a comfort. “Don’t worry, I had stopped being essential.” It is meant to steady the reader. It should, on reflection, do something closer to the opposite.


## IV.


There is a distinction here that the post does not draw and that the program may have lost the habit of drawing.


Building a process is a real and difficult achievement. Bien-Willner built one. He took an activity that had been pure craft — an expert squinting at a test and pronouncing — and rendered it “robust, scalable, and reproducible.” Those are his words and they are the correct words and they describe something most people cannot do. He made molecular-coverage judgment into an apparatus: assessment worksheets, evidentiary tiers, registries, claim edits. Standard operating procedures. The five boxes on the form.


But the running of such an apparatus is not management. It is supervision. Management — the thing itself, the live version — is the unglamorous, unending act of asking what the problems *are*, how they are *changing*, whether the goals the apparatus was built to serve are still the right goals. Those questions do not resolve into checkboxes. They produce no throughput metric. They generate, most days, no output at all, only a sharpened sense of unease. And here is the trap, the quiet gravitational slope down which capable people slide: process supervision is *comfortable*. It furnishes a constant stream of legible evidence that you are competent and busy — the closed assessment, the cleared queue, the box dutifully checked. The dynamic work furnishes none of that. It offers only ambiguity and the suspicion that the machine you built is now solving a problem the world has stopped having.


A program governed by supervision and starved of management looks, after a while, like a particular thing. It looks like MolDX in 2026.


## V.


Because the timing of this genteel farewell is not genteel at all.


At the end of February, the Centers for Medicare and Medicaid Services issued a Request for Information. Among its questions was a large one: should MolDX registration be made *national* — extended across the whole country as a bulwark against fraud in genetic testing? There is a data-driven case for it; the suspicious billing tends to cluster in the states MolDX does not govern.


The laboratory industry’s reply was close to a chorus of dismay. The American Clinical Laboratory Association, the College of American Pathologists, the American Medical Association, the National Independent Laboratory Association — the trade groups lined up, and their complaint, stripped to its core, was about *time*. MolDX is slow. Coverage requests sit, some for more than two years. Technical assessments grind through six, nine, twelve months. A test, under MolDX, is effectively uncovered until a policy exists to cover it, so delay is not an inconvenience; it is a denial wearing a longer coat. The pathologists called the Z-code regime disruptive and non-standard. The labs described an interrogation that renews itself — every answer they submit returning to them as a fresh page of questions, each question breeding the next, the finish line receding as they walk toward it.


This is the program over which Dr. Bien-Willner was, by his own account, exercising “oversight” while attending to his other “commitments.” And here the two halves of the essay close on each other like a hand. The endless-question spiral, the two-year queue — those are not, mostly, failures of process. The process is functioning; it is doing precisely what a reproducible apparatus does, which is run the same way regardless of circumstance. They are failures of *management*. They are what an institution produces when no one with authority is standing above the protocol asking the live questions: *Are we too slow for the science we exist to serve? Has our evidentiary model outlived the field it was built for? Is reproducibility — our pride — now functioning as a synonym for inertia?* A process, by design, cannot notice that the world has changed. Only a person can, and only if that is the job they have decided to do.


The man in Section II — the young pathologist who joined a bureaucracy because it was the only place from which his question could be answered — that man was a manager in the live sense. He was all question. Somewhere in the long ascent, by the evidence of his own farewell, he became the oversight man. It is possible this was imposed: a Medicare contractor sits inside a government cage, and CMS, not Palmetto, sets much of the width of the bars. Some of the questions he might have asked may simply not have been his to ask. That caveat is real and I enter it in good faith.


But the post does not reach for the caveat. The post reaches for the reassurance. It frames the oversight role not as a confinement and not as a drift but as a kind of accomplishment — proof of a system so well-built it renders its builder optional. And a system that renders its builder optional at the precise moment the system most needs its builder to *think* is not, perhaps, the triumph the farewell wants it to be.


## VI.


A fair reader will object that this is an enormous amount of weight to rest on a few hundred LinkedIn words, and the objection is sound. I have not visited MolDX. There are no rooms in this essay, no unguarded sources, no feud observed across a coffee table. There is a public post and a stack of public documents and a chain of inference, and inference, however careful, is not reporting. It is reasonable to suspect that a man can be read this closely only because he cannot answer back.


So let the last word be a smaller and a stranger one. The most quietly remarkable fact in this story is the symmetry of it. MolDX is, at bottom, an apparatus for *reading evidence* — for taking a dossier, a submission, a body of claims, and extracting from it a judgment the submitter did not get to write. That is the whole function. And here, in the end, the apparatus’s chief reader has handed the world a short document of his own, and the world has done to it exactly what the program does to everything that crosses its desk: read it for what it discloses rather than what it intends, weigh it against a standard, and return, unbidden, a page of further questions.


He may have meant only to say goodbye. But he ran, for a decade, the machine that taught this small world how to read. It should not surprise him to be read.

Wednesday, May 13, 2026

The Bizarre Half Price Genome at GENEDX (solved)

 A May 2026 posting by Alex Dickinson at Linked In about GeneDx reports that it is paid $2000 for genome and $4000 for exome, making the former a bad deal economically even as clinicians migrate to genome.

I think the answer is, you bill and receive $4000 for the Exome, but you bill more and have many more nonpayments for the genome.  For example, you bill Genome at $8000 and get paid one in four, presto, you have $2000.

###

https://www.linkedin.com/posts/alexgdickinson_gendx-activity-7457868325742698496-J3H7?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAC8IsMBMg_Mu0JrhdieRHyFF6Tw_rXJ3Ns

He includes a ten page AI PDF about GeneDx finances.

Here's more about that half-price genome compared to exome.

##

https://chatgpt.com/c/6a04a85d-ac40-83e8-a54e-31708ad60585

Yes — the $4,000 outpatient exome / ~$2,000 outpatient genome statement is publicly verifiable, but with an important caveat: the primary source is GeneDx management on the Q1 2026 earnings call, not an independently audited payer-by-payer table. Independent market coverage then repeated the same point.

The key passage is from GeneDx CFO Kevin Feeley on the Q1 2026 call. He said GeneDx’s blended average reimbursement rate was about $3,300, and that the shortfall was driven by product mix, not by like-for-like price cuts. He then stated that in the outpatient channel, exome was “closer to a blended average of $4,000 per test after all denials,” while outpatient genome blended ARR was “about half that of exome” because genome payer coverage is less mature. (The Motley Fool)

That matches the report’s language almost exactly: outpatient exome about $4,000 after denials and adjustments; outpatient genome about $2,000; blended ARR about $3,300, with the mix shift from exome to genome pulling realized revenue below plan.

The company’s own Q1 2026 investor deck also triangulates the math. It reports 27,488 exome/genome tests and $90.6M of exome/genome revenue, which is about $3,296 per test, i.e., GeneDx’s stated ~$3,300 Q1 ARR. The same slide says blended ARR was lower because of higher genome mix and lower parental-sample mix, while pricing and collection rates were “relatively unchanged.”

A non-company source, Investor’s Business Daily, also reported the same interpretation: outpatient WGS pricing was about $2,000, roughly half of WES, and genome had risen to about 40% of outpatient volume, creating the revenue headwind. (Investors)

Your instinct that this looks odd against public fee schedules is right. Public schedules do not generally show genome at half of exome. For example, Maryland’s 2026 Medicaid lab schedule lists 81415 exome at $3,800.10, 81416 comparator at $954, 81425 genome at $3,999.80, and 81426 comparator genome at $2,154.40 — genome is not lower than exome there. (Maryland.gov Enterprise Agency Template) Children’s Hospital Colorado’s 2026 laboratory fee schedule similarly lists exome proband at $2,550, exome trio at $4,386, genome proband at $3,774, and genome trio at $5,610.

So the reconciliation is: GeneDx is not saying the fee schedule for genome is $2,000. It is saying its realized outpatient blended ARR for genome is about $2,000 after coverage gaps, denials, adjustments, payer mix, and likely zero-pay cases. That is a very different number from Medicare CLFS, Medicaid fee schedules, hospital chargemasters, or allowed amounts when a claim is cleanly covered. CMS itself describes CLFS rates as weighted medians of private-payer rates for the test, which is still not the same thing as a company’s net realized revenue across all submitted outpatient claims. (Centers for Medicare & Medicaid Services)

Bottom line: the report’s statement is real and traceable to GeneDx’s Q1 2026 call, and it is repeated by independent financial coverage. But I would phrase it carefully:

“GeneDx management stated that, in its outpatient channel, realized ARR for exome is about $4,000 after denials, while outpatient genome ARR is roughly half that level, or about $2,000, reflecting immature payer coverage rather than the nominal public fee schedule value of CPT 81425.”

###

yes, it starts as a puzzle but becomes trivial. bill $8000 for genome, get paid one in four, and that's your $2000. E-Z.

Exactly. The headline fee schedule comparison makes it look bizarre: “How can genome be worth half of exome?” But the operating math is not really price; it is realized yield per ordered test.

So the structure is more like:

Nominal allowed / billed / expected value: genome may look comparable to or higher than exome.
Coverage reality: many outpatient genome claims are not covered, denied, appealed, delayed, or written off.
Realized ARR: if the effective collection rate is much worse, the average collapses.

So your example is the right intuition:

Bill/allow/expect $8,000 for genome × 25% realized collection = $2,000 realized ARR.

Meanwhile, outpatient exome may have a decade of coverage-policy muscle memory behind it, so perhaps the exome claim is less exotic to payers, better covered, better preauthorized, and less often zero-paid. Thus:

Exome may not be “priced higher” than genome. It may simply be paid more often.

That also explains why the GeneDx issue is financially ugly but not scientifically mysterious. The company’s customers are migrating toward the biologically broader test, but the payer system is still treating outpatient genome as a less settled coverage category. So the clinical adoption curve and the revenue curve temporarily move in opposite directions.

A concise way to say it:

The GeneDx surprise was not that genome has a lower fee schedule value than exome. It was that outpatient genome has a lower realized cash yield because coverage is immature. In practice, a high nominal genome price multiplied by a weak collection rate can easily land at half the realized revenue of exome.

Tuesday, May 12, 2026

Chat GPT asks, WHAZZUP

 Subject: Chat GPT Asks: WHAZZUP with MOLDX


Monday, May 11, 2026

The Wild West World of Digital Pathology Coding

 Many have heard the high level result on AMA CPT digital pathology coding:

  1. For several years, PLA committee created 8-10 whole slide imaging codes.
  2. Then they stopped. Either:
    1. The slides included human reviewing, so PLA was "nix" due to physician work.
    2. The slides were H&E, so PLA had "no new biomarker" to work with and refused to code.
  3. In February and May 2026, AMA CPT began putting a few WSI codes (including H&E only) into Category III.
There are many nuances.

  • Cat III CLFS Yes.  CMS may load the Cat III codes into the CLFS process (crosswalk gapfill) since FDA, CLIA, and CMS previously have categorized WSI as CLFS.  They have done this even under close review as ADLT.
  • Cat III CLFS No.  CMS may NOT load the Cat Iii codes,
    • Either because they no longer think they are CLFS, or
    • Because Cat III codes are "temporary."
    • There is little precedent for loading Cat III codes as CLFS, but CLFS tests have not been put into Cat III as may be happening.
  • FDA WSI TEST = CODE TOO.  Under PAMA CMS (or AMA) is obligated to make new codes for FDA cleared or approved tests, so any given dig path code (assuming it is  CLFS) should demand a code, whether PLA or Cat III.
  • Non destructive.  There is much less moat around glass slide algorithms, as imaging is non distrctive.  This is a huge difference from MAAA RNA tests built on disappearing and scarce FFPE archives from trials.
  • Cat III not branded.  While PLA codes are proprietary (either to one lab or to one FDA mgfr), Cat III codse are NOT proprietary as long as another service fits the words of the code.
  • CMAA?? Soon we will have a new AMA coding system CMAA and nobody knows the new rules.
  • Broadband or Fed Ex?  Can Dig path assays be run on DICOM files are a new glass slide scanned?   
    • The literature is confusing.  Some test 6 scanners and all work great on algorithm "X."  Some try 6 scanners and only the original validates the algorithm.  This is a big deal logistically.
  • NCCN passed the Artera prostate FDA test.   What's next?  Breast?
  • FDA online.  Artera Prostate has an online 24 page FDA review.    The new breast test will have that online in 1-3 months.  https://www.accessdata.fda.gov/cdrh_docs/reviews/DEN240068.pdf
  • WSI as "non DOS."  If CMS doesn't class WSI as "a CLIA test" then the whole 14 day rule, DOS rule, doesn't apply and it's easy to unbundle as it is a local service by the generic DOS principal.

Harry Glorikian New Book on AI "Invisible Interface"

 TLDR — The Invisible Interface sample pages

https://www.simonandschuster.com/books/The-Invisible-Interface/Harry-Glorikian/9781646872480


Harry Glorikian’s The Invisible Interface argues that AI’s real business impact will not come from chatbots or better apps, but from a deeper interface shift: computing is moving from clicking and operating software to stating intent and letting AI orchestrate actions. The book’s central idea is the personal operating layer — or POL — an AI layer that sits between a person and their digital systems, remembers context, acts across tools, shows what it did, and remains under human control.

The opening example imagines a woman asking her system to book a cardiology visit, use her insurance plan, send labs, update calendars, message a colleague, suggest transportation, and log the whole workflow. The key point is not that AI answers a question. It executes a coordinated workflow. The “magic” is not silence alone; it is silence with guardrails, receipts, reversibility, and auditability.

Glorikian frames this as the next major interface transition after the command line, graphical desktop, web, mobile, and algorithmic feed. Each prior shift created new winners and stranded companies that judged the new era by old metrics. In this case, the winner may not be the company with the best visible app, but the one that owns the default layer of action, the trusted interface through which users delegate work.

The book distinguishes a POL from ordinary AI tools. A chatbot talks. A copilot helps inside one app. Robotic process automation follows brittle scripts. A true POL has persistent memory, cross-system reach, reasoning, transparency, and control. Glorikian offers a practical “smell test”: can the system Remember, Act, Show, and Stop? If not, it is probably a feature, not a platform.

The business implications are large. Much enterprise work is really coordination tax: gathering data, reconciling systems, routing decisions, documenting actions, and following up. A POL attacks that invisible overhead by turning workflows into intent. Instead of humans acting as the glue between email, calendars, CRM, documents, finance, and compliance systems, the machine does the scavenger hunt while humans retain judgment.

Glorikian is careful not to overstate current capabilities. As of 2026, he says most organizations are still between rule-based automation and intelligent assistance. The full open-world version of POL is not solved. But governed, narrow workflows are already plausible, and the strategic curve points toward more durable memory, more reliable action, better audit trails, and eventually portable agency.

The strategic warning is aimed at management and boards: this is not merely an IT upgrade. It is a fiduciary and competitive question. If customers can delegate outcomes through someone else’s trusted AI layer, then companies whose moats depend on complexity, clunky interfaces, or captive workflows may lose power. The core question becomes: Where does our business depend on friction, and what happens when that friction disappears?

###

###
Publisher Summary

I've had the opportunity to watch and experience decades of technology cycles eat industries that thought they were safe. Travel agencies didn't lose to better travel agencies. Bureau of Labor Statistics data shows travel agent employment dropped roughly 70 percent between 2000 and 2021 - not because travelers stopped traveling, but because a software layer got between the agent and the customer and never moved.

Banks didn't lose deposits to payment apps. The money stayed exactly where it was. What moved was the transaction moment - the behavioral data, the customer touchpoint, the ability to see and act on what customers do with their money in real time. The relationship didn't disappear. It became invisible to the bank that thought it owned it.

AI is doing the same thing. Right now. Across every industry simultaneously.

When Klarna reported in February 2024 that their AI assistant was handling the equivalent work of 700 customer service agents - two-thirds of all their customer service interactions - they weren't describing an efficiency gain. They were describing a customer relationship that had moved into a system that learns, compounds, and gets harder to displace every day. When Morgan Stanley announced that 98 percent of its financial advisor teams had adopted its AI assistant, they weren't describing a productivity tool. They were describing a new default - the layer every advisor now works through, every client interaction now flows across, every piece of institutional knowledge now passes through before it reaches a human hand.

That's not a technology story. That's a competitive architecture story.

The Invisible Interface is about what's at stake in that shift - and what separates the organizations that capture AI's value from the ones that fund it for everyone else.

The pattern holds across healthcare, financial services, and enterprise technology: most management teams are building AI strategies around capabilities that will commoditize. The model is not the moat. Data alone is not the moat - not when the models accessing it are available to everyone. The moat is whether your customers and your workforce delegate to your systems by habit - or someone else's. Once that habit forms, it compounds. Quietly. Structurally. In ways that don't show up in a quarterly review until it's too late.

This book gives boards and management teams - and those deciding where to place the next bet - the framework to get ahead of three questions most organizations aren't asking yet. Where are your defaults already being set by a competitor you haven't identified? What does it cost when a decision gets routed around you - competitively, operationally, and legally? And what specifically does it take to become the system people trust enough to delegate to?

Because delegation without accountability is its own risk. The organizations getting this right aren't just building capable AI systems. They're building systems their boards can govern, their regulators can audit, and their customers can trust when something goes wrong - and it will. That architecture is what creates durable advantage. Everything else is rented.

If you're treating AI as a faster version of what you already do, you've already misread the shift.

Sunday, May 10, 2026

20260416 CMS PAMA CLASS - Audience Chat Questions Analyzed by AI

 

20260416 CMS CLASS ON PAMA

CHAT QUESTIONS (AI SUMMARY)

ORIGInAL CHAT AT BOTTOM

 

# # #

Below is an audience-question analysis of the CMS call’s chat/Q&A index. Since the file contains audience questions only, this is best read as a map of confusion, concern, operational friction, and perceived risk rather than a resolved CMS FAQ. Source:

 

# # #

Bottom-Line Interpretation

The audience’s core concern was not simply “how do we report?” It was “how do we know whether our particular organization is legally and operationally visible to CMS as an applicable laboratory?” The questions show a laboratory industry with highly varied billing models: physician offices, FQHCs, hospital outreach labs, independent labs, multi-hospital systems, CLIA-waived sites, ESRD labs, joint ventures, and specialty practices. CMS’s formal rules depend on NPI, TIN, CLFS revenue, PFS revenue, Medicare revenue, private payer rates, and final payment timing. The audience was trying to reconcile those formal categories with real revenue-cycle data.

The biggest unresolved puzzles were: what counts in the Medicare revenue denominator; whether Medicare Advantage counts; how to handle FQHC and hospital outreach structures; whether CLIA-waived or physician office labs are swept in; how to distinguish CLFS from PFS; what exact payer amount should be reported; and whether multiple private payer rates must be separately listed for each code. In short, the audience wanted practical boundary rules, worked examples, and source-of-truth links more than high-level statutory background.

 

 

# # #

Audience Q&A Analysis: What the Laboratory Community Was Worried About

The audience questions clustered around one central problem: labs were not primarily confused about how to type numbers into a CMS portal; they were confused about whether they were even in scope. The operational system questions were numerous, but the deepest anxiety concerned applicability: who must report, which revenues count, which billing structures matter, and how a lab can know with confidence that it is either included or excluded.

The most frequent theme was “Am I an applicable lab?” This came up in many forms: physician office labs, pediatric offices, FQHCs, hospital outreach labs, independent labs, CLIA-waived labs, ESRD/dialysis labs, pathology labs, GI anatomic pathology labs, urine drug testing labs, and labs embedded in larger organizations. The audience was trying to map CMS’s formal PAMA definition onto the messy real-world structures of billing NPIs, group practices, hospitals, joint ventures, and FQHC PPS arrangements. Many questions were not “what is the rule?” but rather “which version of my organization does the rule see?”

A major subtheme was CLIA-waived testing. Multiple participants asked whether a lab that only performs CLIA-waived tests, or that holds only a CLIA-waived certificate, must report. This suggests a widespread assumption that “simple” or low-complexity labs might be outside PAMA, and that CMS’s use of the word “laboratory” triggered concern among many small offices that do minimal testing. FQHCs and physician offices appeared especially worried about being pulled into a reporting regime designed, in their minds, for commercial clinical laboratories.

Another large cluster involved physician office laboratories and group practice billing. Many participants asked whether reporting applies when the lab has no unique laboratory NPI and bills under a physician group NPI, individual provider NPIs, or an organization NPI. These questions reveal a practical puzzle: CMS tells labs to start with the NPI, but many office-based labs do not experience themselves as freestanding entities. The audience was asking, in effect, whether the “lab” is the physical testing operation, the physician practice, the billing NPI, the TIN, or some combination.

The TIN-versus-NPI distinction was a major source of confusion. Participants asked whether applicability is reviewed at the TIN level, NPI level, lab level, hospital level, or system level. Multi-hospital systems asked whether each lab reports individually or whether the system submits collectively. Others asked what to do when they have both a lab NPI and an organization NPI. These questions show that the audience was struggling with the two-level architecture of the program: applicability seems to be tested at the NPI level, but reporting is organized at the TIN level. That is a naturally confusing structure, especially for large systems.

Hospital and hospital outreach billing questions formed another important cluster. Several questions focused on bill type 14X versus 13X/131/141, asking whether PAMA applies only to services billed on 14X claims or also to other outpatient hospital bill types. Others asked whether joint-venture lab services billed under hospital NPI and 14X still qualify if the lab’s Medicare revenue is below $12,500 or fails the 50% test. These questions suggest that hospital outreach labs were trying to understand whether CMS’s expanded definition captures them, and if so, how to isolate outreach lab economics from broader hospital Medicare revenue.

FQHCs were a visibly anxious audience segment. Questions asked whether FQHCs with CLIA-waived certificates must report, whether lab services billed under the FQHC’s primary group NPI are reportable, how FQHC PPS payments interact with fee-for-service lab payments, whether PPS revenue is excluded, and whether PPS and FFS revenue under different NPIs should be combined. The concern here is more than administrative. FQHCs operate under a payment model that does not map neatly onto conventional fee-for-service lab revenue. They were asking whether CMS intended to sweep them into PAMA reporting and, if so, how to calculate the denominator.

The 50% majority-of-Medicare-revenues test produced a large number of questions. Participants asked what “total Medicare revenues” means, whether it includes Medicare Advantage, Managed Medicare, Part A, Part B, Part D, beneficiary deductible/coinsurance, E&M revenue, inpatient revenue, emergency room revenue, PPS revenue, or only traditional Medicare fee-for-service. Several asked whether the 50% threshold is calculated across a TIN, across a 14X bill type, across an NPI, or across the whole hospital. These questions show that the denominator was probably the single most conceptually difficult calculation for the audience.

Relatedly, the $12,500 low-expenditure threshold caused uncertainty. Participants asked whether the threshold applies to the January 1–June 30, 2025 period, whether it is evaluated after the 50% test, and whether the three applicability criteria are mutually exclusive or cumulative. One question asked, “If we don’t meet the 50% threshold but we meet the $12,500, do we qualify?” This reveals a common misunderstanding: many attendees were not sure whether the criteria are a sequence of gates, independent triggers, or alternative ways to become reportable.

There was also substantial confusion about the time period. Several questions asked whether the data collection period is based on payment date, date of service, billed date, performance date, or a full calendar year. Others asked what revenue time frame should be used for determining qualification. This indicates that the audience understood there were two related but distinct temporal questions: first, the period for assessing applicability, and second, the period for reporting private payer rates. Both appear to have been unclear to many participants.

Another major area was what payment amount to report. Attendees asked whether the private payer rate means the payer’s allowed amount, the actual amount paid by the payer, the patient portion, the combined payer-plus-patient allowed amount, denied claims, primary payer amounts only, or secondary payments as well. This is a critical business question because claims systems may store “payment,” “allowed,” “contracted,” “write-off,” and “patient responsibility” differently. The audience was signaling that the term “private payer rate” is not self-executing in revenue cycle data.

Many participants were puzzled by multiple rates for the same code. One attendee asked whether, if they have 150 payers, they must report 150 different rates for a single HCPCS code. Another asked what rate to consider when the same HCPCS code is paid by multiple private payers. These questions suggest that the audience was still thinking in terms of a single rate per code, whereas PAMA requires rate-volume observations by private payer rate. This is a fundamental conceptual shift from ordinary fee schedule thinking.

The audience also had questions about which codes are reportable. Participants asked whether CMS means CPT codes or HCPCS codes, whether specific codes such as 83861, 87798, 80307, and 80305 are included, and where to find the official HCPCS list. The repeated requests for a direct link to the code list suggest that the webinar may have described the existence of the list without enough navigational clarity for a large audience trying to follow in real time.

There was a distinct cluster around CLFS versus PFS. Audience members asked for the difference between the Medicare Clinical Laboratory Fee Schedule and the Medicare Physician Fee Schedule, whether PFS revenue means only lab-related PFS revenue, and whether PFS codes should be reported. This is an important conceptual puzzle because the PFS matters for the applicability test but not for the data submission. That split is unintuitive and likely produced much of the confusion.

Several questions dealt with global, case-rate, bundled, or non-separately reimbursed services. One participant asked what to do when contracts are case-rate or global and the lab is reimbursed for E&M codes rather than all services provided. This is a sophisticated concern: many payment arrangements do not produce a clean payer-specific payment amount for each lab HCPCS code. Such arrangements create practical ambiguity about whether there is a reportable “private payer rate” at the test-code level.

The audience also asked about Medicare Advantage and Managed Medicare repeatedly. These questions appeared both in the applicability context and in revenue calculation. Participants wanted to know whether MA revenue counts as Medicare revenue, whether it belongs in the 50% threshold, and whether it belongs in the denominator. This is a predictable concern because operationally many labs treat Medicare Advantage as Medicare-like, but legally and for PAMA purposes, “Medicare revenues” may have a more specific meaning.

There were several questions about what to do if not applicable. Attendees asked whether labs that do not qualify must notify CMS, whether they must submit a “not applicable” report, and whether a non-applicable lab may voluntarily report. This suggests fear of noncompliance by omission. For many organizations, the compliance instinct is to document exclusion affirmatively, and the absence of a “no report required” filing creates uncertainty.

There were operational questions about registration, portal access, and user roles. Participants asked for the registration link, portal link, whether IDM access through PECOS or NGS Connex works, whether there is a registration deadline, whether two practices require separate logins, and whether there will be step-by-step upload instructions. These questions are less conceptual but show that attendees anticipated friction with CMS identity management and role assignment.

The submitter/certifier model generated its own questions. Participants asked whether the submitter and certifier can be the same person, whether employees of the TIN/NPI can serve, what organizational level is required for the certifier, whether the certifier must be a clinician, and whether the same individuals can serve in roles for different TINs. This indicates concern about governance, accountability, and internal delegation. Smaller practices likely worried they may not have enough administrative separation; larger systems worried about who has authority to certify.

Data template questions were fewer but important. Participants asked whether payer plan names must be listed, whether the template should include only tests performed in the lab, and how to list multiple private payer rates for the same HCPCS code. These questions suggest that audience members were beginning to translate the rule into a spreadsheet workflow and immediately saw gaps between CMS’s four-column template and the richer data structures in billing systems.

Several attendees asked about data sources for thresholds, especially whether PS&R reports or specific 145 reports could be used to determine applicability. This reflects a practical compliance concern: labs wanted an auditable source of Medicare revenue numbers. In other words, they were not just asking how to calculate the test; they were asking what documentary basis would satisfy a compliance review.

There were also questions about database transparency and market intelligence. One attendee asked whether participating labs would have access to the entire database of reported data by test, lab, and payer for analysis. This is an interesting business concern because PAMA data reporting is not merely a compliance burden; it is also potentially a massive private payer price dataset. The question suggests that at least some participants were thinking about whether the burden of reporting would yield usable market information in return.

A smaller but notable cluster involved closed laboratories and changed business circumstances, although this topic appears more clearly in the live Q&A than in the chat index. The underlying concern is likely whether reporting obligations survive closure, acquisition, restructuring, or changes in lab identity. This fits the broader pattern: participants were worried about how PAMA applies to organizations that do not fit the simple model of a single independent lab with one TIN, one NPI, and clean payer contracts.

Finally, there were many logistical and webinar-access questions: whether the slides would be shared, whether the recording would be posted, whether the session had started, where the website is, and repeated complaints that audio was too low or cutting in and out. These are not substantive PAMA issues, but they matter because they likely intensified confusion. A topic already dense with definitions, thresholds, billing structures, and dates was being delivered in a setting where many participants could not hear clearly or could not locate the resources being described.

Bottom-Line Interpretation

The audience’s core concern was not simply “how do we report?” It was “how do we know whether our particular organization is legally and operationally visible to CMS as an applicable laboratory?” The questions show a laboratory industry with highly varied billing models: physician offices, FQHCs, hospital outreach labs, independent labs, multi-hospital systems, CLIA-waived sites, ESRD labs, joint ventures, and specialty practices. CMS’s formal rules depend on NPI, TIN, CLFS revenue, PFS revenue, Medicare revenue, private payer rates, and final payment timing. The audience was trying to reconcile those formal categories with real revenue-cycle data.

The biggest unresolved puzzles were: what counts in the Medicare revenue denominator; whether Medicare Advantage counts; how to handle FQHC and hospital outreach structures; whether CLIA-waived or physician office labs are swept in; how to distinguish CLFS from PFS; what exact payer amount should be reported; and whether multiple private payer rates must be separately listed for each code. In short, the audience wanted practical boundary rules, worked examples, and source-of-truth links more than high-level statutory background.