Expansion health classification in the API

Aperta
  • Qualcosa non va?
#3,003 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
28/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Ambito
api

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.
Lingua principale
Nessun dato sulla lingua
Stelle
4
Fork
2
Merge medio
2h 12m
PR unite (30g)
1

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di OpenConceptLab/ocl_issues

Tutte le issue di OpenConceptLab/ocl_issues

Issue simili

Altre issue su Backend & API Design

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.