Hospital Information System

HOSPITAL
INFORMATION MANAGEMENT
M. KAMARAJ, Ph.D.,
Asst. Professor of Business Administration,
Annamalai University
kamarajaudde@gmail.com
- World Health Organization
1
HOSPITAL INFORMATION SYSTEM
M.KAMARAJ,Ph.D., Annamalai University

HOSPITAL
• What is a Hospital?
A hospital is an integral part of social and medical organization,
the function of which is to provide for the population complete
health care, both curative and preventive, and whose outpatient
services reach out to the family and its home environment; the
hospital is also centre for the training of health workers and
bio-social research.
- World Health Organization
2

HOSPITAL
• What is an Information?
Information is the message being conveyed. “Knowledge
communicated or received, concerning a particular fact
or circumstance.
3

HOSPITAL
• What is Health Information Management?
Health information management (HIM)
is information management applied to
health and health care. It is the practice of acquiring,
analyzing and protecting digital and traditional
medical information vital to providing quality patient
care.
4

HOSPITAL
• Objectives of Health Information Management?
Health information management (HIM)
is information management applied to
health and health care. It is the practice of acquiring,
analyzing and protecting digital and traditional
medical information vital to providing quality patient
care. It generates as well as maintains Electronic Medical
Record (EMR) and makes it available across the hospitals.
5

HOSPITAL
• Objectives
 Streamline overall operations and increase
efficiency of hospitals.
 Maintaining high patient satisfaction index
through quality health care services.
 Consolidated patient EMR made readily
available at any point of time.
 Effective Management of available resources
(manpower, machine, space)
6

HOSPITAL
• Objectives
7

HOSPITAL
8

HOSPITAL
• How information is
transforming hospital
organization?
Hospital Managers have
developed creative
application of technology
that have altered the way
members of the organization
work and communicate, how
patients and stakeholders
relate, and even how
hospitals are structured.
9

HOSPITAL
• What is the nature of
Information?
10

HOSPITAL
• Objective of an
information system is
to provide information
that supports decision-
making.
11

HOSPITAL
• Management must
first determine a
policy and strategy for
information
technology.
12

HOSPITAL
• Managers should
develop a plan for
systems. The plan is
likely to suggest new
structures for the
organization, and it
should at least deal
with how information
services are to be
organized.
13

HOSPITAL
14

HOSPITAL
15

HOSPITAL
• The plan will identify new applications areas for
technology will indicate new opportunities for the
use of information technology.
• In today’s environment, it is likely that the plan
will contain ideas on how to encourage users to
apply technology to solve their own problems.
16

HOSPITAL
• The development of an Information Technology
(IT) architecture is closely related to the structure
of the organization.
17

HOSPITAL
• Will the hospitals use a variety
of computers?
• Will its computers be
networked?
• Will it have an intranet as well
as Internet connections?
• Who will manage individual
computer installations
• Who will authorize
expenditures on systems?
• What kind of communication
technology will be used to
provide connectivity among
different locations and users?
18

HOSPITAL
• The way the firm develops
systems is by conducting
systems analysis and design.
• The design of applications has
an impact on users since they
will be trying to access data in
a new system.
• The entire area of information
technology, computers,
communication devices and
networks, and databases
supports the firm’s information
systems architecture and
systems analysis and design.
19

HOSPITAL
• The kinds of systems that are created and the
architecture developed for them will have a
dramatic impact on the hospital organization.
20

HOSPITAL
BENEFITS TO STAKE HOLDERS
21

HOSPITAL
• The final management activity is the evaluation and control of
information technology in the organization.
• Does the organization obtain a return from its investment in
the technology?
• Are information systems under management’s control?
• Is the IS effort fragmented and uncoordinated?
22

HOSPITAL
• The Information at different levels of Management
23

HOSPITAL
• The Information Processing Cycle
24

HOSPITAL
• Components of Information System
.
25

HOSPITAL
• Components of Information System
• Computer hardware. This is the physical
technology that works with information.
• Computer software. The hardware needs to
know what to do, and that is the role of
software.
• Telecommunications.
• Databases and data warehouses.
• Human resources and procedures.
26

HOSPITAL
• Decision Support System
Decision Support Systems (DSS) are a class
of computerized information system that support
decision-making activities. DSS are
interactive computer-based systems and
subsystems intended to help decision makers use
communications technologies, data, documents,
knowledge and/or models to complete decision
process tasks.
27

HOSPITAL
INFORMATION MANAGEMENT:
DECISION SUPPORT SYSTEM
28

HOSPITAL
• Executive Support System
An Executive Support System (ESS) is software that
allows users to transform enterprise data into
quickly accessible and executive-level reports, such
as those used by billing, accounting and staffing
departments. An ESS enhances decision making for
executives.
ESS is also known as Executive Information System
(EIS).
29

HOSPITAL
30

HOSPITAL
31

HOSPITAL
• Management Information System (MIS)
MIS is the use of information technology, people,
and business processes to record, store and
process data to produce information that decision
makers can use to make day to day decisions.
MIS is a collection of systems, hardware,
procedures and people that all work together to
process, store, and produce information that is
useful to the organization.
32

HOSPITAL
• Management Information System
.
33

HOSPITAL
• MIS Report
.
34

HOSPITAL
• Transaction Processing System
• Transaction processing systems consist of
computer hardware and software hosting a
transaction-oriented application that
performs the routine transactions
necessary to conduct business.
Examples include systems that manage sales
order entry, airline reservations, payroll,
employee records, manufacturing, and
shipping.
35

HOSPITAL
• Transaction Processing System Contd…
A transaction processing system, or TPS, is a
system to capture and process the
detailed information necessary to update
data on the fundamental operations of an
organization. Transactions are single events
that change something, such as customer
orders, receipts, invoices, payments, etc.
36

HOSPITAL
• Transaction Processing System Contd…
.
37

HOSPITAL
• Network Topologies
38

HOSPITAL
Components of Computer Network
39

HOSPITAL INFORMATION MANAGEMENT
Uninterrupted Flow of Information, Anytime, Anywhere
Hospitals should
provide Doctors,
Patients and the
Management with a
healthcare Mobile App,
which should work as a
handy tool for sharing
and viewing
information
40

Mobile App for Doctors
Advanced and extremely efficient
mobile application allows doctors to
monitor and treat patients from a
remote location. It provides access to
doctors and authorized users of the
institution to view the patient and
drug interaction information and the
medication knowledge bases.
In other words, it provides the ability
to view patient vitals, alerts, medical
and lab reports, X-rays, intake and
outputs, progress notes, discharge
summaries etc ‘on-the-go’ so that
there is no wastage of time.
41

Mobile App for Decision-Makers
The mobile app also allows the top
management and key decision makers
to view MIS reports and other crucial
financial data. These statistics enable
them to make the right business
decisions that can lead to increased
productivity and revenue, and
reduced operational costs. Since data
can be conveniently and remotely
accessed, it becomes easy to take
decisions at the right time, to avoid a
crisis.
.
42

Mobile App for Patients
The mobile app also allows the top
management and key decision makers
to view MIS reports and other crucial
financial data. These statistics enable
them to make the right business
decisions that can lead to increased
productivity and revenue, and
reduced operational costs. Since data
can be conveniently and remotely
accessed, it becomes easy to take
decisions at the right time, to avoid a
crisis.
.
43

SMART CARD ID
Issuing of e-Health Smart Card
to the patient at the time of
registration / admission, it
feeds the Personal + Clinical
details (Blood Group, Allergies,
Current Health Problems,
Current Medications,
Vision/Implants, etc.),
Insurance Details, Emergency
Contact Information with
mobile numbers, etc.
44

PATIENT PORTAL
The Patient Portal grants rights to
patients to log in to the system using
their unique log in credentials in order
to book appointments, view doctors’
schedules, and access and download
their medical reports and documents,
in just a few clicks, from the comfort
of their home. This minimizes the
need to be physically present in the
healthcare institution in order to book
an appointment with a doctor, or to
view their own medical records.
45

e-WALLET
e-Health offers the one-of-its-kind ‘e-
Wallet’ to promote efficient billing
procedures when a patient is
admitted and is being treated in the
hospital. Payments for diagnostics,
pharmacy, and other departments get
directly deducted from the prepaid
mobile wallet. This in turn minimizes
the need to carry physical money and
makes the billing processes quick and
seamless.
46

Digital Signage
Digital signage facility wherein patients
are assisted with the required information
by the desired doctor through large size
LED/LCD display systems. The system
enables the doctor to recall the patients’
history or call a nurse or any assistance.
The digital unit displays the name of the
consulting doctor occupying the room,
doctor’s profile and the current patient’s
token no. It also encourages patient
education by displaying the doctor’s cases
and other vital health and hospital
information like health tips, wellness
packages, and so on.
47

Healthcare Kiosk
e-Health’s innovative and easy-to-use
Healthcare Kiosk increases patient
satisfaction by lowering waiting times and
providing higher levels of convenience
and privacy. Using the kiosk, patients can
self-register themselves and can also book
appointments, process bills, and collect
reports etc. Institutions can achieve
considerable operational benefits
including improved accuracy in patient
records and records management.
Healthcare kiosk also facilitates
automated application processing,
positive patient experience, reduced
staffing costs, and better visitor
management, amongst the rest.
48

MODULES
INFORMATION DESK MODULE
This module deals with
all types of enquiries
received in regard to
the hospital and in
regard to the patients
who are admitted or
registered.
Features:
• Patient enquiry
• Appointments enquiry
• Investigation appointment enquiry
• Consultants enquiry
• Investigation enquiry
• In-patient enquiry
• Tariff information
• Packages information
• Estimates
• Visitor pass management
49

MODULES
PATIENT REGISTRATION MODULE
This module registers
patient details based on
general and demographic
information. Patients are
allocated a Unique Health
Identification Number
(UHID) and discount cards
at the time of registration.
Features:
•Detailed information of patients
• Mandatory fields for crucial patient
information as per JCI Standards
• Alerts in place to prevent erroneous
data entry
• Generates Smart Card with Unique
Health Identification Number (UHID)
• Advanced multi-criteria search for
registered patients
• RFID wrist band generation
• Provision for recording sponsor,
insurance and medical tourism details
50

MODULES
OUT-PATIENT MANAGEMENT
This module deals with
recording the patients’ basic
medical treatment details and
depends on other modules for
acquiring their registration
details, booking appointments
for consultation, test
appointments, report viewing
etc.
Features:
• Dashboards for patients activity/sponsor activity
• Dashboards for user activity
• Dashboard for advances/payments/refunds etc
• UHID creation/merging/activation
• Schedules for doctors
• Patient evaluation
• Diagnosis
• Lab orders
• Medication orders
• Procedure orders
• Cross referral
• Token system (Digital Signage)
• Data reports on user activity/patient
activity/doctor activity
• Reports on OPD/patient count/service
billing/revenue
• NABH/JCI indicators for patient waiting
time/turnaround time
51

MODULES
IN-PATIENT MANAGEMENT
This module commences
when the patient is being
registered and allotted a
bed in the ward. It deals
with the complete
treatment and services
provided to the patient
during his/her stay in the
hospital.
Features:
• Conversion from OP to IP
• NABH/JCI standards in registration process
• RFID wrist band for tracking of patient in the
hospitals
• Bed allotment
• Inter-departmental consultation
• Bed transfers
• Requisition of drugs and consumables from
the pharmacy
• Raising investigations and report viewing
• Maintenance of billing sheets for patients
• Dashboard for patient access
• Dashboard for billing activities/audit
• Dashboard for quick links (counts, revenue,
discount etc)
• Discharge summary
52

MODULES
PHARMACY INFORMATION SYSTEM
This module deals with the
retail sale of medicines to
general customers & OPD
patients, and issue of medicines
to the in-patients in the
hospital. Its functions include
online drug prescription and
inventory management and
billing of drugs, surgical and
consumables.
Features:
• Provides a comprehensive online list of
available drugs for the doctors
• Displays alternative drugs for the non
available drugs
• Supports interfacing with drug databases
• The ABC, VED classification of medicines
• Auto-generation of alerts when minimum
stock levels are reached
• Online requisition for stock order from
the main store
• Provision to manage consignment items
• Barcode/RFID for the items
• Can be interfaced with Pneumatic tube
for dispatch
• Drug allergy alerts
53

MODULES
ADMISSION, DISCHARGE, TRANSFER (ADT)
ADT or In-patient Admission Transfer
Discharge. This module seamlessly
takes care of admission, discharge and
the transfer processes of patients. It
enables the search on availability and
manages the allocation of a bed,
ward, and room to a patient according
to the availability or cost associated
and thereby manages the transfers. It
takes care that the appropriate
discharge processes are followed and
also ensures that a comprehensive
discharge summary is generated at
the end.
Features:
• Comprehensive form for collection of
precise data regarding the patient
• Thorough evaluation of the patient
condition
• Recording the doctors and nursing notes
for further management
• Processing orders in real time to the
respective departments
• Managing the billing process
• Managing the payments done by third
parties
• Bed and ward allocation and transfer
• E-prescribing of the medications
• Final billing and settlements
• Clinical packages management
54

MODULES
PATIENT CARE (BIRTH & DEATH REGISTRATION)
This module provides the
registration of births and
deaths, accurate birth and
death certificates, handling
of birth and death registers
management and
generation of statistical
reports, updated in real
time.
Features:
• Registration of birth data for a
newborn
• Generation of an ID number when
registering a newborn
• Registration of family relationships
• Printing of accurate, secured birth
certificates
• Providing statistical information
• Information can be ported to any
Govt. Portals
55

MODULES
IDENTITY AND ACCESS MANAGEMENT
This module gives an overall
view of the organization’s
activities, reports, periodic
revenue & expense register,
surgical statistics, OP/IP
statistics like number of walk-in
admissions, appointments,
cancelled appointments,
patient transfers, discharges,
absconding patients, patient
referrals and many more such
reports, registers & views.
Features:
• Electronic prescribing and generating
drug order to pharmacy
• Lab order
• Diet order
• Vital order
• Blood order
• Procedure order
• ICU services by nurse
• Ward services by nurse
• Surgical medication items template
orders
56

MODULES
SERVICE ORDER PROCESSING
The service order processing and
billing is used to process the orders
prescribed by the clinicians or other
staff in real time. This is called e-
prescribing of service or e-
prescription. These orders are
populated in their concerned
departments after passing the
process of billing. These services are
billed on the concerned billing
counters depending upon the
category of the patient (i.e Cash,
insured, guest, staff etc.)
Features:
• Generation of service orders by service points
like clinics, wards, OT etc.
• Electronic processing orders
• Real time updates
• Service order tracking
• Service point account for material
consumption against service order
• Detection of material wastage and loss of
revenue at service point
• Provision for ensuring billing payment before
the processing of order to the concerned
department
• Provision for giving discounts for services
subject to authorization
• Provision for providing healthcare packages
and billing collectively for services provided in
these packages
57

MODULES
LABORATORY INFORMATION SYSTEM
This module is used by the
pathology lab to record
and disseminate the
information regarding the
tests performed. The
laboratory department
receives online orders from
doctors and also allows
laboratory personnel to
generate requests.
Features:
• Service and test setup
• Diagnostic packages using different tests
• Billing using lab orders from clinical
module
• Requisition generation from lab
order/bill
• Requisition creation based on facility
wise, test wise, sample type wise
• Sample collection process
• Interfacing with lab analyzers
• Results fetching from analyzer data
• Results recheck process
• Results authorization
• Print queue process
• Access previous lab results based on
tests and UHID number 58

MODULES
RADIOLOGY / MEDICAL INFORMATION SYSTEM
This module facilitates management
of the workflow of radiology services
and equipment, in addition to
supporting entry of work records and
reports. The ultimate objective is to
store all patient images, scans, and
ECG graphs in the system or as
electronic files due to its integration
with PACS, thereby eliminating the
unnecessary retrieval and
dissemination of films.
Features:
• Sponsor-wise service mapped with diagnostic
tests
• Billing using lab orders from clinical module
• Requisition generation from lab order/bill
• Requisition creation based on facility, test, and
modality
• Report entry using templates
• Results authorization
• Redo process
• Status update
• Print queue process
• Access previous lab results based on tests and
UHID number
• Dashboard for work in progress
• Speech-to-text for radiologists
59

MODULES
CASUALITY AND EMERGENCY MANAGEMENT SYSTEM
This module deals in taking care of
patients from the time they arrive in
the casualty till the time they are
transferred to a department in the
hospital for further treatment. This
module sends alerts to the
corresponding departments, captures
all the relevant data on patient’s
condition at the time of arrival and
the course of action undertaken, and
in turn helps in the planning the
further treatments and procedures.
Features:
• Capturing of whatever basic patient
demographic information is available at
the time of registration of the casualty and
updating the same when fully available
• Consulting details
• Clinical follow up scheduling
• Lab test reports
• Diagnosis
• Service orders and bookings
• Pharmacy/surgical details
• Statutory forms and reports etc
60

MODULES
WARD & BED MANAGEMENT SYSTEM
The ward & bed management module
maintains the record of bed &
occupancy status at all times. It
facilitates the estimation of
appropriate waiting time for patients
and helps in reducing the bed
turnover time which is very essential
for optimization of revenues. It also
provides statistical information
regarding the occupancy status of a
bed over a period of time.
Features:
• Current bed allocation status overview
• Monitoring and reducing the bed
turnover time
• Scheduling the housekeeping and
maintenance activities
• Calculation of revenue generated from
each type of bed
Etc
• Patient search & select
• Patient health status monitoring
• Material requisition for patient’s medical
consumable needs to central stores
• Roster management
• Bed transfer
61

MODULES
MATERIALS MANAGEMENT SYSTEM
This module deals with the
purchase and supply of hospital
equipment/material/inventory
to different departments.
Requisitions for different
items/equipment are sent to
this store from different
departments.
Features:
• Masters (generics, drugs, surgical items,
categories, sub categories)
• Supplier management
• Location management (warehouses, sub
stores, departments, stock points, crash
carts etc)
• Preparation of various warehouses for
general items, drugs, assets, surgical items
• Protocols for purchase, stocking, stock
tracking and verifications, distribution,
sales
• Today transactions reports.
62

MODULES
WARD MANAGEMENT SYSTEM
The bed management module
maintains the record of bed
occupancy status at all times. It
facilitates the estimation of
appropriate waiting time for patients
and helps in reducing the bed
turnover time which is very essential
for optimization of revenues. It also
provides statistical information
regarding the occupancy status of a
bed over a period of time.
Features:
• Patient search & select
• Patient health status monitoring
• Material requisition for patient’s medical
consumable needs to central stores
• Roster management
• Bed transfer
63

MODULES
CASHIER MANAGEMENT SYSTEM
This module facilitates cashier and
billing operations for different
Outpatient and Inpatient categories. 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. The system is tuned to capture
room and bed charges along with
ancillary charges based on the
sponsorship category.
Features:
• Payment modes/details
• Patient billing details
• Sponsor conversions
• Part bill generation
• Multi sponsor billing
• Multi currency payment
• User-defined billing cycles
• Cash collection dashboards
64

MODULES
NURSING MANAGEMENT SYSTEM
This module offers the window
to nursing or ward staff and
facilitates them to manage their
wards on a floor. Special units
like ICU and OT are practically
and effectively managed and
the module also tracks all
services given to a patient
connecting to their wards.
Features:
• Access to patient administration system
• Notification of patient’s pending arrival,
current status, etc
• Comprehensive charts to monitor the patient’s
condition
• Real time test, procedure and medication
ordering to the concerned departments
• For surgery, the theatre schedule is notified,
together with any preparation required
• Ability to record admissions, discharge and
transfers at the wards to update the bed census
• Confirm location of the patient and to notify
ancillary departments such as dietary
• Communicating with departments such as
housekeeping, maintenance, security, etc
• Procedure notes
• Nursing notes
65

MODULES
OPERATING ROOM MANAGEMENT SYSTEM
This module tracks all surgeries that take
place in the hospital. Right from
scheduling the operation, managing the
surgery team, recording the surgery
details to checklists associated with a
surgery; it manages in advance and
prepares for a surgery or operation by
keeping the records of all items required
during the operation. It enables an
electronic consent of the patient or the
relatives. It also maintains the data on
preoperative and postoperative conditions
of the patient.
Features:
• • Accurate scheduling of the operations
with flexibility in managing bookings
• Pre operative checklist
• Time out document
• Anesthesia record
• Operation record
• Multilingual consent forms
• Inventory and stock management of the
OT
• Sterilization schedules, checks and audits
66

MODULES
ELECTRONIC MEDICAL RECORDS MANAGEMENT SYSTEM
This module improves patient care as it
functions as a central source of
information for communication between
health care providers, covering the
patient’s history, observation, diagnosis
and therapeutic conclusions and a wide
variety of unstructured documents and
information.
Features:
• Charts like HGT, intake & output, vital
chart
• Medical record structure based on UHID
like transplant, non transplant, regular etc.
• Access control work flow
• Grouping based on time frame and
department
• ICD codification on diagnosis
• Index creation (dynamic, user defined,
doctor defined) for each patient record
• Index parameters like area, sex, problem,
diagnosis, allergies, MLC, doctor, surgery,
lab parameter value, clinical dept,
discharge type, summary, etc.
• Template based on patient type
67

MODULES
BLOOD BANK MANAGEMENT SYSTEM
This module is concerned with
various blood bank related
activities like donor
registration, physical
examination, blood grouping,
blood infectious tests,
component separation, and
blood requisition and cross
match.
Features:
• Physical examination
• Donation cancellation
• Bag number and donor number
generation
• Cell/serum grouping and validation
• Serology test entry and validation
• Component separation and requisition
• Cross match
• Blood and blood product quantity
• Discard blood and blood product
• Blood and blood product issue
68

MODULES
DIETARY / CATERING MANAGEMENT SYSTEM
This module lets the dietician
prescribe the most suitable diet to
any given patient, based on his/her
medical condition, as instructed by
the physician. It also allows the
maintenance of meal scheduling,
customizing meals as per patient
meals and recording of individual
meal orders.
Features:
• Allows the user to create the food items groups
and food items available in the hospital kitchen
• Captures the calorie count as well as the
nutritional information of all food items
• Facilitates capturing of recipes that are made up
of food items or other recipes and their
proportionate quantities. The steps for preparation
can also be mentioned
• Charts for maintaining the nutritive information of
different food stuffs
• Creation of a meal plan for the kitchen by the
dietician in the system for breakfast, lunch and
dinner for any given period of time as per the
requirements of patients
• Generates an order for the kitchen providing a list
of items to be prepared for each day, based on the
requirements of the patient
69

MODULES
HELP DESK MANAGEMENT SYSTEM
The primary objective of a helpdesk is to
provide a Single Point of Contact (SPOC)
for all problems /issues/ requests and
queries coming from the client
environment and ensuring that the
associated information is maintained and
reported in accordance. In the event of a
problem, the key objective of helpdesk is
to restore normal service as quickly as
possible by providing a work around using
the known error database
Features:
• Incident Management
• Problem Management
• Change Management
70

MODULES
HUMAN RESOURCE MANAGEMENT SYSTEM
This module takes care of the complete
working of the human resources
management in the hospital from the time
candidates apply for a job till the time
they resign. It includes a variety of
activities like deciding what staffing needs
you have, recruiting, training and
conforming to various regulations,
maintaining shift rotation, and delivering
reports on workload on an individual.
Features:
• Interface with biometrics for daily
attendance
• Leave management
• Duty roster
• Overtime management
• Salary, PF, TDS, loans management
• Pay slip generation through intranet
portal
• Bonus and incentive management
• Outsource employee management
71

MODULES
STATISTICS AND REPORTING MANAGEMENT SYSTEM
This module provides information to
the management to help them take
the right decisions. It helps in
measuring the performance of each
department in the hospital. Data can
be mined as per the analysis
required.
Features:
• Facility for exporting the data into
various formats like Excel and PDF
• Department-wise revenue details
• Easily customizable reports as per the
management’s needs
• Auto-scheduler for generating the
reports and sending the reports by Email
• SMS alerts generation
• Operational business reporting for work
reports
• Page perfect reports for formatted
documents such as delivery notes,
accounting documents, etc.
• Pixel perfect reports for documents such
as control panel or data analysis
72

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
73

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
• System Development Life Cycle (SDLC) is a
conceptual model which includes policies and
procedures for developing or altering systems
throughout their life cycles.
74

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
• Phases of System Development Life Cycle
(SDLC)
Systems Development Life Cycle is a systematic
approach which explicitly breaks down the
work into phases that are required to
implement either new or modified Information
System.
75

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
• Phases of SDLC
76

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
FEASIBILITY STUDY OR PLANNING
• Feasibility Study can be considered as preliminary investigation that helps
the management to take decision about whether study of system should be
feasible for development or not.
• It identifies the possibility of improving an existing system, developing a new
system, and produce refined estimates for further development of system.
• It is used to obtain the outline of the problem and decide whether feasible
or appropriate solution exists or not.
• The main objective of a feasibility study is to acquire problem scope instead
of solving the problem.
• The output of a feasibility study is a formal system proposal act as decision
document which includes the complete nature and scope of the proposed
system.
77

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
STEPS INVOLVED IN FEASIBILITY STUDY
• Form a project team and appoint a project leader.
• Develop system flowcharts.
• Identify the deficiencies of current system and set goals.
• Enumerate the alternative solution or potential candidate system to
meet goals.
• Determine the feasibility of each alternative such as technical
feasibility, operational feasibility, etc.
• Weight the performance and cost effectiveness of each candidate
system.
• Rank the other alternatives and select the best candidate system.
• Prepare a system proposal of final project directive to management
for approval.
78

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
STEPS INVOLVED IN FEASIBILITY STUDY
79

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
TYPES OF FEASIBILITIES
• ECONOMIC
• TECHNICAL
• OPERATIONAL
• BEHAVIOURAL
• SCHEDULE
80

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
ECONOMIC FEASIBILITY
• It is evaluating the effectiveness of candidate system by using
cost/benefit analysis method.
• It demonstrates the net benefit from the candidate system in
terms of benefits and costs to the organization.
• The main aim of Economic Feasibility Analysis (EFS) is to
estimate the economic requirements of candidate system
before investments funds are committed to proposal.
• It prefers the alternative which will maximize the net worth
of organization by earliest and highest return of funds along
with lowest level of risk involved in developing the candidate
system.
81

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
TECHNICAL FEASIBILITY
• It investigates the technical feasibility of each
implementation alternative.
• It analyzes and determines whether the solution can be
supported by existing technology or not.
• The analyst determines whether current technical
resources be upgraded or added it that fulfill the new
requirements.
• It ensures that the candidate system provides
appropriate responses to what extent it can support the
technical enhancement.
82

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
OPERATIONAL FEASIBILITY
• It determines whether the system is operating
effectively once it is developed and implemented.
• It ensures that the management should support the
proposed system and its working feasible in the current
organizational environment.
• It analyzes whether the users will be affected and they
accept the modified or new business methods that
affect the possible system benefits.
• It also ensures that the computer resources and
network architecture of candidate system are workable.
83

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
BEHAVIOURAL FEASIBILITY
• It evaluates and estimates the user attitude or
behavior towards the development of new
system.
• It helps in determining if the system requires
special effort to educate, retrain, transfer, and
changes in employee’s job status on new ways
of conducting business.
84

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
SCHEDULE FEASIBILITY
• It ensures that the project should be completed
within given time constraint or schedule.
• It also verifies and validates whether the
deadlines of project are reasonable or not.
85

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
ANALYSIS AND SPECIFICATION
 Gather, analyze, and validate the information.
 Define the requirements and prototypes for new system.
 Evaluate the alternatives and prioritize the requirements.
 Examine the information needs of end-user and enhances the
system goal.
 A Software Requirement Specification (SRS) document, which
specifies the software, hardware, functional, and network
requirements of the system is prepared at the end of this
phase.
86

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
INPUTS TO SYSTEM DESIGN
• Statement of work
• Requirement determination plan
• Current situation analysis
• Proposed system requirements including a conceptual
data model, and Metadata (data about data).
87

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
OUTPUTS TO SYSTEM DESIGN
• Infrastructure and organizational changes for the proposed
system.
• A data schema, often a relational schema.
• Metadata to define the tables/files and columns/data-
items.
• A function hierarchy diagram or web page map that
graphically describes the program structure.
• Actual or pseudocode for each module in the program.
• A prototype for the proposed system.
88

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
TYPES OF SYSTEM DESIGN
LOGICAL DESIGN
• Logical design pertains to an abstract representation of the
data flow, inputs, and outputs of the system. It describes
the inputs (sources), outputs (destinations), databases
(data stores), procedures (data flows) all in a format that
meets the user requirements.
• While preparing the logical design of a system, the system
analyst specifies the user needs at level of detail that
virtually determines the information flow into and out of
the system and the required data sources. Data flow
diagram, E-R diagram modeling are used.
89

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
LOGICAL DESIGN
• Logical design pertains to an abstract representation of the
data flow, inputs, and outputs of the system. It describes
the inputs (sources), outputs (destinations), databases
(data stores), procedures (data flows) all in a format that
meets the user requirements.
• While preparing the logical design of a system, the system
analyst specifies the user needs at level of detail that
virtually determines the information flow into and out of
the system and the required data sources. Data flow
diagram, E-R diagram modeling are used.
90

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
PHYSICAL DESIGN
• Physical design relates to the actual input and output processes of the
system. It focuses on how data is entered into a system, verified, processed,
and displayed as output.
• It produces the working system by defining the design specification that
specifies exactly what the candidate system does. It is concerned with user
interface design, process design, and data design.
• It consists of the following steps −
• Specifying the input/output media, designing the database, and specifying backup
procedures.
• Planning system implementation.
• Devising a test and implementation plan, and specifying any new hardware and
software.
• Updating costs, benefits, conversion dates, and system constraints.
91

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
TYPES OF DOCUMENTATION
• Program documentation
• System documentation
• Operations documentation
• User documentation
92

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
PROGRAM DOCUMENTATION
• It describes inputs, outputs, and processing logic for all the
program modules.
• The program documentation process starts in the system
analysis phase and continues during implementation.
• This documentation guides programmers, who construct
modules that are well supported by internal and external
comments and descriptions that can be understood and
maintained easily.
93

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
OPERATION DOCUMENTATION
Operations documentation contains all the information needed for
processing and distributing online and printed output. Operations
documentation should be clear, concise, and available online if possible.
It includes the following information −
• Program, systems analyst, programmer, and system identification.
• Scheduling information for printed output, such as report, execution
frequency, and deadlines.
• Input files, their source, output files, and their destinations.
• E-mail and report distribution lists.
• Special forms required, including online forms.
• Error and informational messages to operators and restart procedures.
• Special instructions, such as security requirements.
94

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
USER DOCUMENTATION
It includes instructions and information to the users who will interact with the system. For
example, user manuals, help guides, and tutorials. User documentation is valuable in training users
and for reference purpose. It must be clear, understandable, and readily accessible to users at all
levels.
The users, system owners, analysts, and programmers, all put combined efforts to develop a user’s
guide.
A user documentation should include −
• A system overview that clearly describes all major system features, capabilities, and limitations.
• Description of source document content, preparation, processing, and, samples.
• Overview of menu and data entry screen options, contents, and processing instructions.
• Examples of reports that are produced regularly or available at the user’s request, including
samples.
• Security and audit trail information.
• Explanation of responsibility for specific input, output, or processing requirements.
• Procedures for requesting changes and reporting problems.
• Examples of exceptions and error situations.
• Frequently asked questions (FAQs).
• Explanation of how to get help and procedures for updating the user manual
95

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
SYSTEM DOCUMENTATION
System documentation serves as the technical specifications for the IS and how the
objectives of the IS are accomplished. Users, managers and IS owners need never reference
system documentation. System documentation provides the basis for understanding the
technical aspects of the IS when modifications are made.
• It describes each program within the IS and the entire IS itself.
• It describes the system’s functions, the way they are implemented, each program's
purpose within the entire IS with respect to the order of execution, information passed to
and from programs, and overall system flow.
• It includes data dictionary entries, data flow diagrams, object models, screen layouts,
source documents, and the systems request that initiated the project.
• Most of the system documentation is prepared during the system analysis and system
design phases.
• During systems implementation, an analyst must review system documentation to verify
that it is complete, accurate, and up-to-date, and including any changes made during the
implementation process.
96

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
DESIGN STRATEGIES (TOP-DOWN)
• The top-down strategy uses the modular approach to develop
the design of a system. It is called so because it starts from the
top or the highest-level module and moves towards the lowest
level modules.
• In this technique, the highest-level module or main module for
developing the software is identified. The main module is
divided into several smaller and simpler submodules or
segments based on the task performed by each module. Then,
each submodule is further subdivided into several submodules
of next lower level. This process of dividing each module into
several submodules continues until the lowest level modules,
which cannot be further subdivided, are not identified.
97

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
DESIGN STRATEGIES (TOP-DOWN)
98

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
DESIGN STRATEGIES (BOTTOM-UP)
• Bottom-Up Strategy follows the modular approach to develop the
design of the system. It is called so because it starts from the bottom
or the most basic level modules and moves towards the highest level
modules.
• In this technique, The modules at the most basic or the lowest level
are identified.
• These modules are then grouped together based on the function
performed by each module to form the next higher-level modules.
• Then, these modules are further combined to form the next higher-
level modules.
• This process of grouping several simpler modules to form higher level
modules continues until the main module of system development
process is achieved.
99

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
DESIGN STRATEGIES (BOTTOM-UP)
• .
100

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
INPUT, OUTPUT & FORMS DESIGN
INPUT DESIGN
In an information system, input is the raw data that is processed to produce
output. During the input design, the developers must consider the input
devices such as PC, MICR, OMR, etc.
Therefore, the quality of system input determines the quality of system output.
Well-designed input forms and screens have following properties:
• It should serve specific purpose effectively such as storing, recording, and
retrieving the information.
• It ensures proper completion with accuracy.
• It should be easy to fill and straightforward.
• It should focus on user’s attention, consistency, and simplicity.
• All these objectives are obtained using the knowledge of basic design
principles regarding:
What are the inputs needed for the system?
How end users respond to different elements of forms and screens.
101

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
INPUT DESIGN
Objectives of Input Design:
• To design data entry and input procedures
• To reduce input volume
• To design source documents for data capture or devise
other data capture methods
• To design input data records, data entry screens, user
interface screens, etc.
• To use validation checks and develop effective input
controls.
102

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
DATA INPUT METHODS
• It is important to design appropriate data input
methods to prevent errors while entering data.
These methods depend on whether the data is
entered by customers in forms manually and
later entered by data entry operators, or data is
directly entered by users on the PCs.
103

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
DATA INPUT METHODS
A system should prevent user from making mistakes by :
• Clear form design by leaving enough space for writing legibly.
• Clear instructions to fill form.
• Clear form design.
• Reducing key strokes.
• Immediate error feedback.
• Some of the popular data input methods are −
• Batch input method (Offline data input method)
• Online data input method
• Computer readable forms
• Interactive data input
104

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
OUTPUT DESIGN
The design of output is the most important task of any system. During
output design, developers identify the type of outputs needed, and
consider the necessary output controls and prototype report layouts.
Objectives of Output Design
• To develop output design that serves the intended purpose and
eliminates the production of unwanted output.
• To develop the output design that meets the end users requirements.
• To deliver the appropriate quantity of output.
• To form the output in appropriate format and direct it to the right
person.
• To make the output available on time for making good decisions.
105

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
OUTPUT DESIGN (EXTERNAL OUTPUT)
• Manufacturers create and design external
outputs for printers. External outputs enable
the system to leave the trigger actions on the
part of their recipients or confirm actions to
their recipients.
• Some of the external outputs are designed as
turnaround outputs, which are implemented as
a form and re-enter the system as an input.
106

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
OUTPUT DESIGN
Internal outputs are present inside the system, and used by end-users
and managers. They support the management in decision making and
reporting.
There are three types of reports produced by management information:
Detailed Reports − They contain present information which has almost
no filtering or restriction generated to assist management planning and
control.
Summary Reports − They contain trends and potential problems which
are categorized and summarized that are generated for managers who
do not want details.
Exception Reports − They contain exceptions, filtered data to some
condition or standard before presenting it to the manager, as
information.
107

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
FORMS DESIGN
Both forms and reports are the product of input
and output design and are business document
consisting of specified data. The main difference
is that forms provide fields for data input but
reports are purely used for reading. For example,
order forms, employment and credit application,
etc.
108

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
OBJECTIVES OF GOOD FORMS DESIGN
A good form design is necessary to ensure the following:
• To keep the screen simple by giving proper sequence,
information, and clear captions.
• To meet the intended purpose by using appropriate
forms.
• To ensure the completion of form with accuracy.
• To keep the forms attractive by using icons, inverse
video, or blinking cursors etc.
• To facilitate navigation.
109

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
TYPES OF FORMS
Flat Forms
It is a single copy form prepared manually or by a machine and printed on a paper. For additional
copies of the original, carbon papers are inserted between copies.
It is a simplest and inexpensive form to design, print, and reproduce, which uses less volume.
Unit Set/Snap out Forms
These are papers with one-time carbons interleaved into unit sets for either handwritten or
machine use.
Carbons may be either blue or black, standard grade medium intensity. Generally, blue carbons are
best for handwritten forms while black carbons are best for machine use.
Continuous strip/Fanfold Forms
These are multiple unit forms joined in a continuous strip with perforations between each pair of
forms.
It is a less expensive method for large volume use.
No Carbon Required (NCR) Paper
They use carbonless papers which have two chemical coatings (capsules), one on the face and the
other on the back of a sheet of paper.
When pressure is applied, the two capsules interact and create an image. 110

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
TESTING
Testing is the process or activity that checks the functionality and
correctness of software according to specified user requirements
in order to improve the quality and reliability of system. It is an
expensive, time consuming, and critical approach in system
development which requires proper planning of overall testing
process.
A successful test is one that finds the errors. It executes the
program with explicit intention of finding error, i.e., making the
program fail. It is a process of evaluating system with an intention
of creating a strong system and mainly focuses on the weak areas
of the system or software.
111

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
TESTING
• Testing is the process or activity that checks the functionality
and correctness of software according to specified user
requirements in order to improve the quality and reliability of
system. It is an expensive, time consuming, and critical
approach in system development which requires proper
planning of overall testing process.
• A successful test is one that finds the errors. It executes the
program with explicit intention of finding error, i.e., making the
program fail. It is a process of evaluating system with an
intention of creating a strong system and mainly focuses on the
weak areas of the system or software.
. 112

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
TYPES OF TESTING
Unit Testing
Also known as Program Testing, it is a type of testing where the
analyst tests or focuses on each program or module
independently. It is carried out with the intention of executing
each statement of the module at least once.
In unit testing, accuracy of program cannot be assured and it is
difficult to conduct testing of various input combination in
detail.
It identifies maximum errors in a program as compared to other
testing techniques.
.
113

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
TYPES OF TESTING
Integration Testing
• In Integration Testing, the analyst tests multiple module
working together. It is used to find discrepancies between the
system and its original objective, current specifications, and
systems documentation.
• Here the analysts are try to find areas where modules have
been designed with different specifications for data length,
type, and data element name.
• It verifies that file sizes are adequate and that indices have
been built properly.
114

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
TYPES OF TESTING
Functional Testing
• Function testing determines whether the system is functioning
correctly according to its specifications and relevant standards
documentation. Functional testing typically starts with the
implementation of the system, which is very critical for the success of
the system.
• Functional testing is divided into two categories −
Positive Functional Testing − It involves testing the system with valid
inputs to verify that the outputs produced are correct.
Negative Functional Testing − It involves testing the software with
invalid inputs and undesired operating conditions.
115

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
IMPLEMENTATION
• Implement the design into source code through coding.
• Combine all the modules together into training
environment that detects errors and defects.
• A test report which contains errors is prepared through
test plan that includes test related tasks such as test case
generation, testing criteria, and resource allocation for
testing.
• Integrate the information system into its environment and
install the new system.
116

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
IMPLEMENTATION
Training
• The personnel in the system must know in detail
what their roles will be, how they can use the
system, and what the system will or will not do.
The success or failure of well-designed and
technically elegant systems can depend on the
way they are operated and used.
117

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
IMPLEMENTATION
Training
• The personnel in the system must know in detail
what their roles will be, how they can use the
system, and what the system will or will not do.
The success or failure of well-designed and
technically elegant systems can depend on the
way they are operated and used.
118

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
MAINTENANCE / SUPPORT
• Include all the activities such as phone support or physical
on-site support for users that is required once the system is
installing.
• Implement the changes that software might undergo over a
period of time, or implement any new requirements after
the software is deployed at the customer location.
• It also includes handling the residual errors and resolve any
issues that may exist in the system even after the testing
phase.
• Maintenance and support may be needed for a longer time
for large systems and for a short time for smaller systems.
119

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
SECURITY AND EVALUATION
System Audit
It is an investigation to review the performance of an operational
system. The objectives of conducting a system audit are as follows :
• To compare actual and planned performance.
• To verify that the stated objectives of system are still valid in current
environment.
• To evaluate the achievement of stated objectives.
• To ensure the reliability of computer based financial and other
information.
• To ensure all records included while processing.
• To ensure protection from frauds.
120

SYSTEM DEVELOPMENT
LIFE CYCLE (SDLC)
SECURITY
System security refers to protecting the system from theft,
unauthorized access and modifications, and accidental or
unintentional damage. In computerized systems, security involves
protecting all the parts of computer system which includes data,
software, and hardware. Systems security includes system privacy
and system integrity.
System privacy deals with protecting individuals systems from
being accessed and used without the permission/knowledge of
the concerned individuals.
System integrity is concerned with the quality and reliability of
raw as well as processed data in the system.
121

HOSPITAL
• The final management activity is the evaluation and control of
information technology in the organization.
• Does the organization obtain a return from its investment in
the technology?
• Are information systems under management’s control?
• Is the IS effort fragmented and uncoordinated?
122

Thank You
123

Hospital Information System

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Semelhante a Hospital Information System

Semelhante a Hospital Information System (20)

Último

Último (20)

Hospital Information System