A SYNOPSIS

TITLE: “ONLINE EMPLOYEE HEALTHCARE SYSTEM”

INTRODUCTION
We all want to build software that makes things better, avoiding the bad things that lurk in the
shadow of failed efforts. To succeed we need discipline when software is designed and built.
Many individuals and companies still develop software haphazardly, even as they build
systems to service the most advanced technologies of the day. As a result, the quality of the
software that we produce suffers and bad things happen.

This project report will be intended to serve as a guide to the software developed on
ONLINE EMPLOYEE HEALTHCARE SYSTEM. I will try to follow the principles and
rules as suggested by the software engineers as far as possible, in order to make this software
a Successful one.

The report will start with a comprehensive introduction to the project undertaken as its very
First Section. It includes objectives and scope of the project; about the front-end tool used i.e.
ASP.Net with C# and the back-end tool i.e. SQL Server. The second part presents and
discusses the theoretical background of the project. The third section encompasses all the
problems of the software that includes what is expected from the software, the demands and
the requirements of the end-users.

The fourth part is the System analysis and design section. This part focuses on requirements
analysis and specification, analysis issues, detailed procedures and the database designs. In
The fifth section, different approaches to formal evaluation and review techniques are
explored. The sixth section highlights the methodology adopted for this project. The seventh
part suggests the steps required to implement the software on the user machine. The eighth
part discusses the hardware and software requirements of the user machines. The ninth part
deals with the cost benefit analysis. The tenth section contains the data flow diagrams. The
next section is the flowchart part. The next section is for the entity relationship diagram of
the project. The thirteenth part explains the methodology used for testing. The fourteenth
section is the test report. The fifteenth part is the most important part of the project i.e. the
code for the software. The sixteenth part is the user manual section. The seventeenth part is
the annexure for the topic that includes some details about the organization, the data
dictionary, definitions, acronyms and abbreviations used in the report. The final section is the
reference part that contains a list of the books and reports that were referred during the
development of the project and the report as well.
The emphasis in this report is to document the important concepts and techniques used for
the successful development of this project.

I do hope fervently that, through this report, the readers will get a real picture of what the
project is all about. I also wish that may this software satisfies all the needs and requirements
of the organization, for which it is meant.

1
OBJECTIVES & SCOPE OF THE PROJECT
The objective of this software will be to completely automate the following process:

 This software will provide the health card for the patient. It will display a set of
information related to a patient regarding blood, urine, others.

 Provides information related to health and socio-economic data associated with

location wise so that these inputs can further be used to decide about the effectiveness
of the recommendations given to the patient.

 Provides different kinds of reports and analysis for the scientists, planners, doctor so
as to enable them for better decision making on different occasions.

 Provides excellent and easy to access means of communication medium between

doctors and its patients.

 To maintain and store diseases information for past few months.

 Provides as a comparison chart among different reports at different stages.

 This system will providing different types of tests reports

 Blood test
 Urine test
 Other tests

PROBLEM STATEMENT
A Health Care System is an online facility by which user/doctor can view the diagnose
information of a person related to his/her health for better analyzed medicine and medical
treatments.

 This system will help in disease management and preventive services. It will
provide very vital information like patients without an exam for certain time,
patient with certain levels BP, patients who are taking a certain class of medication,
patients who are suffering from a certain type of disease, screening and
immunization information, Lab tests Results, etc.

 Rules can be created for various time frames like a certain time period, last visit to
the hospital, latest Data available Visit, across all visits. The system is completely
dynamic in the sense; each user can have his own rule and his own conditions and
can decide if he wants to be alerted for the patient meeting the rule or for not .

2
NEED OF THE SOFTWARE
This software will develop keeping in mind the above-mentioned problems. The needs and
requirements of the end users are also kept in mind while designing this software. This
software will enable its users to maintain, retrieve and generate reports quickly and requiring
minimum effort.

Thus, ONLINE EMPLOYEE HEALTHCARE SYSTEM will develop in order to facilitate

it users to keep a track of case history regarding health status of Indian citizens. It also helps
them to save their time and energy when they want to retrieve some kind of information for
their specific purposes and needs.

METHODOLOGY

INTRODUCTION
A software life cycle is the series of identifiable stages that a Software product undergoes
during its lifetime. The first stage in the life Cycle of any software product is usually the
feasibility study stage. The Subsequent stages are: requirement analysis and specification,
design, coding, testing and maintenance. Each of these stages is called a life cycle Phase.

A life cycle model represents all the activities required to make a software product transit
through its life cycle phases. It also captures the order in which these activities are to be
undertaken. The most strict life cycle model used is the Classical Life Cycle Model.
However, in any practical software development work, it is not possible to strictly follow the
classical waterfall model from every phase to its preceding phases.

METHODOLOGY ADOPTED

 Structured system analysis techniques will be adopted for the analysis of the
algorithm and software development.

 Structured system design techniques will be adopted for the design of the algorithm
and software development.

 Prototyping model for initial implementation will be used for early testing and
module development.

 Prototyping model will be used for the development of the Graphical User Interface.

 Incremental Model will be used for the development of the software.

 Structured development life cycle will be used for this project.

 PERT chart is the primary Tool will be used for system planning.

3
  Project cost will be estimated as a function of comparing the cost of similar available
products, effort estimation on the project, resources acquired for the project and
COCOMO Model as the theoretical reference.

 Test plan will create to form the strategy of testing. This includes the decision of
testing techniques, decision of testing tools, and decision of milestones when the
testing will commence.

i) ANALYSIS METHODS

 Structured system analysis techniques will be used for the analysis of algorithm and
development.

 Background analysis: concept of mining and about the algorithm is learned through
research papers on Internet and experts theory.

 Fact-finding: facts about the algorithm will be collected from the books and Internet.

 Fact analysis: facts will analyze through different examples related to algorithm.

 DFDs and flowchart will be used to model the algorithm and logic design.

ii) DESIGN METHODS

 Structured design techniques will be used to design the software.

 An activity of all phases of a project is the walk-through. It is an interchange of

ideas among the team members. In design walk-through, the purpose is to
recognize as many problems in the software as possible while they are still “paper
tigers”

 Activity diagram will be used then to define the behavior of mechanism.

 Layering will be done to refine the architecture. Initially, two layers will be
introduced, system layer and application layer.

 Demo version will be created on these lines of design techniques to demonstrate

the feasibility of design methods.

 Database design will be according to the implementation of algorithms.

4
iii) CODING METHODS

 Event driven programming language ASP.Net will be used for coding the modules
and programs.

 Structured English and pseudo-codes will be used to closely refine the mechanisms
using the facility of defined objects.

 Various stubs will be used to facilitate incremental coding followed by testing.

 The basic philosophy followed at this stage:” code one line followed by rigorous
testing”.

 Integrated development environment of .Net will be used for the development of

various modules in integrated manner.

 Incremental compilation will be used to compile and test on which work was in
progress.

iv) TESTING METHODS

 Structured testing tools will be used for testing the programs.

 Small programs will be developed to test the individual modules.

 Each module will be tested by the development of appropriate functionality.

 Groups of people will be assigned to test the software functionality.

 The same group is responsible to test the reliability of software by using various
inputs and techniques, on various parts and functionalities.

 Software will be distributed to doctors and scientist to Beta-test the entire software.

PLATFORM USED

i) Health Care System Specification:

The system specification will be the final work produced by the system and requirements
engineer. It serves as the foundation for hardware engineering, software engineering,
database engineering and human engineering.

Once requirements will be gathered explore each requirements in relationship to others,

examine requirements for consistency, omissions and ambiguity.

5
ii) Hardware Specification
It is recommended that the minimum configuration for clients is as appended below:-
Suggested Configuration of Windows clients:-
Microprocessor : Pentium-2 class processor, 450 megahertz MHz)
Ram : 128 MB of RAM
Hard Disk : 2.5 gigabytes (GB) on installation drive, which includes 500
MB on system drive.
CD ROM Drive : 52 X CD ROM Drive

iii) Software Specifications

Operating System : Windows 2000XP/Windows 2000 NT
RDBMS : Sql Server 2005
Front End : Microsoft Visual Studio.NET with C#

LIMITATIONS
Below few points can be the limitations of this study.

 Provides no facility for Online Payment.

 No Online Chat or voice chats to doctors.
 The site only maintain records of people above 18 years of age, since in Login
process an individual is required to enter his/her name and voter id.

BIBLIOGRAPHY

BOOKS:

 ASP .Net By Peter Norton

 Mastering ASP.Net TECHMEDIA
 Learn ASP.Net in 21 days TMH
 Black book ASP.Net.

LIBRARY:
 MSDN
MSDN Library Visual Studio .Net release
The MSDN Library is the essential reference for developers, with more than a gigabyte of
technical programming information; including sample code, documentation, technical
articles, the Microsoft Developer Knowledge Base, and anything else we might need to
develop solutions that implement Microsoft technology.

WEBSITE:
www.apollohospital.com
www.ducatindia.com
www.ministryofhealth.com