Hospital Management System
Hospital Management System
MANAGEMENT
SYSTEM
MediWeb 1
Contents
Topics Page
#
OVERVIEW
Background 3
Introduction to MediWeb 3
Salient features 4
Overall System Features 4
TECHNICAL DETAILS
Core Modules 5
Reception 6
Registration 6
OPD 6
IPD 7
OT MANAGEMENT 7
BLOOD BANK 7
WARD MANAGEMENT 8
DIAGNOSTICS 8
MATERIAL MANAGEMENT 9
Pharmacy 10
Services 10
Billing 10
SECURITY FEATURES 11
OVERALL SYSTEM ARCHIETECTURE(diagram) 12
IMPLEMENTATION PLAN 20
REQUIREMENT COLLECTION 20
ANALYSIS & DESIGN 21
DEVELOPMENT 22
TESTING 22
IMPLEMENTATION & MAINTENANCE 23
TRAINING 24
MAINTENANCE 24
PROJECT PLAN 24
STAFFING & PERSONNEL PLAN 25
QUALITY ASSURANCE PLAN 25
CONFIGURATION MANAGEMENT 26
PROJECT MONITORING 26
RISK MANAGEMENT 26
HARDWARE & TOOLS 27
DEVELOPMENT TOOLS 28
FINANCIAL PROPOSAL 28
DATA SECURITY/BACK UP 29
COPY/LICENSING RIGHT 29
EXPANDIBILITY 29
WARRANTY & MAINTENANCE 29
MediWeb 2
BACKGROUND
Introduction
MediWeb 3
Salient Features
• It’s Flexible – User Specified rule: Wherever it is possible, user will have
the choice to select the right combination of rules, which is suitable to their
organization.
MediWeb 4
to the LAN, WAN simply using a web browser. It can also be hosted in the
Internet and accessed from anywhere with a internet connection.
Core
Modules
Reception/Help Desk
Registration
Outpatient (OPD)
Inpatient (IPD)
OT/ICU Management
Blood Bank
Ward Management
Diagnostics
Material Management / General Store & Inventory
Services
Billing
Reception/Help Desk:
The Help Desk Module automates the day-to-day functions of the Front
office management of a hospital. This module helps in assisting patient with
accurate information and supports in handling patient related enquiries
efficiently. This module having excellent features and advanced search
facilities improves the quality of services rendered to the user. It provides for
queries relating to the following:
MediWeb 5
Doctor related enquiries
Availability Details
OP Clinic Details
Appointment Schedules
Operation Schedules and Charge Details
Registration
OPD
MediWeb 6
calculates the cost for the services rendered to the patient and reflects in the
billing module appropriately resulting in smooth billing process.
IPD
The inpatient module is designed to take care of all the activities and
functions pertaining to Inpatient Management. This module automates the
day-to-day administrative actives and provides instant access to other
modules, which leads to a better patient care. It provides comprehensive
data pertaining to Admission of Patients & Ward Management: Availability of
beds, Estimation, Agreement preparation, Collection of advance, planned
admission, Emergency admission and so on. The Inpatient module also deals
with Ward Management: Shifting from one ward to the other, Bed
availability, Surgery, Administration of drugs, nursing notes, charge slip and
so on. Important functions of this module are
The module tracks every visit made by the patient and caters to follow-up
visits of patients, along with multiple appointments.
OT/ICU Management
This module deals with operation theatre and Intensive care unit activities
such as equipment used detail, resource ordering and scheduling, drug order,
gynecology detail recording, laboratory order and reports transfer requisition,
patient monitoring, blood request, new born baby detail and details of
delivery.
Blood Bank
The blood bank module provides information on the collection and storage of
blood, results of blood tests, cross-matching identifications, and transfusion
reactions. It also enables the maintenance of donor mailing lists and donation
ledgers.
Ward Management
MediWeb 7
This module, depending on the functionality, is divided into three sub
modules as follows:
Housekeeping activities
This sub module takes care of scheduling and monitoring
housekeeping activities, e.g. the attendance of cleaners, and record
details of any complaints made by the patients or by the supervisor of
the ward. Details of any action taken regarding complaints are also
recorded.
Diagnostics
MediWeb 8
Lab Inventory
Quality Control
General Stores and Inventory module deals with Purchase of Items, Issue of
Items, Maintenance of Stock, Automatic Reorder level Setting, Online request
for stock from various sub-stores, Online stock transfer, maintenance of
stock at different sub-stores, Physical stock verification and adjustment,
Return of items to supplier etc. Key functions of this module are
Stock management
Multi UOM and Multi currency system
Stock control
Stock Purchase through Enquiry generation
Sub stores issues and receipt of stocks
External hospital stock issues and receipt
Option to include and track gift or donation of stock
Stock requisitions from sub-stores and corresponding management
Quotations and Purchase Requisitions
Purchase order generation and processing- LPO, Emergency Purchase
order, Principal and Blanket PO
Advance payment requisitions to Finance
Goods Receipt Note and Purchase returns
Automatic stock updates on receipt of goods
Stock returns and destruction tracking
Invoice verification
Supplier management and supplier payment bucket facility available
Supplier invoice management
Pharmacy
Enquiry
Quotation
Purchase order
Online approval,
Pharmacy drug configuration
Pharmacy stores configuration
Drug issue to patients and billing
Unit dosage facility
Supplier information
MediWeb 9
Maintenance of drug inventory
Automatic reorder level setting
Purchase Requisitions
Purchase Order
Online request for stock from various sub-stores
Online stock transfer
Maintenance of stock at different sub-stores
Return of items nearing expiry
Destruction of expired items
Physical stock verification and adjustment
Goods receipt
Stock Transfer (inter store stock transfer)
Stock Adjustment
Stock in Hand reports
Services
The service module deals with all the services available in the hospital and
the charges for these services are stored through this module. There are
various services that are available in the hospital can be seen in:
Billing
The Patient Billing module handles all types of billing for long-term care. This
module facilitates cashier and billing operations for different categories of
patients like Outpatient, Inpatient and Referral. It provides 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. This module provides for credit partly billing and can be seamlessly
integrated with the Financial Accounting Module. The billing module is
extensively flexible by which each of your billing plans can be configured to
automatically accept or deny. The system is tuned to capture room and bed
charges along with ancillary charges based on the sponsorship category. The
MediWeb 10
Billing Screens is used for In-patient and Outpatient Billing and Invoicing.
Further more the charges for various services rendered can be recorded
through service module and this can be used for billing purposes. Key
functions of this module are
SECURITY FEATURES :
MediWeb 11
OVERALL SYSTEM ARCHITECTURE
MediWeb 12
MediWeb 13
MediWeb 14
MediWeb 15
MediWeb 17
MediWeb 18
MediWeb 19
IMPLEMENTATION PLAN
REQUIREMENT COLLECTION
MediWeb 20
Function network, which are similar to function hierarchy but
they highlight those functions, which are common to more than
one procedure.
List of attributes of the entities - these are the data items which
need to be held about each entity (record)
Analysis:
Design:
Based on the user requirements and the detailed analysis of a new system,
the new system must be designed. This is the phase of system designing. It
MediWeb 21
is a most crucial phase in the development of a system. Normally, the design
proceeds in two stages:
Preliminary or general design
Structure or detailed design
In the preliminary or general design, the features of the new system are
specified. The costs of implementing these features and the benefits to be
derived are estimated. If the project is still considered to be feasible, we
move to the detailed design stage.
DEVELOPMENT
TESTING
Before actually implementing the new system into operations, a test run of
the system is done removing all the bugs, if any. It is an important phase of
a successful system. After codifying the whole programs of the system, a test
plan should be developed and run on a given set of test data. The output of
the test run should match the expected results.
MediWeb 22
Using the test data following test run are carried out:
Unit test
System test
Implementation
After having the user acceptance of the new system developed, the
implementation phase begins. Implementation is the stage of a project
during which theory is turned into practice. During this phase, all the
programs of the system are loaded onto the user's computer. After loading
the system, training of the users starts. Main topics of such type of training
are:
After the users are trained about the computerized system, manual working
has to shift from manual to computerized working. The following two
strategies are followed for running the system:
i. Parallel run: In such run for a certain defined period, both the
systems i.e. computerized and manual are executed in parallel. This
strategy is helpful because of the following:
i. Pilot run: In this type of run, the new system is installed in parts.
Some part of the new system is installed first and executed
successfully for considerable time period. When the results are found
satisfactory then only other parts are implemented. This strategy
builds the confidence and the errors are traced easily.
TRAINING
MediWeb 23
HOMEBOUND, can harvest full benefits of the system only if there is a well
trained team of users. The key users of the system will include top-level
managers (depart managers), mid level employees and also the operators.
Different sessions of training will be organized by ETL depending on
department, level of users etc.
MAINTENANCE
ETL has we well-defined maintenance plan has got proven track record of
smooth execution of such plan.
PROJECT PLAN
Scheduling
Staffing and personnel plan
Quality assurance plan
Configuration management
Project monitoring
Risk management
MediWeb 24
Success of an information system implementation greatly depends of
availability a well-organized and balanced team. The complexity of the total
integrated design of the whole system demands involvement of people from
every functional unit. The team for the proposed system is as follows
A well defined set of procedures for quality assurance is another key element
of project planning. ETL’s streamlined quality assurance plan requires the
development team to maintain proper documentation and tractability record,
which is required for software quality assurance.
As a part of the QA plan for the proposed project following documents will be
produced during different phases of development:
No-matter how well the project plan or the QA plan is, it us useless without
an active monitoring plan. Following methods will be used for project
monitoring:
Project logs
Biweekly meetings
Reviews
MediWeb 25
CONFIGURATION MANAGEMENT
PROJECT MONITORING
Time Sheet
Reviews
Cost-schedule-milestone graph
Unit development folder
RISK MANAGEMENT
Every medium and large-scale project involves certain risks, and risk
management plan are adopted to avoid or minimize the risk. Risk in such a
project can be broadly grouped into three categories:
Cost risk
Performance risk
Schedule risk
With the help of a team consisting of highly experienced ERP consultants and
other top-level staff, ETL can lay out a risk management plan the address
these three areas to assess and control the involved risk. ETL is confident to
eliminate the risks, if any, to a minimum level.
MediWeb 26
The risk management plan adopted by ETL addresses a list of commonly
encountered risk items and attempts to avoid those as much as possible.
However some out of control or unanticipated situation may occur where risk
cannot be avoided. In those cases a risk reduction plan will apply. Well
defined risk resolution procedures will be applied to manage all these
activities.
Hardware Requirements:
Server Configuration:
Processor : Intel® Core™2 Quad Processor (2.4 GHz)
RAM : 4GB
Hard Disk Drive : 160GB x 2
LAN Card : 1000 Mbps
Operating system : Windows 2003 Server
Other Hardware:
1. Switch/Hub
2. Power backup for server and Client PC
3. Data backup device such as External Hard disk
4. DVD writer
5. Cable
6. Modem
7. Printer
DEVELOPMENT TOOLS:
User Interface : C#, ASP.Net
Database : MS SQL Server 2005
Operating System : Windows 2003 server, Windows XP
MediWeb 27
Network Protocol : TCP/IP
FINANCIAL PROPOSAL
Total reduced price in words: One lac fifty thousand Taka only
Mode 0f Payments
MediWeb 28
On Signing of the Contract: 25 % the quoted
amount
At the time of Live Draft 50 % the quoted
amount
On Completion and going Live of the system 25 % the quoted
amount
The offer will not include the license price for RDBMS Software and other
third party tools that may be required. We have not included any costs that
we may incur before or after the assignment is taken up on local conveyance,
stationery, etc. or after the assignment is taken up, which we will absorb
ourselves.
ETL will develop software keeping in mind the Data Security / Backup
procedure. Backup of data can be stored in a specific location of server’s hard
disk drive or in a backup device provided by the client.
EXPANDABILITY
Modification or enhancement of developed software can be provided on terms
mutually agreed upon.
ETL proposes to provide 3 months warranty period for the proposed system.
ETL will provide all the maintenance and bug fixing service during this period
free of cost.
MediWeb 29
1. The client will appoint a team of users representing all functional
departments of the organization lead by project team leader to work
with ETL team in different phases of the implementation.
3. Apart from the office space, it would be desirable for our team to have
office logistics support to be made available to our team by the client.
4. The price quoted and agreed upon will be applicable for the functions
and features specified and documented by ETL in coordination with the
client team. Any major changes requested by client will lead to extra
charges.
5. ETL provide all maintenance, bug fixing and minor changes required
during the agreed warranty period. For any changes after that period
ETL will charge and agreed amount.
6. For any maintenance and support after the warranty period the client
must come to an agreement with ETL, which can be based on annual
maintenance fee or per call basis.
7. HOMEBOUND will provide the purchase and yearly renewal fee for any
RDBMS, Operating System and third party tools used in the project.
8. The Charges and any additional charges are exclusive of any applicable
value added tax or any other tax for the time being in force, which the
Client shall be additionally liable to pay to the Company.
9. ETL will not take any responsibility for hardware failure, crashes and
data corruption due to virus or other reasons.
MediWeb 30