1 / 17

Medical Data Analysis/Record Broker Project Team

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

sandro
Télécharger la présentation

Medical Data Analysis/Record Broker Project Team

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 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. Introduction • Customer: Mid America Heart Institute • a recognized cardiovascular center of excellence • Current Computing Environment • does not support a distributed component-based computing environment.

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

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

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

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

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

  8. Customer’s role • Provide user interface • Define requirements • Define project scope

  9. Medical Data Analysis Broker UML Diagrams

  10. Use Case Diagram • Functional Requirements

  11. System Context Diagram

  12. Medical Record Broker UML Diagrams

  13. Use Case Diagram • Functional Requirements Continued

  14. System Context Diagram

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

  16. EJB Architecture

  17. Project Schedule • See Project Web Site • http://www.cstp.umkc.edu/personal/gwalters/cs551/551_intro.html

More Related