Expansion health classification in the API

Aberta
  • Algo errado?
#3,003 1 comentário 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
28/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Domínio
api

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.
Linguagem predominante
Sem dados de linguagem
Estrelas
4
Forks
2
Merge médio
2h 12min
PRs com merge (30d)
1

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de OpenConceptLab/ocl_issues

Todas as issues de OpenConceptLab/ocl_issues

Issues semelhantes

Mais issues de Backend & API Design

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.