Mapper export: add the CIEL concept behind each bridge match

Abierto
#2,933 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
58/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Área
data

Línea de trabajo

The issue points to the CSV export, the __map_*__ column documentation, and the free-text __result_oclcielbridge_NN__ columns; no file or test is named. Start by locating the export code and its tests, then trace how bridge matches populate rows. Done when bridge rows export the concept id, name, URL, and map type, non-bridge rows leave those columns empty, and the new columns are documented.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

component/mapper decision/ai-ready signal/low-risk signal/well-specified stage/triaged type/feature

For a match found by the CIEL bridge, the CSV export has no column for the CIEL concept the match came through. It's only inside the free-text __result_oclcielbridge_NN__ columns, for example 112480:Severe sepsis --> [BROADER-THAN] --> ….

That concept is what lets a mapping flow on into other systems. OHDSI, for one, gets to OMOP through CIEL's vocabulary in Athena. Today a user has to parse it out of the free text.

Found while preparing the OHDSI 2026 Mapper demo (Mapper 1.0.31-beta).

Related: OpenConceptLab/ocl_issues#2507 (concept details missing from the export).

Acceptance criteria

  • For a row whose mapped concept came via the bridge, the export has columns for the bridge concept (id, name, URL) and the bridge map type (e.g. SAME-AS, BROADER-THAN).
  • They're empty for rows matched without the bridge.
  • The columns are documented with the other __map_*__ export columns.
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

Issues similares

Más issues de Data Engineering

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.