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

2. 2 DREAMS Decision Support Roles and Messages Decision Support System Roles Inter-role Message 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 U ser Event Monitor D atabase Inference Engine N otification S ystem Recipient Input Generating Module

3. 3 DREAMS Notifier / Notification Overview MPI Destinations Gateways (fax, e-mail, pager, etc.) I nput G enerating M odule N otifier D estinations

4. 4 DREAMS A Notifier System Key Terms Input Generating Module –An application/CDSS that generates the XML formatted clinical message 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 Triggering message –The XML formatted clinical message which the input generating module triggers Notification – The formatted message appearing to the end user on the device of his choice.

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

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

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

8. 8 DREAMS Notifier Schematic view (cont….)  Message Processor: Process the Stored Message subject to Business Logic  Extract Data in Collector Table and ensure Business Logic  Business Logic is ensured by using JAVA/COM components  Notification is generated and stored in the Database  Notification is passed on to distributor for 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 Notification table Notification

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

10. 10 DREAMS Application Architecture 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.

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

12. 12 DREAMS Questions ????