1. Jump to first page Medical Data Analysis/Record Broker Project Team Team Members: Leader: Tracy Giglio: giglio4@hotmail.com Data Analysis  Kai Unewisse: ku967@umkc.edu  Galina Walters: wgalina@hotmail.com Record Broker  Leader: Gundamaraju Lavanya: lavanya_gr@yahoo.com  Aarti Nankani: aartinankani@yahoo.com

2. Jump to first page Introduction n Customer: Mid America Heart Institute u a recognized cardiovascular center of excellence n Current Computing Environment u does not support a distributed component- based computing environment.

3. Jump to first page Topics of Discussion n Problems with current environment n Our project(s) role n MAHI database project team’s role n Customer’s role n Functional requirements n Proposed system context n Technology and tools for executing the project(s) n Project Schedule

4. Jump to first page Computing Environment Issues n not scalable, flexible, or interoperable n statisticians manipulate data through custom-made applications/programs wasting valuable time that could be spent analyzing the data n OCR data is hard to interpret n Duplicate patient_ids u created in the past because the data was not normalized and database integrity was compromised u requires consolidation consuming human resources

5. Jump to first page Our Role - General n Develop OO middleware n Developing a configurable database connection n Extract data from sample database n Perform server side applications n Resulting output is fed to user interface

6. Jump to first page Our Role - subproject specific n Data Analysis Broker (project 1) u develop server side statistical applications that manipulate the data u integrate commercial off-the-shelf (COTS) components for graphical output. u provide statistical reports in HTML n Record Broker (project 2) u provide work arounds to OCR recognition errors and database accuracy errors u apply work arounds (algorithms) u end result - return one patient_ID

7. Jump to first page MAHI database project team’s role n Provide structure to data (normalize data) n Provide logical validation (consolidate patient records) n Identify relationships n end result - implement relational database

8. Jump to first page Customer’s role n Provide user interface n Define requirements n Define project scope

9. Jump to first page Medical Data Analysis Broker UML Diagrams

10. Jump to first page Use Case Diagram n Functional Requirements

11. Jump to first page System Context Diagram

12. Jump to first page Medical Record Broker UML Diagrams

13. Jump to first page Use Case Diagram n Functional Requirements Continued

14. Jump to first page System Context Diagram

15. Jump to first page Technology/tools for executing new development effort n JAVA2 Enterprise Edition 1.3 and 2.0 - provide server- side and client-side support for developing enterprise, multitier applications n Together 5.5 -UML modeling tool n JBOSS 2.4.1- application server n ANT 1.4 - Java based build tool n TOMCAT 4.0 / JETTY 3.1.0 - web server n JSPChart - graphics components n MS SQLServer /MS Access 2000 - database

16. Jump to first page EJB Architecture

17. Jump to first page Project Schedule n See Project Web Site http://www.cstp.umkc.edu/personal/gwalters/cs551/551_intro. html http://www.cstp.umkc.edu/personal/gwalters/cs551/551_intro. html