70/100

Moderate evidence

GainPublished recordHealthGood Space

Development and Validation of Human-AI Collaborative Workflow in SNOMED CT Mapping of Bilingual Clinical Text

Truvace record
TRV-2026-1278raw data (JSON)
Version
v3Revised
First published
Evidence type
Controlled or validated comparison
Sources
1 sourcePeer-reviewed
sha256
d2be9184d067…check it

Systematized Nomenclature of Medicine-Clinical Terminology (SNOMED CT) is the principal international standard for semantic interoperability of clinical information, but mapping free-text clinical narratives to SNOMED CT concepts remains labor-intensive. We developed a large language model agent system for mapping bilingual clinical text to SNOMED CT concepts and evaluated its effect on mapping accuracy and efficiency within a human-AI collaborative workflow. We designed a three-module agent system comprising tr…

The gain

In a study at one South Korean hospital, health information managers mapping 2,261 bilingual clinical text segments to SNOMED CT with an AI agent's help were more accurate than human-only mappers and cut mapping time by 53.9%.

What this doesn’t fix

Evaluation was limited to 2,261 segments from a single tertiary academic hospital in South Korea and to bilingual clinical text, which may limit generalizability to other settings and languages.

Sources

1 on file
  1. Journal of Medical Systemsdoi:10.1007/s10916-026-02465-3
    Peer-reviewed2026-10-02

Cite this record

v3

Truvace Impact Record TRV-2026-1278, v3: “Development and Validation of Human-AI Collaborative Workflow in SNOMED CT Mapping of Bilingual Clinical Text.” Truvace, 2026-11-05. /record/TRV-2026-1278 (accessed on the day you copy it). sha256 d2be9184d0675934…

Change history

3 versions

Every change made to this record since it was first published, and why.

  1. Revisedv3d2be9184d067…

    Voice pass: plainer wording and study attribution; no facts or figures changed.

  2. Revisedv26744f44bed9d…

    Editorial pass: sharper headline; gain/problem restated as concrete outcomes.

  3. Publishedv1f8c61e658bf7…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-1278 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.