WHCDS-Wireless Health

Care Database System

Presented By:

Randall Okamoto
Pierre LaRoche
Tony Diep
 WHCDS – Wireless
Health Care Database
System

Introduction
Goal
Users
System Requirements
 What is WHCDS
WHCDS is a hospital database system
that stores, organizes, and allows easy
access to:
 Patients’ records
 Diagnoses and treatments

 Medical bills

 Prescriptions
 The Goal of WHCDS
To enhance record keeping
 Faster updating of patient records
To substitute manual filing system
 Less paperwork
To allow easy access of information
among users
 Users of the System
Doctors/Nurses
Hospital Administrators
 Reception, Billings, and other hospital staff
Insurance Companies
Patients’ Pharmacists
System Requirements
Facilitate up to 300 users concurrently
<3 seconds per transaction
System: Windows 2000 or higher
Programming Language: SQL (database)
Security Software: COM+, Active Directory,
(Window NT Domain)
Overview Diagram for
WHCDS
Insurance

Inquiries/
Response

Doctors
Inquiries/
Response
Patient
database
Inquiries/
Response
Inquiries/
Response

Hospital Admin. Pharmacy

 Data Flow Diagram for
WHCDS
User Type View Type
User Swipes
Patient
Smart Card
Profile
Doctors Database
Doctors Module
UserType and PIN
Restricted
Hosp. Medical Access
Hospital Database for Hosp.
Admin.
Administration Admin.
Security Module
Access Only
Module
Pharmacy Pharmacy
Pharmacy
Module Database
Billing
Module
Insurance
Insurance Insurance
Module
Database
 Doctor’s Module
View patients’ personal profile database
View medical history database
 Symptoms/Diagnosis/Treatments
View pharmacy database
 Fill a prescription request to patient’s pharmacist
View insurance database
 To check if patient has proper insurance for a
particular operation
 Hosp. Admin. Module
View patients’ personal profile database
View insurance database
 To send bills for hosp. stay, treatments,
medications, etc.
View bills through billing module
 To ensure bills recorded and sent to the
patient and insurance company
 Billing Module
1. Ask user to input treatments, lab tests
performed, medications used, and prices
2. Calculate costs for patients’ stay, operations
performed, and medications used
3. Ask user to input insurance info.
4. Calculate amount due to patient and
insurance company
5. Review printout: then send email and mail
to patient/insurance company
6. Additionally, a confirmation statement will
be sent to patient/insurance company
Billing Module Data Flow
Diagram
Hospital
Administrator

Billing
Database
Input

Bill Recorded

Review
Medications, Treatments
Patient's SSN SSN Verify SSN Valid
Labs Test, and /Test Bill Generator
Treatments
Received

Inquiry
Valid/Invalid Bill Transferred
Invoice
Treatment Lab Test
Record File Database

Insurance Data Insurance

Patient
Check for Valid Social Inquiry Company
Profile Inquiry
Security Number Verified Coverage
Database

Co-pay/Deductible

Email Invoice

Invoice sent to Invoice

Invoice
Patient/Insurance Generator
Mail Invoice
 System Databases
Patient Profile
Last Name: string
First Name: string
DOB: string
Gender: char
SSN: string
Address: string
Phone Number: string
Email: string

Medical Pharmacy
Height: double Company Name: string
Insurance
Weight: double Pharmacist: string
Company Name: string
Blood Type: string License #: string
Group #: string
Diseases: string Contact #: string
Group Plan: string
Allergies: string Allergies: string
Insurance Agent: string
Treatment: string Treatment: string
Contact #: string
Physician: string Prescriptions: string
Doctor's Name(s): string
Physician Contact #: string Co-Pay: char
Doctors Notes: string Co-Pay Amount: double
 Security Module
Requirements
Authenticate all users
Ensure that all communication is secure
Ensure that data is not changed in
transit
Ensures that data is not read in transit
Leverage from existing security
technology
 How are the
requirements met?
Create user accounts with strong passwords
Use smart cards to accommodate users (no
need to remember long passwords)
All LAN (Ethernet) traffic is encrypted
All Wireless traffic is encrypted
All WAN traffic is encrypted
 Main features
Kerberos encryption
Wire Equivalency Privacy wireless encryption
Virtual Private Network (VPN) for all WAN
connections
Common Object Component plus (COM+)
Use Active Directory to store all security
related configuration settings
Reuse the security configuration tools
available in Windows 2000
 Kerberos
Secure protocol designed at MIT and
incorporated in Windows 2000
Based on RC4 encryption

String = "Hello" Client Server

Key (128 bit)

01010101...00
String = "Hello"

Key (128 bit)

 WEP
Security standard defined by the IEEE
802.11b wireless protocol
Based on RC4 encryption with shared keys
Encrypts all wireless traffic between stations
(Network Interface Cards) and Access Points
(AP)
 VPN
Protocol used for all WAN connections
Establishes a secured communication
link using existing internet connection
 COM+
COM defines a procedure for specifying the
programming interface between modules.
COM interfaces are used to provide services
to modules written in different programming
languages
COM only works between modules on the
same computer
DCOM extends COM to work between
modules located on different computers
DCOM supports security as defined by the
OS (Kerberos)
COM+ extends DCOM by providing support
for transactions
 Active Directory
Secured database which stores all
configuration information in a Windows 2000
domain (group of computers)
Implemented in Windows 2000 server and
resides in the Domain Controller
Queried through the COM programming
interface
Configured with Windows configuration tools
Logical block diagram
COM+ Administrators

Insurance

Microsoft admin tools

COM+

Security
configuration
COM+ data
COM+

Doctor
Security
Module

COM+

Patient
database
Pharmacy
Physical block diagram
Patient database Active Directory

VPN,
Kerberos
Server (Domain
Controller)
Firewall
WAN

Kerberos
Ethernet

WEP, Access
Kerberos TALK / DAT A
TALK R S CS TR R D TD C D
Point

Wireless

Workstations
 Pharmacy and Insurance Service
Modules

What is it …?

What it is for …?

Why use it … ?

How to use it …?
 Pharmacy Service Module

Online Service
 Word Wide Web
 Available 24 / 7
Allow registered pharmacists to access doctor’s
prescription of patients
Fast, Efficient, and Secure
 Eliminate lost prescriptions
 No waiting no hassle better service
 Insurance Service Module

Online Service
 World Wide Web
 Can be access at anytime and anywhere
Allow registered insurance agents to access
their client medical bills
Fast, Easy, Secure
 Save time reduce works faster payment
Pharmacy and Insurance Service Modules
Website

kevinsmith
*************
Pharmacy and Insurance Service Modules
Website (cont)

Joseph Lee
Evan Pharmacy
(213) 445-6789
(213) 445-6788
AH345-GE987
Kevin Smith
MetLife Inc.
(909) 215-7457
(909) 215-7458
AK345635970
Pharmacy and Insurance Service Modules
Website (cont)

Janet Wong
456-8763

Janet Wong
456-8763
Pharmacy and Insurance Service Modules
Website
Level 2 Data Flow Diagram for Pharmacy and

Insurance Service Modules

Pharmacy

PatientName&
Access
Hospital ID
Log In Inquiry Security Module Correct PatientSearch Database
Reply
Access

Response Incorrect
Prescription & T reatment Record
Insurance

First T imeUser
PatientFile
Registration
 Constraints
System does not cater to patients
 Database system designed specifically to those
that pay for it – the hospitals
 Prevents access from outside users
New patient files added only as fast as
DBA/Hosp. staff can enter them
 Ensures security of database from outside
 Still faster than keeping files in file cabinets
 Having patients input the data themselves would
require training and/or special software to
recognize patient’s handwriting which may not be
error proof.
 Benefits
Easy access to patients’ profiles via PC
tablets, hospital terminals, or via web.
Less paperwork
Shorter billing cycle
Enhanced security
Allows >1 hospital accessibility to
database