MétaCan
Menu
Back to cohort
Record W2076069439 · doi:10.1186/1472-6947-8-s1-s3

Experiences mapping a legacy interface terminology to SNOMED CT

2008· article· en· W2076069439 on OpenAlexaff
Geraldine Wade, S. Trent Rosenbloom

Bibliographic record

VenueBMC Medical Informatics and Decision Making · 2008
Typearticle
Languageen
FieldBiochemistry, Genetics and Molecular Biology
TopicBiomedical Text Mining and Ontologies
Canadian institutionsHewlett-Packard (Canada)
FundersU.S. National Library of Medicine
KeywordsSNOMED CTTerminologySystematized Nomenclature of MedicineComputer scienceHealth informaticsInterface (matter)Artificial intelligenceInformation retrievalMedicinePathologyLinguistics

Abstract

fetched live from OpenAlex

BACKGROUND: SNOMED CT is being increasingly adopted as the standard clinical terminology for health care applications. Existing clinical applications that use legacy interface terminology need to migrate to the preferred SNOMED CT standard. In this paper, we describe our experience and methodology for mapping concepts from a legacy system to SNOMED CT. METHODS: Our approach includes the establishment of mapping rules between terminologists and back and forth collaboration of the mapped results through one or more iterations in order to reach consensus on the final maps. RESULTS: We highlight our results not only in terms of the number of matches, quality of maps, use of post-coordination, and multiple maps but also include our observations about SNOMED CT including inconsistencies, redundancies and omissions related to our legacy mapping. CONCLUSION: Our methodology and lessons learned from this mapping exercise may be helpful to other terminologists who may be similarly challenged to migrate their legacy terminology to SNOMED CT. This mapping process and resulting discoveries about SNOMED CT may further contribute to refinement of this dynamic, clinical terminology standard.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.037
metaresearch head score (Gemma)0.106
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.037
Threshold uncertainty score0.198

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0370.106
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0030.004
Science and technology studies0.0040.003
Scholarly communication0.0050.009
Open science0.0040.008
Research integrity0.0030.003
Insufficient payload (model declined to judge)0.0040.001

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.051
GPT teacher head0.341
Teacher spread0.290 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designNot applicable
Domainnot available
GenreMethods

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations47
Published2008
Admission routes1
Has abstractyes

Explore more

Same venueBMC Medical Informatics and Decision MakingSame topicBiomedical Text Mining and OntologiesFrench-language works237,207