Ministry of Higher Education

And Scientific Research

University of Baghdad
Computer Science Dep.

DATABASE MANAGEMENT SYSTEM FOR HIGH

BLOOD PRESSURE PATIENT BASED ON ELECTRONIC
HEALTHCARE RECORD

A project

Submitted to the Department of Computer Science as part of

the requirements for obtaining a Bachelor’s degree in
Computer Science

By
ZAHRAA KHALID ABDUL-KAREM

Supervised
ASSIST.PROF.DR. FATEN ABD ALI

July 2020 Dhul Qi'dah 1441

Table of contents

Page No. Title

Chapter One : Introduction 1

1.1 Project Overview 1

1.2 High Blood Pressure Diseases 2

1.3 Objectives of the Project 3

1.4 Project Organization 3

Chapter Two: Research Problem and Methodology Used 4

2.1 Introduction 4

2.2 Research problem 4

2.3 The Methodology 5

2.3.1 Create and Manage Databases 5

2.3.1.1 Solving the Problem of Normalization 6

2.3.1.2 Tables Used in Creating the Database 8

2.3.2 Interface design 16

2.3.2.1 Project Environment Identification 16

2.3.2.2 Design and Implementation 17

Chapter Three : The Practical Part 20

3.1 Introduction 20

3.2 Source Code 20

i
Chapter Four : Results and Discussions 27

4.1 Introduction 27

4.2 The Results of Proposed System 27

4.2.1 First visit interface 27

4.2.2 Second visit interface 29

4.2.2.1 Interface Pertains of Second Test 29

4.2.3 Interface of Reports View 30

4.2.4 Interface of Patients File 31

4.2.5 Interface of Research and Reports 32

References 33

ii
List of Figures
Figure Name Page No.

Figure (1.1) Electronic healthcare record process diagram 1

Figure (1.2) Understanding Blood Pressure Readings 2

Figure (2.1) Tables and relations between them 7

Figure (2.2) The overall framework of HBP system 18

Figure (2.3) The main interface of the proposed HBP 19

system

Figure (4.1) The main interface of HBP system 28

Figure (4.2) The interface of the first visit 28

Figure (4.3) The patient identification interface for the 29

second visit

Figure (4.4) Interface of the second visit 30

Figure (4.5) Reports view Interface 30

Figure (4.6) The interface for viewing patient files 31

Figure (4.7) Interface research and repots 32

iii
List of Tables

Table Name Page No.

Table (2.1) Patient Information 8

Table (2.2) The First Reviews 9

Table (2.3) Diabetes's Information 10

Table (2.4) The Second Reviews 11

Table (2.5) The Re_Reviews 12

Table (2.6) Patients Files 13

Table (2.7) Treatments Information 14

Table (2.8) The Iraqi Governorates 15

iv
Abstract
The main goal of this system is to create database for high blood pressure (HBP)
patients based on the electronic healthcare recodes (HER). This EHR is useful
tool to improve HBP management care. Therefore, the overall framework consist
of several steps including: 1) Dataset collection and analysis, 2) System design, 3)
Implementation and 4) System testing. The real dataset of Iraqi patients are
collected from Primary health care Center in AL-Noor training. These dataset
include Personal information (i.e. Patient id, name, age, Gender, Family Number,
Governorates, Practical situation, Measurements) and Medical information (i.e.
HBP, Diabetes, Cardiovascular disease, Treatment, Physical activity, Smoking).
The system is designed by using a set of programming languages (i.e. C#, SQL).
This system contains a set of interfaces that include interfaces for entering patient
information and modifying them, also can Inquired about information previously
entered. The Ensure that the information system meets quality standard (i.e.,
quality assurance). And Ensuring that the information system is operational and
used , Test different aspects of the system (i.e., response time, response to
boundary data, response to no input, response to heavy volumes of input).

v
 Dedication
To...

My Mother... You have made a great effort for my sake, thank

you
My Father… I couldn't have done it without you
My supervisor “Dr. Fatin Abd Ali”… Thank you for everything
you have given me
My friend (Hala) ... Thank you very much, no one like you to.

Zahraa Khalid

July-2020

vi
 Thanks and appreciation

First thanks, Allah Almighty, and then my parents for all their
efforts since my birth

To these moments, you are everything I love you so much,

I am glad to thank everyone who advised, guided, or

contributed

With me in preparing this research,

And, I especially thank my distinguished Assistance professor

Dr. Faten Abd Ali Al-Bayati for her continuous support and
her valuable advised me

To complete the project successfully,

And I would like to thanks all teaching staff in Department of

Computer Science / College of Science /University of Baghdad
and to everyone who helps me

vii
 Chapter One
Introduction

1.1 Project Overview

Healthcare is an important domain that must be given a high priority. To get the best
administration and care for the patients, healthcare associations in many nations have proposed
different models of healthcare information systems. These models are customized, prescient,
participatory and preventive and are dependent on utilization of electronic health records (EHRs)
and tremendous measures of complex information and high caliber omics information.
Contemporarily, the information of electronic health records are also in heterogeneous formats
[1]. EHRs are designed to be shared with other providers and authorized users may instantly
access a patient’s EHR from across different healthcare providers. Digital medical records may
offer significant advantages both to patients and healthcare providers. Medical errors are reduced
and healthcare is improved based on accurate and up-to-date information, Patient charts are more
complete and clear — without the need to decipher illegible scribbles [2]. The EHRs process can
be shown in Figure (1.1).

Figure (1.1) Electronic healthcare record process diagram [1].

1
1.2 High Blood Pressure Diseases

High blood pressure (HPB), sometimes called arterial hypertension, is a chronic condition in
which the arterial blood pressure is high. This height requires the heart to work harder than usual
to be able to push blood into the blood vessels. Blood pressure consists of two numbers, which
are systolic pressure and diastolic pressure, and this depends on the pressure obtained and
measured during the contraction of the heart muscle (contractility) or relaxation between the
strikes (diastole). The normal systolic blood pressure during rest ranges between 90 - 140 mm
Hg (upper reading) and diastolic between 60 - 100 mm Hg (lower reading). Blood pressure is
considered excessive if it has a value of 90 or 140 mm Hg continuously [3]. There isn’t always
an explanation for the cause of high blood pressure, but most people develop high blood pressure
because of their diet, lifestyle or medical condition [4]. The HBP categories can be illustrated in
Figure (1.2).

Figure (1.2) Understanding Blood Pressure Readings [5].

2
1.3 Objectives of the project

The main goal of High Blood Pressure (HBP) patient’s management system is to create database
based on the electronic healthcare recodes (HER). This EHR is useful tool to improve HBP
management care. Therefore, several objectives of this proposed system that satisfied to manage
and organize the information about patients with HBP efficiently through the electronic system
which includes these Features:

 Transferring ordinary administrative work from manual management to computerized

management, by relying on information systems rules that help in making administrative
decisions as quickly and as less as cost.
 Introduce full transparency and accountability system, which will improve electronic
management within any organization.
 The system provides the ability to enter patient information in a very easy way and also
allows us to modify it in case we made a mistake when entering this information (i.e.
personal or medical).

1.4 Project organization

Chapter Two: In this chapter, we will talk about the problems that we were suffering from
before, and we have eliminated them through this system, as we will talk about the languages
used in the project and the reason for choosing these languages.

Chapter Three: In this chapter, parts of the programming code used in the design of the project
will be clarified.

Chapter Four: In this chapter we will take an overview of the electronic system and explain in
detail with the illustrations, interfaces, as well as control interfaces for data management.

3
 Chapter two
Research problem and methodology used

2.1 Introduction

In this chapter, the research problem and the problems that the project addresses will be
illustrated by designing the electronic system to manage the data of high blood pressure patients,
in addition, to clarifying the research methodology, which includes the techniques and languages
used to accomplish this project, the reasons for its selection and the most important advantages,
as well as the program used in designing the electronic system and the reasons that led to choose.

2.2 Research problem

The electronic systems are one of the most prominent features of the era that we are living in
now, as it is one of the basics of the current reality. The research problem is concentrated in
the absence of an electronic system to manage the data and information of patients with high
blood pressure (HBP) in Iraq (according to our knowledge), through which the information is
entered and saved more efficiently and more accurately. Therefore, the project has been chosen
to address and solve this problem by designing the electronic management system for HBP
patients. The programming language #C is used for designing interfaces because the #C
language is a developed language, very powerful, and despite this, it is characterized by
complete ease in dealing and very many uses. Also, tables were added using Access 2016 and
linked with the interfaces for the purpose of display through Microsoft Visual Studio 2012 to
serve as a comprehensive and integrated system and through it focuses on these services and
their management.

4
2.3 The Methodology

The methodology used in designing and implementing the project consists of two main stages:

1- Database management

2- Interface design

For each stage, a set of appropriate programming techniques and languages have been used, as
will be explained in the following subsections, as well as their most important advantages and
reasons for choosing them.

2.3.1 Create and Manage Databases

The database was created and designed using (Microsoft Access 2016) that illustrated such as
follows:

 Microsoft Access

Microsoft Access is a database management program developed by Microsoft Corporation. The

program comes to package Microsoft Office as part of it and has a graphical interface. There
were several versions of the program, so it was with Office 97, then Office 2000 and Office
2003, and the last version of Office 2013 and the last beta version of HoveS 2016. The program
is distinguished by its ability to call data from different systems for Oracle and SQL databases
and any open database (ODBC).

Access uses software developers, data linguists, and data makers to create complex databases
and link them with various types of called programs. Under this, object and internet programs are
involved, while beginners can use valid evidence bases or create reports on them [6]. Also, more
programmers and designers have been certified by ACCESS internationally to increase demand
and companies for these designers, as there are many forums on the web to teach and teach those
who want to learn Microsoft Access, which is characterized by its support for the Arabic
language.

5
 Uses

Access is most used by companies and among designers and developers of programs, and
companies with high client ratios benefit from it to manage their records, and it is also frequently
used in government companies that deal extensively with people. The Access program is a portal
for storing a lot of information so that it can be called for viewing or amendment at any time [6].

 Access database contents

The Access database includes a collection of tables, forms, reports, queries, and some macros, as
well as contains modules. The electronic database is a container for many objects, and one
database can contain more than one table, and the supplement for databases created in the format
of the Access program for recent versions such as the 2007 version is accdb, while the extension
for the databases created with the file formats for versions for Access Legacy is mdb, and Access
2007 can be used to create and save an old Access file in version (Access 2003 and Access 2002-
2003) [6].

2.3.1.1 Solving the Problem of Normalization

Tables and data have been organized as closely as possible by isolating some information in
separate tables in order to ensure that the main information is not duplicated.

Figure (2.1) is present the correlation between the tables such as shown; we have made some
isolation of these tables as will be mentioned.

6
 Figure (2.1): Tables and relations between them.

As shown in the Figure (2.1), several steps have been done such as the following: -

1- The patient's private information (the patient's name, family number, and the
gender of the patient) are isolated in a table on patients' information.

2- The governorates are isolated in a separate table to reduce data consumption and
stored data.
3- The diabetes screening table are isolated from the first visit table and from the second visit
table because diabetes is not done for every patient in order to ensure that no space is stored
for (diabetes screening information) for each patient but rather only for patients who are
eligible for test and thus we ensure that the storage space is not lost as well as we guarantee
more accurate and optimized data organization.

7
2.3.1.2 Tables Used in Creating the Database

There are several tables are used in creating the database for HBP management system and will
be illustrated such as follows:

1- The first table ‘Patient table’ which contains patient information (Patient id, Patient name,
Patient gender, family number) such as shown in Table (2.1).

Table (2.1): Patient Information.

8
2- The second table ‘First Reviews’ contains the data of the available donor, such as
(Review-Date , patient-id , patient-age , blood-pressure , diabetes , heat-disease , smoker ,
re-review , dr-name , Assignment) such as shown in Table (2.2).

Table (2.2): The First Reviews.

9
3- The third table ‘Diabetes's Information’ contains the diabetes data such as: (diabetes_id ,
patient_id , Diabetes_Type , Diabetes_Screening , Diabetes_Screening_Rusult ,
Diabetes_Screening_Type ) such as presented in Table (2.3).

Table (2.3): Diabetes's Information.

10
4- The table ‘Second Reviews’ of the second visits is a table dedicated to the information that
is taken and recorded for the patient in the event he came in a second visit tabled through
the results of the test on the first visit such as shown in Table (2.4).

Table (2.4): The Second Reviews.

11
5- The table ‘Re-Reviews’ is designed for the indication of patients who are given an
appointment for re-reviews after 3 days such as shown in Table (2.5).

Table (2.5): The Re-Reviews.

12
6- Patient files table ‘Patients Files’ is dedicated to the information of patients with chronic
diseases who have been previously infected or have recently been confirmed, where they
are completed a file for them and store more detailed data and information about them.
Table (2.6) is illustrated this information of Patients Files.

Table (2.6): Patients Files.

13
7- The ‘Treatments table’ is dedicated to the treatment of patients with chronic diseases who
have been previously infected or have been newly confirmed and are taking chronic
therapies, while opening a file for them and storing data. Treatments are also stored in this
table such as presented in Table (2.7).

Table (2.7): Treatments Information.

14
8- Governorates table ‘Governorates’ is a special table for pre-stored Iraqi governorates
that is intended to reduce the consumption of warehouse spaces and reduce the amount of
repetition. Table (2.8) is illustrated Iraqi governorates.

Table (2.8): The Iraqi Governorates.

15
2.3.2 Interface design:

The system design stage represents the main stages in our project to find appropriate solutions to
the research problem that was mentioned previously (section 2.2) and that included several major
steps where it was implemented sequentially, such as follows:

1- Defining the project environment (Project Environment Identification)

2- Design and Implementation (Design and Implementation)

2.3.2.1 Project Environment Identification

This step is important in defining the appropriate technologies and programming languages for
the design of the system that will be explained as follows:

1- The program used

The software used in electronic system design is Microsoft Visual Studio 2016 which is
Microsoft's main integrated development environment. It provides graphical user interface
programming and scripts along with Windows Form, websites, web applications and web
services supported by Microsoft Windows, Windows Mobile, Dot Net framework and Microsoft
Silver Lite.

Visual Studio contains a code editor that supports IntelliSense technology and code rewriting. It
also contains a translator that reveals runtime errors and an interpreter that reveals spelling errors
in the codes. It also contains a template designer to build a graphical user interface, a web
designer, a class designer (computer science class), a database planner, and a designer Crystal
Reports.

Visual Studio 2016 supports many programming languages such as Microsoft C ++, Microsoft
Visual C #, Microsoft Visual Basic, Java script, and many other markup languages such as
HTML, XML, and XSL.

16
2- Programming languages

The electronic system has been designed using the programming language #C. The C# language
is a simple, modern, general-purpose, object-oriented programming language developed by
Microsoft within its .NET initiative led by Anders Hejlsberg [7].

 Features of C# Language

There are many important features of C# language that make it more useful and unique
compared to other languages.

 Fast Speed

 Simple

 Object-Oriented

 Modern Programming Language

 Type-Safe

 Interoperability

 Scalable and Updateable

 Structured Programming Language

 Rich Library

 Component Oriented [8].

2.3.1.2 Design and Implementation:

The overall framework of the proposed management system for High Blood Pressure (HBP)
patients consists of several steps that designed such as depicted in Figure (2.2).

17
 Figure (2.2) The overall framework of HBP system.

In the first stage, data analysis and organization are applied based on real dataset for Iraqi HBP
patients to design and manage EHRs. The second stage is implemented by using ‘Main Interface’
which contains several steps including: 1) First visit, 2) Second visit, 3) Modify visits, 4)
Research and reports and 5) View or Add Patients Files.

In addition, a number of multimedia elements have been used, including: the text, pictures,
menus, and tables, for the purpose of presenting the information related to blood pressure
patients' data management in a clear and interesting way, as shown in Figure (2.3) that shows the
main interface (i.e. First frame) of the project. The implementation steps will be explained with
more detailed in Chapter four and the source code in Chapter three.

18
Figure (2.3) The main interface of the proposed HBP system.

19
 Chapter Three

Practical part

3.1 Introduction:

In this chapter, the main sections of the programming code that used to design and
implement the project will be clarified. The following section presents the 'source
code' for each step has been implemented in our proposed management system of
High blood pressure (HBP) patients.

3.2 Source Code

1- Part of the Code (Patient Data save Button):

private void button1_Click(object sender, EventArgs e)
{
if (textBox1.Text != "")
{
try
{
DataTable dt = new DataTable();
OleDbCommand cmd;
OleDbDataReader r;

if (!U_S)
{
if(f1conect.State != ConnectionState.Open)
f1conect.Open();
cmd = new OleDbCommand("select Patient_ID from First_Reviews
where Form_Sequence = '" + textBox1.Text + "'", f1conect);
r = cmd.ExecuteReader();
dt = new DataTable();
dt.Load(r);

if(f1conect.State != ConnectionState.Closed)
f1conect.Close();
}

if (dt.Rows.Count == 0 || U_S)

20
 {
if (age >= 20)
{
if (textBox2.Text != "" && textBox3.Text != "" &&
textBox10.Text != "" &&
(radioButton1.Checked == true || radioButton2.Checked ==
true) && ((age < 40) ||
(age >= 40 && textBox11.Text != "" &&
(radioButton3.Checked == true || radioButton4.Checked == true))))
{
int c=0;
for (int i = 0; i < textBox2.Text.ToString().Length; i++)
{
if (textBox2.Text[i] == ' ')
c++;
}
if (c == 2)
{
string gender;
if (radioButton1.Checked)
gender = radioButton1.Text;
else
gender = radioButton2.Text;

//update
if (!U_S)
{
if(f1conect.State != ConnectionState.Open)

f1conect.Open();

2- Part of the Code (Patient Data save Button for second visit):

private void button4_Click(object sender, EventArgs e)

{
Close();
}

private void button1_Click(object sender, EventArgs e)

{
if (textBox7.Enabled)
{
try
{
string sta;
if (radioButton3.Checked)
sta = radioButton3.Text;
else
sta = radioButton4.Text;
if(f2conect.State != ConnectionState.Open)
f2conect.Open();

OleDbCommand cmd;
DataTable dt = new DataTable();

21
 if (D_ID != "" && update)
{
cmd = new OleDbCommand("update Diabeteses set Diabetes_Screening
= '" + textBox7.Text + "' , Diabetes_Screening_Rusult = '" + textBox11.Text + "' ,
Diabetes_Screening_Type = '" + sta + "' where Diabetes_ID = " + D_ID, f2conect);
cmd.ExecuteNonQuery();
}
if (update)
{
cmd = new OleDbCommand("update Second_Reviews set
Blood_Pressure_High = '" + textBox5.Text + "' , Blood_Pressure_Low = '" + textBox6.Text +
"' , Blood_Pressure_Result = '" + textBox10.Text + "' where Patient_ID = " + P_ID + " And
Review_Date = #" + dt_R.Month + "/" + dt_R.Day + "/" + dt_R.Year + "#", f2conect);
cmd.ExecuteNonQuery();

Form8.U_State = true;

MessageBox.Show("‫;)"بنجاح البيانات تعديل تم‬

Close();
}
else
{
string T;
if (radioButton3.Checked)
T = radioButton3.Text;
else
T = radioButton4.Text;
cmd = new OleDbCommand("Insert into Diabeteses (Patient_ID ,
Diabetes_Type , Diabetes_Screening , Diabetes_Screening_Rusult , Diabetes_Screening_Type)
" +
"values(" + ID + " , 2 ,
'" + textBox7.Text + "' , '" + textBox11.Text + "' , '" + T + "')", f2conect);
cmd.ExecuteNonQuery();

cmd = new OleDbCommand("select Diabetes_ID from Diabeteses where

Patient_ID = " + ID + " And Diabetes_Type = '2'", f2conect);
OleDbDataReader r = cmd.ExecuteReader();
dt = new DataTable();
dt.Load(r);
cmd = new OleDbCommand("Insert into Second_Reviews (Patient_ID ,
Review_Date , Blood_Pressure_High , Blood_Pressure_Low , Blood_Pressure_Result ,
Diabetes_ID) " +
"values(" + ID + " , #" +
DateTime.Now.Month + "/" + DateTime.Now.Day + "/" + DateTime.Now.Year + "# , '" +
textBox5.Text +
"' , '" + textBox6.Text + "' , '" +
textBox10.Text + "' , " + dt.Rows[0][0].ToString() + ")", f2conect);
cmd.ExecuteNonQuery();

3-Part of the Code (open second visit form button):

22
private void button5_Click(object sender, EventArgs e)
{
if (f3conect.State != ConnectionState.Open)
f3conect.Open();
DateTime dt_R = DateTime.Now.Date;
OleDbCommand cmd = new OleDbCommand("select Patient_ID from Patients where
Patient_Name = '" + comboBox1.SelectedItem.ToString() + "'", f3conect);
OleDbDataReader r = cmd.ExecuteReader();
dt = new DataTable();
dt.Load(r);
if (f3conect.State == ConnectionState.Open)
f3conect.Close();
ID = Convert.ToInt16(dt.Rows[0][0].ToString());
Form f2 = new Form2(comboBox1.SelectedItem.ToString(), ID);
f2.ShowDialog();

4- Part of the Code (Cancel Button):

private void button2_Click(object sender, EventArgs e)
{
if (!update)
Ref();
else
Update_Fill();
}

5- Part of the Code (Close Button):

private void button4_Click(object sender, EventArgs e)
{
Close();
}

6- Part of the Code (Create Report Button):

private void button1_Click(object sender, EventArgs e)
{
string Con_Str;
bool f = true;
if (radioButton1.Checked)
{
Con_Str = "select Form_Sequence As [‫ ]االستمارة تسلسل‬,
First_Reviews.Review_Date As " +
"[‫ ]الزيارة تاريخ‬, Patient_Name As [‫ ]المريض اسم‬, Patient_Gendar As
[‫ ]الجنس‬, " +
"Patient_Age As [‫ ]العمر‬, Blood_Pressure As [‫ ]الدم ضغط‬, Diabetes
As [‫ ]السكري‬, " +
"Heart_Diseases As [‫ ]القلب امراض‬, Smoker As [‫ ]تدخين‬,
First_Reviews.Blood_Pressure_Result As " +
"[‫ ]الغربلة الضغط فحص‬, Sub_Query.Diabetes_Screening_Rusult As [‫فحص‬
‫ ]الغربلة سكر‬, " +

23
 "Second_Reviews.Blood_Pressure_Result As [‫ ]التشخيصي الضغط فحص‬, "
+
"Diabeteses.Diabetes_Screening_Rusult As [‫ " ]التشخيصي السكر فحص‬+
"from Sub_Query left join Diabeteses on Diabeteses.Diabetes_ID
= " +
"Sub_Query.Second_Reviews.Diabetes_ID ";

if (radioButton1_1.Checked)
{
if (comboBox1.SelectedIndex > -1)
{
Con_Str += "where Patient_Name = '" +
comboBox1.SelectedItem.ToString() + "'";
}
else
{
MessageBox.Show("‫;)"المريض اسم تحديد يرجى‬
f = false;
}
}
else
{
if (radioButton1_2.Checked)
{
if (dateTimePicker1_1.Value <= dateTimePicker1_2.Value)
{
Con_Str += "where ((First_Reviews.Review_Date >= #" +
dateTimePicker1_1.Value.Month + "/" + dateTimePicker1_1.Value.Day + "/" +
dateTimePicker1_1.Value.Year + "# " +
"and First_Reviews.Review_Date <= #" +
dateTimePicker1_2.Value.Month + "/" + dateTimePicker1_2.Value.Day + "/" +
dateTimePicker1_2.Value.Year + "#) " +
"or (Second_Reviews.Review_Date >= #" +
dateTimePicker1_1.Value.Month + "/" + dateTimePicker1_1.Value.Day + "/" +
dateTimePicker1_1.Value.Year + "# " +
"and Second_Reviews.Review_Date <= #" +
dateTimePicker1_2.Value.Month + "/" + dateTimePicker1_2.Value.Day + "/" +
dateTimePicker1_2.Value.Year + "#))";
}
else
{
MessageBox.Show("‫او اكبر الثاني التاريخ يكون ان يجب الفترة تاريخ تحديد من تأكد‬
‫;)"االول يساوي‬
f = false;
}
}

7- Part of the Code (Edit data Button):

private void button_E_Click(object sender, EventArgs e)

24
 {
if (dataGridView1.SelectedRows.Count > 0)
{
int index = dataGridView1.Rows.IndexOf(dataGridView1.SelectedRows[0]);
if (Update_Type == 1)
{
Form f1 = new Form1(dt.Rows[index], dt_c[index]);
f1.ShowDialog();

if (U_State)
{
Ref_1();
}
}
else
{
Form f2 = new Form2(dt.Rows[index], dt_c[index], dt_ID[index]);
f2.ShowDialog();

if (U_State)
{
Ref_2();
}

8- Part of the Code (Delete file Button):

private void button_L_Click(object sender, EventArgs e)
{
if (i > 0)
{
i--;
}
else
{
i = dt.Rows.Count - 1;
}

Fill();
}

9- Part of the Code (update data Button):

private void button2_Click(object sender, EventArgs e)
{
Form f3 = new Form3();

25
 f3.ShowDialog();
}

private void button3_Click(object sender, EventArgs e)

{
button3.Visible = false;
panel4.Visible = true;
}

private void button4_Click(object sender, EventArgs e)

{
Form f7 = new Form7();
f7.ShowDialog();
}

private void button7_Click(object sender, EventArgs e)

{
button3.Visible = true;
panel4.Visible = false;
}

private void button8_Click(object sender, EventArgs e)

26
 Chapter Four
Results and Discussions

4.1 Introduction
In this chapter, we will look at an overview of the results that obtained when applied the
proposed management system for patients with high blood pressure (HBP). The result of each
step will be explained in detail with illustrations as well as the system interfaces in the following
sub-sections.

4.2 The Results of Proposed System

As mentioned in Chapter 2, the overall framework of the proposed management system for High
Blood Pressure (HBP) patients consists of several steps that designed and implemented using
Microsoft Visual Studio 2016 and the programming language c#, respectively. In the first stage,
data analysis and organization are applied based on real dataset for Iraqi HBP patients to design
and manage EHRs. The second stage is implemented by using ‘Main Interface’ which contains
several steps including: 1) First visit, 2) Second visit, 3) Modify visits, 4) Research and reports
and 5) View or Add Patients Files.
The main interface is the first interface presented to the user that shows him a brief summary of
the system and through which he moves to the rest of the system interfaces, and contains several
parts such as shown in Figure (4.1).

4.2.1 First visit interface

This interface is for entering patient information for the first visit which includes:
1-Form Sequence
2-Patient's name
3-Family number
4-Gender type
5-Age

27
Figure (4.1) The main interface of HBP system.

Figure (4.2): The interface of the first visit.

28
4.2.2 Second visit interface
This interface contains a combo box that includes the names of the patients that were entered on
the first visit as shown in Figure (4.3). This process includes important step that explained in
detailed in the following sub-section.

Figure (4.3) The patient identification interface for the second visit.

4.2.2.1 Interface Pertains of Second Test

This interface contains information that pertains to the second test of the patient, and through it
determines the result of the test for the patient. The information can also review of the first visit
to the patient by pressing the “button” of (open the first visit form), and from the button “Save”
the information is saved and from the button “Cancel” the emptying of the cells is removed, and
the exit button is used to exits and returns to the patient identification interface such as shown in
Figure (4.4).

29
 Figure (4.4) Interface of the second visit

4.2.3 Interface of Reports View

In this interface, the reports that are prepared are displayed as well, allowing for modification in
case of dataset that used in our project such as shown in the following Figure (4.5).

Figure (4.5): The Reports View Interface.

30
4.2.4 Interface of Patients File
This interface is intended to display patient information that was previously stored and organized
in a coordinated and divided form and is done through buttons (right, left) to move between files
for patients from the first patient to the second and so on, respectively. In addition, we can also
modify the patient data by pressing Button “Modify” the data to move to the interface of the
amendment or delete the file by pressing the Button “Delete” the file and then confirm the
deletion. Finally, the Button “Exit” is used to close the interface and return to the main interface
or the reporting interface such as seen in Figure (4.6).

Figure (4.6) The interface for viewing patient files.

31
4.2.5 Interface of Research and Reports
This process is important and consists of three main steps including: 1) First visit report, 2)
Second visit report and 3) Patients report. Through which the type of report, its details, and
conditions are determined through an organized research and display technology as shown in
Figure (4.7). In order to create one of these reports, we need to press the button “Create Report”.
Then, the report is prepared and sent to the report display interface for displaying. The exit
button is used to closes the interface and returns to the main interface.

Figure (4.7): Interface research and reports.

32
References
[1] Electronic Health Record - an overview | Science Direct Topics Science Direct
(https://www.sciencedirect.com › topics)

[2] Electronic Records in Present-Day Healthcare System | by

https://medium.com/sciforce/electronic-records-in-present-day-healthcare-system-2d664

[3] High Blood Pressure | American Heart Association (https://www.heart.org/en/health-

topics/high-blood-pressure)
[4] High blood pressure (hypertension) - Symptoms and causes - Mayo Clinic
(https://www.mayoclinic.org/diseases-conditions/high-blood-pressure/symptoms-causes/syc-
20373410)

[5] High Blood Pressure (Hypertension) | FDA

https://www.fda.gov/consumers/women/high-blood-pressure-hypertension

[6] Microsoft Access (https://en.m.wikipedia.org/wiki/Microsoft_Access)

[7] C Sharp (programming language)-wikipedia (https://en.m.wikipedea.org)

[8] C# feature-javatpoint (https://www.javatpoint.com)

33
 ‫الملخص‬

‫الهدف الرئيسي من هذا النظام هو إنشاء قاعدة بيانات لمرضى ارتفاع ضغط الدم (‪ )HBP‬على أساس‬
‫سجالت الرعاية الصحية اإللكترونية (‪ .)HER‬يعد هذا ‪ EHR‬أداة مفيدة لتحسين رعاية إدارة ‪ .HBP‬لذلك‬
‫‪ ،‬يتكون اإلطار العام من عدة خطوات بما في ذلك‪ )1 :‬جمع وتحليل مجموعة البيانات ‪ )2 ،‬تصميم النظام ‪،‬‬
‫‪ )3‬التنفيذ و ‪ )4‬اختبار النظام‪ .‬يتم جمع مجموعة البيانات الحقيقية للمرضى العراقيين من مركز الرعاية‬
‫الصحية األولية في النور التدريبي ‪ .‬تتضمن مجموعة البيانات هذه معلومات شخصية (أي هوية المريض ‪،‬‬
‫واالسم ‪ ،‬والعمر ‪ ،‬والجنس ‪ ،‬ورقم األسرة ‪ ،‬والمحافظات ‪ ،‬والوضع العملي ‪ ،‬والقياسات) ومعلومات طبية‬
‫(مثل ‪ ، HBP‬والسكري ‪ ،‬وأمراض القلب واألوعية الدموية ‪ ،‬والعالج ‪ ،‬والنشاط البدني ‪ ،‬والتدخين)‪ .‬تم‬
‫تصميم النظام باستخدام مجموعة من لغات البرمجة (مثل ‪ .)SQL ،C #‬يحتوي هذا النظام على مجموعة‬
‫ضا االستفسار عن‬
‫من الواجهات التي تتضمن واجهات إلدخال معلومات المريض وتعديلها ‪ ،‬ويمكن أي ً‬
‫المعلومات التي تم إدخالها مسبقًا‪ .‬ضمان أن نظام المعلومات يفي بمعايير الجودة (أي ضمان الجودة)‪ .‬والتأكد‬
‫من تشغيل نظام المعلومات واستخدامه ‪ ،‬اختبار جوانب مختلفة من النظام (أي ‪ ،‬وقت االستجابة ‪ ،‬االستجابة‬
‫لبيانات محدودة ‪ ،‬االستجابة لعدم اإلدخال ‪ ،‬االستجابة لكميات ضخمة من المدخالت)‪.‬‬

‫‪34‬‬
‫جمهورية العراق‬
‫وزارة التعليم العالي والبحث العلمي‬
‫جامعة بغداد ـ كلية العلوم‬
‫قسم علوم الحاسوب‬

‫نظام إدارة قواعد البيانات لمرضى أرتفاع ضغط الدم على‬

‫أساس سجالت الرعاية الصحية اإللكترونية‬
‫مشروع‬
‫مقدم الى قسم علوم الحاسوب في كلية العلوم ـ جامعة بغداد‬
‫كجزء من متطلبات نيل شهادة البكالوريوس‬
‫في علوم الحاسوب‬

‫من قبل‬
‫زهراء خالد عبدالكريم‬

‫بأشراف‬
‫أ‪.‬م‪.‬د فاتن عبد علي‬

‫‪0202‬تموز‬ ‫‪1441‬ذوالقعدة‬

‫‪35‬‬