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

Jump to first page

Introduction Customer: Mid America Heart Institute

a recognized cardiovascular center of excellence

Current Computing Environment does not support a distributed component-

based computing environment.

Jump to first page

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

Jump to first page

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

Jump to first page

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

Jump to first page

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

Jump to first page

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

Jump to first page

Customer’s role

Provide user interface Define requirements Define project scope

Jump to first page

Medical Data Analysis Broker

UML Diagrams

Jump to first page

Use Case Diagram Functional Requirements

Use Case Model: Project 1 - Medical Data Analysis Broker

Generate HTML Results

Nurse

Generate Graph Views

Compute Frequency Distributions for Each ColumnCompute Central Tendency (mean,

median, mode) for each column

MAHI System Owner/Analyst

MAHI Statisticians

Select Multiple Database Columns

<<extend>>

<<include>>

<<include>>

<<extend>>

<<include>>

<<include>>

Jump to first page

System Context Diagram

The human user interacts with the system by means of a standard I/O devices such as the keyboard and Monitor found on the CPU. The characteristics of these standard I/O devices are of no interest because they are handled by the OS and therefore dipicted as the <<external user>> in the diagram.

1

11

Interfaces with GUI through keyboard and Monitor

1..*

1 1

1

1..* Outputs to1..* Inputs to

1

1

1..* inputs to Outputs to

MAHI Data Repository<<external input device>>

MANI System Owner/Analyst

(from Use Case View)

Nurse

(from Use Case View)

Statistician

(from Use Case View)

1

1

MAHI Medical Data Analysis Broker

Compute Mean()Compute Mode()Compute Median()Compute Frequency Distributions()

<<system>><<external user>>

HTML/Graphics Components<<Internal Output Device>>

"Database Explorer" Kelly's User Interface written in VB<<internal IO device>>

Jump to first page

Medical Record BrokerUML Diagrams

Jump to first page

Use Case Diagram Functional Requirements Continued

Use Case Model: Project 2 - Medical Record Broker

Use Patient_ID

Create New Patient_ID

Maually Consolidate Multiple Record Returns

Nurse

Data Repository

Run Algorithm to Match Patient Attributes

Review Query Results

<<extend>>

<<extend>><<extend>>

Review Results of Algorithm Application

MANI System Owner/Analyst

<<include>>

<<extend>>

Enter Patient Attributes

Query Patient Attributes

<<extend>>

Jump to first page

System Context Diagram

The human user interacts with the system by means of a standard I/O devices such as the keyboard and Monitor found on the CPU. The characteristics of these standard I/O devices are of no interest because they are handled by the OS and therefore dipicted as the <<external user>> in the diagram.

11

1

Interfaces with GUI through keyboard and Monitor

1..*

1

11

1..* Inputs to Outputs to

1

1

MANI System Owner/Analyst

(from Use Case View)

<<external user>>MAHI Medical Record Broker

Apply Algorithm()match misspelled names()match OCR errors()Find missing identifiers()Identify SSN spouse errors()Find Transposed numbers DOB()Find Middle Name/First Name Transpositions()

<<system>>

MAHI Data Repository<<internal IO device>>

"Database Explorer" Kelly's User Interface written in VB

Last NamePatient_IDFirst NameMiddle NameDOBSexRaceSSNMedical Record NumberCorporate Identifier Number

query patient_ID()Add patient attributes()

<<internal IO device>>1

Jump to first page

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

Jump to first page

EJB Architecture

Jump to first page

Project Schedule

See Project Web Site :// . . . / / / 551/551_http www cstp umkc edu personal gwalters cs intr

.o html