Track ocl-content source loads: ICD-10-CM FY27, WHO-ATC and SNOMED GPS uploads blocked by open decisions

Abierto
  • ¿Algo no está bien?
#2,912 3 comentarios 0 reacciones 1 asignado Ver en GitHub

@filiperochalopes ya está trabajando en esto.

Desde el 14/10/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

decision/blocked signal/has-dependencies signal/high-risk signal/needs-access signal/needs-human signal/small-scope stage/triaged type/docs

User story

As the CIEL content owner, I want every source upload, creation and update tracked in one place, so each load has an owner, its open decisions and an audit gate before anything is written to OCL.

Use case

The ocl-content pipelines build OCL bulk-import bundles for several terminologies. The current drafts for three sources are not ready to load: each audit file has upload_ready: false and the reason is recorded in the source's own open decisions or in a required fresh rehearsal.

Workstreams

Source Load mode Current state Blocked by
US-NCHS / ICD-10-CM FY27 full-source refresh Draft bundle, upload_ready: false Six open decisions in TBD.md: instruction-note model (EXCLUDES1/2, includes, seventh-character notes); hierarchy rule (direct XML containment vs derived ranges); legacy UMLS enrichment (CUI, semantic types) keep or remove; non-official T### semantic-type concepts and B10-B10-style range artifacts (retirement); FY27 release identifier and artifact names
WHO / WHOATC full-source load and retirement update Draft bundle and retirement audit, both upload_ready: false Authority decision (WHOCC ATC/DDD Index 2026 vs BioPortal); cut-off policy for 2027 decisions; UMLS licensing and provenance; fresh OCL snapshot and rehearsal before retirements
SNOMED International / SNOMED GPS full-source refresh to the January 2026 scope Draft bundle, upload_ready: false Fresh OCL snapshot and local rehearsal (the importer replaces collection fields)

Not assessed in this issue: LOINC and the WHO ICD-10 pipeline. Add them when reviewed.

Open questions for the next meeting

  1. Which decision on ICD-10-CM instruction notes (structured property, typed description, or mixed model)? Owner: Joe.
  2. Is the hierarchy the direct XML tree or derived range containment? Owner: Joe.
  3. Are the UMLS CUI and semantic-type values on ICD-10-CM intentional published enrichment to keep, or legacy data to remove? Owner: Joe.
  4. Can the non-official T### concepts and the range artifacts be retired? Owner: Joe.
  5. Approve the WHOCC ATC/DDD Index 2026 as the authority for WHO-ATC, with BioPortal/UMLS for enrichment only? Owner: product team.
  6. Confirm the FY27 version identifier and the WHO-ATC cut-off policy for 2027. Owner: product team.

Acceptance criteria

  • Each workstream has an owner and a status: decided, blocked, or on hold.
  • Each open decision above is answered, or explicitly deferred with a reason recorded here.
  • Before any manual import: a fresh OCL snapshot is taken, a local rehearsal passes, and the audit is reviewed.
  • upload_ready is set to true only after the review above.
  • No automated write to production. Each load is a manual step with its audit attached.
  • Source versions are created only after the release identifier is confirmed.

Technical constraints

  • Production writes are manual; the pipelines do not upload.
  • OCL replaces supplied extras and collection fields wholesale, so a partial refresh can delete data.
  • The WHO-ATC retirement audit used a paginated listing because the HEAD export endpoint returned HTTP 204. Candidate discovery must be re-run before any import.
  • Pipeline work is on the ocl-content repository, branch feature/snomed-gps-icd-10-cm-who-atc (not merged to main).

Related

  • #2725 (Mapper vectorization after a source version release)
  • #2555 (CIEL Lab production migration: formal source canonicals)
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

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.