Hms

1CARE HOSPITAL MANAGEMENT SYSTEM

‘INTRODUCTION’

Department Of Computer Science, Christ College, Bangalore-29


1.0. INTRODUCTION

1.1. PROBLEM IDENTIFICATION AND DEFINITION In this system every thing is done manually and it takes lots of time to complete

the work. Problem identification is done to obtain a clear understanding of the

needs of the clients and the users, and what exactly is desired from the software.

1.2. LITERATURE SURVEY

Our project is a real time project, which aims to automate Hospital

Management. This project would help in automating the hospital management

process in educational as well as commercial domain. The existing system of

Hospital Management is a manual method of managing data. Different log

books are maintained for the monitoring of various aspects of Hospital

Management. For retrieving the information required, the data has to be

searched in the respective log books. Updating, deletion and addition of new

records are very tedious. This method requires lot of time and effort.

Thus, the present existing system has many loopholes, which we have tried to

rectify through our project.



1.3. STUDY OF THE EXISTING SYSTEM

The existing system is manual. It is not yet been computerized. Because of this

fact managing data is very inconvenient. Data is inconsistent, redundant, its

storage and maintenance is laborious. Data retrieval is a very difficult task.

Administrator has to invite the doctors and pa tient. We have to review each

paper page by page which needs a lot of effort. If any patient has to take any

appointments it has to be registered by hand which is tedious. All these tasks

consume a lot of time and effort.

Our Hospital Management System will computerize all these tasks and reduce

the efforts and time required. Once the papers are submitted, each and every

step after that is computerized. Patients name, patients appointment timings,

doctors name and patients id number will be done easily by the system.

manually.

We have to review each paper page by page which needs a lot of effort. If any

patient has to take any appointments it has to be registered by hand which is

tedious. All these tasks consume a lot of time and effort.

Our Hospital Management System will computerize all these tasks and reduce

the efforts and time required. Once the papers are submitted, each and every

step after that is computerized. Patients name, patients appointment timings,

doctors name and patients id number will be done easily by the system.



1.4. DISADVANTAGES OF THE EXISTING SYSTEM 1. It provides more staff to operate and manage.

2. Repetition of work.

3. Cost is more.

4. It takes lots of time to complete the work.

5. It can store only small amount of data.

6. It is difficult to track the information.

7. Once the data is lost it cannot be retrieved again.

1.5. DETAILS OF THE PROPOSED SYSTEM

The proposed system for Hospital Management can be used for commercial and

educational institution purposes. It has many advanced features as compared to

the existing system. They are as follows:

Many user types are provided. They are as follows:

FEATURES:

1. REGISTRATION: On the system the user are able to register according to

its hierarchy, so that a username and password will be provided in order to login

to the system. The user data base and records are maintained by the system and

also you can add, update and delete the records from the system with proper

privileges.



2. IN-PATIENT DETAILS: I the new patient gets admitted to the system then a

unique record is generated for each patient and patient details with the room

reservation and its case papers and other details will be stored in the system.

Once the patient gets discharge then his check out from hospital along with the

billing details will be taken care of by the system.

3. OUT-PATIENT DETAILS: If the new patient visits the doctor, the system

generates a unique record for each patient and patient details along with its case

papers and other details are stored in the system. Billing details are also taken

care by the system.

4. LABORATORY: The system keeps track of the laboratories in the hospital.

The equipment purchasing, inventory and billing of the purchase will be

maintained by the system.

5. STAFF RECORD MAINTAINENCE AND PAYROLL SYSTEM: The

system keeps track of the entire staff of the hospital. The staffs pay slips as well

as addition and deductions to their salaries are maintained by the system. The

system also keeps track of the staff’s paid and unpaid leaves.

6. BILLING SYSTEM: The entire billing system for the patient will be

automatically created. It will include expenses of all kind and in the end when

the patient gets a discharge the entire bill will be generated automatically. The

bill will contain all the expenses, which should be charged to patient for the

period for which he/she was admitted to the hospital.



7. DOCTOR CONSULTANT: The system will provide a forum for senior as

well as junior doctors so that they can consult with each other online.

8. PATIENT RECORD MAINTENANCE: The system maintains a detail

record of each patient who will be admitted to the hospital. The patient case

papers will be generated automatically and will be maintained in proper format.

9. MEDICAL EQUIPMENT MAINTENANCE: The total medical equipment

maintenance will be taken care. The items will be disposable, non disposable

equipments and their proper maintenance.

1.5. ADVANTAGES OF PROPOSED SYSTEM

1. It provides less staff to operate and manage.

2. Reduction/elimination of repetition of work.

3. Increased productivity.

4. Decrease the paper work and enhance the accuracy.

5. Faster decision making.

6. Greater control over patient management.

7. Cost saving.

8. It is easy to track, compile and get back the entered information.

9. It can store large data and information.

10. It can provide only one click type of case.



‘SYSTEM ANALYSIS’



2.0 SYSTEM ANALYSIS

It is the starting point of the software development activity. As system grew

more complex it became evident that the goals of the entire system cannot be

easily comprehended. Hence the need for the requirements analysis phases

arose. Some of the difficulty is due to the scope of this phase. The software

project is initiated by the client’s needs. The emphasis was first on coding and

then shifted to design.

2.1 DETAILED ANALYSIS OF THE PROPOSED SYSTEM

This project is fully computerized and it is easy to view all the details. This

project would help in automating the hospital management process in education

as well as commercial domain. By giving one click we can view all the details

like patients id number, patient’s name, patient’s disease, appointment timings,

from how many years is the patient taking treatment from the hospital. We can

update, delete and add new records to the data. This requires less time and it is

very easy to complete work at a given time. In the existing system every thing is

done manually and it requires more employees to complete work at a given time

where as in proposed system it requires less number of employees and can

complete the work with in a given time. In the existing system the data is stored

in the form of records and it can store only small amount of data and it is

difficult to track the information. In proposed system every thing will be

computerized, it can store large amount of data. It provides less staff to operate

and mange. Since it is computerized it increases the productivity and it is easy

to track, compile and get back the entered information. It can have greater



control over patient management. User name and pass word will be provided to

each patient.

Thus, the present manual system has many loopholes, which we have tried to

rectify through our project.

2.2 TOOLS SURVEY

2.2.1. VISUAL BASIC- THE FRONT END TOOL

Visual basic is a procedural event driven programming language. Visual basic is

an application development environment for windows, which popularized

component oriented programming thus, taking away much of redundant coding

that used to be ubiquitous in the Windows programming world.

An application in Visual Basic is built as a collection of controls, which have

well defined interface and functionality, and then the code attached to these

controls to define the behavior of the application.

A project in Visual Basic comprises of forms, controls and modules that take

up an application. A form is a window that displays controls, graphics or other

forms and has some code associated with it. When some code has to be shared

throughout an application, it can be put in a module.

There are quite a number of reasons for the enormous success of Visual Basic

which are as follows:



The structure of the Basic programming language is very simple,

particularly as to the executable code.

VB is not only a language but primarily an integrated, interactive

development environment (“IDE”).

The VB-IDE has been highly optimized to support rapid application

development (“RAD”). It is particularly easy to develop graphical user

interfaces and to connect them to handler functions provided by the

application.

The GUI of the VB-ID provides intuitively appealing views for the

management of the program structure in the large and various types of

entities (classes, modules, procedures, forms…).

VB provides a comprehensive interactive and context-sensitive online

help system.

When editing program texts the “IntelliSense” technology informs you in

a little popup window about the types of constructs that may be entered

at the current cursor location.

VB is a component integration language which is attuned to Microsoft’s

Component Object Model (“COM”).

COM components can be written in different languages and then

integrated using VB.

Interfaces of COM components can be easily called remotely via

Distributed COM (“DCOM”), which makes it easy to construct distributed

applications.



COM components can be embedded in / linked to your application’s

user interface and also in/to stored documents (Object Linking and

Embedding “OLE”, “Compound Documents”).

In this project VB will provide the user interface. It will be used for the

different user logins. Also the details about each user will be displayed

on entering the necessary information.

Of all languages we have worked with, Visual Basic is easiest to learn and use,

which is why we have chosen it as our front end tool.

2.2.1.1 ADVANTAGES

VB is the quickest and easiest way to create powerful application for Microsoft

Window operating system. The VB programming system allows us to create

robust and useful applications that fully make use of the GUI.

VB helps us to be more productive by providing appropriate tools for the

different aspects of GUI development. We create the graphical interface for the

application by drawing objects in a graphical way. We set properties on these

objects to refine their appearance and behavior. Then we make this interface

react to the user by writing code that responds to events that occur in the

interface.



2.2.1.2 INTERFACE ELEMENTS

Tool Bar:

Toolbar provides quick access to commonly used commands in the

programming environment. We click a button on the toolbar once to carry out

the action represented by that button. It provides a set of tools that we use at

design time to place controls on a form.

Menu Bar:

It displays the commands that we use to build the application.

Form:

It serves as a window that we can customize as the interface of the application.

We can add controls, graphics and pictures to a form to create the look that we

want.

Project Window:

It lists the property settings for the selected form or control. A property is a

characteristic of an object, such as size, caption or color.

Object Browser:

Available from the view menu, the Object browser lists objects available for

use in the project and gibes us a quick way to navigate the code.



2.2.1.3. APPLICATIONS

There are three main steps for creating an application for windows in VB

Create the interface.

Set properties.

Write codes.

Creating An Interface:

Forms are the foundation for creating the interface of an application. We can see

forms to add windows and dialogue boxes to our application. The first step in

building the VB application is to create the forms that will be the basic for our

application’s interface. Then we draw the objects which make up the interface

on the forms created.

The properties window consists of the following components:

Object Box:

Display the name of the object for which you can set properties click the arrow

to the right of the object box do display the list of objects for the current form.

Properties List:



The left column displayed all of the properties for the selected object. We can

edit and view settings in the right column.

To set properties from the Properties Window:

From the view menu, choose properties, or click the Properties button on the

toolbar. The properties window displays the settings for the selected form or

control.

From the properties list, select the name of a property.

Writing Code:

The code window is where we write VB code for our application. Code consists

of language statements, constants and declaration. Using the code window, we

can quickly view and edit any of the code in our application.

To create an event procedure:

In the object list box, select the name of an object in the active form. In the

procedure list box, select the name of event of the selected object. Here the click

procedure is already selected, because it is the default procedure for a command

button. Note that a template for the event procedure is now displayed in the

code window.

Type the code between the Sub and End Sub statements.



Running the application:

To run the application, choose start from the Run menu or click the start button

on the toolbar or press F5.

Back End Tool: MICROSOFT ACCESS

MS Access is a relational database management system from Microsoft which

combines the relational MS Jet database engine with a graphical user interface.

It is a member of the MS Office System. Access can use data stored in

Access/Jet, Microsoft SQL server, any ODBC complaint data container.

Relatively unskilled programmer can use it to build simple applications.

Access was also the name of a communication program from Microsoft, meant

to compete with ProComm and other programs. Access proved to be a

Failure and years later Microsoft reused the name for its database software.

Access makes use of the Leszynski naming convention.

Salient features of Microsoft Access used as the back end tool

Access can be used as the database for basic applications, especially web based

applications:



1. It can be used for client-server solutions.

2. Access is used by programmers to create customized desktop.

3. It is relatively compatible with SQL.

4. It gives facility of easy data entry, modification and determines the

type of data to be entered.

5. It can be made to import to any front end tool as VB and used as the

database.

6. It is very much readily available and is quite user-friendly.

2.3. HARDWARE AND SOFTWARE REQUIREMENTS 2.3.1. HARDWARE REQUIREMENTS S.NO. REQUIREMENT1. Computer with 2 GB

hard disk and 256 MB RAM


http://S.NO/


2.3.2. SOFTWARE REQUIREMENTS S.NO. REQUIREMENT 1. Windows 95/98/xp

operating system 2. MS Access

3. Microsoft Visual Basic 6.0

2.4. ENTITY RELATIONSHIP DIAGRAM (E-R DIAGRAM)

The ER diagram is specialized graphic that illustrates the interrelationship

between entities in a database. ER diagrams often use symbols to represent

three different types of information. Boxes are commonly used to represent

entities. Diamonds are normally used to represent relationships and ovals are

used to represent attributes.

The first stage of information system design uses these models to describe

information needs or the type of information that is to be stored in a database

during the requirements analysis.

An entity represents a discrete object. Entities can be thought of as nouns.

Entities and relationships can have both attributes. Every entity must have a

minimum set of uniquely identifying attributes, which is called the entity’s

primary key.

Entity-relationship diagram don’t show single entities of relations. Rather, they

show entity sets and relationship sets.


http://S.NO/


Lines are drawn between entity sets and the relationship sets they are involved

in entities in an entity set must participate in the relationship set, a thick or

double line is drawn. This is called a participation constraint. If each entity of an

entity set can participate in at most one relationship set. This is called a key

constraint. To indicate that each entity in the entity set is involved in exactly

one relationship, a thick arrow is drawn.



E-R DIAGRAM FOR HOSPITAL


HOSPITAL

Doctors

Patients

Lab Technicians

Billing

Wards

Operation Theatre

Labs


E-R DIAGRAM FOR DOCTOR


Doctor

Name ID Number

Specialisation

Timings

Contact Number

Salary


E-R DIAGRAM FOR PATIENT


Patient

NameID Number

Disease

Bill Number

Doctors Name

Date of Admissio


E-R DIAGRAM FOR DISCHARGE PATIENT


Discharge Patient

Name

ID Number

Bill Number

Date of Discharge

Date of Admission

Payment Details


E-R DIAGRAM FOR ADMINISTRATOR

E-R DIAGRAM FOR BILLING


Administrator

Doctor Details

Patient Details

Lab Details

Salary Details

Billing Details

Staff Details

Infrastructure Details


2.5. DATA FLOW DIAGRAM

A Data Flow Diagram is a graphical representation of the “flow” of data

through an information system. A data flow diagram can also be used for the


Billing

Patient’s Name

Lab Charges

Pharmacy Charges

Amount Paid

Balance Amount

Bill Number


visualization of data processing. It is common practice for a designer to draw a

context level DFD first which shows the interaction between the system outside

entities.

CONTEXT LEVEL

Input Output

DATA FLOW DIAGRAM FOR HOSPITAL MANAGEMENT


Database

SystemPatient

Admit new patient


Add new patient

Details of patients

username administrator id

Password

Username Name, doc,DOB,gender

.

Doctor id

Doctor

Specialisation Disease

Staff discharge

Qualification


Login

Userpass

Administrator subsystem

Discharge patient

Transfer patient

patient/ transfer

Personal details

Userpass

Doctor applicant subsystem

Work details

Personal info

Educational details Salary Details

Personal details

Doctor table

Patient table

Discharge table

update/ search/

Authet--ication


‘SYSTEM DESIGN’

3.0 SYSTEM DESIGN

This phase begins when the requirements specification document for the

software to be developed is available. While the requirements specification

activity is entirely in the problem domain, design is the first step to moving

from the problem domain towards the solution domain. Design is essentially the



bridge between requirements specification and the final solution for satisfying

the requirements.

3.1. WORKING MODULES OF THE PROJECT

The different modules in our project, Hospital management are:

Login

Add patient

Delete patient

Update patient

View patient

The working of each module is explained below.

Login:

Using this module one can login into the system. Every user will be provided

with user name and password using this user name and password one can login

to the system and view there details.

Add patient:

Using this module the administrator can add patient details or new patients.

Delete patient:

Using this module we can delete the patient’s database if the patient’s disease

gets cured or the patient gets discharged from the hospital.



Update patient:

Using this module we can update the patient details.

View patient:

This module helps us to see the details of all the patients.

3.2. DATABASE DESIGN

3.2.1. Doctors Table:

Column Name Data Type Allows Null Description

ID No. Number No ID Number

Fname Text Yes First name

Lname Text Yes Last name

Password Numeric No Passwords

Contact No. Number No Contact Number

Address Text No Address

Specialisation Text Yes Specialisation

3.2.2. Patients Table: Column Name Data Type Allows Null Description

Id-Number Auto Number No Unique id number for patients

Password Numeric No Unique password for patients



Fname Text No First name


Contact number Numeric No Contact number of patient

Address Text NO Patient’s address

Disease Text Yes Patient’s disease

Doctor’s name Text Yes Name of the doctor who is treating the patient

3.2.3. Patients Registration Table:

Column Name Data Type Allows Null Description



Patients Id No. Number NO Unique Id number for patients

Patients Name Text Yes Name of the patient

Surname Text No Surname of the patient

Address Text No Address of the patient

Occupation Text No Occupation of the patient

Disease Text No Disease of the Patient

Phone no. number No Phone number

3.2.5. Laboratory Table: Column Name Data Type Allows Null Description

Equipments Numeric Yes Number of equipments in the hospital

Type Text Yes Type of



equipments in the hospital

Fname Text No First name of the lab technician


Salary Numeric Yes Salary of the lab technician

3.2.6. Doctors Table:

Column Name Data Type Description

Doctors Name Text Name of the Doctor

Doctors Id Number Identification number of the doctor

Doctors Specialization Text Specialization of the doctor

3.2.7 Billings Table:

Column Name Data Type Description

Patient-ID Number Identification Number



Bill No. Number Bill Number

Patient Name Text Patient Name

Lab Charges Number Laboratory Charges

Pharmacy Charges Number Pharmacy Charges

Total Amount Number Total Amount

The tables used in the data base are normalized. Database normalization, is

a technique for designing relational database tables to minimize duplication of

information and, in so doing, to safeguard the database against certain types of

logical or structural problems, namely data anomalies. The normal forms are



applicable to individual tables; to say that an entire database is in normal form n

is to say that all of its tables are in normal form n.

First normal form:

The normalization process involves getting our data to conform to progressive

normal forms, and a higher level of normalization cannot be achieved unless the

previous levels have been satisfied. The first normal form requires that the

values in each column of a table are atomic.

Second Normal form:

It deals with the relationships between composite key columns and non-key

columns. To achieve Second normal form, tables must already be in First

normal form.

Third Normal form:

Third normal form requires that all columns depend directly on the primary

key. Tables violate the Third Normal form when one column depends on

another column, which in turn depends on the primary key.



‘CODING’

4.0 CODING

The goal of the coding or programming phase is to translate the design of the

system produced during the design phase into code in a given programming

language which can be executed by a computer, and which performs the



computation specified by the design. For a given design, the aim is to

implement the design in the best possible manner.

The coding phase affects both testing and maintenance profoundly. As we saw

earlier, the time spent in coding is a small percentage of the total software cost,

while testing and maintenance consume the major percentage. Thus it should be

clear that the goal during coding should be to reduce the cost of later phases,

even if it means that the cost of this phase has to increase. In other words, the

goal during this phase is not to simplify the job of the tester and the maintainer.

4.1 PROGRAMMING PRACTICE

4.1.1. Top-Down and Bottom-Up

The design of a software system consists of a hierarchy of modules. The

main program involves subordinate modules. In a top down implementation, the

implementation starts from the top of the hierarchy, and then proceeds to the

lower level. In a bottom-up implementation, the process is the reverse.

4.1.2. Structured Programming

Much emphasis is based on structured programming, although the

concept and motivation behind structured programming is often not well

understood. Structured programming is often regarded as goto-less

programming.

It has a static structure as well as dynamic structure. The static structure is the

structure of the text of the program which is usually just a linear organisation of



statements of the program. The dynamic structure of the program is the

sequence in which statements are executed during the program execution.

4.1.3. Information Hiding

To reduce coupling between modules of a system it is best that different

modules be allowed to access and modify only those data items that are needed

by them. The other data should be hidden from such modules and the modules

should not be allowed to access these data items.

SAMPLE CODES

Private Sub cmdclear_Click()

txtpatientsid.Text = " "

txtSname.Text = " "

txtFname.Text = " "

txtDOB.Text = " "

txtSex.Text = " "

txtOccupation.Text = " "

txtStateOfOrigin.Text = " "

txtCaseRefNo.Text = " "

txtDateOfAdmission.Text = " "

txtDoctorInCharge.Text = " "



txtDoctorsDiag.Text = " "

End Sub

Private Sub cmdabort_Click()

If MsgBox ("Unload and Close admission file?", vbYesNo + vbQuestion) =

vbYes Then Unload Me

End Sub

Private Sub cbobloodgrp_Change ()

cbobloodgrp.AddItem "O+ve"

cbobloodgrp.AddItem "O-ve"

cbobloodgrp.AddItem "A+ve"

cbobloodgrp.AddItem "A-ve"

cbobloodgrp.AddItem "B+ve"

cbobloodgrp.AddItem "B-ve"

cbobloodgrp.AddItem "AB+ve"

cbobloodgrp.AddItem "AB-ve"

End Sub

Private Sub cmdsearch_Click()

Adodc1.Recordset.MoveFirst



While (Text2.Text <> txtpatientsid.Text)

Adodc1.Recordset.MoveNext

Wend

End Sub


40CARE HOSPITAL MANAGEMENT SYSTEM TESTING

5.0 TESTING

Software testing is the process used to measure the quality of developed

computer software. The separation of debugging from testing was initially

introduced by Glenford J.Myres in 1979. Usually, quality is constrained to such

topics as correctness, completeness, security, but can also include more

technical requirements as described under the ISO standard ISO 9126, such as

capability, reliability, efficiency, portability, maintainability, compatibility and



usability. Testing is process of technical investigation, performed on behalf of

stakeholders, that is intended to reveal quality-related information about the

product with respect to the context in which it is intended to operate. This

included, but is not limited to, the process of executing a program or application

with the intent of finding errors.

A good test is sometimes described as one which reveals an error; however,

more recent thinking suggests that a good test is Sone which reveals information

of interest to someone who matters within the project community, as a tests will

measure quality and therefore

May well be unable to find any error, because the software works the way it was

specified.

5.1 UNIT TESTING

Unit testing tests the minimal software component, or module. Each unit of the

software is tested to verify that the detailed design for the unit has been

correctly implemented. Unit testing is a procedure used to validate that

individual units of source code are working properly. A unit is the smallest

testable part of an application. In procedural programming a unit may be an

individual program, function, procedure, etc., while in object-oriented

programming, the smallest unit is always a Class; which may be a base/super

class, abstract class or derived/child class. Units are distinguished from modules

in that modules are typically made up of units.

The goal of unit testing is to isolate each part of the program and show that the

individual parts are correct. A unit test provides a strict, written contract that the

piece of code must satisfy. As a result, it affords several benefits.



Features:

Facilitates Change

Simplifies Integration

Documentation

Separation of interface from implementation

Unit testing will not catch every error in the program. By definition, it only tests

the functionality of the units themselves. Therefore, it will not catch integration

errors, performance problems or any other system-wide issues. In addition, it

may not be easy to anticipate all special cases of input the program unit under

study may receive in reality. Unit testing is only effective if it used in

conjunction with other software testing activities.

5.2 INTEGRATION TESTING

Integration testing exposes defects in the interfaces and interaction between

integrated components. Progressively larger groups of tested software

components corresponding to elements of the architectural design are integrated

and tested until the software works as a whole.

Integration testing is the phase of software testing in which individual software

modules are combined and tested as a group. It follows unit testing and precedes

system testing.



Integration testing takes as its input modules that have been unit tested, groups

them in larger aggregates, applies tests defined in an integration test plan to

those aggregates, and delivers as its output the integrated system ready for

system testing.

The different types of integration testing are:

Big Bang

Bottom Up

5.3. SYSTEM TESTING

System testing is testing conducted on a complete, integrated system to evaluate

the system’s compliance with its specified requirements. System testing falls

with in the scope of black box testing, and as such, should require no knowledge

of the inner design of the code or logic.

As a rule, systems testing rakes, as its input, all of the “integrated” software

components that have successfully passed integration testing and also the

software system itself integrated with any applicable hardware system.

5.4. ACCEPTANCE TESTING

Acceptance testing can be conducted by the end-user, customer or client to

validate whether or not to accept the product. Acceptance testing can be

performed after the testing and before the implementation phase.



It is the black box testing performed on a system in most environments,

acceptance testing by the system provider is distinguished from acceptance

testing by the customer. It generally involves running a suite of tests on the

completed system.

5.5. WHITE BOX TESTING

It uses an internal perspective of the system to design cases based on internal

structure. It requires programming skills to identify all paths through the

software. The tester chooses test case inputs to exercise paths through the code

determines the appropriate outputs.

It includes:

a. Control flow testing

b. Data flow testing

5.6. BLACK BOX TESTING

It takes an external perspective of the test object to derive test cases. These tests

can be functional or non-functional. The designer selects valid and invalid input



and determines the correct output. There is no knowledge of the test objects

internal structure

This method of test design is applicable to all levels of software testing unit,

integration, functional testing, system and acceptance.

This method can uncover unimplemented parts of the specification, one cannot

be sure that all existent paths are tested.



‘SYSTEM IMPLEMENTATION’

6.0 SYSTEM IMPLEMENTATION:

Implementation is the stage of project when theoretical design is turned into a

working system. The implementation involves a full planning, investigation of



current system and its constraints on implementing design of methods to

achieve the change over training of staff over procedure and evaluating over

methods.

The first step in implementation is planning, deciding on the methods and time

scale to be adopted. Once the planning has been completed, the major effort is

to ensure that programming the system is working properly an concentrate on

training users staff.

The steps involve conversation of existing document to compute the media and

setting of these are converted on the computer.

When the change over has taken place there will be need for amendment to

correct or improve the new system. The user can specify null values or existing

primary key values to the fields.



‘SYSTEM MAINTENANCE’

7.0 SYSTEM MAINTENANCE

The objective of this maintenance work is to be making sure that the system

gets into work all tie without any error. The error may occur due to several

reasons.



They may be identified at the installation time but are tend to develop at its

implementation time.

The system is liable to accept any modification after its implementation. This

system is designed to favour all new changes without affecting system

performance or its accuracy.



‘SCREEN SHOTS’

































‘DISCUSSION OF RESULTS’



9.0 DISCUSSION OF RESULTS:

The final project is capable of implementing the proposed features providing

access to a variety of users using the same interface. The proportion of data may

sometimes hinder the project speed of loading and running. The reports serve

the purpose as thought. The validations help user enter correct entries and the

Application as a whole is a very secure one. Lots of security features have been

provided as essential to any hospital management system.



‘CONCLUSION’



10.0 CONCLUSION:

To summarize in a line we have provided the package, which is reliable and

user friendly for any organization. There can be future enhancement where in

many other features can bi included which can make the package more

comfortable to work on for the organization.

Data redundancy will be avoided by creating tables for appropriate fields. It will

be easy for the organization to save the data in the system.



‘REFERENCES’

11.0 REFERENCES



BIBILOGRAPHY

Books:

i. VB 6.0, united publishers.

ii. John Smiley, Learn to program with basic 6, Active path

Publishers.

iii. Pankaj Jalote, An Integrated Approach to Software

Engineering, Narosa publishers

iv. Shamkant B.Navathe, Fundamentals of Database Systems,

pearsons Publishers

Websites:

www.google.com

www.codeguru.com

www.vbcodes.com


http://www.vbcodes.com/

http://www.codeguru.com/

http://www.google.com/