Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Measure labels carry no version outside the measure page, and several screens print a version that never ran

Cerrado
#769 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@Taleef7 ya está trabajando en esto.

Desde el 8/10/2026.

  • #771 de @Taleef7 — abierto

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
java, nextjs, postgresql, typescript

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

maui-pilot pilot-trust

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.0 beside CMS122 and CMS125. On Maui those measures run CMS's CMS122FHIR/CMS125FHIR v1.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_version answer CMS125v14 with v1.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 document CMS125FHIR. /api/programs and 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 show MIPS 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 show MIPS 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 ecqmId is spelled CMS125FHIR. Stored evidence, the published package type and QRDA are unchanged.
  • MCP adds executed/translation alongside policyRef, 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.3 measureVersion value 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.0 or v1.0 for 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

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Taleef7/workwell

Todos los issues de Taleef7/workwell

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.