CLOUD BASED INTERCOM COMMUNICATION FOR HOSPITAL

MEDICAL ERP.
1.2 Project Introduction

This hospital has required a system that maintains its Hospital ERP as well as keeps the record
of the Hospital in database. This software manage all information about patient name,patient
address,doctore information,staff information etc. it also store daily imformation of patient
Which is done by doctore. Also store information about billing , finaly it calcluate total bill of
patient .Hospital are the essential part of our lives, providing best medical facilities to people
suffering from various ailments, which may be due to change in climatic conditions, increased
work-load, emotional trauma stress etc. It is necessary for the hospitals to keep track of its day-
to-day activities & records of its patients, doctors, nurses, ward boys and other staff personals
that keep the hospital running smoothly & successfully.

But keeping track of all the activities and their records on paper is very cumbersome and error
prone. It also is very inefficient and a time-consuming process Observing the continuous
increase in population and number of people visiting the hospital. Recording and maintaining
all these records is highly unreliable, inefficient and error-prone. It is also not economically &
technically feasible to maintain these records on paper. Thus keeping the working of the
manual system as the basis of our project. We have developed an automated version of the
manual system, named as “Hospital Management System”. The main aim of our project is to
provide a paper-less hospital up to 90%. It also aims at providing low-cost reliable automation
of the existing systems. The system also provides excellent security of data at every level of
user-system interaction and also provides robust & reliable storage and backup facilities.

1.3 Existing System

 In existing System Admin manage all the data manually regarding the entire department,
patients, wards and other information.
 In existing System there is no any login for Admin, Doctor, patient and the staff.
 Traditional and reports are handled manually.
 If you want to search any record regarding any patient in any department then it’s very
difficult to manage.
  In manual system maintenance is very high.
 In old system there is store any reports against doctor and the customer

2. Proposed System:

The project “Hospital ERP” is aimed to develop to maintain the day –to-day state of
admission/discharge of patients, list of doctors, reports generation, and etc. It is designed to
achieve the following objectives:

1. To computerize all details regarding patient details & hospital details.

2. Scheduling the appointment of patient with doctors to make it convenient for both.

3. Scheduling the services of specialized doctors and emergency properly so that facilities

provided by hospital are fully utilized in effective and efficient manner.

4. If the medical store issues medicines to patients, it should reduce the stock status of the

medical store and vice-versa.

5. It should be able to handle the test reports of patients conducted in the pathology lab

of the hospital.

6. The inventory should be updated automatically whenever a transaction is made.

7. The information of the patients should be kept up to date and there record should be

kept in the system for historical purposes.

2.1 Assumptions & Dependencies

 The users have sufficient knowledge of computers.

 The users know the English language, as the user interface will be provided in English
 The registration of the Doctor, Patient and Staff is managed by the Administrator.
 The Doctor, Patient, Staff and administrator must have proper login id and password so
that only authorized have proper access to the system.
 Doctor, Patient and Staff details are stored in centralized database.
 The higher authority is responsible for updating database with proper information.With
the help of this system, communication is carried out through notifications between
customer and higher authority of system.
 With proper login, it will not misused by external or other person.
 With the help of this site authorised member can login and verify as per the login ID
stored in database.
 The backup of the database must be stored by the administrator.

2.2 Non Functional Requirement

 Availability : The system will be available 24*7*365
 Capacity: Any time you can use the system within a day and the system will able to
generate same results each time.
 Throughput: The system performs the speedy operations and has very less throughput
time.
 Security: Only users of the system can have the specified access to the system.
2.3 Scope

 The proposed software product is the Hospital ERP.

 The system will be used in any Hospital, Clinic, Dispensary or Pathology labs in any
Hospital, Clinic, Dispensary or Pathology labs to get the information from the patients
and then storing that data for future usage
 The current system in use is a paper-based system.
 It is too slow and cannot provide updated lists of patients within a reasonable
timeframe.
 The intentions of the system are to reduce over-time pay and increase the number of
patients that can be treated accurately.
 Requirements statements in this document are both functional and non-functional.
 Provide secure login to Doctor, Patient and the staff.
 Patient verifies prescription and the treatment status through his/her login.
 Save history of all transaction.
 Doctor also main all data regarding his/her own assign department.
 SMS and Email Management.
 System available 24*7 hours.
 Staff also maintains his/her own department data through this system.
 All Date wise Report Save in Centralized Database.
 Admin can add Doctor, Patient and the Staff details.
 Admin can also add the Medicine Details.
 Admin can create the Appointment schedule and time off schedule.
 Admin can be able to view System generated reports.
 Admin can also create the prescriptions.
 Also Maintain various Lab Test.
 Report generation.
2.4 Module Specification
The system contains different modules as:

1. Admin

a. Add New Doctor Registration

In this module admin can do the registration of the Doctor. Afterwards doctor get the user
name and the password though registered email ID. Doctor can access his/her own panel by
using this user name and the password. Here Admin can add the multiple Doctors.

b. Add New Patient Registration

In this module admin can do the registration of the Patient. Afterwards Patient get the user
name and the password though registered email ID. Patient can access his/her own panel by
using this user name and the password. Here Admin can add the multiple Patients.

c. Add New Staff Registration

In this module admin can do the registration of the Staff. Afterwards Staff get the user name
and the password though registered email ID. Staff can access his/her own panel by using this
user name and the password. Here Admin can add the multiple Staff.
E.g Accountant, Inventory Manager.

d. Add New Lab Test

This option is very useful to add the new Lab test in the Hospital ERP like Urine Test, Blood Test.
Afterward this test will be accessible to the all doctor and the patient.

g. Add New Visiting Doctor Registration

In this module admin can do the registration of the Visiting Doctor. Afterwards Visiting Doctor
get the user name and the password though registered email ID. Visiting Doctor can access
his/her own panel by using this user name and the password. Here Admin can add the multiple
Visiting Doctor.

h. Add New Branch

Here Admin can add the New Branch registration from here. Admin can also add the new
branch website details. Afterwards this branch is accessible through the centralise database.

i. Add New Designation

Admin can add the new designation like Doctor, Patient, Ward Boy, Nurses, and Receptionist.

j. Add New Speciality

This option is very useful to add the new speciality in the Hospital ERP.

k. Add New Disease

Here admin can add the list of the Diseases in detail along with all the information details.

l. Add New Department

This option is very useful to add the new department in the Hospital ERP software. Afterward
this department will be accessible to all other users.

m. Add New Ward

This option is very useful to add the new ward in the Hospital ERP software. Afterward this
ward will be accessible to all other users. The ward will be add in any certain Department.

2. Doctor-
a. View and Edit Profile

In this module Doctor can View and Edit the Profile.

a. Add Appointment Schedule

In this module Doctor can create the appointment schedule afterward this schedule will be
display to the entire patient for book the appointment slot. Here doctor can see the all created
appointment lists.
a. Add Time Off

In this module Doctor can create the Time off schedule afterward this schedule will be display
to the entire patient for book the appointment slot. Here doctor can see the all created Time
off lists.

a. Create Prescription

In this module Doctor can create the prescription it will be display in patient panel and it will be
very useful for the patient.
a. Assign Lab Test

In this module Doctor can assign the lab test to the patient afterwards doctor collect the lab
test status.
a. View and check all Lab Test Result.

Through this module Doctor can see the assign lab test result.
a. Add Medicine

In this module Doctor can add the medicine in the ERP portal.
a. Create Gallery

Through this menu tab admin can upload the photo gallery. Which will be able to see all the
user of the system?
a. View Patient Report

In this module doctor can see the complete patient report. Doctor also able to see the patient
report date wise.
a. View Medicine Report

In this module doctor can see the complete Medicine report. Doctor also able to see the
Medicine report date wise.
 3. Patient-

a. View and Edit Profile

In this module Patient can View and Edit the Profile.

b. Create Appointment
In this module patient can create the appointment afterward this appointment will be display
to the Doctor.

c. View and Search Appointment

Here patient can search and view all the appointment date wise.

d. View Treatment Status and the Prescription Report-

In this module patient can see the Treatment Status and the Prescription Report date wise.

e. View Staff and the Doctor-

Here patient can search and view all the staff and the doctor in his/her department only.

4. Staff

a. View and Edit Profile

In this module Patient can View and Edit the Profile.

b. Bill Generation
In this module staff can create the bill against the patient and the staff department wise and
the ward wise.

c. Salary Management
Staffs also maintain the salary management of the entire department.

d. Medicine Stock Management

In this module staff can maintain the medicine stock management with its expiry date.

e. Inventory Management
Through this module Staff can maintain the Inventory management regarding all the things
which is used in the hospital.

f. Maintain Receipt Book

In this module staff can maintain the receipt book data date wise.

g. Maintain Balance sheet

In this module staff can maintain the Balance sheet data date wise.
2.5 Operational Environments

HARDWARE SPECIFICATION

Dual Core
PROCESSOR

OPERATING SYSTEM Windows

RAM 1 GB

H.D.D 40GB or more

SOFTWARE SPECIFICATION

Operating System Windows XP/Later

Internet Explorer-6/Later
Web Browser
Mozilla Firefox
 Technology JAVAS

Database Mysql

Supportive Technology Ajax, JavaScript, JQuery,Html5,CSS3

3. Methodology and Fact Finding Methods

Before starting the actual development of the system, system analyst collects the important
information about manual system from the user department. In order to collect this information,
system analyst prefers any of the following fact finding techniques.

 Interview
 Questionnaire
 Record review
 Observation

 Interview:
Analysts use interview techniques to collect information of system from individuals or
smaller groups. The respondent is generally a current user of existing system or potential
proposed system. This technique requires some more time than the other fact finding
techniques. It is important to remember that the respondent & analyst should conserve only
during the interview. Interview techniques allow analyst to discover the area of
misunderstanding & unrealized expectation & even indicate of resistance to the proposed
system.

 Questionnaire:
 The use of questionnaire allows the analyst to collect the information about various aspects
of system, from large number of person. The use of standardized question format can yield
more reliable anonymity for respondent which can lead to more honest responses.

 Record review:
Many kinds of records & reports can provide analyst valuable information ion & operation.
In record review analyst examines information that has system & user.
Record exception can be performed at the beginning of the study as an introduction or later
in the study as a basis for comparing actual operation with for the record indicates should be
happening.

 Observation:
Observation allows analysts to collect the information, they cannot obtain by other fact
finding techniques. Thorough observation analyst can obtain first information about how
activities are carried out. This method is most useful when analyst need to actually observe
how documents are handled, how processes are carried out & weather the specific steps are
actually followed.

3.1 Feasibility Study and Tools used for Analysis

A Project feasibility study is an exercise that involves documenting each of the potential
solution to a particular business problem or opportunity. Once the problem is clearly
understood, the next step is to conduct feasibility study, which is high-level capsule version
of the entered systems and design process.
The objective is to determine whether or not the proposed system is feasible. The three tests
of feasibility have been carried out.

 Technical Feasibility
 Economical Feasibility
 Operational Feasibility
TECHNICAL FEASIBILITY

 In Technical Feasibility study, one has to test whether the proposed system can be
developed using new or existing technology or not.
 It is decided after study that to implement the proposed system using .net technology as
the existing system is manual i.e. paper worknot based on any technology.
 It is evident that the necessary hardware and software are available for development and
implementation of the proposed system. Hence, the solution is technically feasible.

ECONOMICAL FEASIBILITY

 As part of this, the costs and benefits associated with the proposed system compared and
the project is economically feasible only if tangible or intangible benefits outweigh costs.
 The system development costs will be significant. So the proposed system is
economically feasible.

OPERATIONAL FEASIBILITY

 It is a standard that ensures interoperability without stifling competition and innovation

among users, to the benefit of the public both in terms of cost and service quality.
 The proposed system is acceptable to users. So the proposed system is operationally
feasible.