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

skin-subs: manuscript write-up — methods, results, discussion #246

New Issue
Open
opened 2026-03-25 05:36:45 +00:00 by kert · 0 comments
kert commented 2026-03-25 05:36:45 +00:00
Owner
Copy Link

Objective

Manuscript-ready write-up of the full analysis.

Structure

  • Abstract: hypothesis, methods, key findings
  • Introduction: skin substitute market explosion, regulatory context, fraud landscape
  • Methods: data sources (ASP, claims, literature), analytic approach, anomaly detection framework
  • Results:
    • Market segmentation and pricing trajectories
    • Geographic and setting variation
    • Predatory pattern indicators
    • Enforcement action correlation
    • Literature synthesis (meta-analysis where applicable)
  • Discussion: policy implications, CMS reclassification impact, limitations
  • Conclusion: soft/hard target framework for skin substitute fraud risk
  • References: full Zotero bibliography, auto-generated
  • Supplementary: detailed tables, code availability statement

Format

  • Docusaurus page in docs/ (web-accessible)
  • PDF export via existing docs infrastructure
  • All figures from marimo notebooks (reproducible)
  • Citation style: JAMA or Health Affairs (TBD)
## Objective Manuscript-ready write-up of the full analysis. ## Structure - [ ] Abstract: hypothesis, methods, key findings - [ ] Introduction: skin substitute market explosion, regulatory context, fraud landscape - [ ] Methods: data sources (ASP, claims, literature), analytic approach, anomaly detection framework - [ ] Results: - Market segmentation and pricing trajectories - Geographic and setting variation - Predatory pattern indicators - Enforcement action correlation - Literature synthesis (meta-analysis where applicable) - [ ] Discussion: policy implications, CMS reclassification impact, limitations - [ ] Conclusion: soft/hard target framework for skin substitute fraud risk - [ ] References: full Zotero bibliography, auto-generated - [ ] Supplementary: detailed tables, code availability statement ## Format - Docusaurus page in `docs/` (web-accessible) - PDF export via existing docs infrastructure - All figures from marimo notebooks (reproducible) - Citation style: JAMA or Health Affairs (TBD)
kert added this to the P29: Skin Substitutes — predatory pricing, distribution, and utilization analysis milestone 2026-03-25 05:36:45 +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
Milestone
No items
No Milestone P29: Skin Substitutes — predatory pricing, distribution, and utilization analysis
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#246
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?