Methodology
How CLV Intelligence monitors, scores, and verifies
Every alert in CLV Intelligence is the output of the same three-step process — sourced from official government records, scored by impact, and linked back to the document it came from. This page explains exactly how that works, so you can judge the alerts on their methodology, not on our word for it.
1. How we monitor
CLV Intelligence ingests from official government and regulatory sources every business day: the CMS Medicare Coverage Database (LCDs and NCDs), CMS Transmittals (Publication 100-04), the Physician Fee Schedule and OPPS, NCCI edits, the Federal Register, the OIG, FDA drug approvals, and the Local Coverage Determination and Billing & Coding Article pages of all 7 Medicare Administrative Contractors. Ingestion runs on a fixed daily schedule; you can see the live status, including the last run and the 15+ source families monitored, at /data-status. The complete list of sources is documented on the data sources page.
2. How we score — the signal score
A date-ordered list of changes assumes you have time to read everything. We don’t make that assumption. Every change is rated by a signal score built from four factors, so the changes most likely to cost revenue or trigger a denial surface first:
Recency
How recently the change was published. Newer changes weigh more, because the window to act is widest right after publication.
Effective-date urgency
How soon the change takes effect. A change with a near-term effective date is more urgent than one effective next year.
Source authority
The weight of the issuing source. A CMS National Coverage Determination or final rule outranks a routine administrative notice.
Change type
What kind of change it is. A coverage restriction or code deletion outranks an informational update — it’s more likely to cause a denial.
The combined score sorts the feed into tiers — critical, high, and routine — so a coverage restriction with a near-term effective date leads the feed while administrative notices settle to the bottom. The same scoring powers the action guidance attached to each alert: a plain-language summary of what changed and what to do.
3. How we verify
Every alert links directly to the originating government document — the transmittal, LCD, NCD, or Federal Register notice it came from — and those source links are verified at ingestion. We do not paraphrase a change and ask you to trust the summary: the summary is there to triage, and the source is there to confirm. That source-first design is also what makes the alerts usable as audit documentation, because a reviewer can follow every claim back to its government origin.
What we deliberately don’t do
- We don’t process PHI. CLV Intelligence reads only publicly available government policy — never patient data or claims. No protected health information enters the platform, so there’s no HIPAA exposure and no BAA required.
- We don’t give legal or compliance advice. Alerts surface and summarize official changes so you can act in time; they are not an audit certification or a substitute for qualified compliance counsel.
- We don’t fabricate dates or details. When a source doesn’t publish a real date, the field stays empty rather than guessed — a NULL is always preferable to a fabricated value.