Kushal S L 1BF18MCA12 Final Report

Integrated Hospital Web Application
Project Report
Submitted By
Kushal S L (1BF18MCA12)
In partial fulfilment for the award of the degree of

Master of Computer Applications
Under the Guidance of
Internal Guide External Guide
K P Shailaja Sharath Raj K
Assistant Professor Project Manager
Dept. of Computer Applications Mobility Softtech
B.M.S College of Engineering. Bengaluru 560040
B.M.S. COLLEGE OF ENGINEERING

(Autonomous Institution Under VTU)
Bengaluru-560019
JULY 2021
Integrated Hospital Web Application
Project Report
Submitted By
Kushal S L (1BF18MCA12)
In partial fulfilment for the award of the degree of

Master of Computer Applications
Under the Guidance of
Internal Guide External Guide
K P Shailaja Sharath Raj K
Assistant Professor Project Manager
Dept. of Computer Applications Mobility Softtech
B.M.S College of Engineering. Bengaluru 560040
B.M.S. COLLEGE OF ENGINEERING

(Autonomous Institution Under VTU)
Bengaluru-560019
JULY 2021
DECLARATION
I hereby that this project is entitled “Integrated Hospital Web Application” carried out at
Mobility Sofftech, is a record of project work submitted to the Department of Computer
Applications, B.M.S College of Engineering, affiliated to Autonomous College under VTU is
an original work and completed by me.
To the best of my knowledge this project has not been submitted in any college or university
or published at any time prior to this.
Kushal S L
(1BF18MCA12)
ACKNOWLEDGEMENT
No achievement is possible without the help, support and guidance of inspirational people and
this project is incomplete without an acknowledgement of the gratitude of these individuals.
Each one of them has contributed in their own unique and invaluable way from the undertaking
of this project.
I wish to place my deep debt of gratitude to Dr. B. V. Ravishankar, Principal, B. M. S. College
of Engineering for his constant help.
I wish to express my heartfelt and deep debt of gratitude to Dr. S. Uma Head, Department of
Computer Applications, B. M. S. College of Engineering for her invaluable inspiration and
guidance throughout my project.
I wish to express my heartfelt debt of gratitude to, Prof. K P Shailaja, Assistant Professor,
Department of Computer Applications, B. M. S. College of Engineering for his continuous
guidance and motivation throughout the completion of my project.
I wish to express my heartfelt debt of gratitude to Mr. Sharath Raj K, Manager, Mobility
Sofftech, for his constant support in the completion of my project. I heartily thank all those
who have helped me directly or indirectly in the successful completion of this project.
Kushal S L
(1BF18MCA12)
ABSTRACT
The project entitled “Integrated Hospital Web application” is a web application that is very
helpful for a hospital organization to maintain its database. This system helps in keeping track
of patient details, doctor appointments, patients record, doctor details, Bed allotment, patient
registration, pharmacy details, medicine, laboratory details, and also hospital records. It’s
intended to use the concepts that are involved in handling the data acquired by hospital records.
The database consists of multiples tables that are managed efficiently. Based on these
classifications databases are created and based on their functions records are clubbed using
respective tables. This project proposes to adopt different technologies that can forecast the
result in an effective way, and these models help in getting more reliable and accurate results,
we have incorporated the latest trending tools to develop this web application. The purpose of
this project is to build a web application software that provides a platform for the Hospital to
carry out the day-to-day work. The technologies used in our project include HTML5, CSS3,
Bootstrap4, Node js, MongoDB.
Integrated Hospital Web Application USN: 1BF18MCA12
Table of Contents
1. Introduction ............................................................................................................................ 5
1.1 Project description. ........................................................................................................... 5
1.2 Motivation ........................................................................................................................ 6
1.3 Objective and Scope ......................................................................................................... 6
1.4 Literature Survey .............................................................................................................. 6
1.4.1 Existing and Proposed System .................................................................................. 6
1.4.1.1 Existing System ..................................................................................................... 6
1.4.1.2 Proposed System .................................................................................................... 7
1.5 Problem Statement ........................................................................................................... 7
1.6 Hardware and Software Requirements ............................................................................. 9
1.6.1 Development side...................................................................................................... 9
1.6.1.1 HardwarezRequirements ........................................................................................ 9
1.6.1.2 SoftwarezRequirements ......................................................................................... 9
1.6.2 Deployment side ..................................................................................................... 10
1.6.2.1 HardwarezRequirements ...................................................................................... 10
1.6.2.2 Software Requirements ........................................................................................ 10
1.7 Company Profile ............................................................................................................ 11
2. Systemxanalysis ................................................................................................................... 12
2.1 FeasibilityiStudy............................................................................................................. 12
2.1.1 Technical Feasibility ............................................................................................... 12
2.1.2 Economical Feasibility............................................................................................ 12
2.1.3 Behavioural Feasibility ........................................................................................... 13
3 Project Plan ........................................................................................................................... 14
3.1 Project Schedule ............................................................................................................. 14
3.2 Gaant Chart .................................................................................................................... 14
4. Software Requirement Specification ................................................................................... 15
4.1. Introduction ................................................................................................................... 15
4.1.1. Purpose................................................................................................................... 15
4.1.2. Scope ...................................................................................................................... 15
4.2. Overall Description ....................................................................................................... 15
4.2.1. Product Perspective ................................................................................................ 15
4.2.3. User Characteristics ............................................................................................... 17
4.3. SpecificxRequirements.................................................................................................. 18
Department of Computer Application-BMSCE Page 1

4.3.1. Functionalxrequirements........................................................................................ 18
Use Casei1:iLogin ............................................................................................................ 18
Use Case 2: Appointment................................................................................................. 18
Use Case 3: Prescription .................................................................................................. 19
Use Case 4: Lab Reports .................................................................................................. 19
Use Case 5: Medicine ...................................................................................................... 19
Use Case 6: Bed Management ......................................................................................... 20
Use Case 7: Billing .......................................................................................................... 20
Use Case 8: Patient .......................................................................................................... 21
Use Case 9: Logout .......................................................................................................... 21
4.3.2. Non-Functional requirements ................................................................................ 22
4.3.2.1 Performance ......................................................................................................... 22
4.3.2.2 Reliability............................................................................................................. 22
4.3.2.3 UI/IX .................................................................................................................... 22
4.3.2.4 Security ................................................................................................................ 22
5. Design .................................................................................................................................. 23
5.1. Use Case Diagram ......................................................................................................... 23
5.2. Class Diagram ............................................................................................................... 24
5.3. ActivityxDiagram .......................................................................................................... 25
5.4. Sequence Diagram......................................................................................................... 28
6. Implementation .................................................................................................................... 30
6.1 Technology Used ............................................................................................................ 30
6.1.1 Bootstrap 4 .............................................................................................................. 30
6.1.2 Node JS ................................................................................................................... 30
6.1.3 Mongo DB .............................................................................................................. 30
6.1.4 Visual studio Editor................................................................................................. 30
6.2 Pseudo code .................................................................................................................... 31
6.3 Screenshots ..................................................................................................................... 32
6.3.1 Login Page. ............................................................................................................. 32
6.3.2 Patient Dashboard. .................................................................................................. 33
6.3.3 Receptionist Dashboard. ......................................................................................... 34
6.3.4 PRO Dashboard. ..................................................................................................... 35
6.3.5 Lab Dashboard. ....................................................................................................... 36
6.3.6 Doctor Dashboard. .................................................................................................. 37
6.3.7 Pharmacy Dashboard. ............................................................................................. 38

6.3.7 Admin Dashboard. .................................................................................................. 39

7. Testing .................................................................................................................................. 40
7.1 Test cases for login page ................................................................................................ 40
7.2 Testing for other cases .................................................................................................... 41
8. Business Model .................................................................................................................... 42
9. Impact on Society and Environment .................................................................................... 43
10. Team Details ...................................................................................................................... 44
11. Conclusion ......................................................................................................................... 45
12. Future Enhancements ......................................................................................................... 46
13. Bibliography ...................................................................................................................... 47

Tables:
Table 1 Hardware requirement – Development side.................................................................. 9

Table 2 Software requirement – Development side ................................................................... 9
Table 3 Hardware requirement – Deployment side ................................................................. 10
Table 4 Software requirement – Deployment side ................................................................... 10
Table 5 Project Schedule .......................................................................................................... 14
Table 6 Product function ......................................................................................................... 16
Table 7 test case table .............................................................................................................. 40
Table 8 other test cases ............................................................................................................ 41
Figures:
Figure 1 Mobility Sofftech Logo ............................................................................................. 11

Figure 2 Gaant Char ................................................................................................................. 14
Figure 3 Use Case Diagram ..................................................................................................... 23
Figure 4 Class Diagram ........................................................................................................... 24
Figure 5 Activity Diagram - Appointment ............................................................................... 25
Figure 6 Activity Diagram – Bed allotment ............................................................................. 25
Figure 7 Activity diagram – Pharmacy .................................................................................... 26
Figure 8 Activity Diagram - Login .......................................................................................... 26
Figure 9 Activity Diagram - Laboratory .................................................................................. 27
Figure 10 Sequence Diagram – Patient Admission.................................................................. 28
Figure 11 Sequence Diagram – Doctor consultation ............................................................... 28
Figure 12 Sequence Diagram – Patient Appointment .............................................................. 29
Figure 13 Sequence Diagram – Pharmacy ............................................................................... 29
Figure 14 Login Page-desktop view ........................................................................................ 32
Figure 15 login page mobile view ........................................................................................... 32
Figure 16 Patient dashboard..................................................................................................... 33
Figure 17 Receptionist dashboard ............................................................................................ 34
Figure 18 PRO dashboard ........................................................................................................ 35
Figure 19 Lab Dashboard......................................................................................................... 36
Figure 20 Doctor dashboard..................................................................................................... 37
Figure 21 Pharmacy Dashboard ............................................................................................... 38
Figure 22 Admin dashboard ..................................................................................................... 39
Figure 23 Business model ........................................................................................................ 42

1. Introduction
1.1 Project description.
The Hospital plays an essential role in every individual life, Each facility seeks to provide
superior help to clients living with a chronic of maladies, notably stress, adverse conditions,
increased work, emotional trauma, other stress. Hospitals to make note of all day to day
operations and regarding the history of their visitors, staff, doctors, schedules, and so on, which
aids in the smooth and efficient operation of the hospital. The Integrated hospital web
application software covers the technologies that make it easier for medical practitioners like
physicians, pharmacists, and nurse to accomplish their jobs.
There is always the option of including a variety of features in the system. They have also been
intended to streamline a variety of operations in order to meet the demands of all clients.
Despite the fact that their demands appear to be different, they are both covered by healthcare
software aspects. In the healthcare business, the much more crucial considerations are still
reliability and protection. Also it is recognised for making constant and quick adjustments in
order to increase primary healthcare care quality and patient happiness. The comprehensive
hospital website feature representation is designed to give visitors, employees, especially health
workers an excellent feedback.
Nowadays there as been a lot of changes in the medical industry. The industry is moving more
towards technology as the situation demands it. Providing good quality service has been the
main agenda of industry because of competition. Compared to before interaction between
hospital and patient become convenient and simplified on both ends.
The components of an integrated hospital web application In particular, data sources can be
specified and merged to satisfy the demands and norms of both the health sector, as well as
standards of quality. Security is one of the main reasons for Inclusive Doctor's web
development tools. Entire information are safeguarded and only authorised individuals have
accessibility to them. To safeguard private data prevent unauthorized disclosure, the design
must match to actual powers and tasks.

This application helps to build a good channel between hospital and patient. Nowadays getting
reports after consultation is too hard. Managing staff also become more problem so this
application provides solutions for these problems. The automating system helped many staff
and patients in their way.
1.2 Motivation
Front-end web development is a fascinating field to work in because it is always growing and
evolving. Initially I have done some projects where majority I worked as front-end developer.
As a front-end developer, this makes it one of the most adaptable careers available to me. The
skillset that I have acquired allows me to work in a variety of fields such as image editing,
UX/UI, mobile development, and others. Front-end web development is all about originality
and problem-solving.
1.3 Objective and Scope
• To build an integrated hospital web application.

• Adding more specifications, Lab and Pharmacy module.
1.4 Literature Survey

1.4.1 Existing and Proposed System
1.4.1.1 Existing System
The existing system lacks many modules like lab and pharmacy. The user interface is more
complex now and need to fix many issues with the user interface. As of now the many of the
records are in paper need to automate. The majority of the modules are missing the graphs
which helps them to view the details graphically in a simplified way. The existing website has
multiple colour combinations which makes the website more complex.

Patient documents need to be added manually. It was time-consuming and more manpower was
needed, as it was done manually there were chances of entering the information wrong and it
was very difficult to send data from one place to another and the loss of data would result in a
major problem for both patients and Hospitals.
In the current system, any patients who want to view their records had to go manually in person
and wait for the receptionist to print their records manually. It will take lots of extra time for
the patient. The patient has to maintain a record of every policy owned by him manually or
enter the details in the excel sheet. Doctors had to know their appointments manually and also
patients had to fix their appointments manually or wait in queue for the appointments or doctor
assistance.
1.4.1.2 Proposed System
Proposed system overcome all the issues that Existing system has, It will reduce human
interference and is easily accessible to the users for their Lab report-related information. Also,
they can easily access the Hospital data with just one click. All details of patients, doctors,
appointments, medicine can be easily accessible with the proposed system. This future
development can easily abolish the drawbacks of the present system which provides the
permanent resolution to all the problems. It would help to improvise the transactions to make
them faster. The development of the Hospital management system is to control everything from
concerned officials through the main menu for preparing the schemes and reports.
1.5 Problem Statement
Its goal would be to provide limited, high-reliability mechanization of existing model.
• As of now the hospital runs Third-Party lab and Pharmacy increase in covid cases
the usage of medicine in pharmacy and lab is more so that management decided to
open new Pharmacy and lab and remove third party lab and Pharmacy.
• Integrating the Lab and Pharmacy module in the existing system.

• Making the Interface more user friendly by removing bugs and improving the
system.
• Integrating the Graphs in some modules to engage the user and to provide
information in a graphical form.
• Including the reports for the user in the website so that user can login any time and
can download the report.

1.6 Hardware and Software Requirements

1.6.1 Development side
1.6.1.1 HardwarezRequirements
Intel(R)zCore(TM)zi5-
Processorz 8265UzCPU @z1.60GHz
1.80zGHz
RAMz 8zGB
Hard Disk 1 TB
Table 1 Hardware requirement – Development side
1.6.1.2 SoftwarezRequirements
OperatingzSystem Windowsz10
Front-End Boostrap4, HTML5, CSS3
Data Base Mongo DB 4.4.2
Server-side Node JS 14.15.5
Code Editor VS Code 1.53.2
Table 2 Software requirement – Development side

1.6.2 Deployment side
1.6.2.1 HardwarezRequirements
Intel(R)zCore(TM) i3 or above
zProcessor
version
RAM Minimum 4 GB
Hard Disk Minimum 256 GB
Table 3 Hardware requirement – Deployment side
1.6.2.2 Software Requirements
Operating System Windows 7 or above version
Google Chrome 85.0 or above /

Browser
Firefox 82.0 or above
Table 4 Software requirement – Deployment side

1.7 Company Profile
Figure 1 Mobility Softtech Logo
Source(https://mobilitysofttech.com/)
Mobility Softtech is fast moving small start-up which is founded by Sharath Raj K. Mobility
Softtech is located in Bengaluru Karnataka. They Majorly work on mobile development and
also works on website development. They Work on Trending technologies and provides best
services to the customers. So, for they received 16+ awards. Several of the Mobility Softtech's
services include Android apps, web design, Apple software development, mixed software
engineering, and internet marketing.

2. Systemxanalysis
2.1 FeasibilityiStudy
The feasibilityistudy is very important for any project. Requirements and features in a project
can be decided by the feasibility study. The feasibility study will be organized with the
association of multiple teams so that the structuring of the financial requirements, operational
requirements and the technical requirements can be properly defined. Feasibility study will
help us to optimize the working. The following features are considered in feasibility study
• Technical Feasibility
• Economic Feasibility
• Behavioural Feasibility
2.1.1 Technical Feasibility
The software's technological requirements are minimal, and it does not require extra systems
and software. This study is being conducted to assess the scientific viability or technical needs
of the equipment. Any system developed must not impose a significant strain on the existing
technological resources. As a result, the customer will be put under a lot of pressure. Because
it will only demand little or no modifications to be executed, the implemented application must
have a low need.
2.1.2 Economical Feasibility
The money is only required for internet and labour cost. Since no other software or hardware
cost any money, this project is cost and time effective. This study is being conducted to
determine the state's monetary effect on the organization. The Hospital does have a certain
amount of funds to engage in the program's research & innovation. It is important to provide
justification for the expenditure. As a consequence, the final product came in just under
expenditure, thanks to the fact that the bulk of the techniques utilized were publicly accessible.

2.1.3 Behavioural Feasibility
The original study goal is to assess the program's degree of acceptance among clients. This
refers to the practise of instructing a user on how to utilise appropriate instruments. The
approaches utilised to educate and acquainted users with the system are entirely accountable
for the consumers' degree of approval. User requires no special knowledge or technical training
to understand the process as everything is Simple.

3 Project Plan
3.1 Project Schedule
Project Integrated hospital web application
Project Manger Sharath Raj K
Start date 05/03/2021
End date 24/07/2021
Overall Progress 100%
Table 5
Project Schedule
3.2 Gaant Chart
Figure 2 Gaant Char

4. Software Requirement Specification
4.1. Introduction
4.1.1. Purpose
Organizations must keep a record of their daily operations and retain records of their patients,
employees, physicians, and consultations, among other things, in order to operate the hospital
smoothly and successfully. The integrated hospital web application software includes features
that make it easier for healthcare providers such as physicians, pharmacists, and nurses to
conduct their jobs, as well as assisting patients in a more comfortable manner. The Software
Requirement Specification (SRS) will provide the features of application and explain the
process.
4.1.2. Scope
• This application helps the Patients to get the reports instantly.
• Organizing the information related to the Hospital work flow.
• Maintaining the details of all the Staffs and Patients of the hospital.
• More the Automation less the man power.
• Managing Lab and Pharmacy made easy.
• It eliminates the delays in generating the reports of patients records.
• It reduces the hectic job of maintaining several documents.
• It provides faster browsing of information by hospital management.
4.2. Overall Description

4.2.1. Product Perspective
The Integrated Hospital System is a web application which stores the information related to the
Hospital Work, staff, and patient.

All details of patients, doctors, Staff, appointments, and Reports can be easily accessible. In
addition, At each and every degree of consumer connection, the system delivers excellent data
protection, as well as powerful and dependable storing and restore abilities. Software is used
to keep track of all meetings and records.
4.2.2. Product function
Classzof Usezcases Usezcases Descriptionzof Usezcases
Use case related to login Loginx Loginztozthezapplication
Usezcase relatedzto Appointment made by

Appointment
Appointments patient
Use case related to Doctor writes Prescription to
Prescription
Prescription patient
Use case related to lab Lab reports are managed by
Lab Reports
Reports lab staff
Use case related to Pharmacy staff manages the
Categories
Categories categories of medicine
Pharmacy staff manages the
Use case related to Medicine Medicine
medicine
Use case related to Bed PRO Manages the beds
Bed management
management rooms and allots to patient
Receptionist Register the
Use case related to Register Register
patient
Receptionist Maintains
Use case related to patients Patients
patient records
Receptionist Maintains
Use case related to Billing Billing
patient bill
Table 6 Product function

4.2.3. User Characteristics
• Admin: Admin is the super user of the system he manages the doctor, staff, pharmacy
staff, Lab staff etc. he provides permissions to the other users. The complete control of
the system is with the admin.
• Patient: Patient can login to the system and can download reports and he can view the
appointments history.
• PRO: Public Relationship Officer has rights to allot bed and rooms to patients who are
in need. They have right to raise the issue.
• Lab Staff: lab staff manages the lab module where they can upload report, search for
the patient, and view appointments.
• Doctor: Doctor manages the doctor module where they write prescription to patient,
view appointment, can add visits, view patient’s data.
• Pharmacy Staff: Pharmacy staff manages pharmacy where they add medicine, add
categories, sales medicine, manage inventory, search for medicine, generates
prescriptions and view graphs
• Receptionist: Receptionist manages Reception module where they register patient,

generates bills, view appointments, searches for patients, have a right to upload the
documents and can view graphs
• Management: Management is responsible for managing the management module where

they view the analytics.

4.3. SpecificxRequirements
4.3.1. Functionalxrequirements
Use Casei1:iLogin
1. PrimaryiActor: User
2. Pre-Conditionx: Open app
3. MainxScenario:
• The person who first opened the programme was sent to the login screen.
• User given login id and password
• System do authentication
• Main screen displayed
Use Case 2: Appointment
1. PrimaryiActor: Patient
2. Pre-Conditioni: Login
3. MainzScenario:
• Patient need to enter details required.

• User can book for appointment after filling details
• User can view the appointment history.
• User can download the reports.
• User can view the enquire about the hospital

Use Case 3: Prescription
1. Primary Actor: Doctor
2. Pre-Condition: Login
3. Main Scenario:
• Doctor search for specific patient ID.

• Doctor later can add prescription for specific patient.
• Doctor can also view the appointment history.
• Doctor can download the reports of patient.
• Doctor can also Add visits.
Use Case 4: Lab Reports
1. Primary Actor: Lab Staff
3. Main Scenario:
• Lab staff can generate reports.

• Lab staff can view the appointment history.
• Lab Staff search for specific patient ID.
• Lab staff can upload reports.
Use Case 5: Medicine
1. Primary Actor: Medical Staff
3. Main Scenario:
• Pharmacy staff can add/delete medicine.

• Pharmacy staff can view the medicine list.

• Pharmacy staff can generate Invoice.
• Pharmacy staff can generate sales report.
• Pharmacy staff search for specific medicine.
• Pharmacy staff can generate reports.
Use Case 6: Bed Management
1. Primary Actor: PRO(Public Relationship Officer)
3. Main Scenario:
• PRO can Add/delete bed.

• PRO can Add/delete Room.
• PRO can view list of beds and rooms.
• PRO can Transfer bed to another patient.
• PRO can allot beds and rooms.
Use Case 7: Billing
1. Primary Actor: Receptionist
3. Main Scenario:
• Receptionist can add billing.

• Receptionist can generate bill.
• Receptionist can search for specific patient.
• Receptionist can close billing of patient after payments

Use Case 8: Patient
1. Primary Actor: Receptionist
3. Main Scenario:
• Receptionist can Register patient.

• Receptionist can book appointment on behalf of the patient.
Use Case 9: Logout
1. Primary Actor: User
3. Main Scenario:
• User can logout of the application

4.3.2. Non-Functional requirements
4.3.2.1 Performance
Hospital admins to provide secure access and privileges based on roles so that end users get
fast and secure access to applications.
4.3.2.2 Reliability
The application is more reliable at storing the overall data and records associated with the
Hospital website.
4.3.2.3 UI/IX
This application is user-friendly. Provides the best experience to the users of the system by
providing consistent font, font colour and font size throughout the website.
4.3.2.4 Security
The system is secured enough in order to maintain the important details of the patients and
staff. And also, the documents provided by the patients.

5. Design
The software is designed by implementing the various design techniques and concepts. The
software comprises of various modules and sub modules it consists of Dashboard of various
users, doctors, patient, lab staff, admin, pharmacy staff and receptionist.
5.1. Use Case Diagram
Figure 3 Use Case Diagram

5.2. Class Diagram
Figure 4 Class Diagram

5.3. ActivityxDiagram
Figure 5 Activity Diagramx- Appointment
Figure 6 Activity Diagrami– Bed allotment

Figure 7iActivityidiagram – Pharmacy
Figure 8 ActivityiDiagram - Login

Figure 9 Activity Diagram - Laboratory

5.4. Sequence Diagram
Figure 10 Sequence Diagram – Patient Admission
Figure 11 Sequence Diagram – Doctor consultation

Figure 12 Sequence Diagram – Patient Appointment
Figure 13 Sequence Diagram – Pharmacy

6. Implementation
6.1 Technology Used

6.1.1 Bootstrap 4
Bootstrap 4 is a popular front-end platform for creating contemporary websites and apps. It's
inexpensive to use and fully accessible, but it includes HTML and CSS designs for UI
components like button as well as forms. Bootstrap 4 also supports JavaScript plugins.
6.1.2 Node JS
Node.js is an open source in this we used for constructing server side. It also functions as a
cross-platform execution environment for developing server-side applications. Node.js also
comes with a large library of JavaScript components, that makes developing web - based
applications using Node.js much easier.
6.1.3 Mongo DB
MongoDB is an open source, cross-platform manuscript database programme. MongoDB is a

NoSQL software for storing and retrieving JSON-like documents and customizable schemas
to store data.
6.1.4 Visual studio Editor
Visual Studio Code is a code editor developed by Microsoft that combines the ease of use of a
text editor with sophisticated developer capabilities like IntelliSense writing code and
diagnostics.

6.2 Pseudo code
Step 1: Login to the application as Admin.
Admin login to the system by giving the valid credentials
Step 2: Admin manages and handles complete system as well as users
Step 3: The Admin adds the user and its privileges
Step 4: The Admin logs out of the system
Step 5: The hospital staff login to the Application credentials set by the admin
Step 7: The Staff views dashboard and logs
Step 8: The staff logs out of the system
Step 9: The Patient login to the Application credentials
Step 10: The Patient views dashboard and Activity logs.
Step 11: The patient logs out of the system

6.3 Screenshots
Client Sensitive information is Removed while taking screenshots like logo, location, contact
information and original photos of Hospital because of security reasons and it’s against
company policies.
6.3.1 Login Page.
Figure 14 Login Page-desktop view
• Patient can login to the system using valid

credentials
• Patient has to register in hospital later he/she can

use the system.
• Login as provided to the all the users and also to
the admin
Figure 15 login page mobile view

6.3.2 Patient Dashboard.
Figure 16 Patient dashboard
Patient dashboard consists of:

• Patient can book for new appointment.
• Patient can view Appointment booking history.
• Patient can download invoice once it is available.
• Patient can look into the reports provided by the lab staff.
• Patient can download prescription.
• Patient can manage profile.
• Patient can enquire to know any details.

6.3.3 Receptionist Dashboard.
Figure 17 Receptionist dashboard
Receptionist dashboard consists of:

• Reception Staff can book for new appointment on behalf of patient.
• Reception Staff register a patient.
• Reception Staff can forward the appointments to doctor or lab staff.
• Reception Staff add bill.
• Reception Staff view appointment booking history.
• Reception Staff can generate and download invoice.
• Reception Staff can add documents of patient.
• Reception Staff can add or delete package.

6.3.4 PRO Dashboard.
Figure 18 PRO dashboard
PRO dashboard consists of:

• PRO can add bed and room
• PRO can view list of rooms and beds
• PRO can raise the issue.
• PRO can allot beds to patients.
• PRO solve the issues.
• PRO can Free the bed.
• PRO can generate the Reports.

6.3.5 Lab Dashboard.
Figure 19 Lab Dashboard
Laboratory dashboard consists of:

• Lab staff can upload the documents.
• Lab staff can check for appointments
• Lab staff can search patient.
• Lab staff can check for activity log.
• Lab staff can view the Tests and its prices if needed.

6.3.6 Doctor Dashboard.
Figure 20 Doctor dashboard
Doctor dashboard consists of:

• Doctor an upload document.
• Doctor can view list of appointments.
• Doctor can generate the reports.
• Doctor can search patient by id or mobile number.
• Doctor can add visits.
• Doctor can view patient details.

6.3.7 Pharmacy Dashboard.
Figure 21 Pharmacy Dashboard
Pharmacy dashboard consists of:

• Pharmacy staff can add or delete medicine.
• Pharmacy staff can add or delete category.
• Pharmacy staff can generate invoice once the patient purchases the medicine.
• Pharmacy staff manage inventory.
• Pharmacy staff can view the prescription.
• Pharmacy staff can view sales graphs.
• Pharmacy staff can generate sales report.

6.3.7 Admin Dashboard.
Figure 22 Admin dashboard
Admin dashboard consists of:

• Admin as the complete control of the system.
• Admin can Manage all the users adding or deleting them.
• Admin have can provide permission to users.
• Admin can view graphs.

7. Testing
Testing is the process used identify the error in the program and check the completeness,
correctness, security and quality of developed Application.
7.1 Test cases for login page
Sl. No Input Excepted output Actual Output Status
Valid Credentials Opens the Opens the

1. Success
(User-id and password) Dashboard page Dashboard page
Invalid Credentials
2. (invalid user-id and Error message Error message Success
password)
Field is empty Field is empty

3. Empty User-id field Success
fill it. fill it.
Field is empty Field is empty

4. Empty Password field Success
fill it. fill it.
Table 7 test case table

7.2 Testing for other cases
Sl. No Input Test Description Output
Logouts from particular

Logouts from particular user
1. Click on logout Session and redirects to
type
home page
Takes the response and

2. Click on Submit Entering details
submits
Points to the required

Not entering the details of
3. Click on Submit field. Response is not
required field
submitted
Click on Drop down

4. Selecting data Data is displayed
list
Table 8 other test cases

8. Business Model
Figure 23 Business model

Edited in (https://edit.org/edit/all/whunc)

9. Impact on Society and Environment
The software application developed might have an impact on the society in a positive way as
described below.
• This project has no negative impact on either Environment or society.

• Providing Soft copy documents reduces the paper work which will be great impact on
environment.
• This helps the Hospital staff and patients to carry out all the work related to hospital in
an easy way with less time consuming.
• It helps to provides good quality and fast service.
• Patient able to get the reports whenever is required need to give time to travel to the
hospital.

10. Team Details
Team consists of the Team lead, Sharath Raj k who is the head of the Mobility softtech
company. He is responsible in assigning the tasks to be performed, during the course of the
project. He also gives guidance about how to carry out the task.
Name – Kushal S L
Designation – Front end development
Roles and responsibility: I Have played a major role in implementation of the User Interface
design of the various modules in the project development.
Name - Akhil
Roles and responsibility: He Worked as a back-end developer played a major role in

implementation of the Server-Side connectivity.
Name - Ajay
Roles and responsibility: He Worked as a back-end developer played a major role in

implementation of the Database project development.

11. Conclusion
The project's objective is to provide management, which is supervised by the hospital, with
something like a system that allowed them to reduce manual operations. Manually able to keep
track of all records and actions, as well as their paper records, is time-consuming and error-
prone. It is both difficult especially. The daily rise in increase in the total number of visitors to
hospitals make keeping records and documents uneconomical and technically impossible. All
of these records must be recorded and maintained, which is wasteful and unreliable. This
technology was created to address all of the shortcomings of the previous system and to give a
comprehensive suite that would benefit both customers and hospital employees.

12. Future Enhancements
This web application has future enhancements,
• Additional Features in User Interface.

• System is not 100% complete there are other departments which needs to be Automated.

13. Bibliography
1. https://www.mobilitysofttech/about-us/
2. https://www.w3schools.com/bootstrap4/bootstrap_typography.asp
3. https://code.visualstudio.com/docs/editor/whyvscode
4. https://www.youtube.com/watch?v=CMk8xB90RpU
5. https://www.w3schools.com/bootstrap4/bootstrap_progressbars.asp
6. https://edit.org/edit/all/whunc

MCA
ORIGINALITY REPORT
2 %
SIMILARITY INDEX
1%
INTERNET SOURCES
0%
PUBLICATIONS
1%
STUDENT PAPERS
PRIMARY SOURCES
1
www.cis.ksu.edu
Internet Source <1 %
2
Submitted to University of Greenwich
Student Paper <1 %
3
Submitted to University of Huddersﬁeld
Student Paper <1 %
4
Submitted to Guru Jambheshwar University of
Science & Technology
<1 %
Student Paper
5
www.securechange.eu
Internet Source <1 %
Exclude quotes On Exclude matches Oﬀ

Exclude bibliography On

Kushal S L 1BF18MCA12 Final Report

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Kushal S L 1BF18MCA12 Final Report

Uploaded by

Copyright:

Available Formats

Integrated Hospital Web Application

In partial fulfilment for the award of the degree of

B.M.S. COLLEGE OF ENGINEERING

In partial fulfilment for the award of the degree of

B.M.S. COLLEGE OF ENGINEERING

Department of Computer Application-BMSCE Page 1

Department of Computer Application-BMSCE Page 2

6.3.7 Admin Dashboard. .................................................................................................. 39

Department of Computer Application-BMSCE Page 3

Table 1 Hardware requirement – Development side.................................................................. 9

Figure 1 Mobility Sofftech Logo ............................................................................................. 11

Department of Computer Application-BMSCE Page 4

1.1 Project description.

Department of Computer Application-BMSCE Page 5

1.3 Objective and Scope

• To build an integrated hospital web application.

1.4 Literature Survey

1.4.1.1 Existing System

multiple colour combinations which makes the website more complex.

Department of Computer Application-BMSCE Page 6

1.4.1.2 Proposed System

1.5 Problem Statement

Its goal would be to provide limited, high-reliability mechanization of existing model.

Department of Computer Application-BMSCE Page 7

Department of Computer Application-BMSCE Page 8

1.6 Hardware and Software Requirements

Table 1 Hardware requirement – Development side

Front-End Boostrap4, HTML5, CSS3

Data Base Mongo DB 4.4.2

Server-side Node JS 14.15.5

Code Editor VS Code 1.53.2

Table 2 Software requirement – Development side

Department of Computer Application-BMSCE Page 9

1.6.2 Deployment side

Hard Disk Minimum 256 GB

Table 3 Hardware requirement – Deployment side

1.6.2.2 Software Requirements

Operating System Windows 7 or above version

Google Chrome 85.0 or above /

Table 4 Software requirement – Deployment side

Department of Computer Application-BMSCE Page 10

1.7 Company Profile

Figure 1 Mobility Softtech Logo

Department of Computer Application-BMSCE Page 11

2.1.1 Technical Feasibility

2.1.2 Economical Feasibility

Department of Computer Application-BMSCE Page 12

2.1.3 Behavioural Feasibility

Department of Computer Application-BMSCE Page 13

3.1 Project Schedule

Project Integrated hospital web application

Project Manger Sharath Raj K

Start date 05/03/2021

End date 24/07/2021

Overall Progress 100%

3.2 Gaant Chart

Figure 2 Gaant Char

Department of Computer Application-BMSCE Page 14

4. Software Requirement Specification

• This application helps the Patients to get the reports instantly.

• Organizing the information related to the Hospital work flow.

• More the Automation less the man power.

• Managing Lab and Pharmacy made easy.