You are on page 1of 28

ABSTRACT

New technologies have improved the ability of electronically storing, transferring and sharing
medical data also changed. At the same time, they also create serious questions about who has
access to this information and how they are protected. The aim of PIS is to store the detailed
information about the Patient like treatment details, date of joining and allocated doctor. The major
modules in this system are allocating the bed, allocating the doctor to the patient.

Features:
Knowing the patient details and patient status
To know the type of treatment he/ she undergoing.
To know the consulted doctor details, his / her visiting hours.
To know the information about the doctors included and deleted.
It allows adding / editing patient registration.
To know the list of doctors available
To know the total list of beds available
INTRODUCTION

This software can be used to keep track of the patients registering in a hospital or clinic also, this
system supports accessing the previous visit histories of any patient, search for patients by name
and other properties etc. This system involves three people’s patient, doctor and receptionist. It is
useful to know the details of consulted doctor details and status of patient who is undergoing
treatment under this doctor. To know the treatment details provided by the doctor.
Patient has registered with the system automatically admitted into the hospital. After login we can
know the patient details by patient id. Then they come to know the patient status by doctor and
bed.
And third and most important member in this system is Receptionist. He is the administrator of
the system. He / she can add or delete the doctor and bed. He allocates the bed and doctor to the
patient. And also he edits and updates the details of the doctor and bed in the system.
Features:
This is totally intranet based system. It maintains the records of patients from starting.
To view the case sheet of patient and details of doctor and bed..
Knowing the previous histories of patients
To know the patient status by doctor and bed
To know the details doctors are in the floor.
Allocation details of doctors and beds.

SYSTEM:
· Designing and implementing the new links.
· Designing and implementing the users.
· Arranging new links as subject wise.
EXISTING SYSTEM
Generally there is a lot of work for maintaining records in the hospital. In olden days all these work
done in the papers which takes lot of time for analyzing the information like availability of
the staff and their timings, number of patients, the treatment provided, and prescription.
They also want to generate periodic reports for analysis .There may be a chance to loss the
data also.

DRAWBACKS
 It takes lot of time for analyzing.
 There may be a chance to loss the information.
 Management has to face a lot of problems while providing periodic reports.

PROPOSED SYSTEM
In this paper, the main goal of the software is to build a good management tool. The main
purpose of this software is to reduce the time taken through manual system in order to maintain all
the records. The Hospital Management software is mainly used by 2 types of user’s i.e. Admin and
Receptionist. Admin has the full Access to the software whereas Receptionist has only limited
Access. Software starts with a login form where Admin can login by entering the username and
corresponding password. If the user name and password matches then ADMIN is directed to the
Admin Master page and Receptionist will be directed to User Master Page.

Advantages

o It reduces the time taken through manual system in order to maintain all the records.
o The management operations are going in a perfect manner.

MODULES

Two Modules

1. USER

2. ADMIN

3. HOSPITAL MANAGEMENT

USER:

In this module first User can register the details using some required details like username,
password, email, phone, etc... After that user can login using username and password otherwise
some message will be printed please enter required details. User can take appointment, if user is
already once taking the appointment that particular patient patient went to old patient.then click
on the old patient button it will ask patient id and name of the patient.after entering the patient id
and name it will display all the details of particular details.if you want to take appointment click
on taking appointment button it will open small promt then you entered why you are taking
appointment and when you want to take appointment.

ADMIN :

In this module first admin login by using username and password..after login admin can view
patient information and hospital management information, and admin can give accessing
permissions to particular hospital.

Hospital management:

In this module first register,then login by using username and password. After login hospital
management view the patients who are taking the appintment and patient rooms alloting. They can
manage all patient details.
 SYSTEM DESIGN
 UML DIAGRAMS:
 UML represents Unified Modeling Language. UML is an institutionalized universally
useful showing dialect in the subject of article situated programming designing. The
fashionable is overseen, and become made by way of, the Object Management Group.
 The goal is for UML to become a regular dialect for making fashions of item arranged PC
programming. In its gift frame UML is contained two noteworthy components: a Meta-
show and documentation. Later on, a few type of method or system can also likewise be
brought to; or related with, UML.
 The Unified Modeling Language is a popular dialect for indicating, Visualization,
Constructing and archiving the curios of programming framework, and for business
demonstrating and different non-programming frameworks.
 The UML speaks to an accumulation of first-rate building practices which have verified
fruitful in the showing of full-size and complicated frameworks.
 The UML is a essential piece of creating gadgets located programming and the product
development method. The UML makes use of commonly graphical documentations to
specific the plan of programming ventures.
 GOALS:
 The Primary goals inside the plan of the UML are as in step with the subsequent:
 1. Provide clients a prepared to-utilize, expressive visual showing Language on the
way to create and change massive models.
 2. Provide extendibility and specialization units to make bigger the middle ideas.
 3. Be free of specific programming dialects and advancement manner.
 4. Provide a proper cause for understanding the displaying dialect.
 5. Encourage the improvement of OO gadgets exhibit.
 6. Support large amount advancement thoughts, for example, joint efforts, systems,
examples and components.
 7. Integrate widespread procedures.
 USE CASE DIAGRAM:

 A use case diagram in the Unified Modeling Language (UML) is a type of behavioral
diagram defined by and created from a Use-case analysis. Its purpose is to present a
graphical overview of the functionality provided by a system in terms of actors, their goals
(represented as use cases), and any dependencies between those use cases. The main
purpose of a use case diagram is to show what system functions are performed for which
actor. Roles of the actors in the system can be depicted.

registeration login
view profile

doctor
add doctor
heart analysis
add precautions to diseases

dangue,maleria,typhoid view user details

user
admin

view doctor details


view doctor

model performance

logout


 CLASS DIAGRAM:
 In software engineering, a class diagram in the Unified Modeling
Language (UML) is a type of static structure diagram that describes the structure of a
system by showing the system's classes, their attributes, operations (or methods), and the
relationships among the classes. It explains which class contains information.


 SEQUENCE DIAGRAM:
 A sequence diagram in Unified Modeling Language (UML) is a kind of interaction diagram
that shows how processes operate with one another and in what order. It is a construct of a
Message Sequence Chart. Sequence diagrams are sometimes called event diagrams, event
scenarios, and timing diagrams.

user system admin doctor

login

registration

add doctors

login login

view user details

view profile

view docor detais


add precautions to diseases

heart analysis

Dengue, Malaria,Thyphoid

view doctor

logout

logout

logout



 COLLABORATION DIAGRAM:

 In collaboration diagram the method call sequence is indicated by some numbering


technique as shown below. The number indicates how the methods are called one after
another. We have taken the same order management system to describe the collaboration
diagram. The method calls are similar to that of a sequence diagram. But the difference is
that the sequence diagram does not describe the object organization where as the
collaboration diagram shows the object organization.

doctor

5: login
7: view profile
9: add precautions to diseases
13: logout
2: registration
4: login
10: heart analysis
11: Dengue, Malaria,Thyphoid
12: view doctor
14: logout
user system admin

1: login
3: add doctors
6: view user details
8: view docor detais
15: logout



 ACTIVITY DIAGRAM:
 Activity diagrams are graphical representations of workflows of stepwise activities and
actions with support for choice, iteration and concurrency. In the Unified Modeling
Language, activity diagrams can be used to describe the business and operational step-by-
step workflows of components in a system. An activity diagram shows the overall flow of
control.

user doctor
admin

registration login
login

login
add doctors

heart analysis view profile


view user details

dengue,maleria,typhoid view doctor details

add precautions to diseases


view doctor model performance

logout



 COMPONENT DIAGRAM:
 Component diagrams are used to describe the physical artifacts of a system. This artifact
includes files, executables, libraries etc. So the purpose of this diagram is different,
Component diagrams are used during the implementation phase of an application. But it is
prepared well in advance to visualize the implementation details. Initially the system is
designed using different UML diagrams and then when the artifacts are ready component
diagrams are used to get an idea of the implementation.

user

system doctor

admin



 DEPLOYMENT DIAGRAM:
 Deployment diagram represents the deployment view of a system. It is related to the
component diagram. Because the components are deployed using the deployment
diagrams. A deployment diagram consists of nodes. Nodes are nothing but physical hard
ware’s used to deploy the application.
 .

doctor

user system admin

databas
e

Software Environment

Java Technology

Python is an interpreted, high-level, general-purpose programming language. Created by Guido


van Rossum and first released in 1991, Python has a design philosophy that emphasizes code
readability, notably using significant whitespace. It provides constructs that enable clear
programming on both small and large scales.Van Rossum led the language community until
stepping down as leader in July 2018.

Python features a dynamic type system and automatic memory management. It supports multiple
programming paradigms, including object-oriented, imperative, functional and procedural, and
has a large and comprehensive standard library.
The Java Programming Language
The Java programming language is a high-level language that can be characterized by all
of the following buzzwords:
 Simple
 Architecture neutral
 Object oriented
 Portable
 Distributed
 High performance
 Interpreted
 Multithreaded
 Robust
 Dynamic
 Secure

Python is meant to be an easily readable language. Its formatting is visually uncluttered, and it
often uses English keywords where other languages use punctuation. Unlike many other
languages, it does not use curly brackets to delimit blocks, and semicolons after statements are
optional. It has fewer syntactic exceptions and special cases than C or Pascal.

Indentation

Python uses whitespace indentation, rather than curly brackets or keywords, to delimit blocks. An
increase in indentation comes after certain statements; a decrease in indentation signifies the end
of the current block. Thus, the program's visual structure accurately represents the program's
semantic structure.This feature is also sometimes termed the off-side rule.

Statements and control flow

 The assignment statement (token '=', the equals sign). This operates differently than in
traditional imperative programming languages, and this fundamental mechanism (including
the nature of Python's version of variables) illuminates many other features of the language.
Assignment in C, e.g., x = 2, translates to "typed variable name x receives a copy of numeric
value 2". The (right-hand) value is copied into an allocated storage location for which the (left-
hand) variable name is the symbolic address. The memory allocated to the variable is large
enough (potentially quite large) for the declared type. In the simplest case of Python
assignment, using the same example, x = 2, translates to "(generic) name x receives
a reference to a separate, dynamically allocated object of numeric (int) type of value 2." This
is termed binding the name to the object. Since the name's storage location doesn't contain the
indicated value, it is improper to call it a variable. Names may be subsequently rebound at any
time to objects of greatly varying types, including strings, procedures, complex objects with
data and methods, etc. Successive assignments of a common value to multiple names, e.g., x
= 2; y = 2; z = 2result in allocating storage to (at most) three names and one numeric object,
to which all three names are bound. Since a name is a generic reference holder it is unreasonable
to associate a fixed data typewith it. However at a given time a name will be bound
to some object, which will have a type; thus there is dynamic typing.
 The if statement, which conditionally executes a block of code, along with else and elif (a
contraction of else-if).
 The for statement, which iterates over an iterable object, capturing each element to a local
variable for use by the attached block.
 The while statement, which executes a block of code as long as its condition is true.
Flask Framework:

Flask is a micro web framework written in Python. It is classified as


a microframework because it does not require particular tools or libraries (except for some basics
standard libraries such as bottom.py ).It has no database abstraction layer, form validation, or any
other components where pre-existing third-party libraries provide common functions. However,
Flask supports extensions that can add application features as if they were implemented in Flask
itself. Extensions exist for object-relational mappers, form validation, upload handling, various
open authentication technologies and several common framework related tools. Extensions are
updated far more regularly than the core Flask program.Flask is commonly used with MongoDB,
which gives it more control over databases and history.

Features:

 Contains development server and debugger


 Integrated support for unit testing
 RESTful request dispatching
 Uses Jinja2 templating
 Support for secure cookies (client side sessions)
 100% WSGI 1.0 compliant
 Unicode-based
 Extensive documentation
 Google App Engine compatibility
 Extensions available to enhance features desired

Structure:

from flask import Flask


app = Flask(__name__)

@app.route("/")
def hello():
return "Hello World!"

if __name__ == "__main__":
app.run()

Pycharm plateform:
PyCharm is an integrated development environment (IDE) used in computer
programming, specifically for the Python language. It is developed by the Czech
company JetBrains.It provides code analysis, a graphical debugger, an integrated unit tester,
integration with version control systems (VCSes), and supports web development with Django.

PyCharm is cross-platform, with Windows, macOS and Linux versions. The Community Edition
is released under the Apache License,and there is also Professional Edition with extra features,
released under a proprietary license.

Features:

 Coding assistance and analysis, with code completion, syntax and error highlighting, linter
integration, and quick fixes
 Project and code navigation: specialized project views, file structure views and quick jumping
between files, classes, methods and usages
 Python refactoring: including rename, extract method, introduce variable, introduce constant,
pull up, push down and others
 Support for web frameworks: Django, web2py and Flask
 Integrated Python debugger
SQL SERVER

DATABASE
A database management, or DBMS, gives the user access to their data and helps them
transform the data into information. Such database management systems include dBase, paradox,
IMS, Sql Server and SQL Server. These systems allow users to create, update and extract
information from their database.

A database is a structured collection of data. Data refers to the characteristics of people,


things and events. SQL Server stores each data item in its own fields. In SQL Server, the fields
relating to a particular person, thing or event are bundled together to form a single complete unit
of data, called a record (it can also be referred to as raw or an occurrence). Each record is made
up of a number of fields. No two fields in a record can have the same field name.

SQL Server Tables


SQL Server stores records relating to each other in a table. Different tables are created for
the various groups of information. Related tables are grouped together to form a database.

Advantages of RDBMS
Redundancy can be avoided
Inconsistency can be eliminated
Data can be Shared
Standards can be enforced
Security restrictions ca be applied
Integrity can be maintained
Conflicting requirements can be balanced
Data independence can be achieved.
Disadvantages of DBMS

A significant disadvantage of the DBMS system is cost. In addition to the cost of


purchasing of developing the software, the hardware has to be upgraded to allow for the extensive
programs and the workspace required for their execution and storage. While centralization reduces
duplication, the lack of duplication requires that the database be adequately backed up so that in
case of failure the data can be recovered.

FEATURES OF SQL SERVER (RDBMS)


SQL SERVER is one of the leading database management systems (DBMS) because it is
the only Database that meets the uncompromising requirements of today’s most demanding
information systems. From complex decision support systems (DSS) to the most rigorous online
transaction processing (OLTP) application, even application that require simultaneous DSS and
OLTP access to the same critical data, SQL Server leads the industry in both performance and
capability.

HTML
HTML stands for Hyper Text Markup Language, which is the most widely used language on
Web to develop web pages. HTML was created by Berners-Lee in late 1991 but "HTML 2.0" was
the first standard HTML specification which was published in 1995. HTML 4.01 was a major
version of HTML and it was published in late 1999. Though HTML 4.01 version is widely used
but currently we are having HTML-5 version which is an extension to HTML 4.01, and this
version was published in 2012.

 Hypertext refers to the way in which Web pages (HTML documents) are linked together.
Thus the link available on a webpage is called Hypertext.

 As its name suggests, HTML is a Markup Language which means you use HTML to
simply "mark up" a text document with tags that tell a Web browser how to structure it to
display.

Originally, HTML was developed with the intent of defining the structure of documents like
headings, paragraphs, lists, and so forth to facilitate the sharing of scientific information between
researchers.

These are some basic tags of html


Tag Description

<!DOCTYPE...> This tag defines the document type and HTML version.

<html> This tag encloses the complete HTML document and mainly comprises
of document header which is represented by <head>...</head> and
document body which is represented by <body>...</body> tags.

<head> This tag represents the document's header which can keep other HTML
tags like <title>, <link> etc.

<title> The <title> tag is used inside the <head> tag to mention the document
title.

<body> This tag represents the document's body which keeps other HTML tags
like <h1>, <div>, <p> etc.

<h1> This tag represents the heading.

<p> This tag represents a paragraph.

SYSTEM REQUIREMENTS

H/W System Configuration:-


 Processor - I3/Intel Processor
 RAM - 4GB (min)
 Hard Disk - 160GB
 Key Board - Standard Windows Keyboard
 Mouse - Two or Three Button Mouse
 Monitor - SVGA

S/W System Configuration:-


 Operating System : Windows 7/8/10
 Front End : HTML,CSS, BOOTSRAP

 Scripts : JavaScript, Jquery

 Server side Script : Python

 Database : My SQL 6.0

2. SYSTEM STUDY

FEASIBILITY STUDY

The feasibility of the project is analyzed in this phase and business proposal is put

forth with a very general plan for the project and some cost estimates. During system analysis

the feasibility study of the proposed system is to be carried out. This is to ensure that the

proposed system is not a burden to the company. For feasibility analysis, some

understanding of the major requirements for the system is essential.

Three key considerations involved in the feasibility analysis are

 ECONOMICAL FEASIBILITY

 TECHNICAL FEASIBILITY

 SOCIAL FEASIBILITY

ECONOMICAL FEASIBILITY
This study is carried out to check the economic impact that the system will have on the

organization. The amount of fund that the company can pour into the research and development of the

system is limited. The expenditures must be justified. Thus the developed system as well within the budget

and this was achieved because most of the technologies used are freely available. Only the customized

products had to be purchased.

TECHNICAL FEASIBILITY

This study is carried out to check the technical feasibility, that is, the technical requirements

of the system. Any system developed must not have a high demand on the available technical resources.

This will lead to high demands on the available technical resources. This will lead to high demands being

placed on the client. The developed system must have a modest requirement, as only minimal or null

changes are required for implementing this system.

SOCIAL FEASIBILITY

The aspect of study is to check the level of acceptance of the system by the user. This includes the

process of training the user to use the system efficiently. The user must not feel threatened by the system,

instead must accept it as a necessity. The level of acceptance by the users solely depends on the methods

that are employed to educate the user about the system and to make him familiar with it. His level of

confidence must be raised so that he is also able to make some constructive criticism, which is welcomed,

as he is the final user of the system.

6. SYSTEM TESTING
Testing is the process of detecting errors. Testing performs a very critical role for quality
assurance and for ensuring the reliability of software. The results of testing are used later on during
maintenance also

Psychology of Testing
The aim of testing is often to demonstrate that a program works by showing that it has no errors.
The basic purpose of testing phase is to detect the errors that may be present in the program. Hence
one should not start testing with the intent of showing that a program works, but the intent should
be to show that a program doesn’t work.
Testing is the process of executing a program with the intent of finding errors.

Testing Objectives:
The main objective of testing is to uncover a host of errors, systematically and with minimum
effort and time. Stating formally, we can say,
Testing is a process of executing a program with the intent of finding an error.
A successful test is one that uncovers an as yet undiscovered error.
A good test case is one that has a high probability of finding error, if it exists.
The tests are inadequate to detect possibly present errors.
The software more or less confirms to the quality and reliable standards.

LEVELS OF TESTING
In order to uncover the errors present in different phases we have the concept of levels of testing.
The basic levels of testing are

A series of testing is done for the proposed system before the system is ready for the user
acceptance testing.
The steps involved in Testing are:

Unit Testing:
Unit testing focuses verification efforts on the smallest unit of the software design, the module.
This is also known as “Module Testing”. The modules are tested separately. This testing carried
out during programming stage itself. In this testing each module is found to be working
satisfactorily as regards to the expected output from the module.

Integration Testing:
Data can be grossed across an interface; one module can have adverse efforts on another.
Integration testing is systematic testing for construction the program structure while at the same
time conducting tests to uncover errors associated with in the interface. The objective is to take
unit tested modules and build a program structure. All the modules are combined and tested as a
whole. Here correction is difficult because the isolation of cause is complicate by the vast expense
of the entire program. Thus in the integration testing stop, all the errors uncovered are corrected
for the text testing steps.

System testing:
System testing is the stage of implementation that is aimed at ensuring that the system works
accurately and efficiently for live operation commences. Testing is vital to the success of the
system. System testing makes a logical assumption that if all the parts of the system are correct,
then goal will be successfully achieved.

The four major system testing are


i. Recovery Testing
ii. Security Testing
iii. Stress Testing
iv. Performance Testing

RECOVERY TESTING
Recovery testing is a system test that forces the software to fail in a variety of ways and verifies
that recovery is properly performed. If recovery is automatic, re-initialization, checkpoint
mechanisms, data recovery, and restart are each evaluated for correctness. If recovery requires
human intervention, the mean time to repair is evaluated to determine whether it is within
acceptable limits.

SECURITY TESTING
Security testing attempts to verify that protection mechanisms built into a system will, in fact,
protect it from improper penetration. During security testing, the tester plays the role of the
individual who desire to penetrate the system. Given enough time and resources, good security
testing will ultimately penetrate a system. The role of the system designer is to make penetration
cost more than the value of the information that will be obtained.

STRESS TESTING
During earlier software testing steps, white box and black box techniques resulted in a thorough
evaluation of normal program functions and performance. Stress tests are designed to confront
programs with abnormal situations.

PERFORMANCE TESTING
For real-time and embedded systems, software that provides required function but does not
confirm to performance requirements is unacceptable. Performance testing is designed to test the
run-time performance of software within the context of an integrated system. Performance testing
occurs throughout all steps in the testing process.
Performance tests are sometimes coupled with stress testing and often require both hardware and
software instrumentation. That is, it is often necessary to measure resource utilization. By
instrumenting a system, the tester can uncover situations that lead to degradation and possible
system failure.

Validation Testing:
At the conclusion of integration testing software is completely assembled as a package, interfacing
errors have been uncovered and corrected and a final series of software tests begins, validation test
begins. Validation test can be defined in many ways. But the simple definition is that validation
succeeds when the software function in a manner that can reasonably expected by the customer.
After validation test has been conducted one of two possible conditions exists.

One is the function or performance characteristics confirm to specifications and are accepted and
the other is deviation from specification is uncovered and a deficiency list is created. Proposed
system under consideration has been tested by using validation testing and found to be working
satisfactorily.

Output Testing:
After performing validation testing, the next step is output testing of the proposed system
since no system could be useful if it does not produce the required output in the

specified format. Asking the users about the format required by them tests the outputs generated
by the system under consideration. Here the output format is considered in two ways, one is on the
screen and other is the printed format. The output format on the screen is found to be correct as
the format was designed in the system designed phase according to the user needs. For the hard
copy also the output comes as the specified requirements by the users. Hence output testing does
not result any corrections in the system.

User Acceptance Testing:


User acceptance of a system is the key factor of the success of any system. The system under study
is tested for the user acceptance by constantly keeping in touch with the prospective system users
at the time of developing and making changes wherever required.

Test Data:
Taking various kinds of test data does the above testing. Preparation of test data plays a vital role
in the system testing after preparing the test data the system under study is tested using the test
data. While testing the system by using the test data errors are again uncovered and corrected by
using above testing steps and corrections are also noted from the future use.

Testing:
The testing done here was System Testing–checking whether the user requirements
were satisfied. The code for the new system has been written completely using JSP as the coding
language, HTML as the interface for front-end designing and Java Script for validating the client-
side applications. The new system has been tested well with the help of the users and all the
applications have been verified from every nook and corner of the user.
Although some applications were found to be erroneous these applications have been
corrected before being implemented. The flow of the forms has been found to be very much in
accordance with the actual flow of data.

Test Results: All the test cases mentioned above passed successfully. No defects encountered.

INPUT DESIGN

The input design is the link between the information system and the user. It comprises the developing
specification and procedures for data preparation and those steps are necessary to put transaction data
in to a usable form for processing can be achieved by inspecting the computer to read data from a written
or printed document or it can occur by having people keying the data directly into the system. The design
of input focuses on controlling the amount of input required, controlling the errors, avoiding delay,
avoiding extra steps and keeping the process simple. The input is designed in such a way so that it provides
security and ease of use with retaining the privacy. Input Design considered the following things:

 What data should be given as input?


 How the data should be arranged or coded?
 The dialog to guide the operating personnel in providing input.
 Methods for preparing input validations and steps to follow when error occur.
OBJECTIVES

1. Input Design is the process of converting a user-oriented description of the input into a computer-based
system. This design is important to avoid errors in the data input process and show the correct direction
to the management for getting correct information from the computerized system.

2. It is achieved by creating user-friendly screens for the data entry to handle large volume of data. The
goal of designing input is to make data entry easier and to be free from errors. The data entry screen is
designed in such a way that all the data manipulates can be performed. It also provides record viewing
facilities.

3. When the data is entered it will check for its validity. Data can be entered with the help of screens.
Appropriate messages are provided as when needed so that the user will not be in maize of instant. Thus
the objective of input design is to create an input layout that is easy to follow

OUTPUT DESIGN

A quality output is one, which meets the requirements of the end user and presents the information
clearly. In any system results of processing are communicated to the users and to other system through
outputs. In output design it is determined how the information is to be displaced for immediate need and
also the hard copy output. It is the most important and direct source information to the user. Efficient and
intelligent output design improves the system’s relationship to help user decision-making.

1. Designing computer output should proceed in an organized, well thought out manner; the right output
must be developed while ensuring that each output element is designed so that people will find the
system can use easily and effectively. When analysis design computer output, they should Identify the
specific output that is needed to meet the requirements.

2. Select methods for presenting information.

3. Create document, report, or other formats that contain information produced by the system.

The output form of an information system should accomplish one or more of the following objectives.

 Convey information about past activities, current status or projections of the


 Future.
 Signal important events, opportunities, problems, or warnings.
 Trigger an action.
 Confirm an action.

 CONCLUSION

 It can be seen that deploying IT can help the medical profession in improving its quality of
service and thus automatically increasing the preparedness and defensiveness. It is of vital
importance that the software must have the right type of modularity and openness so that
it is manageable, maintainable and upgradeable. The hardware should be reliable, available
and have the necessary performance capacity.

REFERENCES

1) https://en.wikipedia.org/wiki/Cardiovascular_disease.
2) http://www.heart.org/HEARTORG/Conditions/HeartAttack/WarningSignsofa
HeartAttack/Warning-Signs-of-
aHeartAttack_UCM_002039_Article.jsp#.WNpKgPl97IU.
3) www.who.int/cardiovascular_diseases/en/. http://food.ndtv.com/health/world-heart-
day-2015-heart-disease-in-india-is-agrowing-concern-ansari-1224160.
4) Shaikh Abdul Hannan, A.V. Mane, R. R. Manza,and R. J. Ramteke, Dec
2010,“Prediction of Heart Disease Medical Prescription using Radial Basis
Function”,IEEE International Conference on Computational Intelligence and
Computing Research (ICCIC), DOI: 10.1109/ICCIC.2010.5705900 ,28-29 .
5) AH Chen, SY Huang, PS Hong, CH Cheng, and EJ Lin,2011, “HDPS: Heart Disease
Prediction System”,Computing in Cardiology, ISSN: 0276-6574, pp.557- 560.
6) Mrudula Gudadhe, Kapil Wankhade, and Snehlata Dongre, Sept 2010,“Decision
Support System for Heart Disease Based on Support Vector Machine and Artificial
Neural Network”,International Conference on Computer and Communication
Technology (ICCCT),DOI:10.1109/ICCCT.2010.5640377, 17-19.
7) Manpreet Singh, Levi Monteiro Martins, Patrick Joanis, and Vijay K. Mago,2016,
“Building a Cardiovascular Disease Predictive Model using Structural Equation Model
& Fuzzy Cognitive Map”,IEEE International Conference on Fuzzy Systems
(FUZZ),pp. 1377-1382.
8) "Health Topics: Health Systems". www.who.int. WHO World Health Organization.
Retrieved 2013-11-24.
9) "Health at a Glance 2013 - OECD Indicators" (PDF). OECD. 2013-11-21. pp. 5, 39,
46, 48. (link). Retrieved 2013-11-24.
10) "OECD.StatExtracts, Health, Health Status, Life expectancy, Total population at birth,
2011" (online statistics). stats.oecd.org/. OECD's iLibrary. 2013. Retrieved 2013-11-
24.
11) World Health Organization. Anniversary of smallpox eradication. Geneva, 18 June
2010.
12) United States Department of Labor. Employment and Training Administration: Health
care. Retrieved June 24, 2011.

You might also like