M. C. Lin (1), D. J. Vreeman (2, 3), C. J. McDonald (4), S. M. Huff (5)
(1) The Department of Biomedical Informatics, The University of Utah, Salt Lake City, UT, USA; (2) Indiana University School of Medicine, Indianapolis, IN, USA; (3) Regenstrief Institute, Inc., Indianapolis, IN, USA; (4) Lister Hill Center, National Library of Medicine, Washington, D.C., USA; (5) Intermountain Healthcare, Salt Lake City, UT, USA
Controlled Vocabulary, LOINC, evaluation research, clinical laboratory information systems
Objectives: We characterized the use of laboratory LOINC® codes in three large institutions, focused on the following questions: 1) How many local codes had been voluntarily mapped to LOINC codes by each institution? 2) Could additional mappings be found by expert manual review for any local codes that were not initially mapped to LOINC codes by the local institution? and 3) Are there any common characteristics of unmapped local codes that might explain why some local codes were not mapped to LOINC codes by the local institution? Methods: With Institutional Review Board (IRB) approval, we obtained deidentified data from three large institutions. We calculated the percentage of local codes that have been mapped to LOINC by personnel at each of the institutions. We also analyzed a sample of unmapped local codes to determine whether any additional LOINC mappings could be made and identify common characteristics that might explain why some local codes did not have mappings. Results: Concept type coverage and concept token coverage (volume of instance data covered) of local codes mapped to LOINC codes were 0.44/0.59, 0.78/0.78 and 0.79/0.88 for ARUP, Intermountain, and Regenstrief, respectively. After additional expert manual mapping, the results showed mapping rates of 0.63/0.72, 0.83/0.80 and 0.88/0.90, respectively. After excluding local codes which were not useful for inter-institutional data exchange, the mapping rates became 0.73/0.79, 0.90/0.99 and 0.93/0.997, respectively. Conclusions: Local codes for two institutions could be mapped to LOINC codes with 99% or better concept token coverage, but mapping for a third institution (a reference laboratory) only achieved 79% concept token coverage. Our research supports the conclusions of others that not all local codes should be assigned LOINC codes. There should also be public discussions to develop more precise rules for when LOINC codes should be assigned
J. Jacobs (1), C. Weir (1), R. S. Evans (1, 2), C. Staes (1)
Appl Clin Inform 2014 5 4: 988-1004
B. Edeler (1), R. W. Majeed (1), J. Ahlbrandt (1), M. R. Stöhr (1), F. Stommel (2), F. Brenck (1), S. Thun (2), R. Röhrig (1)
Methods Inf Med 2014 53 2: 87-91
L. Samal (1), T. A. Stavroudis (2), R. E. Miller (3), H. P. Lehmann (4), C. U. Lehmann (5)
Appl Clin Inform 2011 2 3: 384-394
In recent years, we have witnessed substantial progress in the use of clinical informatics systems...
A For-Discussion-Section in this issue features a pair of discussed review papers on boosting...
Invitation to Apply for the Student Editorial Board 2015/2016 - The Journal Methods of Information...
Information technology in health care has a clear potential to improve the quality and efficiency...
The submission deadline for the Focus Theme on "Big Data and Analytics in Healthcare"...