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

pfs: NPRM Addendum E loader — pfs.gpci_proposed (CMS-1832-P + CMS-1848-P partitions) #629

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

Load the NPRM Addendum E (proposed GPCIs) workbooks — already on disk for both NPRMs under data/cms/pfs_nprm/{2026,2027}/ — into a new lake table pfs.gpci_proposed, mirroring the rvu_proposed pattern (per-cms_rule_id partition delete/reinsert, cms.ingest_log provenance).

Verified layouts:

  • CY2027 file (CMS-1848-P): MAC / State / Locality Number / Locality Name / 2027 PW (no 1.0 floor) / 2027 PE / 2027 MP
  • CY2026 file (CMS-1832-P): same key columns + 2025 baseline, 2026 proposed, 2027 phase-in triplets (biennial GPCI update)

Load long with a gpci_year column, taking year-columns ≥ the NPRM's rule year (1832-P → 2026+2027; 1848-P → 2027; skip the 2025 restatement). Filter footnote rows (non-numeric MAC). PW loads as published (floor-free) — labeling is the notebook's job.

Also: extend dev/scripts/fetch_nprm_addenda.py CONFIGS to attach Addendum E to the bib rule items (CY{year} PFS NPRM Addendum E (proposed GPCIs), existing title-guarded idempotent register), and discover the workbook via the sup:{year}_PFS_NPRM tag like Addendum B does.

Tests: header detection on both real layouts, partition isolation, numeric coercion.

Spec: docs/superpowers/specs/2026-08-17-cy2027-notebook-gpci-pqm-design.md (D1).

Load the NPRM **Addendum E** (proposed GPCIs) workbooks — already on disk for both NPRMs under `data/cms/pfs_nprm/{2026,2027}/` — into a new lake table `pfs.gpci_proposed`, mirroring the `rvu_proposed` pattern (per-`cms_rule_id` partition delete/reinsert, `cms.ingest_log` provenance). Verified layouts: - CY2027 file (CMS-1848-P): MAC / State / Locality Number / Locality Name / 2027 PW (no 1.0 floor) / 2027 PE / 2027 MP - CY2026 file (CMS-1832-P): same key columns + **2025 baseline, 2026 proposed, 2027 phase-in** triplets (biennial GPCI update) Load long with a `gpci_year` column, taking year-columns ≥ the NPRM's rule year (1832-P → 2026+2027; 1848-P → 2027; skip the 2025 restatement). Filter footnote rows (non-numeric MAC). PW loads as published (floor-free) — labeling is the notebook's job. Also: extend `dev/scripts/fetch_nprm_addenda.py` CONFIGS to attach Addendum E to the bib rule items (`CY{year} PFS NPRM Addendum E (proposed GPCIs)`, existing title-guarded idempotent register), and discover the workbook via the `sup:{year}_PFS_NPRM` tag like Addendum B does. Tests: header detection on both real layouts, partition isolation, numeric coercion. Spec: docs/superpowers/specs/2026-08-17-cy2027-notebook-gpci-pqm-design.md (D1).
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 pfsdatapipeline labels 2026-08-17 16:10:10 +00:00
kert closed this issue 2026-08-17 16:39:39 +00:00
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 data pfs pipeline
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#629
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?