
Sign up to save your podcasts
Or


GRAIL Galleri Test Advances at FDA; PAMA Cuts Threaten Lab Margins
In this episode, we discuss two major developments affecting laboratory medicine: GRAIL's Galleri multi-cancer early detection test moving closer to FDA approval, and proposed Medicare reimbursement cuts that could significantly impact clinical laboratories.
We begin with the FDA advisory committee's recent review of Galleri, which received a unanimous 10–0 vote on safety but a narrower 6–4 vote on effectiveness. Despite this progress, questions remain about the test's clinical utility, particularly its relatively low sensitivity for early-stage cancers and its failure to meet the trial's primary endpoint.
We also discuss advances in Alzheimer's disease blood biomarkers, including p-tau217 testing, and the challenges laboratories face in interpreting results across different patient populations.
Finally, we examine newly released CMS data under the Protecting Access to Medicare Act (PAMA), which proposes substantial reductions in clinical laboratory reimbursement beginning in 2027. We consider what these cuts could mean for independent laboratories, industry consolidation, and access to laboratory services in rural communities.
Topics Discussed
Episode: Recent Publications and Our Lab Inspection Debrief
Episode Summary
In this episode, Dr. Zahner and Dr. Aakash dive into their recent article in The Pathologist, "The Vanishing Middle," exploring the growing structural squeeze between centralized mega-labs and decentralized point-of-care facilities. Plus, they break down a recent hospital lab inspection—sharing practical insights on leadership readiness, team culture, and the three golden rules of quality control.
Key Takeaways
Notable Quotes
"There's the centralization, regional centralization, like the big labs, and then there's the small labs, like point-of-care testing and clinical labs, and then there's the hospital, the sort of traditional hospital space."The Human Side of DMT: Trust, Fragility, and Why "Prove It" Kills Progress
Dr. Laposata on the interpersonal realities behind diagnostic management teams — why trust matters, why clinicians engage, and what holds DMTs back from wider adoption.
Episode Summary
Dr. Laposata shifts the conversation from DMT mechanics to the human dynamics that determine whether a DMT succeeds or collapses. He draws on decades of experience — from launching coagulation rounds at MGH in the mid-1990s to leading multiple DMTs at Vanderbilt — to explain why trust is built through results, not promises, and why the "prove it to me" mentality has been the single biggest barrier to adoption.
Key Takeaways
Chapters
Notable Quotes
"Only Pathologists are allowed to consult on coagulation cases."1. The Origin Story — Why Coagulation?
2. The Core Problem DMTs Solve
3. What Works — Successful DMT Models
4. What Doesn’t Work — Failed DMT Models
5. The Three Questions for Starting a DMT
6. The Real Value Proposition
Bottom Line
Start DMTs only in areas you know deeply, commit to daily operation, build redundancy, and focus on clinical impact rather than administrative metrics.
The most successful DMTs solve real diagnostic uncertainty while teaching the next generation of clinicians.
# Why 95%? The Statistical Convention Behind Reference Intervals — and Why It Misleads Patients
## Summary
Chris and Dr. Aakash explain how the 95% reference interval became the standard in laboratory medicine — not from physiology, but from a statistical convention borrowed from astronomy. They show why a healthy person has a 65% chance of flagging "abnormal" on a 20-test panel, why patients interpret red flags as disease, and why the fix isn't fewer tests but more frequent, individualized baselines.
## Key takeaways
- The 95% reference interval comes from measuring 20 healthy people and dropping the top and bottom 1 (2.5% each tail) — a statistical convention, not a disease threshold.
- On a 20-test panel, a healthy person has roughly a 65% probability of at least one result falling outside the reference interval purely by chance.
- "Normal" means four different things: analytical variability (Gaussian error), population distribution, individual baseline, and disease state — and patients hear the last one while labs report the second.
- Clinicians lack intuition for many of the 10,000+ tests labs perform (e.g., protein C/S deficiencies), yet receive no criticality context with results.
- The hosts argue for mapping flags to clinical guidelines rather than statistical cutoffs, and for serial testing to establish each patient's personal baseline — "the best reference range for me is me."
- Current cost-minimization logic (fewer tests) increases false-alarm risk; more frequent testing would reduce unnecessary interventions driven by statistical noise.
- Clinical pathology (statistics-driven) and anatomic pathology (disease-identification-driven) operate on different definitions of "normal," creating systemic confusion.
## Chapters
- The 95% convention and its astronomical origins
- Why healthy people flag "abnormal" on routine panels
- Four meanings of "normal" — and which one patients hear
- Clinician blind spots across 10,000+ tests
- Patient-facing reports: red flags without context
- Mapping results to guidelines, not Gaussian tails
- The case for serial testing and individual baselines
- CP vs. AP: two cultures of "normal"
## Mentioned
- MyChart (patient portal)
- CMP (comprehensive metabolic panel)
- CBC (complete blood count)
- Protein C, Protein S (coagulation factors)
## Quotes
> "We take a hundred percent healthy people. Yeah and measure them and then we call five percent of them unhealthy."
> "The best reference range for me is me not a random assortment of you know other people who are considered healthy."
> "The majority of costs in a health care system first of all are not lab tests. They are the interventions based on those lab tests and the fewer tests that you do the higher the probability that you're gonna freak out when you have one that's elevated or low."
# CMS Proposes Revaluing 88305 RVUs After Maryland Claims Analysis
## Summary
CMS is reconsidering RVUs for pathology codes 88305 and 88307 after the Maryland Health Care Commission analyzed 2023 all-payer claims data using CMS's own 25-minute intraservice time assumption. The analysis found 1,763 provider-days where 88305 alone implied more than 8 hours of work, and 587 days exceeding 24 hours. A 2016 Urban Institute pilot study (three sites) reported a 2-minute median intraservice time for 88305. CAP has scheduled an August 12 webinar on the proposed changes. The hosts argue the methodology ignores workflow reality — easy cases signed out quickly by dermatologists and gastroenterologists, with complex cases referred to pathologists — and call for the field to aggregate its own data to defend against sparse studies driving policy.
## Key takeaways
- CMS assigns 25 minutes of intraservice physician time to 88305 for RVU calculation; no time is submitted on claims.
- Maryland's 2023 APCD analysis multiplied 88305 volume by 25 minutes, producing 1,763 provider-days >8 hours and 587 >24 hours.
- The 2016 Urban Institute time-motion study (n=3 sites) found a 2-minute median for 88305 — used to argue 12–13x overpayment.
- Dermatology and GI clinicians often sign out easy 88305 cases (small biopsies) and refer complex cases to pathologists, skewing volume-time ratios.
- CAP announced the proposed revaluation and hosts a webinar August 12, 2026.
- The field lacks a centralized claims/outcome database to counter sparse studies; hosts suggest building one.
## Chapters
- Opening Studio Updates Personal Chat
- CAP Announcement CMS Fee Schedule
- Maryland Study Challenges 88305 Time
- CMS RVU Methodology Time Assumptions
- Maryland Letter 2016 Pilot Study
- Pathology Workflow Reality Check
- Provider Day Data Deep Dive
- CMS Next Steps August Webinar
- Field Needs Data Aggregation Strategy
# ADLM Signals, Cyclospora Surges, and CLIA Redraws the Lab
## Summary
Chris and Aakash break down three major signals from ADLM 2026: simultaneous centralization of high-throughput systems and decentralization of point-of-care testing, AI shifting from demos to implementation reality with data infrastructure as the real bottleneck, and the Cyclospora outbreak exploding to 4,200 confirmed cases across 41 states. They also unpack CMS and CDC's request for information on modernizing CLIA (last updated 1988) for AI-assisted diagnosis, remote oversight, and data-only facilities, plus the FDA-approved Elecsys sFlt-1/PlGF ratio test for pre-eclampsia risk stratification in hospitalized pregnant patients 23–34 weeks gestation.
## Key takeaways
- **Centralization and decentralization are happening simultaneously** — vendors are building massive high-throughput analyzers for core labs while pushing smaller instruments closer to patients, creating a "mismatch" in product strategy.
- **AI implementation has moved past the demo phase** — the real questions now: who monitors data drift, who owns the data, who tracks software versions, and how performance varies across patient populations.
- **Data infrastructure is the bottleneck, not algorithms** — companies gaining traction (like Bunker Hill) function as infrastructure plays, solving how to connect to health system databases; CAP is prioritizing AI inspection frameworks.
- **Cyclospora outbreak is not slowing** — 4,200 lab-confirmed domestic cases, 7,400+ probable cases under investigation, 300+ hospitalizations, 41 states; CDC warns reporting lags illness onset by ~6 weeks; linked to Taylor Farms iceberg lettuce recall (~2,000 confirmed cases).
- **Testing gaps obscure true outbreak scope** — Cyclospora isn't on routine GI panels; genetic tracking is harder than Salmonella (no whole-genome sequencing); labs may need to spin up testing if this becomes seasonal.
- **CLIA modernization RFI is a critical inflection point** — CMS/CDC asking whether AI-assisted interpretation constitutes a "test," whether data-only facilities count as labs, and how remote competency assessment works for 90+ clinic locations.
- **FDA-approved pre-eclampsia test (Elecsys sFlt-1/PlGF ratio)** — 91% sensitivity, 77% specificity for predicting severe pre-eclampsia within 2 weeks in singleton pregnancies 23–34 weeks; intended to support (not replace) clinical judgment; education needed to prevent off-label confirmatory use.
## Chapters
- Opening and Personal Catch Up
- ADLM Signals Overview
- Centralization and Decentralization Trends
- AI Implementation Beyond Demos
- Data Infrastructure as AI Bottleneck
- Cyclospora Outbreak Escalation
- CLIA Modernization Request for Information
- FDA Approved Pre-eclampsia Test
## Mentioned
- **ADLM** (Association for Diagnostics & Laboratory Medicine) — 2026 conference
- **Bunker Hill** — health AI company focused on data infrastructure/connectivity
- **CAP** (College of American Pathologists) — prioritizing AI inspection frameworks
- **CDC** — Cyclospora outbreak tracking, reporting lag warnings
- **CMS** — CLIA modernization request for information (with CDC)
- **Taylor Farms** — iceberg lettuce recall linked to Cyclospora
- **Elecsys sFlt-1/PlGF ratio** (Roche) — FDA-approved pre-eclampsia risk test
- **CLIA** (Clinical Laboratory Improvement Amendments) — 1988 legislation under review
## Quotes
> "The data infrastructure they call it a layer... is going to be as important as anything else as far as AI implementation... a lot of the health AI companies that are actually gaining real traction are almost like infrastructure companies."
> "The core important questions still need to be asked as, like who monitors the data drift, who owns that data? Who tracks these software versions and like who checks the performances differences amongst different patient populations."
> "It used to just be build the walls higher and thicker, right? That's pretty much what we thought of and now it's a very different world."
What is Disruption in the Laboratory
Defining disruption requires looking at workflow and ROI rather than just technical novelty.
Summary
Market disruption in the lab is not automatically signaled by new technologies or game-changing results. True disruption addresses underlying economic, workflow, and staffing bottlenecks. The focus should be on whether a technology simplifies the lab's work or shifts complexity elsewhere, ultimately impacting the return on investment for the institution.
Key takeaways
* Disruption in the lab must address underlying economics, workflow, and utility of results, not just technical novelty.
* Novelty alone does not equal disruption; it must solve a specific operational problem like staffing shortages or diagnostic delays.
* The key question is whether a technology removes more complexity than it creates for laboratory personnel.
* Disruption often involves shifting value capture: the lab may implement a change that benefits the clinician, making the sale harder to justify internally.
* Physical AI solutions, like robotics, represent disruption by automating manual physical processes, which can be a path forward.
* New testing methods must simplify bench work for fungal or microbiology teams rather than just expanding the scope of testing.
Mentioned
ABB, Roche, Physical AI, Mass Spec, Spine Stat, AI tool for coronary artery calcifications on CT scans.
# After the Cookout: Parasites, Pneumonia, and the Lab’s Summer Surge
## Summary
The conversation covered outbreaks like Cyclosporiasis and Legionnaires Disease, showing how laboratory testing connects to public health investigations. It also discussed the need for better data integration within labs and the potential for diagnostic informatics to drive organic growth in the lab industry.
## Key takeaways
* Outbreaks like Cyclosporiasis and Legionnaires Disease highlight the need for laboratories to act as central hubs connecting patient diagnostics with environmental and public health investigations.
* Connecting local testing data with broader signals, such as social media searches, could alert labs to potential outbreaks faster.
* The laboratory needs to move upstream by driving decisions based on aggregated data rather than just responding to requests from health systems.
* Integration of genomic profiling and molecular assays into platforms like EHRs can improve availability and utilization of testing.
* The focus for the lab industry should shift toward data informatics to facilitate organic growth, rather than solely focusing on vendor sales pitches.
## Chapters
* Welcome To LabReflex
* Summer Outbreak Effects
* Legionnaires Disease Investigation
* Connecting Data And Outbreaks
* Oncology Integration Story
* Lab As Central Hub
## Mentioned
Quest Diagnostics, Flatiron Health, ADLM 2026
DMT Defined Defining what a DMT is and what it is not.
Summary The discussion focuses on defining Diagnostic Management Teams (DMTs) by emphasizing that a true DMT must be expert-driven, patient-specific, and aim to establish a single diagnosis in the context of the patient's illness. It contrasts this with simpler processes like reflex testing or utilization management, highlighting the need for comprehensive interpretation rather than just providing test results.
Key takeaways
Chapters 0:00 Defining What A DMT Is 1:10 The Evolution Of DMTs 3:29 Critical Ingredients Of A DMT 12:45 DMT Versus Utilization Management 14:04 Reflex Testing Is Not A DMT 37:10 Checklist For Real DMTs
Mentioned Dr. Michael Appasada, Penn, Mass General, Spalding Rehabilitation Hospital, Amazon One, Amazon Health, Open Evidence AI, Plavix.
Quotes > You have to say what tests are necessary and you have to provide a diagnosis for that patient, patient specific in the clinical context of that patient. > It is a consult that is expert driven and patient specific in the context of the patient's illness. And its goal is to conclusively establish a single diagnosis. > Reflex testing is not the DMT because reflex testing says to figure out the diagnosis, you would want to do this test first based upon that you do this test or that test.
From the publisher's feed