Expansion health classification in the API

Abierto
  • ¿Algo no está bien?
#3,003 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
28/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Área
api

Línea de trabajo

Read the definitions in OpenConceptLab/ocl_issues#2942 and the read-only analysis behind OpenConceptLab/ocl_online#549; coordinate the design with Sunny before implementation. The API work depends on mapping classes from OpenConceptLab/ocl_online#640 and references related decisions in #2943. Done means health classes, reasons, counts and per-member details are computed and saved for new and copied expansions, existing expansions can be computed without changing members, and every class and reason has tests.

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

Descripción

component/api decision/blocked signal/has-dependencies signal/needs-human stage/triaged type/feature

Repo: oclapi2 · Depends on: OpenConceptLab/ocl_online#640 for mapping classes

Part of OpenConceptLab/ocl_issues#2942, which has the definitions. The API reports each expansion's health, so users, TBv3 and FHIR can see when an expansion isn't healthy without working it out themselves. The read-only analysis behind OpenConceptLab/ocl_online#549 is the starting point for the logic. Agree the design with Sunny before building.

ACs

  • Each member, concept or mapping, gets a class against the repo version its reference resolved to: member of that release, HEAD, interim resource version, resource-versioned reference, version mismatch, ambiguous, or unattributed.
  • Each expansion is healthy, HEAD-resolved, unhealthy or empty, with every reason that applies: inconsistent resolution, duplicate repo versions, resource-versioned references, unresolved references, interim resource versions, version mismatches, ambiguous or unattributed members.
  • A system-version that fails to resolve (OpenConceptLab/ocl_issues#2943) is a parameter reason, apart from lock failures.
  • Two versions of one source: OpenConceptLab/ocl_issues#2943 rejects them in system-version. A value set whose own references name both is valid in FHIR, so the design says whether it counts under duplicate repo versions.
  • Computed when an expansion is built or copied and saved with it. A command computes it for existing expansions without changing members.
  • Shown on the expansion (class, reasons, counts) and, on request, per member.
  • Tests for every class and reason.
Lenguaje dominante
Sin datos de lenguaje
Estrellas
4
Forks
2
Merge medio
2 h 12 min
PR fusionados (30 d)
1

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 OpenConceptLab/ocl_issues

Todos los issues de OpenConceptLab/ocl_issues

Issues similares

Más issues de Backend & API Design

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.