Tell the practice the three claims/survey measures are not shown — and ask whether they want them as tiles
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 85/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- content, documentation
Research direction
Start with ROADMAP §5 MM-1c and the issue’s Definition of Done. Ask the practice in the owner's next message whether to leave measures 479, 484, and 321 off or show them as explicitly non-computed. Record the answer in ROADMAP §5 MM-1c by replacing the struck-through tiles line with the decision.
Written by the indexing model from the issue text.
Description
An owner-run communication step, not agent code. Small, and filed because it was decided silently.
What happened
ROADMAP MM-1c promised informational tiles for the three set members WorkWell cannot compute — 479 (HWR), 484 (MCC) and 321 (CAHPS), all claims- or survey-calculated and computed for the ACO rather than by it. The tiles were dropped on 2026-09-10, and the 2026-09-10 call supports the drop: a tile could only ever say "we do not compute this".
The customer was not told. The roadmap line stayed in place until 2026-09-15, so plan and product disagreed, and the practice's view of their nine-measure program silently became a six-measure screen.
The ask, either way
Both answers are defensible and it is not our call:
- Leave them off — the screen shows what the engine computes, and nothing implies coverage it does not have. Cheapest, and the reading the call supports.
- Show them as explicitly non-computed — the practice sees their whole program in one place, with three rows that say where those numbers come from instead. Costs a little, and removes the "where are the other three?" question permanently.
What must not happen is a tile that looks like a measure with no number in it, which reads as broken rather than as out of scope.
Definition of done
The question is asked in the owner's next message to the practice, and the answer is recorded in ROADMAP §5 MM-1c — replacing the struck-through tiles line with a decision rather than a deletion.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 6h 6m
- Merged PRs (30d)
- 69
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.
More from Taleef7/workwell
-
documentation owner-ops
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 38/100
-
backend
Difficulty 5/5 Over a week Newbie friendliness 35/100
All issues in Taleef7/workwell
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100