# Changelog

User-visible changes to the Verzi Healthcare Data API and dashboard. Format follows [Keep a Changelog](https://keepachangelog.com/); dates are ISO-8601 UTC.

The full commit history is at [github.com/verzihealth/cms-star-ratings](https://github.com/verzihealth/cms-star-ratings). Anything not user-visible (refactors, test-only changes, internal tooling) is deliberately omitted from this log.

---

## Unreleased

### Added
- `GET /vbc/acos/{aco_id}/clinicians` and `GET /vbc/reach/{entity_id}/clinicians` list the clinicians Verzi links to an ACO, one row per NPI, with the best link confidence, every match method and the performance years. Filter by `min_confidence`, `year` and `match_method`; page with `limit` and `offset`.
- Each row of `GET /v1/archive/changes` and `GET /v1/archive/upcoming` carries a `tags` object: `change_type` (edits, fees, coverage_policy, contractor_page, code_set, regulatory, other), `payer`, `state`, `mac_region`, `specialty`, `effective_date` and `upcoming`. The tags are read from the record. Nothing filters on them yet.
- The confirmation email for a code watch names each watched code that no tracked document maps to today. A watch on such a code is saved and sends nothing until a document maps to the code.
- A change alert email entry for a row file (for example an NCCI MUE file) now has a "Codes changed" line. It lists the HCPCS Level II codes whose row changed, sorted, and gives a count of the other changed codes it does not show.
- `GET /v1/archive/changes` takes three new filters: `change_type` (one or more, comma-separated), `payer` and `state`. Each keeps the rows whose `tags` hold that value and runs before the row cap. `GET /v1/archive/changes.rss` takes `change_type`.
- `POST /v1/subscriptions` takes `frequency`: `daily` or `weekly`, for an email subscription. Without it, a code watch is daily and everything else weekly, as before.
- Change alerts by email send an upcoming change again 30 days and 7 days before it takes effect. The entry starts "Takes effect in N days, on <date>", with the days left on the day the email is built. A weekly reader gets the reminder in the next weekly email. Reminders come first in a digest, under "Taking effect soon". A reminder follows the same choices as every other entry. A later revision that takes effect on or before an earlier one replaces it. A version that takes effect later does not, so each upcoming change gets its reminders. One email can then hold two reminders for the same document, one for each date.
- The digest signup on updates.verzi.health has three role buttons: ED coder, DME biller, and Denials and appeals. A button ticks the choices for that role. The coder can change any choice before signing up. The role itself is not saved. A note next to the ED coder button says that alerts by ED CPT code are not available yet.
- The weekly digest signup on updates.verzi.health offers optional choices: change type (NCCI edits, fees, coverage policy, DME MAC page changes), payer (Medicare, Medicaid, with a state list under Medicaid) and specialty (DME). A group left empty means all of it.
- `POST /v1/subscriptions` takes four category filters: `change_types` (edits, fees, coverage_policy, contractor_page), `payers`, `states` and `specialties`. Each is a list of values from the change tags a feed row carries. A change must match every list that is set. An unknown value answers 422. A subscription that names the `contractor_page` change type gets the DME MAC web pages as entries. The confirmation email says when a chosen category cannot send to the address yet.
- Each row of `GET /v1/archive/changes` and `GET /v1/archive/upcoming`, and each webhook change event, carries `changed_codes`: the HCPCS Level II codes whose row changed in that version of a row file (the NCCI MUE file, the DMEPOS fee schedule), against the version before it. Codes only, never a value. A code watch matches on it. The list is empty until the stored comparison is filled.
- **A coder label can carry the refill applicability verdict.** An approved coder label of kind `refill_exempt` on a CMS passage now gives `warrants.applicability` its cited answer: `applies` false. This holds only when the label is approved and still bound to its content, its passage serves on the date by the same rule as W3, and CMS's own words in that passage state that the refill rules do not apply. The first basis entry is the passage's source proof, plus `coder_label_id`, the label that marks it. CMS's words serve under the receipt's license rule. No such label is approved yet, so no answer changes today.
- The archive runner can record a version filed under the wrong document (`--mark-wrong-document`). `--reversion` then files that file under the document the current rules derive. First case: two Arizona DME rental fee files that were filed as purchase rates for FY2027.
- **A manual section on a date, from the chapter or the transmittal that changed it.** `GET /archive/docs/{doc_id}/section?section=181&date=2024-02-01` (key required) answers for Claims Processing chapter 20 (`manual:clm104c20`) and Program Integrity chapter 5 (`manual:pim83c05`) with the section's own words, verbatim, and a citation to the stored file and character span: a held chapter version, or the transmittal that added or revised the section. `status` is `served`, `deleted` (a transmittal deleted the section) or `unknown`, with `unknown_reason`; a transmittal serves a section only when every later revision of the chapter that is dated on or before the date and not rescinded has a held transmittal that was read. Needs the transmittal index of migration 168. Until the PDF text order check lands, a section cited to a manual or transmittal PDF answers `unknown` with `rendering_not_in_document_order`: no text, with the citation, chain and basis kept.
- `--reversion --redate` now writes one kind of change without a schema migration: a stated start for an undated version whose own stored text states it by the manifest's text rule. It goes to `archive_stated_dates`, with BACKUP and UNDO log lines, and a repeat run writes nothing. Every other planned change still writes nothing and fails until migration 223.
- `--mark-wrong-document --allow-empty-doc` may mark every version of a document, but only when the `--redate` planner, in the same run, re-files each one under another document. A plain `--reversion` then files them there. Plain `--reversion` now reads the stored text for a text rule under `window_by_group`, so a re-filed Louisiana PDF fee schedule gets the window its page one states, not an observed one.
- The archive runner can list, for one source, every stored file whose document, version label or effective window would change under the source's current rules (`--reversion --redate --dry-run`). Writing those changes waits on a database change that is not released yet.
- **The archive now captures 42 CFR part 422 (Medicare Advantage) and the CMS-4201-F final rule.** The eCFR source `cfr_42` lists part 422 beside parts 405, 410, 411, 414, 421, 424 and 498, so its weekly run stores one dated version per eCFR amendment date from 2017-01-01 (doc `cfr:42-422`), with the same as-of dating and text rendering as the other parts. Medicare Advantage plans follow Medicare's NCDs and LCDs under 422.101(b), and may use their own posted coverage criteria only where Medicare's are not fully established (422.101(b)(6)). The Federal Register source `fr_cms_rules` pins CMS-4201-F (88 FR 22120, published 2023-04-12, doc `fr:2023-07115`), the rule that added 422.101(b)(6), so it can be captured on its own. No reader serves these yet.
- **`GET /v1/rules/receipt/changes` takes `payer`.** `payer=medicaid` (claim type `dmepos`) says what CMS's public Medicaid NCCI edit files (procedure-to-procedure and medically unlikely edits), for each quarter we have archived, list for the code on two dates, and for the pair when `companion` is given: `r2_mue` and `r2_ptp`, each side with the archived file it was read from, and `changed`. `changed` is `true` when one date is `ok` and the other is `not_listed` or `listed_not_in_window`, or when a value CMS gives differs; `null` when either date is `unknown`. The same values in the next quarter's file is not a change. No Medicare block is in the answer: the blocks it does not read are named under `not_served`. These are national files, and the answer says nothing about coverage. Only public HCPCS Level II codes are answered. Until a quarter's file is loaded, both dates are `unknown` and `changed` is `null`. `payer` omitted, `medicare` or `medicare_advantage` answers as before. Any other payer answers `not_yet_available` with no block.
- **The public code check says whether the HCPCS code was valid on the date of service.** `/check/{hcpcs}` and `/v1/check/{hcpcs}` gain a `code_validity` block with the code warrant's answer (#414). `status` is `valid`, `not_valid` or `unknown`. `reason` names the cause, for example `terminated`, `not_yet_effective` or `no_file_in_force`. `cms_fields` quotes CMS's `ADD_DT`, `EFCTV_DT`, `TERM_DT` and `ACTN_CD` as the HCPCS file states them. `file` cites that HCPCS file: its quarter and sha256. When the file cannot be read, the block says `unknown` with reason `source_unavailable`. The page shows a "Code valid on the date of service" section with these labels and values only.
- **CMS's per-provider totals beside the detail on `/provider/{npi}`.** The `prescribing` and `utilization` blocks gain `cms_summary`: CMS's own totals per data year from "Medicare Part D Prescribers - by Provider" (claims, drug cost, beneficiaries) and "Medicare Physician & Other Practitioners - by Provider" (services, beneficiaries, Medicare payments), 2013 onward. They include the rows CMS suppresses from the per-drug and per-service detail (fewer than 11 claims or beneficiaries), so they can be higher than the detail figures. A provider whose detail rows are all suppressed now shows the summary. Both are rows on `/sources`.
- `GET /archive/upcoming` now ties code-list changes to their codes. A future phase that the Required Prior Authorization List prints for some codes (for example "10/28/2026 Nationwide") is a row of `kind: code_list_phase`, with the phase's date and scope as printed and the codes it covers. A new version of the Required Face-to-Face Encounter and Written Order Prior to Delivery List lists the codes that version names in `affected_codes`, once the list is parsed. Other rows are `kind: document_version`.
- KB code pages show a "Coming changes" card: each dated change on the upcoming calendar that names the code, with the publisher's effective date, the document and version, the publisher's own words (the list's row for the code, or the revision note), and the archived file.
- The receipt for 36415 can quote Claims Processing Manual ch. 16 §60.1, and the receipt for 99281 to 99285 can quote ch. 4 §160, verbatim from the held chapter, once the section passes its slice check. Until then each answers held, with its reason.
- Receipt `rule_passages`: a code map. For 99281 to 99285, 12002, 96374, 36415 and 71046 the block now also resolves CMS manual sections of Claims Processing ch. 12 and Benefit Policy ch. 6, on the date of service. Each passage lists the codes it answers in `codes`, and the block lists the code's refs in `code_refs`. A section serves only after its stored `pdftotext` check matches; until then it answers `unknown` with its citation. An agent picked the sections as a finding aid; a certified coder has not confirmed the map yet.
- `/archive/docs/{doc_id}/section` answers for `manual:clm104c12` and `manual:bp102c06` with chain, basis and citation in place of `chapter_not_supported_yet`. It still serves no PDF text.

Fixed
- Manual section reader: a chapter whose revision table is not found now answers `unknown` (`revision_table_unreadable`). Before, an unread table counted as an empty one, so an incomplete chain could read as complete. The table heading is matched in any letter case.
- `GET /employers?specialty=...` lists groups ranked by how many members have the given CMS primary specialties, with a count per specialty, the primary state, and the curated parent system and employer type. Filter by `state`, `min_providers` and `employer_type` (for example `pe_platform`). Example: every anesthesia group in the US with its anesthesiologist and CRNA counts. An unknown specialty is a 422 that names it.
- **DMEPOS fees inside a CMS revision file's window.** Three held CMS revision files now answer in the window their authority states: the CMS-1687-IFC file (June 2018), the CARES Act file under CMS-5531-IFC (2020-03-06 to 2020-06-30) and the revised 2022 file (2022). Inside the window, a state cell that the quarter file holds answers with the revision file's amount. `as_of.rule` is `revision_window`, and `as_of.revision` names the window, the authority's own sentence, the authority file, how the window ends, and the quarter cell it revises. A cell found only in the revision file answers only in 2020-04-01 to 2020-06-30, where the 2020Q2 zip holds no state table. A cell found only in the revised 2022 file answers no cell, because that file lists codes added through October 2022. The window rows are written by `--reversion` after the quote is found in the archived authority (migration 186). Until they are written and the files are parsed, the `revision_not_served` answer stays. In 2022 Q2 and Q3 no quarter state table is held: the revised 2022 file answers there only over the January 2022 state table that #470 continues into those quarters (member continuations, migration 174), and `as_of.revision.revises` names that continuation. Until #470's continuations are written, those dates keep the `revision_not_served` answer.
- The source archive captures every Medicare Internet-Only Manual that CMS publishes, not only Pub 100-02, 100-03, 100-04 and 100-08: Pub 100, 100-01, 100-05, 100-06, 100-07, 100-09, 100-10, 100-11, 100-16, 100-18, 100-19, 100-22 and 100-24, and Pub 100-04 Ch.39. Each chapter keeps its observed window until a rule maps its revision to a transmittal.
- KB code pages show "Code valid on the date of service": the code's status and reason code, the HCPCS file's own fields as CMS states them (`ADD_DT`, `EFCTV_DT`, `TERM_DT`, `ACTN_CD`), the file's quarter and a link to the archived file. It is the same answer as `/check`. When the HCPCS file cannot be read, it says unknown with the reason `source_unavailable`. The free E0601 page shows it too.
- Receipts can now show labels that have been double-checked but are still waiting for a coder. Each one is in its own list, `receipts.r3.documents[].double_checked_items`. To get there, two independent automated reviews from different model families must both find the label correct, and Verzi's rule checks must pass. No certified coder has reviewed these labels yet. They are not approved, they are never mixed into the approved items, and they may change once a coder reviews them. Each item gives CMS's exact words at its quote span, its section and version as of the date of service, and the sentence "Double-checked by two independent automated reviews; not yet reviewed by a certified coder." `coverage.double_checked_served` counts them separately (it appears only when there are some), and `items_served` still counts approved items only. CMS's sections still serve in full, as before. Receipts signed before this change still verify.
- **The MCP tool `receipt_changes` takes `payer`**, with the same answer as `GET /v1/rules/receipt/changes`. `payer=medicaid` (claim type `dmepos`) compares what CMS's public Medicaid NCCI edit files (procedure-to-procedure and medically unlikely edits), for each quarter we have archived, list on two dates, with no Medicare block. Until a quarter's file is loaded, both dates are `unknown`. `payer` omitted or `medicare` answers as before; `medicare_advantage` reads the same Medicare diff, and its reasons name the ma scope, as on the route. Any other payer answers `not_yet_available` with no block.
- **The MCP server lists keyless coverage tools.** Anonymous `tools/list` includes `check_dme_coverage`, `get_documentation_requirements`, `search`, and `fetch`, and does not include `get_provider` (that lookup still requires an API key). An anonymous documentation answer has document names, CMS links, section headings, counts, and one sample requirement. The rest of the passage text and the denial sentences require a plan that includes receipts. The official endpoint is `https://mcp.verzi.health/mcp`. `https://mcp.verzi.health` is an alias. The support contact is hello@verzi.health. A key is sent as `Authorization: Bearer` or `X-API-Key`. A free key is at `https://docs.verzi.health/signup`.
- **MCP sign-in names two scopes.** `/.well-known/oauth-protected-resource` names the MCP resource `https://mcp.verzi.health/mcp`. A client can ask for `providers:read` or `receipts:read` (`receipts:read` includes provider reads). The authorization server document is at the issuer, `https://auth.verzi.health`. The REST API does not take these tokens.
- **MCP sign-in for paid tools.** A paid MCP tool called with no credential answers HTTP 401 with `WWW-Authenticate`, so Claude, ChatGPT, and Grok Bot can start sign-in. Sign-in is an emailed code on the existing login. A new work email becomes a free account when the code is entered, with no approval wait. Receipts still need a paid plan. An existing Verzi API key still works as `Authorization: Bearer` or `X-API-Key`. Support: hello@verzi.health.
- **The MCP server lists two read-only resources.** `verzi://guide` says when to use Verzi: Medicare DME coverage criteria, LCD and HCPCS lookup, documentation requirements, and receipts, for DME suppliers and billing teams. It does not make a prior-authorization decision. `verzi://codes` shows the HCPCS shape and the public pages. Those page slugs are lowercase (`/codes/e0601`, `/lcd/l33718`). For CPT codes, Verzi serves the code only, never the AMA descriptor. The server does not advertise an MCP App.
- **Maryland COMAR 10.09.12 sections, in Verzi's own format.** `GET /state-regulations/md/comar/{section}` (for example `10.09.12.04`) returns the section's citation, heading, regulation text and stated effective date, parsed from the archived page, with a receipt that cites the COMAR section, links its official page on regs.maryland.gov and carries the archived file's sha256. The publisher's pages are CC BY-NC-SA 4.0, so their bytes and full text are not served: `md_medicaid_dme_coverage` is now `state_reg_own_format`, and the archive file endpoints give no bytes link and no text for it.
- **Arizona Medicaid DME fee rows for every purchase schedule.** Arizona (AHCCCS) DME purchase rates are now parsed for every fee file from FY22 to FY27, not only FY22 and FY27: the FY23 to FY26 files, the July 2026 rates by provider type (09, 18, 19, CN), and its "New Additions" sheet of codes moved from the professional fee schedule. Codes, rates and headings are stored as printed, never descriptions.
- **Arizona Medicaid DME prior authorization and fee rows.** The source archive now captures the documents that state Arizona's (AHCCCS) DME prior authorization rules: AMPM Policy 820, Chapters 8 and 13 of the fee-for-service billing manual, and the fee-for-service prior authorization requirements page. Arizona DME fee rows (codes, modifiers and rates as printed, never descriptions) are now parsed for the FY22 and FY27 purchase schedules and every FY24 to FY27 rental schedule; the other purchase files wait on a parser change.
- **California Medicaid (Medi-Cal) DME purchase and rental rates (paused pending license review).** The source archive can capture Medi-Cal's full rates file (the "Download All Medi-Cal Rates" zip), plus the June 30, 2001 rates file. Rows for the DMEPOS HCPCS codes (A, B, E, K, L and V) parse into the code, the procedure type, and the Basic Rate (the purchase maximum) and Rental Rate as printed. Each row keeps its sheet and row as the receipt locator. For example, E0601 is $609.55 purchase and $75.37 rental in the rates as of October 15, 2026. The Rates page shows an AMA accept screen and states the AMA CPT copyright, so the file is held under the AMA/ADA terms key: its facts and source links are served, but not its bytes, full text or any descriptor. Scheduled capture is paused pending a license review (Adrian, 2026-10-23).
- **California Medicaid (Medi-Cal) DME sources.** The manifests for the Medi-Cal provider manual's Durable Medical Equipment sections, the TAR and Non-Standard Benefits List for the DMEPOS code ranges (A-B, E, K-L), and the Medical Supplies billing workbook are built and tested but not yet scheduled. Rows from that workbook parse into the code, the maximum allowable product cost per unit of measure as printed, the unit, the TAR Required flag and the quantity limit. Each row keeps its sheet and row as the receipt locator, and no description is stored. The DME manual sections print CPT descriptors, so they are held under the AMA/ADA terms key: their facts and source links can serve once captured, their bytes and full text do not. Medi-Cal's DME purchase and rental rates are not included yet, because they download only after an accept screen on the Rates page.
- **Colorado Medicaid (Health First Colorado) DME fees.** The source archive is ready to capture every Colorado DME fee schedule edition that HCPF lists, from 2020 to July 2026, each dated from the effective date in its file name. Rows from the 2021, October 2025 and July 2026 editions parse into the shared state fee table. Each row keeps the code, modifier, purchase or rental unit, non-rural and rural rates, the prior authorization flag and the age range exactly as HCPF printed them, with the sheet and row they came from. No description is stored. The 2020, 2023, 2024 and July 2025 editions will be archived but not parsed. Captures and serving are not live yet.
- **State Medicaid fee schedule route.** `GET /v1/fee-schedules/medicaid/{state}/{code}?dos=` returns a state Medicaid program's own published fee rows for a code, from the version of the state's fee file in force on the date of service. Every row in force is returned with its modifiers, rate heading, area and provider type as printed, the amount cell as published, its sheet and row or page, and the archive citation of its file. `amount` is set only when the cell is a plain number. Optional `modifier` and `kind` narrow the rows. No description is served. `status` is `ok`, `not_found`, `unknown` (no version in force on the date, with the reason), `not_yet_available` (no parsed fee schedule for the state) or `withheld_license` (the state publishes the file under license terms that do not let its rows serve). A state that files each edition of its schedule as a separate document (Washington, Illinois, North Carolina, New York) answers `unknown` with `editions_overlap` on any date two held editions cover, until the editions are dated end to end. The route serves Medicaid data only, never a Medicare amount.
- Florida Medicaid DME: the July 1 2026, January 1 2026 and 2025 AHCA fee schedule workbooks are archived from the Rule 59G-4.002 page and parsed (codes, modifiers, maximum and rental fees as printed, age, units and limits, prior authorization), each edition dated from its stated start.
- Florida Medicaid DME coverage policies (Rules 59G-4.072 to 59G-4.077) and the fee-for-service QIO's list of services that require prior authorization are archived.
- **Georgia Medicaid DME sources.** The source archive now captures the Georgia Department of Community Health DME fee schedule (the current quarter plus the quarterly history back to October 2014) and the quarterly Part II DME policy manual. Georgia fee rows parse into codes, the rate columns as printed (No Modifier, Purchase (NU), Rental (RR), and the state overutilization modifier), maximum units, billing period, prior authorization and under-21 cells. Each edition answers for the calendar quarter its file name states. Both sources are held under the AMA/ADA terms key because the GAMMIS portal posts the AMA and ADA copyright notice: their facts and source links serve, their bytes and full text do not.
- **Illinois Medicaid DME fee rows.** Illinois (HFS) DME fee schedule rows are now parsed from every archived XLSX edition from November 2019 to 2026: codes, purchase and rental prices as printed, the PA Req cell, and Max Qty with Max Days. Each wheelchair code's electric and manual rows keep the state's own Note letter (E or M). Descriptions are never stored. The July 2019 edition is not parsed: it prints one rent heading twice over two different columns.
- **Illinois Medicaid DME sources.** The source archive now captures the seven Illinois HFS Medical Prior Approval Criteria PDFs for DME items (oxygen, standing devices, pediatric specialty beds and others) and the 2025 edition of the Illinois DME fee schedule, which it had missed because HFS files it in a different folder. Illinois fee rows are not parsed yet.
- Indiana Medicaid (IHCP) fee rows (paused pending license review): the monthly Professional Fee Schedule, with DME and medical supply rates (new and rented), PA flags, age and unit limits and each rate's effective and end dates, from the current edition and 15 earlier editions back to July 2018. The IHCP DME code tables (covered codes, capped rental lists) will be archived too. IHCP shows AMA and ADA terms on these files, so their facts and source links can be served once captured, not the files themselves. Scheduled capture is paused pending a license review (Adrian, 2026-10-23).
- **Kentucky Medicaid DME fee rows.** Rows from the Kentucky MSEA (Medical Supplies, Equipment and Appliances) fee schedule now parse into the code, the purchase and rental prices as printed (including `M` for manually priced items), the purchase and rental prior authorization cells and the quantity limit. Each row keeps its sheet and row as the receipt locator, and no description is stored. The workbook carries the AMA CPT notice, so it is now held under the AMA/ADA terms key: its facts and source links serve, its bytes and full text do not. Kentucky's DME prior authorization rule is in regulation 907 KAR 1:479, which the archive already captures; the per-code PA flags come from the fee schedule it points to.
- Louisiana Medicaid DME: the current LDH DMEPOS fee schedule workbook will be archived from the lamedicaid.com DME fee page and parsed (codes, modifiers, type of service, fees as printed, manual-pricing marks, prior authorization, service limit and age cells). The eleven PDF editions LDH still posts (2005 to September 2024) will be archived too, each dated from the window it states. Captures are scheduled (weekly, Tuesday); nothing from these files is served yet.
- Louisiana Medicaid Services Manual Chapter 18 (Durable Medical Equipment) will be archived as the state's DME coverage document. Louisiana marks prior authorization on the fee schedule itself, so no separate list exists.
- **State Medicaid fee schedules: one shared table for every state.** State fee files in the archive can now be parsed into `medicaid_fee_row` by one generic parser driven by a mapping file per state. Each row keeps the state's own words: the rate heading, the area, and the amount exactly as published (a number is read out only when the cell is a plain number), plus the sheet and row or page it came from. Descriptions are never stored. Nothing is served yet: the lookup endpoint with a receipt comes next.
- **Maryland Medicaid DME fee rows.** The Maryland Department of Health DME, disposable supplies, oxygen and prosthetics fee schedule is now parsed: each code's rental price and maximum purchase price as printed (including "I/C", individual consideration, kept as text), with the payment authorization, limitation and price effective date cells. Codes that Maryland prints on several rows with different prices (E0240, T5001 and others) are numbered in file order, never told apart by their descriptions, which are not stored.
- **Michigan Medicaid DME fees and coverage.** The quarterly Michigan DMEPOS fee database (13 of the 14 workbooks MDHHS lists, January 2023 to October 2026) can now be parsed into the shared state fee table. Each row keeps the code, modifier, rate and stated rate-effective date exactly as Michigan printed them, with the sheet and row they came from. The Michigan Medicaid Provider Manual, whose Medical Supplier chapter is the state's DME coverage policy, is now archived each quarter and dated from the edition date it prints.
- Missouri Medicaid (MO HealthNet) DME fee rows: the monthly Durable Medical Equipment and Supplies fee schedule, with purchase, rental and repair rates, covered or noncovered status, prior authorization flags, unit limits and each rate's effective date. The DME provider manual versioning rule reads the edition date from its file name; existing versions will carry that date after a prod reversion run.
- **Mississippi Medicaid fee schedules will be archived monthly.** `ms_medicaid_fee_schedules` stores the Division of Medicaid's current comprehensive, ASC, outpatient hospital and physician-administered drug fee schedules, its comparative rate analysis, its prior authorization procedure code list and its preferred diabetic supplies list. Each renamed edition continues its schedule's document. The files list CPT codes, so they are stored but not served. The first capture is the 2026-12-01 monthly run.
- **North Carolina Medicaid DME fee schedule: every edition now parses.** NC prints its prior approval mark inside the code cell (`E0601*`). Each era of the mapping now admits it, so the printed code is kept, the bare code (`E0601`) and the mark (`*`, "item requires prior approval") are stored beside it, and a lookup by the bare code finds the row.
- A manifest for the Medicaid NCCI edit files (procedure-to-procedure and medically unlikely edits, for practitioner, outpatient hospital and DME services) is ready. It is not yet captured or scheduled. CMS lists MUE files back to January 2020. Once captured, the files carry CPT codes, so they will be cited by link, not served. A code's presence in an edit is not a statement that a state Medicaid program covers it.
- **New York Medicaid DME fee rows.** The current eMedNY DME fee schedule is now parsed: each code's fee, rental fee and By Report basis as printed, with the max units and prior approval cells. Codes that New York prints on several rows with different fees (E1399, T5999, E2599) are numbered in file order, never told apart by their descriptions, which are not stored. Older editions with fee rows that have no code, or with a stray cell beside the table, are not parsed yet: they wait on a parser change.
- **Ohio Medicaid DMEPOS fee schedule: the 07/01/2021 edition is now captured.** Its fixed URL (`DME-DMEPOS-PaymentSchedule.xlsx`) is pinned beside the current edition, so the next capture archives it under the same document, dated 2021-07-01 from the file itself.
- **Ohio Medicaid DMEPOS fee schedule: the 07/01/2021 edition can now be archived.** Its file name (`DME-DMEPOS-PaymentSchedule.xlsx`) states no date, so the archive refused it. The manifest now dates that one name to 2021-07-01, the date the file itself states ("Payment schedule effective 07/01/2021", sheet `Appendix A`, cell A3). It is filed under the same document as the January 2026 edition, which closes it. No edition between the two is archived yet, so once the file is imported, a date of service from 2021-07-01 to 2025-12-31 resolves to the 2021 edition.
- **Ohio Medicaid DMEPOS fees: every rate sheet parses.** The January 2026 ODM workbook now yields 2,712 fee rows from its DME, O&P, Oxygen, Wheelchairs and Atypical Items sheets (before, the DME sheet only). Modifiers printed in the code cell are split out (`A4224 U1`), and same-code rows carry the printed residence (`Non-institutional only`, `LTCF only`) or a row number within the code. Each row keeps its sheet and row as the receipt locator; no description is stored.
- **Ohio Medicaid DME sources.** The source archive now captures the Ohio Department of Medicaid listing of prior authorization requirements (Revised October 2026), and Ohio DMEPOS fee rows from the DME sheet of the January 2026 schedule parse into codes, amounts as printed, effective dates, prior authorization and frequency-limit cells. The Ohio fee file is held under the AMA/ADA terms key because it prints a CPT descriptor: its facts and source link serve, its bytes and full text do not.
- **`GET /v1/rules/receipt?payer=medicaid&claim_type=outpatient&state=CT` now serves `receipts.r3` from the state's own Medicaid manual.** Before, an outpatient request under `payer=medicaid` answered `not_started` with no receipts. Now it returns the outpatient receipt keys: `r3` is the state manual passages block for the `state` param, and every other receipt is `not_yet_available` with a reason. No receipt holds Medicare data, `usable_for` is empty and `meta.claim_type_status` is `not_yet_available`. For Connecticut, `r3` offers the state's hospital outpatient chapter by `link_basis: chapter_scope`. That link is by state and claim type alone, so the same passage comes back for every code, and it does not say any code is covered. For Indiana, `r3` lists the code tables that print the code (`link_basis: code_printed`), as on the dmepos receipt; a printed code is not a coverage claim either. `text` is null with `text_withheld`. `state` is accepted for outpatient only under `payer=medicaid`; Medicare outpatient with `state` is still a 422. The other inputs only the dmepos receipts read (`ordering_npi`, `cba`, `rural`, `beneficiary_state`, `use`, `claim_item`, `denial`, and the `icd10` paging) are now a 422 for Medicaid outpatient, as they are for Medicare outpatient; before, they were ignored on the `not_started` answer. `claim_format=institutional` under `payer=medicaid` answers the same way. Any other claim type that is not started still answers `not_started` under Medicaid. Medicare and Medicare Advantage outpatient answers are unchanged. The MCP `receipt` tool answers the same way.
- State Medicaid fee parser: a layout can now read a header printed on several rows, several sheets of one workbook, a modifier printed in the code cell, and same-code rows told apart by a verbatim cell, by file order, by provider type or by client age band. Each rate group can carry its own effective date, footer rows are skipped by their text, and a date-range cell fills the row's start and end dates. Descriptions are still never stored.
- **`GET /v1/rules/receipt?payer=medicaid` now fills `receipts.r2` from CMS's public Medicaid NCCI edit files** (procedure-to-procedure and medically unlikely edits), for each quarter we have archived. `r2.mue` says whether the file for the date's quarter lists the code, and `r2.ptp` says the same for the pair, read in one order: the code as column 1 and the `companion` as column 2 (`not_listed` says nothing about the other order). `ok` means the file lists the row. A listed pair whose own dates do not cover the date is `listed_not_in_window`, not `ok`. Each part has a `status` (`ok`, `listed_not_in_window`, `not_listed`, `unknown` or `not_requested`), a `statement` with the file's effective date, and the archived file it was read from. These are national files: the block names no state and says nothing about coverage. Only public HCPCS Level II codes are answered. Answers start once each quarter's file is loaded; until then both parts are `unknown` with a reason. The block carries `verzi_note` and no Medicare label, and it never raises the answer's confidence above `partial`. Every other receipt for `payer=medicaid` except `r3` is still `not_yet_available`. `payer=medicare` answers are unchanged.
- **`GET /v1/rules/receipt?payer=medicaid`: each `code_printed` passage in `receipts.r3` now says which file printed the code.** The new `printed_in` object holds the `doc_id` and `file_name`, the publisher's own file name from the archived file's URL. A `code_printed` passage is picked by code alone, so the table that prints the code can be for another kind of claim than the receipt's; `printed_in` lets you see which table it is. It is the publisher's file name, not a Verzi label, and it does not say the code is covered or what claim type the table covers. `file_name` is null when the archived URL names no file (for example a download script). `chapter_scope` passages do not carry it.
- **`GET /v1/rules/receipt?payer=medicaid&state=IN` now fills `receipts.r3` from the state's own Medicaid manual.** `r3` has `receipt_kind: state_manual_passages`. It lists the passages of the edition in force on the date of service. Each passage names its `link_basis`. `code_printed` means the state printed the code in that table. It does not mean the code is covered. `chapter_scope` means the state's chapter for the claim type, chosen by state and claim type and never by code. Each passage carries a receipt: the archived file, the span and the hash of the span. `text` is null on every passage and `text_withheld` says why (`license_held` today). `not_served` names each document that could not be checked or served, on any status. When no passage is found and a document could not be checked, `status` is `unknown`, never `not_found`. `unknown` with reason `chapter_scope_map_not_readable` means the chapter map failed its checks and nothing is served. A heading too long to be a title is null, with `heading_withheld`. Indiana code tables are loaded. The Connecticut chapter link is for outpatient claims, which the Medicaid receipt does not build yet. Every other receipt in a Medicaid answer is still `not_yet_available`, `usable_for` is still empty, and `payer=medicare` answers are unchanged. The MCP `receipt` tool answers the same way. Under `payer=medicaid`, `r3` carries no `crosswalk` label on any status, because the crosswalk rows are Medicare's; with a `use`, `claim_item` or `denial` filter it is left out and named in `meta.filtered_out`. In `confidence`, a state manual passages block never grades above `partial`.
- **`GET /v1/rules/receipt?payer=medicaid&state=TX`: `receipts.r3` can now read the Texas Medicaid Provider Procedures Manual**, the complete book the state publishes each month, from the book in force on the date of service. Texas answers once the books are loaded; until then `r3` says `not_yet_available` (`state_not_loaded`), as for any state not held. A `code_printed` passage is one page of the book that prints the code in a table cell (`passage_kind: book_page`). `heading` is the page's running header, the publisher's own handbook title, and `reviewed_text` is the month the page prints. A `chapter_scope` passage is a whole handbook: the hospital handbook for `claim_type=outpatient` and the durable medical equipment handbook for `dmepos`, chosen by state and claim type and never by code. Neither says a code is covered. `text` is null with `text_withheld` on every Texas passage. Books from June 2015 on are read; for a date of service in January to May 2015 `r3` answers `unknown`. If a book's pages print another month than the edition the archive holds it as, nothing from it is served (`edition_month_mismatch` in `not_served`).
- The source archive now captures CMS's Medicaid prescription drug reimbursement chart by state from Medicaid.gov every month: the current chart and the 12 archived quarters, each dated from the quarter its own page one states. It is listed at `/sources` as `medicaid_rx_reimbursement`.
- South Carolina Medicaid DME: the SCDHHS fee schedule workbook is now parsed (codes, modifiers, payment rate as printed including "M" for manually priced, prior authorization flag, per-row effective date).
- South Carolina Medicaid DME Services Provider Manual, its Change Control Record, and the manual's procedure code section (which names the fee schedule as the prior authorization list) are archived.
- **State Medicaid provider bulletins and notices are now archived for 21 states** (AL, AZ, FL, IA, IN, LA, MO, MT, NC, ND, NE, NH, NY, OK, SC, SD, TX, VA, VT, WA, WY): one `<st>_medicaid_bulletins` manifest each, doc_type `provider_bulletin`. FL, NC, NY and TX run weekly; the rest run monthly.
- The pages are collected only (license `state_ama_ada_terms`, not public): nothing is served on /sources, KB pages or the API.
- Texas Medicaid fee rows now carry the note codes TMHP prints beside each fee (`note_codes`, for example `["5"]`), taken from that fee's own rate group. The parse mapping holds TMHP's legend for the five codes in its own words, so a fee of `0` with note 5 reads as "This procedure is manually reviewed to determine pricing." instead of a zero fee. Other states store no note codes. The parser version is now `medicaid_state_fees/v4`.
- **Texas Medicaid DMEPOS fee rows.** The Texas (TMHP) static DMEPOS fee schedule now parses from both of its fee sheets: purchase and rental fees on the DME sheet, non-facility and facility fees on the General sheet. Each row keeps the code, modifiers, provider type, client age band and type of service as printed, the fee as printed, and the effective date TMHP states for that fee, with the sheet and row it came from. No description is stored. The source stays under the AMA/ADA terms key: its facts and source link serve, its bytes and full text do not.
- **Virginia Medicaid DME fee mapping.** Appendix B, the DMAS DME and Supplies Listing, now has a parse mapping for all seven header layouts its editions have used since July 2021, across every category sheet of the workbook. Each code's fee, SA or PA type and limit are kept as printed, with the rental or other modifier split out of the code cell and the "Old HCPCS Code" cell kept to tell crosswalk rows apart. Descriptions are not stored. No edition is parsed yet: every edition misprints a few code cells (such as "E0272RR" or "E 1405 RR"), and these wait on a parser change.
- **Virginia Medicaid DME service authorization.** The source archive now captures Appendix D of the Virginia DMAS DME provider manual (service authorization rules), and the current December 2025 edition of the DME manual's Chapter IV (covered services and limitations), which it had missed because DMAS reissued the chapter under a new address. Virginia fee rows are not parsed yet.
- Washington Apple Health (HCA) medical equipment and supplies billing guide is archived quarterly as the state's DME coverage document, with dated versions back to 2019 from the Internet Archive.
- Washington DME fee schedule parse mapping: codes, modifiers, the four HCA fee columns (non-rural, rural, Seattle and Vancouver competitive bid areas) and the PA/EPA flag, as printed.
- Wisconsin Medicaid DME fees now parse from the ForwardHealth DME Index and Maximum Fee Schedule PDF: every section (home health, oxygen and respiratory, wheelchairs, orthotics, chiropractic, prosthetics, specialty, complex rehab). Each rental and purchase cell gives its PA part and its fee as printed ("90 / $1.51" is 90 days before PA at $1.51 a day; "Y / $452.20" is PA required, $452.20), with the allowable modifiers, the RB repair dollar limit and the life expectancy. Codes and facts only; descriptions are never stored.
- Louisiana Medicaid DMEPOS fees now parse from the eleven PDF editions LDH posts (September 2005 to September 2024) and the October 2024 PDF, alongside the current workbook: fee, TOS, modifier, PA flag, age restriction and fee effective date per code. The workbook's fee effective date is now read too (manually priced rows have none).
- Wisconsin Medicaid (ForwardHealth) maximum fee schedules for every service area can now be archived: 48 monthly extracts, including Outpatient Hospital, Ambulatory Surgical Center, Physician, Laboratory, Radiology, Anesthesia, Dental, DME and Disposable Medical Supplies. Each row in these files states its own effective and end date. ForwardHealth stops offering the downloads on February 1, 2027, so a copy of every file was taken on November 11, 2026. The files carry CPT and CDT codes and sit behind ForwardHealth's AMA and ADA license screen, so they are cited by link, not served.
- The Wisconsin Disposable Medical Supplies Index and the Noncovered DME codes list can now be archived. Earlier DME Index and DMS Index editions that ForwardHealth still posts on its archive page (named from 2008 on) can now be backfilled.
- Wisconsin Medicaid DME coverage rules (Wis. Admin. Code chapter DHS 107, which holds DHS 107.24 on durable medical equipment and supplies) are now archived, with Internet Archive history back to 2015. Earlier editions of the ForwardHealth DME Index and Maximum Fee Schedule, back to 2016, can now be backfilled from the Internet Archive, and each edition is labeled with the date printed in its footer. ForwardHealth shows AMA and ADA terms on its fee pages and the DME Index prints CPT descriptors, so the DME Index is cited by link, not served.
- `GET /clinicians/{npi}/performance-years` returns MIPS scores by performance year, PY2017 onward. Each year lists every score CMS publishes for the clinician, one per group plus any individual or APM score, with the group PAC ID, the highest final score and the APM programs CMS states, such as SSP or REACH.
- `/provider/{npi}` adds `quality.latest_performance_year`, and `/provider/{npi}/acos` adds `cms_apm_programs`.
- **Medicare Physician Fee Schedule route, internal keys only.** `GET /v1/fee-schedules/mpfs/{hcpcs}?dos=&mac=&locality=` reads CMS's relative value release in force on the date of service: the RVUs, the locality's GPCIs, the conversion factor and the payment indicators, each with the archive version and member files it came from. Today every caller without an internal key gets `status: withheld_license` and no value. `calculated_amount` is worked out by Verzi from the values in the row with the formula CMS prints; it is not an amount CMS printed. A quarter that CMS revised answers `unknown` until a held CMS document states when the revision took effect.
- **The OpenAPI spec now says how to authenticate.** `components.securitySchemes` has `ApiKeyHeader` (`X-API-Key`) and `BearerApiKey` (the same key as `Authorization: Bearer`), and every operation has `security`: both schemes when a key is required, `{}` first when a key is optional, `[]` when the operation is public. OAuth 2.1 protects the MCP server only; the spec description links its metadata.
- The REST API accepts the API key as `Authorization: Bearer <key>` as well as `X-API-Key`, like the MCP server.
- A key that belongs to an organization now gets that organization's daily cap in the rate-limit headers too (`"org-day"` in `RateLimit-Policy`). Browsers can read the rate-limit and deprecation headers (`Access-Control-Expose-Headers`).
- `GET /fee-schedules/opps/{hcpcs}` and `GET /fee-schedules/asc/{hcpcs}` return Medicare's national hospital outpatient (OPPS Addendum B) and ambulatory surgical center (ASC Addendum AA) payment rates by HCPCS code, for every quarter held or one quarter. OPPS rows carry the status indicator, APC, relative weight, rate and copayments. ASC rows carry the payment indicator, an office-based flag for P2 and P3, the weight and the rate. The rates are CMS's published national amounts, with no wage index applied. No procedure descriptor is served.
- `GET /rules/receipt/changes` and the `receipt_changes` MCP tool now answer `claim_type=outpatient`. The answer compares two dates of service for a hospital outpatient code.
- The blocks are `r1` (the OPPS Addendum B row, compared by CMS's values), `r2_mue`, `r2_ptp` (with a companion code) and `rule_passages` (the CMS manual sections mapped to the code). `r2_mue` and `r2_ptp` also compare CMS's values: the same edit in the next quarter's file is not a change. Each side keeps its own citation.
- `rule_passages` names the refs whose served text differs (`changed_refs`). It quotes both sides as served and adds no summary.
- The outpatient answer holds no DME rule. It refuses `state`, `cba`, `rural`, `modifier`, `modifier2` and a `setting` other than `outpatient_hospital` with a 422.
- Each entry of `rule_passages.refs` gives both sides' `status`, `version_id`, `chapter_rev`, `transmittal_number` and `text_sha256`. A section deleted on one date and served on the other is a change.
- `GET /v1/rules/receipt?claim_type=outpatient`: `receipts.r1.fact.as_of` now says when the OPPS Addendum B version in force reached Verzi: `origin`, `first_seen_at`, `first_seen_after_dos` and `versions_held`. `first_seen_after_dos` is `false` when Verzi held the version on or before the date of service. It is `true` when Verzi held a file of the quarter on the date of service and the version in force came later; `first_seen_note` then states the count and the date. It is `null` for a file of any other origin, and for a quarter that Verzi began to hold after the date of service. A `not_found` answer carries the same `as_of`. `first_seen_at` is the UTC date of the capture, so a capture late in the evening in a US time zone has the next UTC date.
- `claim_type=outpatient` on `/rules/receipt` and the MCP `receipt` tool now adds `receipts.rule_passages`. It holds only the CMS manual sections that the code map names for the code, in the map's order, each quoted from the version in force on the date of service. It holds no DME row: the block has no `rows` and no `pending_bounds`. The outpatient answer stays in progress.
- A code that the map does not name answers `rule_passages` `unknown` with reason `no_passage_mapped` and no passage. A section that does not serve on the date says why, as on the DME receipt.
- The mapping of a code to a section is Verzi's finding aid, not the authority. A certified coder has not confirmed it yet. `rule_passages` is not weighed in `confidence`.
- `r3` for outpatient stays `not_yet_available`. Its reason now says that no LCD or Article is linked to outpatient codes yet and that the manual passages are in `rule_passages`.
- `/rules/receipt/appeal`, `/rules/receipt/changes` and their MCP tools take `claim_type` and `claim_format`. The appeal builds its answer for `dmepos` only. Any other claim type, `outpatient` included, answers `status` `not_started` with a reason and `meta`, and no DME rule. `claim_format=professional` serves the dmepos answer with `meta.claim_type_status` `partial`. A request with no claim type gets the same answer as before.
- **`claim_type=outpatient` on `/rules/receipt` and the MCP `receipt` tool serves Medicare hospital outpatient rule blocks, in progress.** The answer has `r0` (provider standing), `r1` (the code's row in the OPPS Addendum B version in force on the date of service: status indicator, APC, payment rate and copayments as CMS lists them, with the file's citation), `r2` (the outpatient hospital MUE and the hospital PTP pair), `code` (the code's OPPS Addendum B listing for the quarter), `timely_filing`, and `modifiers` when you name one. `r3` is `not_yet_available`: policy passages for outpatient codes are not linked yet. No DME block is served for this claim type.
- `meta.claim_type_status` is `in_progress` for outpatient: the rule blocks are served, and the claim field map is not started. `meta.claim_type_reason` gives the count of filled rows. `/rules/claim-fields?claim_type=outpatient` still answers `not_started`.
- For outpatient, `setting` defaults to `outpatient_hospital`. Another setting is a 422, and so are the inputs that only the DME blocks read (`ordering_npi`, `state`, `cba`, `rural`, `beneficiary_state`, `use`, `claim_item`, `denial`, and `icd10_offset` and `icd10_limit` when not their defaults).
- `claim_format=institutional` serves the outpatient blocks with `meta.claim_type_status` `partial`. The other institutional claim types stay `not_started`.
- The outpatient blocks are Medicare rules. For a `payer` other than `medicare` or `medicare_advantage`, `claim_type=outpatient` answers `not_started` with no blocks.
- For a CDT code (first character D), `r1` answers `unknown` with `reason_code` `license_scope` on every date of service: Verzi does not read CDT rows from the OPPS Addendum B file.
- For a CPT code on a date of service before 2022-01-01, `r1` answers `unknown` with `reason_code` `license_scope`, as on `/fee-schedules/opps`. No CPT descriptor is served.
- Pennsylvania Medical Assistance public fee schedule files (ambulance, dental, FQHC and RHC, family planning, and two behavioral health code charts) are captured and rechecked weekly. The Pennsylvania DME coverage chapter is no longer rechecked, because its host now disallows automated access in robots.txt.
- Medicare Part D plan formularies and average unit costs from CMS's monthly and quarterly formulary public use files:
  - `GET /rx/partd/plans/{contract_id}/{plan_id}/{segment_id}`: a plan's premium, deductible, service area, cost share by tier, and insulin cost.
  - `GET /rx/partd/plans/{contract_id}/{plan_id}/{segment_id}/drugs/{ndc11}`: one NDC on one plan, with tier, prior authorization, step therapy, quantity limit, the cost share for its tier, and the plan's average unit cost for a 30, 60 and 90 day supply, as CMS states it (not reflecting discounts).
  - `GET /rx/partd/drugs/{ndc11}/plans`: every plan that lists the NDC, filterable by county.
- Every answer names the CMS release it comes from. Both files refresh monthly.
- The source archive now captures four more Medicare contractor sites every Friday: the CGS A/B MAC (Jurisdiction 15), the CGS Home Health and Hospice MAC, the Noridian A/B MAC (Jurisdictions E and F) and the First Coast A/B MAC (Jurisdiction N). Each page is held as published, with an observed window. Fee schedule pages behind the AMA CPT notice stay out.
- The DME certificates of medical necessity and DME information forms (CMS 484, 846, 847, 848, 849, 854, 10125, 10126) and the ABN (Form CMS-R-131, its instructions and the lab sample) are now captured monthly.
- The CMS DMEPOS competitive bidding page that states the temporary gap period is now captured every Monday. Its last capture was 2026-10-15, so the competitive bidding reader answered unknown for later dates; after the first Monday run its observed window covers them again.
- `GET /clinicians/{npi}/qpp-history` serves CMS's QPP Experience file, PY2017 onward: one row per practice the clinician reported with, per year, with the participation path, practice size and state, special statuses, final and category scores, and the payment adjustment. Practice totals (Medicare patients, allowed charges, services) are labeled as the practice's.
- `GET /clinicians/qpp-cohorts/{cohort}` lists the clinicians of one inferred practice cohort in one year. CMS names no practice; a cohort groups the Group rows that repeat one practice's state, size, Medicare patients and allowed charges.
- `/provider/{npi}` adds a `qpp_experience` block with the newest year's highest-scoring row.
- **The receipt quotes the Article's ICD-10-CM lists in force on the date of service.** `/rules/receipt` and the MCP `receipt` tool add `receipts.icd10_lists`: for each Policy Article mapped to the code, the covered and non-covered ICD-10-CM codes with CMS's descriptions and CMS's group paragraphs, from the Article version in force on the date of service, with the version, its dates, the archived list file (SHA-256) and the CMS source URL. A list Verzi does not hold for that version says so (`not_held`, with the reason); it never falls back to another version and never means a code is not listed. Long lists page with `icd10_offset` and `icd10_limit` (default 500, at most 5000 rows per list); each list states `codes_total` and `next_offset`. The Article's HCPCS code tables are not served, and any CMS text carrying CPT-shaped content is withheld and marked.
- A served label on `/rules/receipt` and the MCP receipt tool carries `review_note: "Approved by a certified coder."` when a certified coder approved that label for the requested code. Other approved labels carry no `review_note`. The receipt never names the coder.
- **`claim_type` and `claim_format` on `/rules/receipt`, `/rules/claim-fields` and the MCP `receipt` and `claim_fields` tools.** `claim_type` takes one of 17 values: `dmepos`, `practitioner`, `independent_lab`, `ambulance`, `asc`, `inpatient`, `outpatient`, `snf`, `home_health`, `hospice`, `esrd`, `rhc_fqhc`, `corf`, `orf`, `cmhc`, `dental`, `pharmacy`. `claim_format` (`professional`, `institutional`, `dental`, `pharmacy`) asks for every claim type with that format. If you send neither, you get `dmepos`, the only claim type filled today, and the answer is the same as before.
- Every answer now names its claim type in `meta`: `claim_type`, `claim_format`, `claim_type_status` (`filled`, `in_progress`, `not_started` or `partial`), `claim_type_reason` when the answer is not complete, and `claim_types`, with one entry for each claim type you asked for.
- A claim type that is not filled yet, such as `practitioner` or `outpatient`, answers `claim_type_status: not_started` with a reason and no receipt blocks or claim fields. It never gets DME rules instead. The answer still echoes your filters the way a served answer does: `meta.filters` when you pass `use`, `claim_item` or `denial`, and an empty `filtered_out`.
- `claim_format=professional` gives the `dmepos` blocks with status `partial`, and `meta.claim_types` marks the other professional claim types `not_started`. On a partial answer, three fields say what the whole-answer fields cover: `meta.note` starts with "Partial answer", `confidence.claim_types` lists the claim types covered and not started, and `usable_for_claim_types` names the claim types that `usable_for` applies to. `usable_for` and `confidence.overall` keep their usual values.
- An unknown value is a 422 that lists the valid values. So is a `claim_type` and `claim_format` that disagree, for example `claim_type=dmepos&claim_format=institutional`.
- **Each receipt block now says which claim fields and denials it answers.** On `GET /rules/receipt` and the MCP `receipt` tool, every block has a `crosswalk` label: whether you need it to fill the claim (`initial_claim`) or to answer a denial (`claim_denial`), the CMS-1500 items it covers (such as `24G`), the Verzi Health denial ids it answers (D1 to D47) and a priority. Each denial also says whether a claim that hits it is `returned` (correct it and send it again, with no appeal rights) or `denied` (reopening or appeal), or `check` where that is not settled yet. Claim items follow the date of service: the oxygen CMN and the DIFs count only for a date before 2023-01-01. The label is Verzi Health's and sits beside CMS's text, never inside a quote.
- **Filter a receipt by use, claim item or denial.** `use=initial_claim` or `use=claim_denial`, `claim_item=24B` and `denial=D25` keep only the matching blocks, on the route and the MCP tool. `meta.filtered_out` lists every block that was left out, so a filtered answer never looks complete when it is not. An unknown claim item or denial id gets a 422 that says which values are valid.
- **`GET /rules/claim-fields?hcpcs=&dos=&use=` and the MCP `claim_fields` tool.** For a code and a date of service, they list every CMS-1500 item and every claim attachment in force on that date. Each row gives who fills the field, the rule that decides it and whether the receipt serves that rule yet, its priority, and the denials it can trigger. Where the receipt already serves the rule for the code, CMS's words are quoted with their receipts. Rows follow the date of service: the oxygen CMN and the DIFs appear only for a date before 2023-01-01, and the ABN row names the form edition valid on that date. These take no claim or patient values.
- **The receipt names the DME MAC for the beneficiary's state on the date of service.** Pass `beneficiary_state` (two letters, no other beneficiary data) to `GET /rules/receipt` or the MCP `receipt` tool. `receipts.dme_mac.jurisdiction` quotes CMS's "Who are the MACs" row for that state (jurisdiction, contractor, states as CMS prints them) from the page version in force on the date of service, with its source proof. A date before the first held capture (2026-09-26) answers `not_determinable` with the reason and the first capture date; nothing is guessed.
- **`receipts.dme_mac.place_of_service`** quotes the place-of-service lines that DME MAC publishes, from the versions in force on the date of service, and lists each code a quoted line names with its offsets (`codes_named`). Which codes are valid for DME at that MAC stays `pending_coder_label` (`codes_valid_for_mac` is null). The CGS supplier manual chapter is cited, not quoted (its PDF rendering is not verified for word order); Claims Processing Manual ch. 26 §10.5 is named with the reason it is not served yet.
- **`receipts.r0.ptan_on_dos`** states that no held source gives the supplier's PTAN or its effective dates (the PECOS enrollment extract carries no PTAN; the supplier directory carries no NPI). No date is given.
- **Face-to-face / written order prior to delivery list on the receipt.** A new block, `receipts.face_to_face_wopd`, says whether the code is on CMS's Required Face-to-Face Encounter and Written Order Prior to Delivery List on the date of service: `required_face_to_face_wopd` is `listed`, `not_listed` or `not_determinable`. The archive's as-of rule picks the list version in force on the date of service. The block never reads the newest version. It quotes CMS's own row (`list_entry`: code, descriptor and row as printed, page) and the list's title, authority line and "Effective date:" line. The receipt pins the version (`version_id`, `file_id`, `sha256`, `publisher_effective_from`/`_to`, `rule`, `boundary`) and gives `row_ref` (the parsed table, file and code, plus the page).
- When no held list version is in force on the date, the block answers `not_determinable` with `not_determinable_kind` `no_version_in_force` and `as_of.reason` (for example `before_first_stated_start`). It never says "not required". Verzi holds only the list effective 10/28/2026 today, so dates of service before 2026-10-28 answer this way until the earlier editions are captured. The confidence rollup does not weigh that absence, the same rule as `prior_authorization`. Other cases also answer `not_determinable`, and they grade weak: a held edition with no parsed rows, an edition whose effective date does not read, and an edition that states a date after the date of service.
- The KB code page shows the same answer under the prior authorization line.
- **Medicare Advantage receipts.** `GET /rules/receipt?payer=medicare_advantage` (alias `ma`) returns the same Medicare envelope plus `receipts.medicare_advantage`: 42 CFR 422.101(b) (the lead-in, (b)(1) national coverage determinations, (b)(2), (b)(3) local coverage decisions) quoted from the eCFR version of part 422 in force on the date of service; 422.101(b)(6) (internal coverage criteria) with its state (`applicable`, `not_yet_applicable`, `not_in_force`, or `unknown` with a reason) and CMS-4201-F's own applicability sentence (88 FR 22120: coverage beginning January 1, 2024); and the Subpart M appeal path (422.566, 422.578, 422.582, 422.584, 422.590). Every quote carries its own receipt: the archived file, the rendering, the version and as-of rule, the character span, the quote's SHA-256 and a `/source-proof` link. When the text is not held or not found, the block says why; it never guesses. If a later rule changed (b)(6)'s words after CMS-4201-F, the state is `unknown`, not dated by CMS-4201-F. `payer=medicare` is unchanged. The MCP `receipt` tool takes the same `payer` value.
- `GET /rules/receipt/appeal?payer=medicare_advantage` frames the exhibit as a request to the Medicare Advantage organization for reconsideration and adds the 422.101(b) and Subpart M quotes beside the code's exhibit.
- **National Coverage Determinations on the receipt.** A new block, `receipts.ncd`, names each NCD CMS links to the code on the date of service and quotes its sections from the NCD version in force on that date. The link is CMS's own words: the code's LCD or Policy Article, in its version in force on the date of service, prints the NCD Manual section number (for example "240.4") in its "CMS National Coverage Policy" section. Each NCD carries that evidence (`cited_by`: the citing document, version, section, the number's character span and CMS's line), the version in force (`version_in_force`, chosen by the archive's as-of rule, never the newest version), its sections (`benefit_category`, `item_service_description`, `indications_limitations`, `cross_reference`, CMS's words with their spans) and a receipt (file, SHA-256, `render_sha256`, renderer version).
- When no version of a linked NCD is in force on the date, the NCD answers `unknown` with `not_determinable_kind` `no_version_in_force` and `as_of.reason` (for example `before_first_stated_start`, or `not_observed_on_date` for an NCD CMS never dated). A missing rendering, missing sections or a section hash that no longer matches also answers `unknown`; no other version is served instead. A code with no CMS citation held answers `none_served`, which says nothing about whether an NCD applies.
- A cited number links only when the NCD version in force on the date of service states that same number; otherwise it is listed under `unresolved_citations` with reason `number_mismatch`. Only a number that directly follows an NCD marker ("100-03", "National Coverage Determinations", "NCD") in the same sentence counts. A number after "version", "$" or "§", or one that belongs to another publication ("Section 110.1 of Pub. 100-02"), never counts. CMS's citing line (`cited_by[].quote`) goes through the same CPT paragraph rule as the NCD's sections. A line with a CPT code, or next to one, is withheld, and its `redactions` say why.
- The KB code page shows one line per linked NCD under the face-to-face line.
- **Receipts name the version CMS had published on the date of service, when CMS later made another version retroactive.** CMS sometimes posts a new version of an LCD or Article after the date of service and makes it effective from the same start date as an earlier version. The receipt still names the later version as the version in force, as before. Beside it, `version_in_force.published_on_dos` now names the version CMS had published on the date of service, with CMS's own "Updated On" dates for both (from the Public Versions table in the archived MCD pages), the character span of each date row in its archived rendering, and a short Verzi-written note (`verzi_note`, not CMS's words), in the form "CMS later made version N effective retroactively from <start date> ... On the date of service the published version was M". It appears only when the two versions differ and the archive proves which one was published on that date; otherwise nothing new appears. The field is in each document of `receipts.r3` on `GET /rules/receipt` and on the MCP `receipt` tool, which returns the same signed answer.
- **Text renderer 2.0.0 keeps the publisher's word order.** It walks an HTML page in document order and keeps table cells apart. It is used only to re-render the LCD and Article versions whose Coverage Indications section could not be matched on the old rendering. Their sections can then be shown. Every rendering made before stays stored and unchanged, so every receipt already issued still checks.
- `GET /source-proof` (and `/warrant/receipt`) now names the renderer that made the cited rendering (`renderer_version`). It also accepts the `render_sha256` of a 2.0.0 rendering.
- `/rules/receipt` and the MCP `receipt` tool carry a new block, `receipts.rule_passages`: for the denial reasons D2 to D46 and the CMS-1500 items 11, 12, 17, 17b, 19, 27 and 32, the 42 CFR and CMS manual sections that decide them, each quoted whole from the version in force on the date of service (42 CFR 410.38, 414.210(f), 414.226, 414.229 and 424.507 today), with its receipt. A section that is not held for the date, or cannot be served, says so with the reason (`not_held`, `unknown`, `not_linked`). Manual sections answer `unknown` until their PDF text is verified to keep CMS's word order. Where CMS's rule sits inside a larger section, `pending_bounds` lists it for a coder; nothing there is approved.
- With a modifier in the request, `receipts.modifiers.required_when` points at the Policy Article text where CMS states when each modifier is required (denial reason D6), beside the validity check.
- `GET /v1/rules/ncci/mue` and `GET /v1/rules/ncci/ptp` take `program=medicaid`. It answers from CMS's public Medicaid NCCI edit files (procedure-to-procedure and medically unlikely edits), for each quarter we have archived. The answer says whether the file for the date's quarter lists the code or the pair (`listed`), with the file's effective date, the value CMS gives, and the archived file it was read from. A pair is read in one order, and the answer's `statement` names it ("Read as column 1 ..., column 2 ..."): a not-listed answer says nothing about the other order. It is a national file: there is no per-state answer, and it says nothing about coverage. Only public HCPCS Level II codes are answered; any other code answers `listed: null` with a `reason`. A quarter that is not held or not yet read also answers `listed: null`. Answers start once each quarter's file is loaded. Until then every `program=medicaid` answer is `listed: null`. `program` omitted means `medicare`, and those answers are unchanged.
- **BPCI Advanced anchor providers as an employment signal.** The attribution ledger gains `bpcia_crosswalk` rows: the hospital (by its PECOS PAC id) where CMS's BPCI Advanced data crosswalk lists the physician as attending or operating physician on anchor episodes, per model year, confidence 0.60. `GET /provider/{npi}/employment` shows them on an employer the physician reassigns benefits to, and `GET /employers/{pac_id}` counts them in that employer's attribution summary. Hospitals only; the crosswalk carries no CCN for physician group initiators.
- **TEAM joins the Innovation Center models.** `GET /vbc/models` lists the Transforming Episode Accountability Model with CMS's stage; `/vbc/models/team/participants` pages the 721 acute care hospitals on CMS's participant list (CCN, mandatory or voluntary, CBSA state), with the list date as the period. TEAM is a row on `/sources`.
- **ACO membership by NPI.** `GET /provider/{npi}/acos` and `GET /vbc/provider-lookup?npi=` answer which MSSP ACOs and ACO REACH entities an NPI is linked to. Every row carries `match_method` and `confidence`: `cms_qpp_participation` (CMS's QPP participation status names the APM entity for the NPI; `high`, or `stated_unresolved` when the name resolves to no single ACO), `organization_name_match` (`medium` when the name belongs to one PECOS organization and one participant row, else `low`), `individual_name_match` (`low`). A name match is never presented as exact. The name search on `/vbc/provider-lookup` stays and marks each row as a participant name search. The `qpp_mips_tin` source now loads CMS's QPP participation status per NPI (practice and APM entity; the TIN stays masked by CMS). Rows appear after the first QPP crawl and the next ACO load on production.
- **DMEPOS fee answers quote CMS's words when ceiling and floor are both 0.00.** `GET /rules/dmepos/fee` adds `ceiling_floor_statement`: CMS's README text for fields 6 (CEILING) and 7 (FLOOR), word for word, with the README file's id, sha256 and name. A zero in those fields is CMS's value, not a missing number. The statement appears only when the quarter's README is one Verzi has read; otherwise the field is absent.
- **Six Innovation Center models.** `GET /vbc/models` lists BPCI Advanced, CJR, Kidney Care Choices, Primary Care First, Making Care Primary and ACO Primary Care Flex with CMS's stage and what we hold. `/vbc/models/{model_id}/participants` pages the participants CMS lists (BPIDs, CCNs, KCC ids, ACO ids). `/vbc/models/{model_id}/results` pages the financial and quality results CMS publishes (CJR reconciliation PY1 to PY7, KCC PY2022 to PY2024, PCF PY2022 to PY2024) as one row per participant, period and metric. `/vbc/models/by-npi/{npi}` returns the model participations CMS states for an NPI (BPCI Advanced anchor providers), each marked `cms_crosswalk_npi`. Each model is a row on `/sources`.
- **The warrant's ordering block states the ordering (not referring) physician's eligibility on the date of service.** `warrants.w0_ordering.order_referring_eligible.eligibility_on_dos` answers `valid` (on the CMS Order and Referring roster in force, with DME = Y), `not_valid` (`dme_n`, `not_in_file_in_force`) or `unknown`, with a reason from the same vocabulary as the other validity facts. It quotes the roster's columns under CMS's own header names, PARTB, DME, HHA, PMD and HOSPICE, as Y or N, and null for any other value. It cites the edition in force and the edition that established the row. Provider standing's unknown answers for the roster now carry a `reason_code`.
- **DMEPOS fee answers for the PEN codes (enteral and parenteral nutrition, B-codes and E0776).** `/rules/dmepos/fee` answers a state fee for these codes from CMS's PEN fee schedule, 2016 to 2026, in the quarter of each PEN file (January, and the quarters CMS revised the file). Other quarters answer no fee cell until CMS's own statement that the PEN file stays in force is recorded. The 2015 PEN file is a national fee and is not served yet. The file states no ceiling or floor, so those fields are null.
- **The warrant says whether the HCPCS code was valid on the date of service.** The new `warrants.code` block answers `valid`, `not_valid` (`terminated`, `not_yet_effective`) or `unknown` with a reason. It quotes CMS's own `ADD_DT`, `EFCTV_DT`, `TERM_DT` and `ACTN_CD` from the HCPCS file in force, and cites that file. It also carries `COV`, `PRCNGCD` and `BETOS` as the file in force states them, and cites that file in `admin_citation`. From 2015 to 2020 only the January file is held, so a code added or ended later in those years is answered from the next file, which states the date. That answer is marked `stated_in_later_file`. `TERM_DT` is the last date of use, with no grace period.
- **`POST /contact`** sends the verzi.health contact form as one email (SES, the KB login sender) to the Verzi team, with the visitor as Reply-To. It accepts posts from verzi.health only and is rate limited per IP. The site's form moves here from its Resend function in a follow-up site PR.
- **An admin can set one API key's daily limit.** `PATCH /admin/api/users/{user_id}/rate-limit` with `{"rate_limit": N}` stores that key's daily cap (1 to 1,000,000). `{"rate_limit": null}` clears it, and the key uses the free-tier default. The daily check and the `X-RateLimit-Limit` header both use that cap.
- **Check any DME code.** `/check` and `/check/E0601` are public pages. A visitor enters a HCPCS code and an optional state and date of service and sees the governing LCD, how many documentation requirements Verzi serves (counts only, with a link to the code's KB page), and the CMS source citation. `GET /v1/check/{hcpcs}` is the same answer as JSON. Both are limited per IP. The signed receipt needs a paid plan.
- **Usage dashboard.** `/admin/growth` shows signups, active keys, calls per day and week, unique organizations, top endpoints and codes, MCP calls, and the week-over-week growth rate. The page reads a daily rollup. Weekly CSV and JSON exports sit on that page. Set `PUBLIC_USAGE_STATS=1` to serve the same numbers at `/usage`.
- **MCP listing pack.** The remote MCP endpoint takes the API key as `Authorization: Bearer` or `X-API-Key`, and rejects a browser `Origin` that is not allowed. `api/mcp/server.json` matches the official registry schema. `docs/mcp-listings.md` has the fields and steps for the MCP Registry, Smithery, mcp.so, PulseMCP, Glama, the Cursor directory, and Claude and ChatGPT connectors. Nothing was submitted.
- **DMEPOS fees for 2015 and for 2016 to 2017 and 2025 to 2026 dates.** `GET /rules/dmepos/fee` answers state fees for the quarters whose main fee file was not read before: 2015 Q1, Q3 and Q4, 2016 Q1 and Q3, 2017 Q1 and Q3, 2020 Q3 and 2025 Q2 to 2026 Q1. The 2015 files state one fee per state and no rural fee, so a rural ZIP on a 2015 date gets that state fee, and the answer carries a `note` that says so.
- **The KB has its own address: `kb.verzi.health`.** The root opens the KB. The site menu and `app.verzi.health` now point there. Links to `api.verzi.health/kb/...` keep working.
- KB policy and code pages: a Contents column on the left (CMS's section headings under "Policy text", then the passages in the other documents, version history, revision history and receipts; Verzi's own sections carry a "Verzi" tag). Each section can close to its heading, with Expand all and Collapse all; sections start open. A table longer than 15 rows shows its first 10, with a button for the rest. Find in policy, a Requirements at a glance click and a Contents link open what they point into, and print shows every section and row. Below 1200px the Contents sit above the text behind a Contents button.
- KB search (`/kb`): one box finds a HCPCS code, an LCD or Article number (L33718, A52467, or 33718), or words from a CMS document title or HCPCS Level II descriptor ("oxygen", "CPAP"). A full code or number opens its page. The document list filters as you type. Links with `?code=` keep working.
- **KB toolbar and side rail.** Each LCD, Article and code page has one toolbar under the header. It holds the date of service and State. In the paid view it also holds Find in policy, Copy + cite (copies selected CMS text with its version citation) and the appeal exhibit. On a wide screen it stays at the top while you scroll, with the not-in-force banner. A right rail holds "Requirements at a glance": the approved labels on the CMS text on the page, grouped by document and kind, each a button to its highlighted passage. The related documents CMS lists moved to the rail. A one-line legend explains the teal highlight.
- **Two more lists in provider standing.** `GET /provider/{npi}/standing` returns `sam_exclusion` (listed on the SAM.gov exclusion list on the date of service) and `medicare_opt_out` (opted out of Medicare on the date of service), each from the archived list in force on that date and each with its own receipt that names the list (`source_list`). They never feed the OIG `exclusion` block. A date no held version covers answers `unknown` with a reason. SAM history starts at our first capture in 2026; the opt-out list starts at the April 2023 release, in force from its release day (about three weeks after the month).
- **The revised January 2021 DMEPOS fee schedule file answers 2021Q1 dates.** CMS posted the January 2021 file twice: `dme21.zip` and, on 2021-03-01, `dme-21ar.zip` ("Revised January 2021 DMEPOS Fee Schedule ... Revised 3/1/21"), filed under the same quarter. The archive now follows that page and versions the revised file as the quarter's second version, with CMS's own marker as its version. On the same start a stated version now ranks above none (migration 164). So `/rules/dmepos/fee` and the warrant's `w1` answer a 2021Q1 date from the revised file once it is captured and versioned, and the first file stays visible as superseded. Before, the revised file was not held and the first file answered.
- **A W1 fee answer says when the file was continued by the publisher.** CMS released no July 2021 DMEPOS fee schedule file; its July 2021 transmittal (R10865) states there are no updates for July 1, 2021, so the April 2021 file stayed in force. `/rules/dmepos/fee` and the warrant's `w1` now answer a 2021Q3 date of service from the April 2021 file. Their `as_of` carries rule `file_quarter_continued` and a `continuation` block: the through date, the archived transmittal's doc id, version id and sha256, and CMS's sentence. Before, those dates answered `not_found` with the gap reason. Nothing changes for a date inside a file's own quarter.
- **KB policy pages carry the main template's version boxes, receipts table and jurisdiction row.** Each version chip now shows its window by the as-of rule ("2020-01-01 to 2021-08-07", "2024-01-01 to today"). Versions superseded the same day they took effect sit behind a toggle, closed by default; it opens when one of them is the version shown. The receipts toggle lists every archived version of the document with its window, capture date and archived bytes sha256 (linked to the file's provenance), then the live CMS pages with the same-version rule and the window rule. A DME MAC jurisdiction row (JA to JD with their states and contract numbers, from CMS's pages) sits under the title; two letters in the State box open the governing jurisdiction.
- **Past NCD versions are captured by number.** The CMS Coverage API lists every version of a National Coverage Determination (`/v1/data/ncd/other-versions/?ncdid=N`) and serves each one with its own effective and end dates. The archive now fetches every past version the list names that it does not hold (206 versions across 112 NCDs on 2026-10-08), so `GET /archive/docs/ncd:{id}/as-of` answers dates before the current version's start once the capture runs.
- **A W2 PTP answer can carry a correction.** A later CMS file can delete a pair on or before a date that the edition in force still lists open. `/rules/ncci/ptp` and the warrant's `w2.ptp` block keep answering from the edition in force. The fact now also carries a `corrections` entry: the later edition, its deletion date, and a note. The entry stays only while every edition after it still agrees. A still-later file that lists the pair open again, or moves the deletion date past the date of service, removes the entry.
- **A free E0601 page.** `/kb/free/E0601` shows the code page in the signed-in view with no key: LCD L33718's full text, for the version in force today and the version before it, with Find, Copy + cite and the appeal exhibit. Every other version, document and code still needs a KB account. The page is not indexed.
- **Find in policy on KB pages.** Once the full text loads for a customer, a search box above it highlights every match inside CMS's verbatim text, shows "N of M matches" with next and previous, and clears with Escape. It runs entirely in the browser (no network call), skips receipts and page labels, and leaves the approved-passage highlights untouched.
- **The paid KB view.** Signed in to the KB (or calling with an API key), a code page loads every approved passage for the code on the chosen date (the same passages the warrant API serves), each with its label, CMS's words, the version, and a receipt behind a toggle; the free view still shows one sample. On a policy page, the loaded verbatim text highlights each approved passage where its words match exactly; a passage that does not match exactly is listed under the text instead, never forced. Pages never ask for a pasted key. An "Appeal exhibit (print)" button prints the page as an exhibit with every receipt open.
- **Why a passage did not serve.** When policy passages resolve, the `w3` block of the signed warrant response (`GET /v1/warrant`) carries a new top-level `withheld` field: the count of approved passages for the version in force that were not served, by reason. `verification_failed` means the words did not verify against the archived bytes. `not_on_serving_registration` means the passage quotes an earlier rendering of that version. Additive; existing fields are unchanged. KB code pages state the same reason in one sentence.
- **ICD-10-CM code lists on KB Article pages.** The current version of a policy Article now shows CMS's ICD-10-CM lists ("Codes that Support Medical Necessity" and "Codes that DO NOT Support Medical Necessity"): each group's paragraph, quoted, and its code count, free. The full code table serves customers with an API key. Read verbatim from CMS's Medicare Coverage Database download, with the file's sha256 as the receipt, and refreshed with each weekly capture. A group paragraph that cites CPT codes is withheld because it cites CPT codes. No list is ever attached to a HCPCS code page by inference.
- **Sample integration page: one code, every payer.** An unlisted, noindex page for E0601, K0606, and A4239 in Utah, with Medicare, Utah Medicaid, and a commercial payer side by side. Columns: rate, prior authorization, edits, coverage passage. Each cell is a table fact with its receipt, a quoted passage, or "Not held yet". Commercial rates come from the payer's Transparency in Coverage files, with each rate-carrying NPI checked against CMS's 2024 Medicare DME supplier file. The date-of-service picker matches the KB pages.
- **Watch a code from its KB page.** Every `/kb/code/{code}` page carries a follow box: "One email when any policy cited for {code} changes or gains a future effective date. Nothing else, ever." It uses the same double opt-in subscription as the updates page.
- **Historical versions get their own chip.** Versions pulled from the past (backfill or Wayback copies) no longer show as news. The updates feed and RSS show what scheduled runs observed; the "Historical versions" chip shows the rest. `GET /v1/archive/changes` takes `origin=live|historical` and returns `truncated` when the window holds more rows than the limit, and the page says so.
- **RSS by chip.** `/v1/archive/changes.rss?category=claim_policy` (or `fee_schedule`, `code_set`, `regulatory`) carries one chip's sources. The page's RSS link follows the chip.
- **Date of service on KB pages.** KB document pages and KB code pages have a "Date of service" calendar picker. It sets `?dos=YYYY-MM-DD`. The page shows the policy version in force on that date. The warrant API's as-of rule chooses the version. One line names it: "Version in force on 2024-03-15: version 48, effective 2021-09-27 to present". A date of service wins over `?v=`. Some dates have no archived version in force. The page then says so and shows no policy content. A bad date gives a plain error line. On code pages, each mapped policy shows its own version in force. The sample passage follows the date.
- **CMS's Required Prior Authorization List for DMEPOS, as of the date of service.** `GET /v1/rules/warrant` adds a `prior_authorization` block. `required_prior_authorization` is `listed`, `not_listed`, `listed_in_stated_states`, or `not_determinable`. It states list membership on the date of service for the request's `state`, from the list version in force by the archive as-of rule. The block carries the list's own row: descriptor, Effective Date cell verbatim, phases with their printed dates and state scope. A state that no phase in effect covers is `not_listed`; the reason quotes the later phase that will cover it, as the list prints it. With no state and only state-limited phases in effect, the value is `listed_in_stated_states`, `scope_on_dos` quotes the scope, and the rollup grades it partial. When any part of the cell the answer needs is unreadable, the answer is `not_determinable`, never a confident `listed` or `not_listed`: `not_determinable_kind` names the cause (`date_not_readable`, `scope_not_readable`, `not_parsed`, `no_version_in_force`, `state_not_recognized`). A scope reads as Nationwide only when its words are exactly "Nationwide", with at most one trailing `:`, `;`, `,`, or `.` (the list prints "Nationwide:" once). A `state` that is not a state, DC, or territory code gives this block `not_determinable` and leaves the rest of the warrant answered. A CBA gives the block no state; `provider_context.prior_authorization_state` echoes the state used. When no list version is in force on the date, or the table is absent, the answer stays in its block and does not feed `confidence.overall`. Every other `not_determinable` stays in the rollup as unknown. Every answer carries a receipt: version, sha256, observed window, and the CMS URL. KB code pages show one line for the picked date of service or today: the date it answers for, the list's Effective Date cell quoted verbatim, and a receipt link. When only state-limited phases are in effect, the line says "for these states only, as the list prints them" with the scope verbatim.
- **Transmittal subject lines, quoted.** Every CMS transmittal entry on the updates feed, the calendar, the weekly digest, the watch-a-code alerts, RSS, and webhook events now carries the cover page's SUBJECT line verbatim, labeled "CMS's subject line, quoted". Extracted deterministically from the archived rendering, joined across its wrapped lines, nothing reworded. MLN Matters articles carry no SUBJECT field and keep the plain statement that none was published. New transmittals get their line in the same weekly load that archives them.
- **Sections changed, by the publisher's headings.** Feed entries and webhook events (`sections_changed`, `sections_changed_vs`) name the sections whose words changed versus the prior version of the same document, using the publisher's own section headings in document order: "Sections changed vs version 48: Coverage Indications, Limitations and/or Medical Necessity · Revision History". Words are compared whitespace-insensitively; no diff text is written. The slot stays empty where no comparable prior version exists.
- Warrant W3 free tier: one sample item per code serves its verbatim passage text, marked `sample: true` (parity with the KB sample slot).
- **One-click unsubscribe headers.** Digest and watch-a-code emails now carry the RFC 8058 headers (`List-Unsubscribe`, `List-Unsubscribe-Post`), so a mailbox provider's own unsubscribe button revokes the subscription in one click. The in-body link keeps the scanner-safe two-step page.
- **Policy KB pages (`/kb`).** Every Medicare DME policy document (LCDs and Articles), rendered verbatim from the archived bytes, one page per document version. An independent fidelity gate proves every served section is word-identical to the source bytes; a section that fails the gate is held, never served. Free, no key: the document title, every version with its effective window, the section outline, counts, CMS's own revision-history notes, and the byte-level receipt (sha256, fetch date). Entitled keys additionally load the full verbatim section text. Thin per-code pages at `/kb/code/{hcpcs}` link each labeled code to its governing documents, and unlock ONE sample passage in full (the first approved item for the code, marked as a sample); unmapped codes say so plainly. `GET /kb/metrics` publishes the corpus numbers (codes, documents, versions, archive depth, fidelity percentage), every number computed live from the database.
- **Bounce and complaint suppression.** An address that bounces permanently or files a complaint never gets another subscription email, including the confirm email after a re-signup. Suppression is per address, written automatically from SES feedback, and checked before every send.
- **Upcoming-changes calendar.** `updates.verzi.health/calendar` lists every document version with a future effective date, soonest first, grouped by date: fee-schedule quarters, dated policy revisions, transmittal batches. `GET /v1/archive/upcoming` serves the rows (public, no key), each with `affected_codes` where a mapping exists. The dates are the publisher's own; a version with no stated effective date is never listed.
- **RSS feed.** `GET /v1/archive/changes.rss` renders the change feed as RSS 2.0; linked as the alternate representation on `updates.verzi.health`. Item text holds the publisher's facts and the sha256 receipt only.
- **Signed change webhooks.** A webhook subscription gets one signed POST per daily run with the matching changes: `X-Verzi-Signature` is `hex(hmac_sha256(secret, body))` with the per-subscription secret from registration. Every event carries its receipt (doc_id, version, sha256 of the archived bytes) and is auditable against `/v1/archive`. At-least-once delivery; dedupe on `version_id`. Documented at `/resources/webhooks`.
- **Watch a code.** Subscribe to one or more HCPCS codes on `updates.verzi.health`. A daily check emails you when a document that governs a watched code gets a new version, including a version with a future effective date ("takes effect <date>"). Same double opt-in, same one-click unsubscribe.
- **Weekly digest email.** Verified subscribers get one plain-text email a week with the window's new document versions: titles, versions, effective dates, and counts, the publisher's facts only, scope-filtered per subscription. Signup form on `updates.verzi.health` (double opt-in). A subscriber with no matching changes gets no email. Non-live versions say so (`backfill`, `wayback`).
- **Change subscriptions.** `POST /v1/subscriptions` subscribes a destination to the archive change feed: an email address (public, double opt-in; nothing sends until the confirm link is opened) or a webhook URL (API key required; deliveries are HMAC-signed with a per-subscription secret, returned once). Scope by HCPCS codes, by source ids, or neither for the full weekly digest. Unsubscribe is one click from every email.
- W3 label queue: `GET /warrant/w3/labels/pending` (verbatim quote + context per item) and `POST /warrant/w3/labels/{id}/decision` (same 409 contract as the requirement seam).
- Warrant W3: the slot now serves verbatim policy passages with Verzi labels (`policy_passages`) when the passage layer resolves for the code and DOS; the legacy requirement shape remains as fallback. Migration 128.
- Warrant W1: an exact fee-cell miss now names the modifier combinations that do exist for the code and area (`available_cells`); status stays `not_found`.
- **Updates feed.** `GET /v1/archive/changes?days=N` lists every new document version the archive observed in the window, with the publisher version, effective window, observation time, and sha256 (public, no key). `updates.verzi.health` serves it as a readable change feed: new LCD versions, fee-schedule quarters, NCCI edits, and code-set releases, grouped by day. Nobody writes these entries; the pipeline observes them.
- **Product selector on signup.** The API-key signup form now asks what you are here for: provider intelligence (the data API), warrants for RCM (paid), or both. The answer routes your access request to the right review; it does not change what a free key can do.
- **Coding rules, parsed from the archive (`/rules/*`).** The first parsed layer over the source archive turns NCCI edits (warrant W2) and DMEPOS fee cells (warrant W1) into as-of lookups, each citing the exact archive file it came from. `GET /rules/ncci/ptp?setting=&code_a=&code_b=&dos=` answers whether a code pair is procedure-to-procedure edited for a setting on a date of service, with its modifier indicator; the row's own effective and deletion dates gate the answer (the deletion date is the first day out of force). `GET /rules/ncci/mue?setting=&hcpcs=&dos=` returns the Medically Unlikely Edit value and its adjudication indicator from the quarter in force on the date. `GET /rules/dmepos/fee?hcpcs=&state=&rural=&dos=` (or `cba=` for a former competitive-bidding area) returns the allowed amount, national ceiling, and floor. Every answer carries its receipt: the version id, the archive member file id, and that file's sha256. The tables hold codes and amounts only, no CPT descriptors. Spec: `docs/PARSING_SPEC.md`.
- **Source archive (`/archive/*`).** The raw, immutable layer under every parsed table: every byte a publisher served, stored exactly as served and hashed (sha256) before any parsing, with zip members as first-class files, versioned per document, and resolvable to the version in force on a date of service. Sources so far: HHS OIG LEIE (full file and monthly supplements), NCCI PTP and MUE tables (with the DME supplier MUE table and the MUE archive back to 2020), the DMEPOS fee schedule (every quarter CMS posts, 1998 to 2026), and HCPCS Level II quarterly files (2023 to 2026). Endpoints: `GET /archive/sources`, `GET /archive/{source_id}/files`, `GET /archive/{source_id}/docs`, `GET /archive/docs/{doc_id}/versions`, `GET /archive/docs/{doc_id}/as-of?date=`, `GET /archive/files/{sha256}` (metadata and a one-hour link to the original bytes), `GET /archive/files/{sha256}/text` (the stored text rendering with its renderer version), `GET /archive/runs`. The as-of answer names the rule that decided it (the publisher's stated window, or when the archive first saw the version) and never guesses. `/sources` gains `warrants`, `archive_file_count`, `last_fetch_at`, `last_change_at`, and `latest_publisher_version`. Text from files that carry CPT descriptors (AMA license) is not served. Spec: `docs/ARCHIVE_SPEC.md`.
- **DailyMed labels, the official SPL record.** `GET /rx/labels` searches human prescription drug labels from DailyMed (the official Structured Product Labeling record, not openFDA's copy) by drug name, labeler, or a required section, returning set_id, version, effective date, title, labeler, and which of the four key sections are present. `GET /rx/labels/{set_id}` returns one label's boxed warning, indications, dosage and administration, and contraindications section text (parsed by LOINC code, nested subsections included), its RxNorm concepts, and its pharmacologic classes. Every `dailymed_url` is pinned to the version we hold (`lookup.cfm?setid=...&version=N`), so a citation never shows newer text than we stored. `GET /rx/drug-classes` serves the pharmacologic classes from DailyMed's official class mapping (1,539 classes) with the number of labels in each, filterable by name and FDA class type (EPC, MoA, PE, CS). Chosen over openFDA's label copy because DailyMed updates daily, keeps version history, and publishes the official SPL-to-RxNorm and pharmacologic class mapping files, while openFDA's copy is weekly, flattens tables, and attaches drug codes only on an exact match. New source `rx_dailymed` at `/sources`. Migration 097.
- **Drugs@FDA: the approved-drug application record.** `GET /rx/drugsfda` searches every FDA-approved drug application (29,336 NDA, ANDA, and BLA applications) by sponsor, drug name, active ingredient, application type, and first-approval-date window, returning the sponsor, products, ingredients, first and latest approval dates, and submission and product counts, ordered by first approval date. `GET /rx/drugsfda/{appl_no}` returns one application's products (form, strength, ingredient, therapeutic equivalence code, marketing status) and its complete submission history, the original plus every supplement with approval dates. The data comes from the FDA's own Drugs@FDA data files, not openFDA's copy. `first_approval_date` is the earliest approved submission; a submission status of TA is a tentative approval (approved on the merits but blocked by another product's patent or exclusivity). New source `rx_drugsfda` at `/sources`, refreshed monthly. Migration 096.
- **FDA drug recalls, matched to the NDC spine.** `GET /rx/recalls` serves the openFDA drug enforcement dataset (about 18,000 recall enforcement reports) filterable by NDC, ingredient, recalling firm, hazard class (Class I, II, III), status (Ongoing, Completed, Terminated), and report-date window. Each recall carries its classification, status, firm, reason, distribution pattern, and report, initiation, and termination dates. NDCs are extracted from three places, because the openFDA drug-code block is present on only about a fifth of records: the openFDA block, the free-text product description, and the code-info lot list. Each extracted NDC is normalized to 11 digits and matched against the current NDC directory; matched NDCs also resolve to their RxNorm ingredient. The match is fuzzy, so the response reports it honestly: `match_stats` and the `methodology_note` state that about 51% of recalls carry a parseable package NDC and about 19% match at least one NDC to the current directory (an older recall cites a discontinued NDC no longer listed). New source `rx_drug_recalls` at `/sources`, refreshed weekly. Migration 095.
- **FDA drug establishments are now queryable.** The FDA Drug Establishments Current Registration Site (DECRS) has been loaded since migration 089 and no endpoint could read it. `GET /rx/establishments` searches all 9,878 registered drug plants worldwide by operation, ISO-3 country, and firm or registrant name, returning FEI number, firm, country, and the registered operations. `operation=API MANUFACTURE` isolates the 2,400 plants that make an active ingredient, the supply-side view behind a drug shortage. `GET /rx/establishments/operations` lists the 15 operation types with counts. The `operations` array is now split into one element per operation (the source file separates them with semicolons, not commas), so a plant that registers "ANALYSIS; API MANUFACTURE; PACK" now matches an API-maker filter; the previous load stored the whole string as one element and missed those plants. The public file does not link a plant to the NDCs it makes; the `methodology_note` says so.
- **CMS Medicare fee schedules (public domain), loaded for internal rate math.** The Medicare Physician Fee Schedule (`medicare.mpfs_rvu`, `medicare.mpfs_gpci`, and the conversion factor) and the Ambulatory Surgical Center payment rates (`medicare.asc_rates`). With these, "a percentage of Medicare" becomes dollars per CPT code and locality. The non-facility allowed amount is `CF x [(work_rvu x work_gpci) + (pe_rvu x pe_gpci) + (mp_rvu x mp_gpci)]` for the named locality. Loaded for the recent years CMS publishes, refreshed quarterly. Today the only reader is the admin-only `/wellness/rates`, so these two sources are held off the public `/sources` catalog until a public fee-schedule endpoint ships (they will return to the catalog in the same change). Note: a CMS 2-digit locality code is not unique nationally, so resolve a locality by name where the code is shared.
- **FDA Orange Book and the generic launch radar.** The Orange Book has been loaded since migration 089 and no endpoint could read it. `GET /rx/orange-book` searches all 48,664 approved products by trade name, ingredient, applicant, application type (N brand, A generic), product type, and therapeutic equivalence code. `GET /rx/orange-book/launch-radar` serves `rx.v_generic_launch_radar`: the 2,457 brand prescription products with no approved generic of the same ingredient, dosage form, and strength, ordered by the date the last listed barrier falls, filterable by ingredient, applicant, and date window, with `unprotected=true` for the 866 products carrying no patent and no exclusivity at all. `loss_of_exclusivity` is an outer bound rather than a forecast: it is the latest listed patent or exclusivity date, so a late device or formulation patent can sit years past the compound patent, and most generics arrive earlier through challenges and settlements that this data does not carry. The `methodology_note` says so on every response.
- **Drug economics spine (schema `rx`).** The platform now speaks NDC. Seven new sources at `/sources`: the FDA NDC Directory (116K products, 218K packages, normalized to 11-digit NDCs), RxNorm prescribable content (NDC-to-RXCUI links and ingredient relationships, no UMLS license needed), NADAC weekly acquisition cost stored as change-only price history per NDC from 2013 forward, CMS Spending by Drug for Part D, Part B, and Medicaid (unpivoted to one row per drug, manufacturer, and year) plus the quarterly Part D file and Part D by geography and drug, Medicaid State Drug Utilization Data from 2019 forward, openFDA drug shortages, and the Mark Cuban Cost Plus Drug Company public price list captured as dated, change-only snapshots. Refreshed on the existing weekly, monthly, and quarterly pipeline cadences. API endpoints follow in a later release.
- **AHRQ MEPS Prescribed Medicines, 2018 to 2024.** Fill-level prescription events with 11-digit NDC, quantity, days supply, payer splits, and person weights, joined to the Full-Year Consolidated file for age and insurance coverage (`rx.meps_rx_fills`, about 200K fills per year). `rx.mv_meps_ingredient_mix` gives the weighted drug mix by year, payer segment, and active ingredient; `person_segment` `private_under_65` is the employer-covered population, which is the honest basis for commercial drug-mix questions that Part D cannot answer. `GET /rx/meps/mix` serves it with median generic NADAC beside the per-unit amount payers actually paid.
- **`/rx/*` Drug Economics API.** `GET /rx/summary` (counts and freshness), `GET /rx/ingredients` and `/rx/ingredients/{rxcui}` (RxNorm ingredients with NDC counts, median generic NADAC, CMS spending, Cost Plus matches, shortages), `GET /rx/ndcs/{ndc11}` and `/rx/ndcs/{ndc11}/nadac` (package profile and change-only price series), `GET /rx/nadac/movers` (largest price moves in a window), `GET /rx/spending` and `/rx/spending/top` (CMS Spending by Drug for Part D, Part B, Medicaid), `GET /rx/shortages`, `GET /rx/cost-plus` and `/rx/cost-plus/{slug}` (Cost Plus public price beside median NADAC, with the implied acquisition cost from the published formula and dated history), `GET /rx/employers` and `/rx/employers/{ein}` (DOL 5500 health plans with funding class, PBM, disclosed PBM fees, and drug-coverage carriers; default sort is active participants, largest first), and `GET /rx/pbms` (PBM rollup by plans, covered participants, and disclosed compensation). Every response carries a `methodology_note`.
- **DOL Form 5500 now covers every industry, with Schedule C and Schedule A.** `dol_5500_filings` previously held healthcare-NAICS sponsors only. It now loads all filings and records the welfare-benefit and funding flags, with a derived `health_funding_class` (self-funded only, self-funded with stop-loss, insured only) for health plans. New `dol_5500_service_providers` (Schedule C Part 1 Item 2: every service provider a plan paid, with direct and indirect compensation, DOL service codes, and a PBM flag with a normalized PBM family) and `dol_5500_insurance_contracts` (Schedule A: carrier, persons covered, health, drug, and stop-loss benefit flags, premiums earned, claims paid). The healthcare-only `financial_filings` aggregation is unchanged.
- **Which self-funded employers buy pharmacy and medical from one conglomerate.** Every DOL 5500 health plan now carries an `integration` class: `same_parent` when the PBM on Schedule C and the health carrier or medical administrator belong to one company (Caremark with Aetna, Express Scripts with Cigna, Optum Rx with UnitedHealthcare or UMR, CarelonRx with Anthem), `blues_affiliated` for Prime Therapeutics with a Blue Cross plan, `different`, or unclassified when a plan names no PBM or no carrier. Self-funded plans file no Schedule A for their medical administrator, so the administrator is read from Schedule C as well. For 2023 that is 295 same-parent self-funded plans covering 3.29M employees. `GET /rx/employers?integration=same_parent` and `GET /rx/employers/integration` (counts, covered employees, and disclosed PBM fees by class and by parent, plus the largest plans).
- **Medicare Part B ASP payment limits and the NDC-to-HCPCS crosswalk, 27 quarters since 2020.** What Medicare pays per billing unit for clinician-administered drugs (`rx.asp_pricing`) and the CMS crosswalk from every NDC to its HCPCS code with billing units per package (`rx.asp_ndc_hcpcs`), loaded quarterly with preliminary files flagged and replaced by the final. `GET /rx/asp` searches by description, HCPCS, or NDC. `GET /rx/biosimilars` puts each FDA Purple Book biosimilar beside its reference product's payment limit (Stelara J3358 against its seven biosimilars, Avastin, Remicade, Prolia and Xgeva) and the cheapest Cost Plus product of the same molecule.
- **Healthcare construction signals — new product surface.** Early construction and expansion signals from public building-permit portals, state Certificate of Need / Determination of Need programs, and statewide project registries across 19 states, refreshed daily by a new pipeline. Permits are keyword-screened and LLM-verified for healthcare relevance; CON/DoN filings are healthcare by definition. Each signal is conservatively resolved (state-scoped exact and fuzzy matching) to a facility, health system, and an organizational contact from public NPPES data where possible. Three endpoints: `GET /signals` (search by state, city, category, system, minimum value, recency), `GET /signals/summary` (counts and dollar volume by state and category), and `GET /signals/systems` (per-system rollup ranked by dollar volume). ~15.6K signals at launch spanning a 400-day window, including hospital towers, ASC build-outs, imaging centers, and senior-care projects with reported values from thousands of dollars to nearly $1B.
- **MSSP financial and quality results, PY2013 to PY2024.** We held 5,361 Shared Savings Program ACOs and 182K participants but no financial results for any of them. The gap is closed. New `mssp_financial_results` holds **5,476 ACO-years** with benchmarks, expenditures, shared savings and losses, quality scores, provider counts by type, beneficiary demographics, risk scores, and utilization. New `mssp_quality_measures` holds **127,374 per-measure results** across 74 distinct measure codes. Three endpoints: `GET /vbc/financials` (search and rank, including `sort=losses`), `GET /vbc/financials/summary` (program rollup by year and track), and `GET /vbc/acos/{aco_id}/financials` (one ACO's full history plus cumulative earned savings). The PY2024 load reconciles exactly with the CMS fact sheet on four independent figures: 476 ACOs, 10,326,340 assigned beneficiaries, $4.12B in performance payments, and 75% of ACOs earning them.
- **Rates are normalized to percent across all 13 MSSP performance years.** CMS switches these columns between a 0-1 fraction and a 0-100 percentage from file to file, and the `%` suffix does not track the switch: PY2024 dropped the suffix but kept the 0-100 scale. Left as published, a PY2018 savings rate of 0.0144 and a PY2024 savings rate of 4.215 describe comparable performance but sort 300 places apart. Savings rate, minimum savings and loss percentages, share and loss rates, quality score, and the dual and long-term-institutionalized percentages are all resolved to percent. Every row also carries `source_row`, the CMS row exactly as published, so the raw values remain available.
- **`qual_score_note` records why a quality score is absent.** PY2014 publishes "P4R" for 119 first-year ACOs, meaning they were scored on reporting the measures rather than on performance. That token now has its own column, so it is distinguishable from CMS small-cell suppression.
- **ACO REACH refreshed to PY2024, with PY2021 to PY2024 history and the full published column set.** REACH was frozen at one performance year (PY2023) since launch. It loaded a fraction of what CMS publishes. The layer now holds **421,523 participant records across four performance years** (was 128,548 for one year), **399 financial and quality records** (was 132), and **578 entity-years** covering PY2021 to PY2026 (was 74 for one year). Participant records gain participation dates, the APO election, and all 14 benefit-enhancement waiver flags. The flags cover telehealth, the SNF 3-day stay, post-discharge home visits, concurrent hospice care, and the rest. Financial results grow from 39 columns to 115. The new columns give provider counts by type (PCP, specialist, NP, PA, CNS, FQHC, RHC, CAH), every quality subscore including CAHPS and the 11 stewardship measures, beneficiary demographics, the inpatient expenditure split, and utilization rates. `GET /vbc/reach` and `GET /vbc/reach/{entity_id}` accept a `year` parameter. The participant list is now paged with `provider_limit`, `provider_offset`, and `provider_total`. One entity reached 18,506 participants in a single year.
- **`GET /accuracy/discipline-coverage`** — we now publish how much of the nation's practitioner discipline we actually hold, per state, benchmarked against the NPDB Public Use File (the only national count of state licensure actions and exclusions). Two classes are reported separately because they are different populations: exclusions (federal LEIE + state Medicaid lists) currently cover **52.1%** of NPDB-reported excluded practitioners for 2023–2025, while state board licensure actions cover **0.3%** — Colorado is the only board feed loaded so far. The gaps are published alongside the wins. Unauthenticated, like the rest of `/accuracy`. The benchmark file carries no names or NPIs; only aggregate counts are published, and state counts below 11 are withheld.
- **Primary-source state license data: Washington, Connecticut, Colorado** — the first state-board licenses loaded from the states' own files rather than NPPES self-attestation. All three come from official state open-data portals with daily refresh, no accounts, fully scriptable. New sources `wa_doh` (2,444,206 credentials), `ct_dph` (785,467 health-profession credentials), and `co_dora` (1,524,923 individual licenses) at `/sources`, with NPI linkage backfilled from NPPES license-number matching (digits + last name, confirmed against first name in WA; digit + name match in CT/CO).
- **Colorado disciplinary actions** — the CO DORA file carries structured discipline (case number, action, effective/complete dates). Of 51,848 distinct disciplinary records, the 3,266 that resolve to an NPI load into `license_disciplinary_actions`; the rest carry no NPI and are not matched by name. First state-board disciplinary source beyond exclusion lists.
- **Washington NPI coverage tripled** — WA licenses now resolve to 136,556 providers, up from 43,373, lifting NPI-linked active clinicians across the three states from 22.9% to 28.7% (40% within WA). The previous match required NPPES and WA DOH to agree on the license prefix, but they use different codes for the same credential, so most licenses could never link. Precision improved at the same time: 47 NPIs that had been attached to two different people are gone, and every linked row now agrees with NPPES on first name. Affects `/licenses/{npi}`, `/licenses/{npi}/disciplinary`, and the `/provider/{npi}` dossier.
- **WA/CT/CO refresh daily** — the three state license sources now run on a new daily pipeline cadence (11:00 UTC), each downloading its own file. `/sources/{id}/history` shows the daily trail.
- **IRS 990 coverage extended to tax years 2020–2023** — the bulk XML parser previously reached only 2024-index filings because the IRS index CSVs for earlier years omit the batch-file column needed to locate each filing's XML. That mapping is now recovered by reading each archive's directory listing directly, without downloading the multi-gigabyte archives. Result: **21,439 Form 990 filings across 5,270 healthcare EINs** (was 3,541 / 3,375) and **144,944 executive-compensation records** (was 24,027), feeding `/systems/{id}/financials` and `/systems/{id}/financials/executives`.
- **Executive-to-provider links now populate** — `executive_compensation.matched_npi` and the `irs_990_schj` attribution signals had been empty since launch (two bugs: candidates were filtered by a state that was never recorded for the filing organization, and names were parsed in the wrong order). Fixed: **44,763 executives now resolve to an NPI** (14,070 high-confidence, 30,693 medium) producing **44,025 new employment-attribution signals**. Matching stays conservative — an executive whose name fits more than one provider is left unmatched rather than guessed, so common names like "Robert Grossman" (17 NPIs nationally) produce no link.
- License Intelligence: primary-source verification links. Each license on `GET /licenses/{npi}` and each alert on `GET /licenses/alerts/recent` now carries a `verify_at` block with the state board lookup and disciplinary-page URLs. `GET /licenses/state/{state}` gains a `board_directory` block. Directory: 222 board portals across all 50 states + DC, link-checked; dead links are excluded.
- **Oregon joins the exclusion layer (34 states)** — OR publishes names + per-person exclusion-letter PDFs only (no dates, no NPI), served from a SharePoint list the loader reads through the public SOAP endpoint. Thin, but official — and it completes coverage of every state with an obtainable list. Letter URLs are kept in each record's raw payload.
- **`GET /ma-events/recent` now returns data** — a new SEC 8-K parser scans every logged healthcare 8-K for M&A item codes (Entry into Material Agreement, Completion of Acquisition/Disposition) and loads typed events into `ma_events`: acquisition announced, acquisition completed, and divestiture, each linked to its SEC filing. Target names and deal values are extracted only when confidently matched — otherwise the event carries the filing link and item facts without guessing. Initial load: 24 events (2023–2026) across Tenet, CHS, UHS, Acadia, Select Medical, Surgery Partners, Addus, Astrana, Pennant, Encompass, and Enhabit, including Astrana's $708M Prospect Health acquisition.
- **Physician employer-move detection is live** — `physician_employer_moves` now carries 207,725 arrival/departure events, derived from three PECOS reassignment snapshots (2026-06-10, 2026-08-13, 2026-08-17). The view had been empty since launch because only one snapshot existed; this week's DAC/PECOS refreshes supplied the comparison points.
- **Exclusion Screening page on the dashboard** (`/exclusions` at app.verzi.health) — screen a provider by NPI against the federal LEIE + all 33 state lists with a single verdict banner, or search state lists by name (most state records carry no NPI). Shows live coverage stats (states loaded, record counts, share of state-excluded NPIs absent from the federal list). Backed by new unauthenticated `/demo/exclusions/*` endpoints (check, search capped at 25 rows, coverage).
- **Exclusion Screening published at `/resources/exclusion-screening`** — product overview for the combined federal + state exclusion layer: per-state coverage table, methodology (primary sources, conservative NPI validation, `oig_reciprocal` handling), and the API surface. Listed in the `/resources` catalog.
- **State exclusion endpoints under `/exclusions`** — the state Medicaid exclusion layer is now queryable directly: `GET /exclusions/comprehensive/{npi}` (one-call federal LEIE + all 33 state lists; the top-level `excluded` flag covers both), `GET /exclusions/state/{npi}` (state-list records for an NPI), `GET /exclusions/state/search` (name/state/entity-type search — most state records carry no NPI, so name search is the primary screening path), and `GET /exclusions/state/coverage` (which states are loaded, per-state counts, LEIE overlap, last-load timestamps). `POST /exclusions/screen` now also returns `state_excluded` hits alongside the federal ones, and `GET /exclusions/crossref/{npi}` carries `state_exclusion_records` plus a risk flag when an NPI is state-excluded but absent from the federal LEIE.
- **State Medicaid exclusion lists — batch 2: 12 more states, 8,598 records (33 states, 85,697 total)** — DE, NE, GA, NV, IA, AK, HI, AZ, KS, NC, WV, WY join the `state_exclusions` layer from their primary state sources. Seven of these publish PDF tables; the pipeline runtime now bundles pdfplumber, so all 33 states — including NJ from batch 1 — sync monthly. Minnesota is the one newly-confirmed dead end (Radware captcha on the DHS page); Oregon stays deferred (names-only SharePoint list). Only remaining unbuilt states are the five blocked ones (MA, NH, MN, ME, FL) and thin OR.
- **State Medicaid exclusion lists — 21 states, 77,099 records** — new `state_exclusions` table loaded from each state's primary public source (CA 22.5K, TX 13.4K, NY 9.0K, PA 6.7K, LA 5.9K, MI, NJ, AR, OH, AL, MD, SC, KY, CO, MO, WA, MS, ND, MT, IN, TN). These lists are additive to the federal OIG LEIE: 69.8% of the 11,286 distinct state-excluded NPIs do not appear in LEIE at all. Records with a valid NPI also materialize into `license_disciplinary_actions` (visible in `/licenses/{npi}/disciplinary` and `/licenses/alerts/recent`); rows a state marks as federal-OIG mirrors are flagged `oig_reciprocal` and excluded from that materialization to avoid double-counting. Each state is a registered source (`{st}_medicaid_exclusions`) with independent load history at `/sources`; 20 states sync monthly in the pipeline (NJ's PDF source loads via script until the Lambda bundles a PDF parser). NPI handling is conservative: state-published NPIs only, validated by check digit — no name matching.
- **`facility_affiliations` on DAC provider records and the `/provider/{npi}` dossier** — all facility types a clinician is affiliated with (hospital, home health, hospice, nursing home, dialysis, IRF, LTCH), with CCN and facility type. The existing `hospital_affiliations` field keeps its shape and now carries hospital names joined from our facilities data.
- **Authorized Official employment signals** — every NPPES Type 2 organization names an Authorized Official; when that name uniquely matches exactly one individual NPI nationally, an attribution signal now links the two (687,084 signals, source `nppes_authorized_official`, confidence 0.60). Signals carry a new `employer_npi` identifier field — the first signal source whose employer is identified by NPI rather than EIN or PAC ID — visible in `/provider/{npi}/employment.attribution_signals[]`.
- **License-state corroboration signals** — 1.24M signals (source `nppes_address_match`, type `state_license_address`, confidence 0.70) marking providers whose active license state matches their PECOS employer's primary state. This signal class existed in code but had never successfully emitted — its signal type was never whitelisted and its upsert broke when the license natural key changed; both fixed.
- **Extend an approved label to another code.** When a pending label in the admin label queue marks the same words (same section, span, quote hash, kind and marker, and neither label has a related code) as an approved label, the queue shows the approved label and its codes, and one action (the "Extend approved label" button, or key `e`) adds the pending label's codes to it and merges the pending label into it. The approved label's approval and words do not change. The coder's email and an audit note are recorded.
- **Labels are code-independent: one label for CMS's words, and a list of the codes it applies to (migration 227).** A document shared across codes, such as article A55426 (DMEPOS standard documentation requirements), was labeled once per code: the same span, one pending label per code, four approvals for the same words. New table `w3_label_code` (label_id, hcpcs, added_by, source_label_id) lists the codes each label applies to. It is backfilled with every label's own code, and an insert trigger adds the new label's code (plus, for a re-anchored copy, its source's codes). New columns `w3_label.merged_into_label_id`, `merged_at` and `merged_by`, and a new approval_status `'merged'` (a check constraint keeps them consistent). The view `w3_label_for_code` has one row per label and code, leaving out merged labels. The receipt, KB, queue, counts and change-feed readers that filter by code now read the view or the mapping, so one approval serves every code the label applies to. Queue items list `codes`. A merged label cannot be decided (409, "merged into label N"). The label decision accepts optional `seen_codes`, the codes the reviewer saw the label apply to: when they differ from the label's codes now, it answers 409 and writes nothing (the admin queue sends them and says the codes changed). A client that sends no `seen_codes` is not checked. A decision and a code insert (propose, dedupe) lock the label row, so they serialize.
- **`scripts.w3.dedupe_labels` collapses duplicate pending labels without deleting any.** Labels at the same span, quote hash, kind and marker that still await a first decision collapse onto the oldest one. The duplicates' codes join it (`source_label_id` names each one), and each duplicate becomes `merged` with a pointer to it. Approved, rejected, needs-changes and re-review labels are never merged and never chosen as canonical, so a pending label never joins an approval for another code. Nor is a label that is a carry candidate: the same code already has an approved label with the same words, which the daily re-anchor carries for that code alone. Those spans, and spans whose kinds differ, are reported. Dry run by default; `--apply` runs under its own advisory lock and the re-anchor's (the lock propose_labels also takes), so the three label writers run one at a time; idempotent. It prints pending per code before and after.
- `scripts.w3.propose_labels` labels shared words once. When a pending, never-approved label already marks the exact span for another code, the new code is added to it (`mapped-onto-shared=`) instead of inserting a second label. A span already held for the code, through its own code or the mapping, is skipped.
- The admin label queue tags a label shared across codes "applies to E0601, K0001, ..." so the coder knows that one approval covers every listed code. The daily re-anchor's carry onto a pending label (#748) skips a label shared with other codes: an approval carried for one code never approves it for others.
- **`scripts.w3.propose_labels --reanchor` places spans taken on a rendering that has no section registration.** Some versions register their sections only on a later rendering (text 2.0.0 from `rerender_text_v2`), while their requirements were extracted from the first one (for example the coverage-JSON 1.2.0 text of Article A52465 v72), so those spans were reported unplaced. With `--reanchor`, the requirement's stored quote must still equal its own rendering, and it must then occur in the version's serving registration verbatim, character for character, exactly once, inside one section. Only then is a new pending label written there, with offsets on that rendering and `proposed_by` `reanchored:w3_requirement:<id>`. Quotes not found, found more than once, or straddling sections are listed and skipped. Nothing existing is changed. A store read error writes nothing. A new `--doc` flag scopes a run to one document, and every apply takes the same advisory lock as `reanchor_labels`.
- **Competitive bidding in the warrant.** `warrants.competitive_bidding` states what the held CBIC files show for the code on the date of service, per round in force: the round and its contract dates (CBIC's or CMS's quote), the code's product-category row, and the held ZIP file with the date range it answers. Each file is cited by its archived version and sha256. The block takes no beneficiary ZIP, and none reaches the API. Where the answer turns on the ZIP, the round says `zip_checked_by_caller` and names the held ZIP file (`zip_file`, with a link to its bytes) to check the ZIP against. `status` is `ok` only where the held files show the contract-supplier requirement did not apply (`basis`: `no_round_in_force` or `code_not_in_awarded_category`). Otherwise it is `unknown` with a reason. The exemptions are not evaluated. A block that is not `ok` is not weighed in the confidence rollup. The MCP `warrant` tool returns the same block.
- **The warrant says whether each HCPCS modifier was valid on the date of service.** When a request names `modifier` or `modifier2`, the new `warrants.modifiers` block has one item per modifier: `valid`, `not_valid` (`terminated`, `not_yet_effective`) or `unknown` with a reason, by the same rule as `warrants.code`. Each item quotes CMS's own `ADD_DT`, `EFCTV_DT`, `TERM_DT` and `ACTN_CD` from the modifier records of the HCPCS file in force, gives CMS's description of the modifier with `description_citation` (the file the description is quoted from), and cites the file that decides. A CPT modifier (digit first) answers `unknown` with `license_scope`, and input that is not a modifier answers `not_a_modifier`. Until the modifier records are parsed, each Level II item answers `not_yet_available`, and the confidence summary does not weigh the block. The weekly HCPCS parse now also parses the modifier records.
- **Timely filing in the warrant.** `warrants.timely_filing` quotes CMS's words for the claim filing time limit on the date of service. It quotes 42 CFR 424.44(a) from the version in force on that date, with its receipt and span. The Claims Processing Manual ch.1 section 70 is held for now (`manual_reason: text_not_servable`) until its stored rendering is verified to keep CMS's word order. A 2015 or 2016 annual CFR edition serves only on its own date (October 1), marked `text_as_of`. The block quotes the rule; it states no deadline and never says a claim is on time. When no version or rendering is held, the block says `unknown` with a reason, and the confidence rollup does not weigh it.

### Changed
- **The admin pipeline page lists the CMS CBP gap page under the daily schedule.** Its per-schedule source counts now match the pipeline schedules, and a test keeps them in step.
- `POST /v1/subscriptions` accepts CPT codes in `codes` (five digits, or four digits and F, T, U or M), beside HCPCS codes. It also accepts a range such as `99281-99285` and expands it. A subscription still watches at most 50 codes. A watch email fires for a code only when a tracked document maps to that code.
- The weekly digest email no longer lists each changed DME MAC web page for a reader who chose no source and watches no code. It shows one line per DME MAC source with the count of changed pages and the start date of the window, and links the feed. A reader who names a source, or watches a code, still gets the pages. Webhooks are not changed.
- Each entry of a digest or a watch email has a new layout: the title, then the reference, version and effective date, the codes, the quoted note, the source link, and the receipt (the sha256 and a link to the list of versions). "cited by warrants for" is now "Codes:". Each section is headed by the name of the source. A long title is cut at 200 characters.
- On updates.verzi.health, MAC web pages (the DME, A/B and HHH contractor sites) sit behind their own chip, "MAC web pages". The other news chips, "All sources" included, no longer list them. The RSS link on the page, and the feed an RSS app finds from the page, follow the same rule.
- A change alert signup that changes only the frequency says so in its confirmation email: the reader already has the other subscription with the same choices, confirming adds this one, and the unsubscribe link in one of its emails stops a subscription.
- `POST /v1/subscriptions`: a 422 for a code or source that is not valid shows at most 40 characters of the item that was sent.
- `POST /v1/subscriptions` refuses a state choice when Medicare is the only payer chosen. A state choice covers state Medicaid sources, and the confirmation email says so.
- The digest signup on updates.verzi.health and its confirmation email use plainer words: "DME MAC page changes", a note that Medicaid tracking is partial, and "(state Medicaid sources we track)". `POST /v1/subscriptions` explains a refused state choice in plainer words.
- The weekly digest lists what is new since the reader's last email (at most 14 days back), not a fixed 7 days. The same rule applies to every email, so no change reaches a reader twice. A reader who confirmed recently gets what is new since confirming. A first capture whose publisher date is up to 14 days old now counts as news in the weekly digest, as it already did in the daily email.
- Employer labels for 34 more anesthesia groups, found by a review of the 100 largest unlabeled groups. New PE-backed groups: 3 under US Anesthesia Partners, 4 under TeamHealth, 1 under National Partners in Healthcare and 1 under Sound Physicians. 11 Florida and Arizona groups are now labeled Envision (staffing). Other groups are labeled as hospital, academic or independent where a public source or the NPPES record states it.
- Employer labels: Essential Anesthesia Management (EmergencHealth and YPS Anesthesia, Varsity Healthcare Partners) and Anesthesia Dynamics (The Edgewater Funds) are now PE-backed platforms, each with its source. The 13 Premier Anesthesia state groups are labeled as staffing under Jackson Healthcare. Premier states it is privately held and free from private equity.
- About 50 more anesthesia group entities now roll up to their platform. The platforms are NAPA (with the former American Anesthesiology groups), NorthStar Anesthesia, National Partners in Healthcare (with MedStream), and USAP (Kansas and Tennessee).
- Each changed row's `notes` names its ownership source. A row matched by an entity naming convention has `match_method: name_pattern` and `confidence: medium` or lower.
- Vituity is now `physician_partnership`, because physicians own it.
- Envision is now `staffing`, because its lenders own it since the 2023 restructuring.
- USAP stays `pe_platform`. Its note says the PE investors hold a minority.
- **The MCP endpoint is `https://mcp.verzi.health/mcp`.** The root of `mcp.verzi.health` is an alias for it (Streamable HTTP). A browser that opens the root gets a short page with the config to connect. `https://api.verzi.health/mcp/` and a bare `/mcp` keep working, now with no redirect.
- The applicability warrant no longer quotes the PIM chapter 5 section 5.2.6 sentence. The text rendering of the PIM PDF is not verified to keep CMS's word order. The `authority` entry keeps its document, version, file, rendering hash and span, and says `text_withheld: "rendering_not_in_document_order"`. The verdict does not change. For a code with no served exemption, `applies` stays null with `no_cms_statement_held`. The quote returns when the PDF renderer is verified.
- **The applicability block quotes CMS's whole refill-scope sentence.** The `authority` entry in `warrants.applicability.basis` now quotes the full PIM chapter 5 section 5.2.6 sentence that sets the scope of the refill rules (for example "Per 42 CFR 410.38 related to DMEPOS products that are supplied as refills to the original order/prescription, suppliers must contact the beneficiary prior to dispensing the refill ..."), with its `span` in the stored rendering. Before, it quoted only the phrase "supplied as refills to the original order". The quote serves only where the receipt's license rule allows it. Otherwise the entry carries `text_withheld` `license` and keeps its source proof. The sentence is a fact in force on the date, not a verdict. `applies` stays null when no held CMS sentence states one.
- **The refill applicability reason names what is missing.** When `warrants.applicability` answers `unknown` (`reason_code` `no_cms_statement_held`), its `reason` now says that a cited answer needs an approved Verzi coder label (kind `refill_exempt`) on a section of an LCD or Policy Article in force on the date of service whose own words exempt the code. The text is the same for every code. `status`, `reason_code` and `applies` do not change.
- **Refill applicability answers only where CMS states it (strict verbatim).** `warrants.applicability` gives a verdict only when a held CMS sentence states it for the code. Today that is a served LCD or Article passage whose own words exempt the code from the refill rules. It answers `applies` false and `completeness` `cited`. The first basis entry is that passage's source proof (`doc_id`, `version_id`, `render_sha256`, `span`).
- The exemption passage's `quote` carries CMS's words only where the receipt's license rule allows the span: any span of a public-domain source, or a span inside a narrative section of an LCD or Article. A span with licensed code text inside it serves no quote. Otherwise the entry carries `text_withheld` (`license`, or `unavailable` when the rendering cannot be read). The words stay reachable at `/warrant/receipt`.
- Every other code and date answers `status` `unknown`, `reason_code` `no_cms_statement_held` and `applies` null. Verzi no longer maps a payment category, an HCPCS descriptor or a code letter to a verdict, so `proxy_only` no longer occurs.
- The basis still lists CMS facts in force on the date: the payment category as the fee file states it (no Verzi label) and the PIM chapter 5 section 5.2.6 refill rule. Removed: `basis[].label`, `basis[].tiebreaker` and the exemption's `requirement_text`.
- The confidence rollup does not weigh an applicability block with `no_cms_statement_held`, as it already does for the exclusion warrant's `none_served`.
- In `/rules/warrant/changes`, the applicability block's `changed` is `null` unless both dates carry a cited verdict. A block with no CMS statement held on either date does not count toward `any_change`.
- `GET /archive/files/{sha256}/text` no longer serves the text of an archived HTML page or PDF, such as a CMS manual chapter, a transmittal or a DME MAC page. The text rendering of these files can put the publisher's words out of order. The answer has `text: null`, `text_withheld: "rendering_not_in_document_order"`, the file's receipt and the link to the original bytes. CFR XML text still serves.
- `GET /warrant/receipt` serves no passage from those same files, for the same reason. It answers `found: false` with `withheld: "rendering_not_in_document_order"`. Receipts for LCD and Article passages are unchanged.
- The KB code page no longer shows the whole text of an in-force LCD or Article with no approved label, for the same reason. It shows the version, its receipt and CMS's copy. The fidelity gate checks the approved passages against CMS's word order, so they still show.
- **A new capture of a Medicare Coverage Database page whose policy sections are unchanged no longer adds a version.** The bytes are still stored. Only page furniture (the version-history panel, help text, scripts) had differed. Two captures of one version that already exist are kept, and the later one serves.
- **The API can run on AWS.** ECS Fargate behind one load balancer is defined in Terraform and deployed by a workflow that stays off until `AWS_DEPLOY_ENABLED` is set. Callers still use the current hosts. See `docs/AWS_RUNTIME.md`.
- **A Stripe subscription turns the paid plan on and off.** When any of an org's Stripe subscriptions is active or trialing, the org's paid flag is on. That flag opens the KB paid view today; the signed-answer gate follows in a later change. When none is, past_due or incomplete keeps the flag, and canceled, unpaid, incomplete_expired, paused or deleted turns it off. A discounted subscription counts the same as full price. Only the org whose Stripe customer matches changes, so a manual grant on another org stays. Every change is written to the org access audit. When Stripe cannot be read, nothing turns on: the webhook answers 503 and Stripe sends the event again.
- **Checkout accepts a promotion code.** The Stripe checkout page for Starter and Pro has a promotion code field. A discounted subscription turns on the paid plan the same as full price.
- **The plan tier follows Stripe's prices.** When a subscription ends, the org's tier is the highest tier among its remaining active, trialing or held subscriptions, read from their Stripe prices. With none left, the tier is free. A price that maps to no tier reads as Starter, never above the org's current tier. An Enterprise tier is not lowered while a subscription is still held. A checkout never sets a tier below another active or held subscription.
- **The CMS competitive bidding page is now captured every day, not every Monday.** The competitive bidding line on a receipt says "no round in force" only for a date of service on or before the last day the page was read live, so a weekly read left up to six days of recent dates of service as unknown. It now runs with the daily 11:00 UTC schedule, and the archive ledger flags it after a day and a half without a good run. Archive manifests accept `cadence: daily`.
- **`GET /v1/rules/receipt/changes` and the MCP tool `receipt_changes`, text only.** With `payer=medicaid` and a claim type that is not started, the answer carries a `note` that says this route compares claim type `dmepos` only (`r2_mue` and `r2_ptp`). For a payer that is not served, `not_served` names the hospital outpatient blocks (`r1`, `r2_mue`, `r2_ptp`, `rule_passages`) when outpatient is asked for and `dmepos` is not. No block is read in either case, as before.
- **`GET /v1/rules/receipt/changes` and the MCP tool `receipt_changes`, for a payer that is not served.** With `claim_type=outpatient` (or `claim_format=institutional`), an input the outpatient timeline does not take (`state`, `cba`, `rural`, `modifier`, `modifier2`, or a `setting` other than `outpatient_hospital`) is now refused with the same 422 as for Medicare; it was a 200 before. For a claim type this route has no timeline for, `not_served` is empty and the `note` says so; it named the DME blocks before.
- **`GET /v1/rules/receipt` and the MCP tool `receipt`, for a payer that is not served.** With `claim_type=outpatient` (or `claim_format=institutional`), an input the outpatient receipt does not take (`state`, `cba`, `rural`, `ordering_npi`, `beneficiary_state`, `icd10_offset`, `icd10_limit`, a filter, or a `setting` other than `outpatient_hospital`) is refused with the same 422 as for Medicare; it was a 200. A request with none of those is answered as before, and the `setting` it echoes in `query` is now `outpatient_hospital`; it was `dme_supplier`.
- **`GET /v1/rules/receipt/changes` and the MCP tool `receipt_changes`, with `payer=medicaid` and `claim_type=outpatient` (or `claim_format=institutional`),** refuse a `setting` other than `outpatient_hospital` with the same 422; it was a 200 (`not_started`).
- **Error text, same requests.** For a payer that is not served on `GET /v1/rules/receipt`, and for `payer=medicaid` on `GET /v1/rules/receipt/changes`, and on their MCP tools, with `claim_type=outpatient` (or `claim_format=institutional`): a `setting` that is not one of the known settings was already a 422, and its detail now reads "setting '...' does not fit claim_type outpatient ..." where it read "setting must be one of ...". A client that matches on the old text should match on the status code.
- **The public contact address is hello@verzi.health.** The docs pages (home, quickstart, privacy, terms, data disclosure), the accuracy and usage pages, the dashboard homepage and footer, and the MCP metadata (server.json, Smithery listing, OAuth pages and resources) now show hello@verzi.health. It replaces adrian@verzi.io, dev@verzi.health (which had no mailbox) and api@verzihealth.com. Contact form routing (CONTACT_TO) and the archive bot User-Agent are unchanged.
- **`claim_format=dental` now asks for the `dental` claim type.** Medicare's format for dental claims is now verified as `dental`: the 837D or the 2024 ADA claim form, from CMS's "Medicare Dental Coverage" page. On `/rules/receipt`, `/rules/claim-fields` and the MCP `receipt` and `claim_fields` tools, `claim_format=dental` answers for the `dental` claim type, with `claim_type_status: not_started` and the usual reason. It no longer answers "not verified". `meta.claim_format` for `claim_type=dental` is now `dental` instead of `check`, and `claim_type=dental&claim_format=dental` is a valid pair.
- **ABN form editions by date of service.** The claim-fields ABN attachment now treats the ABN form CMS-R-131 (Exp. 01/31/2026) as valid through 2026-05-11. From 2026-05-12 only the Exp. 03/31/2029 edition is valid (MLN Connects, 2026-03-19). Before this change, both dates were one day late.
- **Data dictionary lists `ncd_section_number`.** The published data dictionary now includes the table that records the NCD Manual section number each archived NCD version states (migration 226), regenerated from production.
- **The data dictionary lists `w3_label_code` and the merge columns on `w3_label`.** It now covers the table of the codes each label applies to and `w3_label.merged_into_label_id`, `merged_at` and `merged_by` (migration 227), regenerated from production. Only the w3_label rows of the generator output are taken: a cmsadmin read would also have refreshed row counts of tables the usual cms_loader read cannot see. The `dme_mac_lcd_article_history` catalog work row is done: the labels shared across codes were collapsed on prod on 2026-10-25 (442 merged, pending 1,582 to 1,140 distinct labels).
- **The data dictionary no longer publishes customer row counts.** Tables about our own customers and their use of the service (accounts, organizations, sign-ups, sessions, logins, audit trails, request logs, usage rollups) keep their schema in the dictionary, but their row count shows as "withheld" and is never read or added to a total. The dictionary was regenerated in full from production as the `cms_loader` role (which cannot read every table), so its header now describes the whole file.
- The developer landing page now describes labels accurately. A small set of approved labels for E0601, K0001 and E1390 was approved by Verzi Health staff, and coder review is in progress. When a label has passed a double check by two independent automated reviews, a receipt can show it separately and clearly marked, as not yet reviewed by a coder.
- `GET /v1/rules/receipt/changes`, DME (`claim_type=dmepos`): `r1_fee`, `r2_mue` and `r2_ptp` now compare every CMS value the block serves, and not the file. Fee: allowed amount, ceiling, floor, category and jurisdiction. MUE: value, MAI and adjudication rationale. PTP: modifier indicator, effective date, deletion date, the pre-1996 flag, rationale, and a deletion date that a later CMS file back-dates. These files are posted per quarter. Before, every pair of dates in two quarters read as a change, also when the values were the same. DME now gives fewer `changed: true` answers. Each side still cites its own file. A fact that appears or disappears is still a change, and an unknown side is still null.
- `GET /v1/rules/receipt/changes`, outpatient (`claim_type=outpatient`): `r2_ptp` now reports a scheduled deletion of a PTP edit, also one that a later CMS file back-dates, and `r2_mue` now reports a change of the MUE rationale. Before, both read as no change when the other values stayed the same.
- Text values such as the rationale compare as the exact string CMS published. Dates compare as dates.
- **The docs home no longer says documentation labels are approved for E0601 and K0606.** The KB shows no approved Verzi label on any code today; the page now says the labels are in progress. The appeal exhibit is described as coming once a code's labels are approved.
- **The docs home examples use the receipt and the source archive** instead of the provider dossier and OIG exclusion endpoints. The TypeScript sample uses `fetch`, not the design-partner SDK.
- **Pricing tells one story everywhere:** a free key covers the source archive and the catalog; signed answers and the full CMS text are a paid plan, granted per account during the private beta; contact us for access and pricing.
- **The SDK link is gone from the docs nav and footers.** The marketing site (verzi-health-web #32) now 301s `verzi.health/sdk` to the docs.
- The signup form's product choices read "The free key: the source archive and the catalog" and "Signed answers for coverage and coding (paid)". The submitted values are unchanged.
- **Design partners get 90% off the KB and the API, including the signed receipt, for 12 months, then the regular price.** The offer is open to the first 3 partners and replaces "12 months free". The discount is a Stripe promotion code at checkout, so the paid flag comes from a real subscription. The quickstart and the pricing page say: "Design partners get 90% off the KB and the API, including the signed receipt, for 12 months, then the regular price. The offer is open to the first 3 partners."
- **The API reference at `/docs` and `/redoc` shows Verzi Health's own endpoints.** It lists the source archive, rules and receipts, provider standing, the DME code check, the source catalog, the provider dossier, and health and platform meta, under the `/v1` base URL. The spec it reads is at `/docs/openapi.json`. The provider-data endpoints still work, and `/openapi.json` still lists every endpoint.
- **The docs home has four new sections: authentication, rate limits, versioning, and free tier and testing.** They give the same facts as verzi.health/api: `X-API-Key` for REST, OAuth or an API key for MCP, the free-key and keyless limits and their headers, the `/v1` contract with `Deprecation` and `Sunset` headers, and how to test without a sandbox.
- **The docs home says the TypeScript SDK is available to design partners on request.** The sample no longer reads as if `@verzihealth/sdk` were published. It is not on npm yet.
- Employer labels: Essential Anesthesia Management's EmergencHealth group is now medium confidence (its source names the platform, not the group). The second Anesthesia Dynamics entity is marked as a name match.
- **`GET /rules/dmepos/fee`: an area string the fee schedule does not carry is a 422 that lists the valid strings.** Before, `cba=Salt Lake City` answered 404 "No fee cell for that key and date", while the file carries `Salt Lake City, UT`. Now a `state` or `cba` value that no fee cell carries answers 422. The detail has `message`, `valid` (every area string the fee cells carry for that area type, sorted) and `nearest` (the valid strings that contain the given one or are contained by it, case-insensitive), when any exist. A lower-case state such as `ut` still passes.
- The healthcaredata.io homepage now sends visitors to verzi.health. The dashboard pages on www.healthcaredata.io (search, NPI profile, benchmarks, scorecard, hospital profile, exclusions) stay, and sign-in now lands on Search.
- **Illinois Medicaid coverage and Michigan Medicaid fee files are now marked licensed.** The Illinois HFS handbook page shows the ADA CDT end-user license, and the Michigan MDHHS DME page states that CPT codes and descriptions are copyright AMA. `il_medicaid_dme_coverage` and `mi_medicaid_dme_fees` move to `state_ama_ada_terms`: no link to their bytes, no full text; sha256, publisher URL and extracted facts are unchanged.
- **KB HTML names verzi.health as the canonical page when that site publishes the same LCD or HCPCS code and the page is showing the version in force today.** `/kb/lcd/33718` and `/kb/code/E0601` point at `https://verzi.health/lcd/l33718` and `https://verzi.health/codes/e0601`, in the `Link` header and in `<link rel="canonical">`. An older revision keeps `vid` and stays on `https://kb.verzi.health`. A KB page with no site page, including a policy article, names the clean `kb.verzi.health` URL. JSON responses are unchanged.
- KB code pages (`/kb/code/{hcpcs}`) load faster for a visitor with no cookie and no API key. The page is kept for up to 5 minutes for each code, date of service, LCD and version. The page is kept per day (US Eastern), so a new day shows that day's answers. A signed-in reader, a request with an API key, and a request with any cookie always get a fresh page.
- KB code pages send a `Server-Timing` header with the milliseconds of each build stage.
- **The free E0601 page is served from a 5-minute cache.** A visitor with no KB sign-in and no API key gets the page from the cache when the URL has only `dos` and `vid`. A new CMS version shows within 5 minutes. The response carries `X-KB-Cache: hit` or `miss`. Signed-in readers and keyed callers always get a fresh page.
- KB sign-in: the code page now says what to do when no code arrives: check your spam folder, then request a new code.
- **"Today" is no longer the server's UTC date.** `/v1/check` with no `dos` uses today's US Eastern date and says so: `date_of_service_source` is `default_today_us_eastern` (or `given`), and the page reads "(today, US Eastern time)". A KB page says which date "today" is. It renders for the US Eastern date, and a browser with another local date moves to its own date. "Generated" times show in the reader's local time. The change feed's "Takes effect" titles and the upcoming-changes calendar use the US Eastern date too; feed timestamps stay UTC with their zone.
- **Search crawlers and the KB.** Googlebot and Bingbot, verified by forward-confirmed reverse DNS of the client address (never the User-Agent alone), are no longer held to the per-IP KB page limit. Each crawler has its own bucket, 300 requests a minute by default (`KB_CRAWLER_RATE_LIMIT`), named `crawler:google` or `crawler:bing` in the `RateLimit-Policy` header. A request that claims to be a crawler and fails the check keeps the normal per-IP limits.
- **KB edge caching.** Signed-out KB HTML pages answer `Cache-Control: public, max-age=60, s-maxage=300, stale-while-revalidate=600` with `Vary: Cookie`. Every other `/kb` response (signed in, with an API key, setting a cookie, an error, JSON, sign-in) answers `Cache-Control: private, no-store`.
- **A protected MCP call with no credential asks for `receipts:read`.** That is the scope a paid tool needs, so the first sign-in can call it. A client can still ask for `providers:read` on its own.
- **The MCP `receipt` and `receipt_appeal` tool schemas state the `payer` length limit.** The `payer` parameter carries a pattern for 1 to 64 characters, and its description says "At most 64 characters". The tools already refused a longer value.
- **Counted REST responses carry the standard rate-limit headers.** A counted response includes `RateLimit-Limit`, `RateLimit-Remaining`, and `RateLimit-Reset` (seconds until the tightest quota resets), plus `RateLimit` and `RateLimit-Policy` for every quota on that request. `RateLimit` and `RateLimit-Policy` follow the newer IETF draft. `RateLimit-Limit`, `RateLimit-Remaining`, and `RateLimit-Reset` are the older draft. Both are sent on purpose. A `429` also carries `Retry-After`. This covers the public per-IP limits and the keyed daily cap, which still sends `X-RateLimit-Limit`, `X-RateLimit-Remaining`, and `X-RateLimit-Reset: midnight UTC`.
- **Anonymous MCP coverage tools are rate limited in the process that serves them.** A caller with no key is limited to 30 a minute and 500 a day per IP address. A signed-in caller without a plan that includes receipts has the same limits, keyed by user. A plan that includes receipts is not capped on these tools. Over the limit the tool returns a retry-after message. Each process counts on its own.
- **MCP receipt tool description names every section.** The `receipt` tool's description and the server instructions now say the receipt also covers the competitive bidding files, the claim filing time limit, and whether CMS's Required Prior Authorization List and its Required Face-to-Face Encounter and Written Order Prior to Delivery List name the code on the date of service. Text only; no change to the tool's inputs or output.
- **The MCP Registry manifest uses the current schema and the `health.verzi/receipt` name.** `api/mcp/server.json` follows the 2025-12-11 registry schema (camelCase fields, title, icons, repository id) and validates against the live registry. The name is proven by the public key at `https://verzi.health/.well-known/mcp-registry-auth`. The endpoint is still `https://mcp.verzi.health/mcp`. Support on the MCP surface and the listings is now hello@verzi.health.
- **The MCP transport is stateless, and `/mcp` does not redirect.** `POST`, `GET`, and `DELETE` on `/mcp` and `/mcp/` reach the server. There is no standing session: initialize stays a server-sent event stream, GET answers 405, and DELETE with no session answers 405. Listings use `https://mcp.verzi.health/mcp`. Support on the listings is hello@verzi.health.
- **State Medicaid fee schedule route.** Washington and Illinois fee schedules are filed as one document per schedule, so each edition ends when the next one starts. Both states carry a list of every edition known to exist. One Illinois edition states only the date the state updated it and is listed at that date. When an edition that started on or before the date of service is known and not held, the route answers `unknown` with `known_edition_not_held` and the start date of that edition, and never serves the earlier edition's rows. A state under license terms with nothing parsed now also lists its open documents that are not parsed.
- **State Medicaid fee schedule route.** The answer now carries `all_documents_read`: true when every fee document of the state that applied on the date of service was read. When it is false with `status` `ok`, a document is unknown or withheld and `rows` may be partial. A document that its publisher's own stated dates put out of force on the date is listed as `not_in_force` and no longer turns a real miss into `unknown`, as long as another edition of the same schedule was read. A state whose fee schedule is under license terms answers `withheld_license` whether or not its file is parsed. The route lists under the "Medicaid Fee Schedules" tag only. The response is typed in the OpenAPI file and the SDK (`MedicaidFeeResponse`).
- **The claim type sentence for `payer=medicaid`.** On `/v1/rules/receipt`, `/v1/rules/receipt/changes`, `/v1/rules/receipt/appeal` and their MCP tools, `meta.claim_type_reason` said "payer=medicaid is not served. The claim type fields describe no rule of that payer, and the Medicare crosswalk's progress is not shown in their place." next to blocks read from Medicaid sources. It now says "payer=medicaid is not served yet and is filled one block at a time. What was read from a Medicaid source is marked source_program medicaid. The claim type fields describe no Medicaid rule, and the Medicare crosswalk's progress is not shown in their place." The second sentence is left out when the answer holds nothing read from a Medicaid source. No key, status or `served` value changed. Other payers that are not served keep their sentence.
- **New Jersey Medicaid Medical Supplier Manual (N.J.A.C. 10:59) is held as licensed text.** The archived PDF is a LexisNexis copy whose every page carries a New Jersey Office of Administrative Law copyright. `nj_medicaid_dme_coverage` is still captured weekly and cited by URL and sha256, but its bytes and full text are no longer served.
- **New York Medicaid DME sources re-verified (2026-10-22).** The eMedNY DME fee schedule now has a parse mapping for its three header layouts (2007 to 2023, 2008, 2024 on). Codes, FEE, RENTAL FEE and By Report cells, the PA route code and MAX UNITS are kept as printed; descriptions are never stored. No New York fee rows are served yet: every published edition prints some codes on more than one row, told apart only by their descriptions. These editions are held back until the parser can key such rows. The fee history backfill is off because eMedNY's robots.txt now disallows its archive pages.
- **Ohio Medicaid DMEPOS fee schedule: the temporary 07/01/2021 pin is removed.** The 2021 edition was archived and parsed on 2026-10-22 (1,311 rows), so the weekly capture again fetches only the current edition.
- The state Medicaid fee schedules, rate files and provider manuals captured on 2026-11-13 and 14, and the Michigan and Washington DME coverage manuals, are now rechecked on a schedule: weekly for the largest programs (New York, Texas, Michigan, Florida, Ohio, Georgia) and monthly for the rest, so a state change shows up within a week or a month. The closed archives (North Carolina before November 2022, the Arkansas archive, Florida yearly history) are rechecked monthly too, and two Indiana fee sources (outpatient and the 2027 schedules) get their first capture on the monthly run.
- **Tennessee Medicaid DME coverage follows the current rule edition.** `tn_medicaid_dme_coverage` now finds TennCare rule chapter 1200-13-13 on the Secretary of State chapter index instead of a fixed file, so it captures the January 2026 revision and any later one. Before, it kept capturing the superseded June 2025 file.
- NADAC drug prices now refresh every Thursday, after CMS posts the weekly file. Before, the Monday refresh served prices up to one week older than CMS.
- **`years_covered` is filled when only CMS's summary has rows.** In the NPI profile, a `prescribing` or `utilization` block can have no per-drug or per-service rows (CMS suppresses the rows with fewer than 11 claims or beneficiaries) but still have `cms_summary` rows. Its `years_covered` now gives the first and last year of `cms_summary.by_year`. Before, it was null. The detail fields stay null.
- **Ohio Medicaid DME fee files are now marked licensed in prod.** The ODM workbook prints CPT 97542 with its descriptor. `oh_medicaid_dme_fees` moves to `state_ama_ada_terms` (migration 211): no link to its bytes, no full text; sha256, publisher URL and extracted facts are unchanged.
- The OIG exclusion list (LEIE) is now checked every day instead of weekly (archive) and monthly (exclusions table). OIG posts its monthly update on no fixed day, so new exclusions reach provider standing and the exclusion endpoints within a day of OIG posting them. The table reloads only when OIG has posted a newer file.
- `receipts.r0.ptan_on_dos` on an outpatient receipt states the gap for a provider. It no longer names a supplier or the DMEPOS supplier directory.
- Quoted text from a PDF is now served only when a second, independent extractor (pypdf) reproduces it word for word.
- Transmittal effective and implementation date texts in `/archive/docs/{doc_id}` (`inverted_window`) are null until a re-parse confirms them. The dates stay.
- CMS's DMEPOS Required Prior Authorization List is parsed again with every row (code, description, Effective Date) and header text confirmed. A list version with any unconfirmed text answers not determinable.
- The applicability warrant quotes the PIM chapter 5 section 5.2.6 sentence again, for the 30 verified renderings of that chapter. An extractor independent of pdfminer confirmed the sentence in each of them, word for word: the same words, in the same order, split at the same places (#565). Any other or newer rendering keeps the quote held, with `text_withheld: "rendering_not_in_document_order"`.
- **Documentation requirements now map every code CMS lists.** A code maps to the LCDs whose newest listed version in CMS's own code table names it, and to the Articles CMS relates to that version, as the KB code page already shows. Codes with no coder label yet (for example K0001, E0730, E0471, E0260, E0130) now serve the version in force with its receipt and, where the license rule allows, CMS's coverage indications text marked unlabeled. Verzi infers no mapping. The updates feed names the same codes under `affected_codes`.
- **Coder labels follow CMS to the version in force.** Once a day, each approved label on a superseded LCD or Article version is placed on the version in force. When CMS's words are byte-identical there (one exact occurrence, inside one section with the same heading key, the list marker unchanged), the approval carries and the label serves with a signed receipt for the new version. Any other label returns to the review queue as pending. The old labels are kept and still answer older dates of service.
- **R3 serves CMS's documentation-requirement and Policy Article text for unlabeled documents.** When a document in force has no approved coder label for the code, `receipts.r3` already served its Coverage Indications section verbatim. It now also serves the LCD's Associated Information section (and the Coverage API's Documentation Requirements field), where CMS states documentation requirements, and the related Policy Article's text, where CMS states the code-specific coverage, coding and bundling rules. CMS's words as archived, marked unlabeled, under the same license guards. Article A55426 (standard documentation requirements for all DME MAC claims) stays cited without its text. Documents with approved labels are unchanged. The free `/check` answer names these sections too, without text.
- **Rate-limit headers on every API response.** Every REST response now carries the IETF `RateLimit-Policy`, `RateLimit`, `RateLimit-Limit`, `RateLimit-Remaining` and `RateLimit-Reset` headers, including 401 and 404 answers. A keyed request reports its key's daily quota. A request with no key reports the keyless quota, 120 requests per client IP per minute, and counts against it. A keyless caller over that quota gets `429 Too Many Requests` with `Retry-After`. Health checks, CORS preflights, static files, OAuth and the MCP endpoint are not counted.
- **CMS sections that cite a CPT code now serve, minus that paragraph.** In `receipts.r3`, an unlabeled LCD or Policy Article section that holds a CPT-shaped code token used to be withheld whole (`text_withheld: licensed_text`). Now only the paragraph with the token (and a neighbouring line that may carry the AMA's descriptor) is left out, replaced by "[Paragraph with CPT text owned by the AMA, not shown]", and the section lists a redaction `{"reason": "ama_cpt", "span": {"start", "end"}}` naming the left-out span of the cited rendering. Every other paragraph is CMS's text as published. `R3Redaction` gains `span`. The AMA's CPT descriptor text is still never served.
- **Denial labels D12, D21, D26 and D47 read as the receipt crosswalk now words them.** On `/rules/receipt?denial=` and the MCP receipt tool, `meta.denial.title` for these four rows gives the claim-type-neutral wording, followed in brackets by the form's or DME's own wording: D12 "Claim sent to the wrong contractor (DME: the wrong DME MAC for the beneficiary's state)", D21 "Another payer is primary, or the other-payer data is missing (CMS-1500: item 11 not completed)", D26 adds both "(CMS-1500: ...)" and "(DME: ...)", and D47 ends "(CMS-1500: both or neither sex box checked)". Every other field, block and label is unchanged, and the receipts still serve DME claims only.
- **Crosswalk rows for other-payer data, the ABN and the oxygen CMN no longer say "not held".** The MSP manual (Pub. 100-05), Claims 100-04 ch. 26 and ch. 30, the ABN form and its instructions, and CMN form CMS-484 are in the archive. On `GET /rules/claim-fields` and the MCP `claim_fields` tool, CMS-1500 items 4, 10a to 10c and 11 and the ABN, oxygen CMN and primary payer EOB attachments now report `not_linked` instead of `not_held`. So do denial rows D18 and D21 in the receipt's crosswalk labels. Verzi holds these sources, but the receipt does not quote them yet.
- **A document's receipt names the rendering its sections cite.** In `receipts.r3`, an unlabeled document's `receipt.render_sha256` is now the hash of the rendering that its section citations point into, and the new `receipt.renderer_version` names the renderer that made it. For a version re-rendered with text renderer 2.0.0, `capture_render_sha256` and `capture_renderer_version` name the rendering made at capture. It stays stored, so receipts issued before still check.
- **`/rules/receipt` serves the full approved quote for keys with the receipt capability.** In `receipts.r3`, every approved coder label now carries its `passage_text`: CMS's words at the label's `quote_span`, the same text the KB code page and the MCP documentation tool serve. Before, only one item did (the free sample). Labeled sections still carry no `section_text`, unlabeled documents no `document_text`, and licensed text is still withheld (`text_withheld`) or blanked (`redactions`). The MCP `receipt` tool answers the same way. A caller without the capability (local dev with auth off) still gets the one sample item, marked `sample`.
- **Face-to-face / WOPD answers for dates of service before the held CMS list.** Verzi Health holds one edition of CMS's Required Face-to-Face Encounter and Written Order Prior to Delivery List, effective 10/28/2026. For an earlier date of service, `receipts.face_to_face_wopd` used to answer `not_determinable` for every code. It now reads the held update statements of Noridian Healthcare Solutions, the DME MAC for jurisdictions A and D. If a statement names the code with an effective date on or before the date of service, the answer is `listed`. If the statement's date is after the date of service, the answer is `not_listed` only for a date of service on or after the effective date of the next-earlier held statement (2026-04-13 for the October 28, 2026 statement), and never before the Required List's first effective date (2020-01-01). A statement of codes added on a date settles only the list edition in force just before that date. For an earlier date of service, or when no earlier statement is held, the answer is `not_determinable`, with the statement quoted and a reason that says so. Both answers carry `answer_source: "dme_mac_statement"` and `completeness: "contractor_statement"`, which the confidence rollup grades partial. `contractor_statements` quotes Noridian's sentence and code line with a source proof for each (doc_id, version_id, file_id, sha256, render_sha256, character span). An answer from a CMS list edition carries `answer_source: "cms_list"`.
- Example: E1390 on 2026-10-25 is `listed`, from Noridian's statement "Effective April 13, 2026, Medicare selected additional HCPCS codes that require a face-to-face encounter and Written Order Prior to Delivery (WOPD):". L1833 on 2026-10-25 is `not_listed`, from the statement effective October 28, 2026. L1833 on 2026-04-12, and E1390 on 2021-06-01, are `not_determinable`.
- When no held source settles the date, the block still answers `not_determinable`. Its `reason` now names every source checked and what each lacks, and `sources_checked` lists them. Example: E0601 before 2026-10-28. The block also fails closed when the statements disagree (`not_determinable_kind: "sources_disagree"`) or when a checked page or quote cannot be read or its word order cannot be verified (`"source_unreadable"`). The KB code page line says when its answer is the contractor's statement and not CMS's list.
- **Face-to-face / WOPD answers from the older CMS list editions.** Verzi Health now reads every held edition of CMS's Required Face-to-Face Encounter and Written Order Prior to Delivery List: 04/13/2022, 04/17/2023 (two copies), 08/12/2024, 04/13/2026 and 10/28/2026. Before, only the 10/28/2026 edition was read. `receipts.face_to_face_wopd` now answers a date of service from 2022-04-13 on from the CMS edition in force on that date (`answer_source: "cms_list"`). For example, L1833 is `listed` on 2022-06-01 and 2023-06-01 and `not_listed` on 2024-09-01. E1390 is `listed` on 2026-05-01 and 2026-10-25. E0601 and K0001 are `not_listed` on all of these dates.
- The 2022 and 2023 editions print the list in two sections: "DMEPOS ITEMS (NON-POWER MOBILITY DEVICE CODES) ADDED TO THE REQUIRED FACE-TO-FACE ENCOUNTER AND WRITTEN ORDER PRIOR TO DELIVERY LIST" and "POWER MOBILITY DEVICES, REQUIRING A FACE-TO-FACE ENCOUNTER AND ORDER PER EXISTING STATUTE". `list_entry.parse_note` quotes the heading a code is listed under. A `not_listed` answer from one of these editions quotes both headings. A list edition that prints only one of the two sections never gives `not_listed`: the answer is `not_determinable` with `not_determinable_kind: "partial_list"`.
- Noridian's DME MAC statements are now read only for dates of service before 2022-04-13, or when the CMS edition in force states a later date.
- **Receipts quote more CMS manual sections for DME denial rows.** `receipts.rule_passages` now reads PIM chapters 3 and 4, Benefit Policy chapter 15 and Claims Processing chapter 26, besides Claims chapter 20 and PIM chapter 5. No receipt answer changes on the day this ships: a section from a manual PDF serves only when an independent pdftotext check matched that exact span word for word. The receipt says so in `document_order`, with the pdftotext mode that matched. The check runs after a capture that fetches a new chapter version, or in a hand run over the held versions. Until a span has a matched check it stays held, with its citation.
- **Section numbers follow CMS's current numbering.** PIM ch. 4 proof of delivery is §4.7.3.1 and §4.7.3.1.1 (formerly §4.26 and §4.26.1). PIM ch. 5 supplier documentation and evidence of medical necessity are §5.10 and §5.11. CMS-1500 items 14 to 33 are Claims ch. 26 §10.4, and item 12 is §10.3.
- **`GET /archive/docs/{doc_id}/section` reads the same four new chapters.** Before, they answered `chapter_not_supported_yet`. Now they answer with the chain, basis and citation. A PDF span there is still held (`rendering_not_in_document_order`).
- PIM ch. 3 §3.2.3 and §3.3.2.4, and Claims ch. 26 §10.4, stay held for now: pdftotext does not reproduce those spans word for word.
- **A passage labeled for one code but written for another now says so.** When CMS's words in an approved label are another code's requirement in the same document, receipts (`receipts.r3`), the KB code page passages and the MCP receipt tool mark the item with `related_code` and a plain `label_note`, and it no longer counts as the code's own requirement or its free sample. CMS's text and the approval are unchanged. First case: on K0001, L33788 v19's K0005 coverage criteria now show as related code K0005.
- **Breaking: the signed answer is a receipt.** Routes, MCP tools, OpenAPI fields, and JSON keys that said warrant now say receipt. Level labels in responses are R0, R1, R2, and R3 (`receipts.r0` through `receipts.r3`, plus `r0_ordering`, `r1_fee`, `r2_mue`, `r2_ptp`, `r3_requirements`). The block type field is `receipt_kind`. A citation object keeps the key `receipt`. The old public paths (`GET /rules/warrant`, `/rules/warrant/appeal`, `/rules/warrant/changes`, `/rules/warrant/signing-key`, `/warrant/receipt`, and their `/v1` forms) stay as hidden aliases: they answer exactly as the new route does, with the new JSON keys, and carry `Deprecation: true` and a `Link` header naming the successor path. They are not in the OpenAPI schema. Signup stores the product `receipt` (migration 204). The public key is `GET /rules/receipt/signing-key`. Source proof is `GET /source-proof`.
- **New captures use text renderer 2.0.0.** HTML pages and Coverage API documents captured from now on are rendered in the publisher's word order. Files captured before keep their stored 1.0.0 rendering, so every receipt already issued still checks.
- **Whole text from a 2.0.0 rendering now serves.** `GET /archive/files/{sha256}/text` and the KB code page serve the whole text of a rendering made with 2.0.0, where the source's license allows it. For a file that also has a 2.0.0 re-rendering, `/text` serves that one and names it (`render_sha256`, `renderer_version`), with the capture rendering's hash beside it (`capture_render_sha256`). Renderings made with 1.0.0 stay held.
- Request logs are now deleted after 90 days, as the privacy policy says. Daily usage counts stay.
- The privacy policy now says that we log the pages signed-in knowledge base users view, and that we may email you about Verzi products. Every such email tells you how to stop them.
- **The signed answer needs a paid plan.** `/rules/warrant`, `/rules/warrant/changes`, `/rules/warrant/appeal`, `/warrant/receipt`, `/provider/{npi}/standing`, `/rules/ncci/ptp`, `/rules/ncci/mue` and `/rules/dmepos/fee` (also under `/v1`) need a paid plan or a granted entitlement: the key's own flag, or an active organization with the plan. Without one they answer 402 with `error: capability_required` and an upgrade link. The source archive, as-of reads, the catalog, the public code check and `/rules/warrant/signing-key` stay free. A paying organization's members also skip the free tier's row cap.
- Eight archive sources that only ran by hand are now on the schedule: the MCD coverage lists (weekly), the national Medicaid NCCI edit files (weekly, first capture on its first run), and six closed or annual sets (NUCC taxonomy release dates page, 42 CFR annual editions, Title 42 US Code editions, legacy ICD-10-CM files, DMEPOS fee schedule item pages, DMEPOS Federal Register notices) monthly.
- **KB pages live on `kb.verzi.health` only.** A browser request for `api.verzi.health/kb/...` now answers `301` to the same path and query on `kb.verzi.health`. API clients are not redirected: requests with an `X-API-Key` or `Authorization` header, requests whose `Accept` prefers JSON, non-GET methods, and the KB JSON routes (`/kb/metrics`, `/kb/{kind}/{num}/v/{ver}/sections`, `/kb/code/{hcpcs}/passages`) are served where they are. Sign in on `kb.verzi.health`; a session from the API host does not carry over.
- `kb.verzi.health` has its own `robots.txt` and `sitemap.xml`, listing the KB index, document pages and code pages.
- KB HTML pages answer `HEAD`.
- Raw archived files (`/archive/files/...`) and the `/kb/file/{sha256}` pages send `X-Robots-Tag: noindex`.
- **The daily building-permit signals run moved from Fargate to the box, and its LLM stage runs on the Claude Code subscription instead of the Anthropic API.** `signals_pipeline.pipeline.classify` has a `claude-code` backend (`SIGNALS_LLM_BACKEND`, the default when no `ANTHROPIC_API_KEY` is set) that runs the signed-in `claude` CLI headless with no tools, a `--json-schema` for the verdicts, and an allowlisted environment, so no API key or database URL reaches it. A usage-limit message raises `ClaudeCodeUsageLimit`, and any CLI error fails the batch instead of reading as no verdicts. `aws_entry` no longer requires `ANTHROPIC_SECRET_ID`, and accepts `SIGNALS_DATABASE_URL` in place of `DB_URL_SECRET_ID`. `building_permit/box/run_daily.sh` is the box runner (lock, per-day success stamp, own SSM tunnel to RDS). The EventBridge schedule `verzi-signals-daily` is now `State: DISABLED` in `infra/template.yaml`; the task definition is unchanged. The signals classifier tests now run in CI.
- Public pages, the Coverage KB, host sites (status, archive, updates), MCP and sign-in, and the admin console use Direction A "Signed": black, white, and Rx Green, with self-hosted Schibsted Grotesk and JetBrains Mono. Customer-facing copy says receipt.
- **Six state Medicaid exclusion lists are paused: Colorado, Hawaii, Kansas, Michigan, New Jersey and Nevada.** The exclusion loaders now identify themselves as our archive bot. These six sites refuse that, sit behind a bot check, or forbid bots, so their lists stop refreshing. The rows already loaded stay, as of each state's last load. The other 28 states still load monthly.
- **Mississippi Medicaid exclusions marked "OIG Exclusion" now count as federal OIG actions.** They are no longer listed a second time as Mississippi state actions in license discipline results. The federal OIG exclusion list (LEIE) already lists them, and Delaware and Louisiana work the same way.
- **State exclusion loads no longer keep dates of birth.** Some states print them in their lists. They were kept in the stored copy of each row and never served. They are now dropped when a list loads.
- **State exclusion results now say how current each record is.** Every state record from `/exclusions/state/{npi}`, `/exclusions/comprehensive/{npi}`, `/exclusions/state/search`, `/exclusions/crossref/{npi}` and the batch screen carries `as_of` and `current`. `as_of` is the date its state list was last loaded. `current` is true while the list is still scheduled. For the six paused states (Colorado, Hawaii, Kansas, Michigan, New Jersey and Nevada, paused since 2026-11-16), `current` is false, and `currency_note` says the list is not refreshed and why. Their records are still returned and still count. `/exclusions/state/{npi}` also lists `paused_states`, and `/exclusions/state/coverage` shows each state's `paused_on` and `pause_reason`.
- **A paused source is not reported as stale.** On `/sources` and `/status`, the six paused lists read as exempt, with their age and a "paused since" note. They never count as stale or critical.
- `/status` and `/v1/sources` now mark a source critical when our check for a new release has failed on runs at least 20 hours apart, with no good check between. Before, a source read fresh while its last load was recent, even when we could not ask the publisher. The `freshness` object has a new field, `check_failing_since` (a date, or null).
- Transmittal parser 1.4.2 reads 114 more change tables (113 of the 445 tables that 1.4.1 held back, and one more). It now reads a table that ends at a "III." line after a page break or at "*III.  FUNDING", and a table with a contents row in another shape. A row with a letter-suffix number, such as 10.2A, now holds its table back instead of naming the wrong section. The manual section reader uses these rows after the prod re-parse.
- Manual sections (`receipts.rule_passages` and `/archive/docs/{doc_id}/section`): each `chain` entry now names the `parser_version` of the transmittal parse that proved the revision.
- A section touched by a transmittal change row whose action (R, N or D) could not be read now answers `unknown` with `action_not_paired`. Before, it could answer from the transmittal's text for that section. No served receipt passage changes: receipts serve chapter text only.

Fixed
- The transmittal parser (1.4.0) reads a change table whose rows follow the "III. FUNDING" line in the stored text. This takes effect after the transmittals are parsed again.
- **Texas Medicaid (TMHP) files are now marked licensed.** TMHP shows the AMA/ADA End User License Agreement on its fee schedules and provider manuals, so `tx_medicaid_dme_fees` and `tx_medicaid_dme_coverage` move from `public_domain` to the new `state_ama_ada_terms` key. `/archive/files/{sha256}` no longer gives a link to their bytes, and `/archive/files/{sha256}/text` holds their text; the sha256 and the publisher URL are still shown. Extracted facts (codes, modifiers, amounts, effective dates, PA flags) are not affected.
- **KB: the free E0601 page and search.** A sample date chip names its document ("Article A52467, version 35"), and on the free page it stays on the free page. A search for E0601 by a reader without the KB plan opens the free page. The KB sign-in page offers a path for a reader who is not a customer: the free E0601 page, a free API key, or a demo.
- **The refill applicability warrant reads the HCPCS descriptor from the file in force on the date of service.** Before, it read the newest HCPCS file. The IN-category tiebreaker now cites the quarter file in `basis[].tiebreaker.descriptor_source` (document, quarter, version, member file, sha256). When no descriptor resolves, `descriptor_reason` says why: `before_first_held_file` (before 2015), `no_file_in_force` (2021 Q4), `file_in_force_not_parsed` (with `unparsed_version_id` and, when its zip holds its own code table, `unparsed_member`) or `code_not_in_file_in_force`. A changed file not parsed yet is never skipped for an older copy. The descriptor text is still not served.
- The `/check` page and JSON, and the KB code page, still show the current HCPCS descriptor. They now name its file: `descriptor_quarter`, and on the check page the note "Current HCPCS file (2026Q4), not the file in force on the date of service." For a code CMS has dropped, the note says "Last HCPCS file listing this code (2023Q2); the current file is 2026Q4."
- **A request with no API key gets a 401 that says what to do.** A keyed route called without `X-API-Key` used to answer FastAPI's raw 422 validation body. It now answers 401: "A Verzi API key is required. Send it in the X-API-Key header. Get a free key at https://docs.verzi.health/signup." A request with other validation errors still gets the 422.
- The archive's `/as-of?date=` answers carry that date in `meta.as_of`, not "current".
- The docs samples call `/v1/provider/{npi}`, not the missing `/v1/npi/{npi}`.
- **The API's pages say Verzi Health API, not Verzi Healthcare Data API.** This covers the OpenAPI title, the docs, status, sources, accuracy, usage and resources pages, the quickstart, the data disclosure statement and the code samples. The privacy policy and terms of service keep the old name until their legal text is updated.
- **The MCP server's instructions no longer say that the signed answer decides whether a claim is supported.** They now say what it returns. Each block names its source file and the version in force on the date of service. Otherwise it gives a status (unknown, not_found or not_requested) and, where known, the reason. A requirement found in CMS's text carries source proof. The signed-answer tool does not decide whether a claim is supported, covered or paid.
- **Signed-in KB readers with a plan are not counted by the KB page limit.** A KB session or an API key with the KB plan reads `/kb/code` and `/kb/free` without the 30-a-minute per-IP limit, so a team behind one office address does not share it. The check spends no daily request. A cookie or key that is not valid or has no plan still counts.
- **The public code check says when a source could not be read.** `/check/{hcpcs}` and `/v1/check/{hcpcs}` no longer leave out a source that failed. When the documentation requirements fail, `documentation_requirements.status` is `unknown` (it was `unavailable`) with `reason` `source_unavailable`. When the Required Prior Authorization List fails, `prior_authorization` is present with `status` `unknown` and the same reason (it was left out). Each LCD gains `in_force_status` and `in_force_reason`; a failed version lookup says the version in force could not be read. The page shows a "could not be read" line for each. When the list was read but cannot answer, `prior_authorization.reason` is the list's own cause (`no_version_in_force`, `not_parsed`, ...). Otherwise `reason` is `null`. The quickstart sample response shows the new keys.
- **A busy service answers 503, not 500.** When no database connection comes free within 3 seconds, the API answers `503` with `Retry-After: 5` and `{"error": "service_busy"}`. Retry after the stated delay. A database query that runs longer than 30 seconds now ends with an error.
- **The KB code and free pages allow 30 requests a minute per IP.** `/kb/code/{hcpcs}` and `/kb/free/{hcpcs}` share one counter of 30 per minute per IP, on top of the general limit of 120. Above it they answer `429`. Every `429` from a public per-IP limit now carries `Retry-After`, the seconds until the window resets. Crawlers stay allowed.
- **`GET /vbc/reach` and `GET /vbc/ngaco` page their lists.** Both take `limit` (default 50, max 500) and `offset` and answer `{total, count, limit, offset, results}`. Before, both ignored `limit` and returned every row. `GET /vbc/reach/{entity_id}` already paged its participants with `provider_limit` and `provider_offset`.
- **`GET /provider/{npi}` reads Open Payments and answers by year.** The dossier gains an `open_payments` block (records, payments, the general plus research amount as `total_amount`, the ownership interest value apart, the split by payment type, manufacturers, one row per program year) and `data_available.open_payments`; the docs had listed Open Payments but the code never read it. `prescribing` and `utilization` carry `by_year` rows beside their totals. The whole dossier now runs on one database connection, so a busy pool no longer fails it five times over, and a dossier slower than 5 seconds logs the time of each block.
- **`/sources` marks a source stale when the publisher lists a newer release.** Each yearly source (Open Payments, Part D Prescriber, Physician Utilization, HCRIS, MA Stars) now carries `latest_release_available`, `latest_release_loaded` and `release_checked_at`. A source whose publisher lists a newer release than the newest loaded one shows `stale` with both releases in `freshness.detail`, whatever the clock says. The pipeline asks the publishers once a day. A newly listed year loads once it is listed in the registry, after its layout is checked.
- **The KB index says how many documents are in force and how many are retired.** The line above the table reads "151 LCDs and Articles (143 in force today, 8 retired)" instead of the total alone. `docs/CORPUS_COUNTS.md` defines each corpus count once.
- **Design partner contact mail goes to both inboxes.** `POST /contact` with interest `partner` or `design_partner` sends one email to robert@verzi.io and adrian@verzi.io. The subject is "Verzi design partner request". Other interests still go to `CONTACT_TO` (default adrian@verzi.io). `CONTACT_TO` and `CONTACT_PARTNER_TO` may list several addresses, separated by commas. No Railway change is required for the default.
- **The quickstart's first example is a DME code check.** The curl, Python, and JavaScript samples call `GET /v1/check/E0601?state=CO&dos=2026-08-15`. The sample response is a real free-key answer: coverage `lcd_listed`, LCD L33718 version 52, and `signed_receipt.included` false. The signed receipt comes with a paid plan or a design partner plan.
- **The public code check counts the KB's approved labels.** `/check/{hcpcs}` and `/v1/check/{hcpcs}` count the approved passages on the version in force (the KB's label layer, quoted from CMS), not the older requirement rows. Where labels are proposed but not yet approved, the page says "N proposed requirements, under coder review." `documentation_requirements` gains `pending`. Counts only: no passage text.
- **Signup shows the key only after an email code.** `POST /signup` no longer shows a key on the page. It emails a 6-digit code to the address, and the key appears once, after you enter the code at `/signup/verify`. Free-mail providers (Gmail, Yahoo, Outlook, Hotmail, iCloud, AOL, Proton, GMX, Mail.com, Yandex, Zoho, Fastmail, Hey, Tuta, QQ, Comcast and the country variants of the first group) are refused: use your work email.
- The free organization daily limit is 10,000 again. The free per-key limits stay 1,000 requests a day and 100 rows a request.
- **A manual chapter revision is dated by its transmittal's Effective date.** `GET /archive/docs/{doc_id}/as-of` for a CMS manual chapter (Claims Processing, Program Integrity, Benefit Policy, NCD manual) now starts a revision on the Effective date of the transmittal it names, not on the Implementation date. This moves 216 of 792 revision dates, almost always earlier (median 60 days); the Implementation date is kept when the Effective date is missing, conflicting, or more than 365 days before the transmittal's issue date. The answer carries `effective_from_source` (`transmittal_effective` or `transmittal`) and, when the Effective date precedes the transmittal's issue date, `transmittal_issue_date`.
- **A manual chapter answers with its highest Rev in force, and says when a lower Rev is still ahead.** `GET /archive/docs/{doc_id}/as-of` for a CMS manual chapter now returns the highest Rev that has started on the date of service. The transmittal dates are not in Rev order (82 chapter version pairs on 2026-10-14 started in the wrong order, 114 with the Effective dates), so a lower Rev could answer after a higher one. New field `inverted_window`: set when a lower Rev starts after the date of service. It names the answering Rev and each such lower Rev with the transmittal's issue, effective and implementation dates and its own wording quoted from the parsed transmittal. Null otherwise.
- **The rest of the public pages use the Ledger brand.** Quickstart, data disclosure, terms, privacy, signup, and the other public pages that used the midnight theme now share the docs landing's ink, paper, green, and gold, IBM Plex, the Ledger lockup, and the dark-mode toggle. Marketing copy says receipt and signed answer. The terms keep the legal phrase "represent and warrant."
- **A work email gets a free API key immediately.** Gmail, Yahoo, Outlook, Hotmail, iCloud, AOL, and Proton are still reviewed by hand. The message on a key that is waiting no longer says approval takes usually within 1 business day.
- **The free tier is 1,000 requests per day and 100 rows per request.** Both numbers come from one setting (`FREE_DAILY_LIMIT` and `FREE_ROW_CAP`). The signup page, the quickstart, and the pricing page use them.
- **Developer docs use the Ledger brand.** The docs landing page uses ink, paper, green, and gold, IBM Plex, and a dark mode that follows the system and a toggle. Public copy says receipt and signed answer. The favicon is the Ledger mark, and the social cards are redrawn in the same palette.
- KB pages (right margin): Requirements at a glance on a code page lists every approved passage for the code on the page, from each document the page shows (the LCD first, then the other documents that hold the code), grouped by document and version, then by kind; a click opens its quote. The version line names each companion Article version in force on the LCD version's start date, linked when the KB holds its page. The receipts table lists the page's own document only; one line links each related document's own receipts.
- KB Copy + cite copies CMS's words only. Words Verzi writes inside the policy text (the section headings Verzi names, table column names, N/A) are left out, with a "[...]" line where they were; the citation names each section the quote spans. Paragraphs and list items end with a line break and table cells with a tab. Copy + cite refuses a selection in several pieces when CMS text lies between them. A browser that splits one drag around the section toggles still copies it as one quote.
- **KB links now name `kb.verzi.health`.** The `kb_url` field in the archive and as-of JSON, the updates feed's KB links, and the links in watch alert and digest emails use `https://kb.verzi.health/kb/...`. Old `api.verzi.health/kb/...` links keep working. Each KB page names its `kb.verzi.health` address as canonical in a `Link` header (with only the version and date-of-service parameters), and the KB sign-in pages carry `X-Robots-Tag: noindex`.
- **NCCI PTP answers for dates before 2022 cover HCPCS Level II pairs only.** For a date of service before 2022-01-01, `GET /rules/ncci/ptp`, the edits block of `GET /rules/warrant` and `GET /rules/warrant/appeal`, and `GET /rules/warrant/changes` answer a pair only when both codes are public HCPCS Level II (first character A to V, not D). A pair with any other code, such as a CPT code or a D code (CDT), answers `unknown` (`edited: null` on `/rules/ncci/ptp`) with a reason. On `/rules/ncci/ptp` and the edits block, `checked.rule` is `license_scope`. No answer changes today: Verzi holds no PTP file read for a date before 2024-04-01 yet.
- **NCCI MUE answers for dates before 2022 cover HCPCS Level II codes only.** For a date of service before 2022-01-01, `GET /rules/ncci/mue`, the MUE part of the edits block of `GET /rules/warrant` and `GET /rules/warrant/appeal`, and `GET /rules/warrant/changes` answer only for a public HCPCS Level II code (first character A to V, not D). Any other code, such as a CPT code or a D code (CDT), answers `unknown` (`mue_value: null` on `/rules/ncci/mue`) with a reason. In the edits block, `checked.rule` is `license_scope`. This changes answers today: Verzi has read the 2020Q1 to 2021Q4 tables, and CPT and D codes in the practitioner and outpatient hospital tables for those quarters now answer `unknown`. The DME supplier table holds no such codes, and a HCPCS Level II code such as E0601 answers as before.
- **A KB page says when the version shown is not the one in force today.** A quiet banner sticks under the top bar: "You are viewing version 20 (2020-01-01 to 2021-08-07). Version 52 is in force today.", with the in-force version as a link when the KB holds its page. It shows for an older version, a version not yet in force, and a document with no version in force today; it does not print. CMS's quoted revision note at the top now shows only on the version in force today; CMS's full log stays in the revision history section.
- **KB receipts are built for an auditor.** The "Receipts for auditors" table reads Document, Version, In force, Archived on and Verify. Verify links CMS's own copy of that version and Verzi's archived file. The table carries no hash. The table lists the page's own document only; one line links each related document's own receipts. Every small receipt toggle on the page is now a "source" toggle with the same two links. A new page, `/kb/file/{sha256}`, shows one archived file: its document, capture time and URL, size, sha256 fingerprint and how to check it, the structured rendering's sha256 and the archive file id. A signed-in KB account gets a one-hour download link for the original file there; an anonymous reader gets a sign-in link, never the download. Files from sources whose license carries CPT descriptors (the AMA license) offer no download. The appeal exhibit keeps the full receipt under each passage.
- **KB policy and code pages end with the main template's bottom sections.** Under the text, each page shows its version history (one box per version, "v20" over its window, with a button that shows the versions superseded the same day they took effect), then CMS's revision history as its own open section, then one "Receipts for auditors" box. A receipt line under the title names the version shown and its dates. On a code page, the free list of in-force documents no longer repeats the LCD the page shows, a signed-in customer gets those documents' text without a second list, and CMS's code-to-policy list moves into the receipts. A document version with no stored text rendering now says so, instead of a hash failure line.
- **A KB code page now holds its policy, in the main template.** `/kb/code/E0601` shows the code large, the LCD's title, CMS's descriptor, and then the LCD itself: the DME MAC jurisdiction row, CMS's code list, the revision note, the date of service picker, the version chips, the sections, the customer line and the receipts. The picker and the chips reload the code page, so one date drives every block. When CMS lists the code in more than one LCD with a KB page, chips switch between them (`?doc=`). A signed-in customer gets the LCD's verbatim text with its highlights, and below it the approved passages and CMS text of the code's other documents, such as its Article. A version id from another document shows the newest version and says so. A code with no LCD page keeps the old page. The policy page `/kb/lcd/{num}` is unchanged.
- **The applicability warrant answers faster on a cache hit, and fails closed on rendering drift like `w3` already does.** It now reads a document's text rendering through `w3`'s existing cache, instead of fetching it from the store, unchecked, on every request. A stored rendering that no longer matches its recorded hash now leaves that basis without a span or quote instead of quoting a span from drifted text. No field or shape changed otherwise.
- **The `w3` and `applicability` warrant blocks answer faster.** Both resolve a code's governing documents (an LCD and its Article, commonly two) in one batched as-of lookup instead of one query per document. Response bodies are byte-identical; no field or shape changed.
- **The warrant endpoint answers faster.** `/rules/warrant`'s seven to eight blocks (`w0`, `w1`, `w2`, `w3`, `exclusions`, `applicability`, `prior_authorization`, and `w0_ordering` when `ordering_npi` is set) run concurrently instead of one after another. They are independent reads; no field or shape changed. Measured on the five demo calls: 44 to 60% faster (for example 12.8s to 5.1s).
- **W2 PTP answers from CMS's PTP file in force on the date of service.** `/rules/ncci/ptp`, the warrant's `w2.ptp` block and the change timeline read the complete quarter file for the date's quarter, from the change-only store, and name it in `checked` (rule `ptp_edition_in_force`) and in `as_of.version_in_force`. Before, the newest held file answered for every date and the citation always named it; a pair CMS dropped from a later file answered `not_edited` for dates on which the edit was in force, and a date before the first held file answered from a 2026 file. A date whose quarter has no complete file now answers `edited: null` with a `reason` that names the quarter and the nearest files read; no other quarter's file answers for it (on 2026-10-09 the files read are 2024Q2 to 2025Q3 and 2026Q3 to 2026Q4, both settings). A `not_edited` answer cites the pair's newest row, with `present: false` and `recorded_in` when CMS's file no longer lists it. The fact's `citation` names the archived part file whose bytes carry the row (the file that recorded it, never a newer one).
- **Codes are checked and upper-cased on every rules and warrant route, and on the MCP warrant tools.** A code is five characters, digits or capital letters. `hcpcs=e0601`, `code_a=e0601` and `modifier=rr` now read as `E0601` and `RR`; before, the fee route answered 404 for a lowercase key. A value that is not a code (`1312`), or a code paired with itself (`code_a=13121&code_b=13121`, `companion` equal to `hcpcs`), is a 422; before, PTP answered `edited: false` for them.
- **The fee route states what 0.0 means.** `/rules/dmepos/fee` and the warrant's `w1` serve the file's own ceiling and floor; CMS's DMEPOS README says the fields are filled with zeros for codes adjusted using competitive bidding information, so `0.0` is CMS's value (E0601 RR), and `null` means the file leaves the cell blank or the area is not subject to them.
- **`/kb/metrics` serves its cached numbers at once and refreshes them in the background.** The first request after a deploy no longer waits about 20 s: the cache fills at app start, and an expired value serves while one refresh runs (`meta.stale`, `meta.refresh_error`).
- **W3 serves the in-force LCD or Article verbatim, marked unlabeled, when no approved label is in force.** A missing label no longer makes `warrants.w3` answer `not_yet_available`. Each in-force document now carries `label_status` (`labeled` or `unlabeled`). An unlabeled document carries its version, its title, and a `receipt` (archived file, sha256, rendering sha256, fetch time, publisher URL). `warrants.w3` never carries the document text. Entitled KB readers and keys get `document_text`, CMS's full text for that version, from `/kb/code/{hcpcs}/passages`, served only when it matches its stored hash (else `text_available: false`). `coverage.completeness` is `unlabeled` when no approved label serves, and `coverage.documents_unlabeled` counts these documents. The confidence rollup grades an unlabeled W3 as `partial`. The KB code page lists the in-force documents with their receipts; signed-in customers get the full CMS text.
- **The sample integration page needs a signed-in KB session.** It moved under the KB path (the KB sign-in reaches it) and shows only to readers whose plan includes the warrant; anyone else gets 404. The old path is gone.
- **Private beta wording on the docs landing and signup.** Badge says "private beta" instead of "self-serve keys"; signup says "Free key on request" instead of "Self-serve key"; the quickstart notes that keys are approved by hand during the beta.
- **Footer updated across all public pages.** The copyright line is now "(c) 2026 Verzi"; the verzi.health pages carry "Rules data, not PHI" and the provider-data pages (/sources, /platform/stats, /accuracy, /status, /my-usage) carry "Public data, not PHI".
- **The free tier card on the docs landing now lists archive and catalog items** instead of "Provider intelligence lookups and aggregates", matching the signup page.
- **CPT rationale blocklist comparison is now case-insensitive and whitespace-tolerant.**
- **The KB's receipts table shows the companion Article under each LCD version.** For every Article CMS relates to the LCD, a row under each LCD version names the Article version in force on that LCD version's stated start date (the as-of rule the warrant uses), with its window, a link to that version's page and the sha256 of the archived bytes. An LCD version with no stated start gets no row.
- **The KB opens on a code search.** Type a HCPCS code or the start of one at `/kb`: the page lists the codes that an LCD lists in CMS's own code-to-document table, with CMS's descriptor, and each code links to its page with the policy documents. The document table stays below it.
- **A KB code page shows no descriptor for a code that is not public HCPCS Level II.** A D code (`/kb/code/D0120`) is CDT, the ADA's licensed text. Its page says so in one line and does not show the descriptor. Public HCPCS Level II pages are unchanged.
- app.verzi.health now opens the KB sign-in. The provider-data dashboard stays at www.healthcaredata.io.
- Responses on api.healthcaredata.io no longer carry Deprecation or successor-version Link headers. healthcaredata.io stays the home of the provider-data product.
- **Pricing is by contact during the private beta.** `/pricing` shows one line: contact hello@verzi.health for access and pricing. The page is out of the sitemap and marked noindex. `/my-usage` shows the same contact line to Free and Starter accounts instead of prices and a checkout button, and the quickstart's rate-limit note points to it.
- **KB customer log in.** KB pages no longer ask you to paste an API key. "Customer? Log in" opens `/kb/login`: enter your work email, then the 6-digit code we email you. The session lasts 14 days. Signed in, the page shows your organization and a Log out link, and loads the verbatim text when your plan includes it. Access is by organization: when the organization's plan includes the KB paid view, every member reads the verbatim text. API clients keep the `X-API-Key` header on `/kb/{kind}/{num}/v/{ver}/sections`; a key with the paid view still works when the browser session's plan does not include it. The login email is matched without regard to case, and Log out is a button (a POST), not a link.
- **Dashboard login signs in approved accounts only.** The dashboard login no longer creates an account for a new email. It sends a code only to an existing, approved account, and it gives the same answer for every email. Get an account at `/signup`. Dashboard sessions last 14 days; earlier sessions end and need one new sign-in.
- **One account per email, in any case.** Signup and the dashboard login store emails lowercase and find an existing account without regard to case: `Pat@Example.com` and `pat@example.com` are the same account.
- **Sample integration page: CMS's words for the rate types.** The rate-type legend now quotes CMS's own Transparency in Coverage schema definitions, linked to the pinned schema file. Receipts name their documents in words ("CMS DMEPOS fee schedule file, quarter 2026Q4") beside the file hash.
- **No empty sample box.** A KB code page with no approved label for the code shows no "Sample passage" box at all; the box appears with the first approval. Where approved passages exist but none is in force on the chosen date, the page still says so. On the one-code-every-payer sample page, the empty policy-passage cell reads "Not held yet" like every other empty cell.
- **Sample integration page in plain words.** A fee cell where CMS's file prints 0.00 reads "CMS's file lists 0.00 for this cell" instead of $0.00. The commercial payer's rate ranges say how many rows its own file publishes at 0.00 ("The payer's file lists 0.00 for 404 rows"). The edit cell names the MUE adjudication indicator (MAI) in CMS's own term. Rate types keep their published names, with a one-line legend. The Medicare check on commercial providers reads as three short sentences. Raw CMS column names and internal version ids move out of the cells; receipts keep the column names behind the "receipt" toggle.
- **KB pages say whose code list it is.** LCD pages list the codes CMS's own LCD code table names for the current version ("Codes CMS lists in this LCD"); Article pages, for which CMS publishes no DME code table, label their list as Verzi's coverage-label mapping. Receipts under quotes and lists now sit behind a "receipt" toggle. A governing LCD outside the Verzi KB links CMS's own page and says so. On a date-of-service view, the version-in-force line sits directly above the note it explains.
- **Code pages list governing policies as CMS lists them.** `/kb/code/{hcpcs}` now names every LCD whose current version lists the code in CMS's own LCD code table (from the Medicare Coverage Database download), with CMS's description of the code quoted, the group and version it sits in, the Articles CMS relates to each LCD, and the file's sha256 as the receipt. HCPCS Level II only. Nothing is inferred, and the list refreshes with each weekly capture. Code pages also answer faster (cached lookups).
- **Clearer code-page and receipt wording.** The prior-authorization line labels CMS's Effective Date cell as a quote. A code with no approved label keeps the "unlocks when the first label is approved" line on every date. Receipts drop the renderer tool string and state plainly when CMS gave a version no dates.
- **Status page reasons in plain words.** A failing source shows one fixed sentence for its state ("The latest run failed.", "The latest run found no files.", and so on) and the run date, never the raw error text. Raw errors stay in `GET /v1/archive/runs`. Empty status tiles read "not reported" instead of a dash.
- **Watch-a-code alert subjects use the document's headline**: "E0601: Positive Airway Pressure (PAP) Devices changes 2026-11-01", the same headline rule as the feed.
- **KB policy pages lead with CMS's newest note.** The top block quotes the selected version's own revision note. On the newest version without its own note, it quotes CMS's newest note on file and names the version it belongs to. The "last changed" date comes from that same entry, so the two agree. Where no note is extracted, the page says exactly that instead of claiming CMS wrote none.
- **CMS's revision history and the related documents come before the key prompt.** The full revision history is its own section above the "Already a customer?" line, no longer inside the receipt. LCD pages list the Articles CMS relates to them, and Article pages list their LCDs, from CMS's own related-documents file. Each links to its KB page where one exists.
- **The "open on CMS's site" link works.** For versions captured from the Coverage API, the receipt links the public Medicare Coverage Database page; the API address (which needs a key) is shown as text.
- **Version links are exact.** KB version chips link each captured version by its archive id, so two captures of one CMS version, or a version CMS did not number, each open their own page. The verbatim-sections response names the version it actually served.
- **KB index:** documents without CMS dates say so, titles show CMS's characters ("/", not "&sol;"), and the count says which documents have archived history pages. Version chips read "version 48".
- **The archive page opens on a worked example** (every version of LCD L33718) instead of an empty box.
- **Status page platform numbers read as labels**, not a raw JSON block.
- **Plain words on free pages.** "backfill" reads "pulled from the past" and "wayback" reads "Wayback Machine copy" on the feed and in the digest. Feed chips are keyboard buttons. Pages carry a favicon.
- **A colon, never a dash, in every headline and subject.** "Takes effect 2026-10-30: Claims Processing Manual transmittal R13954" on the feed, calendar, digest, alerts, and RSS; alert subjects read "{code}: {document} changes {date}". The Order and Referring file reads "Order and Referring", CMS's own dataset title.
- **Readable names for regulatory entries.** Price Transparency, No Surprises Act, Interoperability and Prior Authorization, and 42 CFR entries now carry a label from CMS's own program name and the publisher's URL slug. `pt:hospital-price-transparency-enforcement-updates` reads "Price Transparency: hospital price transparency enforcement updates", and `cfr:42-414` reads "42 CFR Part 414". The label comes from the id only, never from content, and an unmapped id keeps its raw form.
- **The free surfaces, to spec.** Every change surface now shares one entry anatomy: headline (a future effective date leads, bold), gain line (document reference, version, effective date, "cited by warrants for" the mapped codes), the publisher's revision note quoted and labeled or the plain statement that none was published, then a collapsed receipt with the KB and CMS source links. Applies to the updates feed, the calendar, the weekly digest, the watch-a-code alerts, and RSS.
- **Filter chips and the pipe rule.** The feed defaults to all sources with chips (All / Claim policy / Fee schedules / Code sets / Regulatory). Notification pipes (digest, watch-a-code, webhooks) carry claim-policy and fee-schedule sources only; regulatory overlays, code sets, and provider files never ride in an inbox, whatever the subscription says. Regulatory entries on the feed say so.
- **Calendar, date first.** `updates.verzi.health/calendar` leads with the effective date, claim-policy sources only, the quoted note under each item, and an "Add to my calendar" export (`GET /v1/archive/upcoming.ics`).
- **Status page freshness.** `status.verzi.health` adds a per-source freshness table: every archived source with its last capture, cadence, and a fresh or stale pill. Stale is shown as plainly as fresh.
- **The engineer door says so.** `GET /v1/archive/docs/{doc_id}/as-of` now carries a notice naming itself a machine surface, with the KB page link for the readable version. Payload otherwise unchanged.
- **KB doc pages lead with CMS's words** (the approved free-surfaces layout): title, one-line identity (versions, span, last-changed date), then the version's revision note quoted and expanded; the version strip and a one-sentence section summary follow; the API-key box is a one-line "Already a customer?" link after the free content; receipts collapse behind one toggle at the bottom. When CMS published no note, the page says so plainly. Code pages show the sample passage before anything else asks for a key.
- **Readable names for transmittals and MLN Matters entries.** Feed, calendar, digest, and RSS entries derive a human label from CMS's own id structure (the transmittal suffix names the manual it amends): `transmittal:r13954cp` reads "Claims Processing Manual transmittal R13954". Metadata only, never content; anything unmapped keeps its raw id.
- **Policy documents first.** The updates feed defaults to entries with document titles or revision notes (the DME policy corpus), with counts for both views; "All sources" shows every observed version. The digest lists policy sources first.
- **KB pages wear the shared brand.** `/kb` pages now use the one site component (light default with a persisted theme toggle, standard nav, brand type). Serif is reserved for verbatim document text: passages, the sample quote, and CMS's revision notes; interface text is sans. No words changed; the fidelity gate's guarantees are untouched.
- **One brand across the public pages.** The status, archive, updates, calendar, and subscription pages now share one brand component: light theme by default, dark via the toggle in the nav (your choice persists per browser), Reddit Sans interface, turquoise accent, and a serif reserved for verbatim document text. Same nav row everywhere, now including the Coverage KB.
- **Corpus metrics on the status page.** `status.verzi.health` now leads with the Medicare DME corpus numbers, read live from `GET /kb/metrics`: codes answering, policy documents and versions, the fidelity percentage with its section counts, archive depth, A/B MAC captures, and Medicaid states tracked.
- **Revision notes on the feeds.** Where the renderer extracted one, every change on `updates.verzi.health`, the calendar, the weekly digest, the watch-a-code alerts, and the webhook events now carries the publisher's own revision note verbatim (`revision_note`, with `rev_number` and `rev_date` where stated). Null when absent; never a paraphrase.
- **Readable updates feed.** Each entry on `updates.verzi.health` now leads with the document title, the effective date, and the HCPCS codes the coverage layer maps to the document, beside the version, origin, and sha256. `GET /v1/archive/changes` carries the codes as `affected_codes` on every change row (empty when no mapping exists). The entries stay machine-observed; the titles and dates are the publisher's own words from the archived bytes.
- **Pending keys say so.** A key awaiting access review now gets a 403 that says it is pending review, instead of the generic "deactivated" message. (Signup has been approval-gated since the private-beta lock; access requests are now reviewed in the admin portal.)
- **Source archive now holds A/B and HHH MAC coverage documents (all jurisdictions).** `mcd_ab_mac` adds 4,569 archived LCDs and Articles (29,237 dated versions, 2015 to 2025) alongside the DME MAC set, so `GET /archive/docs/{doc_id}/as-of` resolves the local coverage document in force on a date of service for A/B and HHH jurisdictions too. Proposed and draft versions are archived but carry no effective date (they were never in force). Older CMS transmittals back to 1999 were also backfilled, so more manual-chapter revisions resolve a stated effective date.
- **DAC, PECOS reassignment, and NPPES refreshed** after 66 days stale — DAC to the 2026-07-31 file (2.01M rows), reassignment re-derived (1.77M), NPPES to the August file (9.73M providers, now including Authorized Official name/title/credential on 1.96M organizations). `/sources` freshness reflects the reloads.
- **Source freshness now distinguishes "no refresh commitment" from "late"** — sources with no expected rhythm (hand-curated mappings, static reference crosswalks, as-needed enrichment, declared-but-not-yet-live loaders) previously fell back to monthly staleness thresholds and showed permanently stale badges at `/sources`. They now report an explicit `exempt` freshness with the reason, and never degrade `/status`. A genuinely late scheduled source still turns `/status` amber or red exactly as before.
- **`ca_medical_board` source entry declares its real cadence** — the entry is NPPES-derived (no state loader exists yet) but declared weekly cadence, so it drifted to "critical" by construction and kept `/status` red for two months. Now monthly, matching the NPPES reload cycle that actually feeds it; the notes field says so explicitly.
- **Hospital Financial & Regulatory Deep-Dive** — a coordinated set of additions closing several hospital financial/regulatory gaps in one pass. See `docs/HOSPITAL_FINANCIALS.md` (published at `/resources/hospital-financials`) for the full writeup.
  - **HCRIS deep worksheet parse: balance sheet, charity care, cost centers, DSH** — the HCRIS loader previously extracted 8 numeric coordinates from the same NMRC file we already download quarterly; it now extracts across four more worksheet domains. New tables: `hcris_balance_sheet` (Worksheet G — full balance sheet with derived current/quick/debt-to-equity ratios), `hcris_uncompensated_care` (Worksheet S-10 — charity care charges/costs, bad debt, total uncompensated care), `hcris_cost_centers` (Worksheet A + C Part I — charges, total costs, and salary/non-salary split for ~20 named cost centers plus all other reported lines). New `hcris_reports` fields: `operating_income`, `other_income`, `total_salaries`, `dsh_patient_pct`, `dsh_payment_amount`, `medicare_days`/`medicaid_days`/`medicare_discharges`/`medicaid_discharges` (populating the previously-unused `medicare_days_pct`/`medicaid_days_pct` columns). New endpoints: `GET /cost-reports/{ccn}/balance-sheet`, `GET /cost-reports/{ccn}/charity-care`, `GET /cost-reports/{ccn}/cost-centers`. Every coordinate was empirically validated by reconciling internal worksheet subtotals and cross-checking against a real hospital's published financials — every headline figure matched exactly or within trivial rounding.
  - **Hospital Readmissions Reduction Program (HRRP) penalties** — new `hrrp_penalties` and `hrrp_measures` tables loaded from the CMS IPPS Final Rule HRRP Supplemental Data Files (FY2021–FY2026). Three new endpoints under `/vbc/`: `GET /vbc/hrrp/{ccn}` (payment adjustment factor history), `GET /vbc/hrrp/{ccn}/measures` (per-condition excess readmission ratios for AMI, COPD, HF, pneumonia, CABG, THA/TKA), and `GET /vbc/hrrp` (search/rank hospitals by penalty severity). `payment_reduction_pct` is always derived from the payment adjustment factor rather than trusted from CMS's own column, whose unit is inconsistent across fiscal years in the source files.
  - **Case Mix Index (CMI) and wage index** — new `ipps_impact` table loaded from the CMS IPPS Final Rule Impact File (FY2023–FY2026). New endpoint `GET /hospitals/{ccn}/case-mix-index` returns the full fiscal-year history (CMI, transfer-adjusted CMI, wage index, DSH patient percentage, resident-to-ADC ratio); `GET /hospitals/{ccn}` now includes a compact `case_mix_index` block with the latest year. CMI is always resolved to the current MS-DRG grouper version for that fiscal year, so a schema change isn't needed when CMS increments the grouper annually.
  - **Hospital service lines, accreditation, and teaching status** — CMS Provider of Services (POS) file now feeds a new `facility_services` table (~50 curated clinical service-line flags — cardiac cath lab, open heart surgery, NICU, transplant services, imaging, behavioral health, and more) plus new `facilities` columns for accreditation agency/dates and medical school affiliation. New endpoint `GET /hospitals/{ccn}/services`; `GET /hospitals/{ccn}` now includes `accreditation_agency`, `accreditation_expiration_date`, and `medical_school_affiliation`. Accreditation-organization and teaching-status code labels were empirically validated (not pulled from an official crosswalk, which wasn't accessible) against known accreditor market share before shipping — unverified codes are stored raw rather than guessed. `scripts/enrichment/enrich_from_pos.py` gains two new always-refresh enrichment passes (service availability and accreditation legitimately change over time, unlike the existing backfill-only legal-name/bed-count passes).
  - **CBSA (metro/micro area) population estimates** — new `cbsa_population` table loaded from Census Bureau annual estimates (2020-2025). `GET /hospitals/{ccn}` now includes a `cbsa_population` block (latest year + year-over-year growth); new endpoint `GET /market-intelligence/cbsa/{cbsa_code}/population` for the full history.
  - **ClinicalTrials.gov integration** — new `clinical_trials`, `clinical_trial_sites`, and `clinical_trial_investigators` tables loaded from the free ClinicalTrials.gov API v2 (193,782 US-located studies, 2.37M site records, 188K investigators). Site-to-facility and investigator-to-NPI matching uses a conservative normalized name + location match (109,684 sites and 82,639 investigators matched with zero ambiguous guesses — ties are left unmatched rather than resolved arbitrarily). New endpoints: `GET /clinical-trials` (search), `GET /clinical-trials/{nct_id}` (detail with matched sites/investigators), `GET /hospitals/{ccn}/clinical-trials` (facility rollup by status/phase), `GET /provider/{npi}/clinical-trials` (investigator's trials). `GET /provider/{npi}` now includes a compact `clinical_trials` dossier block.
  - **Facility square footage, depreciation, and EBITDA** — extends the same HCRIS Worksheet A/B-1/C parse: `hcris_cost_centers` now carries `square_footage` per cost center (Worksheet B-1 reuses the identical cost-center line numbers already validated), and `hcris_reports` gains `total_facility_sqft`, `depreciation_expense` (Worksheet A-7 Part III), and a derived `ebitda` (operating income + depreciation). Closes the EBITDA gap explicitly left open in the initial HCRIS deep-parse work, which needed a depreciation figure not yet located at the time. All figures validated exactly or within trivial rounding against a real hospital's published numbers.
- **Enterprise contact-sales tier** on the dashboard pricing section — the $1,499/mo tier is renamed "Scale" and a new custom-priced Enterprise tier covers the employment + financial intelligence lines, custom data cuts, security review, and MSA. Procurement note added: 100% public and licensed data, no PHI, no BAA required.
- **Dashboard redesigned on the Verzi corporate brand** (verzihealth.com): deep green-black theme (`#00110F`), turquoise accent, pill CTAs, JetBrains Mono as the data voice. The homepage hero now shows a **live pipeline ledger** — real per-source refresh dates and freshness straight from the public `/sources` registry — and a full **data atlas** table of all 45 sources with license, cadence, and last-load date. Every headline stat carries a provenance chip linking to the registry. PDF/print export keeps the light palette.
- **Dashboard homepage hero** rewritten verify-first: "Provider data you can actually verify," with direct links to `/sources` and `/accuracy` and a "Check Our Accuracy" call-to-action. Site metadata updated to match.
- **A DMEPOS fee miss says why, and names the files it checked.** In the signed answer, `warrants.w1` no longer answers a bare `not_found`. Each answer that is not `ok` carries `reason_code` and `reason`. A miss also carries `checked`: the fee schedule versions in force on the date and each fee table read, with its `doc_id`, `version_id`, `member_file_id` and `sha256`. `not_found` now means the tables in force are read and do not hold the cell. `code_not_in_file` means the table does not list the code. `cell_not_in_file_in_force` means it lists the code but not this key; `available_cells` names the keys it has. A miss that does not show that no fee exists is `unknown`: `no_file_in_force`, `file_in_force_not_parsed` or `no_table_in_force` (for example, a quarter whose files hold only CBA tables, asked for a state cell). It was `not_found`. A quarter that keeps an earlier quarter's state or PEN table in force (a CMS statement that the file has no update) reads that table too, as the fee lookup does. `checked` lists it with `continuation`: the quarter, the authority and the sentence. A miss there is `not_found`. The 404 from `GET /rules/dmepos/fee` carries the same `status`, `reason_code`, `reason` and `checked`. When `status` is `unknown`, its `message` says that the miss does not show that no fee exists. In `/rules/warrant/changes`, such a side is `unknown`, and `changed` is `null`. A missing state answers `reason_code` `state_not_supplied`.
- **A carried approval now also lands on a label already pending at the same spot.** The daily re-anchor (`scripts.w3.reanchor_labels`, also used by `rerender_text_v2` and `propose_from_excerpts`) carries an approved label onto a newer version when the words are byte-identical. When a pending label already held that key, the carry was skipped as "existing" and a coder had to approve the same text again. Now, if that pending label was never approved and has the same content hash, the approval is written onto it in one guarded UPDATE (`decided_by=carry_forward`, `carried_from_label_id` set to the approved source, audit note "Carried forward from label N"). Rejected, needs-changes, approved or different-hash rows are never touched, and a dry run writes nothing. Counted as `carried-onto-pending=` in the re-anchor log and `labels_carried_onto_pending` in rerender reports. No schema change.
- **The W3 label extractor can run on the Claude Code subscription instead of the Anthropic API.** `scripts.w3.extract` has a `--backend` flag (or `W3_MODEL_BACKEND`): `claude-code` runs the signed-in `claude` CLI headless with no tools and an allowlisted environment, so no `ANTHROPIC_API_KEY` or other secret reaches it and nothing is billed to an API account; `api` keeps the old Anthropic API call. With no `ANTHROPIC_API_KEY` set, `claude-code` is the default. A Claude Code usage-limit message stops the run with `ClaudeCodeUsageLimit` instead of parsing as zero candidates. The run's notes record the backend and the token counts the CLI reports.
- **The admin label queue is now a fast coder review screen.** Labels on a page are grouped by the section they sit in (document, version, section heading), each still shown with CMS's exact words in context. Groups keep the server's order, so labels the second model check flagged still come first. One key per action: `j`/`k` (or arrows) move, `a` approves, `r` rejects (with the note typed on that row), `s` approves the highlighted label's whole section, `?` shows the keys. Each section also has an "Approve section on this page" button (asks to confirm when it has more than one label). Every approval is still one POST per label, pinned to the content hash the coder saw. Every decision now carries an audit note written by the admin API from the session: `<status> by <email> in the admin label queue (<key|button|section|batch>); label <id>, content <hash prefix>`, then the coder's own note, if any. `decided_by` stays the signed-in email. No schema change.
- **The daily ledger collapses duplicate pending labels.** After the daily label re-anchor, which queues one pending label per code, the archive ledger function now runs the label dedupe (scripts/w3/dedupe_labels.py, applied): pending labels on the same words of a document shared across codes become one label for every code, so duplicates no longer build up between manual runs. It never merges into an approved label or across kinds or markers; those still wait for a coder. Like the re-anchor, a dedupe error is logged and returned in the function's result and never fails the function.
- **Only requirement labels count as documentation requirements.** The W3 coverage counts (`items_served`, `labels_pending`), a document's `label_status` `labeled`, and the public `/check` counts ("N approved documentation requirements", "N proposed requirements, under coder review") now count only the requirement kinds (order, face_to_face, clinical, rental_phase, compliance, other, initial_coverage, continued_coverage, modifier_rule). A label of another kind, such as `refill_exempt`, still serves beside its passage, and is never counted. A document whose only approved labels are of another kind serves `unlabeled` and lists them in `labels`. No current label changes count: every label written so far has a requirement kind.
- **The paid warrant serves CMS's coverage-indications text for an unlabeled LCD.** When no approved coder label serves for a code on the date of service, `warrants.w3` now serves the in-force LCD's "Coverage Indications, Limitations, and/or Medical Necessity" section. Each section carries CMS's words exactly as stored, its source proof (file, rendering hash and span), `label_status: "unlabeled"`, and the note "Unlabeled: CMS text as published. No Verzi coder label points into this section." The KB already showed this text. A section that touches licensed text, or holds a CPT-shaped code, serves no text. Coder-approved items stay the layer on top.
- **The free check names the section.** `/v1/check` lists each unlabeled section in `documentation_requirements.unlabeled_sections`: CMS's heading, the version, the archived file and a link. It carries no section text and no span.
- **The W3 second check (verify) can run on the Claude Code subscription instead of xAI's API.** `scripts.w3.verify` has a `--backend` flag (or `W3_VERIFY_BACKEND`): `claude-code` runs the signed-in `claude` CLI headless with no tools, no session persistence, an empty working directory and an allowlisted environment (the same runner the extractor uses), so no API key reaches it and nothing is billed to an API account; `xai` keeps the xAI Grok call unchanged. With no `XAI_API_KEY` set, `claude-code` is the default. The claude-code model is `W3_VERIFY_CLAUDE_MODEL` (default `claude-sonnet-5-5`, a different tier from the Opus extractor), and every requirement is a fresh, reasoning-blind call that never sees the extraction call or the document, so it stays an independent check. A usage-limit message stops the run and writes nothing for that document instead of marking requirements not_grounded. A malformed JSON reply is asked again in a fresh process (up to `W3_VERIFY_JSON_RETRIES`, default 2) before it fails closed, and the run checks up front that the CLI exists and the model id fits the backend. New `--workers N` runs up to N verifier calls at once; the DB writes stay in one transaction. The run notes record the backend.
- **The second model check no longer gates label proposals; it orders the coder queue instead.** Carrying out the 2026-10-04 verbatim decision (`docs/VERBATIM_DECISION.md`: the entailment verify leaves the authority path), `scripts.w3.propose_labels` now proposes every extracted span whose quote anchors verbatim: the stored quote equals its own rendering at its offsets, and occurs in that rendering exactly once. That holds whether `scripts.w3.verify` passed it, failed it, or never ran. A requirement a person rejected is not proposed, and a quote that does not anchor is listed and skipped. A new `--run-id` flag (repeatable) scopes a run to extraction runs. The script now always reads the archive store to check each quote. Verify stays optional and unchanged, number check included. The label queue (`/receipt/r3/labels/pending`, `/admin/api/r3/labels/pending`) lists labels whose second check failed first, then unchecked, then confirmed. Each item has a `verify` block (verdict, reason, confidence, priority) and the page has `high_priority_total`. The admin label queue shows the flag and the reason. Coder approval stays the only gate for serving, and the exact-match approval rules do not change.
- **Warrants serve CMS's words only, never a Verzi paraphrase.** `warrants.w3` always serves the passage layer: CMS's passages, with any approved coder label beside its passage. It no longer serves the older requirement list. That list's `requirement_text` was Verzi's paraphrase.
- **`requirement_text` is now always null.** This holds in `warrants.exclusions` and in `/warrant/changes`. The applicability block no longer carries the key at all (see the applicability entry). The field will be removed later. Each W3 citation now carries `quote_sha256`, the hash of CMS's words at its span.
- **`/warrant/changes` compares W3 requirements by CMS's words.** The identity is `quote_sha256` plus the coder labels (kind, rental month, service context). Each item in `added` and `removed` is now an object with those four fields. Before, each item was a paraphrase string.
- **The appeal exhibit states no Verzi conclusion.** It carries CMS's quotes, dates and source proof only. The sentences that said a requirement "does not apply" or that a denial "is therefore not supported" are gone. The draft says "Exhibit" where it said "Argument".
- **The appeal lists labeled CMS passages.** The requirements part lists the CMS passages that carry an approved coder label, each with its receipt, and shows the label as a coder label. `verzi_summary` is now always null and will be removed later.

### Deprecated
- **The unversioned twins of `/v1` paths on api.verzi.health are deprecated.** They keep working. Each response now carries `Deprecation: @1792627200` (2026-10-22) and a `Link` with `rel="successor-version"` that points at the same path under `https://api.verzi.health/v1`. No removal date is set; one will be announced at least 90 days ahead with a `Sunset` header. healthcaredata.io hosts and the `/check/{hcpcs}` web page are unchanged.
- **Three always-null warrant fields are deprecated, and will be removed on or after 2026-12-01.** `requirement_text` (W3 requirements and exclusions, and the change timeline), `verzi_summary` (the appeal exhibit's evidence) and the legacy `requirements[]` list have been null or absent since strict verbatim (2026-10-16). The OpenAPI schema now marks them `deprecated`.
- **What to read instead.** In `warrants.w3`, read CMS's words from `documents[]` and each citation's source proof. In `/rules/warrant/changes`, the legacy list still appears in `blocks.w3_requirements.from` and `.to`. Read `added[]` and `removed[]` there instead: each names a requirement by `quote_sha256`, the hash of CMS's words.

### Removed
- **`warrants.applicability.statement`.** The block no longer carries a Verzi sentence that restates the verdict ("Refill and recurring-supply documentation does not apply to X."). Strict verbatim: `status`, `applies` and the quoted basis carry the meaning, and the basis entry quotes CMS's own words with their source proof.
- **The MCP server no longer has a `get_provider` tool.** The Verzi Health MCP server is for Medicare DME coverage and receipts. The provider lookup by NPI stays on the REST API at `GET /v1/provider/{npi}`, with no change.
- **Named-system case study retired from `/resources`** — the catalog now carries methodology + product docs only. The accuracy benchmark at `/accuracy` continues to publish per-system variance; systems under private evaluation are excluded from public surfaces.

### Fixed
- `GET /v1/alerts` answered HTTP 500 for every key. It now returns your organization's watchlist alerts. This fixes the error only: the alerts are the facility watchlist alerts, not code-change alerts.
- **The refill authority quote resolves again for dates from 2024.** From PIM Rev. 12512 (in force from 2024-01-01), a line break falls inside "supplied as refills to the original order" in the stored rendering, so the `authority` entry carried no span or quote. The reader now finds the phrase with line breaks between its words.
- CMS transmittal titles: a notice whose newest stored copy has no SUBJECT field now takes its title from the newest copy that has one, the same rule the KB subject quotes use.
- **The daily archive ledger no longer posts a version loss alert for versions held through the MCD coverage API.** It was a false alert. The real check comes once revision histories are parsed.
- **A file the archive already holds, captured again as a version of another document, now takes the date its own text states.** Before, a `text_regex` rule found nothing on that path, so the version was stored undated (the DMEPOS PA list of 2018-06-01, 2026-10-14). Versions created from now on read the stored text rendering; one with no readable rendering stays undated, as before. Stored rows are not changed.
- **The updates feed, the upcoming-changes calendar and a source's document list skip defective versions.** A version whose archived file is recorded as defective (truncated, migration 166) or that is recorded as wrongly filed (migration 167) no longer appears in `/archive/changes` or `/archive/upcoming`, and no longer counts in a document's `version_count` or effective-date range. The as-of answers already skipped them.
- **Archive source URLs no longer carry a publisher's access token.** Some publishers send each file through a redirect that adds a server token to the URL (Medi-Cal's provider manual files do). The archive now drops the `access_token` parameter before it stores or logs a URL, and every page and API response that shows an archived file's source URL (the `/archive` API, KB pages, receipts, the change feed and its emails) drops it too, including for files captured before this fix. The archived bytes and their sha256 are unchanged.
- `GET /v1/rules/receipt/changes`: the `note` names only the blocks that the answer carries. Before, it always named `r2_ptp` (and, for DME, `r1_fee`), also when the answer had no such block. `r2_ptp` is in the answer only when a companion code is given, and DME `r1_fee` only when a state or CBA is given.
- **`/v1/check` says why it serves no documentation requirement when approved ones quote a policy version that is not in force on the date.** `documentation_requirements.reason` is `approved_labels_not_in_force` when nothing serves on the date of service but approved requirements exist on a version of the policy that is not in force on that date. The W3 passage block adds `coverage.labels_not_in_force`, the count of those labels. What serves does not change.
- The transmittal parser reads a column-layout change table as not read when it lost a row (a letter with no row, or a row that cannot be read). Before, the rows that were read could let a chapter's chain pass while the lost row's section answered from older chapter text. This takes effect after the transmittals are parsed again.
- **LCD and Article text captured from the Coverage API keeps CMS's characters.** The LCD and Article text rendering read CMS's UTF-8 text as Latin-1, so a curly apostrophe, a dash or a "≥" came out garbled, the same problem the NCD text rendering had. New captures now use text renderer 2.0.1, which keeps those characters. Renderings made before stay stored and unchanged, so receipts already issued still check, and text with no such characters renders the same as before. For E0601, K0001, E1390 and L1833, no served LCD or Article section had any of these characters. The only one affected was the title line of Article A58824's rendering.
- **LCD and Article text already archived from the Coverage API can now be re-rendered with CMS's characters.** A new job, `scripts.w3.rerender_coverage_utf8`, gives each stored LCD or Article version whose text came out garbled (a curly quote, a dash or a "≥" read as Latin-1) a second rendering with text renderer 2.0.1 and registers its sections on it. Sections that hold such a character could never be located in the garbled text, so they were not served; on the new rendering they register. The old rendering, its registration and its labels stay stored and unchanged, so receipts already issued still check. Approved labels carry over only when the quoted words are byte-identical in the same section; everything else goes back to a coder as pending. Dry run by default; nothing has been run against production yet.
- **The link to an archived file's original bytes now follows the same fail-closed license rule as its text.** `GET /archive/files/{sha256}`, `GET /archive/docs/{doc_id}/as-of` and the KB file page give a one-hour download link only when every copy of the bytes is held under a public-domain source. Before, only an MCD, CPT or state-terms copy held the link back, so bytes held under NUCC, ADA, NUBC, X12 or an unclassified license could still be downloaded. The sha256 and the publisher's URL still identify the file.
- **Physician utilization says why a descriptor is missing.** When `hcpcs_description` is null because the code is CPT (Category I, II or III), CDT or not a public HCPCS Level II code, the row carries `hcpcs_description_withheld`: `ama_cpt_license`, `ada_cdt_license` or `unknown_code_set`. HCPCS Level II descriptors still serve, with no flag.
- DAC facility affiliations (`/provider/{npi}` affiliations) now refresh every month from CMS's Doctors and clinicians file, with the DAC load. Before, one hand load filled them and nothing refreshed them. `/sources/dac_facility_affiliations` shows the load date and the row count.
- **The docs home now states the real label state.** Coder-approved documentation requirements are live in receipts for E0601, K0001 and E1390. They cover part of each policy, and the rest are in review. The earlier line said none were live. The page title no longer names the SDK.
- Five employer labels corrected, each with a public source: Lexington Health (SC) is Lexington Medical Center, not a PE chain; New Jersey Healthcare Specialists is Envision; North Atlanta Anesthesia Professionals is Northside Hospital; Affinity Physicians is Care New England; Privia is a public company (Nasdaq: PRVA), not a PE-backed partnership.
- The Hospitalist Medicine Physicians groups are Sound Physicians, not TeamHealth, and Galen Inpatient Physicians is Vituity. Vituity, Sound and Optum rows that had no source now name one.
- `GET /employers`: a page past the last row now reports the real `total_count`, not 0.
- `GET /archive/files/{sha256}/text` now names its reason when it holds text because a licensed source holds the same bytes: `text_withheld: licensed_text`, as on the other licensed-text holds. Before, that answer carried `contains_licensed_descriptors: true` and a reason sentence, but no `text_withheld` key. The text was held either way.
- **Receipts for E1390 and L1833 no longer fail with a server error.** Since the face-to-face/WOPD contractor answer shipped earlier on 2026-10-25, a receipt that read a captured DME MAC page needed a library the API did not install, and the request returned HTTP 500. The API now installs it.
- **The status page judges a source by its latest scheduled or live run.** A one-off backfill run (for example a Wayback history fill) or a run scoped with `--only` no longer marks a healthy source as failing, and the daily ledger no longer raises a failing alert from two failed backfill runs. NCCI PTP and Medicare Order and Referring showed as failing only because their latest run was a manual backfill. A failed scheduled run still shows as failing. The second tile now reads "DME policy documents with archived history (60 LCDs, 63 Articles) · 1,444 archived versions", so it no longer looks like a count of all policy documents. The first tile of the status page now says what it counts: "DME codes answering (HCPCS codes with a DME supplier MUE edit)".
- IP signup records are now deleted after 30 days, as the privacy policy says.
- CMS transmittal subject quotes: on about 70 older notices (2000 to 2010) the quoted subject line ran on into the paragraph after it ("This Program Memorandum (PM) outlines ...", "Transmittal 1710 has been rescinded ..."). The quote now stops at the end of the subject.
- KB transmittal subjects: two April 2003 Program Memoranda (A-03-030 and A-03-031), whose cover-page subject runs straight into the body text, no longer show a run-on subject quote. They show no subject until it can be quoted exactly.
- Kentucky, Louisiana and Wisconsin Medicaid DME fee sources are now relicensed to state_ama_ada_terms at deploy instead of waiting for the next archive run. The Kentucky workbook prints CPT 99601 and 99602 with descriptors; the Wisconsin PDF prints CPT 94762 and 94772 with descriptors; the Louisiana sources carry no CPT text but their index page shows AMA terms. Migration 222.
- The coder review queues no longer count a rejected or sent-back label or requirement as pending. Before, an item that was approved, then rejected, and whose text then changed, showed again as pending. The pending counts drop by those items.
- Licensed code text that CMS quotes (the ADA's CDT descriptor for D7880) is blanked in more shapes: when the code is written in another letter case, and when the code appears twice in a row. In Article A52512 they still hold the text, as before.
- The W3 requirement check reads every document for that descriptor, not only the listed one. A requirement whose span overlaps it is withheld.
- Manual chapters that CMS serves under two file names (for example `clm104c26.pdf` and `clm104c26pdf.pdf`) are now one document. Revisions held only under the second name answer for the chapter: for example Claims Processing Ch. 26 Rev 12671 from 2024-01-01 and Program Integrity Ch. 3 Revs 928 to 937 from 2019-11-19.
- Chapters of four more Medicare manuals now answer as-of questions from the dates of the CMS transmittals that issued them: the State Operations Manual (Pub 100-07), the General Information manual (100-01), the Contractor Beneficiary and Provider Communications manual (100-09) and the PACE manual (100-11). For example, State Operations Manual Appendix Z (emergency preparedness) Rev 204 answers from 2021-04-16.
- **The MCP `receipt` and `receipt_appeal` tools refuse a `payer` longer than 64 characters**, as `GET /v1/rules/receipt` and `GET /v1/rules/receipt/appeal` already do. The value is echoed in the answer.
- **MCP search returns article and NCD pages.** A search result may live on `verzi.health` or `kb.verzi.health`. Searching an article id such as A52467 returns that page. The server instructions say denial language is included with a plan that includes receipts.
- **MCP: calling a tool that does not exist returns a JSON-RPC error.** The response is error code `-32602` with the message `Unknown tool: <name>`, the same for every caller. Before, a caller without a key was told to get an API key. The call does not count against any limit.
- **MCP: bad arguments to a tool return a short, specific message.** The message names the argument and the problem, for example `Invalid arguments for server_info: unexpected argument 'bogus'.` or `missing required argument 'hcpcs'`. It is still a tool error (`isError: true`).
- Arizona Medicaid DME fees: the first post of the FY27 purchase workbook (effective 10/01/2026, later replaced in place by AHCCCS) now parses instead of being skipped. Its base rates and its rates by provider type (09, 18, 19, CN) are stored as printed, on both its main sheet and its "New Additions" sheet. Descriptions are never stored. Every other Arizona file keeps the same rows.
- Arizona Medicaid DME fees: the FY27 rental workbook (`FY27_Final_DMERR_WebsiteRates.xlsx`) is now filed as the FY27 rental document instead of the purchase document, so its 630 rental rate rows parse. Every other AHCCCS file keeps its document and dates.
- **Georgia Medicaid DME fee schedule and manual: the pinned files now get a version on capture.** The archive names a direct download from its URL as written, with `%20` escapes, so the date patterns now accept `%20` as well as a space. The first prod capture stored both current files without a version.
- **A `payer=medicaid` receipt no longer reports Medicare crosswalk progress as its own.** `meta.claim_type_status` is `not_yet_available` with a `claim_type_reason`, and each `meta.claim_types` entry has `status: not_yet_available`, `served: false` and a `reason`, with no `rows_tagged` or `rows_filled`. With a `claim_format`, `usable_for_claim_types` is empty and no partial-answer note is added. With the `denial` or `claim_item` filter, `meta.denial` and `meta.claim_item` carry only the id asked for, `status: not_yet_available` and a `reason`. Before, these fields were read from the Medicare crosswalk and said `filled` and `served: true`. `payer=medicare` and `payer=medicare_advantage` answers are unchanged. The MCP `receipt` tool answers the same way, and its `payer` description now names `medicaid`.
- **Michigan Medicaid DME fees: April 2023 now parses.** All 14 quarterly DMEPOS fee workbooks MDHHS lists (January 2023 to October 2026) now parse. The April 2023 workbook prints rate and coverage end dates in its effective-date column; those rows now carry the stated end date, and the file is no longer skipped.
- State Medicaid fee rows now store a spreadsheet amount as the sheet prints it. A cell formatted with fixed decimals (for example `#,##0.00`) is rounded half up to those decimals, so a rate shown as 532.08 is no longer stored as `532.0799999999999`. Cells in General format keep the stored number. The parser version is now `medicaid_state_fees/v2`.
- State Medicaid fee rows now carry the bare code and its marker. A code printed with a trailing mark (`K0738*` in Ohio's oxygen sheet, `A4928*` in Michigan's 2023 files) keeps its printed code and gains `code_bare` (`K0738`) and `code_marker` (`*`), so a lookup by the bare code finds the row. A marked cell whose bare part is not a HCPCS or CPT code still fails the file closed. The parser version is now `medicaid_state_fees/v3`.
- Virginia Medicaid DME fee schedules (DMAS Appendix B) now parse. DMAS prints a few code cells per edition with a modifier glued to the code (`E0272RR`, `E1392RR U1`) or a space inside the code (`E 1405 RR`, `E 1820`), and every edition was skipped. Those rows keep the code as printed, are found by the bare code (`E0272`, `E1405`) with their modifiers, and record which repair read them in a new `code_repair` field. Any other misprint still skips the file.
- **`GET /v1/rules/receipt?payer=medicaid` no longer returns Medicare data.** Before, a Medicaid request got the full Medicare receipt with one note that the payer was not served. Now every receipt in a Medicaid answer (except `r3`, which a later entry fills from the state's own manual) has `status: not_yet_available`, a `reason` (`medicaid_source_not_served` or `medicare_program_rule`), a `note` and a null `source_program`. `usable_for` is empty and `confidence.overall` is `unknown`. The payer value is matched in any case and echoed as `medicaid`. `payer=medicare` and `payer=medicare_advantage` answers are unchanged. If you read Medicare receipts under `payer=medicaid`, ask for `payer=medicare`. The MCP `receipt` tool answers the same way.
- Washington Apple Health medical equipment and supplies fee files from 2020-07-01 on now parse. HCA prints a few codes (A9286, A6609) on two rows with no column to tell them apart; each row is now kept and numbered in file order (`variant_ordinal`), with its sheet and row locator. Every WA edition from 2019-04-01 to 2026-07-01 parses.
- MIPS PY2023 scores, missing from releases 2025-12 to 2026-05, and the PY2017 and PY2018 scores of the 2022-09 release are now served by performance year.
- Mississippi Medicaid exclusions load again. The state moved its Sanctioned Providers List to a new page, so the monthly load had stopped finding the file. It now reads the current list from the Division of Medicaid Resources page.
- **NCD sections with curly quotes and other non-ASCII characters now serve.** The NCD text rendering read CMS's UTF-8 text as Latin-1, so a character such as the apostrophe in "patient’s" came out garbled and the section could not be registered. NCD 240.2 (Home Use of Oxygen) version 2 served only its Benefit Category and Item/Service Description; its Indications and Limitations of Coverage now registers too. The NCD text renderer is now version 1.0.1. Renderings made before stay stored and unchanged, and an NCD whose text is plain ASCII keeps its existing rendering and registration.
- **Need map 7.1 and 7.2 no longer share one citation credit.** Both still match every held HCPCS quarter file (`hcpcs:{yyyy}Q{q}`), so both stay held. A receipt citation under the modifiers group credits only 7.2; any other citation of that file credits only 7.1. The admin "shares its source" flag no longer applies to that pair. The Data Inventory sample does not name modifiers, so 7.2 will read not_linked there until a sample (or real receipt) includes a modifier; that is the honest answer.
- Code-watch alert emails and webhooks now include LCD and Article changes for a watched code, the same codes `/archive/changes` lists in `affected_codes`. Before, the notifier mapped codes only through Verzi's labeled requirements, so a new LCD or Article version found through CMS's own code table never reached the code's watchers. Both now use one mapping.
- **Prior authorization receipts for 2022 to 2024 dates of service now answer from CMS's list instead of "not determinable".** The 2022 editions of the Required Prior Authorization List print some Effective Date cells as state groups, each followed by its date ("NY, IL, FL, and CA: 04/13/2022 ... Nationwide: 10/11/2022"), with the state list and the date wrapping over lines. The parser now reads each group as one phase, with CMS's states, CMS's printed date and CMS's words for that group. For example, L1833 on 2022-05-01 is listed for NY and not listed for CO, and the answer quotes the later nationwide phase. A cell the parser still cannot read answers "not determinable", as before.
- `GET /v1/rules/receipt` is faster. The manual passages of `receipts.rule_passages` read each manual chapter once per request, and the transmittal index read no longer computes the whole version view. No answer changes: a replay test pins the passages of E0601 and 99283 on two dates of service.
- Receipts and KB code pages no longer list proposed LCDs as policies that govern a code. CMS's coverage export gives each proposed LCD revision its own number and code list (for example DL33318, a proposed Knee Orthoses revision that lists L1833, and DL33797, a proposed Oxygen revision that lists E1390). A proposed LCD has no effective date and governs no claim, so only final LCDs are listed now. Receipts serve the final DME MAC LCD and its Articles for the date of service, as documented in `docs/W3_SCOPE.md` §8.
- **The KB code page's prior authorization line now says when a phase starts after the date of service.** For L1833 on 2026-10-24, the line used to read "Not on … on 2026-10-24" and then quote the "10/28/2026 Nationwide" cell, which looked as if that phase were already in force. It now gives the reader's reason first: "The list names this code with an effective date of 10/28/2026, after the date of service." Then it quotes CMS's whole Effective Date cell, labeled as having no phase in force on that date, so a cell with several later phases keeps all its words. The list version and the phase were already chosen by the date of service.
- When a held list version's rows were refused by the current parser (`parse_run` status `skipped`), the `prior_authorization` reason used to say Verzi "could not read its rows". It now says the rows "have not been read yet: the current parser did not accept this file's layout", because a later parser version reads the file again.
- **`GET /rx/asp` no longer serves or searches the CPT descriptor.** The Part B ASP file carries about 48 CPT codes (vaccines and immune globulins, 90xxx) beside the HCPCS Level II J-codes. A CPT short descriptor is AMA licensed text. For a CPT row, `short_description` is now null, and the `q` search reads public HCPCS Level II descriptors only. A CPT row of a quarter before 2022-01-01 is not returned, and the new `license_scope` field says why. Payment limits for HCPCS Level II codes do not change.
- Medicaid State Drug Utilization Data (`rx_sdud`) now loads one year per pipeline item, 2019 onward. The quarterly run on 2026-10-01 loaded every year in one transaction and stopped with nothing loaded. A year CMS republishes under a new file name loads again, and its old rows are replaced.
- **Georgia CON filings are pulled again.** Georgia DCH moved its weekly tracking report to a new download path and changed the report's layout in early October 2026, so the `ga_con` signals source had failed on every run since Oct 8. It now finds the report under either path, reads the application date from "Filed:" as well as "Received:", knows the renamed sections ("Recently Approved Applications", "Recently Denied Applications", "Disqualified Applications", "Appealed Determinations", "Expired Letters of Intent"), and closes an entry at each section heading so determination text is never added to the entry before it. Tests use saved copies of the current page and report.
- **The box signals run no longer misses a day when the box is asleep at 6:00 AM.** `building_permit/box/run_daily.sh --catch-up` runs the day's job at the first 15-minute cron slot after 6:00 AM MT that the box is awake, and does nothing once any run has started that day.
- **Sign-in and signup codes now respect bounces and complaints.** Verzi Health no longer sends a sign-in or signup code to an address that bounced permanently or marked our mail as spam, and those events from sign-in, signup and contact-form mail are now recorded the same way as for update subscriptions.
- The transmittal parser (1.4.1) counts a change table row that names a part of the manual and no numbered section (a table of contents, an exhibit, an addendum, an appendix). At 1.4.0 such a row made the whole table read as no rows. This takes effect after the transmittals are parsed again.
- The transmittal parser (1.4.1) no longer reads a nested row whose section numbers do not nest, such as `16/60/1/...` written for section 60.1. Read as written, the row named the wrong section, so the manual section reader could pass a section the transmittal changed. The table now reads as no rows, and the reader answers `unknown` (`chain_incomplete`) for a section whose revision chain needs that transmittal. This takes effect after the transmittals are parsed again.
- **The appeal exhibit no longer shows Verzi's summary of a requirement as cited text.** When the documentation-requirement block serves its older shape, each requirement's text is Verzi's summary, not CMS's words. `GET /rules/warrant/appeal` and the MCP `warrant_appeal` tool now put that text in a new evidence field, `verzi_summary`, and leave `quote` empty. The draft prints it on a line that starts "Verzi summary (not CMS's words):", with no quote marks. The next line points to CMS's words at the archived receipt. "Cited text" now appears only before a slice of the archived rendering.
- **An older LCD version in the KB no longer shows the newest version's lists.** CMS's download lists codes and related Articles for the newest version only. On an older version, the KB now says that no list is held for that version, and shows none. The version line names no companion Article from that list. The receipts line names the version its related Articles are for.
- **Eleven held CMS Order and Referring editions get versioned** (after their reversion runs). Ten 2021-07 to 2022-03 Wayback files and one 2024-05-13 live file were stored but not versioned, because their names were variants: lower case, `(1)`, `(2)`, `_0` or `_2`. The earliest edition the ordering physician answer can use becomes 2021-07-26.
- **The DMEPOS fee lookup answers a PEN code in a quarter where CMS stated there is no PEN update.** CMS publishes the PEN fee file only in some quarters. In 13 other quarters a CMS transmittal states there is no PEN update. The fee answer for those quarters comes from the last PEN file, and its `as_of` says `rule: member_continued` with the transmittal and its exact sentence. A quarter with no such statement still answers nothing.
- **The appeal exhibit no longer prints "None" for a policy-text exemption.** An exemption's evidence named its authority as "lcd:X §None (None)" and its version as None. It now names only the fields the basis has (for an exemption, the document id), takes the version in force from the exemption's as-of, and leaves out the version line when no version is known.
- **No DMEPOS fee is served where a CMS revision file covers the date and is not parsed yet.** Before, the fee answer served the unrevised amount. Three revisions are covered: CMS-1687-IFC (rural and non-contiguous state cells, June 2018), CMS-5531-IFC under the CARES Act (non-rural contiguous state cells from 2020-03-06, and every state cell from 2020-04-01 to 2020-06-30; for example, E0601 RR in Connecticut on 2020-03-15 served 40.37, while the July 2020 file states 55.98), and the revised 2022 file (AK, HI, PR and VI cells, 2022). The warrant's fee block answers `unknown` with `reason_code: revision_not_served`, naming the rule and the held file. `/rules/dmepos/fee` answers 404 whose detail has `status: "unknown"` and names the revision. The appeal timeline marks such a date unknown, not changed.
- **Leapfrog grades no longer disappear after one failed table check.** `GET /hospitals/{ccn}/leapfrog` and `/leapfrog/history` check once that the Leapfrog table exists. A busy pool or a dropped connection during that check used to be remembered as "no table" until the next restart, so the grades were hidden. A failed check is now not remembered, and the next request checks again.
- **The ordering physician answer no longer says "not on the roster" for a date the roster change table does not reach.** Nine CMS Order and Referring editions (2023-06-01 to 2023-07-03) are parsed, but the change rows begin with the 2023-07-06 edition. For a date of service in that window, provider standing and the warrant's ordering block answered "not on the roster" for every NPI. They now answer `unknown` with `reason_code: edition_before_change_baseline`.
- **The April 1 ICD-10-CM updates of 2022, 2023 and 2024 are versions of their fiscal year.** CDC NCHS posted April 1 updates during FY2022, FY2023 and FY2024 (the 2022 order file, and the 2023 and 2024 code description, table and index, and addendum files). The `icd10cm_nchs` source now stores each as a version of its fiscal year document from April 1 to September 30, so `GET /v1/archive/docs/{doc_id}/as-of` answers those dates from the April file once the approved `--backfill` run stores them. Stored rows do not change until that run.
- **ICD-10-CM code files named with a slash in the update date get a version.** The FY2023 and FY2024 files of the `icd10cm` source have names such as `...-updated-01/11/2023.zip`, and the versioning rule read none of them (174 files had no version). The rule now reads the update date with its slashes, so `GET /v1/archive/docs/{doc_id}/as-of` answers dates from 2022-10-01 to 2024-09-30 once the approved `--reversion` run gives those documents a version. Stored rows do not change until that run.
- **An MUE table that CMS posted for two quarters with the same bytes now answers for both.** CMS posted the dme_supplier tables for 2020Q3 and 2020Q4 byte for byte. `/rules/ncci/mue` and the W2 edits block answered 2020Q4 dates as held but not read. They now answer from that table, citing the 2020Q4 version and its own file.
- The free E0601 KB page (`/kb/free/E0601`) keeps a signed-in reader's org name and Log out. A signed-in reader without the KB plan, or a key over its daily limit, reads the free view without spending a daily request. A shared cache never keeps a served sections response.
- **A KB code page no longer prints an empty rendering hash.** The receipt of an in-force document with no approved label said "Text rendering sha256 ." when the archived file has no stored text rendering (a Coverage API version before its render pass, such as LCD L33718 version 52). The receipt now says "No text rendering is stored for this file yet." The signed-in receipt says it in similar words.
- **W0 keeps a reinstatement that OIG posted after the LEIE snapshot.** The archive dates the monthly reinstatement files by their month since 2026-10-08. The exclusion reader took that month start as the version's posting date. A LEIE snapshot taken inside the month then outranked the file, and a provider reinstated after the snapshot date stayed "excluded". We found this on 2026-10-09 with the 2026-09 file: the reader still excluded a provider on 2026-09-24 whom OIG reinstated on 2026-09-23. The reader now takes the later of the version's stated date and the first day of the following month as its posting date. So the reinstatement file wins over any snapshot taken in its own month. A snapshot from a later month still wins. Versions that carry a Last-Modified date from before the rule keep that date.
- **Coverage API documents carry their titles.** `archive_doc.title` was never set for LCDs, Articles and NCDs captured from the CMS Coverage API, so the KB pages and the coverage warrant showed ids only (for example `article:52467`). A one-time reader records the title each document's own stored JSON states (`data[0].title`), the publisher's string trimmed at the ends and nothing else, from the highest held version. A document first captured later stays untitled until the reader runs again.
- **W2 PTP answered not_edited for pairs CMS edits, when CMS lists the pair twice with the same effective date.** CMS's cumulative PTP files carry, for some pairs, a line deleted the day it starts (modifier indicator 9) and a live line. The stored table kept one row per (pair, effective date), so the live line was dropped at load: 3,948 live edits across the 2026Q4 files, 3,847 of them hospital. The row identity is now (pair, effective date, deletion date), both lines are stored, and the reader picks the one in force. Parts loaded before this fix answer `unknown` ("parsed before the duplicate-key fix; re-parse pending") until they are re-parsed; they never answer `not_edited` from the old rows.
- **Coverage API Article versions answer by the dates CMS states in them.** Article versions captured from the CMS Coverage API were stored without their effective dates, so a date of service could find no version in force (for example article:52467, the CPAP article, on 2026-09-15). Once the stated-dates reader runs after this release, the archive reads each held version's own stored JSON for the window CMS states (article_eff_date, article_rev_end_date) and uses it where the stored row has no date. Stored rows are not changed. Article versions whose JSON states no effective date stay undated.
- **Coverage API Articles carry their effective dates, and missing DME LCD and Article versions are captured by number.** Articles from the CMS Coverage API were stored without their effective dates, because the Article fields were not read. A DME LCD or Article version that CMS's own revision history names, and that the archive did not hold, is now fetched by its version number (131 of the 134 such versions were served on 2026-10-08). A document that still holds an undated version is held back until that version is dated, because a dated past version beside an undated current one would answer for today. Until the capture runs, some dates answer an older version or no version (for example A52457 on 2025-06-15 answers none; version 63 was in force).
- **Excel members of archived NCCI and DMEPOS files now parse.** The parser stores each archived file under a name with no extension, and the Excel reader refused those names, so every Excel-only member was skipped. For NCCI PTP that meant practitioner parts f1 and f2 of 2026Q3 and 2026Q4, which W2 answers as `unknown`. The reader now opens the file directly. The affected quarters answer once they are re-parsed.
- **W0 exclusion answers past windows for reinstated providers.** A provider excluded and later reinstated is no longer in the current LEIE file, so a date of service inside the old exclusion window used to answer "not excluded". The OIG monthly reinstatement files (every month from 2015-01 is retrievable, most from the Wayback Machine) answer it once they are captured and parsed. For the same exclusion, the newer of the LEIE file and the reinstatement file wins. When the archive cannot prove the answer (a provider who left the LEIE file with no reinstatement file held, or a date before the first live snapshot with a reinstatement month not yet parsed), `excluded_on_dos` is null with `status: "unknown"` and a reason. Each exclusion record names its archived file in a new `source` field. A W0 block whose exclusion answer is `unknown` rolls the warrant's `confidence.overall` up to `unknown`.
- **The sample integration page no longer shows CPT-licensed rationale text.** The blocklist filters "Code Descriptor / CPT Instruction" from the MUE cell display.
- **A long KB search uses its first 5 words.** A pasted CMS title of more than 5 words found nothing. The search now uses the first 5 words and says so. The help line under the box says that spaces inside a code do not count (e 0601 finds E0601) and that a word of one letter is left out (x-ray finds ray). A KB page's canonical link carries `dos` only when it is a date (YYYY-MM-DD).
- **Receipts no longer show an observed window that ends before it starts.** A version captured from the Wayback Machine (or loaded by a backfill), and any version that states its own dates, now shows no `observed_to`; only undated live captures carry an observed window. A Wayback or backfill version's `observed_from` is the time we stored it, and a dated version can be captured out of stated order, so an end date computed from a later live capture could fall before its start. Answers do not change: the observed window decides an answer only for live captures.
- **Manual chapter dates come only from the same manual's transmittal.** The archive dates a CMS manual chapter revision from the transmittal its "Rev." number names. Before the 2020 unified sequence, each manual numbered its own transmittals, so one number can name a Benefit Policy, a Claims Processing and a State Operations Manual transmittal. Two Benefit Policy chapter 15 revisions (Rev. 235 and Rev. 241) carried State Operations Manual dates; they now show no date until their own transmittals are held. Pre-2019 transmittals with upper-case file names (R3444CP.pdf) are now read as the same documents as the live ones.
- **Edits fail closed when a CMS file is missing.** The warrant's edits block (`w2`), `/rules/ncci/ptp` and `/rules/ncci/mue` answer "not edited" or "no MUE" only from files that are held and parsed. PTP answers from the latest quarter held when it is complete; otherwise from the newest held file that carries the pair; otherwise `unknown` (PTP `edited: null`, MUE `mue_value: null`) with a `reason` naming the missing parts. Every answer, negative included, now names the files it relied on in `checked` (rule, quarter, doc_ids, version_ids). Before this fix, a pair in an unparsed part (for example practitioner part 1 in 2026) answered "not edited" with no receipt. **Client change:** the `/rules/ncci/mue` 404 `detail` is now an object (`message` plus `checked`), not a string. An unknown edits part now makes the warrant's `confidence.overall` read `unknown` (the `w2` entry of `confidence.blocks` adds `mue_status` and `ptp_status`), and `/rules/warrant/changes` reports `changed: null` (and `any_change: null` when nothing else moved) when either date is unknown, instead of `false`.
- **The printed appeal exhibit carries no site chrome.** Printing a KB page no longer prints the top bar (brand, theme button, "Get a key") or the find-in-policy box and its yellow marks.
- **The updates feed shows one entry per document per capture run.** When one run captures several new versions of a document, only the newest is news; the others move to Newly archived. RSS, the weekly digest, alerts, and webhooks follow the feed. This removes about 1,750 identical Noridian rows and the skipped versions of MCD Articles from the 30-day feed.
- **Updates feed headlines name files and pages in words.** Quarterly files read "OPPS Addendum Q, 2026Q4" and "DMEPOS fee schedule, 2026Q4"; downloads carry the publisher's file name ("Medicare Coverage Database download current_lcd.zip", "FDA NDC Directory file ndctext.zip"); CMS pages read "CMS page: code sets". Word slugs show their hyphens and underscores as spaces. Citations and host names keep their characters.
- **One feed entry for an LCD change, not two.** CMS's revision-history file for an LCD or Article, captured in the same run as the document, no longer shows as a separate news entry; the document's entry carries CMS's note. It reads "LCD L33824 revision history" under Newly archived.
- **Source archive page in plain words.** The search box asks for a "document id", and an effective date CMS did not state reads "not stated" instead of a blank cell.
- **Better free samples on KB code pages.** The one free sample passage per code is now chosen by a stated rule: an LCD before an Article, a passage that stands on its own before a fragment (never one that ends pointing at text below it), and coverage criteria before order and documentation rules. E0601 now shows the re-evaluation rule (days 31 to 91); K0606 shows its first coverage criterion.
- **KB pages after hostile pass 3.** A code page whose approved passages are not in force today names the dates that show the sample, as links ("See the sample at: 2020-04-03, version 35"). The sample integration page's policy-passage cell uses the same sentence instead of "Not held yet" when approved passages exist on other dates. The sample caption states CMS's window: "in force since 2020-01-01" for an open window, "in force 2020-04-03 to 2021-08-07" for a closed one. CMS's revision notes keep their line breaks. The KB index range ends with "today" when a version of the document is in force today, so a current version with no CMS date no longer reads as retired.
- **The sample integration page loads fast after the first visit.** Its three code tables cache for five minutes per date of service, so a warm load skips about 9 seconds of database reads. A render where any cell could not be read is never cached.
- **A KB code page names each related Article once.** CMS's related-documents file can list one Article twice for an LCD version. The code page's list of Articles for each LCD now names it once, in CMS's order.
- **A retired document no longer answers "in force today".** A version with a stated effective window is now in force only inside that window. Before, a fresh capture of a retired LCD, Article, or quarterly file (stated end in the past) resolved for dates after its end. The as-of answer (`GET /v1/archive/docs/{doc_id}/as-of`, warrants, KB pages) for such a date is now `none`, with a new `reason` field: `before_first_stated_start`, `after_last_stated_end`, `gap_between_stated_windows`, `not_observed_on_date`, or `no_versions`. Versions with no stated date still resolve by their observed window.
- **A real effective date on the capture day still counts.** Only sources whose archive manifest dates versions by our own fetch treat that date as no date. Any other source's effective date is the publisher's, so a quarterly file effective October 1 and first captured October 1 shows as news.
- **The latest pipeline run names its source** on the status page.
- **`GET /v1/archive/changes` rejects an unknown `source_id`** with HTTP 422 instead of returning an empty list.
- **The updates feed shows changes, not first captures.** A version is news when the document was held before and this version is newer than every version held before it, in the publisher's order (effective date, then version number, then observed time). A retroactive revision is still the newest version, so it is news. A document's first capture is news only when its effective date falls in the window or later. First captures and older versions filled in by a later crawl sit behind a new "Newly archived" chip, out of "All", and never ride RSS, the digest, watch-a-code alerts, or webhooks. `GET /v1/archive/changes` takes `kind=news|newly_archived` and `category=`, both filtered before the row cap, and every row carries `news` and `newly_archived`. RSS guids are unique per version.
- **Readable names for the rest of the feed.** Transmittals for the Medicare Secondary Payer, Financial Management, General Information, State Operations, Communications, Managed Care, and Demonstrations manuals carry their manual name; any other transmittal reads "Transmittal {number}". Competitive Bidding pages read the site's own category path ("Competitive Bidding: Educational Information / News and Bulletins"), and pages known only by a document key read "Competitive Bidding document {key}".
- **Status ledger in plain words.** Each run shows its source name, the time in UTC, and one fixed sentence ("Checked. Nothing changed.", "The latest run failed."). Raw errors stay in `GET /v1/archive/runs`, which adds `source_name` and `summary`.
- **Faster feed and status.** The change feed, the upcoming list, and the source catalog are cached for two minutes.
- **Archive page and as-of JSON.** The archive page names documents ("LCD L33718"), drops internal ids, shows plain dates, and links the KB page. The as-of JSON's `kb_url` keeps the date (`?dos=`). Feed receipts name the source host, and history entries say "version", not "new version".
- **Revision notes for current policy versions.** LCD and Article versions captured from the Coverage API now carry CMS's own revision-history entry for that version (for example L33718 version 52, R11, 2024-01-01), read verbatim from CMS's revision-history endpoint. Before, the newest version of a policy showed no note while older versions did. 126 current versions gain a note. The quote carries its own receipt: the sha256 of the archived revision-history file it comes from, on the feed's receipt and as `note_sha256` on webhook events.
- **The honest-empty line says only what we know.** Where Verzi extracted the publisher's note and found none, an entry reads "CMS published no revision note for this change." Where no extraction runs for the source, it reads "No revision note is extracted for this source." Applies to the feed, calendar, digest, alerts, RSS, and the calendar export.
- **KB links that work.** Feed receipts and the as-of JSON link to `/kb/lcd/{n}` or `/kb/article/{n}`, and only when a KB page exists. The as-of notice names the KB page only when there is one.
- **No raw ids or internal numbers in headlines.** An entry with no title or label reads as its source's name plus the id's own tail. The gain line shows the publisher's version, or just "new version", never Verzi's internal version id.
- **Failing sources say so.** The status page reads each source's latest finished run. A failed, partial, or zero-capture run shows a "failing" pill with the run's own error line, as plainly as "fresh".
- **A complete source is not "failing".** Some sources skip files we already hold. When every file is held, the run finds nothing new and records that. The status page and the daily ledger no longer read that run as a moved page. CMS DME supplier utilization (44 of 44 files held) and Medicare provider enrollment (2 of 2) show their real state.
- Fixed: manual-chapter effective dates from transmittals now require publication agreement (migration 135); seven cross-publication false dates retracted to honest unknowns.
- **`/sources` understated our own freshness on 20 datasets we hold and serve.** The page reported "never loaded" for Part D Prescriber (102.9M rows), Physician Utilization (29.1M), Open Payments (27.7M), HCRIS, MA Star Ratings, HSAF, CDC PLACES, ClinicalTrials.gov, HRRP, IPPS Impact, the VBC/ACO layer, the CBSA crosswalk and population files, Dartmouth, AHRQ SDOH, Medicare Geographic Variation, CMS POS service lines, Medicaid SDUD, the SEC 8-K feed, and the employer typology crosswalk. Only the pipeline ever wrote `last_loaded_at`, and it writes it only for runs it wrapped. A loader run by hand never reached it, and neither did a yearly source that had already loaded its last published year: the Checker finds nothing new, so the loader never runs, so the page keeps saying never. Every registered loader now stamps the catalog itself when it succeeds, and a test fails the build when a new one does not.
- **`/sources` published per-run numbers as record counts.** The page claimed we hold 73 hospitals, 17 nursing homes, 6 hospices, 3 long-term care hospitals and 8 clinicians. Those were the counts of CSV files inside the last quarterly CMS ZIP. NPPES showed 73,243, the size of one weekly delta against a 9.7M-row registry. `last_record_count` now means what it says: the rows a source currently holds. The per-run number stays in the load history at `/sources/{source_id}/history`.
- **DAC stopped reporting its own refreshes.** The pipeline calls the source `dac`; the published catalog row is `dac_providers`. Every audit and freshness write went to a source_id no row has, and an `UPDATE` that matches nothing is not an error. So `/sources` froze DAC at its last manual load while the monthly pipeline kept reloading it, and `/sources/dac_providers/history` showed no runs at all. The two ids are mapped explicitly now, and a mismatch is a test failure rather than a silent no-op.
- **`GET /rx/demand` county and metro rows now cover rural counties and Connecticut.** A prescriber's county was taken from the ZIP-to-CBSA crosswalk, so prescribers in about 1,200 counties outside any metro or micro area had no county row, and Connecticut had no county or metro rows at all. The county is now the one that holds most of the practice ZIP's population, and the metro is that county's CBSA.
- **Paging through a list endpoint no longer repeats or skips rows.** Many list endpoints sorted on columns that tie, such as participant counts, dollar amounts, distance, or last name. Postgres returns tied rows in no fixed order, so `limit` and `offset` pages could return the same row twice and never return another. Every paged query now ends its sort on a unique key. This affects `/rx/employers`, `/rx/employers/metros`, `/rx/asp`, `/rx/biosimilars` and the other `/rx` lists, facility searches by radius, Part D and physician utilization, Open Payments, OIG exclusions, HPSA, DAC, PECOS, clinicians, HCRIS, community health, market opportunity, signals, and the VBC lists.
- **`/status` and `/sources` no longer flag healthy CMS sources as critical.** Eight CMS Archive sources declared a `weekly` update cadence. That is how often the pipeline checks them, not how often CMS publishes, and the freshness thresholds read that field. Every one of them turned critical between releases while working correctly, leaving `/status` red with 10 critical sources. Measured from the CMS archive API over the last 13 releases, the median gap is 91 days for hospitals, long-term care, inpatient rehab and hospice, 84 days for home health and dialysis, and about 30 days for nursing homes and doctors/clinicians. Cadences now match the publisher, so the two monthly sources stay on monthly thresholds rather than being lumped in as quarterly. `/status` is green with zero critical sources. How often the pipeline checks is unchanged.
- **The homepage no longer shows invented numbers.** It carried a hardcoded fallback row count, source count, facility count and clinician count, plus sample market-share and community-health panels that named real health systems beside fabricated figures. The fallbacks rendered whenever `/platform/stats` was unreachable, and the sample panels rendered always, so a visitor could not tell a real figure from a placeholder. The page now renders live figures, and omits a count entirely when the API does not answer.
- **Column lookups now fall back to a case-insensitive match.** CMS re-cases column names between files: the MSSP savings rate is `Sav_rate` in twelve files and `Sav_Rate` in PY2021, and the ambulance expenditure is `CapAnn_AmbPay` except in PY2014, where it is `CapAnn_ambpay`. The loader's fixed set of name variants missed both and produced silent NULLs for a whole year. Found by checking every field against every file header rather than by spot-checking.
- **ACO REACH participant records were dropped on load.** The table held a unique key on ACO, performance year, and participant name. CMS publishes one row per participation spell instead. A clinician whose capitation arrangement changes mid-year is several rows with several start dates. The key discarded 16% to 33% of each year's published rows. The key is removed. The loader now collapses only rows that are identical in every column. A REACH participant list is a set of dated spells, not a set of names.
- **Hospital affiliations were empty on DAC and dossier endpoints** — CMS removed the `hosp_afl_*` columns from the DAC national file in 2026; the affected endpoints read those columns and silently returned no affiliations. They now read the Facility Affiliation dataset (2.25M rows). `GET /dac/hospital/{ccn}/affiliates` matches providers through the same dataset.
- **Weekly CMS quality data resumed after a months-long silent stall** — CMS replaced its provider-data archive API in 2026. The old endpoint froze its index around Feb–April and later returned 503, so the weekly sync saw "no new data" and hospital, nursing home, hospice, and other CMS quality sources stopped updating (hospitals and hospice last refreshed 2026-02). All downloaders now use the new archive API, and the stalled quarters are backfilled.
- **`/status` and `/sources` no longer hide staleness on sources without load-tracking history** — a source with no recorded load timestamp used to classify as "never loaded" and was excluded from the health rollup, which is how the stall above went unflagged. A source that has never recorded a load is now judged by its age since registration on the same cadence thresholds, so it turns stale/critical like any other source.
- **`GET /hospitals/{ccn}` returned 500 for every hospital from ~2026-07-23 to 2026-08-13** — the hospital deep-dive code deployed on 07-23, but its database migrations were not applied to production, so every detail request failed on a missing table. Search, history, and other endpoints were unaffected. Fixed by applying migrations 045–059 and loading the six new data sources (HRRP, CMI/wage index, service lines, CBSA population, HCRIS deep worksheets, ClinicalTrials.gov) to production. Two guards now prevent recurrence: migrations run automatically before each deploy and abort it on failure, and a synthetic probe checks the public endpoints every 5 minutes and alarms on consecutive failures.
- **Hospice facility count corrected: 8,391, not 14,067** — the 2020-08 and 2020-11 CMS hospice files quote CCNs and ZIPs in Excel's text-forcing format (`="011500"`). The loader stored the wrapper literally, which created 5,676 duplicate facility rows under phantom IDs and ~823K quality/patient-experience rows that never joined to the real facility. The duplicate rows are removed, the historical measure rows are re-keyed to the correct CCNs (no history lost), and the loader now strips the wrapper so reloads cannot reintroduce it. If you had paged through `/hospice`, roughly 40% of rows were duplicates of other rows; per-CCN lookups for the affected facilities previously required the wrapped literal and now work with the plain CCN.
- **HCRIS `net_income` was silently wrong for every hospital** — the worksheet coordinate pointed at line 02500 ("Other Income"), not the actual Net Income line (02900). For a hospital with material non-operating income, this understated net income by orders of magnitude. Also fixed: `total_discharges` was reading a Medicare-days count instead of an actual discharge count, which meant `cost_per_discharge` was calculated against the wrong denominator for every loaded report. Both are corrected in the loader; existing rows are corrected on the next reload.
- **HCRIS "latest report" queries could nondeterministically return a stale, superseded report** — `/cost-reports/{ccn}` and related endpoints picked the most recent report by fiscal year end with no tiebreaker, so a hospital with two report submissions for the same fiscal year (e.g. an amended resubmission) could have either one served depending on unspecified row order. Now breaks ties by preferring the higher `rpt_rec_num` (more recently processed). Affects roughly 13% of loaded report-years.
- **HCRIS balance sheet quick ratio now uses the standard definition** (current assets minus inventory and prepaid expenses) rather than summing individual line items, which understated it.
- **HCRIS square footage bounded against known data-entry anomalies** — a small number of source submissions carry physically-impossible square footage values (one report showed 22 billion sq ft; a worksheet subtotal line was being read as if it were a single cost center, showing up to 200M sq ft). Both are now excluded/nulled rather than surfaced.
- **The DMEPOS fee lookup answers 2022 Q2 and Q3 dates from the January 2022 state table** (after its reversion run). CMS posted no DMEPOS fee file for April or July 2022, and transmittals R11292CP and R11451CP state there are no updates to the DMEPOS fee schedule file for those quarters. The answer's `as_of` says `rule: member_continued` with the transmittal and its exact sentence. For certain codes in Alaska, Hawaii, Puerto Rico and the U.S. Virgin Islands, CMS's revised 2022 file (DME22-R) changes these amounts and is not applied yet, so those 2022 amounts are not final.
- **The archive file text endpoint answers 503, not 500, when the stored rendering cannot be read.** `GET /v1/archive/files/{sha256}/text` (and `/archive/files/{sha256}/text`) answered 500 when the S3 read of the rendering failed or timed out. It now answers 503 with `Retry-After: 5`. The log keeps the error type and code only.
- **A payer the receipt does not serve no longer gets Medicare data.** `GET /v1/rules/receipt` with a `payer` other than `medicare`, `medicare_advantage` (alias `ma`) or `medicaid` used to return the full Medicare receipt under a payer block that said `not_yet_available`. Now every receipt in that answer has `status: not_yet_available`, `reason: payer_not_served`, a `note` and a null `source_program`; `usable_for` is empty, and `meta` says the claim type is not served, with no row counts. If you sent another value and read the Medicare receipts, send `payer=medicare`.
- **`payer=Medicare` in any case is Medicare.** `medicare` is now matched in any case, with spaces trimmed, as `medicaid` and the Medicare Advantage aliases already were. Before, `payer=Medicare` was reported as a payer that is not served.
- **An empty `payer` is a 422** on `GET /v1/rules/receipt` and `GET /v1/rules/receipt/appeal`, and an error on the MCP `receipt` and `receipt_appeal` tools. Leave `payer` out for Medicare. A `payer` longer than 64 characters is a 422 on both routes.
- **`GET /v1/rules/receipt/appeal` builds no Medicare exhibit for a payer that is not served.** Before, any payer other than Medicare Advantage, `medicaid` included, got a Medicare redetermination exhibit. Now the answer is `status: no_exhibit` with a reason that names the payer.
- **The not-started answer carries no Medicare crosswalk counts for a payer that is not served.** For an unserved payer and a claim type that is not started, `meta.claim_types` entries no longer carry `rows_tagged` or `rows_filled`. `meta.claim_type_reason` names the payer, and each entry carries a reason code (`payer_not_served` or `medicaid_source_not_served`); on `GET /v1/rules/receipt` an `outpatient` entry keeps its own sentence, which says it is served for Medicare and Medicare Advantage only.
- The upcoming-changes calendar (`/v1/archive/upcoming`) lists effective dates up to two years ahead, and the response names the last date as `horizon_through`. A CMS transmittal whose text states a typo year (R499PI states 2104) no longer shows as upcoming. The version and its as-of answer still carry the date CMS states.
- **A label with a related code stays with its own code.** The receipt shows a label's related-code note (CMS wrote these words for another code) for every code the label serves, so the daily label dedupe no longer merges such a label, and new codes are no longer mapped onto it. It is reported for a coder instead. When the daily re-anchor copies such a label onto a new document version, the copy keeps its related code. On production only one label (990, K0001 words marked related to K0005) has a related code; it serves only K0001 and was never merged.

### Security
- `GET /archive/files/{sha256}/text` holds a rendering that quotes the ADA's CDT descriptor for D7880 in any form Verzi can detect: another letter case, a tag, a line break or an invisible character inside it, another dash, or an HTML entity. The response has `text_withheld: "licensed_text"` and no text. The rendering of three more CMS documents that quote the descriptor is held by document.
- The receipt service now checks a certified coder's claim itself. A label decision or batch sign-off sent with `decided_by_certified: true` is accepted only when `decided_by` is an active portal account marked certified whose coder ID matches `decided_by_coder_id`. Anything else gets a 422 and nothing is written. Before, the service trusted the flag from any caller holding the approver key. A decision without the flag works as before. A receipt says "Approved by a certified coder." only after this check passes.
- The weekly digest emails, the alerts and the webhooks now apply the licensed-text check to revision notes, as the API feeds do. A note that quotes licensed code text CMS cites, or comes from a document that does, serves no text. The email says Verzi holds the note, and the webhook event carries `revision_note: null` and `revision_note_withheld: "licensed_text"`.
- The receipt viewer, the W3 passages and the KB pages now apply the same licensed-text check as `GET /archive/files/{sha256}/text`. They hold the text of the three CMS documents that quote the ADA's CDT descriptor for D7880. They also hold a text that still has the descriptor in another form after the exact blank. A held receipt serves no quote and no context.
- The KB code-list paragraphs, their asterisk notes and the revision notes now go through the licensed-text check. A held one shows a Verzi line and keeps its receipt.
- In `GET /archive/changes`, the upcoming calendar, the RSS and ICS feeds and the status pages, a revision note that quotes licensed code text serves no text. `revision_note_withheld` is `licensed_text`.
- `GET /archive/files/{sha256}` and `GET /archive/docs/{doc_id}/as-of` give no link to the original bytes of those three documents. `url_withheld` says why, and the sha256 and `resolved_url` still serve.
- **MCP sign-in finishes only in the browser that started it.** Allowing the connection requires that browser. A sign-in link opened somewhere else asks you to start again from the assistant.
- The OIG exclusion list loader now checks the OIG server certificate when it downloads the full list. It used to skip that check.
- The portfolio, watchlist and alert routes now answer 403 for an API key that belongs to no organization. Before, such a key was served under its user id.
- `POST /v1/watchlists` answers 404 when the portfolio is not your organization's own.
- **Only a working credential skips the keyless rate limit.** A caller whose IP has used up the keyless quota of 120 requests per minute still gets through with a valid API key, admin session or KB sign-in. A made-up, expired or revoked key or session cookie no longer does: that request gets `429 Too Many Requests` with `Retry-After`, like any keyless request over the quota.
- **One rule decides which stored source text the API serves, and it fails closed (issue #498).** Before, `GET /warrant/receipt` served any span of any archived rendering to any key, including MCD and CPT-licensed files that `/archive/files/{sha256}/text` withholds. Now the receipt serves the whole rendering only for a public-domain source. For an MCD source it serves only spans inside a narrative section of the coverage document (not the code tables), with the context clipped to that section. For any other license, or a license not classified, it serves no text: `found` is false and `withheld` says why. A quote is at most 5,000 characters. A file that only a non-public source holds answers 404. An out-of-range span no longer reports the rendering's length. `/archive/files/{sha256}/text` now uses the same rule, so a license value not yet classified (NUCC, X12, HL7, payer CPT terms) is held there too, and so is the text of bytes that any such source also holds. The link to the original bytes (the archive file metadata, the as-of answer and the KB file page) is withheld for MCD and CPT copies only, as before. The receipt's MCD section list holds the Coverage API field `coding_guidelines` for now. The KB passages do not follow this rule: they serve every section as before (next line).
- **The KB passages serve every section again.** The license gate briefly withheld the quote and section text of approved labels outside the narrative sections of an MCD document (for example the Coding Information panel) on the KB code page and in the free sample. That is undone: nothing is removed from the KB. Scans for issue #498 found no CPT descriptor and no revenue code text in the served KB sections or in the newest stored renderings. The gate stays on `/warrant/receipt` and `/archive/files/{sha256}/text`.
- The physician utilization endpoints no longer return a CPT descriptor in `hcpcs_description`. They return it only for public HCPCS Level II codes; for any other code it is null.
- The API no longer takes the client address from a visitor-supplied `X-Forwarded-For` or `CF-Connecting-IP`. Rate limits, the signup caps and the OTP caps now use the address Railway appended. Cloudflare headers count only when `CF_EDGE=1` is set.
- **`/archive/files/{sha256}` and `/archive/docs/{doc_id}/as-of` no longer give a link to the original bytes of a source whose files carry CPT descriptors.** These are the sources under the AMA license (`cms_ama_cpt_terms`) and the MCD terms (`cms_mcd_terms`), the same ones whose `/text` rendering the API already withholds. Before, any API key got a one-hour link to those bytes. `url` is now `null` for them, with or without a key, and `url_withheld` says why. The sha256 and the publisher's `resolved_url` still identify the file. Other sources are unchanged.
- The server access log no longer records query strings. A warrant request can carry a date of service and a patient ZIP, which together can identify a patient. The log keeps the path only.
- The MCP tools `warrant`, `warrant_changes` and `warrant_appeal` now return signed answers, the same Ed25519 attestation the REST warrant routes carry. Verify them offline with the key at `/v1/rules/warrant/signing-key`.
- **Verzi leaves out the CDT text that CMS quotes in Article A52512.** CMS's Oral Appliances Policy Article quotes the ADA's CDT descriptor for D7880. Every surface that serves the Article's text now shows "[CDT text owned by the ADA, not shown]" in place of that descriptor: the KB's signed-in text, the KB sections API, the W3 passages (full text, section text, labeled quotes and the free sample), and the receipt viewer (`/warrant/receipt`). The code and CMS's own words stay. W3 and receipt JSON name each gap in `redactions` (`reason: ada_cdt`, `code: D7880`). Verzi holds any text that quotes the code in another form, or that cuts into the descriptor.

---

## [2026-07-08]

### Added
- **Per-source freshness monitor** — `/status` and `/sources` now show whether each registered source is refreshing within its declared cadence. New shared module `api/providers/_shared/freshness.py` classifies each `source_registry` row as `fresh` / `stale` / `critical` / `never` against per-cadence thresholds (daily = 2/8d, weekly = 10/21d, monthly = 45/100d, quarterly = 100/200d, annual = 400/550d). Customer-facing consequence: if we say a source is monthly and it's actually 4 months stale, `/sources` shows a red "stale · 121d" badge with an explanatory note instead of hiding the drift. The `/status` pipeline check switches from "look at the single most recent successful run" (which was silently masking slow-cadence outages) to a per-source rollup that fails when any source is critical. Three CloudWatch alarms in `infra/template.yaml` (`PipelineNoRunAlarm` 25h, `PipelineWeeklyAlarm` 8d, `PipelineFailureAlarm` any) implement the same principle server-side. Alarm on the absence of success, not just the presence of failure.
- **NPPES Authorized Official schema** — migration 052 adds 8 AO columns (last/first/middle name, title, credential, name prefix/suffix, phone) to `nppes_providers` plus a partial index on the AO name pair for Type 2 orgs. Loader updated to capture them from the NPPES bulk file. Fields will populate on the next NPPES full-refresh run (monthly cadence). Unblocks the future `authorized_official` attribution signal migration.
- **Tenet Healthcare decomposition** — 6 new `system_hierarchy` rows: TENET parent + TENET_USPI, TENET_HEALTHSYSTEM, TENET_CALIFORNIA, TENET_FLORIDA, TENET_HOSPITALS. Sourced from CMS Hospital All Owners disclosures (60 hospitals under TENET HEALTHCARE CORPORATION + 24 USPI + 18 regional). EIN 952557091 linked. `/systems/TENET` now returns a real rollup.
- **UHS decomposition** — 7 new rows: UHS parent + UHS_ACUTE + UHS_BEHAVIORAL + UHS_DELAWARE + UHS_HOLDING + UHS_GEORGIA + UHS_PENNSYLVANIA. Only public behavioral-health rollup at scale (Provo Canyon, Cambridge, Cygnet). 145 hospitals under UNIVERSAL HEALTH SERVICES INC. EIN 232077891 linked.
- **Surgery Partners decomposition** — 3 new rows: SGRY parent + SGRY_ASC + SGRY_STONEBRIDGE. ASC roll-up; 17 direct facilities. EIN 473620923 linked. Unique in the market — no other public API exposes ASC ownership at NPI level.
- **Amazon One Medical decomposition** — 1 new row: ONE_MEDICAL as standalone primary-care group. Identified via 4 PECOS org_pac_id matches (ONE MEDICAL GROUP INC, ONE MEDICAL OF NY PC, ONE MEDICAL SENIORS GROUP INC, ONE MEDICAL P.C.). Amazon acquired for $3.9B Feb 2023.
- **IRS 990 XML index for 2020 + 2021** — 989K more rows loaded after fixing the `sub_date VARCHAR(4)` schema constraint (migration 049 widened to TEXT to accept the legacy `1/2/2020 3:03:27 PM` format). Combined with 2022-2024, healthcare-EIN discovery graph now spans 5 tax years (~2.7M index rows).

### Fixed
- **6 remaining sec_10k EINs** — Acadia, American Well, LifeStance, Privia Health, Select Medical, Pennant Group all previously had CIK-in-EIN or SEC placeholder `000000000`. Backfilled real 9-digit EINs by parsing each company's most recent 10-K cover page for the `XX-XXXXXXX` pattern. All 30 `org_eins.sec_10k` rows now have valid EINs.

### Removed
- **QPP MIPS TIN loader** was killed as a plan item after investigation confirmed CMS redacts TIN across all public files (Doctors and Clinicians, PECOS Individual Enrollment, QPP annual). No public path exists; moved to DATA_GAPS Tier 2.1 with external-constraint status.

---

## [2026-07-07]

### Added
- **DOL Form 5500 healthcare backfill** — loaded 107K healthcare-NAICS filings across tax years 2020-2024 (peak years 2021-2024 each cover 24-27K filings representing ~26M W-2 employees per year). Data lives in `dol_5500_filings` (raw) and `financial_filings` (aggregated per EIN × tax period). Powers the `/systems/{id}/financials/workforce` endpoint for any org whose EIN is known. Confirmed correct at the top of the distribution — Trinity Health at 158K W-2 employees (2023), Kaiser 149K, matching each system's publicly-stated head-counts.
- **DOL 5500 employment attribution signals** — 222,138 new signals in `employment_attribution_signals` with `source='dol_5500'`, `signal_type='participant'`, `confidence=0.55`. Cross-cites the DOL W-2 employer floor for NPIs whose PECOS reassignment org matches a linked EIN. Top employers surfaced: NYU (5,724 NPIs), Mayo Clinic (4,899), Montefiore (2,797), Henry Ford (2,538). Ready to grow substantially once the org_eins fuzzy-match review lands.
- **IRS 990 XML index for 2022-2023** — 1.36M new `irs_990_index` rows spanning both years. Combined with the pre-existing 2024 index, the healthcare EIN discovery graph now covers three tax years. 2020-2021 blocked on a `tax_period VARCHAR(4)` constraint issue (older years use different format); tracked in DATA_GAPS.

### Fixed
- **`org_eins` CIK-in-EIN data-model bug** — 30 rows sourced from SEC 10-K filings were storing the SEC EDGAR CIK in the `ein` column (variable-width, not a real EIN). Migration 047 added a proper `cik` column and moved the misplaced values. `scripts/providers/sec_filings/backfill_eins.py` then backfilled 25 real 9-digit EINs via SEC EDGAR submissions API (e.g. Tenet now correctly resolves to EIN 952557091 instead of CIK 70318). Remaining 5 issuers (American Well, LifeStance, Privia Health, Select Medical, Pennant Group) return SEC's placeholder `000000000` and are documented as a follow-up gap.
- **`org_eins.org_pac_id` first population** — 51 rows auto-linked to PECOS `org_pac_id` via trigram fuzzy match (similarity ≥ 0.85) using `scripts/providers/sec_filings/link_org_eins_to_pac.py`. 198 ambiguous candidates written to `data/ein_pac_id_review.csv` for human triage.

---

## [2026-07-02]

### Added
- **`/my-usage` HTML dashboard** — the authenticated usage endpoint now serves a styled dashboard to browsers with a tier badge, color-coded usage progress bar (green under 50%, amber under 90%, red at 90%+), tile grid, and a contextual upgrade CTA. JSON shape unchanged for API clients; a new `billing_tier` key is additive.
- **JSON-LD structured data** on the six main marketing pages (`/`, `/pricing`, `/quickstart`, `/sources`, `/accuracy`, `/legal/data-disclosure`). Enables Google Rich Results eligibility — pricing tiles as native price cards, quickstart as a HowTo card, `/sources` as a Dataset result.
- **`/changelog`** — public user-visible change log (this file). Content-negotiated: browsers get styled HTML, `curl` gets raw markdown.
- **`/status`** — public traffic-light health page. Shows real-time state of the four dependencies (PostgreSQL, S3, SES, pipeline freshness).
- **`/health/deep`** — deep health check endpoint. Runs live dependency probes. `/health` remains shallow + fast for CI polling.
- **`/examples`** and **`/examples/{lang}`** — copy-paste ready code samples in Python, Node.js, curl, Go, and PHP. Browsers get a styled page; `curl` gets the raw source file with the correct MIME type.
- **OpenAPI/Swagger enrichment** — 12 endpoints across `hospitals`, `nursing-homes`, `exclusions`, `provider` (npi_profile), `licenses`, and `mips` routers now carry `summary`, `description`, path/query examples, and response payload examples. The Swagger UI at `/docs` "Try it" form now auto-fills with real CCNs, NPIs, and state codes.
- **Sitemap now includes `/resources/{slug}` and `/examples/{lang}` URLs** with `lastmod` pulled from each file's mtime — helps search engines prioritize recently-updated content.

### Changed
- `/pricing` "Start with Free" CTAs pre-wired to `/billing/checkout?tier=starter` and `?tier=pro`. Currently return `503` until Stripe env vars are set; will flip on live automatically the moment the keys land.
- `/quickstart` "What's next" section now leads with `/examples` as the primary CTA (was "Full API Reference").
- `/health` split into shallow (`/health`, unchanged, fast) vs deep (`/health/deep`, runs real dependency probes).

---

## [2026-06-28]

### Added
- **`/quickstart`** — 5-minute developer integration guide with tabbed curl / Python / JavaScript samples, endpoint gallery, rate-limit callouts.
- **Open Graph social preview cards** — 1200×630 branded PNGs on every marketing page. LinkedIn / Twitter / Slack previews now render with a proper card instead of a bare URL.
- **`/sources/{source_id}`** now returns a styled HTML detail page in browsers (was JSON-only). Completes the `/sources/*` HTML family (list, detail, history).
- **`/resources` catalog + `/resources/{slug}`** rendered documents — the methodology docs (API Style Guide, Accuracy Benchmark, License Intelligence, Financial Intelligence, Employment Reconciliation) are now browsable as styled HTML with the site's brand chrome. `curl` still gets raw markdown.
- **`robots.txt`** and **`sitemap.xml`** for search-engine discovery. Allows public marketing surfaces; blocks admin / billing internals.

### Fixed
- `/billing/plans` legacy URL 301s to the canonical `/pricing`. Old page said "17 data sources" and referenced the wrong tier limits.

---

## [2026-06-27]

### Added
- **`/sources/{source_id}/history`** HTML — per-source refresh audit timeline with status-colored markers, four stat tiles (session count, success rate, last run, last status), and a smart empty state.
- **`/accuracy`** HTML — the marquee proof page. Four summary tiles (median variance, mean variance, systems within ±10%, within ±25%), methodology callout, sorted results table with color-coded variance (green/amber/red), and a ground-truth submission invitation.
- **`/platform/stats`** HTML — live dashboard with pulse-animated "refreshed Xs ago" badge, four stat tiles (data rows, sources, facilities, clinicians), last-pipeline-run card with status pill.
- SEO + Open Graph meta tags across seven public pages (description, `og:title`, `og:description`, `og:type`, `og:site_name`, `og:url`, `twitter:card`).
- **`/pricing`** page with four tiers (Free / $49 Starter / $199 Pro / Enterprise), FAQ, and cross-sell to the executive dashboard.
- **Shared content-negotiation helper** (`api/providers/_shared/content_negotiation.py:prefers_html`) — same URL serves HTML to browsers and JSON to API clients based on `Accept` header + explicit `?format=` override.

### Changed
- **`BILLING_TIERS`** aligned with the new 4-tier pricing (Free 10K/day, Starter 50K/day, Pro 500K/day, Enterprise 10M/day). Was 3 tiers with stale limits.
- **`/billing/checkout`** accepts a `?tier=` query param (starter or pro). Tier flows through Stripe checkout metadata so the webhook upgrades to the right tier.

### Fixed
- `test_admin::test_get_organization` was failing because it referenced a `starter` tier that didn't exist in `BILLING_TIERS`. Now passes.

---

## [2026-06-26]

### Added
- **Live source catalog at `/sources`** — every dataset we ingest with license, refresh cadence, accuracy class, and last-loaded state. 38 sources across CMS (13), other federal (5 — OIG, HRSA, CDC, AHRQ, Census/OMB), academic (1 — Dartmouth), state open-data (1 — CA Medical Board), commercial (2 — Google Maps, FMP), and Verzi-original layers (13). Same URL serves JSON to API clients.
- **Per-source refresh history at `/sources/{source_id}/history`** — every load attempt, success or failure, with timing and row-count deltas.
- **`/platform/stats`** endpoint — live row counts, source counts, facility / clinician counts, last pipeline run status. Backs the marketing numbers without hardcoding them.
- **Data Use & Disclosure Statement** at `/legal/data-disclosure` — canonical, version-controlled statement of which datasets we ingest, under what license, and our HIPAA classification. Maintained outside the auto-generated Terms/Privacy so Termly regenerations can't wipe substantive disclosure.
- **LoadSession instrumentation** — every pipeline loader run now records a session row (`source_id`, `started_at`, `completed_at`, `status`, `rows_loaded`, `error_message`) to the `load_sessions` table.

### Changed
- Homepage stats now fetch from `/platform/stats` via Next.js ISR (1-hour revalidation) instead of hardcoded strings. Row counts stop drifting.
- Data source attribution rewritten across README, `PROJECT_OVERVIEW`, `terms.html`, `privacy.html`, and the homepage to reflect the full 30+ source catalog (CMS, HHS OIG, HRSA, CDC, AHRQ, IRS, DOL, SEC EDGAR, Census, Dartmouth, plus commercial APIs) instead of claiming CMS-only. Every `312M+ rows` / `27 sources` reference updated to live counts or durable phrasing.
- Signup form bot-prevention hardening: honeypot field, disposable email denylist, per-IP rate limit, Cloudflare Turnstile scaffolded and env-flag-gated.

### Fixed
- Migration tooling: `run_migrations.py --stamp` bootstrap flag, cleaner prod auth flow via AWS Secrets Manager (`cms-dev/postgres-credentials`), fixed URL-encoding issue with prod password.

---

## [2026-06-17]

### Added
- **Financial Intelligence** product layer — IRS Form 990 deep XML pipeline (Schedule R + Schedule J), DOL Form 5500 loader, SEC EDGAR 10-K via FMP for 30 curated public healthcare tickers.
- **`financial_filings`** table — cross-source EIN × filing_type × tax_period_end unified store. 15K+ rows.
- **`executive_compensation`** table — Schedule J + 10-K NEO records, 267 entries with matched NPIs for clinician-executives.
- **Financial Intelligence API endpoints**: `/systems/{id}/financials`, `/systems/{id}/financials/executives`, `/systems/{id}/financials/workforce`, `/companies/{ticker}`, `/companies/search`, `/ma-events/recent`, `/provider/{npi}/financial-affiliation`.

---

## [2026-06-16]

### Changed
- **API consolidation**: `/quality` nested under `/provider`, `/quality` router renamed to `/mips`, fixed `/systems` route collision.

---

## [2026-06-11]

### Added
- **License + Quality Intelligence v1**
  - `provider_licenses` (5M+ NPI-keyed licenses derived from NPPES taxonomy across all 50 states)
  - `license_disciplinary_actions` (8.5K OIG LEIE joined to NPI)
  - License Intelligence API: `/licenses/state/{state}`, `/licenses/{npi}`, `/licenses/{npi}/disciplinary`, `/licenses/alerts/recent`
  - Quality Intelligence API: `/quality/{npi}`, `/quality/leaderboards/{specialty}`, `/quality/systems/{system_id}`
  - Extended `/provider/{npi}` dossier with new `license_intelligence`, `quality_intelligence`, `employment_intelligence` blocks

---

## [2026-06-10]

### Added
- **Physician Employment Intelligence v2** — multi-source attribution + system decomposition
  - `org_eins`, `employment_attribution_signals`, `system_hierarchy` tables
  - Large national systems decomposed into operating divisions
  - Accuracy benchmark at `/accuracy` — per-system variance vs publicly-stated counts
- **Physician Employment Intelligence v1** — initial employer typology product
  - `physician_employer_systems`, `employer_facts` materialized view
  - 12 API endpoints at `/provider/*`, `/employers/*`, `/systems/*`

---

## Older

Prior to 2026-06-10, changes were tracked via git log only. The last major additions before that date were VBC/ACO analytics, HCAHPS benchmarking materialized views, market intelligence (HSAF), community health (CDC PLACES, Medicare Geographic Variation, AHRQ SDOH), and the initial 9 CMS provider-type ingestion.

---

## How to read this

- **Added** — new endpoints, tables, or user-visible features
- **Changed** — modifications to existing behavior (usually backward-compatible)
- **Fixed** — bugs or inconsistencies resolved
- **Deprecated** — features scheduled for removal (none yet)
- **Removed** — features removed (none yet)
- **Security** — security-relevant changes (none breaking; hardening only)

For the machine-readable API changelog, hit `curl https://api.verzi.health/changelog` — returns raw markdown.
