Reqirement Specification Document FOR Hospital Management System

REQIREMENT SPECIFICATION DOCUMENT
FOR
HOSPITAL MANAGEMENT SYSTEM
TABLE OF CONTENTS
1. Introduction
1.1 Purpose
1.2 Scope
2. Glossary
3. User requirements specification

3.1 New patient registration
3.2 In patient management
3.3 Out patient management
4. System architecture
4.1 Hardware requirements
4.2 Software requirements
5. System requirements specification

5.1 Registration
5.2 In patient management
5.3 Out patient management
5.4 Billing
5.5 Pharmacy and lab facilities
6. System evolution
6.1 General Maintenance and Evolution
6.2 Need for Additional Functionalities
6.3 Future Technologies
6.4 Predicted Evolution
1. INTRODUCTION:
This automated system is mainly provided to facilitate the

easy management of the nursing home or the hospital. This system has to maintain the
database of doctors working in the hospital and the patients who are treated in that
particular hospital. This system includes the following scenario:
1. New patient registration
2. in patient management
3. out patient management
4. billing
5. pharmacy and lab facilities
1.1 Purpose
To provide an integrated solution for a hospital system which
1.helps in efficient management of the hospital
2.enhances patient care
3.improves work efficiency
4.enables the growth of hospital
1.2 Scope
The user will enter the patient information . This will include the
type of the patient (inpatient/outpatient and corporate/individual),and billing details . The
user will also have to select the laboratory tests done by the patient, the date of discharge
of the in patient . The user will have to be familiar with the billing module. If needed, the
user should be trained up to use this module. The user may be an administrator, nurse or a
cashier. It depends upon the particular hospital.
2. GLOSSARY
HMS – Hospital Management System
PDB – Patient Database
DDB- Doctor ‘s Database
3. USER REQUIREMENTS SPECIFICATION:
. The user may be an administrator, nurse or a receptionist. It depends upon the
particular hospital.
3.1 New Patient Registration
3.2 Out Patient Management

3.2 In Patient Management
4. SYSTEM ARCHITECTURE:
4.1 Hardware Requirements:
Since this implementation is essentially a user interface, there will be little to no

new hardware requirements. The main hardware requirements will be that of a
ordinary system .
4.2 Software Requirements:
The software requirements will be grouped into two categories: GUI and
Computational Software.
The GUI:
The GUI for the system will be a should a one or two form main interface with
separate smaller pop-up dialogs for interactions such as the registration as well as static
forms for in patient and out patient management and billing .On each form will be an
array of button, tabs, checks boxes, and/or radio buttons from that will allow the user to
customize the process of optimization and registration. To promote a platform
independent application, this GUI will be written in JAVA.
Computational Software:
The code that will parse the latest course schedule and then perform the
combinatorial mathematics on a set user selections to produces the optimized schedule
will be written in ANSI C++. The fact that this code will most likely be in pre-compiled
form upon delivery will eliminate the problem of portability.
5. SYSTEM REQUIREMENTS SPECIFICATION:
5.1 Registration
Function Registration
Description It provides each patient with a unique id for easy management
Inputs The details of the patient
Outputs Patient id
Pre-condition Shouldn’t have already registered
Post-condition Patient recognition card
Destination Add the details to the DB
5.2 out patient management

Function Out patient management
Description It manages the services provided to out patients
Inputs Complaints
History
Diagnosis
Outputs Advice
Medicine
Next visit
Pre-condition Should be an existing patient
Post-condition None
5.3 in patient management

Function In patient management
Description It deals with complete treatment and service to the patient
Inputs Patient’s investigation report
Outputs Patient’s daily report
Pre-condition Patient should have registration id
Post-condition Updation of the CSDB
5.4 Billing
Function billing
Description It provides bill details for both in and out patients
Inputs List of service provided
Outputs Payment receipt
Pre-condition Completion of diagnosis
Post-condition Payment receiving
5.5 Pharmacy and lab facilities

Function Pharmacy and lab facilities
Description It notes down the cost and reports from lab and pharmacy
Inputs Tests to be done and medicine prescription
Outputs Lab reports and corresponding billing
Pre-condition Test description and medicine prescription
Post-condition Integration with billing
Destination Add details to DB
6. SYSTEM EVOLUTION:
The hospital management system manage all the interactions between a patient and the
hospital . it provides easy use to the patients and helps the hospital in efficient
management . We believe the functionalities of our current HMS project will satisfy the
Hospital’s needs for efficient patient management . However, all computerized systems
needs to be maintained, supervised and possibly configured to operate efficiently for the
hospital. The evolution of the HMS system depends heavily on the hospital’s future need
for further computerized-assisted operations and newer technologies that may become
available to the hospital.
6.1 General Maintenance and Evolution
After the system has been beta tested and configured for optimal performance,
system administrators monitoring the operational systems will give general feedback on
desired usability and what they would like to see the system involve into. Thus, the
system may be reconfigured for newer versions.
During the two first years of operations, HMS is entitled to four updated versions of
the system to ensure product validity within the scope of operations defined in the Bid
For Proposal. Computer software is always in a continuous life cycle of updates,
configuration and amendments. Like most other Hospital tools and utilities, the patient
management system must be updated and renewed at various times.
6.2 Need for Additional Functionalities
The hospital may desire to add or change functionalities to HMS or configure the
parameters for the optimization process. This may include adding functionalities like
online appointment scheduling or consultants enquiry or change in the billing modes of
payment . In this case, a new version of the system would be released to replace the
existing registration system.
6.3 Future Technologies
The proposed registration and management system will provide the hospital with
greater performance and simplicity of patient management, the same ideal that sparked
the idea for the current HMS registration system. The patient and doctor management
system will evolve around the availability of newer technologies. Newer technological
breakthroughs affect the management system in one of two ways. The new
hardware/software will either be compatible or not be compatible with the management
system. Future technologies could, and is most likely to, uphold and improve the current
standards, which would not harm the functionality of this project. New computer
platforms will rather enhance the usability and efficiency of the system.
6.4 Predicted Evolution
The computer processing power and the Internet data transfer capability are likely
to keep developing in the future. The Internet infrastructure will allow the appointment
scheduling system to become the most effective and beneficial computer assisted tool at
PEC. Therefore, we predict a long lifespan of the product with the major adjustments in
the front-end usability and further back-end configuration options for system
administrators.

Reqirement Specification Document FOR Hospital Management System

Uploaded by

Copyright:

Available Formats

Reqirement Specification Document FOR Hospital Management System

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

Reqirement Specification Document FOR Hospital Management System

Uploaded by

Copyright:

Available Formats

REQIREMENT SPECIFICATION DOCUMENT

3. User requirements specification

5. System requirements specification

This automated system is mainly provided to facilitate the

3. out patient management

5. pharmacy and lab facilities

1.helps in efficient management of the hospital

2.enhances patient care

3.improves work efficiency

4.enables the growth of hospital

3.2 Out Patient Management

4.1 Hardware Requirements:

Since this implementation is essentially a user interface, there will be little to no

4.2 Software Requirements:

5. SYSTEM REQUIREMENTS SPECIFICATION:

5.2 out patient management

5.3 in patient management

5.5 Pharmacy and lab facilities

6.1 General Maintenance and Evolution

6.2 Need for Additional Functionalities

6.3 Future Technologies

6.4 Predicted Evolution

You might also like