Online Healthcare Clinic Management System

Generated by Foxit PDF Creator © Foxit Software
http://www.foxitsoftware.com For evaluation only.

Principles and Practices of Software Production [CE00003-2]
Online Healthcare Clinic Management System
Module Code [CE00003-2]
Date: 3 September 2009 Group No: - 6
Submitted To- Submitted By-

Mr. Virendra Srivastava Pankaj Manjhi (G.L) …………….PTL00782234
(Module lecturer) Sanjeev Kumar……………………..PTL00782219
Nagesh Trivedi………………………PTL007822
Vinay Kumar…………………………..PTL00782202
Asia-Pacific Institute of Information Technology Page 1

Table Of Content
Sl. No Page No
Topic
01 Introduction 03-05
01.1 Purpose 03
01.2 Scope 04
01.3 Technology To be Used 05
01.4 Objective of the proposed system 05
02 Problem Background 06
03 Proposed Solution 07
04 Schedule Planning 07
05 Selection of Methodology 08
06 Project Planning Control 09
07 Cost Estimanitation 10-11
08 Risk Management 12-13

Introduction
As we are preparing a system on Online Healthcare Clinic Management lets first see what s
does the word healthcare stands for, Health care (healthcare in American English), refers to
the treatment and management of illness, and the preservation of health through services
offered by the medical, dental, pharmaceutical, clinical laboratory sciences (in vitro
diagnostics), nursing, and allied health professions. Health care embraces all the goods and
services designed to promote health, including “preventive, curative and palliative
interventions, whether directed to individuals or to populations”
Health care systems are designed to meet the health care needs of target populations. There
are a wide variety of health care systems around the world. In some countries, the health care
system has evolved and has not been planned, whereas in others a concerted effort has been
made by governments, trade unions, charities, religious, or other co-ordinate bodies to deliver
planned health care services targeted to the populations they serve. However, health care
planning has often been evolutionary rather than revolutionary.
Purpose
Ø The Software is for the automation of Hospital Management.

Ø It maintains two levels of users:- Administrator Level and User Level
Ø The system includes:-
• Maintaining Patient details.
• Providing Prescription.
• Precautions and Diet advice.
• Providing and maintaining all kinds of tests for a patient.
• Billing and Report generation.

Scope
As Healthcare clinic is a registered private firm providing medical services to the patients around, it
can be used for maintaining patient details and their test results.
Technologies to be used
This project will be a desktop application to be developed in ASP.net having Ms Access as backend.
• Database Design (Ms Access)
• Form Design (ASP.net 2.0)
• Coding (ASP.net 2.0)
• Testing (ASP.net 2.0)
• Designing (Adobe Photoshop 7.0)
• DFD (Visio 2007)
• Gantt chart (Project 2007)
• Reporting Tool (Data Report)

Objective of proposed system
1. Planned approach towards working: - The working in the organization will be well
planned and organized. The data will be stored properly in database, which will help in
retrieval of information as well as its storage.
2. Accuracy: - The level of accuracy in the proposed system will be higher. All operation
would be done correctly and it ensures that whatever information is coming from the center is
accurate.
3. Reliability: - The reliability of the proposed system will be high due to accuracy and
planned working as the above stated reasons. The system is that now there would be proper
storage of information.
4. No Redundancy: - In the proposed system utmost care would be that no information is

repeated anywhere, in storage or otherwise. This would assure economic use of storage space
and consistency in the data stored.
5. Immediate retrieval of information: - The main objective of proposed system is to

provide for a quick and efficient retrieval of information. Any type of information would be
available whenever the user requires.
6. Immediate storage of information: - In manual system there are many problems to store
the largest amount of information.
7. Easy to Operate: - The system should be easy to operate and should be such that it can be
developed within a short period of time and fit in the limited budget of the user.

Problem Background
Healthcare clinic is providing medical services to the patients around New Delhi. A lot of
patients daily visits the Healthcare clinic and are facing problems regarding pre-appointments
and on the spot registrations. The administrative staff of the clinic is not able to keep and
locate the daily appointments and the history record details of the patients manually.
There are a small number of most significant problems in the current system as follows:-
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. Preparation of accurate and fast reports: - This becomes a difficult task to create fast
and accurate reports as information is difficult to collect from various registers.
3. Error in manual calculation: - Manual calculations may have error and take a lot of time
to calculate, this may result in incorrect information. For example calculation of patient’s
bill based on various treatments.

Proposed Solution
As there are many problems in manual system, the management of Healthcare clinic
decided to choose for a computerized online management system that can help them
to reduce the problems that the manual system currently they are running and also
trying for the better dealings with their patients by providing those expert services.
The proposed Online Management system will provide the following updated features
to their patients:
The old manual management system is to be replaced by Online Management system

including database.
1. Improved Manual System: - Proper person for proper work should be made
responsible so that a better efficiency could be achieved. This needs a lot of work
force. One of the alternative solutions is the improvement of the manual system.
Anything, which can be done manually, can be automated.
2. This system (OHCMS) provides online storage/ updations and retrieval facility. This
system promises very less or no paper work and also provides help to Doctor and
operational staff.
In this system everything is stored electronically so very less amount of paper
work is required and information can be retrieved very easily without searching
here and there into registers. This system is been discussed here.

SELECTION OF METHODOLGY
Hybrid of Waterfall and Spiral Model: Here we bring together best features of both
waterfall and spiral model. It insures well analysis of requirements and its documentation.
And also insures well rapid user-driven software delivery. It’s a useful methodology where
implementation is a prototype.
Reasons for choosing Waterfall model:
We have selected this model because:
o It has features of both waterfall and Spiral model.

o It fits well for our system, as we are developing a student level project.
o In early stages we will follow waterfall model for detailed requirement specification
and thereafter switch to spiral model for physical design and construction phases.
o So, our common approach will be to use a structured method for the requirements
analysis and specification stages and later we will switch upon more RAD based
approach, using prototyping for the incremental delivery of software.
o At student level, project is not to the standard as in professional software development
organization. Where intellectuals and resources are no any issue. Hence, this model is
a good approach in developing the required system.

PROJECT PLANNING CONTROL
Project control is based on creating a proper plan, and creating the proper plan means having
a clear understanding of what it takes to achieve that control. Using a project control model,
this course shows that effective project management depends on the appropriate execution of
activities such as estimating, planning, resourcing, communicating, reporting, and
documenting.
The main purpose of the project planning is that people who are involved in this project are
able to create and modify a project plan, and produce project progress reports.
The project consists of various activities such as patient services, doctors’ service,
transactional services and report section.

COST ESTIMATION
Cost Estimation is a part of a system budgeting and accounting practices which helps
the system analyst to determine the approximate cost and savings for an organization
It basically includes judgment the hardware and the software cost of the system.
Ø Hardware
• Computer (Minimum configuration- Intel Pentium Processor, 1 G.B. RAM, 60 G.B
hard disk, Windows vista O.S.) – Rs-26,000 X 4 = 1, 40,000
Ø Software
• MS Windows XP Pro = 7200
• Visual Studio (for ASP .NET 2.0) = 8000
• MS Office (for Visio 07, Project 07, Word 07, Access 07)= 6800
Ø Operational Cost
• System Maintenance = 1500 per month
• Communication Expenses = 1000 per month
• Salary = 10000 X 4 = 40000 per month
Ø Travel and training costs

This involves the measure of the rate at which individual engineers involved in
software development to produce software and associated documentation.
There is no simple way to make an accurate estimate of the effort required to develop a
software system. Initial estimates are based on inadequate information in a user requirements
definition; Project cost estimates may be self-fulfilling.

The Constructive Cost Model (COCOMO) is an Algorithmic Cost Model. There are
four steps to be taken to compute the estimated cost.
Step 1: Calculated Information Domain Value to define the complexity of the project
(Unadjusted Function Point Count)
The Information Domain Value Table entries are-
• External inputs: Those items provided by the user that describe distinct application-
oriented data (such as file names and menu selections)
• External outputs: Those items provided to the user that generate distinct application-
oriented data (such as reports and messages, rather than the individual components of
these)
• External enquiries: Interactive inputs requiring a response
• External files: Machine-readable interfaces to other systems
• Internal files: Logical master files in the system
Step 2: Calculation of ‘Complexity adjustment values’ based on responses to the questions

Technical Complexity Factor
Complexity Weighting Factors
FP = UFC x TCF (VAF*)
Where: UFC – Average-Unadjusted Function Point Count
TCF - Technical Complexity Factor
Step 3:-Calculating the lines of code by choosing the programming language used in
developing the project.
– LOC = AVC * number of function points;

Where, Object Oriented Languages (AVC Average Line of code)
Step 4:-Finding out the complexity of the software project.

RISK MANAGEMENT
Risk: - Many problems we come across while developing a software project. A risk is
something that may happen and if it does, it will have an adverse impact on the project. A
risk is the probability of loss or something bad which can happen to the project. Secondly we
can consider that it will have an adverse impact because if not then it is not termed as a risk.
A risk implies a probability of between 0 to 100%. Especially in software world it is
important because most of the software after it has been destroyed; it was found that it could
have been solved if the reason would have been found earlier.
Risk Management: - Basically, risk management is the sum of all proactive management-
directed activities within a program that are intended to acceptably accommodate the
possibility of failures in elements of the program. To identify, address & eliminate risk items
before they become either threats to successful software operation or major sources of
software rework.
.
Ø Risk Management Plan: - There are four stages to risk management planning. They
are: ·
• Risk Identification
In this stage, we identify and name the risks. The best approach is a meeting
with business and IT people to carry out the identification. We may say that it is a
combination of brainstorming and reviewing of standard risk lists.
There are different sorts of risks and we need to decide on a project by project
basis what to do about each type.
Risks may be defined in two parts. The first is the cause of the situation
(Vendor not meeting deadline, Business users not available, etc.). The second part is
the impact (Budget will be exceeded, Milestones not achieved, etc.).
• Risk Response
There are four things which you can do about a risk. They are: -
Avoid the risk: Use an alternate approach that does not have any risk, but this
is not a sure option for always. However, this is the most effective risk management
technique if it can be applied.
Transfer the risk: An attempt to pass the risk to another program element. This
means that anyone else can be made responsible for that risk.

Mitigate the risk: Take actions to reduce the impact or chance of the risk
occurring. If the risk relates to availability of resources, draw up an agreement and get
sign-off for the resource to be available.
Accept the risk: The risk might be so small the effort to do anything is not
worthwhile. In these cases we can accept the risk and carry on our work as it is.
• Risk Monitoring and Control
The final step is to continually monitor risks to identify any change in the
status, or if they turn into an issue. It is best to hold regular risk reviews to identify
actions outstanding, risk probability and impact, remove risks that have passed, and
identify new risks.

Online Healthcare Clinic Management System

Uploaded by

Document Information

Original Description:

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

Online Healthcare Clinic Management System

Uploaded by

Copyright:

Available Formats

Generated by Foxit PDF Creator © Foxit Software

http://www.foxitsoftware.com For evaluation only.

Online Healthcare Clinic Management System

Module Code [CE00003-2]

Date: 3 September 2009 Group No: - 6

Submitted To- Submitted By-

(Module lecturer) Sanjeev Kumar……………………..PTL00782219

Asia-Pacific Institute of Information Technology Page 1

01.3 Technology To be Used 05

01.4 Objective of the proposed system 05

06 Project Planning Control 09

07 Cost Estimanitation 10-11

08 Risk Management 12-13

Asia-Pacific Institute of Information Technology Page 2

Ø The Software is for the automation of Hospital Management.

Asia-Pacific Institute of Information Technology Page 3

• Database Design (Ms Access)

• Form Design (ASP.net 2.0)

• Coding (ASP.net 2.0)

• Testing (ASP.net 2.0)

• Designing (Adobe Photoshop 7.0)

• DFD (Visio 2007)

• Gantt chart (Project 2007)

• Reporting Tool (Data Report)

Asia-Pacific Institute of Information Technology Page 4

Objective of proposed system

4. No Redundancy: - In the proposed system utmost care would be that no information is

5. Immediate retrieval of information: - The main objective of proposed system is to

Asia-Pacific Institute of Information Technology Page 5

Asia-Pacific Institute of Information Technology Page 6

The old manual management system is to be replaced by Online Management system

Asia-Pacific Institute of Information Technology Page 7

Reasons for choosing Waterfall model:

We have selected this model because:

o It has features of both waterfall and Spiral model.

Asia-Pacific Institute of Information Technology Page 8

PROJECT PLANNING CONTROL

Asia-Pacific Institute of Information Technology Page 9

Ø Travel and training costs

Asia-Pacific Institute of Information Technology Page 10

The Information Domain Value Table entries are-

Step 2: Calculation of ‘Complexity adjustment values’ based on responses to the questions

Complexity Weighting Factors

FP = UFC x TCF (VAF*)

Where: UFC – Average-Unadjusted Function Point Count

TCF - Technical Complexity Factor

– LOC = AVC * number of function points;

Step 4:-Finding out the complexity of the software project.

Asia-Pacific Institute of Information Technology Page 11

Asia-Pacific Institute of Information Technology Page 12

• Risk Monitoring and Control

Asia-Pacific Institute of Information Technology Page 13

You might also like