Expansion health classification in the API

オープン
#3,003 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
28/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
領域
api

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.
主要言語
言語のデータがありません
スター
4
フォーク
2
平均マージ
2時間 12分
マージ済み PR(30日)
1

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

OpenConceptLab/ocl_issues のほかの issue

OpenConceptLab/ocl_issues の issue をすべて見る

似ている issue

Backend & API Design の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。