homelab/stack
1
0
Fork 0
Code Issues 262 Pull Requests 2 Actions Packages Projects 1 Releases Wiki Activity

notebooks: CY2027 NPRM — GPCI & locality section (near-term deltas, long-term trends, locality-adjusted payment) #631

New Issue
Closed
opened 2026-08-17 16:10:10 +00:00 by kert · 1 comment
kert commented 2026-08-17 16:10:10 +00:00
Owner
Copy Link

Add a GPCI section to notebooks/cy2027_pfs_proposed_rule.py (between current Sections 2 and 3), replacing the intro's "GPCI = 1.0, this notebook does not join pfs.gpci" disclaimer:

  • Near-term: CY2027-proposed (CMS-1848-P, pfs.gpci_proposed) vs CY2026-final (pfs.gpci) work/PE/MP deltas per locality — biggest-movers table + diverging bar; up/down/flat counts; the 1832-P-projected-2027 vs 1848-P-actually-proposed-2027 self-join. Work-GPCI floor status labeled (proposed PW published without the 1.0 floor).
  • Long-term: locality GPCI trends 2016–2026 + 2027-proposed (flagged "final rule pending").
  • Payment effect: pfs.calcs.payment.payment(rvu, gpci, cf) for the notebook's existing 99213/27447/70553 trio at best/worst locality vs national.
  • Intro + provenance cells updated (pfs.gpci/pfs.gpci_proposed ingest-log rows now included).

Gate: nb_integration.py single-notebook run green in the prod notebooks container.

Depends on #629, #630. Spec: docs/superpowers/specs/2026-08-17-cy2027-notebook-gpci-pqm-design.md (D3).

Add a GPCI section to `notebooks/cy2027_pfs_proposed_rule.py` (between current Sections 2 and 3), replacing the intro's "GPCI = 1.0, this notebook does not join pfs.gpci" disclaimer: - **Near-term**: CY2027-proposed (CMS-1848-P, `pfs.gpci_proposed`) vs CY2026-final (`pfs.gpci`) work/PE/MP deltas per locality — biggest-movers table + diverging bar; up/down/flat counts; the 1832-P-projected-2027 vs 1848-P-actually-proposed-2027 self-join. Work-GPCI floor status labeled (proposed PW published without the 1.0 floor). - **Long-term**: locality GPCI trends 2016–2026 + 2027-proposed (flagged "final rule pending"). - **Payment effect**: `pfs.calcs.payment.payment(rvu, gpci, cf)` for the notebook's existing 99213/27447/70553 trio at best/worst locality vs national. - Intro + provenance cells updated (`pfs.gpci`/`pfs.gpci_proposed` ingest-log rows now included). Gate: `nb_integration.py` single-notebook run green in the prod notebooks container. Depends on #629, #630. Spec: docs/superpowers/specs/2026-08-17-cy2027-notebook-gpci-pqm-design.md (D3).
kert added this to the P39: CY2027 Notebook Deep-Dive — GPCI locality analysis + primary-care (ACO attribution) services milestone 2026-08-17 16:10:10 +00:00
kert added the pfsnotebooks labels 2026-08-17 16:10:10 +00:00
kert closed this issue 2026-08-17 16:39:39 +00:00
kert commented 2026-08-17 16:40:00 +00:00
Author
Owner
Copy Link

Shipped in 8c4e13c (combined commit with #632 — the two sections were built as one splice into the notebook). Verified: nb_integration.py single-notebook run in the prod notebooks container → pass=1 (twice — after the initial build and after the coverage-prose fix). Section contents: locality movers vs CY2026 final (109 localities matched), 1832-P-projected vs 1848-P-proposed 2027 self-join (6 of 109 localities revised), 2016–2027p component trends (hi: Miami FL, lo: Wisconsin, vs all-locality median), and pfs.calcs.payment locality-adjusted pricing for the 99213/27447/70553 trio. Work-floor caveat labeled per the Addendum E column headings.

Shipped in 8c4e13c (combined commit with #632 — the two sections were built as one splice into the notebook). Verified: `nb_integration.py` single-notebook run in the prod notebooks container → `pass=1` (twice — after the initial build and after the coverage-prose fix). Section contents: locality movers vs CY2026 final (109 localities matched), 1832-P-projected vs 1848-P-proposed 2027 self-join (6 of 109 localities revised), 2016–2027p component trends (hi: Miami FL, lo: Wisconsin, vs all-locality median), and `pfs.calcs.payment` locality-adjusted pricing for the 99213/27447/70553 trio. Work-floor caveat labeled per the Addendum E column headings.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
REST API (FastAPI)
 auth
Authentication and authorization
 bib
Bibliography, Zotero, citations
 ci
CI/CD pipelines and Woodpecker plugins
 cli
CLI commands and UX
 cloud
Cloud provider abstraction (AWS, GCP, Azure, self-hosted)
 config
Configuration and wiring
 data
Data loading, CCLF, BCDA, seeds
 databricks
Databricks jobs and deployment
 docs
Documentation and generated references
 image:api
image:docs
image:mc
image:notebooks
image:zotero
infra
lakehouse
Nessie, Polaris, Trino, Iceberg
 llm
llm module — local RAG over comments + Zotero corpus
 notebooks
marimo notebook errors (auto-filed by nb-watcher/nb-integration)
 packaging
Python packaging, optional deps, build system
 pfs
pipeline
Pipeline execution and validation
 pipeline:ci
pipeline:deploy
pipeline:harden
pipeline:infra-ci
pipeline:rebuild-all
pipeline:release
qpp
quality
Testing, coverage, error handling
 step:build
step:deploy
step:hadolint
step:lint
step:publish
step:scan
step:test
step:validate
styles
Charts, figures, visual theming
 tree
Project directory structure and file organization
No Label notebooks pfs
Milestone
No items
No Milestone P39: CY2027 Notebook Deep-Dive — GPCI locality analysis + primary-care (ACO attribution) services
Projects
Clear projects
No project
Assignees
Clear assignees
kert renovate-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: homelab/stack#631
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?