Expansion health classification in the API

Offen
  • Stimmt etwas nicht?
#3,003 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
28/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Bereich
api

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.
Vorherrschende Sprache
Keine Sprachdaten
Sterne
4
Forks
2
Ø Merge
2 Std. 12 Min.
Gemergte PRs (30 T.)
1

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus OpenConceptLab/ocl_issues

Alle Issues in OpenConceptLab/ocl_issues

Ähnliche Issues

Weitere Issues zu Backend & API Design

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.