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

literature sweep: per-question evidence for eligibility criteria and FWA in community-based palliative care #646

New Issue
Closed
opened 2026-08-18 14:14:34 +00:00 by kert · 1 comment
kert commented 2026-08-18 14:14:34 +00:00
Owner
Copy Link

CMS asks every statement to be supported by peer-reviewed or institutional evidence in sufficient detail for review. Sweep and capture (Zotero, P42 tag scheme) evidence keyed to the RFI questions:

  • (a) where fraud/waste/abuse concentrates in community-based palliative care and adjacent hospice programs
  • (b) life-expectancy certification as an eligibility gate: evidence for/against, prognostic accuracy, state Medicaid <1yr precedents
  • (c) functional-status (ADL) and caregiver-strain based eligibility: instruments, evidence they identify the serious-illness population (extend from Kelley 2017)
  • (d) essential service elements of palliative care management (interdisciplinary teams, home visits, shared decision-making — CMMI synthesis findings)
  • (e) quality measurement for palliative care management; whether CBE 3665 alone is sufficient

Deliverable: tagged collection + a short evidence-map note per question feeding P44 drafting.

CMS asks every statement to be supported by peer-reviewed or institutional evidence in sufficient detail for review. Sweep and capture (Zotero, P42 tag scheme) evidence keyed to the RFI questions: - (a) where fraud/waste/abuse concentrates in community-based palliative care and adjacent hospice programs - (b) life-expectancy certification as an eligibility gate: evidence for/against, prognostic accuracy, state Medicaid <1yr precedents - (c) functional-status (ADL) and caregiver-strain based eligibility: instruments, evidence they identify the serious-illness population (extend from Kelley 2017) - (d) essential service elements of palliative care management (interdisciplinary teams, home visits, shared decision-making — CMMI synthesis findings) - (e) quality measurement for palliative care management; whether CBE 3665 alone is sufficient Deliverable: tagged collection + a short evidence-map note per question feeding P44 drafting.
kert added this to the P42: Palliative Care RFI — evidence base & source capture milestone 2026-08-18 14:14:34 +00:00
kert added the bib label 2026-08-18 14:14:34 +00:00
kert commented 2026-08-18 19:54:24 +00:00
Author
Owner
Copy Link

Delivered via the PRISMA pipeline rather than a hand sweep: 4,999 identified (8 uncapped PubMed domains + elink snowball + grey standards/RFI-cited docs), 4,997 stage-2 screened on the local fleet model — 2,245 include / 2,636 exclude / 116 uncertain, per-question coverage via rfi:{a-e,codeset} tags, per-record rationale notes on every Zotero item. The two unscreened records are 1990s items no prompt shape elicits a tool call for; left honestly unscreened. Per-question evidence-map notes for P44 drafting come out of stage-3/extraction, tracked by the milestone.

Delivered via the PRISMA pipeline rather than a hand sweep: 4,999 identified (8 uncapped PubMed domains + elink snowball + grey standards/RFI-cited docs), 4,997 stage-2 screened on the local fleet model — 2,245 include / 2,636 exclude / 116 uncertain, per-question coverage via rfi:{a-e,codeset} tags, per-record rationale notes on every Zotero item. The two unscreened records are 1990s items no prompt shape elicits a tool call for; left honestly unscreened. Per-question evidence-map notes for P44 drafting come out of stage-3/extraction, tracked by the milestone.
kert closed this issue 2026-08-18 19:54:24 +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 bib
Milestone
No items
No Milestone P42: Palliative Care RFI — evidence base & source capture
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#646
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?