The Hospital Management System-individual assignment-jayashan-cb004082

CE00846-3 BWA Jayashan Fernando-CB004082
APIIT Sri Lanka Page 1 of 40
1 Acknowledgement
This module looks at the practical considerations of developing web applications that support
with database. The student will have the opportunity to design, implement and critically
evaluate server side web applications with an understanding of issues relating to web
standards and web development methodologies.
Through this module as students we gain knowledge of current web standards and their
impact on web applications and as well as conceptual understanding of issues relating to web
design and development. Through the specifications, design and implementation of web
applications we learnt MVC architecture and also 3 layer architecture.
As an outcome of this module we understand the real world problems, in web development
industry. In here we specially discussed globalization in creating and developing web
applications.

Table of Contents
1 Acknowledgement .............................................................................................................1
2 Introduction........................................................................................................................4
2.1 Main features of the (AHMS) .....................................................................................4
3 Requirement specification .................................................................................................5
3.1 Scope...........................................................................................................................5
3.2 Audience definitions, Acronyms and abbreviations ...................................................5
3.2.1 Audience definitions............................................................................................5
3.2.2 Acronyms and abbreviations................................................................................5
3.3 Overall description......................................................................................................6
3.3.1 Product perspective..............................................................................................6
3.3.2 Product functions .................................................................................................6
3.3.3 Administrators......................................................................................................6
3.3.4 Doctors.................................................................................................................6
3.3.5 Patients.................................................................................................................6
3.3.6 Nurses ..................................................................................................................7
3.3.7 Pharmacists ..........................................................................................................7
3.4 Operating environment................................................................................................7
3.5 Design and implementation constraints ......................................................................7
3.6 Assumptions and dependencies...................................................................................7
3.7 Functional requirements..............................................................................................8
3.7.1 System administrator ...........................................................................................8
3.7.2 Patient ................................................................................................................10
3.7.3 Nurse..................................................................................................................12
3.7.4 Pharmacists ........................................................................................................14
4 Requirement modelling....................................................................................................16
4.1 Data Flow Diagram (DFD) .......................................................................................16
4.2 E-R Diagram .............................................................................................................17
4.3 Database diagram ......................................................................................................18
4.4 Constraints.................................................................................................................19
4.5 Assumptions and dependencies.................................................................................19
4.6 Specific requirements................................................................................................19
4.6.1 Functional requirements.....................................................................................19
5 Analysis of web development platforms..........................................................................21
5.1 On deciding between web application platforms ......................................................21
5.1.1 What are most commonly used platforms in industry .......................................21

5.1.2 Comparison with different web platforms .........................................................22
5.2 Comparison differences between PHP and ASP.NET..............................................23
5.2.1 What is PHP?.....................................................................................................23
5.2.2 What is ASP.NET? ............................................................................................23
5.2.3 Speed..................................................................................................................23
5.2.4 Cost ....................................................................................................................24
5.2.5 Platform compatibility .......................................................................................25
5.2.6 Database connectivity........................................................................................25
5.2.7 Brief summary ...................................................................................................25
5.2.8 Conclusion .........................................................................................................26
5.3 Comparison differences between PHP and Perl........................................................26
5.3.1 What is PERL Language?..................................................................................26
5.3.2 Similarity between PHP and PERL ...................................................................26
5.3.3 Differences between PHP and PERL.................................................................26
6 Logical design..................................................................................................................27
6.1 Structure of hospital management system.................................................................27
6.2 Wireframes and interfaces.........................................................................................28
6.3 Sign up Form.............................................................................................................29
6.4 Patient Login .............................................................................................................30
6.4.1 Logged In...........................................................................................................30
6.5 Admin panel..............................................................................................................31
6.5.1 Admin dashboard...............................................................................................31
6.6 Add admin users........................................................................................................32
6.7 Add doctors ...............................................................................................................32
6.8 Add nurses.................................................................................................................33
6.9 Arrange doctor schedule............................................................................................33
6.10 Update the contents of the web application...........................................................34
7 Implementation ................................................................................................................35
7.1 System implementation.............................................................................................35
7.1.1 Step 1: designing interface.................................................................................35
7.1.2 Step2: Coding for patient login page .................................................................36
7.1.3 Step 3: display database values..........................................................................37
7.1.4 Step 4: Create sessions, call sessions and delete sessions .................................37
8 Conclusion .......................................................................................................................39
9 References........................................................................................................................40

2 Introduction
The Hospital Management System (AHMS) is a web based management system that is
designed for instead of manual process of hospital that the user can do systematic methods of
managing hospital and records patient’s appointment details more effectively and efficiently
for both patients and hospital administrator through online.
2.1 Main features of the (AHMS)
This online system manages daily activities of hospital and all its departments such as
pharmacy and laboratory. Through this online system especially customer can make
appointments with particular doctor and able to make payments online.
Any patient can register with this system or by informing the hospital administrator patient
can register with this system. Each system users who system administrator, doctor nurse and
pharmacist have privileges to access this system. This system is globalized with Sinhala,
Tamil and English languages so user can choose preferred language as user want.

3 Requirement specification
The purpose of this report is to introduce the hospital management system (AHMS) as
product. This report contains the functional and non-functional requirements of the project.
3.1 Scope
HMS product is basically performing the manual hospital system in to a web based
application system so that the users who patients can know the available of specialist doctors
under specialty. So patients can make appointments through online and can check their
medical reports through online. Patients can view invoices and manages own profile too.
The project is specifically designed for the patients and hospital administrators. The product
will work as a complete user interface for hospital management process and hospital usage
from ordinary users. HMS can be used to monitor patients through online.
3.2 Audience definitions, Acronyms and abbreviations
3.2.1 Audience definitions
The intended readers of this document are the developers of this web site, testers, hospital
owners and administrators, doctors, patients, nurse pharmacist and coordinators. If any
suggested changes based on the customer requirements must be included with the system.
3.2.2 Acronyms and abbreviations
Acronyms Meaning
AHMS APIIT Hospital Management System
SQL
Structured Query Language
PHP
Hypertext Pre-processor
MVC
Model View Controller
PERL
Practical Extraction and Report Language

3.3 Overall description
3.3.1 Product perspective
HMS is a replacement for the ordinary management systems which depend on paper work for
recording patient’s appointment details and medical details. AHMS will provide an advanced
hospital management system and make it easy for patients to keep contact with hospital and
the specialist doctor through online.
3.3.2 Product functions
3.3.3 Administrators
 Manage departments of hospital
 Manages doctor account
 Manage patients account
 Manage nurse account
 Manage pharmacist account
 Update and edit doctor’s appointment schedule
 Manage Patients appointment history
 Manage own profile
 Manage system settings
3.3.4 Doctors
 Manage patient’s account opening and updating
 Create and manage appointments with patients
 Create prescribe for patient
 Keep records of patients
3.3.5 Patients
 Can register with the system
 Search doctors
 Check doctors time table
 View own appointments list
 View doctors list
 View invoices

3.3.6 Nurses
 Manage patients account and opening
 Manage own account
3.3.7 Pharmacists
 Manage medicine categories
 Add new medicine to the system
 Provide medication to prescription
 Manage own account
3.4 Operating environment
The AHMS is web based application system shall operate in all famous browsers for model
we are taking Microsoft Internet Explorer , Google Chrome, Mozilla Firefox with flash and
java scripts.
3.5 Design and implementation constraints
 The information of all users, must be stored in a database that is accessible by through
the web application
 My SQL Server will be used as SQL engine and database
 Users must have their correct username and passwords to enter in to system and
maintain own accounts
3.6 Assumptions and dependencies
The product needs following third party products
 MY SQL Server to store database, in here developers used XAMP P server to run this
application on a local server.
 PHP, bootstrap to develop and design this product

3.7 Functional requirements
3.7.1 System administrator
Prerequisite (admin signed in) for all requirements below
Title Description
Add doctors
This action is done to add new doctors to the
system
Add users
This action is done to add new users to the
system
Delete users
Admin can delete users due some specific
rules
3.7.1.1 Use case for system administrator

3.7.1.2 Activity diagram for administrator

3.7.2 Patient
Prerequisite (patient must signed in) for all requirements below
Title Description
Search doctors
This action is done to add new doctors to the
system
Make an appointment
This action is done to add new users to the
system
Check medical info
Admin can delete users due some specific
rules
3.7.2.1 Use case diagram for patient

3.7.2.2 Activity diagram for patent

3.7.3 Nurse
Prerequisite (nurse must signed in) for all requirements below
Title Description
Manage patients account Able to manage and view patients account
Manage own account
Nurse can make settings and update own
profile info
3.7.3.1 Use case diagram for nurse

3.7.3.2 Active diagram for nurse

3.7.4 Pharmacists
Prerequisite (patient must signed in) for all requirements below
Title Description
Manage Medicine
Categorise medicine and add different types
of medicine to the system
Provide Medication Provide medication to prescription
Manage own account Manage and update own account info
3.7.4.1 Use case diagram for pharmacists

3.7.4.2 Activity diagram for pharmacists

4 Requirement modelling
4.1 Data Flow Diagram (DFD)
Figure 1: Data Flow Diagram

4.2 E-R Diagram
Figure 2:E-R Diagram

4.3 Database diagram
Figure 3: database diagram

4.4 Constraints
 The information of all the users including patient’s info must be stored in the hospital
database that is accessible by the online hospital management system
 Users can access the AHMS from any computer that has internet browsing
capabilities and an internet connection.
 The users must have their correct username and passwords to enter in to the AHMS
4.5 Assumptions and dependencies
 The users must have sufficient knowledge of accessing of web applications.
 This application provide globalized with 3 different languages such as Sinhala,
English and Tamil so user can select preferred language.
 The product can access AHMS database.
4.6 Specific requirements
This section describes in detail all the functional requirements.
4.6.1 Functional requirements
 Support database, here developers use My SQL server database to save user data.
 User authentication procedures
 Functions with certain degree of complexity such as functions that generate page
content from a database.
 Support internet and public users as well as administrators.
 Development should be based on MVC architecture.
 Required accessibility, globalization features already implemented.

4.6.1.1 Logon capabilities
The system shall provide the users with logon capabilities.
4.6.1.2 Alerts
The application can alert the users in case of any problem such as when they the user insert
invalid username and password
4.6.1.3 Usability
 Since all users are familiar with the general usage of browsers, so no need specific
training is required.
 This web application is user friendly and self explanatory
4.6.1.4 Accuracy
The accuracy of the product will be depending on the speed of the internet that provide by the
service provider.

5 Analysis of web development platforms
5.1 On deciding between web application platforms
Huge numbers of projects of all sizes for building web-based applications of all sorts are
started each year. But when selecting web development platforms to use is a great challenge.
And it may appear sensible for given project.
According to the (techopedia) platform is a group of technologies that are used as a based
upon which other applications, processes are developed or platform is a programming
language with combination of set of technological pieces such as frameworks, libraries, tools
and auxiliary languages. (techopedia, 2014).
Most of web application platforms work with number of auxiliary languages such as HTML,
CSS and java scripts.
5.1.1 What are most commonly used platforms in industry
 .NET (ASP.Net....etc)
 Java EE
 Perl
 PHP
 Ruby
 Python

Asp.net Java EE Perl PHP Ruby Python Scala
Java
Script
Perl C++
Ranking 23 100 70.1 84.6 78.6 92.4 62.5 84.3 70.1 95.5
23
100
70.1
84.6
78.6
92.4
62.5
84.3
70.1
95.5
0
20
40
60
80
100
120
Rank%
Spectrum’s 2014 Ranking
0
10
20
30
40
50
60
70
80
90
Asp.net Perl PHP
Rank%
platforms
Spectrum’s 2014 Ranking
Ranking
5.1.2 Comparison with different web platforms
Altogether when comparing with the above ranking there was a strong representation from
PHP and a somewhat weaker turnout from .NET. Given some enthusiastic promotion from
the Perl community, there was a slightly more than expected turnout of Perl language.
The platforms considered in this evaluation part are ASP.Net, Perl and PHP.
Figure 4: Source: IEEE Spectrum’s 2014 Ranking
Figure 5: Figure 1: Source: IEEE Spectrum’s 2014 Ranking

5.2 Comparison differences between PHP and ASP.NET
5.2.1 What is PHP?
According to the PHP official web site PHP is a widely used open source language and a
scripting language that is especially suited for web development and can be directly
embedded in to HTML rather than calling an external file to process data.
In PHP, we use some special PHP tags that programmer can alternate between HTML and
PHP. To view the output of the PHP to the end user, programmer must execute PHP on the
server, unless client cannot view the PHP code.
5.2.2 What is ASP.NET?
According to the Microsoft official web site ASP.NET is a unified web development model
that is server side scripting environment that is developed and released by Microsoft and it is
a part of the .NET framework.
Developers mainly use ASP to create and run dynamic web server applications. It also can
alternate between HTML and ASP.
5.2.3 Speed
Even though PHP and ASP.NET are scripting languages, when compare with speed of both,
PHP has an upper hand because PHP code runs faster than ASP and PHP code run its own
memory space.

This point may prove PHP faster than ASP .NET
These calculations done by ZOOM SEARCH application and it shows how much of time
generate to load a small website.
5.2.3.1 Test 1
Searching a small/typical website with 400 pages, and 296,601 total words (11,995 unique
words); Time is in seconds to generate and display results.
Figure 6: Evidence to show that PHP is faster than ASP.NET (Wrensoft, 2014)
5.2.4 Cost
ASP only runs on IIS installed on a windows platform server which is not free. PHP program
run on Linux, which is free.
PHP can connect to various databases, mainly My-SQL which is freely available, whereas
ASP mainly uses MS-SQL which is a product of Microsoft that needs to be purchased.
0.0000
0.2000
0.4000
0.6000
0.8000
Test 1 Test 2 Test 3 Test 4 Test 5 Test 6 Test 7
Time(sec)
Tests
Small site -400 pages,294k words
PHP
ASP.NET

5.2.5 Platform compatibility
PHP runs various platforms like Linux, UNIX, Windows and Solaris but as ASP is mainly
associated with windows platforms. Any way ASP run on Linux platforms, when install
Apache on the server.
5.2.6 Database connectivity
PHP, being extremely flexible, can connect to various databases. The most popular being
My-SQL but ASP mainly uses MS-SQL
5.2.7 Brief summary
PHP ASP.NET
Can runs on various platforms Runs only on windows platform
Available inbuilt features like FTP, email
from a web page or even encryption
mechanisms
Such features not available so some
additional components are required so
additional cost is need to for pay
Can connect various databases Mainly uses MS-SQL
PHP codes tend to easier than ASP codes Similar to visual basic syntax which also a
product my Microsoft.
PHP code based on C++ language and syntax
are similar to C/C++ and those are best
programming languages in software
developing industry.
MS-SQL which is a product of Microsoft that
needs to be purchased.ccc
PHP is open source language in free of cost
Figure 7: Some differences between PHP and ASP (webpronews, 2014)

5.2.8 Conclusion
When comparing with the above table (Figure 4) we can see, both languages have some
unique features and advantages for the users. But depending on the user requirements
developer can choose any language. Even ASP have some equally capabilities when a
developer looking for e- commerce or multimedia web application then majority would call
PHP but it doesn’t mean that ASP cannot provide user requirements like PHP.
5.3 Comparison differences between PHP and Perl
5.3.1 What is PERL Language?
PERL language is a programming language that runs on various platforms such as Windows,
Mac OS and UNIX. Normally if a developer has a knowledge of C then PERL will be very
easy to learn.
5.3.2 Similarity between PHP and PERL
Both PERL and PHP are scripting languages and the basic syntax in PHP are very similar to
PERL. Especially when declare variables both in PERL and PHP we add dollar mark ($) in
front of variables.
5.3.3 Differences between PHP and PERL
PHP PERL
Executes within browser
window
No No
Requires HTTP to execute
Yes No
Can update files on server
Yes Yes
Can use MySQL
Yes Yes
Figure 8: Differences between PHP and PERL (tutorials point 2014)
From my perspective, PHP is an all-around better choice than ASP and PERL

6 Logical design
6.1 Structure of hospital management system
In above structure (Figure 5) shows structure of Home page. The initialization interface
would be shown in the browser if don’t have any server errors. Once the user log in
successfully the user would be able to select the main functions of the AHMS which were
View, Members area and e-channel service.
If the user name or password that user entered not valid, then the server would notice it as an
error message. This web application link with the My-SQL server so all the information used
in this system was stored in the database server.
Initialization -interface
Login
Selection Functions Logout
Home View E-Channel Members Area Contact
Server error
Body
Footer
Figure 5: AHMS structure

6.2 Wireframes and interfaces
Patients can
sign up from
here

6.3 Sign up Form

6.4 Patient Login
6.4.1 Logged In
After patient login patient can view available doctors and patient can search doctors by giving
date and name and patient can make an appointment.

6.5 Admin panel
6.5.1 Admin dashboard Admin can admin users to the system
Add doctors to the
system
Add nurses to the
system
Add patients to the
system
Add doctor
schedule and update
the schedule
In here admin can
change the vision
and mission of the
web site
Get the reports of
login details

6.6 Add admin users
6.7 Add doctors
View admin table from
the database

6.8 Add nurses
6.9 Arrange doctor schedule
View nurse table from
the database
Admin can search table by
giving doctor name, then
admin can arrange the
doctor schedule

6.10Update the contents of the web application

7 Implementation
This application can easily implemented under various situation inside a hospital. Developer
added many features to this application.
7.1 System implementation
The developer has given full effort to implement a theoretical hospital system in to working
system. During the interface designing and database designing developer faced lot of
challengers. Most difficult challenge is to achieve a real time working system that it work
efficiently and effectively.
7.1.1 Step 1: designing interface
Actually as customer wanted this product within a short period of time, developer had to
complete this complex system within a short period. Actually that wasn’t so easy. To make
this easy way within a short period of time, developer used bootstrap that is a most popular
front-end frameworks and its open source project. Without using bootstrap, developer
wouldn’t be able to design lot of interfaces within short period of time. That was a major help
to the developer.
7.1.1.1 Bootstrap file structure
Figure 9 : bootstrap File Structures (Bootstrap (2014))
Bootstrap is combination of all HTML, CSS and JS functions so developer only has to call these files.

7.1.2 Step2: Coding for patient login page
Here patient can log in to system by giving correct username and password, so developer add
some user validations

7.1.3 Step 3: display database values
7.1.4 Step 4: Create sessions, call sessions and delete sessions
7.1.4.1 Create sessions
Here is the place where create session for the username that user enter to log in to system and
header is the place where we call that session that me make
Figure 10 : create sessions

7.1.4.2 Call sessions
Above picture
Above picture (Figure 8) show how secession call in a page. Use session_start () method to
call the session what we create earlier.
From the if statement we compare the session username with the session what we created if
not equal then it turn back to other page
7.1.4.3 Print the sessions
7.1.4.4 Delete sessions
To delete sessions used session_destroy() method
Figure 11: call sessions

8 Conclusion
Main of Task of this assignment was to research about current problems in websites and
identifies them and provides necessary solutions and to build a website with less the solutions
implemented to minimize the problems.
In requirement specification the author analyzed problems and proposed a well functional
system which solve the problem to some extent basically in this area the author discussed
about the user characteristics, usability and also most of the functions implemented by the
system and provided a prototype with less problems. In Requirement modelling author
provided the basic model of the system being developed with the aid of use cases, activity
and database design. In implementation author discussed about the data validations and
sessions create and deletion.
Finally the author implemented the website with the solution and proved that the problems
were solved for some extent and succeeded in providing solutions for the problems and
building a well smoothly functioning website. By Accomplishing these specific tasks author
gained immense knowledge.
The knowledge gained will help in author’s career in creating websites with fewer problems.

9 References
Techopedia (2014)http://www.techopedia.com/definition/3411/platform [ONLINE] Available at:
[Accessed 4 September 2014].
Wrensoft cooperate web site (2014) http://www.wrensoft.com/zoom/benchmarks.html [ONLINE]
Available at: [Accessed 4 September 2014].
Bootstrap cooperate web site (2014) http://getbootstrap.com/about/ [ONLINE] Available at: [Accessed
4 September 2014].
PHP cooperate web site (2014) http://php.net/manual/en/intro-whatis.php [ONLINE] Available at:
MSD cooperate web site (2014) http://msdn.microsoft.com/en-
us/library/vstudio/4w3ex9c2%28v=vs.100%29.aspx [ONLINE] Available at: [Accessed 4 September
2014].
Web-prove-news (2014) comparison differences between asp and PHP
http://www.webpronews.com/asp-vs-php-2005-12 [ONLINE] Available at: [Accessed 4 September
2014]
Tutorials point (2014) ,what is PERL http://www.tutorialspoint.com/perl/ [ONLINE] Available at:

The Hospital Management System-individual assignment-jayashan-cb004082

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to The Hospital Management System-individual assignment-jayashan-cb004082

Similar to The Hospital Management System-individual assignment-jayashan-cb004082 (20)

Recently uploaded

Recently uploaded (20)

The Hospital Management System-individual assignment-jayashan-cb004082