Methods Inf Med 2012; 51(06): 529-538
DOI: 10.3414/ME11-02-0023
Focus Theme – Original Articles
Schattauer GmbH

SNOMED CT Implementation

Mapping Guidelines Facilitating Reuse of Data
A. Randorff Højen
1   Department of Health Science and Technology, Medical Informatics, Aalborg University, Denmark
,
K. Rosenbeck Gøeg
1   Department of Health Science and Technology, Medical Informatics, Aalborg University, Denmark
› Institutsangaben
Weitere Informationen

Publikationsverlauf

received:22. August 2011

accepted:21. Mai 2012

Publikationsdatum:
20. Januar 2018 (online)

Summary

Clinical practice as well as research and quality-assurance benefit from unambiguous clinical information resulting from the use of a common terminology like the Systematized Nomenclature of Medicine – Clinical Terms (SNOMED CT). A common terminology is a necessity to enable consistent reuse of data, and supporting semantic interoperability. Managing use of terminology for large cross specialty Electronic Health Record systems (EHR systems) or just beyond the level of single EHR systems requires that mappings are kept consistent. The objective of this study is to provide a clear methodology for SNOMED CT mapping to enhance applicability of SNOMED CT despite incompleteness and redundancy. Such mapping guidelines are presented based on an in depth analysis of 14 different EHR templates retrieved from five Danish and Swedish EHR systems. Each mapping is assessed against defined quality criteria and mapping guidelines are specified. Future work will include guideline validation.

 
  • References

  • 1 Elkin PL, Trusko BE, Koppel R, Speroff T, Mohrer D, Sakji S. et al. Secondary use of clinical data. Studies in health technology and informatics. 2010; 155: 14-29.
  • 2 IHTSDO. SNOMED CT Clinical Terms. User Guide. 2010. Available at. http://ihtsdo.org/fileadmin/user_upload/doc/
  • 3 Wasserman H, Wang J. An applied evaluation of SNOMED CT as a clinical vocabulary for the computerized diagnosis and problem list. AMIA Annual Symposium Proceedings: American Medical Informatics Association. 2003
  • 4 McClay JC, Campbell J. Improved coding of the primary reason for visit to the emergency department using SNOMED. Proceedings of the AMIA Symposium: American Medical Informatics Association. 2002
  • 5 Brown SH, Rosenbloom ST, Bauer BA. et al. Direct Comparison of MEDCIN® and SNOMED CT® for Representation of a General Medical Evaluation Template. American Medical Informatics Association. 2007
  • 6 Chute CG, Cohn SP, Campbell KE, Oliver DE, Campbell JR. The content coverage of clinical classifications. Journal of the American Medical Informatics Association 1996; 3 (03) 224-233.
  • 7 Wade G, Rosenbloom ST. Experiences mapping a legacy interface terminology to SNOMED CT. BMC medical informatics and decision making 2008; 8 (Suppl. 01) Suppl S3
  • 8 Elkin PL, Brown SH, Husser CS. et al. Evaluation of the content coverage of SNOMED CT: ability of SNOMED clinical terms to represent clinical problem lists. Mayo Clinic Proceedings: Mayo Clinic. 2006
  • 9 Brown SH, Bauer BA, Wahner-Roedler DL, Elkin PL. Coverage of Oncology Drug Indication Concepts and Compositional Semantics by SNOMED-CT®. AMIA Annual Symposium Proceedings: American Medical Informatics Association. 2003
  • 10 Spackman KA. Normal forms for description logic expressions of clinical concepts in SNOMED RT. Proceedings of the AMIA Symposium: American Medical Informatics Association. 2001
  • 11 Andrews JE, Richesson RL, Krischer J. Variation of SNOMED CT coding of clinical research concepts among coding experts. Journal of the American Medical Informatics Association 2007; 14 (04) 497-506.
  • 12 Chiang MF, Hwang JC, Alexander CY, Casper DS, Cimino JJ, Starren J. Reliability of SNOMED-CT coding by three physicians using two terminology browsers. AMIA Annual Symposium roceedings. American Medical Informatics Association; 2006
  • 13 Smith B, Brochhausen M. Putting biomedical ontologies to work. Methods Inf Med 2010; 49 (02) 135-140.
  • 14 Schulz S, Hanser S, Hahn U, Rogers J. The Semantics of Procedures and Diseases in SNOMED® CT. Methods Inf Med 2006; 45 (04) 354
  • 15 Rector AL, Brandt S. Why do it the hard way? The case for an expressive description logic for SNOMED. Journal of the American Medical Informatics Association 2008; 15: 744-751.
  • 16 Cornet R. Definitions and Qualifiers in SNOMED CT. Methods Inf Med 2009; 48 (02) 178-183.
  • 17 Dolin RH, Spackman KA, Markwell D. Selective retrieval of pre-and post-coordinated SNOMED concepts. Proceedings of the AMIA Symposium. American Medical Informatics Association; 2002
  • 18 IHTSDO. SNOMED Clinical Terms. Technical Reference guide. 2008; Available at. SNOMED_ CT_Technical_Reference_Guide_20080731.pdf 2010
  • 19 Cornet R, de Keizer N. Forty years of SNOMED: a literature review. BMC Medical Informatics and Decision Making 2008; 8 (Suppl. 01) Suppl S2
  • 20 Rogers J. Quality assurance of medical ontologies. Methods of Information in Medicine - Methodik der Information in der Medizin 2006; 45 (03) 267-274.
  • 21 Lee DH, Lau FY, Quan H. A method for encoding clinical datasets with SNOMED CT. BMC medical informatics and decision making 2010; 10: 53
  • 22 IHTSDO. SNOMED Clinical Terms. Technical Implementation Guide. 2010; Available at. http://ihtsdo.org/fileadmin/user_upload/doc/
  • 23 Rasmussen AR, Rosenbeck K. SNOMED CT implementation: implications of choosing clinical findings or observable entities. Studies in health technology and informatics 2011; 169: 809-813.
  • 24 Zhang GO, Bodenreider O. Large-scale, exhaustive lattice-based structural auditing of SNOMED CT. AMIA Annual Symposium Proceedings. American Medical Informatics Association; 2010
  • 25 Rector AL. Clinical terminology: why is it so hard?. Methods Inf Med 1999; 38: 239-252.
  • 26 Bakhshi-Raiez F, Ahmadian L, Cornet R, de Jonge E, de Keizer NF. Construction of an Interface Terminology on SNOMED CT. Generic Approach and Its Application in Intensive Care. Methods Inf Med. 2010: 49
  • 27 Park H, Lundberg C, Coenen A, Konicek D. Evaluation of the content coverage of SNOMED CT representing ICNP seven-axis version 1 concepts. Methods Inf Med 2011; 50 (05) 472-478.
  • 28 Ryan A, Eklund P, Esler B. Toward the interoperability of HL7 v3 and SNOMED CT: a case study modeling mobile clinical treatment. Studies in health technology and informatics 2007; 129: 626-630.
  • 29 Qamar R R, Kola JS, Rector AL. Unambiguous data modeling to ensure higher accuracy term binding to clinical terminologies. AMIA Annual Symposium Proceedings. American Medical Informatics Association; 2007