Measure labels carry no version outside the measure page, and several screens print a version that never ran
Los mantenedores suelen responder en 1 día
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 35/100
Línea de trabajo
Start with run/employee-profile.ts:114-118 and trace how evidence_json.official is used for result labels, then inspect the named CSV, MCP, compliance API, and OpenAPI surfaces. Add coverage for official and translated results, mixed-logic run details, and served ecqmId spelling; done means the listed surfaces reflect executed logic, while selection surfaces remain unversioned.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
What is wrong
A measure's label carries its version on only two screens: the measure page (/programs/<id>) and the admin measures grid. Everywhere else the label is MIPS 305 · CMS137 with no version. That includes the program cards, work list, cases list, case page, patient page, roster, attributed lists and people timeline. CMS revises each eCQM every year, so an unversioned id does not say which year's logic scored a result. MIE's quality team asked on 2026-10-01 for the CMS id to always carry its version.
Several places print a version that never ran:
- The patient page prints WorkWell's authored library version
2.0.0beside CMS122 and CMS125. On Maui those measures run CMS'sCMS122FHIR/CMS125FHIRv1.0.000 (run/employee-profile.ts:114-118). Five more copies of the same lookup feed the cases CSV, the runs CSV, MCP and the audit packets. - "Run This Measure" lists
v1.0(the catalog record's version), as does the Studio header. - MCP
list_measures/get_measure_versionanswerCMS125v14withv1.0. That is a QDM identity next to a version neither belongs to. - An All Programs run detail names no artifact at all.
- The compliance API serves
ecqmId: "125FHIR"(the manifest's bare form), while COMPLIANCE_API.md and the OpenAPI spec documentCMS125FHIR./api/programsand the attributed-list report (§6.6) also serve the bare form.
What is needed
Every surface that shows a result names the logic that scored it, read from that row's evidence (evidence_json.official), never from today's routing:
- A result CMS's artifact scored:
MIPS 305 · CMS137FHIR v1.0.000 (from CMS137v14). Narrow chips showMIPS 305 · CMS137FHIR (from CMS137v14), with the full form in the tooltip. - A result scored by WorkWell's translation:
MIPS 305 · WorkWell translation of CMS137v15 (ww-2027.1). Chips showMIPS 305 · WW translation of CMS137v15. - A result scored by authored CQL (TWH occupational measures): unchanged.
- Selection surfaces (pickers, filters) stay unversioned, because a measure spans years.
- Every served
ecqmIdis spelledCMS125FHIR. Stored evidence, the published package type and QRDA are unchanged. - MCP adds
executed/translationalongsidepolicyRef, which stays the catalog's QDM lineage. It never pairs the QDM id with the executed version. - The §6.2/§6.3 CSVs append
executedLogic. The §6.3measureVersionvalue becomes the executed version, as §6.2's already is.
The "(from CMS137v14)" lineage comes from a pinned map keyed by the vendored artifact's sha, not from the catalog's policyRef. Otherwise it would change when the catalog moves to 2027.
Done when
- No result surface prints
2.0.0orv1.0for an official-routed measure. - An All Programs run detail lists the logic per measure. A run that mixed logics says so instead of naming one.
- A 2027-dated translated result renders the translation's label. This is proven in CI (e2e-maui), because the sandbox has no 2027 run.
- Lenguaje dominante
- TypeScript
- Estrellas
- 0
- Forks
- 0
- Merge medio
- 3 h 43 min
- PR fusionados (30 d)
- 141
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de Taleef7/workwell
-
documentation owner-ops waiting
Dificultad 1/5 1-3 horas Aptitud para principiantes 86/100
Los mantenedores suelen responder en 1 día
-
owner-ops waiting
Dificultad 1/5 1-3 horas Aptitud para principiantes 85/100
Los mantenedores suelen responder en 1 día
-
backend infra maui-pilot
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
Los mantenedores suelen responder en 1 día
-
fqm-execution: master passes every gate; take the next release (fqm-execution PR 375) when it shipsAbiertocql-engine dependencies
Dificultad 4/5 1-2 días Aptitud para principiantes 35/100
Taleef7/workwell#850 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
cql-engine maui-pilot
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
Taleef7/workwell#847 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de Taleef7/workwell
Issues similares
-
支持对已取消(cancelled)任务生成报告Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
Clouditera/VulnHunter#57 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
bug bug:behavior clawsweeper:bulk-filed clawsweeper:fix-shape-clear clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:auth-provider issue-rating: 🦞 diamond lobster P2
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
openclaw/openclaw#185297 · 1 comentario · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
-
bug needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
apex-dev-tools/apex-log-parser#199 ·
Los mantenedores suelen responder en 1 día