592b845584
All checks were successful
CI / lint (push) Successful in 1m9s
CI / notebooks-smoke (push) Successful in 1m54s
Deploy / changes (push) Successful in 23s
CI / test (push) Successful in 4m25s
Infra CI / notebooks (push) Successful in 1m8s
Infra CI / zotero (push) Successful in 19s
Infra CI / docs (push) Successful in 1m21s
Infra CI / api (push) Successful in 1m15s
Infra CI / llm (push) Successful in 52s
Infra CI / mc (push) Successful in 17s
Infra CI / bcda (push) Successful in 1m47s
Deploy / notebooks (push) Has been skipped
Deploy / zotero (push) Has been skipped
Deploy / docs (push) Successful in 46s
Package Supply Chain / pkg-supply-chain (push) Successful in 1m31s
Deploy / api (push) Successful in 1m12s
Deploy / bcda (push) Successful in 1m47s
Deploy / mc (push) Has been skipped
Deploy / llm (push) Successful in 1m13s
Deploy / report (push) Successful in 14s
Nothing pulled open dockets on a schedule, so the FY2027 Hospice (CMS-2026-1156, 215 comments) and CY2027 ESRD (CMS-2026-2245, 228) proposed-rule dockets sat unpulled for months. - `stack bib pull-open-dockets`: walk every unsealed docket from its watermark (attachments on), then enrich the new stubs at the 1000/hr reg.gov budget. Sealed dockets cost nothing; a docket quiet long enough after its period closes seals itself, so the job idles between seasons. - Comment Pull workflow (02:30 nightly, generated): register this year's PFS proposed rule when it appears, pull + enrich the open dockets in the api container, index new comments in the llm container. - compose: api gets REGULATIONS_GOV_API_KEY and ./.state/comments (rw); the llm extra gains typer so `stack llm index` runs inside llm. - CLI reference regenerated for the new command. Security: streamlit 1.66.0 capped pillow <13, leaving pillow 12.3.0 with 41 advisories (5 critical) fixed only in 13.0. streamlit 1.66.1 (Oct 21) lifts the cap; exempted from the 7-day cooldown via exclude-newer-package, and constraint-dependencies holds pillow >=13. Lock scans clean.
2.4 KiB
2.4 KiB
title, sidebar_position
| title | sidebar_position |
|---|---|
| stack pfs exposure | 95 |
stack pfs exposure
Usage: stack pfs exposure [OPTIONS]
The exposure calendar (pfs.code_exposure, #693): when each code became
payable, was revalued, changed payable status, ended, or was listed for
telehealth — dated 1 January of the rule year (or the correction notice's
date), anchored to the FR paragraph from its lineage, with the status and
RVU-decile band a control set matches on.
--write always rebuilds every code (control sets need the whole
calendar); --code/--family only filter what is printed.
╭─ Options ────────────────────────────────────────────────────────────────────╮
│ --code <str> Filter to a code; repeatable. │
│ --family <str> Filter to a family key (CCM, APCM, …); repeatable. │
│ --controls <int> With one --code and --year: list up to N │
│ never-treated control codes (same status + RVU │
│ band, no exposure within --window years). │
│ [default: 0] │
│ --year <int> The exposure year --controls refers to. │
│ [default: 0] │
│ --window <int> ±years a control must be quiet for. [default: 2] │
│ --write Rebuild the whole calendar into pfs.code_exposure │
│ and republish. │
│ --help Show this message and exit. │
╰──────────────────────────────────────────────────────────────────────────────╯