Clinic Management System Project Report: January 2021

Download as pdf or txt
Download as pdf or txt
You are on page 1of 85

See discussions, stats, and author profiles for this publication at: https://www.researchgate.

net/publication/382947045

CLINIC MANAGEMENT SYSTEM PROJECT REPORT

Research Proposal · January 2021


DOI: 10.13140/RG.2.2.16327.71847

CITATIONS READS
0 362

1 author:

Kamal Acharya
Tribhuvan University
211 PUBLICATIONS 3,164 CITATIONS

SEE PROFILE

All content following this page was uploaded by Kamal Acharya on 08 August 2024.

The user has requested enhancement of the downloaded file.


AN
INTERNSHIP REPORT
ON
CLINIC MANAGEMENT SYSTEM PROJECT
BY
KAMAL ACHARYA
(Tribhuvan University)

Date: 2021/01/17

i
ABSTRACT

This project is a clinic management system that will be used to solve the current
problems that facing by the local clinic in Malaysia. Clinic Management System is a
web-based platform system. The main objectives of this project is to improve the
business process of the clinic in Malaysia by using the information technology and also
enhance the current clinic management software in the market. The scope of this project
include systematic scheduling in queue list, appointment module with SMS notification,
patient’s registration using MyKad reader and generate medical certificate (MC) to print
out. Systematic scheduling can sort the patient in the queue fairly and display the waiting
time of each patient. Patient can make appointment and notification will be send to their
phone. Besides, patient can use MyKad during the registration at the counter which is
quite convenient and save time. Other than that, MC can be generated and print out on the
paper and doctor just need to sign the MC and chop with his name. As this is a web-based
platform system, C# is the programming language and the project is developed under
ASP.Net framework. The software development methodology that used in this project is
phased development because of fast implementation and short time schedule. The clinic
management system can divide into few phases and each phase consist of few modules
which can easily develop and build up the system in short time.

ii
TABLE OF CONTENTS

DECLARATION OF ORIGINALITY ii

ACKNOWLEDGEMENTS iii

ABSTRACT iv

TABLE OF CONTENTS v

LIST OF FIGURES x

LIST OF TABLES xiii

LIST OF ABBREVATION xv

1.0 Introduction 1

1.1 Motivation and Problem Statement 1

1.1.1 Motivation 1

1.1.2 Problem Statement 3

1.2 Project Scope 4

1.3 Project Objectives 5

1.4 Impact, significance and contribution 6

1.5 Background Information 6

1.5.1 What is health care? How IT helps in this industry? 6

1.5.2 Project Title 7

iii
2.0 Literature Review 8

2.1 First Benchmarked System – SoftClinic 8

2.2 Second Benchmarked System – ClinicPlus 10

2.3 Third Benchmarked System – Vanda Clinical Management Systems 13

2.4 Studies on SMS Implementation 15

2.5 Studies on MyKad Reader 16

2.6 Studies on iTextSharp Library 17

3.0 System Design 19

3.1 Chosen Methodology 19

3.2 System Design and Analysis 22

3.2.1 Use Case Diagram 22

3.2.2 Activity Diagram 23

3.2.3 Sequence Diagram 30

3.2.4 Entity Relationship Diagram (ERD) 33

3.4 Timeline 34

4.0 Interface Design and Requirements 36

4.1 Graphical User Interface Design 36

4.2 Functional Requirement 37

4.3 Non-Functional Requirement 38

4.4 Hardware Specification 38

iv
5.0 Implementation and Testing 39

5.1 Tools/Technology Involved 39

5.2 Implementation Issues and Challenges 39

5.3 User Manual 40

5.3.1 Login Module 40

5.3.2 Dashboard Module 40

5.3.3 Patient Registration Module 41

5.3.4 Patient Edit Module 42

5.3.5 Search Patient Function 42

5.3.6 Queue Patient Module 43

5.3.7 Create Appointment Module 43

5.3.8 List Appointment Module 44

5.3.9 Custom SMS Module 44

5.3.10 SMS List Module 45

5.3.11 Create Visitation Report Module 45

5.3.12 List Visitation Report Module 46

5.3.13 Search Visitation Report Module 46

5.3.14 Generate MC Module 47

5.3.15 List MC Module 48

5.3.16 Clinic Information Module 48

5.3.17 Staff Management Module 49

5.3.18 Add Staff Module 49

v
5.3.19 Edit Staff Module 50

5.4 System Testing 51

5.4.1 Login Module Testing 51

5.4.2 Dashboard Module Testing 51

5.4.3 Patient Registration Module Testing 52

5.4.4 Patient Edit Module Testing 53

5.4.5 Search Patient Function Testing 53

5.4.6 Queue Patient Module Testing 54

5.4.7 Create Appointment Module Testing 55

5.4.8 List Appointment Module Testing 55

5.4.9 Custom SMS Module Testing 56

5.4.10 SMS List Module Testing 57

5.4.11 Create Visitation Report Module Testing 57

5.4.12 List Visitation Report Module Testing 58

5.4.13 Search Visitation Report Module Testing 58

5.4.14 Generate MC Module Testing 59

5.4.15 List MC Module Testing 60

5.4.16 Clinic Information Module Testing 60

5.4.17 Staff Management Module Testing 61

5.4.18 Add Staff Module Testing 62

5.4.19 Edit Staff Module Testing 62

vi
6.0 System Limitations and Future Enhancement 64

6.1 Limitations and Considerations 64

6.2 Possible Future Improvement 64

7.0 Conclusion 66

8.0 References 67

Appendix A Final Year Project Biweekly Report 69

vii
LIST OF FIGURES

Figure Number Title Page

Figure 1-1 Nurse uses a book to do record 2

Figure 2-1 Appointment System in SoftClinic 9

Figure 2-2 Patient Registration Form in SoftClinic 10

Figure 2-3 Queue List in ClinicPlus 11

Figure 2-4 SMS Notification in ClinicPlus 12

Figure 2-5 Queue List Module in Vanda Clinical Management System 14

Figure 2-6 Sample Screenshot of Print Function inside PDF File 18

Figure 3-1 Available Software Methodology 19

Figure 3-2 Phased Development Methodology 20

Figure 3-3 Clinic Management System Use Case Diagram 22

Figure 3-4 Activity Diagram for Make Visitation 23

Figure 3-5 Activity Diagram for Register Patient 24

Figure 3-6 Activity Diagram for Queue Patient 25

Figure 3-7 Activity Diagram for Make Appointment 26

Figure 3-8 Activity Diagram for Notify Patient 27

Figure 3-9 Activity Diagram for Type Visitation Report 28

Figure 3-10 Activity Diagram for Print Report 29

Figure 3-11 Activity Diagram for Generate MC 29

Figure 3-12 Sequence Diagram for Make Visitation 30

viii
Figure 3-13 Sequence Diagram for Make Appointment 31

Figure 3-14 Sequence Diagram for Notify Patient 31

Figure 3-15 Sequence Diagram for Type Visitation Report 32

Figure 3-16 Clinic Management System Entity Relationship Diagram 33

Figure 3-17 Gannt Chart for Final Year Project 1 34

Figure 3-18 Gannt Chart for Final Year Project 2 (Current Semester) 35

Figure 4-1 Logo Design 36

Figure 4-2 Layout Design 36

Figure 4-3 Overview of System Layout 37

Figure 5-1 Login Interface 40

Figure 5-2 Dashboard Interface 40

Figure 5-3 Patient Registration Interface 41

Figure 5-4 Patient Edit Interface 42

Figure 5-5 Search Patient Interface 42

Figure 5-6 Queue Patient Interface 43

Figure 5-7 Create Appointment Interface 43

Figure 5-8 List Appointment Interface 44

Figure 5-9 Custom SMS Interface 44

Figure 5-10 SMS List Interface 45

Figure 5-11 Create Visitation Report Interface 45

Figure 5-12 List Visitation Report Interface 46

Figure 5-13 Search Visitation Report Interface 46

ix
Figure 5-14 Generate MC Interface 47

Figure 5-15 Sample of MC .PDF File 47

Figure 5-16 List MC Interface 48

Figure 5-17 Clinic Information Interface 48

Figure 5-18 Staff Management Interface 49

Figure 5-19 Add Staff Interface 49

Figure 5-20 Edit Staff Interface 50

x
LIST OF TABLES

Table Number Title Page

Table 1-1 Problem Statement in Appointment, Registration and Queue 3


List Module

Table 1-2 Table of Main Objectives and Problems 5

Table 2-1 Table of Method that provided by One Way SMS 16

Table 5-1 Login Module Testing 51

Table 5-2 Dashboard Module Testing 51

Table 5-3 Patient Registration Module Testing 52

Table 5-4 Patient Edit Module Testing 53

Table 5-5 Search Patient Function Testing 54

Table 5-6 Queue Patient Module Testing 54

Table 5-7 Create Appointment Module Testing 55

Table 5-8 List Appointment Module Testing 55

Table 5-9 Custom SMS Module Testing 56

Table 5-10 SMS List Module Testing 57

Table 5-11 Create Visitation Report Module Testing 57

Table 5-12 List Visitation Report Module Testing 58

Table 5-13 Search Visitation Report Module Testing 58

Table 5-14 Generate MC Module Testing 59

Table 5-15 List MC Module Testing 60

xi
Table 5-16 Clinic Information Module Testing 61

Table 5-17 Staff Management Module Testing 61

Table 5-18 Add Staff Module Testing 63

Table 5-19 Edit Staff Module Testing 63

xii
LIST OF ABBREVATION

API Application Programming Interface

IC Identity Card

IE Internet Explorer

IT Information Technology

MC Medical Certificate

NRD National Registration Department

PDF Portable Document Format

RAD Rapid Application Design

SDK Software Development Kit

xiii
Chapter 1 Introduction

1.0 Introduction

1.1 Motivation and Problem Statement

1.1.1 Motivation

Nowadays, there are a lot of clinics in Malaysia. People who suffer from sick or
pain will visit the clinic which nearby their location. However, most of the staff in the
clinic still using paper works in their workflows. Those paper works such as patient
registration using form, patient record using manila card, open bill statement using
handwriting, record appointment using book and so on. Because of these manual
operations are done by few nurses in a clinic, it may slow down the procedure in many
way. For example, when the doctor uses manila cards to write the patient’s diagnosis
record, the manila card need to be keep in the clinic by put them on the cupboard. Once
the clinic operates for few years, there will be a lot of manila cards on the cupboard. So
when a patient comes to the clinic, the nurse maybe need use 3 to 5 minutes to find the
patient’s record card which is quite wasting time.

The information technology improves a lot today. A lot of computer based


systems can help to manage the business process. Michael Hammer and James Champy
define a business process as a collection of activities that take one or more kinds of input
and create an output that is value to the customer (Mathias Weske, 2012, p.4). Once a
system can manage the business process, a lot of works are able to automation and no
need manual operation. Clinic management system is one of the software that available in
the market and able to help the business process of a clinic.

In Malaysia, there are many clinics no matter in public sector or private sector.
However, not all of them are using the clinic management system especially private
sector. The main reason is because the system is not that popular in Malaysia. A lot of
private sector clinics will choose for the traditional manual operation. They feel it is not a
need for a clinic to purchase a system as it is not that reliable for them. For example,

1|Page
Chapter 1 Introduction

everything that can be done in the system is actually just replace the paperwork. As
doctor and nurse are not technical people, therefore they need to learn and know how the
system works. They prefer to stay with the old way which is paperwork and it is quite
convenient to them. Data inconsistency is also another reason they think about. Most of
the staff worry about the power failure and hardware failure of the computer which may
cause the data loss.

Another reason of not using clinic management system is most of the doctors and
nurses don’t aware of the information technology can manage their data efficiently. For
example, appointment that made by patient is record either in a book or on a piece of
paper, it doesn’t notify the patient or doctor about the appointment unless the nurse
reminds them.

From the above stated points, we can know that there are a lot of problems that
exist in the traditional manual operations and available systems in the market.

Figure 1-1 Nurse uses a book to do record

2|Page
Chapter 1 Introduction

1.1.2 Problem Statement

Nowadays, doctor and nurse worry about the available system is because it is not
quite popular and it required some specific skills in order to install or operate it. The
functionality of the system can actually replace using the traditional way which is the
paperwork in their mind. The current clinic management system that available in the
market is just replace the paperwork by using computer and store the data into the
database. The normal functionalities include the patient record management module,
inventory module and billing module. There is not much new functionality that available
in the system. In this project, I intend to solve the problem that the doctor and nurse
worry about in the available system and add in new innovations that help the patient and
staff of clinic in my own developed system.

Compare with the available system, there are a lot of modules inside. I will focus
the problems in these three modules which are appointment, registration and queue list.

Module Problem

Appointment module Patient always forget or remember wrong the date and time for
the appointment they made with the clinic. It will make extra
troubles for the staff of the clinic to rearrange the appointment
with doctor again.

Registration module When a patient first time visits the clinic, he/she need to
register into the system. Nurse needs to type the details of
patient into the system which may slow down the process of
registration and typo will be occurred sometimes.

Queue list module The simple queue list system without any schedule system
makes the patient wait longer. Patient will get frustrated easily
since they are in sick and feel disappointed and won’t visit the
clinic next time.

Table 1-1 Problem Statement in Appointment, Registration and Queue List Module
3|Page
Chapter 1 Introduction

1.2 Project Scope

This project aims to develop a clinic management system for the clinic that
located in Malaysia which is still using the manual operation – paperwork. This system
can be used by doctor and nurse. It suits for any ages of patients especially the old folks.
The clinic management system includes a combination of modules and most of the basic
modules already done in the available system in the market. In order to attract more
clinics to use the system, from the problem statement that I mentioned above, I would
like to focus on 3 modules here which are:

Appointment module – Patient is able to make appointment through the phone and the
staff will record it in the system. After that, system will use the SMS feature to notify the
patient on the day of appointment.

Registration module – When a patient comes to the clinic, he/she needs to register first if
it is the first time visitation. The registration processes will use the IC (MyKad) by insert
into reader to get the basic information such as IC number, full name, address, gender,
race from the chip and store into database. However, if the patient’s age is under 12 or
not Malaysian citizen, manually key in the information is needed.

Queue list module – When a patient wants to see a doctor, first he/she needs to inform the
counter and the nurse will add the patient into queue list. The queue list module will
comes with a time tracking for each patient to know how long they are waiting in the
clinic.

Moreover, doctor can type the diagnosis report for each patient during each
visitation. If there is a need, doctor can print the report as a reference. Besides, doctor can
generate MC and print it out to the patient when the patient is quite serious for illness.

4|Page
Chapter 1 Introduction

1.3 Project Objectives

The main objectives of clinic management system is to improve the current


available system that lack some innovations which are more likely required in the clinic.

Objectives Problems

1) To provide a systematic schedule 1) Patients get frustrated for waiting


system. longer in the clinic because there is no
system keep tracks their waiting time.

2) Some patients which are quite suffer


and making appointment with doctor
cannot be schedule properly.

2) To provide an appointment system with 1) Making appointment through phone


SMS notification. call may cause misinformation with
wrong information received.

2) Patient may forget their appointment.

3) To reduce the workloads and mistakes 1) Filling up the patient details manually
made by the nurse by providing consumes a lot of time.
information received from IC (MyKad).
2) The nurse might key in the wrong
details of patient.

4) Provide a computer generated 1) Using pen to write the details of patient


documents for MC and diagnosis report on MC is time consuming for a doctor.
which minimal the workload of doctor.
2) Doctor or nurse need to find the
historical diagnosis report which is
quite time consuming.

Table 1-2 Table of Main Objectives and Problems

5|Page
Chapter 1 Introduction

1.4 Impact, significance and contribution

At the end of this project, the new functionality in each module will be able to
solve many of the problems. By having these modules in the system, patient that suffer in
sick no need to waste a lot of time in the clinic to see a doctor. This system is able to
decrease the time of a patient waiting in the clinic and also reduce the workloads for a
nurse and doctor when serving the patients.

In addition, with the appointment module that integrated SMS notification, it also
helps to prevent the patient for not being miss the appointment with doctor. Through this
feature, patients no need to worry about they missed out for the appointment and need to
rearrange appointment again.

1.5 Background Information

1.5.1 What is health care? How IT helps in this industry?

Health care is the diagnosis, treatment, and prevention of disease, illness, injury,
and other physical and mental impairments in human beings. Health care is delivered by
practitioners in dentistry, medicine, optometry, pharmacy, psychology and other care
providers. (Freebase, n.d.) When IT starts to be mature, it actually helps to reduce the
workloads and process time for the business process in the health care industry. The
business process includes the patient registration, appointment, billing, inventory and so
on. Nowadays, some of the IT technologies are used to research those new diseases. With
the help of the IT, health care industry is having a very bright future in developing of
health care system that can actually help the patients over the world.

6|Page
Chapter 1 Introduction

1.5.2 Project Title

The title of Clinic Management System in this project is clear enough because the
title is simple for users understanding. Clinic management system would help to solve the
problems by replacing the traditional way of paper works to information system.
However, the title is not specific enough because it is too general as people have different
views regarding the system. For instance, some users might think that this is the system
that let the doctor and nurse use smart phone or tablet to work in the clinic. Instead, this
system uses computer to do those administration tasks with new innovations such as
systematic schedule, SMS notification and MyKad reader.

7|Page
Chapter 2 Literature Review

2.0 Literature Review

Based on the research in the internet, there are a lot of clinic management systems
around the world. However based on Malaysia, there are only a few clinic management
systems in the market. Three of the existing benchmarked systems that available in the
market will be chosen as my literature review by compare their features in three modules
which are appointment, registration and queue list that I stated above. Besides, some of
the problem domains will be studied independently.

2.1 First Benchmarked System – SoftClinic

SoftClinic is a software system that available in the market. Their company JVS
Group founded in USA but currently office located at Nepal. SoftClinic software
designed keeping in mind all the physicians is currently being used by over 500 doctors
every day in Nepal and other countries. Awarded one of the Best Hospital Management
Software by various Physicians & Surgeons Association, SoftClinic can be used by all
physicians, small hospitals & nursing homes for computerizing their entire facility. (JVS
Group, n.d.)

Strengths

Basic modules is included in the system which simplify the workflows of the
clinics. Most of the paper works are able to replace by this computerized system. Simple
interface with the left navigation which increase the ease of use of this software. User
may able to find what they want using the left navigation easily.

Weaknesses

All the modules I intend to solve is included in this system. However, their
display way is not that user-friendly. For example, the appointment module with a list of
different colors in each row is quite unprofessional. Besides, a lot of fields need to be fill

8|Page
Chapter 2 Literature Review

in the registration form and it might take some times for the nurses to key in based on the
details on IC (MyKad).

Figure 2-1 Appointment System in SoftClinic

9|Page
Chapter 2 Literature Review

Figure 2-2 Patient Registration Form in SoftClinic

Solve the weaknesses

Design is another way that we need to take note because too colorful design may
bring unprofessional look. Moreover, to save the time of the task that filling the basic
details of patient, IC reader (MyKad reader) need to be use and we can direct get their
information from the chip without manually type in.

2.2 Second Benchmarked System – ClinicPlus

ClinicPlus by TRM NETT SYSTEMS (M) SDN. BHD is a complete clinic


management software in the market. This user friendly yet comprehensive software
solution will save tremendous amount of work load for the clinics. With this tool, clinics
can drastically reduce the administration and management hassle and dedicate their time
to providing quality healthcare services. (TRM NETT SYSTEMS (M) SDN. BHD., n.d.)
10 | P a g e
Chapter 2 Literature Review

Strengths

With the basic features in the software, it simplifies the workflow processes of a
nurse and doctor in a clinic. Moreover, all the data in the clinic no matter record,
inventory and bill are recorded and stored in database and able to retrieve anytime
efficiently.

Weaknesses

From the three modules I choose to improve, there is only 2 modules that
available in this system which is the patient registration and queue list. Appointment
modules is not available in the system, so the nurse need to take down the appointment
details using paperwork.

Figure 2-3 Queue List in ClinicPlus

11 | P a g e
Chapter 2 Literature Review

The queue list module is not sufficient enough to improve the workflow of the
process. From the screenshot in Figure 4, nurse still needs to add the patient manually to
the queue list. Only the time in is stated, but there is no any time out in the system, and
we can’t know which queue is considered visitation or appointment.

Figure 2-4 SMS Notification in ClinicPlus

In Figure 5, it is the screenshot of SMS notification in the ClinicPlus system.


Although there is no any appointment module in this system, the SMS notification
function still available in the system to let doctor or nurse use to inform patient about
what they want to deliver. However, this module needs manually add the phone number
and name of the patient and also type the message.

12 | P a g e
Chapter 2 Literature Review

Solve the weaknesses

To solve the weaknesses which stated above in ClinicPlus system, appointment


module is needed to add in the system. Besides, both of the queue list module and SMS
notification need to be improved, such as queue list module should able to track down the
time that a patient waits how long in the clinic and SMS notification should have
predefined template when sending appointment notification to the patients.

2.3 Third Benchmarked System – Vanda Clinical Management Systems

Magicsoft Asia Systems Sdn Bhd is a company that founded in Singapore. The
company has branch offices which are located in Indonesia and Malaysia. The company
developed a system which called Vanda Clinical Management Systems and it is used by
doctors, nurses, pharmacist, dispensers or whoever holds an operational or managerial
pose in the clinic, pharmacy, office and etc. It provides solutions which significantly
increase the clinical efficiency, allowing doctors/nurses to spend more time with patients
and less time with paperwork. (Magicsoft Asia Systems, n.d.)

Strengths

Vanda Clinical Management Systems comprises the basic features of the modules
that a clinic needs. All the modules I intend to improve are inside the system. Their SMS
feature already comes with templates and is able to auto notify the patients that make
appointment with the clinic. Moreover, appointment system can be view in day or months
which produce a clearer understanding for the nurse and doctor.

13 | P a g e
Chapter 2 Literature Review

Weaknesses

Some of the weaknesses in the queue list module can be found. Although the
module includes time in, time out and the status of patient, it is still lack the time tracking
system that state how long the patient waits in the clinic.

Figure 2-5 Queue List Module in Vanda Clinical Management System

Solve the weaknesses

To improve the queue list module, total waiting time is needed to add in to state
how long a patient waits. Besides, we need to make a highlight to the nurse if a patient is
waiting too long such as 1 hour outside the room. It is important because the nurse don’t
know how long the patient need to wait after 1 hour. Sometimes the patients that make
appointment may join the queue earlier. So it is better for nurse to ask the patients come
back in the next few hours or at least inform them that they need to wait longer time.

14 | P a g e
Chapter 2 Literature Review

2.4 Studies on SMS Implementation

Some of the patients might forget the appointment because of too busy in daily
life. Therefore, to solve this problem, it is a need to implement the Short Message Service
(SMS) in the appointment module to notify patient before each of the appointment time.
The reason of using SMS is because SMS can easily reach people when the person has a
mobile device with him. SMS doesn’t require any of the mobile application or mobile
data network. It is convenient to all of the mobile devices.

In order to implement the SMS feature in the appointment system, SMS provider
is needed. There are a few SMS provider companies that located in Malaysia. I had
chosen one of the company which is One Way SMS that located in Kuala Lumpur. It is a
company that established since 2009 and with years of experience, they have a good
technical support. (One Way SMS, n.d.)

15 | P a g e
Chapter 2 Literature Review

Based on the official website, there are three methods to send SMS to user, which
include using their web system, email to SMS and Application Programming Interface
(API).

Method Advantage Disadvantage

Web system User friendly, functions that Time consuming as users need to go into
provided in One Way SMS can their web system and send the message.
easily use by users inside the
web system panel.

Email Suitable for business people as it -


transform the text inside an
email to SMS and send to
people.

API Used to integrate with own Hard to implement especially for normal
developed system with available user.
API that provide by One Way
SMS.

Table 2-1 Table of Method that provided by One Way SMS

From the above table, API will be selected as our method as it gives us flexibility
to inform the patients. Besides, it fulfills the scenario which we need to integrate with the
clinic management system in this project. The documentation of API in One Way SMS
will be studied and lastly, the problem will be solved once it can send SMS notification to
the patients using the system in this project.

2.5 Studies on MyKad Reader

To avoid typo occurred and the process time during patient registration, MyKad
reader is being selected as a tool to help improve the business process. MyKad is an

16 | P a g e
Chapter 2 Literature Review

identity card for Malaysia citizen aged 12 and above. The basic details inside the MyKad
include name, address, date of birth and IC number. As the system is developed and used
in Malaysia, therefore MyKad reader is choose to improve the processing time during
patient registration. However, the limitation of MyKad reader is that citizens below 12
and foreigner can’t use it as they don’t have MyKad.

The National Registration Department (NRD) mentioned that the MyKad Reader
is selling around RM 52 to RM 2800 depends on the functionalities. (Lee Yen Mun, 2013)
After research on the internet, there are several suppliers in the market. One of the
suppliers which named MyKad Solution claimed that they are selling the MyKad reader
device with the Software Development Kit (SDK) together at RM 200. Besides, the SDK
that provided for web-based platform only ActiveX, which mean user need to use Internet
Explorer (IE) to use the MyKad reader. (MyKadPro Solutions, n.d.)

Although the drawback of the SDK is limit to IE, but it is still very important to
implement in this project as it improve the process time. Compared to human typing
speed, MyKad reader can get the details in few seconds without any typo.

2.6 Studies on iTextSharp Library

In order to print the diagnosis report and MC on paper, a study is conducted and
found that a PDF file can be print out on web browser directly. Therefore, iTextSharp
Library is selected as one of our tool that going to use in the printing feature. iTextSharp
is a PDF library that allows people to create, adapt, inspect and maintain documents in
the Portable Document Format (PDF). With the functions that provided in the library, it
can generate any kind of documents or reports in PDF file format. It can dynamically
generate the PDF file that interact with the data in database as well. (iTextSharp, n.d.)

17 | P a g e
Chapter 2 Literature Review

Figure 2-6 Sample Screenshot of Print Function inside PDF File

In this project, the system can print out two type of documents which is the
diagnosis report and MC. Both of the functions should implement with iTextSharp
Library in order to generate the PDF file and print out. At the end of this project, the
system can print the documents with correct data and this may decrease the time
consuming for doctor in paperwork.

18 | P a g e
Chapter 3 System Design

3.0 System Design

3.1 Chosen Methodology

There are a lot of software methodologies in the world and each methodology has
their own advantage and disadvantage. Figure 8 shows the software methodologies
available nowadays and it compares all the six methodologies to find out which
methodology is the best for each aspect given.

Figure 3-1 Available Software Methodology

Nowadays, the most suitable system development methodology is rapid


application design (RAD). RAD is chosen by most of the people because of fast
implementation. It can delivers a high quality and faster way results of build up a system
compared with other methodologies. Based on Figure 8, there are two methods which are
phased development methodology and throwaway prototyping methodology that given a
good or excellent in each of the aspects. Two of these methodologies is actually in the
RAD category. For this project, I would like to choose the phased development
methodology as my development methodology to develop my own system. It is because

19 | P a g e
Chapter 3 System Design

the phased development methodology is one of the RAD and it fulfill the requirement of
short time schedule.

Figure 3-2 Phased Development Methodology

Figure 9 shows that a phased development methodology way. Basically there are
4 general phases involving in System Development Life Cycle (SDLC) which are
planning, analysis, design and implementation. In phased development-based
methodology, it breaks an overall system into a series of versions, which are developed
sequentially. It takes short time on the planning phase which identifies the project plan,
state the objectives and scope and develop the work plan. After that, the analysis phase
identifies the overall system concept and then categorize the requirements into series of
versions. The most important and fundamental requirements are bundled into the first
version of the system, followed by design and implementation and a system version 1
will be implemented. This system version can let the users test and get their feedback.
Additional analysis is required after version 1 and combined with new requirements and

20 | P a g e
Chapter 3 System Design

issues that given by the users. Version 2 will be designed and implemented based on
version 1 and this process will be continue until the system is complete or no longer use.
(Dennis, Wixom and Tegarden, 2010, p.11)

The advantage of phased development-based methodology is users can get the


useful system in the hand very soon although it is not a complete developed system. After
that, users can generate some new ideas based on the system version and improve in the
next version till the end of the project.

Based on the project I wish to develop, first I will focus on the patient registration
module and queue list module as the first system version. Patient registration and queue
list is the very fundamental module as it is required and related to other modules that I
wish to develop. After that, appointment module will be implemented into the second
system version. Lastly, generate MC and report module will be implemented into the
third system version. After this, a system that I wish to develop will fully implemented
and presented. During the way of developing, I will seek advice from my supervisor as
well as my friends in order to generate new ideas and get some feedbacks from them to
improve in every next system version. By doing this, the mistakes and failures that I
made will be reduced.

21 | P a g e
Chapter 3 System Design

3.2 System Design and Analysis

3.2.1 Use Case Diagram

Figure 3-3 Clinic Management System Use Case Diagram

22 | P a g e
Chapter 3 System Design

3.2.2 Activity Diagram

Figure 3-4 Activity Diagram for Make Visitation

23 | P a g e
Chapter 3 System Design

Figure 3-5 Activity Diagram for Register Patient

24 | P a g e
Chapter 3 System Design

Figure 3-6 Activity Diagram for Queue Patient

25 | P a g e
Chapter 3 System Design

Figure 3-7 Activity Diagram for Make Appointment

26 | P a g e
Chapter 3 System Design

Figure 3-8 Activity Diagram for Notify Patient

27 | P a g e
Chapter 3 System Design

Figure 3-9 Activity Diagram for Type Visitation Report

28 | P a g e
Chapter 3 System Design

Figure 3-10 Activity Diagram for Print Report

Figure 3-11 Activity Diagram for Generate MC

29 | P a g e
Chapter 3 System Design

3.2.3 Sequence Diagram

Figure 3-12 Sequence Diagram for Make Visitation

30 | P a g e
Chapter 3 System Design

Figure 3-13 Sequence Diagram for Make Appointment

Figure 3-14 Sequence Diagram for Notify Patient

31 | P a g e
Chapter 3 System Design

Figure 3-15 Sequence Diagram for Type Visitation Report

32 | P a g e
Chapter 3 System Design

3.2.4 Entity Relationship Diagram (ERD)

Figure 3-16 Clinic Management System Entity Relationship Diagram


33 | P a g e
Chapter 3 System Design

3.3 Timeline

In this project, gantt chart will be used for illustrating the project timeline. Gantt
chart is a visual tool that illustrate the project flow measured against time and give people
the overview of the schedules for the whole project at a glance. (Tantry, n.d.)

Figure 3-17 Gannt Chart for Final Year Project 1

34 | P a g e
Chapter 3 System Design

Figure 3-18 Gannt Chart for Final Year Project 2 (Current Semester)

35 | P a g e
Chapter 4 Interface Design and Requirements

4.0 Interface Design and Requirements

4.1 Graphical User Interface Design

In this system, since it is an internal system, therefore it is being design in a very


simple layout. The system is using blue and white color in the design since it gives
clearer layout to the people as nurse and doctor need to face the screen for the whole long
working hour.

Figure 4-1 Logo Design

Figure 4-2 Layout Design

36 | P a g e
Chapter 4 Interface Design and Requirements

Figure 4-3 Overview of System Layout

4.2 Functional Requirement

There are few of the functional requirements in the system. First, the system
should able to store and record the details of the patient accurately. To achieve this,
system will let the nurse to insert the MyKad into the MyKad Reader and read the data
from the chips. It will decrease the typo from the nurse.

Second, system should perform a systematic scheduling in the queue list. First
come first serve is being used in the system to make sure it is fair to all the patients.

Third, system should able to make notification to the patient when appointment is
coming on date. SMS notification is the primary way to notify the patient since most of
the people are having mobile phone.

Last, system should able to generate PDF file for the visitation report and also
MC. This may bring convenience to the nurse as well as doctor in the documentation
process.

37 | P a g e
Chapter 4 Interface Design and Requirements

4.3 Non-Functional Requirement

Since the system is used in a clinic, it is a must to ensure that everything is doing
well especially performance during the working hours. Few non-functional requirements
are found and listed below:

 Usability

The system must fulfill its’ own objectives. All the modules and functions
of the system should be usable. It is important to ensure that every function is
meaningful to the system.

 Responsiveness

The system must responds every requests from the user in very few
seconds in order to decrease the waiting time of the patient as well as doctor and
nurse. Responsiveness is one of main concern during the system implementation.

 Reliability

The system should be reliable all the time. The functions in the system
should produce the correct output to the user.

4.4 Hardware Specification

This system is developed under ASP .Net, it will be hosted locally and need an
internet connection in order to send SMS notification to patients, therefore the minimum
hardware requirement are:

Operating System: Windows XP, Windows 7 or above

Processor: Intel Core 2 Duo Processor

RAM: 2GB or above

Disk Space: 100GB or above

Internet Connection: At least 1Mbps

38 | P a g e
Chapter 5 Implementation and Testing

5.0 Implementation and Testing

5.1 Tools/Technology Involved

To develop this clinic management system, Microsoft Visual Studio is required as


it will be the main tools to coding. C# is the main programming language and it will be
used to write applications in the ASP .NET framework. Besides, MSSQL is selected as
the database storage.

In order to get the details from the MyKad, MyKad reader will be used for the
system development as well. Moreover, a server is needed as it will be used as local host
to run the system during the working hours in the clinic. Internet connection is a must in
order to communicate with SMS provider through online to send notification to patients.

5.2 Implementation Issues and Challenges

Clinic management system is a system that will developed under ASP .Net
framework as a web-based platform. The first implementation issue will be the
programming language, which need to use some time to research and digest on C#. In
order to make sure the system works well, a lot of testing is needed. The second
implementation issues will be MyKad reader. As it is a device that need to purchase,
communicate with the suppliers is a must in order to get student discount price.

The implementation challenges in this project include implementation of SMS in


appointment module and MyKad reader SDK because both of these functions need code
study in order to integrate to the own developed system. Another challenge will be
combining all the modules together as it may arise some bugs or problems which need
time to fix them.

39 | P a g e
Chapter 5 Implementation and Testing

5.3 User Manual

5.3.1 Login Module

Figure 5-1 Login Interface

Before using the functionality of the system, nurse or doctor needs to login with
their own account. There are two types of account, which are nurse and doctor. Both of
the accounts have different functionalities to use. The account can be requested through
the system administrator.

5.3.2 Dashboard Module

Figure 5-2 Dashboard Interface

After nurse or doctor login into the system, the first page will be the dashboard
module. The dashboard will display today’s queue list in the clinic. It is using the first
come first serve to schedule. The appointment will show on top of the list then goes with
normal visitation. With this, patient may know when is his or her turn correctly.

40 | P a g e
Chapter 5 Implementation and Testing

5.3.3 Patient Registration Module

Figure 5-3 Patient Registration Interface

The patient registration page can store the basic details of the patients such as
name, IC number, address, gender and contact number. All the information except the
contact number can get from the chips of MyKad using MyKad Reader. The nurse just
need to press the “Read MyKad” button after insert patient’s MyKad into the reader. It
will took around five to ten seconds to auto fill in the form. MyKad Reader also can read
the image of the person and store inside the system. By using MyKad Reader, the typo
and process speed during registration may decrease much compared with manually
typing.

41 | P a g e
Chapter 5 Implementation and Testing

5.3.4 Patient Edit Module

Figure 5-4 Patient Edit Interface

Nurse or doctor can edit the profile of patients to update the latest details. The
most probably information that will update is address and contact number.

5.3.5 Search Patient Function

Figure 5-5 Search Patient Interface

Nurse or doctor can search the patient by typing their name or IC number in the
text box. This search function can be used when want to edit patient, queue patient, make
appointment, list visitation report, notify patient and generate MC.

42 | P a g e
Chapter 5 Implementation and Testing

5.3.6 Queue Patient Module

Figure 5-6 Queue Patient Interface

Nurse can queue the patients when they register themselves at the counter. After
registration, the patients will insert in the queue list using first come first serve.
Alternatively, nurse can queue the patients directly without register them if they are
second time visit to the clinic.

5.3.7 Create Appointment Module

Figure 5-7 Create Appointment Interface

Nurse can create the appointment for patient that book an appointment with the
doctor. SMS notification may send out on the appointment day automatically. The SMS
template is already predefined in the system.

43 | P a g e
Chapter 5 Implementation and Testing

5.3.8 List Appointment Module

Figure 5-8 List Appointment Interface

Appointments that insert into the system will be list down in a table. This table
will show in a very clear manner on which date who already made appointments. When
the patient comes, nurse can queues the patient and it will directly on the top of the queue
list.

5.3.9 Custom SMS Module

Figure 5-9 Custom SMS Interface

Custom SMS can be send to the patients when schedule on the specific date. The
message don’t have any templates and it is being manually typed by the nurse or doctor.

44 | P a g e
Chapter 5 Implementation and Testing

5.3.10 SMS List Module

Figure 5-10 SMS List Interface

This module will display simple report for the SMS delivery status. It will also
show the credit of SMS that available in the account at the SMS provider. Once credit is
not enough, SMS will not able to send out to the patients.

5.3.11 Create Visitation Report Module

Figure 5-11 Create Visitation Report Interface

45 | P a g e
Chapter 5 Implementation and Testing

After doctor check in the patients, then the system will goes to the create
visitation report section. Doctor can type the diagnosis report there as much as they want.

5.3.12 List Visitation Report Module

Figure 5-12 List Visitation Report Interface

This module can list out every daily visitation report in the clinic. It gives the
nurse and doctor to search who is coming on specific date and what is their report datails
on that day. Report can be edit and print out individually.

5.3.13 Search Visitation Report Module

Figure 5-13 Search Visitation Report Interface


46 | P a g e
Chapter 5 Implementation and Testing

The visitation report can be searched by using patient’s name or IC No. It will list
out the specific patients and all the visitaion reports the doctor created.

5.3.14 Generate MC Module

Figure 5-14 Generate MC Interface

MC can be generate by the doctor by filling in the date, duration for how many
days and reason. The system will automatically generate a .PDF file which is in A4 size
and able to print out. Doctor just need to chop and sign with his signature in order to
prove it is the original MC.

Figure 5-15 Sample of MC .PDF File


47 | P a g e
Chapter 5 Implementation and Testing

5.3.15 List MC Module

Figure 5-16 List MC Interface

This module will display the MC that has been created on the specific date in a
table form. MC can be view and print again anytime.

5.3.16 Clinic Information Module

Figure 5-17 Clinic Information Interface

Doctor can update their clinic information. The information is used when generate
the MC and visitation report in the PDF file.

48 | P a g e
Chapter 5 Implementation and Testing

5.3.17 Staff Management Module

Figure 5-18 Staff Management Interface

The table lists out all the staff in the clinic that holding a login account. Morever,
it allowed doctor to add new staff or edit staff’s details.

5.3.18 Add Staff Module

Figure 5-19 Add Staff Interface

Doctor can create an account for the staff to login in this module. The system
stores the basic details of the staff. MyKad Reader also being used in this module so it
can decrease the typo.

49 | P a g e
Chapter 5 Implementation and Testing

5.3.19 Edit Staff Module

Figure 5-20 Edit Staff Interface

Doctor can edit the staff details such as address and contact number when there is
any updates.

50 | P a g e
Chapter 5 Implementation and Testing

5.4 System Testing

5.4.1 Login Module Testing

Objectives: To ensure only authenticated staff can login the system.

No. Testing Method Action Done Expected Result Result

1 Login with correct Login the user User successfully Pass


account username account with correct login into the system.
and password. username and
password.

2 Login with Login with User is restricted to Pass


incorrect username randomized username login and error
or password. and password, such message will prompt
as ABC as username, out.
123 as password.

3 Leave blank for Do not key in User is restricted to Pass


both of the anything in the login login and asked to key
username and textbox. in username and
password. password.

Table 5-1 Login Module Testing

5.4.2 Dashboard Module Testing

Objective: To ensure specific patient can check in and the queue list is correct all the time.

No. Testing Method Action Done Expected Result Result

1 Check in the Press the check in Patient successfully Pass


specific patient. button for the specific remove from the
patient. queue after check in.

Table 5-2 Dashboard Module Testing


51 | P a g e
Chapter 5 Implementation and Testing

5.4.3 Patient Registration Module Testing

Objective: To ensure patient’s details is stored inside the database of system.

No. Testing Method Action Done Expected Result Result

1 Use MyKad Reader Insert the MyKad of Able to get the basic Pass
to get personal patient into MyKad details of patients and
details of patient. Reader and press the fill into relative text
“Read MyKad” boxes.
button.

2 Use MyKad Reader Directly press the Error will prompt out Pass
without connect the “Read MyKad” and asked to check
device. button. and connect the device
properly.

3 Recreate the Fill in the details of Error will displays and Pass
patient’s details patients and press shows duplicate IC
which has visit to “Create Patient” No. found, which
the clinic before. button. mean the patient’s
detail is already inside
the system.

4 Manually type in Type the patient’s User can key in Pass


the patient’s details. details for those who anything in the text
don’t have MyKad. box without any
problem.

5 Insert the data of Press the “Create Patient’s details Pass


patient into the Patient” button after successfully insert into
system. all the details are the database.
filled.

Table 5-3 Patient Registration Module Testing

52 | P a g e
Chapter 5 Implementation and Testing

5.4.4 Patient Edit Module Testing

Objective: To ensure patient’s details can be edit and save into database.

No. Testing Method Action Done Expected Result Result

1 Use MyKad Reader Insert the MyKad of Able to get the basic Pass
to get latest patient into MyKad details of patients and
personal details of Reader and press the fill into relative text
patient. “Read MyKad” boxes.
button.

2 Manually edit the Type the patient’s User can key in Pass
specific details of details at specific text anything in the text
patient. box. box without any
problem.

3 Save the data of Press the “Update Patient’s latest details Pass
patient into the Patient” button after successfully save into
system. all the details are the database.
updated.

Table 5-4 Patient Edit Module Testing

5.4.5 Search Patient Function Testing

Objective: To ensure can get the correct patient’s detail when searching.

No. Testing Method Action Done Expected Result Result

1 Search using Type patient’s IC No. Able to found specific Pass


correct IC No. in the text box and patient.
press “Retrieve”
button.

53 | P a g e
Chapter 5 Implementation and Testing

2 Search using Type patient’s name Able to found specific Pass


correct name. in the text box and patient’s details. If
press “Retrieve” duplicate names are
button. found, it will show the
IC No. to let the user
choose which they
want to select.

3 Search with blank No type anything in Error will display and Pass
input. the text box. ask to type in IC No.
or name into text box.

4 Search with Type dummy value Error will display and Pass
dummy value. such as ABC as show no patient found
name. in the system.

Table 5-5 Search Patient Function Testing

5.4.6 Queue Patient Module Testing

Objective: To ensure patient successfully queue into queue list.

No. Testing Method Action Done Expected Result Result

1 Search patient Type patient’s IC No. Display a message Pass


using correct IC or name in the text saying that
No. or name. box and press successfully insert into
“Retrieve” button. queue list. Queue list
in the dashboard will
have the patient’s
details.

Table 5-6 Queue Patient Module Testing

54 | P a g e
Chapter 5 Implementation and Testing

5.4.7 Create Appointment Module Testing

Objective: To ensure appointment of a patient successfully insert into system and SMS
notification will send on time.

No. Testing Method Action Done Expected Result Result

1 Search patient Type patient’s IC No. Display a message Pass


using correct IC or name in the text saying that specific
No. or name. box and press patient successfully
“Retrieve” button. insert into
appointment list. SMS
notification will be
scheduled to send on
the appointment date.

Table 5-7 Create Appointment Module Testing

5.4.8 List Appointment Module Testing

Objectives: To list out all the appointments by date to the nurse or doctor.

No. Testing Method Action Done Expected Result Result

1 Go to List Press the List All the appointments Pass


Appointment Appointment in the of the patients will list
Module. navigation menu. out based on date.
Queue appointment
link can be press in
order to queue the
patients into the queue
list when patient reach
the clinic.

Table 5-8 List Appointment Module Testing

55 | P a g e
Chapter 5 Implementation and Testing

5.4.9 Custom SMS Module Testing

Objectives: Make custom SMS notification to the patients for any urgent matter.

No. Testing Method Action Done Expected Result Result

1 Search patient Type patient’s IC No. Show a form that Pass


using correct IC or name in the text display patient’s
No. or name. box and press name, IC No. and
“Retrieve” button. mobile number and
ask user to fill in the
send date and message
details.

2 Leave blank for Do not key in Error display and ask Pass
both of the date and anything in the date user to key in details
SMS details. and SMS details text in two of the text
box. boxes.

3 Insert with valid Key in the specific SMS will successfully Pass
date and SMS date that SMS want schedule in the system
details. to send out and the and send on time.
SMS details.

Table 5-9 Custom SMS Module Testing

56 | P a g e
Chapter 5 Implementation and Testing

5.4.10 SMS List Module Testing

Objectives: Show the report of SMS notification to the user.

No. Testing Method Action Done Expected Result Result

1 Search specific date Select the date using A list of SMS Pass
of SMS report. calendar and press notification that has
“Search Report” been scheduled will
button. list out with the status.
If it is failed, it will be
record and can be one
of the reference for
system administrator
to check.

2 No input any date Do not select date, Error will display and Pass
of SMS report. directly press the ask to insert a specific
“Search Report” date.
button.

Table 5-10 SMS List Module Testing

5.4.11 Create Visitation Report Module Testing

Objective: To ensure every visitation report is saved into the system.

No. Testing Method Action Done Expected Result Result

1 Insert with correct Doctor types in the Visitation report is Pass


visitation details. visitation details in saved into database
text boxes that is and can be tracked
provided and press back.
“Create Visitation
Report” button.

Table 5-11 Create Visitation Report Module Testing

57 | P a g e
Chapter 5 Implementation and Testing

5.4.12 List Visitation Report Module Testing

Objective: To list out all the visitation reports by date.

No. Testing Method Action Done Expected Result Result

1 Search specific date Select the date using A list of visitation Pass
of visitation report. calendar and press report on the specific
“Search Report” date will show out.
button. Nurse or doctor can
view, print and edit
the report when there
is a need.

2 No input any date Do not select date, Error will display and Pass
of visitation report. directly press the ask to insert a specific
“Search Report” date.
button.

Table 5-12 List Visitation Report Module Testing

5.4.13 Search Visitation Report Module Testing

Objective: To list out all the visitation report by patient.

No. Testing Method Action Done Expected Result Result

1 Search patient Type patient’s IC No. The system will list Pass
using correct IC or name in the text out all the visitation
No. or name. box and press reports with view,
“Retrieve” button. print and edit
functions for the
specific patient.

Table 5-13 Search Visitation Report Module Testing

58 | P a g e
Chapter 5 Implementation and Testing

5.4.14 Generate MC Module Testing

Objective: To generate MC for patient for a specific time period.

No. Testing Method Action Done Expected Result Result

1 Search patient Type patient’s IC No. The system will list Pass
using correct IC or name in the text out the name and IC
No. or name. box and press No. of the patient and
“Retrieve” button. also the form that used
to fill in data.

2 Input blank data for Don’t type in System will display Pass
the date and reason. anything in the date error and ask user to
and reason text box. type something in the
text box.

3 Input correct data Select the date of System will save the Pass
for the date and MC, type in the record of MC and pop
reason. reason, and press up one PDF file that
“Generate MC” used to print out.
button.

Table 5-14 Generate MC Module Testing

59 | P a g e
Chapter 5 Implementation and Testing

5.4.15 List MC Module Testing

Objective: To list out all the MC by date.

No. Testing Method Action Done Expected Result Result

1 Search specific date Select the date using A list of MC on the Pass
of MC. calendar and press specific date will show
“Search MC” button. out. Nurse or doctor
can view and print the
MC when there is a
need.

2 No input any date Do not select date, Error will display and Pass
of MC. directly press the ask to insert a specific
“Search MC” button. date.

Table 5-15 List MC Module Testing

5.4.16 Clinic Information Module Testing

Objective: To ensure the clinic information can be update.

No. Testing Method Action Done Expected Result Result

1 Go to Clinic Press the Clinic The basic details about Pass


Information Information Module the clinic will
Module. in the navigation automatically fill in
menu. the text box.

60 | P a g e
Chapter 5 Implementation and Testing

2 Update Clinic Update any relevant The latest clinic Pass


Information. information which information will save
need update by into the database of
changing the text in the system.
the text box and press
“Update” button.

Table 5-16 Clinic Information Module Testing

5.4.17 Staff Management Module Testing

Objective: To list out all the staff in the clinic.

No. Testing Method Action Done Expected Result Result

1 Go to Staff Press the Staff The basic details about Pass


Management Management Module the clinic will
Module. in the navigation automatically fill in
menu. the text box.

Table 5-17 Staff Management Module Testing

61 | P a g e
Chapter 5 Implementation and Testing

5.4.18 Add Staff Module Testing

Objective: To ensure the doctor can add the staff into the system.

No. Testing Method Action Done Expected Result Result

1 Use MyKad Reader Insert the MyKad of Able to get the basic Pass
to get personal staff into MyKad details of staff and fill
details of staff. Reader and press the into relative text
“Read MyKad” boxes.
button.

2 Use MyKad Reader Directly press the Error will prompt out Pass
without connect the “Read MyKad” and asked to check
device. button. and connect the device
properly.

3 Insert the data of Press the “Register” Staff’s details Pass


staff into the button after all the successfully insert into
system. details are filled in. the database.

Table 5-18 Add Staff Module Testing

5.4.19 Edit Staff Module Testing

Objective: To ensure staff’s details can be edit and save into database.

No. Testing Method Action Done Expected Result Result

1 Use MyKad Reader Insert the MyKad of Able to get the basic Pass
to get latest staff into MyKad details of staff and fill
personal details of Reader and press the into relative text
staff. “Read MyKad” boxes.
button.

62 | P a g e
Chapter 5 Implementation and Testing

2 Manually edit the Type the staff’s User can key in Pass
specific details of details at specific text anything in the text
staff. box. box without any
problem.

3 Save the data of Press the “Update” Staff’s latest details Pass
staff into the button after all the successfully save into
system. details are updated. the database.

Table 5-19 Edit Staff Module Testing

63 | P a g e
Chapter 6 System Limitations and Future Enhancement

6.0 System Limitations and Future Enhancement

6.1 Limitations and Considerations

The limitations of the current system is that it is only workable in Internet


Explorer for the MyKad Reader since it needs ActiveX to connect to the device. User
cannot use those browsers which they feel convenient such as Google Chrome and
Firefox. However, since our system is installed under Windows operating system,
Internet Explorer already preinstalled in the system, which also gives convenience to the
user.

Another limitations is the SMS notification needs the internet connection since
the system is using services that provided by SMS provider. If there is problem for the
internet connection, such as can’t connect to the internet service provider, then the system
may fail to send the SMS to the patients.

Another considerations is that the system needs large disk space in the future if it
is running few years as system is keeping the photo of each people from the MyKad,
therefore it may take up little amount of the disk space.

6.2 Possible Future Improvement

The system may have better improvement in the future since the current system is
being sketched down to few modules. It can be added with more modules such as
inventory, billing, data analysis and so on in the future which may help the doctor and
nurse to do more tasks with lesser time.

Moreover, the MyKad Reader that required ActiveX can be replaced with Java
Applet so that every browser can use it, but by doing this it needs to get support from the
MyKad supplier.
64 | P a g e
Chapter 6 System Limitations and Future Enhancement

Lastly, the system may also improve by implement mobile applications so that
user can actually make appointment or checking the queue list by using their smart phone.
It makes another convenience to the patients since they can direct interact with the system.

65 | P a g e
Chapter 7 Conclusion

7.0 Conclusion

In a nutshell, clinic management system is an internal web-based platform system.


It simplifies the works for nurse and doctor, as well as improve the business process
between patient, nurse and doctor. This project aims to solve the problems in the clinic
especially in Malaysia. By using this system, the staffs in the clinic should be able to do
their works more efficiently and time saving. The waiting time for patients will be
decrease as well as most of the business process is done using computer rather than
handwriting. Besides, with the implementation of SMS feature, patients will not miss any
of the appointment. Moreover, there is a function to generate MC to the patient. Doctor
just need to sign the MC rather than writing the details of the patient. Although there are
similar systems in the market, but those good functions are not implement together. At
the end of project, good and new features that implement into the system will solve part
of the problems of healthcare field.

66 | P a g e
Chapter 8 References

8.0 References
1. Acharya, Kamal, Attendance Management System Project (April 28, 2024).
Available at
SSRN: https://ssrn.com/abstract=4810251 or http://dx.doi.org/10.2139/ssrn.4810251
2. Acharya, Kamal, Online Food Order System (May 2, 2024). Available at
SSRN: https://ssrn.com/abstract=4814732 or http://dx.doi.org/10.2139/ssrn.4814732
3. Acharya, Kamal, University management system project. (May 1, 2024). Available at
SSRN: https://ssrn.com/abstract=4814103 or http://dx.doi.org/10.2139/ssrn.4814103
4. Acharya, Kamal, Online banking management system. (May 1, 2024). Available at
SSRN: https://ssrn.com/abstract=4813597 or http://dx.doi.org/10.2139/ssrn.4813597
5. Acharya, Kamal, Online Job Portal Management System (May 5, 2024). Available at
SSRN: https://ssrn.com/abstract=4817534 or http://dx.doi.org/10.2139/ssrn.4817534
6. Acharya, Kamal, Employee leave management system. (May 7, 2024). Available
at SSRN: https://ssrn.com/abstract=4819626 or http://dx.doi.org/10.2139/ssrn.4819626
7. Acharya, Kamal, Online electricity billing project report. (May 7, 2024). Available at
SSRN: https://ssrn.com/abstract=4819630 or http://dx.doi.org/10.2139/ssrn.4819630
8. Acharya, Kamal, POLICY MANAGEMENT SYSTEM PROJECT REPORT. (December 10,
2023). Available at
SSRN: https://ssrn.com/abstract=4831694 or http://dx.doi.org/10.2139/ssrn.4831694
9. Acharya, Kamal, Online job placement system project report. (January 10, 2023). Available
at
SSRN: https://ssrn.com/abstract=4831638 or http://dx.doi.org/10.2139/ssrn.4831638
10. Acharya, Kamal, Software testing for project report. (May 16, 2023). Available at
SSRN: https://ssrn.com/abstract=4831028 or http://dx.doi.org/10.2139/ssrn.4831028
11. Acharya, Kamal, ONLINE CRIME REPORTING SYSTEM PROJECT. (August 10, 2022).
Available at
SSRN: https://ssrn.com/abstract=4831015 or http://dx.doi.org/10.2139/ssrn.4831015
12. Acharya, Kamal, Burger ordering system project report. (October 10, 2022). Available at
SSRN: https://ssrn.com/abstract=4832704 or http://dx.doi.org/10.2139/ssrn.4832704
13. Acharya, Kamal, Teachers Record Management System Project Report (December 10,
2023). Available at
SSRN: https://ssrn.com/abstract=4833821 or http://dx.doi.org/10.2139/ssrn.4833821
14. Acharya, Kamal, Dairy Management System Project Report (December 20, 2020). Available
at SSRN: https://ssrn.com/abstract=4835231 or http://dx.doi.org/10.2139/ssrn.4835231
15. Acharya, Kamal, Electrical Shop Management System Project (December 10, 2019).
Available at
SSRN: https://ssrn.com/abstract=4835238 or http://dx.doi.org/10.2139/ssrn.4835238

67 | P a g e
Chapter 8 References

16. Acharya, Kamal, Online book store management system project report. (Febuary 10, 2020).
Available at
SSRN: https://ssrn.com/abstract=4835277 or http://dx.doi.org/10.2139/ssrn.4835277
17. Acharya, Kamal, Paint shop management system project report. (January 10, 2019).
Available at
SSRN: https://ssrn.com/abstract=4835441 or http://dx.doi.org/10.2139/ssrn.4835441
18. Acharya, Kamal, Supermarket billing system project report. (August 10, 2021). Available at
SSRN: https://ssrn.com/abstract=4835474 or http://dx.doi.org/10.2139/ssrn.4835474
19. Acharya, Kamal, Online taxi booking system project report. (March 10, 2022). Available at
SSRN: https://ssrn.com/abstract=4837729 or http://dx.doi.org/10.2139/ssrn.4837729
20. Acharya, Kamal, Online car servicing system project report. (March 10, 2023). Available at
SSRN: https://ssrn.com/abstract=4837832 or http://dx.doi.org/10.2139/ssrn.4837832
21. Acharya, Kamal, School management system project report. (July 10, 2021). Available at
SSRN: https://ssrn.com/abstract=4837837 or http://dx.doi.org/10.2139/ssrn.4837837
22. Acharya, Kamal, Furniture Showroom Management System Project Report (March 21,
2021). Available at
SSRN: https://ssrn.com/abstract=4839422 or http://dx.doi.org/10.2139/ssrn.4839422
23. Acharya, Kamal, Online Vehicle Rental System Project Report (March 21, 2019). Available
at SSRN: https://ssrn.com/abstract=4839429 or http://dx.doi.org/10.2139/ssrn.4839429
24. Acharya, Kamal, Fruit Shop Management System Project Report (August 10, 2023).
Available at
SSRN: https://ssrn.com/abstract=4841048 or http://dx.doi.org/10.2139/ssrn.4841048
25. Acharya, Kamal, Hall Booking Management System Project Report (December 21, 2023).
Available at
SSRN: https://ssrn.com/abstract=4841055 or http://dx.doi.org/10.2139/ssrn.4841055
26. Acharya, Kamal, Lundry Management System Project Report (October 21, 2023). Available
at SSRN: https://ssrn.com/abstract=4841059 or http://dx.doi.org/10.2139/ssrn.4841059
27. Acharya, Kamal, A CASE STUDY OF CINEMA MANAGEMENT SYSTEM PROJECT
(September 25, 2023). Available at
SSRN: https://ssrn.com/abstract=4841209 or http://dx.doi.org/10.2139/ssrn.4841209
28. Acharya, Kamal, A CASE STUDY ON ONLINE TICKET BOOKING SYSTEM PROJECT
(May 25, 2024). Available at
SSRN: https://ssrn.com/abstract=4841210 or http://dx.doi.org/10.2139/ssrn.4841210
29. Acharya, Kamal, ONLINE DATING MANAGEMENT SYSTEM PROJECT REPORT. (April
25, 2023). Available at
SSRN: https://ssrn.com/abstract=4842066 or http://dx.doi.org/10.2139/ssrn.4842066
30. Acharya, Kamal, ONLINE RESUME BUILDER MANAGEMENT SYSTEM PROJECT
REPORT. (April 25, 2021). Available at
SSRN: https://ssrn.com/abstract=4842071 or http://dx.doi.org/10.2139/ssrn.4842071
31. Acharya, Kamal, TOLL TEX MANAGEMENT SYSTEM PROJECT REPORT (August 21,
2023). Available at
SSRN: https://ssrn.com/abstract=4842082 or http://dx.doi.org/10.2139/ssrn.4842082
68 | P a g e
Chapter 8 References

32. Acharya, Kamal, Chat Application Through Client Server Management System Project
Report (June 25, 2023). Available at
SSRN: https://ssrn.com/abstract=4842761 or http://dx.doi.org/10.2139/ssrn.4842761
33. Acharya, Kamal, Web Chatting Application Management System Project Report (April 25,
2022). Available at
SSRN: https://ssrn.com/abstract=4842771 or http://dx.doi.org/10.2139/ssrn.4842771
34. Acharya, Kamal, Automobile management system project report (May 25, 2022). Available
at SSRN: https://ssrn.com/abstract=4846917 or http://dx.doi.org/10.2139/ssrn.4846917
35. Acharya, Kamal, College bus management system project report (April 25, 2023). Available
at SSRN: https://ssrn.com/abstract=4846920 or http://dx.doi.org/10.2139/ssrn.4846920
36. Acharya, Kamal, Courier management system project report (May 25, 2023). Available at
SSRN: https://ssrn.com/abstract=4846922 or http://dx.doi.org/10.2139/ssrn.4846922
37. Acharya, Kamal, Event management system project report (April 25, 2021). Available at
SSRN: https://ssrn.com/abstract=4846927 or http://dx.doi.org/10.2139/ssrn.4846927
38. Acharya, Kamal, Library management system project report II (May 25, 2020). Available at
SSRN: https://ssrn.com/abstract=4848857 or http://dx.doi.org/10.2139/ssrn.4848857
39. Kamal Acharya. Teacher record management system project report. Authorea. August 02,
2024.
DOI: https://doi.org/10.22541/au.172261514.46787329/v1
40. Kamal Acharya. POST OFFICE MANAGEMENT SYSTEM PROJECT
REPORT. Authorea. August 02, 2024.
DOI: https://doi.org/10.22541/au.172261514.44494375/v1
41. Kamal Acharya. Fruit shop management system project report. Authorea. August 02, 2024.
DOI: https://doi.org/10.22541/au.172261514.42227675/v1
42. Kamal Acharya. Dairy management system project report. Authorea. August 02, 2024.
DOI: https://doi.org/10.22541/au.172261513.39402347/v1
43. Kamal Acharya. DATA COMMUNICATION AND COMPUTER NETWORK
MANAGEMENT SYSTEM PROJECT REPORT. Authorea. August 01, 2024.
DOI: https://doi.org/10.22541/au.172254873.37480177/v1
44. Kamal Acharya. School management system project report. Authorea. August 01, 2024.
DOI: https://doi.org/10.22541/au.172254873.34023165/v1
45. Kamal Acharya. A CASE STUDY OF CINEMA MANAGEMENT SYSTEM
PROJECT. Authorea. August 01, 2024.
DOI: https://doi.org/10.22541/au.172254873.30191075/v1
46. Kamal Acharya. A CASE STUDY ON ONLINE TICKET BOOKING SYSTEM
PROJECT. Authorea. August 01, 2024
DOI: https://doi.org/10.22541/au.172254872.26972790/v1
47. Kamal Acharya. Web chatting application project report management
system. Authorea. August 01, 2024.
DOI: https://doi.org/10.22541/au.172254871.18588592/v1
48. Kamal Acharya. RETAIL STORE MANAGEMENT SYSTEM PROJECT
REPORT. Authorea. August 01, 2024.
DOI: https://doi.org/10.22541/au.172254871.14590154/v1

69 | P a g e
Chapter 8 References

49. Kamal Acharya. SUPERMARKET MANAGEMENT SYSTEM PROJECT


REPORT. Authorea. August 01, 2024.
DOI: https://doi.org/10.22541/au.172252491.19145062/v1
50. Kamal Acharya. SOCIAL MEDIA MANAGEMENT SYSTEM PROJECT
REPORT. Authorea. August 01, 2024.
DOI: https://doi.org/10.22541/au.172252491.11210579/v1
51. Kamal Acharya. Online music portal management system project report. Authorea. August
01, 2024.
DOI: https://doi.org/10.22541/au.172252488.89734698/v1
52. Kamal Acharya. COLLEGE BUS MANAGEMENT SYSTEM PROJECT
REPORT. Authorea. July 31, 2024.
DOI: https://doi.org/10.22541/au.172245277.70798942/v1
53. Kamal Acharya. AUTOMOBILE MANAGEMENT SYSTEM PROJECT
REPORT. Authorea. July 31, 2024.
DOI: https://doi.org/10.22541/au.172245276.67982593/v1
54. Kamal Acharya. Ludo management system project report. Authorea. July 31, 2024
DOI: https://doi.org/10.22541/au.172243999.98091616/v1
55. Kamal Acharya. Literature online quiz system project report. Authorea. July 31,
2024
DOI: https://doi.org/10.22541/au.172243825.53562953/v1
56. Kamal Acharya. Avoid waste management system project. Authorea. July 29, 2024
DOI: https://doi.org/10.22541/au.172228528.85022205/v1
57. Kamal Acharya. CHAT APPLICATION THROUGH CLIENT SERVER MANAGEMENT
SYSTEM PROJECT. Authorea. July 29, 2024.
DOI: https://doi.org/10.22541/au.172228527.74316529/v1
58. Kamal Acharya. Parking allotment system project report. Authorea. July 29, 2024.
DOI: https://doi.org/10.22541/au.172227078.89966943/v1
59. Kamal Acharya. HEALTH INSURANCE CLAIM MANAGEMENT SYSTEM. Authorea. July
26, 2024.
DOI: https://doi.org/10.22541/au.172202020.06707762/v1
60. Kamal Acharya. ONLINE TRAIN BOOKING SYSTEM PROJECT REPORT. Authorea. July
22, 2024.
DOI: https://doi.org/10.22541/au.172167914.45160406/v1
61. Kamal Acharya. COVID MANAGEMENT SYSTEM PROJECT REPORT. Authorea. July 16,
2024.
DOI: https://doi.org/10.22541/au.172116616.60220024/v1
62. Kamal Acharya. COVID MANAGEMENT SYSTEM PROJECT REPORT. Authorea. July 16,
2024.
DOI:https://doi.org/10.22541/au.172116616.60220024/v1

70 | P a g e
Chapter 8 References

71 | P a g e

View publication stats

You might also like