Data sources
Where CLV Intelligence gets its data
CLV Intelligence draws exclusively from official, publicly available government and regulatory sources — 15+ source families across CMS, all 7 Medicare Administrative Contractors, the Federal Register, the OIG, and the FDA. Every alert links back to the originating document, so nothing rests on our interpretation alone.
CMS Medicare Coverage Database (LCDs & NCDs)
Visit source ↗Local and National Coverage Determinations — the coverage criteria and medical-necessity requirements that drive most Medicare coverage decisions and denials.
CMS Transmittals (Publication 100-04)
Visit source ↗Internet-Only Manual transmittals and Change Requests that operationalize Medicare policy for claims processing.
Medicare Administrative Contractors (all seven MACs)
Visit source ↗The LCD and Billing & Coding Article pages of Noridian, CGS, First Coast, NGS, Novitas, Palmetto GBA, and WPS — monitored by jurisdiction.
Federal Register
Visit source ↗Proposed and final rules — Physician Fee Schedule, OPPS, IPPS, ESRD — read for the provisions that change coverage or payment.
Office of Inspector General (OIG)
Visit source ↗The OIG Work Plan and guidance, which signal the billing and coding areas under federal audit focus.
U.S. Food & Drug Administration (FDA)
Visit source ↗Drug and biological approvals with billing implications — new products that drive new HCPCS/J-codes and coverage questions.
NLM Clinical Tables API — ICD-10-CM & HCPCS
Visit source ↗Authoritative, free code definitions from the National Library of Medicine, powering the code lookup tool and linked to CMS and CDC source documentation.
CMS NCCI edits & fee schedules
Visit source ↗National Correct Coding Initiative edits and the Physician Fee Schedule / OPPS pricing files that change correct coding and payment.
Freshness & verification
All sources are ingested and signal-scored every business day, and source links are verified at ingestion. You can see the live ingestion status — including the last run and the 1,150+ alerts on record — at /data-status. For how those sources are scored and verified, see our methodology.