CoChat

Using Commercial Knowledge Bases for Clinical Decision Support: Opportunities, Hurdles, and Recommendations

Open access
Kuperman, G. J., Reichley, R. M., Bailey, T. C. · 2006 · Journal of the American Medical Informatics Association
Cited by 78

The DOI matches its Crossref record; 12 of the 12 references it cites were found in a registry or an index.

Abstract

The quality and safety of health care leaves much to be desired.1,2 Automated clinical decision support (CDS) tools embedded in clinical information systems (CISs) such as computer provider order entry (CPOE) and electronic health records (EHR) applications have the potential to improve care and should be part of any comprehensive approach to improve quality.3,4,5,6 Medication prescribing is a component of health care with well documented quality and safety problems that can be improved by CDS.7,8,9 Medication-related CDS requires that pharmaceutical knowledge be represented in a computable, explicit and unambiguous form. Creating an automated representation of medical knowledge often is the most time consuming step in the development of a CDS system and is known as the “knowledge acquisition bottleneck.”10 For a time, it was hoped that the move toward explicit guidelines in medicine would decrease the knowledge acquisition effort,11 but that has not happened.12 Experiments on data sharing from over a decade ago have not progressed.13 As a result, just a few organizations, primarily academic medical centers, are creating rules and benefiting from CDS,14 but most health care organizations do not have the expertise or resources to create such knowledge bases themselves. One potential solution to the problem of access to automated medication-related knowledge is the set of commercial vendors that supply medication-related knowledge bases for pharmacy and prescribing applications. These vendors' products contain such knowledge as drug-drug and drug-disease interactions, minimum and maximum dosing suggestions, drug-allergy cross-sensitivity groupings, and groupings of medications by therapeutic class. Developers of CISs (either vendor-based or “homegrown”), with appropriate licensing, can incorporate commercial knowledge bases into their products. The knowledge base vendor receives a licensing fee for each CIS implementation and can amortize the costs of knowledge creation over several clients. Any given health care organization pays just a fraction of the total knowledge development costs and is spared the effort of developing the knowledge itself. The CIS developers can create CDS features based on the commercial knowledge base, for example, a drug-drug interaction checking feature within a CPOE application. To the end-user of the CIS, it may not be evident that the CIS application and the knowledge contained therein are two distinct components. The CIS developer may provide end-user configuration tools that allow certain decision support features to be turned on and off. However, several end-user organizations have reported that, when used as the basis for CDS within clinical systems, commercial knowledge bases generate excessive number of alerts, many of which are clinically unhelpful.15 Specific examples include overly sensitive drug-allergy interaction checking,16 drug-drug interaction checking,17 and dose limit checks.18 Such frequent alerts are bothersome to practicing clinicians who deem them to be “nuisance” or “nonsense” alerts. Such nuisance alerts are problematic in various ways. First, they are not helpful in the particular circumstance. Second, they degrade clinician confidence in the entire category of alerts (e.g., a clinically irrelevant maximum dose alert can decrease clinicians' confidence in all maximum dose alerts). Third, excessive nuisance alerts can decrease confidence in the alerting system and CDS as a whole and can cause clinicians to ignore clinically relevant alerts. Fourth, inappropriate CDS may cause clinicians to be dissatisfied with the CIS within which the CDS resides.19,20,21 Such dissatisfaction may impede the nation's progress towards the policy goal22 of rapid and broad dissemination of health information technology. Another problem with the use of commercial knowledge bases is that the tools within the CIS that allow the CDS features to be turned on and off may be inadequate to achieve the alerting functionality desired by the end-user. For example, the tools may permit all class-based duplicate medication alerts to be turned off, but the same tools may not have the capability to turn off the alerting feature for some medications (e.g., antibiotics) while leaving it on for others (e.g., potassium preparations). The result of all these problems is that, in at least some instances, decision support features in CISs that are based on commercial medication knowledge bases have not been well received by the clinician community.15,19 Perhaps it should not be surprising that the use of commercial knowledge bases within CISs results in a large number of alerts. Knowledge base vendors and CIS developers may have incentives (legal as well as financial) to point out when any possible breach of reasonable behavior has occurred. A naïve perspective may be that “any information is good” and some parties may not appreciate the costs of false positive alerts and the human factors involved

Overview

The claims and statistics of this paper haven’t been checked yet.

Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.

A few free checks a day · papers already verified open instantly · results are public

Integrity signals

Registry

Crossref · 10.1197/jamia.m2055

Cites

12 of 12 references verified0 citation errors · 0 not checkable

Statistics

Verification

Claims the paper makes

The claims and statistics of this paper haven’t been checked yet.

Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.

A few free checks a day · papers already verified open instantly · results are public

Self-check

Percentages, sums and reported differences re-computed from the paper’s own numbers.

The self-check needs the paper’s full text.

Citations

Cites

Show all 12 references

Cited by

Metadata

Authors
Kuperman, G. J., Reichley, R. M., & Bailey, T. C.
Venue
Journal of the American Medical Informatics Association
Published
2006-07-01
Volume
13
Issue
4
Pages
369-371
ISSN
  • 1067-5027 (ISSN-L)
  • 1527-974X
OpenAlex
W2188589943
Cited by
78
References
12
FWCI
15.04
Type
journal article
Language
en
Open access
bronze

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review

Data sources

Bibliographic data: Semantic Scholar, OpenAlex, Crossref.

Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).

Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.