Transcript May 29, 2001

MAHI Research Project
Guides :
Dr. D. Medhi
Dr. Y. Lee
Members:
Manish Mehta
Anup Marwadi
Hongming Wang
Quddus Chong
MAHI Research Database
The Current System.
A Proposed System.
Challenges.
Objectives
• Improve the quality of clinical data by
clearly defining data points and tracking
more relevant attributes and dynamically
add data points.
• Increase reliability, timeliness of data
access, make it user friendly.
• Provide a means for making Ad-Hoc
queries.
• Need for generalization, but in accordance
with the current hospital standards.
• A means to incorporate wireless standards
in the existing system.
Database Overview
• The database is made up of 3 parts:
– Quarantine Area: This is the area where all data destined
for the repository is cleansed. Anomalies and exceptions
are addressed in this section
– Repository Area: This is the section where all the
authorative and clinical data is stored. Highly
normalized and non-redundant data storage area.
– Analysis Area: Used for data extraction and analyzing
the data.
Acquire Data
Load/Store
Data
Extract/ Analyze
Data
Quarantine
Repository
Analysis
Current System Configuration
• Windows NT based.
• Microsoft SQL server.
• MS Visual Basic for the front end.
Performance critical elements are created
using VC++. Ad-Hoc queries are developed
using crystal reports provided by VB.
• Front End- The common functions are built
using COM(adv.) or ActiveX modules. No
direct manipulation of databases is allowed.
All accesses through a class object. Secure
transactions using Commit/Rollback.
• Security Issues!!!
Repository Entities
• A patient goes to a location and a caregiver does
something to that patient. In that process a
material may be consumed.
• Various tables are studied.
• Relevance of cross-references are yet to be
determined.
Data Mining in MAHI Project
• Data Cleaning
• Data Integration and Transformation
• Data Mining
Data Cleaning
• Missing values: Ignore the tuple or fill in values
• Noisy data: Binning, Clustering, and Regression
• Inconsistent values: correct manually.
Data Integration and transformation
• Data identification problem: X=Y?
• Redundancy problems: Correlation analysis
• Value conflict.
Data Mining Techniques
• Decision trees: Make right decisions
• Association rules: Find unknown relationships
Data Mining Tools
• Decision trees: C5.0
• Association rules: reference to SONAR
Possible Components
• X_MAKER: decision trees
• Y_FINDER: association rules
• XY_MIXER: decision making based on the \
association rules
MAHI Research Database
• Role of XML technology
Benefits
Benefits
• • Extensible,
Extensible,reusable,
reusable,flexible.
flexible.
• • Provide
Providedocument
documentvalidation
validationthrough
throughDTDs
DTDsand
and
XML
XMLSchema.
Schema.
• • Existing
ExistingXML
XMLspecs
specsfor
formedical
medicalsystems
systems(e.g.
(e.g.
SynExML).
SynExML).
• • Microsoft
Microsoftprovides
providesCOM-compatible
COM-compatibleXML
XML
component
component (MSXML).
(MSXML).
XML in Data Movement
• Client input to be formatted as XML for data
validation and transmission.
• Use of DTDs and XML Schema as validation
template.
• Capability of XML in performing batch processing.
XML in Data Extraction
• Data extracted from data store after query to be
formatted into XML and transmitted to requesting
client.
• Modules/components to do XML formatting should
be part of a middleware layer.
• Web-interface should be designed to allow for adhoc queries.
XML in User Interface
• A dynamic user view can be generated using XSL, but
should be “wrapped” by a main user interface frame.
• For security/platform neutrality/mobility issues, more
investigation into XML-related specifications like SOAP,
WML is needed.
• Two types of client systems to handle different functionality:
q Standard query/view – used by caregivers.
q Analysis – used by clinical researchers/bio-statisticians. This
client will require a customized adaptor to communicate between
middleware layer and local analysis software (e.g. SAS).
Data Flow with XML
User query via
CGI/ASP/JSP
Quarantine
Query
Generator
Component
Data Store
Repository
Data Store
Middleware
Server
Results
(in XML)
Customized
XSL
Stylesheet
Basic Client
Results
(in HTML)
Adaptive View
Component
Adaptor
Interface
Analysis
Data Store
Web-enabled
Browser
Middleware
Layer
Customized
Browser
Results
(in XML) Research/Analysis
Client
Tasks to be addressed
•
•
•
•
Platform Neutral Architecture
Mobility of end users
Simple user Interface
Security
Implementation objectives of my
Interest
• Provide ability to move the data in timely and
• efficient manner. ( WLAN )
• Reduce the load on the end terminals as they can be
• battery operated devices with comparatively low
• computing power (eg. PDA). ( Thin Client )
• Provide security of data and Authentication of
• the users. ( Wireless Security Issues )
• Define different Access Levels for different sets of
• users. ( Multi Level Security )
Why WLAN ?
Wireless LAN systems have shown to meet
the technological and organizational needs of
Health care market by ..
• speeding diagnostic and case analysis time
turnaround
• Reducing Hospital Labor
• Reducing Procedural costs
• Reducing Scheduling time
Issues ( WLAN)
•
•
•
•
•
•
Health Affects
Security
Cost
Range
Throughput
Interoperability with Wired Networks
Thin Client
• The end terminals (can be a wireless device like
PDA) are to be used to populate the Database by
gathering the data and sending to the Server for
processing.
• Similarly the end terminals are to be used only to
query the data and display the data on the user’s
screen.
Security and Authentication
• In Wireless Environment we need to get rid
of unintended receivers ( eavesdroppers )
listening to wireless traffic.
• Every user using the system should be
authenticated by the system.
• Provide Multiple levels of security for
different sets of users.
Issues in Security and
Authentication
• Key distribution for encryption of data
• Key management and Key refreshing issues
• Levels of security and their privileges.