This website uses cookies

Read our Privacy policy and Terms of use for more information.

S

Hey friends, “Is this covered?” sounds like one question. It’s actually nine questions wearing a trench coat. Most people do not notice until one of them produces a denial. This week, we are taking the coat apart one piece at a time. Meet Eleanor. She is 69, enrolled in Original Medicare, and has never been diagnosed with cancer. She is also Biscuit’s aunt—a small connection for regular readers, but you do not need to know Biscuit or any previous pre·imbursed characters to follow her story. By the end, you will know what CMS actually does, where national and local Medicare policies come from, why a code and a price do not guarantee payment, and how to research the answer before a claim is submitted - Tania

Hey there, We’re Shivang & Tania. Each week, we write in plain English (and some sass) about how health insurance works, why claims get denied, and how patients and healthcare teams can get paid or reimbursed. If you’re new here, we recommend you start with Health insurance 101 (and why your checkup costs $1,000s)

Eleanor’s question

Eleanor’s mother had breast cancer. During an outpatient visit, Dr. Singh, Eleanor’s physician, recommends a hereditary-cancer genetic panel: a blood test that looks for inherited variants associated with cancer risk.

Eleanor asks the only question she cares about: “Will Medicare cover and pay for this test?”

Otis, the claims expert, does not answer right away.

“That’s not one question,” he says. “It’s at least nine, and they don’t all get answered by the same person or document.”

Otis places nine empty puzzle pieces on the table:

  1. Program

  2. Legal authority

  3. Coverage policy

  4. MAC and jurisdiction

  5. Coding

  6. Documentation

  7. Applicable policy version

  8. Payment methodology

  9. Eleanor’s individual facts

Those nine pieces, not any one document, determine the answer.

A published code and price may look like proof Medicare will pay, but neither one establishes clear coverage.

What is CMS, and how is Medicare different from Medicaid?

First piece: which healthcare program are we dealing with?

A senior bloodhound in a navy blazer steps in. This is Mabel, a CMS official who explains the federal Medicare framework.

“I’m not your insurance plan,” she tells Eleanor. “CMS is the Centers for Medicare & Medicaid Services, a federal agency within the Department of Health and Human Services. CMS administers Medicare, works with states to oversee Medicaid, and carries out its work through contractors, states, and Medicare-approved private plans.”

CMS says its programs provide health coverage to more than 160 million people through Medicare, Medicaid, CHIP, and the Health Insurance Marketplace. But CMS headquarters does not personally process most individual claims. [1]

Medicare is primarily health insurance for people 65 or older. Some people qualify earlier because of a disability, ALS, or end-stage renal disease. Eleanor qualifies based on age. [17]

Mabel draws three paths:

  • Original Medicare includes Part A and Part B. It is the federal fee-for-service pathway, administered by CMS through Medicare Administrative Contractors.

  • Medicare Advantage, or Part C, is another way to receive Part A and Part B benefits through a Medicare-approved private plan. These plans must cover the medically necessary services Original Medicare covers and must follow applicable Medicare coverage requirements. They may use publicly accessible internal criteria when Medicare’s criteria are not fully established. [2][3]

  • Medicaid is a joint federal-state program. States administer their own programs within federal requirements, so the controlling coverage and payment documents vary by state and delivery system. [4]

“Wait,” Eleanor says. “What are Part A and Part B?”

Mabel adds two cards to the table:

  • Part A is Hospital Insurance: It mainly helps cover inpatient hospital care, skilled nursing facility care, hospice care, and some home health care.

  • Part B is Medical Insurance: It helps cover services from doctors and other clinicians, outpatient care, durable medical equipment, many preventive services, and medically necessary clinical diagnostic laboratory tests.

The letters describe different Medicare benefits, not different insurance companies. Part A can include hospital laboratory services when Eleanor is formally admitted as an inpatient. But this genetic panel is being ordered during an outpatient doctor visit, so the relevant benefit path is generally Part B. That identifies the benefit branch; it does not answer whether this particular test and use meet Medicare’s coverage requirements. [4][5]

For orientation, Part C is Medicare Advantage, the private-plan alternative for receiving Part A and Part B benefits, and Part D is prescription-drug coverage. We will not go deeper into Part D because Eleanor’s laboratory test is not a pharmacy-benefit question.

Eleanor has Original Medicare, Parts A and B. Because Dr. Singh is ordering an outpatient laboratory test, the group follows the Part B path. That is why the rest of this issue focuses on the NCDs, LCDs, MAC jurisdiction, and billing guidance relevant to Original Medicare.

The reimbursement puzzle.

Otis, the claims expert, takes over and turns the nine pieces face up.

“People treat these as different words for the same thing,” he says. “They are not.”

  • Coverage: Under what circumstances may Medicare cover the service?

  • Coding: How should the service be identified on the claim?

  • Documentation: What must the medical record demonstrate?

  • Payment: Which methodology determines the amount Medicare may pay if the service is payable?

  • Claim adjudication: Does Eleanor’s specific claim satisfy the applicable requirements?

A test may be covered in defined circumstances and still not be payable for Eleanor. Her facts, documentation, code, jurisdiction, and date must match the applicable requirements.

One piece sits underneath all five. Congress created Medicare’s legal authority. An item or service must fit within a Medicare benefit category, must not be excluded by law, and generally must be reasonable and necessary for diagnosing or treating illness or injury—or improving the functioning of a malformed body member. [6]

FDA authorization answers a different legal question. It does not automatically create Medicare coverage or payment.

The national layer: NCDs

Mabel, our CMS guide, picks up the national-policy piece: a National Coverage Determination, or NCD.

CMS begins a formal National Coverage Analysis, reviews the evidence, and may use an external Technology Assessment or seek advice from MEDCAC (Medicare Evidence Development & Coverage Advisory Committee), its evidence advisory committee. CMS then posts a proposed decision for public comment and later posts a final decision memorandum explaining its conclusion.

For the standard statutory timeline, CMS generally posts the proposed decision within six months after opening the NCA. When the analysis includes an external Technology Assessment or a MEDCAC meeting, that period is generally nine months. The proposed decision receives a 30-day public-comment period, and CMS issues the final decision no later than 60 days after comments close. The overall process generally takes nine to twelve months. [7]

“An NCD answers a national Medicare coverage question,” Mabel says. “MACs must follow it. But it does not, by itself, assign a billing code or determine the payment amount.”

The final decision memorandum makes the NCD effective; manual changes and claims-system instructions may follow to implement it operationally.

A test may not have a test-specific NCD and still fall under a broader national policy. That matters in genetic testing: CMS’s NCD 90.2 governs certain next-generation sequencing tests for cancer. Never stop the search just because the product name does not appear in an NCD title.

What is a MAC, and what is an LCD?

Mabel introduces the next piece.

“A Medicare Administrative Contractor, or MAC, is a private company contracted by CMS to administer specified Original Medicare responsibilities within an assigned jurisdiction.”

A basset hound in a tan blazer welcomes the group to a regional MAC office. He is the local-policy guide for this issue; readers do not need to remember him from anywhere else. CMS currently lists 12 A/B MACs and four DME MACs. A/B MACs process Part A and Part B fee-for-service claims within defined jurisdictions; DME MACs handle durable medical equipment claims. [8]

The distinction matters: a MAC is not CMS, a Medicare Advantage plan, or a state Medicaid agency. It works under a CMS contract. A MAC may develop local coverage policy, but it cannot contradict an applicable NCD.

One more distinction comes up constantly in molecular diagnostics: MolDX is not a MAC. It is a molecular diagnostic services program administered by Palmetto GBA and adopted by participating MACs. Palmetto administers the program in Jurisdictions M and J; other participating jurisdictions are administered by their respective MACs. [9]

For this example, Eleanor’s test is billed by a laboratory located in South Carolina. South Carolina is part of Palmetto GBA’s Jurisdiction M for Medicare Part A and Part B claims, together with North Carolina, Virginia, and West Virginia. That is why Jurisdiction M, not a different MAC jurisdiction, is the relevant local layer in Eleanor’s coverage puzzle. The applicable MAC can depend on the service, claim type, and billing provider or laboratory location, so teams should verify the correct jurisdiction for each case.

The MAC representative picks up the local-policy piece: a Local Coverage Determination, or LCD.

“An LCD is a MAC’s determination, within its jurisdiction, about whether a particular item or service is reasonable and necessary under Medicare’s applicable standard.” [10]

An LCD applies only within the contracts and jurisdiction identified in the document. Another MAC may have a different local policy when no controlling national rule resolves the question.

For new or revised LCDs that require the full comment-and-notice process, the MAC generally provides at least a 45-day public-comment period and at least a 45-day notice period before the final LCD becomes effective. Administrative revisions do not necessarily repeat that full process. [11]

An LCD is often linked to a separate Billing and Coding Article. For most A/B MAC policies, codes and claim-submission guidance are maintained in the related article rather than the LCD itself. The article supports the policy; it is not the LCD.

If there is no applicable NCD or LCD, that is not an automatic yes or no. The MAC may adjudicate the claim under other applicable Medicare authorities, instructions, evidence, and patient-specific facts. Silence is not a coverage determination.

The document map and the date problem

Otis sorts the paperwork into five piles:

  • Coverage: NCDs and LCDs.

  • Process and explanation: NCA tracking sheets, decision memoranda, and responses to comments.

  • Evidence: Technology Assessments and advisory materials.

  • Billing and implementation: Billing and Coding Articles, Change Requests, Transmittals, and Medicare manual instructions.

  • Payment: The applicable fee schedule or payment system.

“A Billing and Coding Article is not an LCD,” Otis says. “And a fee-schedule amount does not establish coverage.”

The dates also matter. A document may have a publication date, effective date, implementation date, and retirement date. Those dates may differ. The policy version governing Eleanor’s claim is the version applicable to her date of service, not automatically the version visible today.

Using the wrong version can produce the wrong coverage analysis or weaken a denial review or appeal.

What the team needs to finish the puzzle

To answer Eleanor’s question, the group needs:

  • Program and plan type

  • Date of service

  • Provider and laboratory locations

  • Claim type

  • Applicable MAC and jurisdiction

  • Test or service name

  • CPT or HCPCS code

  • Diagnosis and ICD-10-CM code

  • Applicable NCD

  • Applicable LCD

  • Linked Billing and Coding Article

  • Covered indications and limitations

  • Documentation and ordering requirements

  • Applicable policy version

  • Payment methodology

  • Eleanor’s clinical facts

No single character owns all of that information. Eleanor brings her coverage and clinical history. Dr. Singh brings the order and medical record. Mabel explains the national framework. The MAC representative identifies the local rules. Otis connects the operational pieces.

That is the real shape of “Will Medicare cover this?” once we stop treating it as one question.

Where the pieces commonly get mixed up

  • CMS is not an insurance plan, and a MAC is not CMS.

  • Original Medicare, Medicare Advantage, and Medicaid do not use one identical coverage pathway.

  • No published NCD or LCD does not mean automatic coverage—or automatic denial.

  • An LCD is local, not national.

  • A Billing and Coding Article supports an LCD but is not the LCD itself.

  • A billing code does not create coverage, and a fee-schedule amount does not guarantee payment.

  • The wrong jurisdiction can lead to the wrong policy.

  • The current policy may not be the version that applied on the date of service.

  • General coverage does not replace patient-specific documentation.

  • FDA authorization does not automatically create Medicare coverage.

None of these mistakes requires bad intent. They happen when a nine-part question gets treated like a one-part question.

How to stay ahead

  1. Identify the program and plan. If it is Medicaid, identify the state and delivery system.

  2. For Original Medicare, identify the correct MAC, contract, and jurisdiction.

  3. Search the Medicare Coverage Database by service name and code.

  4. Check for a controlling NCD, including broader NCDs that may apply.

  5. Check for an applicable LCD.

  6. Read any linked Billing and Coding Article.

  7. Review documentation, ordering, and utilization requirements.

  8. Match the policy version to the actual date of service.

  9. Research the payment methodology separately.

  10. Monitor proposed policies, final policies, and implementation instructions.

  11. Preserve retired versions for older claims and appeals.

The Medicare Coverage Database is the primary search tool for NCDs, LCDs, and related documents. MAC websites provide contractor-specific education, meetings, and notices. CMS publishes Change Requests and Transmittals separately, while MLN Matters explains many changes for providers. The weekly MLN Connects newsletter summarizes national fee-for-service news, billing and coding updates, and educational resources.

Complete the puzzle

Every character now adds the piece only they can supply:

  • Eleanor: enrollment, date of service, location, and individual clinical facts

  • Dr. Singh: the order, diagnosis, clinical rationale, and medical record

  • Mabel: the CMS framework and national coverage layer

  • MAC representative: jurisdiction and local coverage layer

  • Otis: coding, claim instructions, policy version, and payment methodology

So, is Eleanor’s test covered?

No, not based on the facts in this example.

Eleanor is unaffected: she has never received a cancer diagnosis. She is seeking hereditary-cancer testing because her mother had breast cancer. The applicable MolDX policy requires all three patient conditions: a cancer diagnosis, a clinical indication for germline testing, and a hereditary-cancer risk factor. Eleanor may have a risk factor, but she does not have the required cancer diagnosis. The puzzle is incomplete. [12]

That answer is the point of the puzzle. Dr. Singh may have a clinically reasonable reason to recommend the test. The test may have a billing code and a published price. The documentation may be complete. But none of those pieces can create coverage when Eleanor does not meet the governing policy’s conditions.

Final answer for Eleanor: Based on the facts provided, Eleanor does not meet the coverage criteria in the cited MolDX LCD because she has no cancer diagnosis. Before reaching a final case-level conclusion, the laboratory should confirm that this is the controlling policy for the test, date of service, claim type, and billing jurisdiction.

Coverage defines whether and when the door can open. Coding and documentation help a payable claim pass through it. Payment rules set the amount. Eleanor’s individual facts determine whether the coverage conditions are met.

Turn the puzzle into action

Knowing how coverage works is useful. Building the answer into the workflow before the service is performed is where the value appears.

For RCM teams: build a pre-service coverage check

Choose one high-denial service and create a one-page coverage matrix before the next claim goes out. Include:

  • Program and plan type

  • Date of service

  • Performing provider and laboratory location

  • Correct MAC, contract, and jurisdiction

  • Controlling NCD, applicable LCD, and linked Billing and Coding Article

  • Covered indication and limitations

  • Required diagnosis, CPT or HCPCS codes, and claim details

  • Documentation, ordering, and utilization requirements

  • Policy version and effective date

  • Separate payment methodology

Then compare that matrix with the order, medical record, and claim. If one element is missing, route the case for clarification before testing or billing. Do not use the checklist only after a denial.

When a denial does occur, classify the failure before appealing it: coverage, coding, documentation, jurisdiction, policy version, payment, or claim processing. The appeal should address the actual failure instead of sending the same records again and hoping for a different result.

IIf you want help managing some of these moving pieces in one place, check out converus.ai. Converus AI brings payer policies, billing guidance, effective dates, and case-specific requirements into one traceable workflow, helping reimbursement teams evaluate cases before submission.

For market access teams: map the pathway before launch

Do not stop at FDA authorization or the existence of a code. Build a payer pathway for the technology:

  1. Identify the Medicare benefit category and any statutory exclusion.

  2. Search for national policies that may control the technology, including broader NCDs.

  3. Map the relevant MAC jurisdictions, LCDs, and Billing and Coding Articles.

  4. Compare the published evidence requirements with the evidence the product currently has.

  5. Separate coverage gaps from coding, documentation, and payment gaps.

  6. Monitor proposed NCDs and LCDs, public meetings, comment periods, final policies, Change Requests, and effective dates.

The useful output is not a list of links. It is a gap map: what is already supported, what remains uncertain, which decision-maker controls each issue, and what evidence or operational change could close the gap.

For patients: ask for the answer in writing

Before the test or service, ask:

  • Which part of Medicare or which health plan will be billed?

  • What is the exact test or service and billing code?

  • Is there an NCD, LCD, or plan policy that applies to me?

  • Do my diagnosis and medical history meet the policy’s covered indication?

  • Is prior authorization or additional documentation required?

  • If Medicare does not pay, what could I owe?

For Original Medicare, if the provider believes Medicare may not cover the service, ask whether you should receive an Advance Beneficiary Notice of Noncoverage, or ABN, before the service. An ABN is a notice, not a coverage decision or a promise that Medicare will deny, but it should explain why payment may be denied and the estimated cost so you can make an informed choice. [16]

Keep the order, policy information, ABN if one is issued, claim, Medicare Summary Notice, and denial letter together. Those documents are much more useful in an appeal than trying to reconstruct the case months later.

The deeper operational lesson is that the service name and billing code are never enough on their own. The same test can produce a different coverage answer when the program, jurisdiction, controlling policy, policy version, or patient facts change. The useful work product is therefore not a generic checklist: it is a dated, case-specific decision record showing which rule controlled, which facts were tested against it, where uncertainty remains, and who owns the next decision.

That's it for this issue. Hit reply. I read everything.

Sources

  1. Electronic Code of Federal Regulations: 42 CFR § 422.101, Medicare Advantage basic-benefit requirements
    https://www.ecfr.gov/current/title-42/chapter-IV/subchapter-B/part-422/subpart-C/section-422.101

  2. Palmetto GBA — MolDX Frequently Asked Questions
    https://palmettogba.com/palmetto/moldxv2.nsf/DID/9A7MFG4181

  3. CMS Medicare Coverage Database — MolDX: Lab-Developed Tests for Inherited Cancer Syndromes in Patients with Cancer (L38972)
    https://www.cms.gov/medicare-coverage-database/view/lcd.aspx?lcdid=38972

Disclaimer: The content published by preimbursed (the "Newsletter") is provided for general informational and educational purposes only and reflects the opinions and commentary of the author. It does not constitute, and should not be relied upon as, medical, legal, financial, tax, insurance, or other professional advice. No physician-patient, attorney-client, fiduciary, or other professional relationship is created by reading the Newsletter or by corresponding with the author. The Newsletter is not a substitute for individualized advice from a qualified professional. Before making any healthcare, coverage, insurance, financial, or legal decision, you should consult your own physician, attorney, benefits administrator, or other licensed advisor and review your specific plan documents, policies, and applicable law. The author is not responsible for any action taken or not taken in reliance on the content herein, and you assume full responsibility for your use of the information provided. Information in the Newsletter is believed to be accurate as of the date of publication and is drawn from the sources cited. Laws, regulations, coverage rules, corporate ownership, market data, and other facts change frequently and may have changed since publication. Certain statements describe pending, recently enacted, or phased-in legal and regulatory changes whose scope, interpretation, and effective dates may shift. The author makes no representation or warranty, express or implied, regarding the accuracy, completeness, timeliness, or reliability of any content, and disclaims all liability for any errors or omissions to the fullest extent permitted by law. References to any company, organization, product, government program, or individual are made solely for purposes of news reporting, commentary, analysis, and criticism, and do not imply any endorsement, sponsorship, affiliation, or partnership. All trademarks, service marks, and trade names are the property of their respective owners and are used only for identification and descriptive purposes. Where a named party disputes a characterization or finding, the Newsletter notes that dispute. Statements concerning identified companies reflect cited reporting and the author's opinion and analysis of matters of public concern. Certain characters, organizations, and scenarios in the Newsletter, including but not limited to Biscuit, Dr. Singh, and composite payer and provider names, are fictional and used for illustration. Any resemblance to actual persons or entities is coincidental.

Disclosure: The authors are the co-founders of Converus.ai, a company that organizes payer policy information for healthcare providers, and therefore has a commercial interest in the subject matter discussed. References to Converus.ai are made only where relevant and are not paid placements. To the fullest extent permitted by applicable law, the author and preimbursed disclaim all warranties and shall not be liable for any direct, indirect, incidental, consequential, or other damages arising out of or in connection with your use of, or reliance on, the Newsletter.

Keep Reading