Switch to
| Predicate | Object |
|---|---|
| rdf:type | |
| lifeskim:mentions | |
| pubmed:issue |
2
|
| pubmed:dateCreated |
1992-6-4
|
| pubmed:abstractText |
The utility of drug-interaction software is limited by the fact that products on the market are unable to interface with preexisting stored medication lists, so that it is necessary to record medication lists twice. With the variety of automated medical records now in existence, it may be impractical for vendors of drug-interaction software to provide enough interfaces to overcome this problem. However, if vendors allowed greater access to their drug-interaction data, existing automated records could easily be altered to incorporate this clinically relevant information. This article describes a commercially available drug-interaction software package and the logic used to build an interface to a preexisting automated medical record.
|
| pubmed:commentsCorrections | |
| pubmed:language |
eng
|
| pubmed:journal | |
| pubmed:citationSubset |
IM
|
| pubmed:status |
MEDLINE
|
| pubmed:issn |
0724-6811
|
| pubmed:author | |
| pubmed:issnType |
Print
|
| pubmed:volume |
9
|
| pubmed:owner |
NLM
|
| pubmed:authorsComplete |
Y
|
| pubmed:pagination |
115-8
|
| pubmed:dateRevised |
2001-11-26
|
| pubmed:meshHeading | |
| pubmed:articleTitle |
Interfacing a commercial drug-interaction program with an automated medical record.
|
| pubmed:affiliation |
Department of Medicine, Harbor-UCLA Medical Center, Torrance.
|
| pubmed:publicationType |
Journal Article
|