PolicyEngine / PolicyEngine/calibration-diagnostics
Add healthcare release-over-release comparison view
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 4
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 13
Description
Context
The healthcare target tab already supports scope=healthcare for ACA, Medicaid/CHIP, and Medicare targets, with healthcare-specific KPIs for the latest release or a selected release. The compare page already supports release-to-release target matching with generic filters for source, measure, geography, improved/regressed, and under/over target.
What is missing is the combined workflow: show healthcare targets over releases.
Proposed implementation
- Add a healthcare scope to
/populace/compareusing the same target scope as the healthcare target tab. - Treat healthcare targets as ACA marketplace, Medicaid/CHIP, Medicare, and related PTC targets from the existing healthcare target predicate.
- Add a one-click Healthcare segmented control or preset on the compare page.
- Add healthcare summary cards for:
- ACA marketplace
- APTC recipients
- Medicaid
- Medicaid + CHIP
- CHIP implied
- Medicare Part B
- For each healthcare summary card, show A error → B error and the fit change.
- Preserve compare state in the URL, including
scope=healthcare,a, andb. - Add a deep link from the healthcare target tab: “Compare this release to previous”, pointing to
/populace/compare?scope=healthcare&a=<previous>&b=<current>.
Acceptance criteria
/populace/compare?scope=healthcare&a=<previous>&b=<current>loads directly into healthcare-scoped comparison.- Compare summary totals, added/removed counts, improved/regressed counts, mover lists, and the all-target table reflect the healthcare-scoped target surface.
- Switching between All targets and Healthcare updates the URL.
- The healthcare target tab links to the previous-vs-selected release healthcare comparison when a previous release exists.
- Generic compare filters continue to work within the healthcare scope.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the existing /populace/compare page and the healthcare target tab, tracing how target scope, release parameters, filters, and URL state are currently handled. Add the healthcare comparison workflow and previous-release deep link, then verify the acceptance URLs, summary cards, counts, mover lists, table, and generic filters for the healthcare scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- analytics, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100