TRV-2026-1278Version 3 · Revised

Saved · see the current record

Why this version exists

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

The exact text we saved

This is the version exactly as it was saved, character for character. The SHA-256 hash below is a 64-character code worked out from that text. Run the same text through SHA-256 and you get the same code; change a single letter and the code comes out completely different. Each version also stores the previous version’s hash, which chains them together so no version can be swapped out quietly.

TRUVACE RECORD VERSION
record: TRV-2026-1278
version: 3
kind: revised
reason: Voice pass: plainer wording and study attribution; no facts or figures changed.
timestamp: 2026-11-05T11:20:04.963985Z
status: published
lens: g_space
sector: health
headline: Development and Validation of Human-AI Collaborative Workflow in SNOMED CT Mapping of Bilingual Clinical Text
dek: 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…
gain_title: 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%.
problem_title: (none)
trace_subject: (none)
gain_reading: 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%.
gain_evidence: reduced total mapping time by 53.9% (from 1.57 to 0.72 min per segment, including agent processing)
problem_reading: (none)
problem_evidence: (none)
quick_read: At a tertiary academic hospital in South Korea, researchers developed an LLM agent system to map bilingual free-text clinical narratives to SNOMED CT and tested it in a human-AI collaborative workflow against human-only mapping by three health information managers on 2,261 segments.

The collaborative approach matters because SNOMED CT mapping is labor-intensive but critical for semantic interoperability; the study shows accuracy gains alongside a 53.9% time reduction, though it remains uncertain how well the results transfer beyond one hospital, one language pair, and the nine categories studied.
limitation: 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.
tag: Evidence-backed gain
key_points: Study used 2,261 de-identified clinical text segments across nine clinical categories collected at a tertiary academic hospital in South Korea. | System comprised translation, abbreviation expansion, and vector-based retrieval components integrated with a pre-embedded SNOMED CT vector database. | Three health information managers compared human-only, Agent-only, and Agent-assisted human mapping using hit rate, precision, recall, F1 at k=1 and 5, and R-precision. | Modular architecture supports periodic vector database updates without retraining for bilingual terminology standardization.
rundown: Researchers built a three-module agent with translation, abbreviation expansion, and vector retrieval linked to a pre-embedded SNOMED CT database, then tested it on 2,261 de-identified bilingual segments from nine clinical categories.

Three health information managers mapped the same segments under human-only, Agent-only, and Agent-assisted conditions, with performance measured by hit rate, precision, recall, F1 at k=1 and 5, and R-precision, plus time per segment.
sources:
- peer_reviewed | Journal of Medical Systems | https://doi.org/10.1007/s10916-026-02465-3 | 2026-10-02
prev: 6744f44bed9d4c1d7ce685674fe98e417f267ca4fdc09bba56932d7a7ea12ede
SHA-256 hash
d2be9184d067593404874269d01a35f98ca8ad77c48ee4da60d322f0ca7760ce
Previous version’s hash
6744f44bed9d4c1d7ce685674fe98e417f267ca4fdc09bba56932d7a7ea12ede
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.