Do not stop at the first search result. A Medicare coverage answer is only reliable when the correct document, jurisdiction, effective version and related coding article have been confirmed.
GOHEALTHCARE RCM AUTHORITY CENTER • Medical Billing, Coding & Reimbursement Intelligence
Medicare NCD, LCD & MAC Coverage Intelligence
A practical guide to Medicare coverage research using NCDs, LCDs, MAC jurisdiction and related billing and coding articles in the Medicare Coverage Database.
Developed by GoHealthcare Practice Solutions
Expert Review: Pinky Maniri, MSc
CRCR, CSAPM, CSPPM, CSBI, CSPR, CSAF
Certified in Healthcare A.I. Governance
CEO & Founder
DIRECT ANSWER
Medicare coverage analysis requires the correct hierarchy. National Coverage Determinations apply nationally to the services they address; Local Coverage Determinations are issued by Medicare Administrative Contractors within their jurisdictions when applicable. Coverage research must also account for related
CORE CONTROL
Verify national versus local coverage, document the source, and reconcile changes before the claim leaves the organization.
RCM PRINCIPLE
A denial is often the visible end of an earlier workflow defect. Find the first defect, not only the final payer response.
How to use this resource. Use this page when determining which Medicare coverage authority applies to a service and date of care. National policy, local policy, billing and coding articles, jurisdiction and effective dates must be read together. Payer, plan, jurisdiction, coding and legal requirements should be reverified for the specific case and date of service.
01
DIRECT ANSWER
Medicare NCD, LCD & MAC Coverage Intelligence
Medicare coverage analysis requires the correct hierarchy. National Coverage Determinations apply nationally to the services they address; Local Coverage Determinations are issued by Medicare Administrative Contractors within their jurisdictions when applicable. Coverage research must also account for related billing and coding articles, benefit category, documentation and the service date.
Policy intelligence is a version-control discipline. The correct answer depends on who issued the rule, what population and service it addresses, where it applies and when it became effective.
PRACTICAL RCM POINT
02
WHY THIS MATTERS
Why Medicare Coverage Research Requires a Hierarchy
Medicare coverage is not a single national list of payable procedures and diagnoses. NCDs address national coverage questions; MACs may issue LCDs within their jurisdictions when applicable; and related articles often contain coding and billing details that are no longer carried in the LCD itself. The effective date and jurisdiction matter.
The practical task is to identify which rule answers which question before deciding how the case should move forward.
WATCH-OUT
Do not fill gaps in Medicare NCD, LCD & MAC Coverage Intelligence with assumptions. If the answer changes by payer, product, jurisdiction, date of service, network status or code-set version, verify the current source and document why it applies to the case.
03
DECISION ARCHITECTURE
What Has to Be Distinguished
Determine whether an NCD addresses the service. If not, identify the correct MAC and search for an applicable LCD and related articles. Confirm that the document is in effect for the date of service and read the coverage language separately from coding instructions and payment rules.
| Decision Field | What to Verify | Evidence to Keep |
|---|---|---|
| Authority Type | Confirm the current authority type for the patient, payer, setting and date of service when it can change the answer. | the named policy, source URL, effective date, applicability fields and documented decision |
| Payer And Product | Confirm the current payer and product for the patient, payer, setting and date of service when it can change the answer. | the named policy, source URL, effective date, applicability fields and documented decision |
| Jurisdiction | Confirm the current jurisdiction for the patient, payer, setting and date of service when it can change the answer. | the named policy, source URL, effective date, applicability fields and documented decision |
| Effective Date | Confirm the current effective date for the patient, payer, setting and date of service when it can change the answer. | the named policy, source URL, effective date, applicability fields and documented decision |
| Clinical Criteria And Documentation | Confirm the current clinical criteria and documentation for the patient, payer, setting and date of service when it can change the answer. | the named policy, source URL, effective date, applicability fields and documented decision |
04
DEEP-DIVE ANALYSIS
The Issues That Change the Answer
Medicare coverage research can fail even when staff find a legitimate CMS document. The question is whether it is the right document type, correct MAC jurisdiction, current version and applicable date of service—and whether a related Billing and Coding Article contains the coding detail the LCD no longer carries.
National Versus Local Coverage
national versus local coverage should be verified from the source that actually governs the case. Record the answer before it is handed to the next revenue-cycle step.
The practical control is to make the question visible. A reviewer should be able to see what was verified, when it was verified, what source was used, what exception exists and who owns the next action. That is especially important for Medicare NCD, LCD & MAC Coverage Intelligence, because a technically valid claim can still be nonpayable when the underlying benefit, coverage, documentation, coding or reimbursement condition is not met. Conversely, a payer denial does not automatically prove the service was coded incorrectly; the denial reason must be classified before the workflow is changed.
Mac Jurisdiction
If mac jurisdiction changes after scheduling, the financial assumptions may change with it. Reconcile the final fact before the claim is released.
Billing And Coding Articles
Do not leave billing and coding articles as an unresolved note for A/R to discover later. Confirm the rule, document the answer and route any exception before it becomes a denial.
Reasonable And Necessary Standard
The effect of reasonable and necessary standard is case-specific. Preserve the source and date used so the decision can be reproduced during payer review, appeal or audit.
Coverage Database Research
coverage database research should be verified from the source that actually governs the case. Record the answer before it is handed to the next revenue-cycle step.
Effective And Retirement Dates
If effective and retirement dates changes after scheduling, the financial assumptions may change with it. Reconcile the final fact before the claim is released.
Medicare Advantage Considerations
Do not leave medicare advantage considerations as an unresolved note for A/R to discover later. Confirm the rule, document the answer and route any exception before it becomes a denial.
Documentation And Diagnosis Limitations
The effect of documentation and diagnosis limitations is case-specific. Preserve the source and date used so the decision can be reproduced during payer review, appeal or audit.
05
CLINICAL & DOCUMENTATION
Documentation Has to Support the Financial Story
Coverage policy should be compared with the actual clinical record, not used as a script for creating documentation. The note must independently support the patient's condition and service; the policy tells the reviewer which facts matter for Medicare coverage.
When documentation is incomplete, the appropriate response is a compliant clarification or query process, not an unsupported assumption. The record should be clinically useful first and sufficiently specific for coding and payer review second. Copy-forward language, cloned templates and payer-keyword documentation can create contradictions that are more damaging than a shorter but accurate note.
BEST PRACTICE
For Medicare NCD, LCD & MAC Coverage Intelligence, reconcile the final signed record with what was scheduled, authorized and expected financially before a high-risk claim is released. If the service changed, recheck authorization, coding, modifiers, units, site of service and patient-financial implications.
06
CODING & CLAIM INTEGRITY
Coding Must Follow What Was Actually Done
Do not expect the NCD or LCD alone to answer every coding question. CMS notes that NCDs do not contain claims-processing codes, and for most local coverage the coding detail is in related articles, manuals or transmittals. Use the appropriate source for each question.
For every high-risk claim, the coding review should consider the final note, current CPT/HCPCS conventions, ICD-10-CM linkage, modifiers, units, add-on relationships, global-period rules, professional or technical components, place of service and NCCI/MUE edits where applicable. Commercial payers may apply additional claim edits or proprietary payment policies, so Medicare logic should not automatically be assumed to control every commercial claim.
CODING GUARDRAIL
When Medicare NCD, LCD & MAC Coverage Intelligence exposes noncoverage, bundling, edit logic or an authorization defect, do not try to code around it. Identify the condition accurately and use the appropriate coverage, coding, financial or appeal pathway.
07
PAYER & COVERAGE
Coverage, Authorization and Payment Are Separate Questions
Start with national coverage, then determine whether local coverage applies through the patient's MAC jurisdiction. Read the effective version and related articles. A proposed LCD, retired policy or document from another jurisdiction should not be treated as current authority for the claim.
Authorization and coverage are related but separate. An authorization may confirm that a payer or UM entity approved a requested service under specified conditions; it does not guarantee that every downstream claim requirement will be satisfied. Eligibility can change, the performed service can differ from the request, documentation may be incomplete, the authorization can expire, or another payment rule may apply.
08
REIMBURSEMENT
Payment Has to Be Reconciled
Coverage and payment rate are separate. An item or service can meet a coverage policy and still be subject to fee-schedule, bundling, setting or other payment rules. Do not interpret an LCD as a reimbursement guarantee.
The revenue-cycle team should compare the expected result with the remittance. A claim that paid is not necessarily a correctly paid claim. Incorrect multiple-procedure reductions, modifier handling, unit calculations, contract loads, patient cost sharing, packaging or other pricing rules can create silent underpayments that never appear in a denial report.
PAYMENT INTEGRITY
Expected-payment analysis for Medicare NCD, LCD & MAC Coverage Intelligence is a reconciliation control. Base it on the final claim and the contract, fee schedule, plan methodology, statute or other payment rule that actually applies; not every difference between charge and payment is recoverable.
09
ROOT-CAUSE CONTROL
Common Failure Modes and Corrective Action
| Failure Mode | What It Looks Like | Corrective Principle |
|---|---|---|
| Wrong authority used | Staff rely on an old policy, wrong product, wrong jurisdiction or a rule that answers a different question. | Identify the controlling authority and effective date before changing the case. |
| Authorization and final service do not match | The approved service, setting, level, units or dates differ from what was furnished. | Reconcile the authorization against the final record before claim creation. |
| Documentation is incomplete | The claim contains specificity that cannot be supported from the signed record. | Use a compliant clarification process before coding or billing. |
| Coding edit is treated as a coverage denial | The team appeals medical necessity when the actual problem is a code pair, unit or modifier issue. | Classify the payer response before choosing correction or appeal. |
| Paid claim is closed without reconciliation | A payer underpayment or incorrect contractual adjustment is never detected. | Compare actual payment with expected allowable and investigate material variance. |
| Patient balance is assigned too early | A payer or contract issue is transferred to the patient before adjudication is correct. | Resolve payer responsibility first, then determine lawful patient responsibility. |
| A/R has no owner | The balance ages because the next action, deadline or responsible party is not visible. | Every material balance needs a reason, owner, next action and target date. |
| Policy change is not operationalized | Teams continue using the prior rule after an effective-date change. | Use change control, education and post-change QA to confirm adoption. |
10
SOLUTION FRAMEWORK
A Practical Revenue-Cycle Framework
Document the source used for the decision, including the policy identifier, contractor or national authority, effective version and relevant article. When the policy changes, update the operational reference rather than relying on an old printout or prior authorization outcome.
| Stage | What Good Looks Like |
|---|---|
| Define | Identify the exact question: benefit, coverage, authorization, coding, reimbursement, network, injury or patient-balance. |
| Verify | Use the current authoritative source and case-specific facts. |
| Reconcile | Compare scheduled, authorized, documented, coded and billed information. |
| Submit | Create the claim or required request using accurate, supportable data. |
| Classify | When an adverse response occurs, assign the correct root cause before taking action. |
| Resolve | Correct, appeal, negotiate or escalate through the appropriate pathway. |
| Reconcile Payment | Compare the adjudicated result with the expected financial outcome. |
| Learn | Feed the defect back to the upstream process so the same problem does not recur. |
11
DENIALS & APPEALS
Resolve the Actual Reason for the Adverse Result
When Medicare denies a service, identify whether the issue is coverage, coding, documentation, claim processing or another requirement. An appeal should cite the authority that actually governs the adverse decision rather than attaching unrelated policy language.
Appeal only when the record and governing authority support reconsideration. A corrected claim, benefit inquiry, network dispute or payment-variance review may be the correct remedy instead.
WATCH-OUT
When Medicare NCD, LCD & MAC Coverage Intelligence intersects with a coding edit, separate that issue from medical necessity. Do not change a modifier or diagnosis merely to produce payment; the correction or appeal should address the actual defect.
12
A/R & PAYMENT INTEGRITY
Every Material Balance Needs a Reason and Next Action
Medicare A/R involving coverage should retain the policy identifier, applicable version, MAC, date reviewed, denial reason and appeal status. That record allows the organization to distinguish a true coverage dispute from a coding or processing issue.
For this subject, A/R analytics should also show the defect that created the balance. If repeated accounts trace back to the same authorization mismatch, documentation gap, policy misunderstanding, network issue or payment variance, the organization has a process problem—not simply an A/R productivity problem.
13
COMPLIANCE & AUDIT READINESS
Financial Performance Must Be Defensible
Using an outdated or inapplicable policy can create both payment and compliance risk. Version control is therefore part of revenue-cycle governance, not clerical housekeeping.
The safest reimbursement strategy is to capture every dollar legitimately earned for medically necessary, properly documented and correctly billed care while preventing leakage, avoidable denials and payer underpayments. It is not to maximize codes, manipulate diagnoses or bypass legitimate payer edits.
COMPLIANCE PRINCIPLE
In Medicare NCD, LCD & MAC Coverage Intelligence, stop when the financial decision depends on a clinical fact that is not documented. Revenue-cycle staff should request compliant clarification rather than create the fact. When the controlling rule is legally or jurisdictionally complex, involve qualified legal or compliance counsel.
14
LEADERSHIP & KPIs
Metrics That Actually Help
Leadership should see the few measures that reveal whether this specific workflow is reliable, where dollars are at risk and whether the same defect is recurring.
| Metric | What It Tells You |
|---|---|
| Coverage-source verification rate | Measures whether high-risk Medicare services have a documented current authority before billing. |
| Wrong-jurisdiction policy use | Identifies cases where staff relied on another MAC’s LCD or article. |
| Outdated-policy exception rate | Shows how often a retired or superseded document was used. |
| Coverage-related denial rate | Tracks denials tied to reasonable-and-necessary or policy criteria. |
| Article / LCD mismatch findings | Shows whether coding articles and coverage policy are being reviewed together. |
| Time to update policy references after change | Measures version-control responsiveness. |
15
CASE APPLICATION
A Realistic Operating Scenario
Scenario
A practice is preparing a Medicare claim for an MSK service that staff remember seeing in an LCD. The review first checks whether an NCD governs the service, then confirms the patient’s MAC jurisdiction. The current LCD is located in the Medicare Coverage Database, and the related billing and coding article is reviewed for code and diagnosis information. The team documents the version in effect for the date of service and avoids using an LCD from another jurisdiction as if it were binding.
The critical step was confirming the current MAC jurisdiction and the related article instead of relying on a remembered LCD from a prior case.
16
COMMON QUESTIONS
Frequently Asked Questions
What is the difference between an NCD and an LCD?
An NCD is a national Medicare coverage determination. An LCD is issued by a Medicare Administrative Contractor and applies within that contractor's jurisdiction when applicable. The correct source depends on the service, jurisdiction, and date of care.
Where are Medicare diagnosis and procedure codes usually found for an LCD?
For most local coverage, CMS places coding information in related Billing and Coding Articles rather than in the LCD itself. The Medicare Coverage Database should be used to locate both the policy and related article.
Do NCDs contain all of the codes needed to bill a service?
No. CMS states that NCDs do not contain claims-processing instructions such as diagnosis or procedure codes. Related CMS manuals, transmittals, and other claims-processing guidance may be needed.
Why does MAC jurisdiction matter?
A local coverage rule applies within the jurisdiction of the MAC that issued it. Using an LCD from the wrong jurisdiction can produce an incorrect coverage conclusion.
Can an old LCD or article be used if the wording looks the same?
Do not assume so. Check the effective and revision dates and use the version applicable to the date of service. Retired and superseded documents can be useful historically but should not be treated as current authority.
Does an LCD guarantee payment when its criteria are met?
No. Coverage is only one layer. Eligibility, benefit category, documentation, coding, claim processing, and other Medicare requirements still apply.
How should a Medicare coverage decision be documented operationally?
Record the national or local source, document identifier, contractor when applicable, effective version, date reviewed, and the patient or service facts that make it applicable.
What should be checked when a Medicare policy changes?
Identify the effective date, determine which scheduled or open claims are affected, update operational references, educate the relevant teams, and verify that the new rule is being applied correctly.
17
RELATED RESOURCES
Continue the RCM Research Path
Revenue Cycle ManagementRevenue Cycle Management OverviewRevenue Cycle Management ProcessRevenue Integrity for MSK Specialty CarePrior Authorization ProcessProcedure LibraryCase StudiesContact GoHealthcareMedical Billing Strategy for Specialty HealthcareMedical Coding Strategy for MSK & Injury CareICD-10-CM Diagnosis Coding & Medical Necessity
18
AUTHORITATIVE REFERENCES
Authoritative References
- CMS — Medicare Coverage Determination Process
https://www.cms.gov/medicare/coverage/determination-process - CMS — Medicare Coverage Database
https://www.cms.gov/medicare-coverage-database/search.aspx - HHS OIG — Compliance Guidance
https://www.oig.hhs.gov/compliance/compliance-guidance/
| Authority | Reference |
|---|---|
| CMS | Medicare Coverage Database https://www.cms.gov/medicare-coverage-database/search.aspx |
| CMS | Medicare Coverage Center https://www.cms.gov/medicare/coverage |
| HHS OIG | General Compliance Program Guidance https://oig.hhs.gov/compliance/general-compliance-program-guidance/ |
| GoHealthcare | Revenue Cycle Management https://www.gohealthcarellc.com/revenue-cycle-management.html |
Sources reviewed August 20, 2026. Coverage, coding, payment and regulatory requirements change; verify the payer, product, jurisdiction, code-set version and effective date before applying any rule to a specific case.
Continue With the Next RCM Question
GOHEALTHCARE RCM AUTHORITY CENTER
Explore All 150 RCM Authority Pages
Move across the complete GoHealthcare MSK and Injury Revenue Cycle Management knowledge system: specialty RCM, medical billing and coding, coverage and reimbursement intelligence, injury cases, workers’ compensation, in-network and out-of-network RCM, and ancillary MSK services.
Revenue Cycle Management — Main Flagship PageAmbulatory Surgery Centers
Hand & Upper Extremity
Interventional Pain Management
MSK Radiology & Diagnostic Imaging
Neuromodulation
Neurosurgery
Occupational Medicine / Workers’ Compensation MSK
Orthobiologics & Regenerative MSK Medicine
Orthopedic Surgery
Physical Medicine & Rehabilitation (PM&R)
Spine & Interventional Spine
Sports Medicine
Medical Billing, Coding & Reimbursement Intelligence
- Medical Billing Strategy for Specialty Healthcare
- Medical Coding Strategy for MSK & Injury Care
- ICD-10-CM Diagnosis Coding & Medical Necessity
- Diagnosis-to-Procedure Alignment in Specialty RCM
- CPT Coding Strategy for MSK & Injury Services
- HCPCS Coding for Drugs, Devices, DME & Supplies
- Modifier Strategy & Compliance
- NCCI Edits in MSK & Injury Revenue Cycle Management
- Medically Unlikely Edits & Unit-Based Billing Controls
- Global Surgery & Postoperative Billing
- Place-of-Service Coding & Reimbursement
- Professional vs Facility Billing
- Site-of-Service Reimbursement Strategy
- Drug, Biologic, Injectable & J-Code Billing
- Implant, Device & Supply Reimbursement
- Unlisted Codes & Emerging Procedure Billing
- Clinical Guidelines vs Coverage Policies
- Medicare NCD, LCD & MAC Coverage Intelligence
- Commercial Payer Medical Policy & Utilization Management Intelligence
- Payer Contracts, Fee Schedules, Expected Allowables & Payment Integrity
Injury Case RCM
- Injury Cases Revenue Cycle Management Hub
- Workers’ Compensation RCM Services
- Auto Accident RCM Services
- Auto Accident Medical Billing Services
- PIP & No-Fault Medical Billing
- MedPay Medical Billing & Reimbursement
- Personal Injury Medical Billing
- Medical Lien RCM Services
- Letter of Protection / LOP Medical Billing
- Attorney, Lien & Medical Receivable Management
- Injury Case Documentation, Diagnosis & Causation
- Injury Case A/R, Settlement Timing & Receivable Risk
- Medicare Secondary Payer, Coordination of Benefits & Third-Party Liability
- Injury Case Compliance, Patient Financial Responsibility & Medical Records
In-Network & Out-of-Network RCM
- Network Status & Reimbursement Strategy Hub
- In-Network Revenue Cycle Management Strategy
- Out-of-Network RCM Services
- In-Network vs Out-of-Network Revenue Cycle Management
- Out-of-Network Medical Billing Services
- Out-of-Network Benefits Verification & Financial Clearance
- Out-of-Network Prior Authorization & Medical Necessity
- Out-of-Network Allowed Amounts & Reimbursement Methodologies
- Out-of-Network Denial Management & Appeals
- Out-of-Network A/R & Underpayment Recovery
- No Surprises Act & Out-of-Network RCM
- Good Faith Estimates & Patient Financial Disclosure
- Single Case Agreements & Network Exceptions
- Self-Funded / ERISA Out-of-Network Claims
- Out-of-Network Facility & Professional Billing, Compliance & Payment Resolution
ABOUT THE EXPERT REVIEWER
Pinky Maniri, MSc
CRCR, CSAPM, CSPPM, CSBI, CSPR, CSAF
Certified in Healthcare A.I. Governance
CEO & Founder, GoHealthcare Practice Solutions
Pinky Maniri is a healthcare operations and financial management executive with approximately 30 years of experience in revenue cycle management, prior authorization, payment and reimbursement, physician and ambulatory practice operations, healthcare finance, business intelligence, and MSK specialty healthcare operations.
HFMA Certified Professional in:
- Physician Practice Management
- Ambulatory Practice Management
- Revenue Cycle Management
- Payment & Reimbursement
- Accounting & Finance
- Business Intelligence
- Healthcare A.I. Governance
Editorial Review Scope
This resource was developed by GoHealthcare Practice Solutions and reviewed for healthcare operations, revenue cycle, reimbursement, and operational accuracy. Coverage, coding, medical necessity, utilization management, payer policy, and reimbursement requirements may vary by payer, plan, jurisdiction, setting, and date of service. Current authoritative sources should be reviewed before applying information to a specific patient, claim, or reimbursement determination.
Disclaimer
This educational resource is provided for general informational and operational planning purposes. It is not legal advice, medical advice, coding advice for a specific claim, payer authorization, or a guarantee of coverage or reimbursement. Coding, coverage, benefit design, contracts, fee schedules, federal and state requirements, utilization-management criteria and payer policies change frequently and may vary by patient, plan, jurisdiction, provider type and site of service. Use current official sources, licensed coding materials and qualified professional counsel as appropriate before making case-specific decisions.
KNOWLEDGE CENTER
Search GoHealthcare Practice Solutions
Search the GoHealthcare website for another MSK, injury, prior-authorization, coding, payer or revenue-cycle question.