NOTIFIER DREAMS Vijaya Mekala The University of Texas

NOTIFIER DREAMS Vijaya Mekala The University of Texas Health Science Center at Houston Arden Syntax SIG Jan 14, 2003, San Antonio, TX. 1

Decision Support Roles and Messages Input Generating Module User Database Notification System Decision Support System Roles Inter-role Message DREAMS Event Monitor 2 Inference Recipient Engine Example: User updates patient data with an associated rule, event monitor detects event (change in database), calls inference engine, rule generates output and sends it to notifier which routes output to proper recipient

Notifier / Notification Overview Input Generating Module Notifier DREAMS Gateways (fax, e-mail, pager, etc. ) MPI 3 Destinations

A Notifier System Key Terms n Input Generating Module – An application/CDSS that generates the XML formatted clinical message n Notifier – A programming framework that processes, generates and routes personalized and timely notifications to the user via a range of pathways subject to user preference. – Used for on-ambulance CDSS – Used to alert physicians to request for assistance DREAMS n Triggering message – The XML formatted clinical message which the input generating module triggers n Notification – The formatted message appearing to the end user on the device of his choice. 4

A Notifier System A Bird’s eye view IGM Notifier Triggering Message DREAMS The Input Generating Module (CDSS) ØTriggers XML Clinical Message Ø XML Message routed to Notifier ØReceive XML message ØProcess XML message as per pre-determined BI ØFormat Notification as per end-user device Destinations ØDisplay Notifications 5 Destinations Notification

Notifier A Schematic view CDSS Triggering Message DREAMS Triggering message Message Collector 6 Destinations Notifier Notification Message Processor Message Distributor

Notifier Schematic view (cont…. ) § Message Collector Store the collected input messages in the Database Ø Ø DREAMS Ø Input Message received as XML Document Loaded via XML API converts Document into Database-Friendly Format XML document DSS 7 XML API Collector Table

Notifier Schematic view (cont…. ) § Message Processor: Process the Stored Message subject to Business Logic Ø Ø Ø DREAMS Ø Ø Ø Extract Data in Collector Table and ensure Business Logic is ensured by using JAVA/COM components Notification is generated and stored in the Database Notification is passed on to distributor further delivery System also ensures Fail Safe delivery Fail safe delivery is established by escalating messages sequentially and conditionally Process the data according to the rules (Java or COM) and then writes the notifications Message collector table 8 Notification table

Notifier Schematic view (cont…. ) § Message Distributor: Format and Distribute Notification to end-user Ø Ø DREAMS Ø Receive Stored Notification from Processor Achieve Device-Specific format using XSLT Deliver Notification using various Protocols (SMTP, HTTP etc. ) Formatter XSLT Notification Table 9 HTTP

Application Architecture n n DREAMS n 10 Data tier: Storage of the events and notifications in a database for persistent record information. Business Tier: Business objects and rules Data Manipulation and transformation into information that could be used in a stateful manner Presentation tier: Formatting the notification into a device specific format.

Deployment Architecture n Configures where the subsystems are located and how they operate. n Notifier can be deployed on a single server or on multiple servers. MC MP MD Single server DREAMS Pros: Communication Compatibility Single Server Cons: Failure MC Multiple Server Pros: Scalability Failure Availability MP MD Cons: Communication Compatibility 11 Multiple Server

Questions DREAMS 12 ? ?