title: Clinical event monitoring at the University of Pittsburgh.
abstract: Although the literature on event monitoring is extensive, it does not cover all issues that we encountered while developing an event monitor at our institution. We had to resolve issues related to event detection, scalability, what topics were suitable for asynchronous decision support, and overlap of efforts of other groups at the institution attempting to improve quality and lower cost of care. In this paper, we describe our experience deploying CLEM, the clinical event monitor at the University of Pittsburgh with emphasis on these topics.
authors.affiliation: Center for Biomedical Informatics, University of Pittsburgh, USA.
authors.forename: M M
authors.initials: MM
authors.lastname: Wagner
authors.forename: M
authors.initials: M
authors.lastname: Pankaskie
authors.forename: W
authors.initials: W
authors.lastname: Hogan
authors.forename: F C
authors.initials: FC
authors.lastname: Tsui
authors.forename: S A
authors.initials: SA
authors.lastname: Eisenstadt
authors.forename: E
authors.initials: E
authors.lastname: Rodriguez
authors.forename: J K
authors.initials: JK
authors.lastname: Vries
mesh_terms: D000046:Academic Medical Centers; D003195:Computer Communication Networks; D020000:Decision Support Systems, Clinical; D005103:Expert Systems; D006751:Hospital Information Systems; D006801:Humans; D008991:Monitoring, Physiologic / Q000379:methods*; D010414:Pennsylvania