Scope of Study:
ABC hospital has three main
branches island wide. These branches are not interconnected. Therefore, a
patient who receives treatment from one branch will have to continue his/her
further treatments at the same branch. To avoid this situation, i
am proposing a centralized system for all three branches. For this
purpose we recommend rfid card usage for each patient. Each patient will be
entitled with an electronic card containing all his/her previous medical
treatments, reports and other valued data. This system will allow the patient
to obtain the best medical treatments as available at any of the ABC
hospital branches.
Procedure for an indoor patient
·
Patient requests for a doctor.
·
A doctor is assigned for the patient by help desk.
·
After the 1st visit by the patient, doctor decides
whether the patient should be issued a card for further treatment.
·
If a card is decided to be issued, appropriate details are entered
to the database and a card is issued for the patient.
·
When the patient arrives for a scheduled treatment, the card is
provided for validation of the visit and his previous medical records.
·
The card is updated after every visit.
·
This cycle continues until the patient’s treatment concludes.
Introduction to the database
A
database can be known as a one main component of any system software. This is
because the entire system depends on the data stored in the database. Therefore
the indoor card system we propose for ABC hospital also needs a very strong
database design. When we design the database we always think about the end
user. This system helps to reduce the data redundancy as well.
ABC
hospital has three branches which are situated in three different places.
Therefore, the system needs to access the database from three different places.
Keeping all data in one location arise unnecessary risks. As a solution for
this problem, we have proposed a distributed database system. This reduces the
risks regarding functionality, reliability, capacity, incremental growth and
efficiency
The
database contains large volume of data in relation to patients, doctors,
assistants, treatments, etc. The electronic card of the patient, acts as the
key in this system and the database. The important medical information about
the patient is stored in the portable electronic card. System users can access
the patient’s data and previous records using the electronic card and also can
add new records to the database.
A
database can be known as a one main component of any system software. This is
because the entire system depends on the data stored in the database. Therefore
the indoor card system we propose for ABC hospital also needs a very strong
database design. When we design the database we always think about the end
user. This system helps to reduce the data redundancy as well.
ABC
hospital has three branches which are situated in three different places.
Therefore, the system needs to access the database from three different places.
Keeping all data in one location arise unnecessary risks. As a solution for
this problem, we have proposed a distributed database system. This reduces the
risks regarding functionality, reliability, capacity, incremental growth and
efficiency
The
database contains large volume of data in relation to patients, doctors,
assistants, treatments, etc. The electronic card of the patient, acts as the
key in this system and the database. The important medical information about
the patient is stored in the portable electronic card. System users can access
the patient’s data and previous records using the electronic card and also can
add new records to the database.
To
implement the database of indoor card system we use SQL server 2010.
Associate problems
- Since this is a total new concept, we will have to start
right from the beginning. This means a huge initial financial investment for:
- Work stations
- Networking
-
Card printing machinery
-
Card readers
-
Fully air conditioned environment in order to
safe guard equipment.
-
End users have to be
given a proper trained, since they do not have an exposure to this sort of a
system.
End users have to be
given a proper trained, since they do not have an exposure to this sort of a
system.
- System failure : Eg:-
-
Software/Hardware failure
-
Software/Hardware failure
-
Network failure
-
Unlike
manual systems, we assume this system will need frequent system maintenance
during the early stage depending on the usage, in order to maintain system
performance.
Unlike
manual systems, we assume this system will need frequent system maintenance
during the early stage depending on the usage, in order to maintain system
performance.
Proposed interface designs
Interface ID
|
Interface Name
|
Screen_01
|
Main Screen
|
Screen_02
|
Branch
|
Screen_03
|
Doctor Master
Details
|
Screen_04
|
Doctor Details
|
Screen_05
|
Appointment
|
Screen_06
|
Admit Patient
Treatments
|
Screen_07
|
Patient Details
|
Screen_08
|
Surgery Details
|
*All the screens are not
included in here
Screen_01
Screen_02
Screen_03
Screen_04
Screen_05
Screen_06
Screen_07
Screen_08
*All the screens are not
included in here
Screen_01
Screen_02
Screen_03
Screen_04
Screen_05
Screen_06
Screen_07
Screen_08
Table designs
01)
Attribute Details:
Name
Data
Type And Size
Description
H_Id
int(5)
Hospital ID
H_Name
varchar(20)
Hospital Name
H_Address1
varchar(20)
Hospital Address1
H_Address2
varchar(20)
Hospital Address2
H_City
varchar(20)
Hospital City
H_Email1
varchar(50)
Hospital Email 1
H_Email2
varchar(50)
Hospital Email 2
P_Tel1
bigint(10)
Hospital Telephone 1
P_Tel2
bigint(10)
Hospital Telephone 2
02)
Attribute Details:
Name
Data
Type And Size
Description
B_Id
int(5)
Branch ID
B_Name
varchar(20)
Branch Name
B_Address1
varchar(20)
Patient’s Address1
B_Address2
varchar(20)
Patient’s Address2
B_City
varchar(20)
Patient’s City
B_Email1
varchar(50)
Hospital Email 1
B_Email2
varchar(50)
Hospital Email 2
B_Tel1
bigint(10)
Hospital Telephone 1
B_Tel2
bigint(10)
Hospital Telephone 2
03)
Attribute Details:
Name
Data
Type And Size
Description
D_Id
int(5)
Doctor ID
D_FName
varchar(20)
Doctor‘s First Name
D_MName
varchar(20)
Doctor‘s Middle Name
D_LName
varchar(20)
Doctor‘s Last Name
D_Address1
varchar(20)
Doctor‘s Address1
D_Address2
varchar(20)
Doctor‘s Address2
D_City
varchar(20)
Doctor‘s City
D_DOB
datetime
Doctor‘s Date of Birth
D_NIC
varchar(10)
Doctor‘s NIC No
D_Gender
char(1)
Doctor‘s Gender
D_Tel1
bigint(10)
Doctor‘s Telephone number
D_Tel2
bigint(10)
Doctor‘s Telephone number
D_Experience
decimal(2.00)
Doctor‘s Experience
D_Speciality
varchar(10)
Doctor‘s Speciality
D_WorkingHours
varchar(15)
Doctor‘s Working Hours
04)
Attribute Details:
Name
Data
Type And Size
Description
N_Id
int(5)
Nurse ID
N_FName
varchar(20)
Nurse First Name
N_MName
varchar(20)
Nurse Middle Name
N_LName
varchar(20)
Nurse Last Name
N_Address1
varchar(20)
Nurse Address1
N_Address2
varchar(20)
Nurse Address2
N_City
varchar(20)
Nurse City
N_DOB
datetime
Nurse Date of Birth
N_NIC
varchar(10)
Nurse NIC No
N_Gender
char(1)
Nurse Gender
N_Tel1
bigint(10)
Nurse Telephone number
N_Tel2
bigint(10)
Nurse Telephone number
N_Experience
decimal(2.00)
Nurse Experience
05)
Attribute Details:
Name
Data
Type And Size
Description
P_Id
int(5)
Patient ID
D_Id
int(5)
Doctor ID
N_Id
int(5)
Nurse ID
P_FName
varchar(20)
Patient’s First Name
P_MName
varchar(20)
Patient’s Middle Name
P_LName
varchar(20)
Patient’s Last Name
P_Address1
varchar(20)
Patient’s Address1
P_Address2
varchar(20)
Patient’s Address2
P_City
varchar(20)
Patient’s City
P_DOB
datetime
Patient’s Date of Birth
P_NIC
varchar(10)
Patient’s NIC No
P_Gender
char(1)
Patient’s Gender
P_Tel1
bigint(10)
Patient’s Telephone number
P_Tel2
bigint(10)
Patient’s Telephone number
06)
Attribute Details:
Name
Data
Type And Size
Description
M_Id
int(5)
Medicine ID
B_Id
int(5)
Branch ID
M_Name
varchar(20)
Medicine Name
M_Brand
varchar(20)
Medicine Brand
M_AvailableQty
Bigint(8)
Medicine Available Qty
M_ExpiryDate
datetime
Medicine Expiry Date
M_Dossege
decimal(4.2)
Medicine Dossege
07)
Attribute Details:
Name
Data
Type And Size
Description
C_Id
int(5)
Clinic ID
B_Id
int(5)
Branch ID
C_Description
varchar(20)
Clinic Description
C_Date
varchar(20)
Clinic Date
C_NoOfPaitents
Bigint(8)
Clinic No of Patients
08)
Attribute Details:
Name
Data
Type And Size
Description
W_Id
int(5)
Ward ID
B_Id
int(5)
Branch ID
N_Id
int(5)
Nurse ID
W_Name
varchar(20)
Ward Name
W_NoOfRooms
Int(5)
No of Rooms in the ward
09)
Attribute Details:
Name
Data
Type And Size
Description
W_Id
int(5)
Ward ID
R_No
Int(5)
Room No
R_Type
Int(2)
Room type
R_Description
varchar(20)
Room Description
09)
Attribute Details:
Name
Data
Type And Size
Description
T_Id
int(5)
Treatment ID
D_Id
int(5)
Doctor ID
C_Id
int(5)
Clinic ID
T_Date
datetime
Treatment Date
T_Description
varchar(20)
Treatment Description
T_Authorized
Bit(1)
Treatment Authorized
10)
Attribute Details:
Name
Data
Type And Size
Description
T_Id
int(5)
Treatment ID
P_Id
int(5)
Patient ID
P_NextClinicDate
datetime
Next Clinic Date for the patient
11)
Attribute Details:
Name
Data
Type And Size
Description
M_Id
int(5)
Medicine ID
Pl_Id
int(5)
Patient ID
Pl_Miligrames
Decimal(4.2)
Milligrams for Plill
12)
Attribute Details:
Name
Data
Type And Size
Description
M_Id
int(5)
Medicine ID
Cp_Id
int(5)
Patient ID
Cp_Coate
varchar(10)
Coating for Capsules
13)
Attribute Details:
Name
Data
Type And Size
Description
M_Id
int(5)
Medicine ID
Sy_Id
int(5)
Patient ID
Sy_Mililiters
decimal(4.2)
Milliliters for Syrup
Attribute Details:
Name
Data
Type And Size
Description
M_Id
int(5)
Medicine ID
Vc_Id
int(5)
Patient ID
Vc_SyringeType
byte
Syringe Type
01)
Entity Name: Hospital
Description: Contains details of the Hospital
Attribute Details:
Name
|
Data
Type And Size
|
Description
|
H_Id
|
int(5)
|
Hospital ID
|
H_Name
|
varchar(20)
|
Hospital Name
|
H_Address1
|
varchar(20)
|
Hospital Address1
|
H_Address2
|
varchar(20)
|
Hospital Address2
|
H_City
|
varchar(20)
|
Hospital City
|
H_Email1
|
varchar(50)
|
Hospital Email 1
|
H_Email2
|
varchar(50)
|
Hospital Email 2
|
P_Tel1
|
bigint(10)
|
Hospital Telephone 1
|
P_Tel2
|
bigint(10)
|
Hospital Telephone 2
|
02)
Entity Name: Branch
Description: Contains details of the Branches
Attribute Details:
Name
|
Data
Type And Size
|
Description
|
B_Id
|
int(5)
|
Branch ID
|
B_Name
|
varchar(20)
|
Branch Name
|
B_Address1
|
varchar(20)
|
Patient’s Address1
|
B_Address2
|
varchar(20)
|
Patient’s Address2
|
B_City
|
varchar(20)
|
Patient’s City
|
B_Email1
|
varchar(50)
|
Hospital Email 1
|
B_Email2
|
varchar(50)
|
Hospital Email 2
|
B_Tel1
|
bigint(10)
|
Hospital Telephone 1
|
B_Tel2
|
bigint(10)
|
Hospital Telephone 2
|
03)
Entity Name: Doctor
Description: Contains
details of the Doctors
Attribute Details:
Name
|
Data
Type And Size
|
Description
|
D_Id
|
int(5)
|
Doctor ID
|
D_FName
|
varchar(20)
|
Doctor‘s First Name
|
D_MName
|
varchar(20)
|
Doctor‘s Middle Name
|
D_LName
|
varchar(20)
|
Doctor‘s Last Name
|
D_Address1
|
varchar(20)
|
Doctor‘s Address1
|
D_Address2
|
varchar(20)
|
Doctor‘s Address2
|
D_City
|
varchar(20)
|
Doctor‘s City
|
D_DOB
|
datetime
|
Doctor‘s Date of Birth
|
D_NIC
|
varchar(10)
|
Doctor‘s NIC No
|
D_Gender
|
char(1)
|
Doctor‘s Gender
|
D_Tel1
|
bigint(10)
|
Doctor‘s Telephone number
|
D_Tel2
|
bigint(10)
|
Doctor‘s Telephone number
|
D_Experience
|
decimal(2.00)
|
Doctor‘s Experience
|
D_Speciality
|
varchar(10)
|
Doctor‘s Speciality
|
D_WorkingHours
|
varchar(15)
|
Doctor‘s Working Hours
|
04)
Entity Name: Nurse
Description: Contains
details of the Nurses
Attribute Details:
Name
|
Data
Type And Size
|
Description
|
N_Id
|
int(5)
|
Nurse ID
|
N_FName
|
varchar(20)
|
Nurse First Name
|
N_MName
|
varchar(20)
|
Nurse Middle Name
|
N_LName
|
varchar(20)
|
Nurse Last Name
|
N_Address1
|
varchar(20)
|
Nurse Address1
|
N_Address2
|
varchar(20)
|
Nurse Address2
|
N_City
|
varchar(20)
|
Nurse City
|
N_DOB
|
datetime
|
Nurse Date of Birth
|
N_NIC
|
varchar(10)
|
Nurse NIC No
|
N_Gender
|
char(1)
|
Nurse Gender
|
N_Tel1
|
bigint(10)
|
Nurse Telephone number
|
N_Tel2
|
bigint(10)
|
Nurse Telephone number
|
N_Experience
|
decimal(2.00)
|
Nurse Experience
|
05)
Entity Name: Patient
Description: Contains
details of the indoor patients
Attribute Details:
Name
|
Data
Type And Size
|
Description
|
P_Id
|
int(5)
|
Patient ID
|
D_Id
|
int(5)
|
Doctor ID
|
N_Id
|
int(5)
|
Nurse ID
|
P_FName
|
varchar(20)
|
Patient’s First Name
|
P_MName
|
varchar(20)
|
Patient’s Middle Name
|
P_LName
|
varchar(20)
|
Patient’s Last Name
|
P_Address1
|
varchar(20)
|
Patient’s Address1
|
P_Address2
|
varchar(20)
|
Patient’s Address2
|
P_City
|
varchar(20)
|
Patient’s City
|
P_DOB
|
datetime
|
Patient’s Date of Birth
|
P_NIC
|
varchar(10)
|
Patient’s NIC No
|
P_Gender
|
char(1)
|
Patient’s Gender
|
P_Tel1
|
bigint(10)
|
Patient’s Telephone number
|
P_Tel2
|
bigint(10)
|
Patient’s Telephone number
|
06)
Entity Name: Medicine
Description: Contains
details of the Medicine
Attribute Details:
Name
|
Data
Type And Size
|
Description
|
M_Id
|
int(5)
|
Medicine ID
|
B_Id
|
int(5)
|
Branch ID
|
M_Name
|
varchar(20)
|
Medicine Name
|
M_Brand
|
varchar(20)
|
Medicine Brand
|
M_AvailableQty
|
Bigint(8)
|
Medicine Available Qty
|
M_ExpiryDate
|
datetime
|
Medicine Expiry Date
|
M_Dossege
|
decimal(4.2)
|
Medicine Dossege
|
07)
Entity Name: Clinic
Description: Contains
details of Clinics
Attribute Details:
Name
|
Data
Type And Size
|
Description
|
C_Id
|
int(5)
|
Clinic ID
|
B_Id
|
int(5)
|
Branch ID
|
C_Description
|
varchar(20)
|
Clinic Description
|
C_Date
|
varchar(20)
|
Clinic Date
|
C_NoOfPaitents
|
Bigint(8)
|
Clinic No of Patients
|
08)
Entity Name: Ward
Description: Contains
details of Wards in a hospital
Attribute Details:
Name
|
Data
Type And Size
|
Description
|
W_Id
|
int(5)
|
Ward ID
|
B_Id
|
int(5)
|
Branch ID
|
N_Id
|
int(5)
|
Nurse ID
|
W_Name
|
varchar(20)
|
Ward Name
|
W_NoOfRooms
|
Int(5)
|
No of Rooms in the ward
|
09)
Entity Name: Room
Description: Contains
details of Rooms in a Ward
Attribute Details:
Name
|
Data
Type And Size
|
Description
|
W_Id
|
int(5)
|
Ward ID
|
R_No
|
Int(5)
|
Room No
|
R_Type
|
Int(2)
|
Room type
|
R_Description
|
varchar(20)
|
Room Description
|
09)
Entity Name: Treatment
Description: Contains
details of Treatments
Attribute Details:
Name
|
Data
Type And Size
|
Description
|
T_Id
|
int(5)
|
Treatment ID
|
D_Id
|
int(5)
|
Doctor ID
|
C_Id
|
int(5)
|
Clinic ID
|
T_Date
|
datetime
|
Treatment Date
|
T_Description
|
varchar(20)
|
Treatment Description
|
T_Authorized
|
Bit(1)
|
Treatment Authorized
|
10)
Relationship Name: Patient
gets Treatment
Description: Table
for the Relationship
Attribute Details:
Name
|
Data
Type And Size
|
Description
|
T_Id
|
int(5)
|
Treatment ID
|
P_Id
|
int(5)
|
Patient ID
|
P_NextClinicDate
|
datetime
|
Next Clinic Date for the patient
|
11)
Entity Name: Pills
Description: Generalization
for Medicine
Attribute Details:
Name
|
Data
Type And Size
|
Description
|
M_Id
|
int(5)
|
Medicine ID
|
Pl_Id
|
int(5)
|
Patient ID
|
Pl_Miligrames
|
Decimal(4.2)
|
Milligrams for Plill
|
12)
Entity Name: Capsules
Description: Generalization
for Medicine
Attribute Details:
Name
|
Data
Type And Size
|
Description
|
M_Id
|
int(5)
|
Medicine ID
|
Cp_Id
|
int(5)
|
Patient ID
|
Cp_Coate
|
varchar(10)
|
Coating for Capsules
|
13)
Entity Name: Syrup
Description: Generalization
for Medicine
Attribute Details:
Name
|
Data
Type And Size
|
Description
|
M_Id
|
int(5)
|
Medicine ID
|
Sy_Id
|
int(5)
|
Patient ID
|
Sy_Mililiters
|
decimal(4.2)
|
Milliliters for Syrup
|
14)
Entity Name: Vaccine
Description: Generalization
for Medicine
Attribute Details:
Name
|
Data
Type And Size
|
Description
|
M_Id
|
int(5)
|
Medicine ID
|
Vc_Id
|
int(5)
|
Patient ID
|
Vc_SyringeType
|
byte
|
Syringe Type
|
Comments
Post a Comment