TRV-2026-1278Certified recordPeer-reviewed

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

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…

Health · Good Space — documented gain · certified 2026-10-04 · v1 · article view · machine-readable

Current reading — gain

A three-module LLM agent system for bilingual clinical text expanded valid SNOMED CT candidates for expert mappers, raising hit rate@1 and R-precision while cutting per-segment mapping time by about half.

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.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1278, v1: “Development and Validation of Human-AI Collaborative Workflow in SNOMED CT Mapping of Bilingual Clinical Text.” Truvace, 2026-10-04. /record/TRV-2026-1278 (accessed at citation time). sha256 f8c61e658bf75764…

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv1f8c61e658bf7…

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1278 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.