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

The measurement period is UTC and the practice is not: confirm the zone and decide the instant-precision edge cases

Abierto
  • ¿Algo no está bien?
#847 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
typescript
Área
backend, databases

Línea de trabajo

Start with backend-ts/src/config/deployment-profile.ts and the scheduler comment to establish the conflicting zone settings; then trace WebChart's issued fallback in normalize.ts and the calculateOfficial measurement-period handling described in the issue. Confirm the practice zone with MIE and decide how to handle Z timestamps and instant-precision boundaries, including whether fqm needs a change or the limitation should be documented. Done means the zone and edge-case decisions are recorded, with the practice time zone and its test updated as agreed.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

cql-engine maui-pilot

The measurement period is evaluated in UTC, and the practice is not in UTC. Measured, this is narrower than it sounds, but it is not nothing. And the practice's zone is still unsettled.

How the period works today

fqm-execution builds the measurement period at offset 0. Version 1.8.5 also ignores a stated offset: 2026-01-01T00:00:00-10:00 becomes 2026-01-01T00:00:00Z (projecttacoma/fqm-execution#376).

What a UTC period gets wrong, measured through calculateOfficial

  • day of comparisons are right while the data keeps its local offset. They read each event in the offset it states. QRDA import has kept the stated offset since #797.
CMS125 qualifying encounter Counted in 2026?
2026-12-31T19:00-10:00 (local 31 Dec; 05:00Z on 1 Jan) yes
the same instant written 2027-01-01T05:00Z no
2025-12-31T20:00-10:00 (local 31 Dec 2025) no
the same instant written 2026-01-01T06:00Z yes

  • Comparisons without day of use the instant against the UTC boundary. These are:

    • CMS125's six mastectomy exclusions ("on or before end of the period");
    • CMS165's ESRD encounter and procedure, the hypertension-diagnosis window, and the pregnancy/renal diagnosis;
    • CMS137's first SUD episode.

    In CMS125 test case 4cf81a94, with its bilateral mastectomy moved to 2026-12-31T19:00-10:00 (or -05:00), the patient is no longer excluded for 2026. At 13:00 the same day, they are. So an event in the last 10 local hours before a boundary (Hawaii), or the last 5 (Eastern), lands on the wrong side.

Do not hand fqm a zoned period, on 1.8.5 or on master

fqm master converts 2026-01-01T00:00-10:00 .. 2026-12-31T23:59:59.999-10:00 into 2026-01-01T10:00Z .. 2027-01-01T09:59:59.999Z, both at offset 0. day of would then read 1 January 2027 as inside 2026. A real practice-zone period needs fqm to keep the stated offset. Neither version does.

The zone itself is unsettled

backend-ts/src/config/deployment-profile.ts says America/New_York, while the scheduler's comment says Hawaii.

To do

  • Confirm the practice's zone with MIE, then set practiceTimeZone and its test.
  • List the ingest paths that write Z times, such as WebChart's issued fallback in normalize.ts. Converting a Z instant into the practice offset is a representation change, but it moves the day that day of reads, so it is an owner call.
  • Decide whether the instant-precision cases need a practice-zone period (an fqm change, upstream or patched) or a documented limitation, and record the decision where the measures are described.
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.