ArticleJournal of biomedical informatics2009
A graph-based approach to auditing RxNorm.
Article in Journal of biomedical informatics, 2009. The graph could read no effect estimate from its abstract, so it casts no vote on the map. Cited by 7 papers.
What it found
Each row is one number read from the abstract, on the scale the paper reported it, with its interval. Left of the dashed line favours the treatment, right favours the comparator. Under each row is the sentence it came from. New to these charts? A ten-minute tutorial.
The abstract states no effect estimate the extractor could read, or names no intervention and outcome on the map, so this paper lights no cell and moves no belief. It is still indexed, cited and linked below.
The trial behind it
Trials whose registry record cites this paper, or whose number appears in the abstract. A trial that started after this paper was published is citing it as background, not reporting it.
Neither the registry nor the abstract names a trial number. If this is a trial report, that itself is worth knowing.
Who cites it
7 citing papers in PubMed.
- Comparison of UMLS terminologies to identify risk of heart disease using clinical notes.Journal of biomedical informatics · 2015Article
- Evaluation of Herbal and Dietary Supplement Resource Term Coverage.Studies in health technology and informatics · 2015Article
- Mapping Partners Master Drug Dictionary to RxNorm using an NLP-based approach.Journal of biomedical informatics · 2012Article
- Quality assurance in LOINC using Description Logic.AMIA ... Annual Symposium proceedings. AMIA Symposium · 2012Article
- Using RxNorm for cross-institutional formulary data normalization within a distributed grid-computing environment.AMIA ... Annual Symposium proceedings. AMIA Symposium · 2011Article
- Managing Medical Vocabulary Updates in a Clinical Data Warehouse: An RxNorm Case Study.AMIA ... Annual Symposium proceedings. AMIA Symposium · 2010Article
- Development and evaluation of an ensemble resource linking medications to their indications.Journal of the American Medical Informatics Association : JAMIAArticle
Corrections and comments
PubMed lists nothing against this paper. Absence here is not a guarantee, only a check that was made.
Authors and funding
2 authors.
Funding
Abstract
objectivesRxNorm is a standardized nomenclature for clinical drug entities developed by the National Library of Medicine. In this paper, we audit relations in RxNorm for consistency and completeness through the systematic analysis of the graph of its concepts and relationships.
methodsThe representation of multi-ingredient drugs is normalized in order to make it compatible with that of single-ingredient drugs. All meaningful paths between two nodes in the type graph are computed and instantiated. Alternate paths are automatically compared and manually inspected in case of inconsistency.
resultsThe 115 meaningful paths identified in the type graph can be grouped into 28 groups with respect to start and end nodes. Of the 19 groups of alternate paths (i.e., with two or more paths) between the start and end nodes, 9 (47%) exhibit inconsistencies. Overall, 28 (24%) of the 115 paths are inconsistent with other alternate paths. A total of 348 inconsistencies were identified in the April 2008 version of RxNorm and reported to the RxNorm team, of which 215 (62%) had been corrected in the January 2009 version of RxNorm.
conclusionThe inconsistencies identified involve missing nodes (93), missing links (17), extraneous links (237) and one case of mix-up between two ingredients. Our auditing method proved effective in identifying a limited number of errors that had defeated the quality assurance mechanisms currently in place in the RxNorm production system. Some recommendations for the development of RxNorm are provided.
Indexed as
Identifiers
What OpenQuestion holds
Registered trials
Read under generation 80e0d062 · epoch 390. Bibliography from PubMed, PubMed Central and OpenAlex; grants from NIH RePORTER; trial links from ClinicalTrials.gov; estimates, votes and beliefs from the OpenQuestion graph.