title: Design of a clinical event monitor.
abstract: The issues and implementation of a clinical event monitor are described. An event monitor generates messages for providers, patients, and organizations based on clinical events and patient data. For example, an order for a medication might trigger the generation of a warning about a drug interaction. A model based on the active database literature has as its main components an event (which triggers a rule to fire), a condition (which tests whether an action ought to be performed), and an action (often the generation of a message). The details of implementing such a monitor are described, using as an example the Columbia-Presbyterian Medical Center clinical event monitor, which is based on the Arden Syntax for Medical Logic Modules.
authors.affiliation: Department of Medical Informatics, Columbia-Presbyterian Medical Center, New York, New York 10032, USA.
authors.forename: G
authors.initials: G
authors.lastname: Hripcsak
authors.forename: P D
authors.initials: PD
authors.lastname: Clayton
authors.forename: R A
authors.initials: RA
authors.lastname: Jenders
authors.forename: J J
authors.initials: JJ
authors.lastname: Cimino
authors.forename: S B
authors.initials: SB
authors.lastname: Johnson
mesh_terms: D001185:Artificial Intelligence; D003195:Computer Communication Networks; D004347:Drug Interactions; D006801:Humans; D007256:Information Systems; D016490:Integrated Advanced Information Management Systems; D016347:Medical Records Systems, Computerized; D008509:Medication Systems; D016571:Neural Networks, Computer; D015203:Reproducibility of Results; D012984:Software; D018511:Systems Integration; D014584:User-Computer Interface