Hospital mangement system report file

1
HOSPITAL MANAGEMENT SYSTEM
A
Report Submitted
In Partial Fulfillment of the Requirements
For the Degree of
BACHELOR OF TECHNOLOGY
in
Computer Science
by
Nausheen Hasan(11104320761)
Under the supervision of
Amandeep Kaur
Assistant Professor
BBD University, Lucknow
School of Engineering
BABU BANARASI DAS UNIVERSITY
LUCKNOW
May, 2015

2
CERTIFICATE
It is certified that the work contained in this Project entitled “Hospital Management
System”by NausheenHasan for theaward of Bachelor of Technology from Babu Banarasi Das
University has been carried out under my supervision.
Amandeep Kaur Reena Srivastava
Computer Science Head, Computer Science
School of Engineering School of Engineering
BBD University BBD University
Lucknow(U.P) Lucknow(U.P)
Date:

3
ABSTRACT
My project Hospital Management System include registration of patients,storing their detail into
the system and also computerized .My software has the facility to give a unique id for every
patient and store the detail of every patient and doctor automatically. User can search availability
of a doctor and the details of a patient using the id.
The hospital Management System can be enter using a user name and
password. It is accessible either by administrator or receptionist. Only they can add the data into
the database. The data can be retrieved easily. The interface is very user friendly.

4
ACKNOWLEDGEMENT
Whenever a module of work is completed successfully, a source of inspiration and
guidance is always there for the student. I, hereby take the opportunity to thank those entire
people who helped me in many different ways.
First and foremost, I am grateful to my thesis guide Assistant professor/AmandeepKaur,
B.B.D. University, for showing faith in my capability and providing able guidance and his
generosity and advice extended to me throughout my thesis.
Last, but not least I would like to thank all my faculty and my friends for helping me in all
measure of life and for their kind cooperation and moral support.
TABLE OF CONTENTS
Page No.
Certificate....................................................................................................................ii
Abstract ......................................................................................................................iii
Acknowledgment........................................................................................................iv
List of Figure ............................................................................................................vii
List of Table ...............................................................................................................ix
Nomenclature .............................................................................................................x
Chapter 1: Introduction p-p
1.1 Introduction p
1.2 Objective p
1.3 Problem Definition
1.4 Project Report Layout
1.5 Summary

5
Chapter 2: Requirement Analysis p-p
2.1 Introduction
2.2 Feasibility Study
2.3 Functional Requirement
2.4 Non-Functional Requirement
2.5 Software Requirement Specification
2.6 Summary
Chapter 3: Software Designp-p
3.1 Introduction
3.2 Data Flow Diagrams
3.3 Use Case Diagrams
3.4 ER Diagram
3.5 Interface Design
3.6 Summary
Chapter 4: Software Code
4.1 Introduction
4.2 Code
4.3 Summary
Chapter 5: Software Interface
5.1 Introduction
5.2 Snapshots
5.3 Summary
Chapter 6: Test procedure and Test Cases
6.1 Introduction
6.2 Test Procedure
6.3 Test Cases
6.4 Summary
Chapter7: Conclusion and Scope of future Work
7.1 Conclusion
7.2 Scope of Future Work
Referencep-p

6
CHAPTER-1
INTRODUCTION
1.1Introduction
The project of Hospital Management System include the registration of patient and the doctor.
The management of the hospital concerned with the increacing effort in keeping the record of
patient and recording their activities. The hospital also keep the information of the employees.
Management and information system, which may keep the record of each patient, employee and
medicine. The hospital treats both indoor and outdoor patients. It has to maintain full information
of the indoor patients as well as outdoor patients for the purpose of hitorical use.
The software has the facility to give a unique id to the every patient and
every doctor and store the detail of the patients and doctors in the system. The user can search
the availability of the doctor and detail of the patient by using the particualr id. The hospital
management system can be entered using the user name and the password. It is accessible either
by administators or receptionist. Only they can add the data with the database. The data can be
reterived easily. The interface is user friendly.

7
Help human hospital has a group of soial and profeesional people as director
and manager in its management, who provide a personal as well as professinol touch to the over
all working of the hospital. Proper guideliness and objectives are laid down for every process and
section of the hospital which result ensuring statisfation of the patient.

8
1.2 Objectives
The software is for the automation of hospital management.
It maintain two level of user :-
1. Administator level
2. User level
The Software include
 Maintaing patient detail.
 Providing and maintaing all kind of test for a patient.
 Billing and report generation.
 Maintainance record of indoor and outdoor patient.
 Result of test will be automatically updated in the database.
 User or administator cab search patient’s record by his/her name or their registration
date.
 Information about the patient is done by just writing patient’s name and id whenever
the patient comes up the information in the store freshly.
 Information about the doctor is also done by writing the name of the doctor and
his/her id.

9
1.3 Problem Defination
1. Lack of immediate retrievals: -The information is very difficult to retrieve and to
find particular information like- E.g. - To find out about the patient’s history, the user
has to go through various registers. This results in inconvenience and wastage of
time.
2.Lack of immediate information storage: - The information generated by various
transactions takes time and efforts to be stored at right place.
3. Lack of prompt updating: - Various changes to information like patient details or
immunization details of child are difficult to make as paper work is involved.
4. Error prone manual calculation: - Manual calculations are error prone and take a
lot of time this may result in incorrect information. For example calculation of
patient’s bill based on various treatments.
5. Preparation of accurate and promptreports: - This becomes a difficult task as
information is difficult to collect from various registors.

10
1.4 ProjectReport Layout
 Login Module - This module record only user id and password. This module
is only used by adminstator or receptionist.
 Patient Module – It keeps track of all details of both in-patient and out-
patient. Patient id, name, date of birth, gender, city name, state name, phone
number, doctor id are entered in a form and stored for the future refrence.
Also particular patient detail can be view in the table using a separate form
with an attribute patient id.
 Doctor Module – It keeps track of all details of doctors. Doctor id will be
automatically genrated by application. Doctor name, date of birth,
professional detail like qualification, specialist, desgination, prehospital,
salary, work experince, city’s name, state’s name, phone number and email id
are enterd in a form which has to patient to find the particular doctor.
Particular doctor detail can be viewed in the table using a separate form with
an attribute doctor id.
 Billing Module- The patient billing module handles all type of billing for long
term care. This module facilities cashier and billing operation for different
categories of patient like out- patient and in- patient. It provide automatic
posting of charges related to different services like bed charges, lab tests
conducted, medicines issued, consultant’s fee, food, beverage and telephone
charges etc.
 Medicine Module – Medician id, medician name, batch number, Mfd date,
expiry date, company name, desciprtion, price, stock ,stock end are entered in
a form which help the receptionst to provide the medicine to the particular
patient.

11
1.5 Summary
The hospital management system is designed for any hospital to replace their
existing manual,paper based system. The help human hospital is used to
provide the patient information,doctor information and the medicine
information. These services are provided in an efficient,cost effective manner
with the goal of reducing the time and more complicated paper work.
Now in the next chapter we are going to describe about feasibility
study,functional and non-functional requirement of the system.Feasibility
study is the test of system proposal according to its work ability,impact of the
organization,ability to meet the need and effection use of resources.

12
CHAPTER-2
REQUIREMENT ANALYSIS
2.1 Introduction
The software requirement engineering determines the functional or non-functional
requirements for engineering software. The requirements engineering is the first stage
of any software project development. It is the process of determining functions of the
software systems. The process encompasses all activities concerned with the
requirements eliciting, analyzing, documenting, validating and managing software or
systems. In requirement engineering the real world goals are explored and established
for the software system that is being developed. Before any project, the requirements of
the user are collected to accomplish the user’s task. The first stage of requirements
engineering process is requirement gathering. Unfortunately, complete requirements
cannot be perceived at a given point of time. The reason is that they evolve with time
mostly they are observed after the system deployment. This evolutionary nature of
requirements poses difficulties in almost every phase of software development process.
With every change in requirements, the system analyst is required to recollect the
changed or new requirements, then analyze and document them. Consequently in all the
steps of software development human intervention is required for the changed
requirements.
This paper proposes a model of software intelligent agent that automatically senses and
gathers user’s new requirements and generates a report of it and finally sends it to the
developer. This model of software intelligent agent gathers therequirement through
various learning methods. The intelligent agents can either be embedded with HMS or
installed at user’s site. During the course of HMS operation, the intelligent agents sense
new requirements from user’s operations and use them to evolve HMS dynamically by
adding functionalities that satisfies the newly captured requirements.
System requirement –
Minimum Hardware Required:-
o Processor –Intel® Atom™ Processor N2600
(1M Cache, 1.6 GHz)
o RAM - 2.0GB
o HDD -1 GB ( For installing)
Software Required:-
o Operating system window 7 Ultimate SPI
o Window installer 3.5
o Microsoft .Net Framework 4
o Microsoft SQL Server 2005

13
2.2 Feasibility Study
Depending on the results of the initial investigation the survey is now expanded to amore
detailed feasibility study. “FEASIBILITY STUDY” is a test of system proposalaccording to its
workability, impact of the organization, ability to meet needs andeffective use of the resources. It
focuses on these major questions:
 What are the user’s demonstrable needs and how does a candidate system meet
them?
 What resources are available for given candidate system?
 What are the likely impacts of the candidate system on the organization?
 Whether it is worth to solve the problem?
 During feasibility analysis for this project, following primary areas of interest
are to beconsidered.
 Investigation and generating ideas about a new system does this.
Steps in feasibility analysis :Eight steps involved in the feasibility analysis are:
1) Form a project team and appoint a project leader.
2) Prepare system flowcharts.
3) Enumerate potential proposed system.
4) Define and identify characteristics of proposed system.
5) Determine and evaluate performance and cost effective of each proposed system.
6) Weight system performance and cost data.
7) Select the best-proposed system.
8) Prepare and report final project directive to management.
Technical feasibility
A study of resource availability that may affect the ability to achieve an acceptablesystem. This
evaluation determines whether the technology needed for the proposedsystem is available or not.

14
1) Can the work for the project be done with current equipment existing software
technology & available personal?
2) Can the system be upgraded if developed?
3) If new technology is needed then what can be developed?
4) This is concerned with specifying equipment and software that will successfully
satisfy the user requirement.
The technical needs of the systemmay include:
Front-end and back-end selection
An important issue for the development of a project is the selection of suitable front-endand
back-end. When we decided to develop the project we went through an extensivestudy to
determine the most suitable platform that suits the needs of the organization aswell as helps in
development of the project.The aspects of our study included the following factors.
Front-end selection:
1) It must have a graphical user interface that assists employees that are not from IT
background.
2) Scalability and extensibility.
3) Flexibility.
4) Robustness.
5) According to the organization requirement and the culture.
6) Must provide excellent reporting features with good printing support.
7) Platform independent.
8) Easy to debug and maintain.
9) Event driven programming facility.
10) Front end must support some popular back end like Ms Access. According to the above
stated features we selected VB6.0 as the front-end for developing our project. Hospital
Management System
Back-end Selection:

15
1) Multiple user support.
2) Efficient data handling.
3) Provide inherent features for security.
4) Efficient data retrieval and maintenance.
5) Stored procedures.
6) Popularity.
7) Operating System compatible.
8) Easy to install.
9) Various drivers must be available.
10) Easy to implant with the Front-end.
According to above stated features we selected Ms-Access as the backend.The technical
feasibility is frequently the most difficult area encountered at this stage. Itis essential that the
process of analysis and definition be conducted in parallel with an assessment to technical
feasibility. It centers on the existing computer system(hardware, software etc.) and to what
extent it can support the proposed system.
Economicalfeasibility
Economic justification is generally the “Bottom Line” consideration for most systems.Economic
justification includes a broad range of concerns that includes cost benefit analysis. In this we
weight the cost and the benefits associated with the candidate system and if it suits the basic
purpose of the organization i.e. profit making, the project is making to the analysis and design
phase.The financial and the economic questions during the preliminary investigation areverified
to estimate the following:
1) The cost to conduct a full system investigation.
2) The cost of hardware and software for the class of application being considered.
3) The benefits in the form of reduced cost.
4) The proposed system will give the minute information, as a result the performance is
improved which in turn may be expected to provide increased profits.

16
5) This feasibility checks whether the system can be developed with the available funds.
The Hospital Management System does not require enormous amount of money to be
developed. This can be done economically if planned judicially, so it is economically
feasible. The cost of project depends upon the number of manhours required.
Operational Feasibility
It is mainly related to human organizations and political aspects. The points to beconsidered are:
1) What changes will be brought with the system?
2) What organization structures are disturbed?
3) What new skills will be required? Do the existing staff members have these skills? If not,
can they be trained in due course of time?
4) The system is operationally feasible as it very easy for the End users to operate it. It only
needs basic information about Windows platform.
Schedule feasibility
Time evaluation is the most important consideration in the development of project. Thetime
schedule required for the developed of this project is very important since moredevelopment
time effect machine time, cost and cause delay in the development ofother systems.
A reliable Hospital Management System can be developed in the considerable amountof time.

17
2.2 Functional Requirement
Registration
 Add patients- The hospital management system shall allow front-desk staff to
add new patient to the system.
 Assign Id- The hospital management shall allow front desk staff to give each
patient a id and add it to the patient’s record. This id shall be used by the patient
through out his/her stay in hospital.
Report generation
 Patients information- The hospital management system shall generate report on
patient about the following information like patient’s name, patient’ phone
number and doctor name which was assigned.
Database
 Patient Mandatory Information- Each patient shall have the following
mandatory information like first name, last name, phone number , address, city,
patient number.
 Update patient information- It shall allow the user to update any of the patient
information as described in SRS 007.
Technical issue
 Database- The system shall the MySQL Database which is open source and free.
 Operating System- Operating System window 7 ultimate SPI.

19
2.3 Non Functional Requirement
Performance
 Response time – This system shall give response in one second after checking the
patient information.
 User Interface – The user interface screen shall report within a 5 sec.
 Conformity – The system must conform to the Microsoft Accessibility.

20
2.4 Software Requirement Specification
The SRS is produced at the culmination of the analysis task. The function and
performance allocated to software as part of the system engineering and redefine by
establishing a complete information description, a detail functional description, a
representation of system behaviour indication of performance requirement and design
constrains, appropriate validation criteria and the other information related to the
requirement.
The SRS is technical specification requirement of the Hospital Management System.
This specification describe what the proposed system should do without describing how
it will do it. It describe complete external behaviour of proposed system.
Purpose- The main purpose of our system is to make hospital task easy and is to develop
software that replaces the manual hospital system into automated hospital management
system. This document serves as the unambiguous guide for the developer of this
software system.
Scope-This document only cover the requirement specification for the hospital
management system. This document does not provide any references in the other
component of the hospital management system.

21
2.5 Summary
In this chapter we describe about the process of determining functions of the software
systems. The process encompasses all activities concerned with the requirements
eliciting, analyzing, documenting, validating and managing software or systems.Her we
discuss about the feasiability study,funtional and non functional requirement of the
hospital management system. FEASIBILITY STUDY is a test of system
proposalaccording to its workability, impact of the organization, ability to meet needs
andeffective use of the resources. And now in next we study about software design and
flow diagram of hospital management system. Software design aims to identify the
modules in the system, the specification of those module and how they interact with each
other to produce the result. The goal of the design is to produce a model that can be used
later to build the system. The produce model is called the design of the system.

22
CHAPTER-3
SOFTWARE DESIGN
3.1 Introduction
The purpose of the design phase is to plan a solution for problem specified by the
requirement. System design aim to identify the module the should be in the system. The
specification of module and how to interact with each other to produce the result .The
goal of the result process to produce the model that can be used later to build that
system. The produced model is called design of the system.
System design is the process of defining the architecture ,component ,module, interface
and data for a system to satisfy specified requirement. Normally design proceeds in two
state-
 Physical Design
 Database Design
Physical design – T he physical design is a graphical representation of the
system showing the system’s internal and external entities and flow of data into
and out of these entities. An internal entity is an entity within the system that
transform the data. To represent the physical design of the system we use
diagram like data flow diagram and use case diagram.
Database design- It is the process of producing of detail data model of a data
base. This logical data model contains all the needed logical and physical design
choices and physical storage parameters needed to generate a design in data
definition language, which can be used to create data base.

23
3.2 Data flow diagrams
The data flow diagram is a graphical representation of the flow of the data
through an information system. Data flow diagram are used by system analysis to
design information processing system but also as a way to model whole
organisation. The main merit of DFD is that it can provide an overview of what
data a system would process, what information of data are done, which data are
stored and which data is used and where the result is flowed.
Symbol Description
Process
This entity describe the process. A process
shows the transformation of the data flows
Within the system.
External entity
This is a external entity.
Data flows This is a data flow entity. A data flow
shows flow of information from source to
destination. A line shows the direction of
flow.
Data base This is data base entity.

29
3.5 Interface Design
There are many factors that must be considered when designing the user interface of a software
because the user must be able to interact with the system in away that the system will understand
whatever the input given by the user. Therefore, the quality of the interface and software in
general must pass the us ability testing standard. Some usability factors, such as fit for use, ease
of learning, task efficiency, ease to remember, subjective satisfaction and under standabilitybut
all be put into consideration when designing the user interface. .
The application will have a user friendly and menu based interface,. Following
screens will be provided
 A Login Screen for entering user name, password , administrator will be provided.
Access to different screen will be based upon the role of the user.
 A form for search the details of patient.
 The form for creating a new patient record will contain text field where the Patient id
will be generated automatically and the rest of the detail will have to be filled up.
 A form the creating a new doctor record will contain text field where the Doctor id will
be generated automatically and the rest of the details will have to filled up.
 The form to produce a bill create fields such as Patient Id, Doctor’s charges and the
medicine charges.

30
3.7Summary
In this chapter we study about the software design .Software design aims to identify the module
that should be in the system .Software design is the process of defining the architecture ,
component, module , interface and data for a system to satisfy to specified requirement. We also
discuss about the data flow diagram in which we show 0- level DFD, 1-level DFD, 2-level DFD,
3-level DFD and the ER diagram of hospital management system. DFD is graphical
representation of the flow of the data through an information system.
Now in the next chapter we have to study about the test procedure and the test case.
Where we describe about the all type of testing which we used in the our system. Test procedure
helps in assuring software quality. It ensure that doctor can access their id any time and patient
can check or update his treatment detail .Testing is the process of executing a program with the
intention of finding error.`

31
CHAPTER-6
TEST PROCEDURE AND TEST CASES
6.1 Introduction
Test procedure and test cases plays a critical role in assuring software quality. It serves the
purpose of quality assurance, verification and validation. Studies indicate that 50% of cost for
software development is given to testing. Basically testing procedure is an investigation
conducted to provide information about quality of product or services. It can also provide an
objective view of software to allow the user to understand the risk of the system. We use this
technique to find out software bugs or error in hospital management system. It ensures that
doctors can access their id any time and patient can check or update his treatment detail any time.
Unit testing, integration testing , white and black box testing etc are used in hospital management
system.
A test cases is a set of conditions under which a tester will determine the features of
system or software is working well or not. Generation of test cases is a time consuming process.
Hence, automation is an important issue. There are two main approaches to generate test cases -
 Generating test cases from requirements and design specification.
 Using source code .
In order to fully test that all the requirement of an system are met, there must be atleast two test
cases that is one positive test and one negative test. We can define test cases as-
Formal test cases- In formal test case, test case is characterized by a known input and by an
expected output, which is worked out before the test is executed. Formal testing is done by
testing team formally.
Informal test cases- In informal test cases, testing is done by a coder before giving file to a
testing team. No procedure is used in informal testing

32
6.2 Testprocedure
Test procedure helps in assuring software quality. The purpose of test procedure is a quality
assurance, verification and validation. Basically testing procedure is an investigation conducted
to provide information about quality of product or services. It ensures that doctors can access
their id any time and patient can check or update his treatment detail any time. Testing is the
process of executing a program with the intention of finding errors. It is used to represent the
ultimate review of specification, design, coding. Different test conditions should be thoroughly
checked and the bugs detected should be fixed. Testing in hospital management system are
fallowed as –
1. Unit testing- Unit testing plays a crucial role in early phase of software testing life cycle
which helps in detection bugs; and once properly planned and executed, it reduces cost of
quality. However, if unit tests are not written well, or they are executed incorrectly, bugs go
through into the production phase. This oversight can cost a company thousands, if not
hundreds of thousands of dollars depending on the scale of the project.Unit testing needs a
deep expertise of looking into code with various perspectives such as Code coverage, Loop
coverage, Branch coverage, Condition coverage, and Fuzzing code to predict its expected
failure, predefined negative tests while developing code . This involves not just insights into
code, but a much required methodological approach towards testing the code for its afferent
and efferent coupling.
Testing Goal -Dots squares unit testing service goal is to catch as many bugs early in the
development as possible. This is achieved by writing accurate and quality unit tests, while at the
same time providing detailed documentation for the development process. This ensures that bugs
and inconsistencies we detect early in the development stage, can be re-factored by the
development team. We work intimately with your team to thoroughly ensure all project goals are
met on time and within budget.
Benefits of Unit Testing -
 Finding problems early -Unit tests find problems early in the development cycle.
 Facilitate change -Allows the programmer to re-factor code during the testing process and at
a later date, while making sure the module still works correctly.
 Simplify integration -By testing the parts of a program first and then testing the sum of its
parts, integration testing becomes much easier.
 Documentation -Developers looking to learn the result of a unit test can look at the unit test
documentation to gain a better understanding.
 Design-Each unit test can be seen as a design element specifying classes, methods, and
observable behaviors during the project life-cycle.
2. Integration testing - We normally do Integration after unit testing. Once all the individual
units are created and tested, we start combining those “Unit Tested” modules and start doing
the integrated testing. So the meaning of Integration testing is quite straight forward-

33
Integrate/combine the unit tested module one by one and test the behaviour as a combined
unit.
Testing goal -The main function or goal of Integration testing is to test the interfaces
between the units/modules. The individual modules are first tested in isolation. Once
themodules are unit tested, they are integrated one by one, till all the modules are integrated,
to check the combinational behaviour, and validate whether the requirements are
implemented correctly or not.
Here we should understand that, Integration testing does not happens at the end of the cycle,
rather it is conducted simultaneously with the development. So in most of the times all the
modules are not actually available to test and here is what the challenge comes to test something
which does not exist
There are fundamentally 2 approaches for doing Integration testing:
 Bottom up approach
 Top down approach.
Black box testing
Black Box testingis a software testing techniques in whichfunctionality of the software under
test (SUT) is tested without lookingat the internal code structure, implementation details and
knowledge of internal paths of the software. This type of testing is based entirely on the software
requirements and specifications.
Black box testing - Steps
Here are the generic steps followed to carry out any type of Black Box Testing.
 Initially requirements and specifications of the system are examined.
 Tester chooses valid inputs (positive test scenario) to check whether SUT processes them
correctly . Also some invalid inputs (negative test scenario) are chosen to verify that the
SUT is able to detect them.
 Tester determines expected outputs for all those inputs.
 Software tester constructs test cases with the selected inputs.
 The test cases are executed.
 Software tester compares the actual outputs with the expected outputs.
 Defects if any are fixed and re-tested.

34
Types of Black Box Testing
There are many types of Black Box Testing but following are the prominent ones -
 Functional testing - This black box testing type is related to functional requirements of a
system; it is done by software testers.
 Non-functional testing - This type of black box testing is not related to testing of a
specific functionality , but non-functional requirements such as performance, scalability,
usability.
 Regressiontesting - Regression testing is done after code fixes , upgrades or any other
system maintenance to check the new code has not affected the existing code.

35
CHAPTER-7
CONCLUSION AND SCOPE OF FUTURE WORK
7.1 Conclusion
The project Hospital management system is for computerizing the working in a hospital. The
software takes care of all the requirements of an average hospital and iscapable to provide easy
and effective storage of information related to patients that come up to the hospital. It is great
improvement over the manual system has speed up the process. The hospital managing system
thoroughly checked and tested with the data and thus is found reliable. The software takes care
of all the requirement of an average hospital and is capable to provide easy and efficient storage
of information related to patients that comes up to the hospital..
It generates test reports; provide prescription details including various tests, diet advice, and
medicines prescribed to patient and doctor. It also provides injection details and billing facility
on the basis of patient’s status whether it is an indoor or outdoor patient. The system also
provides the facility of backup as per the requirement.
The system is secure as a user can modify the information only after the proper
authentication. Chances of error are also eliminated to large extent. Computerization and
automation of the whole system helps in easy and fast access to the required information.. The
system is highly user friendly as appropriate message are provided to guide the user logged in.

36
7.2 Scope offuture Work
The hospital management system can enhance by including more facility like pharmacy system
for the stock details of medicine in pharmacy. Providing each future enable the users to include
more comment in the system.Although the project is complete in itself but as there is always a
future scope for improvement; the same applies to this software. The provision for getting
appointment from the doctor through Internet, i.e., Online Appointment facility can be added.
The doctor could view the requests from several patients and accordingly give the appointment if
possible.
Further, Mobile Application can be implemented to allow the patients to view their previous visit
details and get appointment from doctors through mobiles. Posting of employees from one
hospital to another can also be managed. Further, doctors can be given the provision to post their
articles on the website of hospital.It generates test reports; provide prescription details including
various tests, diet advice, and medicines prescribed to patient and doctor. It also provides
injection details and billing facility on the basis of patient’s status whether it is an indoor or
outdoor patient. The system also provides the facility of backup as per the requirement.

Hospital mangement system report file

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (19)

Similar to Hospital mangement system report file

Similar to Hospital mangement system report file (20)

Recently uploaded

Recently uploaded (20)

Hospital mangement system report file