Comparing and evaluating terminology services application programming interfaces: RxNav, UMLSKS and LexBIG

Jyotishman Pathak, Lee Peters, Christopher Chute, Olivier Bodenreider

Research output: Contribution to journalArticle

Abstract

To facilitate the integration of terminologies into applications, various terminology services application programming interfaces (API) have been developed in the recent past. In this study, three publicly available terminology services API, RxNav, UMLSKS and LexBIG, are compared and functionally evaluated with respect to the retrieval of information from one biomedical terminology, RxNorm, to which all three services provide access. A list of queries is established covering a wide spectrum of terminology services functionalities such as finding RxNorm concepts by their name, or navigating different types of relationships. Test data were generated from the RxNorm dataset to evaluate the implementation of the functionalities in the three API. The results revealed issues with various aspects of the API implementation (eg, handling of obsolete terms by LexBIG) and documentation (eg, navigational paths used in RxNav) that were subsequently addressed by the development teams of the three API investigated. Knowledge about such discrepancies helps inform the choice of an API for a given use case.

Original languageEnglish (US)
Pages (from-to)714-719
Number of pages6
JournalJournal of the American Medical Informatics Association
Volume17
Issue number6
DOIs
StatePublished - Nov 2010
Externally publishedYes

Fingerprint

RxNorm
Terminology
Information Storage and Retrieval
Documentation
Names

ASJC Scopus subject areas

  • Health Informatics

Cite this

Comparing and evaluating terminology services application programming interfaces : RxNav, UMLSKS and LexBIG. / Pathak, Jyotishman; Peters, Lee; Chute, Christopher; Bodenreider, Olivier.

In: Journal of the American Medical Informatics Association, Vol. 17, No. 6, 11.2010, p. 714-719.

Research output: Contribution to journalArticle

@article{20318d085b724c9a9b97f3e6ddd9193e,
title = "Comparing and evaluating terminology services application programming interfaces: RxNav, UMLSKS and LexBIG",
abstract = "To facilitate the integration of terminologies into applications, various terminology services application programming interfaces (API) have been developed in the recent past. In this study, three publicly available terminology services API, RxNav, UMLSKS and LexBIG, are compared and functionally evaluated with respect to the retrieval of information from one biomedical terminology, RxNorm, to which all three services provide access. A list of queries is established covering a wide spectrum of terminology services functionalities such as finding RxNorm concepts by their name, or navigating different types of relationships. Test data were generated from the RxNorm dataset to evaluate the implementation of the functionalities in the three API. The results revealed issues with various aspects of the API implementation (eg, handling of obsolete terms by LexBIG) and documentation (eg, navigational paths used in RxNav) that were subsequently addressed by the development teams of the three API investigated. Knowledge about such discrepancies helps inform the choice of an API for a given use case.",
author = "Jyotishman Pathak and Lee Peters and Christopher Chute and Olivier Bodenreider",
year = "2010",
month = "11",
doi = "10.1136/jamia.2009.001149",
language = "English (US)",
volume = "17",
pages = "714--719",
journal = "Journal of the American Medical Informatics Association : JAMIA",
issn = "1067-5027",
publisher = "Oxford University Press",
number = "6",

}

TY - JOUR

T1 - Comparing and evaluating terminology services application programming interfaces

T2 - RxNav, UMLSKS and LexBIG

AU - Pathak, Jyotishman

AU - Peters, Lee

AU - Chute, Christopher

AU - Bodenreider, Olivier

PY - 2010/11

Y1 - 2010/11

N2 - To facilitate the integration of terminologies into applications, various terminology services application programming interfaces (API) have been developed in the recent past. In this study, three publicly available terminology services API, RxNav, UMLSKS and LexBIG, are compared and functionally evaluated with respect to the retrieval of information from one biomedical terminology, RxNorm, to which all three services provide access. A list of queries is established covering a wide spectrum of terminology services functionalities such as finding RxNorm concepts by their name, or navigating different types of relationships. Test data were generated from the RxNorm dataset to evaluate the implementation of the functionalities in the three API. The results revealed issues with various aspects of the API implementation (eg, handling of obsolete terms by LexBIG) and documentation (eg, navigational paths used in RxNav) that were subsequently addressed by the development teams of the three API investigated. Knowledge about such discrepancies helps inform the choice of an API for a given use case.

AB - To facilitate the integration of terminologies into applications, various terminology services application programming interfaces (API) have been developed in the recent past. In this study, three publicly available terminology services API, RxNav, UMLSKS and LexBIG, are compared and functionally evaluated with respect to the retrieval of information from one biomedical terminology, RxNorm, to which all three services provide access. A list of queries is established covering a wide spectrum of terminology services functionalities such as finding RxNorm concepts by their name, or navigating different types of relationships. Test data were generated from the RxNorm dataset to evaluate the implementation of the functionalities in the three API. The results revealed issues with various aspects of the API implementation (eg, handling of obsolete terms by LexBIG) and documentation (eg, navigational paths used in RxNav) that were subsequently addressed by the development teams of the three API investigated. Knowledge about such discrepancies helps inform the choice of an API for a given use case.

UR - http://www.scopus.com/inward/record.url?scp=78650425307&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=78650425307&partnerID=8YFLogxK

U2 - 10.1136/jamia.2009.001149

DO - 10.1136/jamia.2009.001149

M3 - Article

C2 - 20962136

AN - SCOPUS:78650425307

VL - 17

SP - 714

EP - 719

JO - Journal of the American Medical Informatics Association : JAMIA

JF - Journal of the American Medical Informatics Association : JAMIA

SN - 1067-5027

IS - 6

ER -