HOSPITAL MANAGEMENT SYSTEM ANDROID, Project 1

1. Page -1
CHAPTER I
INTRODUCTION
In this document, we will describe two possible projects for taking the exam of the” Android
application Development (Android mobile application)”. One can select a project from this
set, or suggest something else based on personal interests or ideas. What I want to
achieve in that project, to see if it can meet the class requirements. The following project
descriptions should be used as a track for my final work, leading you to some key points
that has to be done, but of course you can (and you are encouraged to do so) expand and
add new features to your application.
Hospitals deal with the life and health of their patients. Good medical care relies on well
trained doctors and nurses and on high quality facilities and equipment. Good medical care
also relies on good record keeping. Without accurate, comprehensive and up to date and
accessible patient notes, medical personnel may not offer the best treatment or may in fact
misdiagnose the condition, which can have serious consequences. Associated records,
such as x-rays, specimens, drug records and patient registers, must also be well cared for
if the patient is to be protected. Good records care also ensures the hospitals
administration runs smoothly; unneeded records are transferred or destroyed regularly,
keeping storage areas clear and accessible; and key records can be found quickly, saving
time and resources. Records also provide evidence of the hospital’s accountability for its
actions and they form a key source of data for medical research, statistical reports and
health information systems. Managing Hospital Records addresses the specific issues
involved in managing clinical and non-clinical hospital records. A comprehensive records
management system in a hospital helps to ensure that staff have access both to clinical
information and to administrative records on a wide range of issues, including policy,
precedents, legal rights and obligations, personnel, finance, buildings, equipment and
resources. Records Management refers to an ongoing process of managing the records
in a media neutral basis in accordance with approved policies, procedures and schedules.
Records Management as a discipline defines and applies business rules related to the
creation, protection, retrieval and disposition of an organization as records over time.
Retention schedules are the cornerstone of a successful Records Management process.
Records Management as a discipline involves records keeping. Record keeping is an
important aspect of every organizations/ institution’s day to day operations. There cannot
be a records management system without records and neither can there be efficient record
keeping without a good records management system. Therefore, record keeping is the
Systematic procedure by which the records of an organization are created, captured,
maintained, and disposed of. This system also ensures their preservation for evidential
purposes, accurate and efficient updating, timely availability, and control of access to them
only by authorized personnel. The record in question here refers to any item or collection
of data.

2. Page -2
1.1 BACKGROUND STUDY
Android is a mobile operating system that is based on a modified version of Linux. It was
originally developed by a startup of the same name, Android, Inc. In 2005, as part of its
strategy to enter the mobile space, Google purchased Android and took over its
development work (as well as its development team). Google wanted Android to be open
and free; hence, most of the Android code was released under the open-source Apache
License, which means that anyone who wants to use Android can do so by downloading
the full Android source code. Moreover, vendors (typically hardware manufacturers) can
add their own proprietary extensions to Android and customize Android to differentiate
their products from others. This simple development model makes Android very attractive
and has thus piqued the interest of many vendors. This has been especially true for
companies affected by the phenomenon of Apple’s iPhone, Samsung a hugely successful
product that revolutionized the smartphone industry. Such companies include Motorola
and Sony Ericsson, which for many years have been developing their own mobile
operating systems. When the iPhone was launched, many of these manufacturers had to
scramble to find new ways of revitalizing their products. These manufacturers see Android
as a solution- they will continue to design their own hardware and use Android as the
operating system that powers it. The main advantage of adopting Android is that it offers
a unified approach to application development. Developers need only develop for Android,
and their applications should be able to run on numerous different devices, as long as the
devices are powered using Android. In the world of smartphones, applications are the most
important part of the success chain. Device manufacturers therefore see Android as their
best hope to challenge the onslaught of the iPhone, which already commands a large base
of applications.
1.2 Problem Statement
The current manual system need to call or fill the form to do appointment with doctor. The
current manual system takes more time to meet with doctor because there is no schedule.
If we do it by online we need less time to manual system. Online appointment scheduling
systems are not only time-saving agents but income-generating assistants too, that
provide operational convenience and promote relations built with patients.
The current health care providers are using different ways and systems for managing
information. Some health care providers are using only one system for managing the
health information but it is not comprehensive for managing all the information, for instance
the system can support only the patient information but cannot support the patient
appointment or cannot support the doctor schedule.
The information is very difficult to retrieve and to find particular information for Example:
To find out about the patient’s history, the user has to go through various registers. This
results in in convenience and wastage of time.

3. Page -3
1.3 Objective
The objectives of Hospital Management System (HMS) are:
I. To provide an online appointment
II. To provide systematic way of storing data
III. To retrieve patient information.
1.4 Scope of Study
I. User Scope
In Hospital Management System (HMS) a user of this system are patient and admin.
II. System Scope
A. Patient
I. Register module
The system should allow patient to register to login the system by inserting personal
information of patient.
II. Login module
The system should allow patient to access their accounts through the insert correct email
and password.
III. View patient info module
The system should allow patient to view details which consists of patient name, patient
email, patient type, address, and contact number.

4. Page -4
III. View appointment module
The system should allow patient to view appointment which consists of doctor name, time
of appointment with doctor.
IV. Make payment module
The system should allow patient to make confirmation payment. Patient have to make
payment either by online or cash. Next, the system should allow patient to click complete
order and invoice will be produced.
B. Admin
I. Login module
The system should allow admin to access their accounts through the insert correct admin
ID and password.
II. Manage patient module
The system should allow admin to check list of patient that consists of patient name, patient
type, and address. The system should allow admin to search, update and delete patient
information.
III. Register patient module
The system should allow admin to register new patient by inserting personal information
of patient.
IV. Generate bills module
The system should allow admin to view summary of bills. Admin can generate bills of
patient.
1.5 Hardware and software requirements
1.5.1 Hardware requirements
To develop this system, hardware requirement is important things to be required. Table
1.1 shows the hardware requirements to develop Hospital Management System (HMSA).

5. Page -5
Table 1.1 Hardware requirements
1.5.2 Software requirements
After hardware requirement, software requirement is the important things to be install.
Table 1.2 shows the software requirement to develop Hospital Management System
(HMS) and Android studio.
Table 1.2 Software Requirements
Hardware Description Cost (RM)
Laptop with 4GB of RAM Workstation for the project 2000.00
Hard disk space (227GB) To save data
Others Keyboard and Microsoft Mouse or compatible
pointing device and Android mobile etc.
1000.00
Printer A printer to test the report generating function. 300
Total: 3300.00
Software Description Cost (RM)
Easy PHP Website interface Free
Android studio Android version Free
Microsoft Office 2007 Documentation Tools. Free
Notepad +++ Website coding editing tool Free
Mysql Database used for this system. Free
Microsoft Visio To draw Gantt chart Free
Web hosting Platform to get hosting 500
Google Chrome, Internet Explorer Web Browser. Free

6. Page -6
1.6 Significance of Project
Currently the hospital operates a manual records system. With the introduction of an
automated system the following will be achieved.
The system is a land mark in the field of modern technology since its automated it becomes
a quick access to the required information as it is only ‘one click away’. In the field of ICT,
decision support and information availability which is required by the administration. This
is because it is able to generate reports daily, monthly and yearly. This makes it simple for
managers to make decisions. Electronic security is maintained as the staff and
management are able to login and access the system depending on their privileges. They
are also able to work on the policies and claims more effectively and efficiently.
The hospital management system will improve hospital operation for both staff and the
patient. For the staff, it will make it easy during registration process. If the patient is an
existing patient, they can easily retrieve back the record of the patient.
1.7 Summary
Introduction chapter is the initial chapter that represents the research headline and
research objectives. This chapter starts by presenting hospital management system
backgrounds, definitions and importance of information system in the health care.
Next the research focuses on the research area study and the expected outcomes from
this research. Moreover, the scope of this research is about managing the patient
information in the hospital. The objective is to develop an integrated hospital management
system. Hence, the significance of this research comes from the importance of using
health care electronic record to provide a complete patient health records to make proper
diagnoses, prescription, and treatments. It is also to track down all patient information.

7. Page -7
CHAPTER II
2.0 LITERATURE REVIEW
2.1 Introduction
The second chapter is Literature Review. A literature review is a body of text that aims
to review the critical points of current knowledge on a particular topic. The purpose of
Literature review is to discuss several literatures that are related to this project area. This
chapter will include description about the hospital management system Android (Android
mobile application)” definition and briefly discuss two case studies about the existing
system. Then, the chapter will continue on the comparison techniques or variables that
have been established based on journal, articles and web sites that are related to
methodology and approaches.
In The development of applications for smartphones and tablet PCs running operation
systems like Apple iOS or Google Android attracts the interest in many fields of daily living.
In healthcare new applications fields like home tele monitoring or ambient assisted living
have been based on mobile devices acting as remote terminals for medical data collection
and intuitive user interaction. At hospital wards smartphones and tablet PCs enable
clinicians and nurses to treat patients more easily directly at their hospital beds or to share
and present data to clinical personnel for decision making independently on their current
location. In this chapter will present insights into the development process of a mobile
Android-based in-hospital glucose management system for the treatment of acute ill
patients with diabetes type. The system will provide decision support for insulin dosing and
therefore falls within the scope of the revised medical device directive (MDD) for software
design and implementation. Thus, we focus our discussion on the designand development
process of software as a medical device.
2.2 Domain
Concerns abound about serious lack of specialized health care facilities (Ouma and
Herselman; 2008). Web-Based Hospital Management information Systems include
strategic decision support systems and clinical documentation systems. Some of the
clinical support systems include medicine Maintenance System, and electrics health
record management Systems Others are pharmacy information systems and personal
data analysis systems with important added feature for messaging between providers and
staff, and the ability to share data with other medical facilities (Keenan et al;
2006).According to Zhejiang chiyan (2014) Grassroots healthcare institutions (GHIs) are
the smallest administrative levels of medical institutions, where most patients access
health services.

8. Page -8
2.3 Case study
I choose two case study that related to the hospital management system. The first
case study is Medicine Maintenance System and second case study is Electronic Health
Record Management System
2.3.1 Case study 1: Medicine Maintenance System
When the hospital buy a whole sale medicine form the pharmacy, all the medicine
information are store individual with a specific code attached to each of when it is stored
into this database. This will give good detailed information of how many were bought and
how many were used while also preventing an out of stock situation.
2.3.2 Case study 2: Electronic Health Record Management System
The patient Record Management System is a system that can manage multiple users
of the system and can have the track of the right assigned to them. It makes sure that all
the users function with the system as per the rights assigned to them and they can get
their work done in efficient manner. It is a Customizable and strong administration system
i.e. changes of password of users at the administration point. The information management
system will be able to capture information about an old patient the information captured
will be easily managed by the administrators more easily.
2.3.3 Case Study: Mobile Application for in-hospital Glucose Management Design
Phase.
Referring to the requirements of the medical device directive (especially IEC 62366 and
IEC 14971), which target usability of medical software and consequently the provision of
clinical safety for users and patients, we have chosen a user-centered design approach.
A team consisting of technicians, software engineers, physicians and nurses from
JOANNEUM RESEARCH and the Division of Endocrinology and Metabolism at the
Medical University of Graz defined in weekly meetings the first version of the user interface
and the functionality of the glucose management system. We used paper1 and software
mockups as trigger in order to have a basis for discussion and testing. FORTH-ICS
provided external reviews for the design phase. We supported the design
http://www.artfulbits.com/Android/Stencil.aspx process by regular risk analysis sessions
with all involved stakeholders. Derived risks have been collected and incorporated as
change requests into the requirements. In the first iteration, we summarized the elicited
requirements in an extensive specification document. A detailed discussion of the design
phase can be found in.

9. Page -9
2.3.4 Development Phase. Due to maintainability and expandability we decided to
distinguish between an Android-based user interface and a platform independent backend
(Java-based webserver) which contains business logic for the decision support, as well as
the data storage and interfaces to the hospital information system. The exchange of data
between the backend and frontend components requires mutual authentication and is
completely done via encrypted web services to provide data security. The frontend
application presents the data, received from the backend, in an appropriate manner to the
user and collects new relevant data. The behavior of the frontend application relates in
every step to the clinical workflow, which was identified together with end-users in the
design phase. During the development process of the frontend, as well as of the backend,
we adapted Atlas Sian JIRA2 as a requirement, issue tracker and task management tool
for the documentation of each implementation step. JIRA acts as preparation for the needs
of the IEC 62304 standard, and for ensuring an overview of open and already completed
requirements, development tasks and identified bugs. In JIRA, each of these issues is
assigned to an authorized editor who reports after finishing the issue. We connected JIRA
to Atlas Sian Fisheye for source code management and Atlas Sian Bamboo for continuous
integration and release management.
2.3.5 Verification Phase. In addition to the need of a detailed documentation, IEC 62304
and IEC 62366 demands also for verification and validation during the development
process. Whilst we use TestNG3 for the backend to verify the functionality after finishing
the implementation of each system unit, we are testing the correct behavior of the frontend
application on simulated user interactions. Android offers tools for instrumentation testing,
which verifies, that the application prints out the desired output on the screen for every
input. We used the free testing tool rubidium for the simulation of user interactions. Before
we start frontend test cases the database is initialized with test case specific data through
a separate web service. We use the Maven-Android plugin5 as software project
management tool for the generation of executable files. Maven for Android organizes
application related dependencies and allows the automated execution of the frontend
tests. Thus, we created a flexible and configurable development and verification process,
for the Google Android-based development environment, that provides a stable base for
developing according to the regulations of the medical device directive.

10. Page -10
Table: Comparison between case study 1 and case study 2
Features
Case Study 1:
Medicine
Maintenance System
Case Study 2: Electronic
Health Record
Management System
Login module √ √
User module X √
Product module √ √
Order module √ √
Inventory module √ √
Report module √ √
Complain module √ √
Use database concept √ √
Using Hypertext Preprocessor
(PHP) as a programming language
X √
Android Studio √ √
Using Structured Query Language
(SQL) as a database
√ √
Standalone system √ √
This table about the record of medicine maintenance system and health record Management
system. Here I Have need to know about Login module, User module, Product module,
Order module etc. For User Module and Using Hypertext Preprocessor (PHP) as a
programming language no need to know case study 1.
2.4 Development environment
2.4.1 Comparison of programming language
I. Hypertext Preprocessor
Hypertext Pre-processor (PHP) was written in the C programming language and it is
an HTML-embedded Web scripting language. The output from the PHP functions on the
page is typically returned as HTML code, which can be read by the browser. Because the
PHP code is transformed into HTML before the page is loaded, users cannot view the PHP
code on a page. (TechTerms.com) This make PHP pages secure enough to access
databases and other secure information. PHP is also great for creating database-driven
Web sites.

11. Page -11
PHP: Hypertext Preprocessor (or simply PHP) is a server-side scripting language
designed for Web development, but also used as a general-purpose programming
language. It was originally created by (Rasmus Lerdorf in 1994) the PHP implementation is
now produced by The PHP Group. PHP originally stood for Personal Home Page, but it
now stands for the recursive initialism PHP: Hypertext Preprocessor.
PHP code may be embedded into HTML code, or it can be used in combination with
various web template systems, web content management systems, and web frameworks.
PHP code is usually processed by a PHP interpreter implemented as a module in the web
server or as a Common Gateway Interface (CGI) executable. The web server combines
the results of the interpreted and executed PHP code, which may be any type of data,
including images, with the generated web page. PHP code may also be executed with
a command-line interface (CLI) and can be used to implement standalone graphical
applications.
phpMyAdmin is a free software tool written in PHP, intended to handle the administration
of MySQL over the Web. phpMyAdmin supports a wide range of operations on MySQL
and MariaDB. Frequently used operations (managing databases, tables, columns,
relations, indexes, users, permissions, etc.) can be performed via the user interface,
while you still have the ability to directly execute any SQL statement.
phpMyAdmin comes with a wide range of documentation and users are welcome to
update our wiki pages to share ideas and how to for various operations. The phpMyAdmin
team will try to help you if you face any problem; you can use a variety of support
channels to get help.
phpMyAdmin is also very deeply documented in a book written by one of the developers
– Mastering phpMyAdmin for Effective MySQL Management, which is available in
English and Spanish.
To ease usage to a wide range of people, phpMyAdmin is being translated into 72
languages and supports both LTR and RTL languages.
phpMyAdmin is a mature project with a stable and flexible code base; you can find out
more about the project and its history and the awards it earned. When the project
turned. we published a celebration page.
The phpMyAdmin project is a member of Software Freedom Conservancy. SFC is a not-
for-profit organization that helps promote, improve, develop, and defend Free, Liber, and
Open Source Software (FLOSS) projects.

12. Page -12
2.4.2 Comparison of database technology
i. Android
Android is a mobile operating system currently developed by Google, based on the Linux
kernel and designed primarily for touchscreen mobile devices such as smartphones and
tablets. And as we said before, Android offers a unified approach to application
development for mobile devices.
Android is an open-source operating system named Android. Google has made the code
for all the low-level "stuff" as well as the needed middleware to power and use an electronic
device, and gave Android freely to anyone who wants to write code and build the operating
system from it. There is even a full application framework included, so third-party apps can
be built and installed, then made available for the user to run as they like.
The "proper" name for this is the Android Open Source Project, and this is what people
mean when they say things like Android is open and free. Android, in this iteration, is free
for anyone to use as they like.
ii. Android Studio
Android Studio is the official integrated development environment (IDE)
for Google's Android operating system, built on JetBrains' IntelliJ IDEA software and
designed specifically for Android development. It is available for download
on Windows, mac OS and Linux based operating systems. It is a replacement for
the Eclipse Android Development Tools (ADT) as primary IDE for native Android
application development.
Android Studio was announced on May 16, 2013 at the Google I/O conference. It was in
early access preview stage starting from version 0.1 in May 2013, then entered beta stage
starting from version 0.8 which was released in June 2014. The first stable build was
released in December 2014, starting from version 1.0. The current stable version is 3.2,
which was released in September 2018.
iii. My SQL
A database is a structured collection of data. It may be anything from a simple shopping
list to a picture gallery or the vast amounts of information in a corporate network. To add,
access, and process data stored in a computer database, you need a database
management system such as MySQL Server. Since computers are very good at handling
large amounts of data, database management systems play a central role in computing,
as standalone utilities, or as parts of other applications.
MySQL is a database system used on the web. Basically, a MySQL database allows
creating a relational database structure on a web-server somewhere in order to store data
or automate procedures. If we compare to Microsoft Access, MySQL is what holds all

13. Page -13
tables, PHP acts as queries, and forms are basically web pages with fields in them. With
all of this combined, we can create truly spectacular projects on the web.
MySQL is a central component of the LAMP open-source web application software stack
(and other "AMP" stacks). LAMP is an acronym for "Linux, Apache, MySQL, Perl /PHP/
Python". Applications that use the MySQL database
include: TYPO3, MODx, Joomla, WordPress, Simple Machines Forum, phpBB, MyBB,
and Drupal. MySQL is also used in many high-profile, large-scale websites,
including Google (though not for searches), Facebook, Twitter, Flickr, and YouTube.
2.5 Justification
Features Description
Programming
Language
Hypertext Preprocessor
 Open source general-purpose scripting language
that is especially suited for web development and
can be embedded into HTML.
Database Technology
MySQL
 To add, access, and process data stored in a
computer database.
2.6 Summary
This chapter has discussed the literature review for subject registration system. The
chapter has described several. Software development methods will be used in order to
develop the system. Although the majority of the research completed on Android
development techniques is very comprehensive, existing literature still lacks support for
thesis problems. These deficiencies are explored throughout the research for this thesis
and explained in the following paragraphs.

14. Page -14
CHAPTER III
3.0 RESEARCH METHODOLOGY
3.1 Introduction
The chapter firstly describe about the questionnaire as data collection method which
include the sample for mix methods that used during the data collection methods. After
successful data collection, collected data will be analyzed and interpreted.
Then, the chapter will continue on the software/product development methods to describe
the selected approach used in the project. The detail activities that may have to be done
in every stage shall be describes.
3.2 Data collection methods
Data collection method is important in developing any project. The data collection method
that are used in gathering info to develop the system is questionnaire.
3.2.1 Questionnaire
Questionnaire has been is made to gather information of this system. The questionnaire
is made by my own design that related to the project. (ok state) This questionnaire consists
two structure of questions which is question A is for general personal data and section B
is for current flow of business processes.
Besides, the pilot questionnaire also has been done to test the questionnaire. (help.
survey. monkey) It is evaluated by five respondents to test if the main questionnaire being
developed is going to function properly. It is usually done to improve the research method
that is used in the questionnaire. Next the questionnaire were distributed to thirty-two
respondents and also get the same amount for good feedback.
3.3 Data analysis method
All the data or requirement that has been collect will be analyze one by one to find the
proper solution to the problem and design the solution they need.
In this project the data analysis method that being used for questionnaire data is statistical
analysis, the questionnaire are being collected and the statistical of answer are choose,

15. Page -15
that mean the developer will make a decision depend on the answer most selected for
example most of respondent (18 over 25) strongly agree to use the online ordering. The
developer will find solution to fulfill the requirement ask by customer.
3.4 Software/product development methods
To develop this system, I had identified a suitable methodology to follow during the
implementation of Hospital Management System (HMS). The chosen methodology is
Unified Software Development Process or known as the USDP. USDP is an architecture-
centric, use-case driven, iterative and incremental development process that leverages
unified modelling language and is compliant with the system process engineering Meta
model. (Programmers. Stackexchane)
USDP is divided into four phases’ inception, elaboration, construction and transition.
Figure 3.1 shows how it works.
Figure 3.1 Unified software development process
I. Inception Phase
The project planning starts in this phase. Inception is the smallest phase in the project.
First, the information is gathered and the end users about the manual system. Before
starting to build the system, problem must be analyses in current system then try to solve
problem that have in current system. At the same time, element that is in the database
should be known.
Inception
Phase
Elaboration
Phase
Construction
Phase
Transition
Phase

16. Page -16
II. Elaboration Phase
During this phase, the manual system is investigated and improvement opportunities are
identified based on the information gathered in the Initiation phase. The user requirements
are gathered, analyzed and reviewed. The final deliverable from this phase is plan for the
Construction phase.
III. Construction Phase
Construction is the largest phase in this project. The output produced in the Elaboration
phase is built on the foundation laid in Elaboration. Common UML (Unified Modeling
Language) diagrams used during this phase include Activity and Sequence Diagram.
IV. Transition Phase
The final project phase is Transition. In this phase the system is deployed to the target
users. Feedback received from an initial release (or initial releases) may result in further
refinements to be incorporated over the course of several Transition phase iterations.
3.5 Summary
This chapter has discussed the research methodology for Hospital management Android
system HMSA. The chapter has been described data collection method and analysis
method is used based on the type of data collection methods. The software/product
development method USDP is used to accomplish this study.
The next chapter will discuss the analysis phase which will cover the user requirements
and system requirements of the project. The system requirements will consists functional
requirements and non-functional requirements in order to capture the system work's flow.

17. Page -17
CHAPTER IV
4.0 ANALYSIS
4.1 Introduction
Analysis phase is important to capture any requirement of the software project and it
is involved in any of project approach and methodology. Analysis was the second phase
of this project which will describe two main topics which is user requirements and system
requirements. This chapter will begin by presenting the user requirements which will show
the gathered information based on the analysis of the user requirement. Later than that,
this chapter will describe indeeply the system requirement of the online registration system
which will include the functional requirements and non-functional requirements. Data flow
diagram is used to presents specified functions of the system. (Smart draw) Besides, the
discussion of non-functional requirement of the system also will be applied in this chapter.
4.2 User requirements
In Hospital Management System (HMSA), a user of this system are patient and admin.
4.2.1 Questionnaire analysis
Questionnaire analysis is a quantitative analysis which all the data are presented in
number form. Based on the number of respondents this is the result of their opinion from
the questionnaire regarding the satisfaction and need that they wish to be added into the
online registration system. The Questionnaire question as in Appendix A.
Figure 4.1 Percentage of patient that prefer to making appointment
48%
24%
16%
12%
Making appointment for checkup
strongly agree agree not sure disagree

18. Page -18
Clinics need information to identify you, to locate your medical record and to reserve the
appropriate amount of time for your appointment. We will ask you for the following
information:
 Your name
 Your date of birth or Social Security number (this helps ensure that your medical
information is not confused with someone who has a similar name)
 Reason for the appointment (be as specific as possible so that we can reserve the
right amount of time for your visit)
 Whether you want a particular doctor/healthcare provider or the first available
appointment.
Figure 4.2 Percentage of patient that how much time they have to wait in hospital
The amount of time a patient waits to be seen is one factor which affects utilization of
healthcare services. Patients perceive long waiting times as barrier to actually obtaining
services and keeping patients waiting unnecessarily can be a cause of stress for both
patient and doctor.
Figure 4.3 Total percentage of patient that they satisfied this hospital
Patient satisfaction is an important and commonly used indicator for measuring the
quality in health care. Patient satisfaction affects clinical outcomes, patient retention, and
medical malpractice claims. It affects the timely, efficient, and patient-centered delivery of
quality health care. Patient satisfaction is thus a proxy but a very effective indicator to
measure the success of doctors and hospitals. This article discusses as to how to ensure
patient satisfaction in dermatological practice.
41%
29%
18%
12%
Waiting time in hospital
strongly agree agree not sure disagree

19. Page -19
4.3 System requirements
4.3.1 Functional requirements
Table 4.1 Functional requirements for patient
List of Requirement Description
PATIENT
Requirement 1: Register The system should allow patient to register to login the
system by inserting personal information of patient.
Requirement 2: Login The system should allow patient to access their accounts
through the insert correct email and password.
Requirement 3: View patient
info module
The system should allow patient to view details which
consists of patient name, patient email, patient type,
address, and contact number.
Requirement 4: View
appointment module
The system should allow patient to view appointment
which consists of doctor name, time of appointment with
doctor.
Requirement 5: Make payment
module
The system should allow patient to make confirmation
payment. Patient have to make payment either by online
or cash. Next, the system should allow patient to click
complete order and invoice will be produced.
Table 4.2 Functional requirements for admin
List of Requirement Description
ADMIN
Requirement1: Login The system should allow admin to access their
accounts through the insert correct admin ID and
password.
Requirement2: Manage
patient module
The system should allow admin to check list of patient
that consists of patient name, patient type, address.
The system should allow admin to search, update and
delete patient information.
Requirement3: Register
patient module
The system should allow admin to register new patient
by inserting personal information of patient.
Requirement4: Generate
bills module
The system should allow admin to view summary of
bills. Admin can generate bills of patient.

20. Page -20
4.3.2 Non-functional requirements
Table 4.3 Non-functional requirements
List of
Requirement
Description
Requirement 1:
Consistency
The Hospital Management System (HMS) provide consistency
user interface design to the end-user. The designs of the screen
are standardize and consistent that make the end-user feel
comfortable to use it
Requirement 2:
Availability
The system provide the end-user to login the system 24 hours a
day.
Requirement 3:
Security
The Hospital Management System (HMS) provide the password
security access control to avoid unauthorized user to login to the
system.
Requirement 4:
Reliability
The HMS provide the effective method to maintain the back-end
of the system. All of the subject list are manage by this system
effectively.
Requirement 5:
Usability
Learning time and experience needed such as hours or number
of lessons to learn the system
4.4 Summary
To ensure a successful outcome, the developer must satisfy all the needs and wants of
the user when the development is complete. To achieve this, developer need should not
only be studied by techniques such as interview or make analysis, but they should also be
reflected back to user in order to create the prototype based on the user requirements.
The requirement will be clearer as the system develops and more formal user evaluation
takes place.

21. Page -21
REFERENCES
Developer: Google, Open Handset Alliance last update Android P / July 25, 2018;
Available: https://en.wikipedia.org/wiki/Android_(operating_system), [Accessed: 27
November 2018].
Developer : Google, JetBrains, Android Studio 3.2 RC3 (September 10, 2018; Available:
https://en.wikipedia.org/wiki/Android_Studio, [Accessed: 27 November 2018].
Dr Dinesh Chandra Misra, I.A.S. (Retd.) 2006, Defining e-government: a citizen-centric
criteria based approach, Available: http://unpan1.un.org/ intradoc/groups/ public
/documents/ UNPAN/ UNPAN023588.PDF (10-03-2008).[ Accessed: 27 November 2018].
Rasmus Lerdorf, 2018: Available: https://en.wikipedia.org/wiki/PHP, [Accessed: 27
November 2018].
Mansi Chitkaram, 2011, “Hospital Management System” International School of
Informatics & Managemen, Available: http:// www.scribd.com/doc /13569522/ 09
ProjectHospital - Management-System, [Accessed: 27 November 2018].
Ouma and Herselman; 2008. Designing A Web Based Hospital Management System For
MOUAU Clinic Available: http://www.ijtrd.com/papers/IJTRD1361.pdf . [Accessed: 26
November 2018].
Keenan et al; 2006. An Electronic Medical Record in Pediatric Medical Education: Survey
of Medical Students’ Expectations and Experiences, Available:
https://www.researchgate.net/publication/6659949_Electronic_Medical_Records_and_Th
eir_Impact_on_Resident_and_Medical_Student_Education. [Accessed: 26 November
2018].

22. Page -22
Appendix A Questionnaire
Hospital Management System Android (HMSA)
Instructions: (Please tick √ and fill in the blank space below)
PART A: General Personal Data
1. Users :
Diploma Degree Lecturer
1st semester student 2nd semester student Lecturer
PART B: Business Flow
Strongly Agree- 1 Agree- 2 Uncertain- 3 Disagree- 4 Strongly Disagree- 5
 
1 2 3 4 5
1. Ease of making appointment for checkups
(physical exam, well visits, and routine follow-up
appointments)?
2. Ease of making appointments for sickness?
3. Ease in obtaining follow-up information and care
(test result, medicines, and care instructions)?
4. The way your doctor involves other doctors and
caregivers in your care when needed?
5. Waiting time in our Hospital?
6. Overall patient satisfactions?