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.

 

 

20260416 PAMA Education Session at CMS / Bruce Docu Blog

20260416 PAMA education at CMS

###

This is a second set of notes - see main DIHP blog for my initial posting of detailed notes plus links to powerpoints etc.

###

 COPY SUMMARY

20260416 CMS PAMA 1 hr

Transcript

https://otter.ai/u/rRD0iboaRruzWyADpiS0CDoyG3c?view=summary

Overview (Notes from OTTER)

The webinar, led by Sarah Shiri losso and Sarah Harding from CMS, focused on the Clinical Laboratory Fee Schedule (CLFS) data collection and reporting process. The session covered the importance of the data for future Medicare payment rates, the updated data collection period from January 1, 2025, to June 30, 2025, and the need for applicable labs to report applicable information. Key steps include verifying lab status, registering submitters and certifiers, preparing data using the provided template, and submitting data via the CMS Enterprise Portal. The webinar also addressed common questions and provided resources for further assistance.

Action Items

  • [ ] Post the recording of today’s CLFS/PAMA training webinar to the CLFS and PAMA reporting resources website immediately after the session ends.
  • [ ] Respond to any outstanding questions submitted via the CLFS inquiries email address after the webinar, ensuring that all unanswered questions are addressed.
  • [ ] Create and upload additional step-by-step user guide materials and short "YouTube-style" videos for submitter and certifier roles in the CLFS data collection system within the next few days.
  • [ ] Publish quick reference guides on how to determine applicable laboratory status on the CLFS and PAMA reporting resources website.

Outline

Introduction and Overview of the Webinar

  • Sarah Shiri losso introduces herself as the director of ambulatory services at CMS and welcomes participants to the webinar on the clinical laboratory fee schedule data collection system.
  • The webinar is being recorded and will be posted on the CLFS and PAMA reporting Resources website.
  • Participants are encouraged to use the Q&A button for questions, and frequently asked questions will be addressed during the second half of the session.
  • Sarah Harding, the CMS Medicare policy lead on laboratory payment under Medicare, will provide an overview of the program and the CLFS data collection system.

Background and Purpose of the Webinar

  • Sarah Harding explains the purpose of the webinar, which is to help participants prepare to register, submit accurate data, and understand the system and resources available.
  • The webinar is focused on clearing up definitions and providing detailed instructions on the data collection process.
  • The data collection period is from January 1, 2025, to June 30, 2025, and the data will be used to update Medicare clinical lab fee schedule payment rates for 2027 through 2029.
  • The webinar aims to address common questions and provide resources to assist participants in the data collection process.

Detailed Instructions on Data Collection and Reporting

  • Sarah Harding provides a detailed explanation of the data collection process, including the types of information that need to be reported.
  • The data collection system includes the CMS Enterprise Portal, which hosts all CMS applications, and the fee for service data collection system.
  • Participants need to verify their laboratory's applicable status and identify two individuals responsible for the data submission process.
  • The data collection template is available online, and participants are advised not to make any changes to the template to avoid rejection.

Steps for Determining Applicable Laboratory Status

  • Sarah Harding outlines the steps for determining whether a laboratory is an applicable laboratory, including evaluating the majority of Medicare revenues and calculating the threshold.
  • The data collection period is from January 1, 2025, to June 30, 2025, and the data will be used to update Medicare clinical lab fee schedule payment rates for 2027 through 2029.
  • Participants are advised to consult the CLFS and PAMA reporting Resources website for additional resources and guidance.
  • The webinar includes detailed instructions on the data collection process, including the steps for registering, preparing data, and submitting data.

Q&A Session and Additional Resources

  • Maria Durham provides a summary of key dates and upcoming tasks, including the deadline for data submission on July 31, 2026.
  • Participants are encouraged to visit the CLFS and PAMA reporting Resources website for all available resources, including registration guides, user guides, and reporting templates.
  • The webinar includes a Q&A session to address common questions and provide additional clarification on the data collection process.
  • Participants are advised to contact the CLFS Help Desk for technical assistance and the CLFS mailbox for all other inquiries.
#####
NOTES FROM ChAT GPT

Below are detailed business meeting notes from the CMS education webinar on Clinical Laboratory Fee Schedule / PAMA private payer data reporting. Source transcript:

CMS Education Webinar Notes: CLFS / PAMA Laboratory Price Reporting

CMS opened the session by welcoming laboratory stakeholders to a training webinar on the Clinical Laboratory Fee Schedule data collection system and the associated PAMA reporting requirements. CMS noted that the high level of stakeholder interest had required a midstream platform change to increase webinar capacity. The session was recorded and CMS stated that the recording would be posted to the CLFS and PAMA reporting resources website. Participants were encouraged to use the webinar Q&A function, and CMS noted that many questions had already been received through the CLFS mailbox. CMS emphasized that the purpose of the session was to help laboratories understand the reporting requirement, determine whether they are “applicable laboratories,” prepare to register in the system, submit accurate data, and use available CMS resources.

CMS explained that the statutory basis for the reporting requirement is Section 1834A of the Social Security Act, established by Section 216 of the Protecting Access to Medicare Act of 2014, commonly referred to as PAMA. Under PAMA, applicable laboratories must report certain private payer information to CMS for clinical diagnostic laboratory tests paid under the Medicare CLFS. CMS noted that the first round of PAMA data collection and reporting occurred in 2017, and that for many laboratories and even some CMS staff, this current round may feel like a new process because there has been no reporting cycle for many years. CMS attributed the delay to a series of statutory delays and pandemic-related interruptions.

CMS highlighted an important recent legislative update. The Consolidated Appropriations Act enacted February 3, 2026, updated the reporting period and the relevant data collection period. CMS explained that prior delays had created concern that the next CLFS rates could be based on 2019 data, which by the 2027–2029 rate cycle would have been roughly ten years old. Congress therefore updated the data collection period to require laboratories to report private payer data from January 1, 2025 through June 30, 2025. CMS emphasized that this updated six-month window is the period from which applicable information must be drawn.

CMS defined the core item being collected as “applicable information.” This includes, for each relevant HCPCS code on the CLFS, the private payer rate for which final payment was made during the January–June 2025 data collection period, along with the associated test volume corresponding to that specific rate. CMS stressed repeatedly that laboratories should report each distinct private payer rate separately. If a lab receives multiple different rates for the same HCPCS code, each rate should be reported on a separate line with the volume associated with that specific rate. CMS was explicit that laboratories should not average rates, should not report only the highest or lowest rate, and should not report total expenditures for a code during the collection period. The agency wants the individual rate-and-volume pairings because those data are used to calculate future Medicare CLFS payment rates.

CMS advised laboratories to benchmark suspicious values against the existing Medicare CLFS. For example, if a lab’s internal data show a private payer rate of $1,000 for a test that Medicare pays at $10, the lab should review whether the data were extracted or formatted correctly. CMS also noted that the upload system has built-in warnings for rates that appear implausibly high, such as a value that may represent total expenditures rather than a single payment rate. These warnings are intended to prompt review before certification.

CMS then described the data reporting infrastructure. Reporting begins with the CMS Enterprise Portal, which is CMS’s broader system for accessing CMS applications. Users who already have a CMS Enterprise Portal account may be able to use their existing username and password. Within the Enterprise Portal, users must access the Fee-for-Service Data Collection System, or FFS DCS, which contains several data collection modules. Laboratories must select the Clinical Laboratory Fee Schedule module, not other modules such as ASP or ground ambulance reporting. CMS acknowledged that users may see internal roles such as CLFS admin or CLFS staff, but external laboratory users should request only the submitter or certifier role.

The first substantive step for laboratories is to determine whether they are an applicable laboratory. CMS described this as the “million dollar question” and emphasized that applicability is determined at the NPI level, while reporting is organized at the TIN level. An applicable laboratory must bill Medicare Part B either under its own National Provider Identifier, or, in the case of certain hospital outreach laboratories, on the Form CMS-1450 under bill type 14X. CMS emphasized that laboratory business structures can be complex, including shared NPIs, shared physician office arrangements, and hospital outreach relationships, but the legal analysis begins with the billing NPI or 14X bill type.

CMS described the majority of Medicare revenues threshold. For a laboratory with its own NPI, the lab must calculate whether its Medicare CLFS revenue plus Medicare Physician Fee Schedule revenue, divided by its total Medicare revenue, exceeds 50 percent during the January–June 2025 data collection period. CMS emphasized an important distinction: PFS revenue is included in the applicability calculation, but PFS codes are not included in the data reported to CMS. Only CLFS codes are reported. If a laboratory attempts to upload Physician Fee Schedule codes, the upload will be rejected.

CMS also discussed the low expenditure threshold. Even if a laboratory meets the majority-of-Medicare-revenue test, it is not considered an applicable laboratory if its Medicare CLFS revenue for the relevant billing NPI is less than $12,500 during the six-month data collection period. CMS explained that this threshold was intended to reduce the reporting burden on laboratories with limited CLFS activity.

CMS separately addressed hospital outreach laboratories that bill under the hospital’s NPI using 14X type of bill. CMS explained that this was an expansion of the applicable laboratory definition compared with the first PAMA reporting cycle. For hospital outreach laboratories in this category, the numerator is CLFS plus PFS revenue under the 14X bill type, and the denominator is total Medicare revenue under the 14X bill type. CMS observed that many such outreach labs are likely to meet the majority-of-Medicare-revenue threshold because the relevant 14X Medicare revenue may consist primarily, or entirely, of CLFS and/or PFS services.

CMS emphasized that it cannot make individual applicability determinations for specific laboratories. The agency explained that it may not have sufficiently current or complete information about each laboratory’s billing structure, ownership, revenue, NPI relationships, or business model. CMS therefore expects laboratories to make a good faith determination using CMS guidance and, where needed, legal counsel. CMS pointed attendees to FAQs, flow charts, quick reference guides, videos, and other materials on the CLFS and PAMA reporting resources website. CMS specifically mentioned that several FAQ pages address physician office laboratories with shared offices, shared spaces, and shared NPIs.

The webinar then turned to user roles. Each reporting entity must identify two separate individuals: a submitter and a certifier. The submitter is selected by the laboratory, creates or uses an account in the CMS Enterprise Portal, requests the submitter role in the CLFS module, uploads the data on behalf of the relevant TIN, and notifies the certifier once data have been submitted. There can be only one submitter per TIN, although one individual may submit data for multiple TINs. The certifier must be the laboratory’s president, CFO, or an individual designated by one of those officers. The certifier creates or uses an Enterprise Portal account, requests the certifier role, reviews the submitted data, and attests to its accuracy. There can be only one certifier per TIN, and the certifier may certify on behalf of multiple TINs. CMS stressed that the submitter and certifier must be two different people.

CMS explained that submitters and certifiers must complete identity management registration through CMS’s identity verification process. Users must create a username and password, establish multifactor authentication, request access to the FFS DCS application, and request the appropriate CLFS module role. CMS advised users to use their personal identifying information during identity verification rather than business information, because the identity management system is designed for personal credentialing and business information may cause delays. CMS stated that the CLFS policy team does not see this personal information; it is maintained within CMS’s broader enterprise identity system.

CMS then described the data preparation process. Laboratories should first review the CMS-provided list of reportable HCPCS codes on the CLFS. Labs should not report codes that are not on that list, including codes paid under the Physician Fee Schedule. Laboratories should then calculate, for each CLFS HCPCS code, each distinct private payer rate for which final payment was made during the January–June 2025 data collection period, along with the volume of tests paid at that rate. CMS emphasized that laboratories should not include blank rows, should not report codes they do not perform, and should not submit empty line items.

CMS presented the data reporting template, which consists of four data columns: HCPCS code, payment rate, test volume, and NPI. CMS emphasized several times that laboratories must not alter the Excel template. They should not change the formatting, add columns, remove columns, delete tabs, move tabs, insert blank rows, or otherwise modify the structure. CMS stated that modified templates may be rejected by the upload system. The template includes an instruction tab and a data entry tab, both of which must remain intact.

CMS explained that the same HCPCS code may appear repeatedly in the template if the laboratory received multiple private payer rates for that code. This repetition is expected and appropriate. CMS also clarified a somewhat counterintuitive NPI issue. Applicability is determined at the NPI level, and submitters must register all NPIs for which they are reporting. However, once the laboratory reports at the TIN level, CMS allows the data to be aggregated under a single representative NPI within the TIN. In other words, the NPI column in the data template does not need to identify the specific NPI associated with each data row, as long as all NPIs included in the reporting have been registered in the system.

CMS advised laboratories to prepare and review the data outside the CMS system before uploading. CMS specifically recommended that the certifier pre-review the completed template before formal upload, because this may reduce the need for corrections later. If the system identifies formatting errors, the submitter—not the certifier—must correct them. If the certifier identifies substantive errors after receiving the data, the submitter must log back into the system and correct the file before final certification.

CMS described the submitter workflow. After logging into the CMS Enterprise Portal and accessing the FFS DCS application, the submitter selects the CLFS module. The submitter’s home page includes a business process flow. The submitter must associate the laboratory TIN with the relevant NPI information, upload the data file using the provided template, and generate a one-time password for the certifier. This one-time password links the certifier to the submitted data and is intended as a security measure to ensure that only the appropriate certifier can view and certify the submission.

CMS described the certifier workflow. The certifier logs into the system, associates themselves with the relevant TIN and NPI information, enters the one-time password provided by the submitter, reviews the data, and certifies its accuracy. Certification must occur inside the CMS data collection system. CMS stated that a laboratory cannot certify its data by emailing CMS or the CLFS inquiries mailbox. Reporting is not complete until certification is completed in the system. Once data are certified, the submission is closed, and the laboratory will no longer be able to enter additional data for that TIN or view the data in the system. If corrections are needed after certification, the laboratory must contact the CLFS help desk.

CMS then reviewed key dates. Laboratories can begin determining applicable lab status, selecting submitters and certifiers, and preparing their data immediately. Submitters and certifiers can create CMS Enterprise Portal accounts now. The CLFS reporting link becomes available in the FFS DCS application tile on May 1, 2026, and submitters can begin uploading data at that time. All submissions are due by 11:59 p.m. Eastern Time on July 31, 2026. CMS strongly advised laboratories not to wait until the deadline. After the reporting window closes, CMS will analyze the data during summer 2026. CMS also noted that a public meeting and a FACA meeting will occur later in 2026, with proposed and final payment determinations in fall 2026. The resulting CLFS payment rates will be effective January 1, 2027.

CMS reviewed available resources. The CLFS and PAMA reporting resources website includes registration guides, submitter and certifier user guides, the HCPCS code list, reporting templates, system videos, FAQs, quick reference guides on applicable laboratory status, and forthcoming fact sheets. CMS noted that it has received a high volume of questions and is turning recurring questions into fact sheets in real time. CMS also described outreach efforts, including certified letters sent in March to potentially applicable laboratories, email communications, MLN Connects articles, social media posts, and engagement with professional organizations such as AACC, NILA, CLC, AAFP, AMA, PACDA, and MGMA. CMS encouraged laboratories that belong to these organizations to seek additional help and resources through them.

During the Q&A, CMS clarified that total Medicare revenues, for purposes of the denominator in the majority-of-Medicare-revenues test, means the sum of all Medicare fee-for-service payments under Parts A and B, prescription drug payments under Part D, and associated Medicare beneficiary deductible or coinsurance for services furnished during the collection period. However, for hospital outreach laboratories determining applicability under the 14X type of bill, the denominator is total Medicare revenue under the 14X bill type.

CMS clarified that the data collection period is based on the date final payment was made, not the date of service. Therefore, laboratories should report private payer rates for which final payment occurred between January 1 and June 30, 2025, regardless of whether the underlying service date occurred earlier.

CMS reiterated during Q&A that it cannot tell an individual laboratory whether it is an applicable lab. The agency stated that laboratories must make their own good faith determinations because applicability depends on entity-specific billing structure, revenue data, and operational information that CMS may not possess. CMS recommended that laboratories consult legal counsel if uncertainty remains after reviewing CMS guidance.

CMS was asked whether a laboratory that has closed must report. CMS responded that under the regulation at 42 CFR § 414, a reporting entity must report applicable information for each clinical diagnostic laboratory test furnished by its component applicable laboratories during the corresponding data collection period. CMS did not provide a definitive blanket answer for closed laboratories and recommended that such laboratories consult legal counsel to determine whether they must report.

CMS also clarified that laboratories that are not applicable laboratories should not report. In response to another question, CMS stated that CLIA-waived laboratories are not categorically exempt from the reporting requirement. A laboratory that performs only CLIA-waived tests must still evaluate whether it meets the applicable laboratory definition using the same steps described in the webinar.

Overall, the webinar’s main operational message was that laboratories should begin early, determine applicability carefully at the NPI level, identify separate submitter and certifier roles at the TIN level, use CMS’s unmodified reporting template, report each distinct private payer rate and associated volume separately, avoid including non-CLFS codes, and complete both upload and certification before the July 31, 2026 deadline. CMS repeatedly emphasized that most mistakes can be avoided by using the official template, consulting the HCPCS code list, reviewing CMS’s published FAQs and guides, and allowing enough time before the deadline to address registration, formatting, identity verification, and data correction issues.

Friday, May 8, 2026

HR 8500 (LCD REFORM) in LATIN. (Easter egg: Also in German.)

HR 8500

LCD REFORM

Here is a Latin rendering of the bill text you provided. I have kept modern legal/Medicare terms in a somewhat literal Neo-Latin style, since there is no classical Latin equivalent for “Medicare administrative contractor,” “local coverage determination,” or “Social Security Act.”


H. R. 8500

Ut titulus XVIII Legis de Securitate Sociali emendetur, quo tempestiva recognitio petitionum de determinationibus localibus coverage sub programmate Medicare curetur.

IN DOMO REPRAESENTANTIUM

Die XXVII mensis Aprilis, MMXXVI

Dominus Dunn Floridensis, pro se ipso, Domina Barragán, et Domina Tenney, hoc rogationis libellum introduxit; qui ad Comitium de Modis et Mediis relatus est, atque praeterea ad Comitium de Energia et Commercio, per tempus a Praeside Domus postea statuendum, prout quaeque praescripta ad iurisdictionem cuiusque comitii pertineant.

ROGATIO LEGIS

Ut titulus XVIII Legis de Securitate Sociali emendetur, quo tempestiva recognitio petitionum de determinationibus localibus coverage sub programmate Medicare curetur.

A Senatu et Domo Repraesentantium Civitatum Foederatarum Americae in Congressu congregatis sancitum sit:


SECTIO I. Titulus brevis.

Haec lex citari potest ut “Lex de Tempestivo Accessu ad Decisiones Coverage Anni MMXXVI.”


SECTIO II. De tempestiva recognitione petitionum de determinationibus localibus coverage sub programmate Medicare.

(a) In genere.

Sectio 1862(l)(5) Legis de Securitate Sociali emendatur, addendo in fine novam subparagraphum sequentem:

“(E) Tempus statutum ad decisiones de petitionibus pro determinationibus localibus coverage.

(i) In genere. Secretarius requiret ut quisque conductor administrativus Medicare, qui petitionem formalem LCD die vel post diem nonagesimum post diem promulgationis huius subparagraphi accipit, determinet utrum talis petitio sit completa an incompleta, non serius quam intra dies LX postquam talis conductor talem petitionem acceperit.

(ii) Notificatio circa petitiones incompletas. Si conductor administrativus Medicare determinationem sub clausula (i) facit, qua petitionem formalem LCD incompletam esse statuit, talis conductor, non serius quam intra dies LX post diem quo talem petitionem accepit, mittet enti quod petitionem submisit notificationem scriptam huius determinationis, quae singula indicet quae informationes additae necessariae sint ut petitio completa fiat.

(iii) Tempus decisionis pro petitionibus completis. Si conductor administrativus Medicare determinationem sub clausula (i) facit, qua petitionem formalem LCD completam esse statuit, talis conductor, non serius quam intra annum unum post diem quo talem petitionem accepit, actiones describtas in clausulis (i) et (ii) subparagraphi (D) peraget.

(iv) Definitio petitionis formalis LCD. In hoc subparagrapho, vocabulum ‘petitio formalis LCD’ significat documentum quod se ipsum formalem petitionem pro determinatione locali coverage esse declarat.”


(b) Petitiones reconsiderationis.

Sectio 1862(l)(5) Legis de Securitate Sociali, ut per subsectionem (a) emendata est, ulterius emendatur addendo in fine novas subparagraphos sequentes:

“(F) Tempus statutum ad decisiones de petitionibus reconsiderationis pro determinationibus localibus coverage.

(i) In genere. Secretarius requiret ut quisque conductor administrativus Medicare, qui petitionem formalem reconsiderationis die vel post diem nonagesimum post diem promulgationis huius subparagraphi accipit, determinet utrum talis petitio sit completa an incompleta, non serius quam intra dies LX postquam talis conductor talem petitionem acceperit.

(ii) Notificatio circa petitiones incompletas. Si conductor administrativus Medicare determinationem sub clausula (i) facit, qua petitionem formalem reconsiderationis incompletam esse statuit, talis conductor, non serius quam intra dies LX post diem quo talem petitionem accepit, mittet enti quod petitionem submisit notificationem scriptam huius determinationis, quae singula indicet quae informationes additae necessariae sint ut petitio completa fiat.

(iii) Tempus decisionis pro petitionibus completis. Si conductor administrativus Medicare determinationem sub clausula (i) facit, qua petitionem formalem reconsiderationis completam esse statuit, talis conductor, non serius quam intra annum unum post diem quo talem petitionem accepit, actiones describtas in clausulis (i) et (ii) subparagraphi (D) peraget.

(iv) Definitiones. In hoc subparagrapho:

(I) Petitio formalis reconsiderationis. Vocabulum ‘petitio formalis reconsiderationis’ significat, quoad conductorem administrativum Medicare, documentum quod—

(aa) se ipsum formalem petitionem pro reconsideratione partis vel totius determinationis localis coverage finalis a tali conductore factae pro area geographica declarat; et

(bb) ab parte cuius interest submittitur.

(II) Pars cuius interest. Vocabulum ‘pars cuius interest’ significat, quoad determinationem localem coverage a conductore administrativo Medicare factam pro area geographica—

(aa) individuum beneficiis sub parte A intitulatum vel sub parte B inscriptum, quod in tali area habitat aut res vel servitia in tali area accipit;

(bb) provisorem servitiorum vel suppeditatorem qui in tali area res vel servitia tali determinationi subiecta praebet, confert, aut suppeditat; vel

(cc) quodvis ens quod Secretarius partem cuius interest in tali area esse statuit.

“(G) Recognitio agentiae decisionis reconsiderationis.

Ad petitionem partis cuius interest, ut in subparagrapho (F)(iv) definitur, Secretarius recognoscet determinationem finalem, ut in subparagrapho (D)(ii) definitur, factam a conductore administrativo Medicare post petitionem formalem reconsiderationis completam sub subparagrapho (F). Talis recognitio includet analysin utrum—

(i) determinatio non applicaverit, aut perperam interpretata sit, probationem qualificatam, ut in subparagrapho (D)(iv) definitur, quae ad talem determinationem pertineat;

(ii) determinatio linguam adhibuerit quae fines propositi determinationis excesserit;

(iii) determinatio erraverit in statuendo utrum res vel servitium sit rationabile et necessarium ad diagnosis vel curationem morbi aut iniuriae sub sectione 1862(a)(1)(A);

(iv) determinatio non descripserit, quoad talem rem vel servitium, condiciones clinicas adhibendas ad statuendum utrum talis res vel servitium sit rationabile et necessarium ad diagnosis vel curationem morbi aut iniuriae sub sectione 1862(a)(1)(A);

(v) determinatio non applicetur rebus vel servitiis quibus destinata erat applicari; vel

(vi) determinatio cum alia lege, regula, regulatione, aut determinatione nationali coverage pugnet, prout Secretarius statuerit.”


(c) Processus evolutionis pro determinationibus localibus coverage specificatis.

Sectio 1862(l)(5)(D) Legis de Securitate Sociali emendatur ut ita legatur:

“(D) Processus edendi determinationes locales coverage specificatas.

(i) In genere. In casu determinationis localis coverage specificatae, ut in clausula (iii) definitur, intra aream a conductore administrativo Medicare factae, talis conductor has actiones circa talem determinationem peragere debet antequam talis determinatio vim habere possit:

(I) Publicare in pagina publica interretiali Centrorum pro Medicare et Medicaid Services, vulgo dicta ‘Medicare Coverage Database’ sive pagina successoria, et in pagina publica interretiali conductoris administrativi Medicare, versionem propositam determinationis localis coverage specificatae, quae in hoc subparagrapho ‘determinatio draft’ appellatur, una cum quavis informatione de codificatione vel computatione mercedum, ratione scripta pro determinatione draft, et descriptione omnis probationis qua conductor in evolutione determinationis draft usus est et quam consideravit.

(II) Non serius quam intra dies LX post diem quo conductor administrativus Medicare determinationem draft secundum subclausulam (I) publicat—

(aa) unum vel plura conventus apertos et publicos convocare ad determinationem draft recognoscendam, et, quoad quemque conventum, instrumenta praebere quibus publicum remoto modo interesse possit, atque agendam pro tali conventu saltem XIV diebus ante publice accessibilem facere;

(bb) commentarios circa determinationem draft accipere; et

(cc) consilium tabulae peritorum obtinere, quae includet—

(AA) unum vel plures medicos;

(BB) unum vel plures sodales Comitatus Consiliarii Conductoris, ut in capite XIII Manualis Integritatis Programmatum Medicare describitur, prout die XII Februarii MMXIX valebat; et

(CC) unum vel plura entia quae pro uno vel pluribus individuis beneficiis sub parte A intitulatis vel sub parte B inscriptis advocent.

(III) Quoad quemque conventum sub subclausula (II)(aa) convocatum, in pagina publica interretiali conductoris, non serius quam intra dies XIV postquam talis conventus convocatus est, acta talis conventus publicare, quae includere possint tabulam video vel audio conventus.

(IV) Tempus submissionis commentariorum publicorum scriptorum de tali determinatione draft praebere, quod incipiat die quo omnia acta, quae circa talem determinationem draft sub subclausula (III) publicanda sunt, ita publicata sunt, et quod non minus quam dies XXX duret.


“(ii) Finalisatio determinationis localis coverage specificatae.

(I) In genere. Subiecta subclausulae (II), conductor administrativus Medicare qui contractum cum Secretario sub sectione 1874A iniit, antequam determinatio localis coverage specificata, quae in hoc subparagrapho ‘determinatio finalis’ appellatur, vim habeat, in Medicare Coverage Database et in pagina publica interretiali conductoris sequentia publicabit:

(aa) Responsionem ad commentarios publicos acceptos et ad quaestiones pertinentes in conventibus sub clausula (i)(II)(aa) convocatis circa determinationem draft propositas.

(bb) Textum plenum omnium talium commentariorum publicorum acceptorum.

(cc) Rationem determinationis finalis.

(dd) Si conductor administrativus Medicare probationem qualificatam, ut in clausula (v) definitur, in evolutione determinationis consideravit quae in notificatione scripta sub clausula (i)(I) provisa non descripta erat, descriptionem talis probationis qualificatae.

(ee) Diem effectivum determinationis finalis, qui non minus quam dies XLV post diem quo talis determinatio ita publicata est futurus est.

(II) Requisitum progressionis logicae. Non obstante subclausula (I), determinatio finalis vim habere non potest nisi talis determinatio sit progressio logica determinationis draft sub clausula (i) publicatae.


“(iii) Definitio determinationis localis coverage specificatae.

Ad usus huius subparagraphi, vocabulum ‘determinatio localis coverage specificata’ significat, quoad aream geographicam pertinentem—

(I) novam determinationem localem coverage;

(II) determinationem localem coverage revisam quae revisionem substantivam uni vel pluribus determinationibus localibus coverage iam exsistentibus facit, sicut imponendo nova requisita circa coverage rei vel servitii pertinentis, aut mutando quamlibet informationem de codificatione vel computatione mercedum ad talem determinationem pertinentem; vel

(III) quamlibet aliam determinationem localem coverage a Secretario per regulationes specificatam.


“(iv) Definitio probationis qualificatae.

Ad usus huius subparagraphi, vocabulum ‘probatio qualificata’ significat probationem publice accessibilem de generali acceptione a communitate medica, quales sunt investigationes originales in diariis medicis pari recognitione editis, recensiones systematicae et meta-analyses, sententiae consensuales probationibus innixae, et praecepta clinica.”


(d) Dies effectivus.

Haec sectio, et emendationes per hanc sectionem factae, applicabuntur incipiendo die qui est annus unus post diem promulgationis huius sectionis.

##

##

##

Easter Egg: Also German.

Here is a contemporary German translation, aiming for clear normal German, not stiff legal German. Source text:


H. R. 8500 GERMAN

Ein Gesetzentwurf zur Änderung von Titel XVIII des Social Security Act, um eine zeitnahe Prüfung von Anträgen auf lokale Medicare-Abdeckungsentscheidungen sicherzustellen.

Im Repräsentantenhaus

27. April 2026

Herr Dunn aus Florida brachte diesen Gesetzentwurf für sich selbst, Frau Barragán und Frau Tenney ein. Der Entwurf wurde an den Ausschuss für Ways and Means sowie zusätzlich an den Ausschuss für Energy and Commerce überwiesen, jeweils für die Teile, die in die Zuständigkeit des jeweiligen Ausschusses fallen. Die Dauer dieser Überweisung wird später vom Sprecher des Repräsentantenhauses festgelegt.

Gesetzentwurf

Zur Änderung von Titel XVIII des Social Security Act, um eine zeitnahe Prüfung von Anträgen auf lokale Medicare-Abdeckungsentscheidungen sicherzustellen.

Beschlossen durch den Senat und das Repräsentantenhaus der Vereinigten Staaten von Amerika im Kongress:


Abschnitt 1. Kurztitel

Dieses Gesetz kann als „Timely Access to Coverage Decisions Act of 2026“ bezeichnet werden — auf Deutsch etwa: „Gesetz von 2026 über den zeitnahen Zugang zu Abdeckungsentscheidungen.“


Abschnitt 2. Zeitnahe Prüfung von Anträgen auf lokale Medicare-Abdeckungsentscheidungen

(a) Allgemein

Section 1862(l)(5) des Social Security Act wird geändert, indem am Ende der folgende neue Unterabschnitt eingefügt wird:

„(E) Fristen für Entscheidungen über Anträge auf lokale Abdeckungsentscheidungen

(i) Allgemein. Der Secretary muss jeden Medicare Administrative Contractor verpflichten, der an oder nach dem Tag, der 90 Tage nach Inkrafttreten dieses Unterabschnitts liegt, einen formellen LCD-Antrag erhält, spätestens 60 Tage nach Eingang des Antrags festzustellen, ob der Antrag vollständig oder unvollständig ist.

(ii) Mitteilung bei unvollständigen Anträgen. Wenn ein Medicare Administrative Contractor nach Absatz (i) feststellt, dass ein formeller LCD-Antrag unvollständig ist, muss er der Stelle, die den Antrag eingereicht hat, spätestens 60 Tage nach Eingang des Antrags eine schriftliche Mitteilung über diese Entscheidung übermitteln. Diese Mitteilung muss genau angeben, welche zusätzlichen Informationen erforderlich sind, damit der Antrag vollständig wird.

(iii) Entscheidungsfrist bei vollständigen Anträgen. Wenn ein Medicare Administrative Contractor nach Absatz (i) feststellt, dass ein formeller LCD-Antrag vollständig ist, muss er spätestens ein Jahr nach Eingang des Antrags die in Unterabschnitt (D), Absätze (i) und (ii), beschriebenen Schritte durchführen.

(iv) Definition eines formellen LCD-Antrags. In diesem Unterabschnitt bedeutet der Begriff „formeller LCD-Antrag“ ein Dokument, das sich selbst als formellen Antrag auf eine lokale Abdeckungsentscheidung bezeichnet.“


(b) Anträge auf erneute Prüfung

Section 1862(l)(5) des Social Security Act wird, wie durch Unterabschnitt (a) geändert, weiter geändert, indem am Ende die folgenden neuen Unterabschnitte eingefügt werden:

„(F) Fristen für Entscheidungen über Anträge auf erneute Prüfung lokaler Abdeckungsentscheidungen

(i) Allgemein. Der Secretary muss jeden Medicare Administrative Contractor verpflichten, der an oder nach dem Tag, der 90 Tage nach Inkrafttreten dieses Unterabschnitts liegt, einen formellen Antrag auf erneute Prüfung erhält, spätestens 60 Tage nach Eingang des Antrags festzustellen, ob der Antrag vollständig oder unvollständig ist.

(ii) Mitteilung bei unvollständigen Anträgen. Wenn ein Medicare Administrative Contractor nach Absatz (i) feststellt, dass ein formeller Antrag auf erneute Prüfung unvollständig ist, muss er der Stelle, die den Antrag eingereicht hat, spätestens 60 Tage nach Eingang des Antrags eine schriftliche Mitteilung über diese Entscheidung übermitteln. Diese Mitteilung muss genau angeben, welche zusätzlichen Informationen erforderlich sind, damit der Antrag vollständig wird.

(iii) Entscheidungsfrist bei vollständigen Anträgen. Wenn ein Medicare Administrative Contractor nach Absatz (i) feststellt, dass ein formeller Antrag auf erneute Prüfung vollständig ist, muss er spätestens ein Jahr nach Eingang des Antrags die in Unterabschnitt (D), Absätze (i) und (ii), beschriebenen Schritte durchführen.

(iv) Definitionen. In diesem Unterabschnitt gilt:

(I) Formeller Antrag auf erneute Prüfung. Der Begriff „formeller Antrag auf erneute Prüfung“ bedeutet, bezogen auf einen Medicare Administrative Contractor, ein Dokument, das—

(aa) sich selbst als formellen Antrag auf erneute Prüfung eines Teils oder der Gesamtheit einer endgültigen lokalen Abdeckungsentscheidung bezeichnet, die dieser Contractor für ein bestimmtes geografisches Gebiet getroffen hat; und

(bb) von einer interessierten Partei eingereicht wird.

(II) Interessierte Partei. Der Begriff „interessierte Partei“ bedeutet, bezogen auf eine lokale Abdeckungsentscheidung eines Medicare Administrative Contractors für ein bestimmtes geografisches Gebiet—

(aa) eine Person, die Anspruch auf Leistungen nach Part A hat oder in Part B eingeschrieben ist und in diesem Gebiet wohnt oder dort Waren oder Leistungen erhält;

(bb) einen Leistungserbringer oder Anbieter, der in diesem Gebiet Waren oder Leistungen bereitstellt, erbringt oder liefert, die von dieser Entscheidung betroffen sind; oder

(cc) jede andere Stelle, die der Secretary in diesem Gebiet als interessierte Partei bestimmt.


„(G) Prüfung einer Entscheidung über erneute Prüfung durch die Behörde

Auf Antrag einer interessierten Partei, wie in Unterabschnitt (F)(iv) definiert, muss der Secretary die endgültige Entscheidung eines Medicare Administrative Contractors überprüfen, die nach einem vollständigen formellen Antrag auf erneute Prüfung nach Unterabschnitt (F) getroffen wurde. Diese Prüfung muss analysieren, ob—

(i) die Entscheidung relevante qualifizierte Evidenz, wie in Unterabschnitt (D)(iv) definiert, nicht berücksichtigt oder falsch interpretiert hat;

(ii) die Entscheidung Formulierungen verwendet hat, die über den beabsichtigten Zweck der Entscheidung hinausgehen;

(iii) die Entscheidung falsch beurteilt hat, ob die betreffende Ware oder Leistung nach Section 1862(a)(1)(A) vernünftig und notwendig für die Diagnose oder Behandlung einer Krankheit oder Verletzung ist;

(iv) die Entscheidung es versäumt hat, für eine solche Ware oder Leistung die klinischen Bedingungen zu beschreiben, anhand derer bestimmt werden soll, ob die Ware oder Leistung nach Section 1862(a)(1)(A) vernünftig und notwendig für die Diagnose oder Behandlung einer Krankheit oder Verletzung ist;

(v) die Entscheidung nicht auf die Waren oder Leistungen anwendbar ist, auf die sie eigentlich angewendet werden sollte; oder

(vi) die Entscheidung mit einem anderen Gesetz, einer Regel, einer Vorschrift oder einer nationalen Abdeckungsentscheidung kollidiert, wie vom Secretary festgestellt.“


(c) Entwicklungsprozess für bestimmte lokale Abdeckungsentscheidungen

Section 1862(l)(5)(D) des Social Security Act wird geändert und lautet künftig:

„(D) Verfahren zur Herausgabe bestimmter lokaler Abdeckungsentscheidungen

(i) Allgemein. Bei einer bestimmten lokalen Abdeckungsentscheidung, wie in Absatz (iii) definiert, die ein Medicare Administrative Contractor für ein Gebiet trifft, muss der Contractor die folgenden Schritte durchführen, bevor die Entscheidung in Kraft treten kann:

(I) Er muss auf der öffentlichen Website der Centers for Medicare & Medicaid Services, die allgemein als „Medicare Coverage Database“ bezeichnet wird — oder auf einer Nachfolge-Website — sowie auf der öffentlichen Website des Medicare Administrative Contractors eine vorgeschlagene Fassung der bestimmten lokalen Abdeckungsentscheidung veröffentlichen. Diese wird in diesem Unterabschnitt als „Entwurfsentscheidung“ bezeichnet. Außerdem müssen alle zugehörigen Kodierungs- oder Abrechnungsinformationen, eine schriftliche Begründung für die Entwurfsentscheidung und eine Beschreibung der gesamten Evidenz veröffentlicht werden, auf die sich der Contractor bei der Entwicklung der Entwurfsentscheidung gestützt oder die er dabei berücksichtigt hat.

(II) Spätestens 60 Tage nach Veröffentlichung der Entwurfsentscheidung gemäß Unterabsatz (I) muss der Medicare Administrative Contractor—

(aa) eine oder mehrere offene öffentliche Sitzungen einberufen, um die Entwurfsentscheidung zu prüfen. Für jede solche Sitzung muss er der Öffentlichkeit eine Möglichkeit zur Fernteilnahme bereitstellen und die geplante Tagesordnung mindestens 14 Tage im Voraus öffentlich zugänglich machen;

(bb) Kommentare zur Entwurfsentscheidung entgegennehmen; und

(cc) den Rat eines Expertengremiums einholen. Dieses Gremium muss umfassen—

(AA) einen oder mehrere Ärzte;

(BB) ein oder mehrere Mitglieder des Contractor Advisory Committee, wie es in Kapitel 13 des Medicare Program Integrity Manual beschrieben ist, in der am 12. Februar 2019 geltenden Fassung; und

(CC) eine oder mehrere Organisationen, die sich für Personen einsetzen, die Anspruch auf Leistungen nach Part A haben oder in Part B eingeschrieben sind.

(III) Für jede Sitzung nach Unterabsatz (II)(aa) muss der Contractor spätestens 14 Tage nach der Sitzung auf seiner öffentlichen Website eine Aufzeichnung oder Zusammenfassung der Sitzung veröffentlichen. Dies kann auch eine Video- oder Audioaufzeichnung der Sitzung sein.

(IV) Er muss eine Frist für schriftliche öffentliche Kommentare zu dieser Entwurfsentscheidung vorsehen. Diese Frist beginnt an dem Tag, an dem alle nach Unterabsatz (III) erforderlichen Sitzungsunterlagen zu dieser Entwurfsentscheidung veröffentlicht wurden, und muss mindestens 30 Tage dauern.


„(ii) Abschluss einer bestimmten lokalen Abdeckungsentscheidung

(I) Allgemein. Vorbehaltlich Unterabsatz (II) muss ein Medicare Administrative Contractor, der einen Vertrag mit dem Secretary nach Section 1874A abgeschlossen hat, bevor eine bestimmte lokale Abdeckungsentscheidung — in diesem Unterabschnitt als „endgültige Entscheidung“ bezeichnet — in Kraft tritt, die folgenden Informationen in der Medicare Coverage Database und auf der öffentlichen Website des Contractors veröffentlichen:

(aa) eine Antwort auf die eingegangenen öffentlichen Kommentare und auf die relevanten Fragen, die in den Sitzungen nach Absatz (i)(II)(aa) zur Entwurfsentscheidung aufgeworfen wurden;

(bb) den vollständigen Text aller eingegangenen öffentlichen Kommentare;

(cc) die Begründung für die endgültige Entscheidung;

(dd) falls der Medicare Administrative Contractor bei der Entwicklung der Entscheidung qualifizierte Evidenz berücksichtigt hat, wie in Absatz (v) definiert, die in der schriftlichen Mitteilung nach Absatz (i)(I) nicht beschrieben wurde, eine Beschreibung dieser qualifizierten Evidenz;

(ee) ein Datum, an dem die endgültige Entscheidung wirksam wird, wobei dieses Datum mindestens 45 Tage nach der Veröffentlichung der Entscheidung liegen muss.

(II) Erfordernis einer logischen Weiterentwicklung. Ungeachtet Unterabsatz (I) darf eine endgültige Entscheidung nicht in Kraft treten, es sei denn, sie ist eine logische Weiterentwicklung der nach Absatz (i) veröffentlichten Entwurfsentscheidung.


„(iii) Definition einer bestimmten lokalen Abdeckungsentscheidung

Für die Zwecke dieses Unterabschnitts bedeutet der Begriff „bestimmte lokale Abdeckungsentscheidung“, bezogen auf das relevante geografische Gebiet—

(I) eine neue lokale Abdeckungsentscheidung;

(II) eine überarbeitete lokale Abdeckungsentscheidung, die eine wesentliche Änderung an einer oder mehreren bestehenden lokalen Abdeckungsentscheidungen vornimmt, etwa indem sie neue Anforderungen für die Abdeckung der betreffenden Ware oder Leistung einführt oder Kodierungs- oder Abrechnungsinformationen im Zusammenhang mit dieser Entscheidung ändert; oder

(III) jede andere lokale Abdeckungsentscheidung, die der Secretary durch Vorschriften bestimmt.


„(iv) Definition qualifizierter Evidenz

Für die Zwecke dieses Unterabschnitts bedeutet der Begriff „qualifizierte Evidenz“ öffentlich zugängliche Evidenz für eine allgemeine Akzeptanz in der medizinischen Fachwelt, zum Beispiel veröffentlichte Originalforschung in peer-reviewten medizinischen Fachzeitschriften, systematische Übersichtsarbeiten und Meta-Analysen, evidenzbasierte Konsenserklärungen und klinische Leitlinien.“


(d) Inkrafttreten

Dieser Abschnitt und die durch ihn vorgenommenen Änderungen gelten ab dem Tag, der ein Jahr nach Inkrafttreten dieses Abschnitts liegt.

Thursday, May 7, 2026

Has GRAIL Considered GALLERI as a Diagnostic Test for "Possible Cancer" e.g. weight loss

GRAIL has repeatedly and publicly described a second product direction called DAC — Diagnostic Aid for Cancer — aimed at patients with non-specific signs and symptoms plus clinical suspicion of cancer, distinct from Galleri’s main asymptomatic MCED screening use case.

The cleanest public highlight is GRAIL’s own current page: https://grail.com/diagnostic-aid-for-cancer/

“We are developing our diagnostic aid for cancer (‘DAC’) test to accelerate diagnostic resolution for patients with non-specific signs and symptoms, but with a clinical suspicion of cancer.”

GRAIL says DAC is intended to help physicians “aid diagnosis, achieve resolution more quickly, and avoid unnecessary workups,” and estimates that about 16 million U.S. patients present each year with such non-specific signs and symptoms.

The strongest SEC evidence is even more explicit. In GRAIL’s spinout registration materials, the company described DAC as a test to “accelerate diagnostic resolution” in patients with non-specific signs and symptoms but clinical suspicion of cancer. It also said the product was a medium- to longer-term objective, with launch dependent on factors including U.S. reimbursement requirements. In the same filing, GRAIL quantified the clinical/economic story: about 16 million U.S. patients with non-specific signs/symptoms; more than 70% undergo imaging, scoping, biopsies or other procedures; more than 25% take over four months to reach diagnosis after referral; and only about 4% ultimately have cancer.

So the public thesis was very close to what you described: use a blood-based multi-cancer signal and cancer-signal-origin result to triage or route patients earlier in the diagnostic workup, instead of sending them through serial, organ-specific workups. GRAIL’s 2023 ASCO release on SYMPLIFY said the test showed feasibility in helping clinicians decide the route of referral from primary care. It specifically named symptoms like weight loss, anemia, and abdominal pain, and quoted the need for tools that could expedite diagnosis and potentially avoid invasive or costly investigations.

The Lancet Oncology/SYMPLIFY press materials reinforce the same public narrative. SYMPLIFY enrolled over 6,000 symptomatic patients referred for urgent diagnostic follow-up for suspected cancer. GRAIL said the study suggested the MCED methylation platform could assist referral decisions from primary care; the commonly reported symptoms included unexpected weight loss, bowel-habit change, post-menopausal bleeding, rectal bleeding, abdominal pain, pain, dysphagia, and anemia.

GRAIL also funded/postered real-world work in U.S. nonspecific-signs/symptoms patients. That AACR 2023 poster listed NSSS such as weight loss, anemia, fatigue, pain, malaise, nonspecific abdominal symptoms, abnormal labs, abnormal LFTs, abnormal iron, abnormal platelets/WBCs, and argued that these symptoms may lack a clear diagnostic pathway, causing undirected or misdirected evaluation. The conclusion proposed that a multi-cancer detection test could help stratify cancer risk and direct diagnostic evaluation in NSSS patients.

There is also public evidence that GRAIL later pulled back. In August 2024, after its spinout and portfolio review, GRAIL announced a restructuring focused on the core MCED/Galleri opportunity and said it was substantially decreasing investment in product programs beyond Galleri, including diagnostic aid for cancer and MRD. The November 2024 10-Q repeats that GRAIL had reduced investment in products beyond Galleri, including DAC. Reuters summarized the same restructuring as a 350-job reduction and a focus on Galleri.

So, in blog/diligence prose, I’d say:

Public documents show that GRAIL pursued, for several years, a second major use case beyond asymptomatic MCED screening: a “Diagnostic Aid for Cancer” for patients with non-specific symptoms and clinical suspicion of cancer. The premise was that a blood-based multi-cancer signal and tissue-of-origin prediction could help physicians route patients faster and avoid long, serial, organ-specific workups. GRAIL supported this strategy with SYMPLIFY and with U.S. real-world NSSS studies. But public filings also show that after its 2024 spinout, GRAIL substantially decreased investment in DAC and refocused resources on Galleri/MCED, with U.S. reimbursement requirements named as one of the gating factors for DAC commercialization.

#

#

16M possible cancers vs $2m actual incident cancers, circa 8X for $614 test vs circa $400 CT-MRI.

The goal is praiseworthy.  

The public-health denominator is the problem. The United States diagnoses about 2.1 million cancers per year, excluding common non-melanoma skin cancers. The top 15 cancer types account for roughly 1.8 million of those cases. But a “possible cancer” indication may sweep in something like 16 million Americans with anemia, weight loss, fatigue, vague abdominal symptoms, abnormal labs, or other non-specific findings. That is not a cancer population; it is a vast diagnostic-anxiety population in which cancer is the minority outcome. For payers, that makes policy writing, utilization control, and evidence expectations far harder than the phrase “diagnostic aid” might suggest.

Roche: From BioImagene to PathAI

 Roche acquired BioImagene in August 2010, through Ventana Medical Systems, for about $100 million. At the time, BioImagene was a Sunnyvale digital pathology company led by Ajit Singh, and the logic was straightforward: Roche/Ventana already had tissue diagnostics, IHC/ISH, breast-marker image analysis, and the lab footprint; BioImagene added scanning/workflow/digital-slide management capability. (PharmaTimes)

My read: not exactly a fizzle, but an absorption. BioImagene did not become a visible, standalone Roche growth engine. It seems to have been folded into the Ventana/Roche Tissue Diagnostics stack. The old BioImagene language became “Ventana digital pathology, powered by BioImagene,” and products such as Virtuoso and iScan/Coreo appear in the early post-acquisition period. Ventana launched Virtuoso 5.0 in 2011 as software for image acquisition, case management, reporting, and collaboration. (LinkedIn)

So I’d describe BioImagene this way:

BioImagene gave Roche an early digital pathology substrate, but Roche did not become the Apple of digital pathology from that acquisition. It became part of a long, incremental Ventana/Roche tissue-diagnostics evolution: scanners, workflow software, IHC algorithms, uPath, NAVIFY, and now FDA-cleared whole-slide imaging systems.

Roche’s current digital pathology offering is real, but it has had a somewhat quiet, platform-adjacent feel compared with Leica/Aperio or some scanner-first competitors. Roche now markets the VENTANA DP 200 and DP 600 scanners, uPath / NAVIFY Digital Pathology enterprise software, and image-analysis algorithms tied to Roche tissue assays. The DP 200 received FDA 510(k) clearance for diagnostic use in June 2024; the DP 600 high-volume scanner received FDA clearance in early 2025. (Diagnostics)

The reason Roche’s digital pathology may feel less visible is that Roche’s strategic center of gravity is not “scanner company.” It is oncology tissue diagnostics (Ventana) plus companion diagnostics plus pharma-linked biomarker development. Leica/Aperio often feels more like a digital pathology infrastructure vendor. Roche feels more like: “We own the stain, the assay, the pathologist workflow, the CDx relationship, the oncology drug context, and now we need the digital/AI layer to make that more powerful.”

That is where PathAI fits.

Roche announced on May 7, 2026 that it agreed to acquire PathAI for $750 million upfront, plus up to $300 million in milestone payments, with expected closing in the second half of 2026. Roche says PathAI will be integrated into Roche Diagnostics and that PathAI’s image management system, advanced AI analysis, and workflow capabilities will complement Roche’s digital pathology portfolio. (Roche)

This was not a random bolt-on. Roche and PathAI had already partnered since 2021, and in 2024 expanded the relationship to develop AI-enabled companion diagnostic algorithms. (Roche Assets)

So the logic is:

BioImagene = early digital pathology infrastructure layer.
Ventana/uPath/NAVIFY = Roche’s internalized pathology workflow and assay-linked digital platform.
PathAI = modern AI/algorithm, image-management, biopharma/translational, and companion-diagnostic acceleration layer.

In plainer English: Roche bought BioImagene before the market was really ready. It probably helped seed Roche’s internal digital pathology capability, but it did not produce a market-defining independent digital pathology franchise. Fifteen years later, Roche is buying PathAI because the market has finally shifted: scanners are cleared, labs are digitizing, pharma wants AI pathology endpoints, and companion diagnostics increasingly need richer image-based interpretation.

Roche could acquier BioImagene for only $100M.  Now in 2026, Roche is paying much more for PathAI because the same thesis has become more actionable: digital pathology is no longer just slide viewing; it is AI-enabled tissue interpretation linked to oncology drugs, biomarkers, and CDx.

Tuesday, May 5, 2026

How Does Canada Code Healthcare? A quick look.

https://chatgpt.com/c/69f9f395-21e0-83e8-8b30-c30c6af3be0f 


I understand Canada national (sort of provincial) health insurance is largely built on fee for s ervice, what coding do they use,? Is it US AMA CPT? Or ICD Procedures? Or??