Compare the steward's expected stratifier results (cms125, cms130, cms137), in the gate and end to end
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 72/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- testing
Research direction
Start with the official-cases gate run by pnpm test:official-cases and inspect how it reads group.stratifier beside populationCountsByRate. Then read src/test-support/madie-end-to-end.ts and the cms125, cms130, and cms137 cases. Done means both checks compare the steward’s per-stratum expectations with fqm-execution results and persisted official.strata values.
Written by the indexing model from the issue text.
Description
Why
The MADiE decks for cms125, cms130 and cms137 carry the steward's expected stratifier results (for example, age-band breakdowns) alongside the population vectors. Neither check compares them:
- The official-cases gate (
pnpm test:official-cases) compares population vectors only. - The end-to-end test from #727 compares populations, statuses, cases and rates, and leaves stratifiers out, as decided there.
evidence_json.official.strata is persisted on stratified outcomes (DATA_MODEL_CONTRACTS §5) and feeds MeasureReport and QRDA. So a stratifier the engine gets wrong would reach an export with nothing checking it.
Proposal
- Gate: read each case's expected
group.stratifierresults next topopulationCountsByRate, and compare them with fqm-execution's per-stratum results. - End to end: check the persisted
official.strataper patient against the same expectations, reusingsrc/test-support/madie-end-to-end.ts.
Scope
cms125, cms130, cms137, which are the Maui measures whose decks declare stratifiers.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 3h 6m
- Merged PRs (30d)
- 113
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from Taleef7/workwell
-
documentation owner-ops waiting
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
owner-ops waiting
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
infra maui-pilot
Difficulty 3/5 1-2 days Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
backend bug
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
backend enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
All issues in Taleef7/workwell
Similar issues
-
refactor
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
tomnewport/memprot-topo#55 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
WalletConnect/walletconnect-monorepo#7368 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
BU-Spark/se-chem-apll#47 ·
-
embed: handleTurboSignMessage header comment says the signing page posts to '*' (it never does)Opendocumentation
Difficulty 2/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 Half a day Newbie friendliness 70/100
udistrital/paginaweb_root#23 ·