hospital management system origanal

7/30/2019 Hospital Management System Origanal

1/82

[Hospital Management System] [2013]

Page 1

1. Introduction

1.1) Purpose

The Software is for the automation of Hospital Management.

It maintains two levels of users:-

Administrator Level

User Level

The Software includes:-

Maintaining Patient details.

Providing Prescription, Precautions and Diet advice.

Providing and maintaining all kinds of tests for a patient.

Billing and Report generation.

1.2) Scope

It can be used in any Hospital, Clinic, Dispensary or Pathology labs for maintaining

patient details and their test results.

1.3) Technologies to be used

This project will be a desktop application to be developed in VB 6.0 having Ms

Access as backend.

Database Design (Ms Access)

Form Design (VB 6.0)

Coding (VB 6.0)

Testing (VB 6.0)

Reporting Tool (Data Report)


2/82


Page 2

1.4) Overview

Project is related to Hospital Management System.

The project maintains two levels of users:-

Administrator Level-Doctor

User Level-Data Entry Operator

Main facilities available in this project are:-

Maintaining records of indoor/outdoor patients.

Maintaining patients diagnosis details, advised tests to be done.

Providing different test facilities to a doctor for diagnosis of patients.

X-Ray

Urine Test

Stool TestSonography Test

Gastroscopy TestColonoscopy TestBlood Test

Biochemistry Test

Maintaining patients injection entry records.

Maintaining patients prescription, medicine and diet

advice details.


3/82


Page 3

Providing billing details for indoor/outdoor patients.

Maintaining backup of data as per user requirements.

If user forgets his/her password then it can be retrieved by hint

question.

In this project collection of data is from different pathology labs.

Results of tests, prescription, precautions and diet advice will beautomatically updated in the database.

Related test reports, patient details report, prescription and billing reports canbe generated as per user requirements.

User or Administrator can search a patients record by his/her name or their

registration date.

Patients diet advice can be provided in Hindi.


4/82


Page 4

2. Overall Description

2.1) Goals of proposed system

1. Planned approach towards working: - The working in the organization willbe well planned and organized. The data will be stored properly in data stores,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. Alloperation would be done correctly and it ensures that whatever information iscoming from the center is accurate.

3. Reliability: - The reliability of the proposed system will be high due to theabove stated reasons. The reason for the increased reliability of the system is thatnow there would be proper storage of information.

4. No Redundancy: - In the proposed system utmost care would be that noinformation is repeated anywhere, in storage or otherwise. This would assureeconomic use of storage space and consistency in the data stored.

5. Immediate retrieval of information: - The main objective of proposedsystem is to provide for a quick and efficient retrieval of information. Any typeof information would be available whenever the user requires.

6. Immediate storage of information: - In manual system there are manyproblems to store the largest amount of information.

7. Easy to Operate: - The system should be easy to operate and should be suchthat it can be developed within a short period of time and fit in the limited budgetof the user.


5/82


Page 5

2.2) Background

A Hospital is a place where Patients come up for general diseases. Hospitals provide

facilities like:-

Consultation by Doctors on Diseases.

Diagnosis for diseases.

Providing treatment facility.Facility for admitting Patients (providing beds, nursing, medicines etc.)

Immunization for Patients/Children.

Various operational works that are done in a Hospital are:-

Recording information about the Patients that come.

Generating bills.Recording information related to diagnosis given to Patients.

Keeping record of the Immunization provided to children/patients.

Keeping information about various diseases and medicines available to cure

them.

These are the various jobs that need to be done in a Hospital by the operational staff and

Doctors. All these works are done on papers.

The work is done as follows:-


6/82


Page 6

Information about Patients is done by just writing the Patients name, age andgender. Whenever the Patient comes up his information is stored freshly.

Bills are generated by recording price for each facility provided to Patient on a

separate sheet and at last they all are summed up.Diagnosis information to patients is generally recorded on the document, whichcontains Patient information. It is destroyed after some time period to decrease

the paper load in the office.Immunization records of children are maintained in pre-formatted sheets, which

are kept in a file.Information about various diseases is not kept as any document. Doctors

themselves do this job by remembering various medicines.

All this work is done manually by the receptionist and other operational staff and lot of

papers are needed to be handled and taken care of. Doctors have to remember various

medicines available for diagnosis and sometimes miss better alternatives as they cant

remember them at that time.


7/82


Page 7

2.3) Project Requirements

Hardware Requirements

Processor RAM Disk Space

Pentium II, Pentium III,

Pentium IV or higher64 Mb or Higher 130 Mb

Software Requirements

Operating System Database

Win-98, Win-XP, Linux or any other

higher version Ms Access

2.4) User Characteristics

Every user should be:

Comfortable of working with computer.

He must have knowledge in medical field.

He must also have basic knowledge of English too.


8/82


Page 8

2.5) Constraints

GUI is only in English.

Login and password is used for identification of user and there is no facility forguest.


9/82


Page 9

2.6) Definitions of problems

Problems with conventional system

1. Lack of immediate retrievals: -The information is very difficult to retrieveand to find particular information like- E.g. - To find out about the patientshistory, the user has to go through various registers. This results in inconvenienceand wastage of time.

2. Lack of immediate information storage: - The information generated byvarious transactions takes time and efforts to be stored at right place.

3. Lack of prompt updating: - Various changes to information like patientdetails or immunization details of child are difficult to make as paper work isinvolved.

4. Error prone manual calculation: - Manual calculations are error prone andtake a lot of time this may result in incorrect information. For examplecalculation of patients bill based on various treatments.

5. Preparation of accurate and prompt reports: - This becomes a difficulttask as information is difficult to collect from various registers.


10/82


Page 10

2.7) Alternative Solutions

1. Improved Manual System:-

One of the alternative solutions is the improvement of the manual system.

Anything, which can be done by using automated methods, can be done

manually. But the question arises how to perform thing manually in a sound

manner. Following are some suggestions, which can be useful in the manual

system.

A more sophisticate register maintenance for various Patient Information, Doctor

diary, Immunization Details and a good system for writing bill amountemployees and stock availed for the customers can be maintained at central place.

Adequate staff may be maintained so that updations are made at the very moment

at the same time. Proper person for proper work should be made responsible so

that a better efficiency could be achieved. This needs a lot of work force.

2. Batch System:-

Another alternative solution can be used of computer based batch system for

maintaining the information regarding purchase details, customers and

employees. A batch system refers to a system in which data is processed in a

periodical basis.

The batch system is able to achieve most of the goals and sub goals. But a batch

system data is processed in sequential basis. Therefore batch system is not

suggested.

3. Online System:-

This system (HMS)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.


11/82


Page 11

3. Feasibility Study

Depending on the results of the initial investigation the survey is now expanded to a

more detailed feasibility study. FEASIBILITY STUDY is a test of system proposalaccording to its workability, impact of the organization, ability to meet needs and

effective use of the resources. It focuses on these major questions:

1. What are the users demonstrable needs and how does a candidate system

meet them?

2. What resources are available for given candidate system?3. What are the likely impacts of the candidate system on the organization?4. Whether it is worth to solve the problem?

During feasibility analysis for this project, following primary areas of interest are to beconsidered. Investigation and generating ideas about a new system does this.

Steps in feasibility analysis

Eight steps involved in the feasibility analysis are:

Form a project team and appoint a project leader.

Prepare system flowcharts.

Enumerate potential proposed system.

Define and identify characteristics of proposed system.

Determine and evaluate performance and cost effective of each proposed system.Weight system performance and cost data.

Select the best-proposed system.

Prepare and report final project directive to management.


12/82


Page 12

3.1) Technical feasibility

A study of resource availability that may affect the ability to achieve an acceptable

system. This evaluation determines whether the technology needed for the proposedsystem is available or not.

Can the work for the project be done with current equipment existing software

technology & available personal?

Can the system be upgraded if developed?

If new technology is needed then what can be developed?

This is concerned with specifying equipment and software that will successfully satisfy

the user requirement. The technical needs of the system may include:

Front-end and back-end selection

An important issue for the development of a project is the selection of suitable front-end

and back-end. When we decided to develop the project we went through an extensive

study to determine the most suitable platform that suits the needs of the organization aswell as helps in development of the project.

The aspects of our study included the following factors.

Front-end selection:

1. It must have a graphical user interface that assists employees that are not from IT

background.

2. Scalability and extensibility.

3. Flexibility.

4. Robustness.

5. According to the organization requirement and the culture.

6. Must provide excellent reporting features with good printing support.7. Platform independent.

8. Easy to debug and maintain.

9. Event driven programming facility.

10.Front end must support some popular back end like Ms Access.

According to the above stated features we selected VB6.0 as the front-end for

developing our project.


13/82


Page 13

Back-end Selection:

1. Multiple user support.

2. Efficient data handling.

3. Provide inherent features for security.

4. Efficient data retrieval and maintenance.

5. Stored procedures.

6. Popularity.

7. Operating System compatible.

8. Easy to install.

9. Various drivers must be available.

10. Easy to implant with the Front-end.

According to above stated features we selected Ms-Access as the backend.

The technical feasibility is frequently the most difficult area encountered at this stage. It

is essential that the process of analysis and definition be conducted in parallel with an

assessment to technical feasibility. It centers on the existing computer system

(hardware, software etc.) and to what extent it can support the proposed system.

3.2) Economical feasibility

Economic justification is generally the Bottom Line consideration for most systems.

Economic justification includes a broad range of concerns that includes cost benefit

analysis. In this we weight the cost and the benefits associated with the candidate

system and if it suits the basic purpose of the organization i.e. profit making, the projectis making to the analysis and design phase.

The financial and the economic questions during the preliminary investigation are

verified to estimate the following:

The cost to conduct a full system investigation.


14/82


Page 14

The cost of hardware and software for the class of application being considered.

The benefits in the form of reduced cost.

The proposed system will give the minute information, as a result the

performance is improved which in turn may be expected to provide increasedprofits.

This feasibility checks whether the system can be developed with the available

funds. The Hospital Management System does not require enormous amount of

money to be developed. This can be done economically if planned judicially, so itis economically feasible. The cost of project depends upon the number of man-

hours required.

3.3) Operational Feasibility

It is mainly related to human organizations and political aspects. The points to be

considered are:

What changes will be brought with the system?

What organization structures are disturbed?

What new skills will be required? Do the existing staff members have theseskills? If not, can they be trained in due course of time?

The system is operationally feasible as it very easy for the End users to operate it. It

only needs basic information about Windows platform.

3.4) Schedule feasibility

Time evaluation is the most important consideration in the development of project. The

time schedule required for the developed of this project is very important since more

development time effect machine time, cost and cause delay in the development of

other systems.

A reliable Hospital Management System can be developed in the considerable amount

of time.


15/82


Page 15

OJECTIVE

The object of HMS Project is to design software to

automate the process of issuing a patient information patient disease,

information doctor information. The main objective of proposed

systemic to provide for a quick and efficient retrieval of information.

Related information of hospital would be available whenever the user

requires. Provides excellent and easy to access means of communication

medium between doctors and its patients.

Project Category

RDBMS:-

In recent years, Database Management System (DBMS) have established

themselves as primary means of data storage for information system ranging

from large commercial transaction to PC desktop application. At the heart of


16/82


Page 16

todays most of the information system is Relational Database System

(RDBMS) Have been the workhouse for data management operation for over

a decade and continue to evolve and mature, providing sophisticated storage,retrieval and distribution function to enterprisewide data processing and

management system compared to the file system, RDBMS provides

organization with capability to easily integrate and leverage the massive

amount of operational data into meaningful data.

The evolution of high-powered database engine such as SQL Server

2005 has faster the development of advance enabling technology including

client/server ,data warehousing and online processing ,all of which comprise

the core todays state ofart information system. A database is an organized

collection of related information. Any meaningful data is called information.

A database management system is a collection of interrelated data a set ofprograms to access that data.

The SQL Server architecture in this section is generic architecture that

applies all platforms on which SQL run. These may be different platform, but

the fundamentals are same. Physically in its simplest form, an SQL database is

nothing more than a set of files on the disk. Logically the database is divided

into a set of user account, each of which is identified by username and

password unique to the database. Tables and objects are owned one by one of

these. SQL Server maintains its own list of authorized user and their


17/82


Page 17

associated privileged, manages memory cache paging; control locking for

concurrent resource usage; dispatch and schedules users request; manages

space usage within its table space structure.

MODULES DISCRIPTION

ADMIN MODULE

ADMIN MODULE:-In Hospital Management System Admin can login ,

enter the patient information , doctor information, patient diseas

information, nurse information,room information and ambulanceinformation.all the authritee is to the admin.


18/82


Page 18

D A T A F L O W D I A G R A M

I N T R O D U C T I O N

The DFD also known as the Bubble Chart is a simple graphical formalism that can be used to

represent a system in terms of the input data to the system. Various processing carried out on these data, and the

output data generated by the system. The main reason why the DFD technique is so popular is probably because

of the fact that DFD is a very simple formalism-it is simple to understand and use. A DFD uses a very limited

number of primitive symbols to represent the functions performed by a system and the data flow among these

functions. Starting with a set of high-level functions that a system performs, a DFD model hierarchically

represents various sub functions. The five different types of primitive symbols used for constructing DFDs are:


19/82


Page 19

SYMBOLS USED:

PROCESS:

A function is represented using a circle. This symbol is called a process or a bubble. Bubbles are annotated

with the names of the corresponding functions.

EXTERNAL ENTITY:

An external entity such as a librarian, a library member, etc. is represented by a rectangle. The

external entities are essentially those physical entities external to the software system that interact with the

system by inputting data to the system or by consuming the data produced by the system. In addition to the

human users, the external entity symbols can be used to represent external hardware and software such as

application software.


20/82


Page 20

DATA FLOW:

A directed arc or an arrow is used as a data flow symbol. A data flow symbol represents the data flow

occurring between two processes, or between an external entity and a process, in the direction of the data flow

arrow. Data flow symbols are usually annotated with the corresponding data names.

DATA STORE:

A data store represents a logical file. It is represented using two parallel lines. A logical file can represent either

a data store symbol, which can represent either a data structure, or a physical file on disk. Each data store is

connected to a process by means of a data flow symbol. The direction of the data flow arrow shows whether

data is being read from or written into a data store. A arrow flowing in or out of a data store implicitly

represents the entire data of the data store and hence connecting to a data store need not be annotated with the

name of the corresponding data items.


21/82


Page 21

OUTPUT SYMBOL:

The output symbol is used when a hard copy is produced and the user of the copies cannot be clearly specified

or there are several users of the outpu

C O N T E X T D I A G R A M

The context diagram is the most abstract data flow representation of a system. It represents

the entire system as a single bubble. This bubble is labeled according to the main function of the

system. The various external entities with which the system interacts and the data flows occurring

between the system and the external entities are also represented.


22/82

[Hospital Management System] [2013

Page 22

4. Data Flow Diagrams

DFD: Level 0


23/82


Page 23

DFD:

Level 1


24/82


Page 24

DFD: Level 2


25/82


Page 25

DFD: Level 3


26/82


Page 26

5. Entity Relationship Diagram

loginpassword HMS

Log

in p

asswor

d

userhave

Admin

do

do

Loginwrite

dotake give

write

Patient

Reg.

TestBackup

Login

do Prescription

Test

give prescriptionPatient


27/82


Page 27

6. Data Tables

1. Login Table:-

Field Name Data Type Description

User_Name Text

Password Text

Hint_Question Text

Hint_Answer Text

User_Type Text


28/82


Page 28

2. Patient Detail Table:-


Registration_No Text

Registration_Date Date/Time

Name Text

Address Text

City Text

TelePhone_Mobile_No Text

Marital_Status Text

Religion Text

Gender Text

Father_Husband_Name Text


29/82


Page 29


Status Text Indoor / Outdoor

Age Number

3. Patient Diagnosis Table:-


Dignosis_No Text


Dignosis_Date Date/Time

Provisional_Dignosis Text

Remark Text

BioChemistry Yes/No

Stool Yes/No

Blood Yes/No

Colonoscopy Yes/No

Gastroscopy Yes/No

Urine Yes/No

XRay Yes/No

SONOGRAPHY Yes/No

Others Text

Reconsultation_Advice_Week Text Week Wise

Reconsultation_Advice_Date Date/Time

FINAL_Diagnosis Text

ECG Yes/No


30/82


Page 30

4. Patient Diet Advice Table:-


Dignosis_No Text

Diet_Advice Text

5. Patient Medicine Table:-


Dignosis_No Text

Medicine_No Number

Medicine_Name Text

Precaution Text Medicine Related Hindi

Words

No_of_Doses Number

6. Patient Injection Dates Table:-


Dignosis_No Text

Injection_Date Date/Time

Status Text Injection Taken or Not


31/82


Page 31

7. Biochemistry Test Table:-



Test_Date Date/Time

Glucose_Fasting_R Text 70-110 mg %

Two_Hr_Pg_Pp Text < 100 mg %

Blood_Urea Text 10-40 mg %

Creatinine Text 0.6-1.5 mg %

S_Cholesterol Text 130-250 mg %

Total_Protein Text 6.0-8.0 gm %

Albumin Text 3.5-5.0 gm %

Globwlin Text 2.3-3.6 gm %

A_G_Ratio Text ? 1.5 :,-2.3:1

Game_Gt Text 11-50 UL

Alkaline_Ptase Text 10-90 U/L Adult

Bilirubin_Direct Text 0.0-0.8 mg %

Bilirubin_Indirect Text 0.0-0.6 mg %

Bilirubin_Total Text 0.2-1.0 mg %

Sgot Text 0-40 U/L

Sgpt Text 0-40 U/L

Half_Hr_Pg_Pp Text < 110 mg %

One_Hr_Pg_Pp Text < 160 mg %

One_And_Half_Hr_Pg_Pp Text < 140 mg %


32/82


Page 32


Bun Text 8-20 mg %

Hdl_Cholesterol Text 30-55 mg %

Ldl_Cholesterol Text 60-165 mg %

Vldl_Cholesterol Text 0-60 mg %

Triglycerides Text 0-60 mg %

S_Total_Lipids Text 400-700 mg %

S_Amylase Text 25-125 U/L

S_Lipase Text 8-54 Ug/L

Sodium Text 136_146 mEq/L

Potassium Text 3.5-5.0 mEq/L

Chloride Text 94-111 mmo I/L

Calcium Text 8.5-11.0 mg/dl

Ldh_Total Text 230-461 U/L

Ck_Nac_Activated Text 0-190 U/L

Ck_Mb_Nac_Activated Text < 12 U/L

Uric_Acid Text 4-6mgdl

Urine_Sugar1 Text

Urine_Sugar2 Text

Urine_Sugar3 Text

Urine_Sugar4 Text

Acid_Ptase Text

Glucose_R_PP Text

T3 Text 0.3-2.5 uI U/L


33/82


Page 33


T4 Text 4.5-12 uI U/L

TSH Text 0.4-4.0 uI U/L

8. Blood Test Table:-


REGISTRATION_NO Text

TEST_DATE Date/Time

HAEMOGLOBIN Text 13-15 GMS%

TLC Text 4500-10500

CELLS/CUMM

NEUTROPHILS Text DLC , 45-68%

LYMPHOCYTES Text DLC , 25-45%

EOSINOPHIL Text DLC , 2-6%

MONOCYTES Text DLC , 1-4%

BASOPHILS Text DLC , 1-2%

OTHERS Text DLC

ESR Text 0-10 MM IST Hr

PERIPHERAL_BLOOD_FILM_1 Text

PERIPHERAL_BLOOD_FILM_2 Text

HAEMATOCRIT_PCV Text

TOTAL_RBC Text MIL/C.MM

PLATELETS Text CU.MM

COLOUR_INDEX Text


34/82


Page 34


MCHC Text

MCV Text FI

MCH Text PG

TEC Text CU.MM

VEC Text

PARACYTES Text

BLOOD_GROUPING Text

RH_FACTOR Text

RH_ANTIBODY_TILER Text

DIRECT Text

INDIRECT Text

PLASMA_FIBRINOGEN Text 150-400 mg%

HIV Text

HBSAG Text

WIDAL Text

FOETAL_HAEMOGLOBIN Text

RETICULOCYTES Text

BLEEDING_TIME_MIN Text

BLEEDING_TIME_SEC Text

CLOTING_TIME_MIN Text

CLOTING_TIME_SEC Text

PROTHROMBIN_TIME_CONTRO

L

Text


35/82


Page 35

field Name Data Type Description

SECS_PATIENT_2 Text

PTTK_CONTROL Text

HAEMOLYSIS_START_FROM Text

SALINE_COMPLETE_AT Text

CLOT_RETRACTION_TIME_CRT Text

LE_CELLS Text

ESR_PLATELETS Text

9. Colonoscopy Test Table:-



TEST_DATE Date/Time

ANAL_CANAL Text

RECTUM Text

SIGMOID_COLON Text

DESCENDING_COLON Text

SPLENIC_FLEXURE Text

TRANSVERSE_COLON Text

HEPATIC_FLEXURE Text

ASCENDING_COLON Text

CAECUM Text


36/82


Page 36


BIOPSY Text

OPINION_1 Text

OPINION_2 Text

10. Gastroscopy Test Table:-



Test_Date Date/Time

Esophgus Text Esophgus

Fundus Text Stomach

Corpus Text Stomach

Antrum Text Stomach

Blub Text Deuodenum

First_Part Text Deuodenum

Second_Part Text Deuodenum

Biopsy Text

Opinion_First Text

Pylorospasm Text

Biliary_Reflux Text

Gut_Hypomotility Text

Opinion_second Text


37/82


Page 37

11. Sonography Test Table:-



Test_Date Date/Time

L_Size Text Liver

L_Echotexture Text Liver

Focal_Pathology Text Liver

Ihbr Text Liver

Pv Text Liver

Cbd Text Liver

G_Size Text Gall Bladder

Wall_Thickness Text Gall Bladder

Lumen Text Gall Bladder

P_Size Text Pancreas

P_Shape Text Pancreas

P_Echotexture Text Pancreas

S_Size Text Spleen

S_Shape Text Spleen

S_Echotexture Text Spleen

K_Size_Rt Text Kidneys

K_Size_Lt Text Kidneys

K_Shape_Rt Text Kidneys

K_Shape_Lt Text Kidneys


38/82


Page 38


K_Cortex_Rt Text Kidneys

K_Cortex_Lt Text Kidneys

K_Corticomedullary_Differentiation_Rt Text Kidneys

K_Corticomedullary_Differentiation_Lt Text Kidneys

K_Pcs_Rt Text Kidneys

K_Pcs_Lt Text Kidneys

K_Calculus_Rt Text Kidneys

K_Calculus_Lt Text Kidneys

Aorta Text Petroperitoneal

Structures

Ivc Text Petroperitoneal

Structures

Pre_Paraortic_Lymphadenopathy Text Petroperitoneal

Structures

Fluid_In_Peritoneal_Cavity Text Petroperitoneal

Structures

Visualised_Bowel Text Petroperitoneal

Structures

U_Status Text Urinary Bladder

U_Wall_Thickness Text Urinary Bladder

U_Calculus Text Urinary Bladder

Prevoid_Urinary_Vol Text Urinary Bladder

Postvoid_Urinary_Vol Text Urinary Bladder

Pr_Size Text Prostate

Pr_Echotexture Text Prostate


39/82


Page 39


Pr_Capsule Text Prostate

U_Size Text Uterus

U_Position Text Uterus

U_Echotexture Text Uterus

U_E_Cavity Text Uterus

U_Endometrium Text Uterus

O_Size_Rt Text Ovaries

O_Size_Lt Text Ovaries

O_Shape_Rt Text Ovaries

O_Shape_Lt Text Ovaries

O_Echotexture_Rt Text Ovaries

O_Echotexture_Lt Text Ovaries

O_Adenexal_Mass_Rt Text Ovaries

O_Adenexal_Mass_Lt Text Ovaries

Free_Fluid_In_Pouch_Douglas Text Ovaries

Impression Text

12. Stool Test Table:-



Test_Date Date/Time

Color Text Physical


40/82


Page 40


Mucus Text Physical

Blood Text Physical

Wbc_Hpf Text Micoscopic

Rbc_Hpf Text Micoscopic

Mecrophages Text Micoscopic

Trophozoite Text Parasites

P_Ova Text Parasites

P_Cyst Text Parasites

C_Ova Text Concentration Method

C_Cyst Text Concentration Method

Occult_Blood Text Special Test

Ph Text Special Test

Red_Sub Text Special Test

13. Urine Table



TEST_DATE Date/Time

APPEARANCE Text ROUTINE

SP_GRAVITY Text ROUTINE

REACTION Text ROUTINE

ALBUMIN Text ROUTINE ,mg%

SUGAR Text ROUTINE


41/82


Page 41


RBCS_HPE Text MICROSCOPIC

WBCS_HPF Text MICROSCOPIC

EPITH_CELLS_HPF Text MICROSCOPIC

CRYSTAILS_HPF Text MICROSCOPIC

CAST_HPF Text MICROSCOPIC

AMORPHOUS_SEDIMENTS Text MICROSCOPIC

SPERMATOZOA Text MICROSCOPIC

OTHERS Text MICROSCOPIC

BILE_SALT Text SPECIAL_TEST

BILE_PIGMENT Text SPECIAL_TEST

UROBILINOGEN_HPF Text SPECIAL_TEST

PORPHOBILINOGEN Text SPECIAL_TEST

ACETONE Text SPECIAL_TEST

OCCULT_BLOOD Text SPECIAL_TEST

PKU Text SPECIAL_TEST

BECE_JONES_PROTEINS Text SPECIAL_TEST

AMINO_ACID Text SPECIAL_TEST

24HRS_URINARY_PROTEIN Text SPECIAL_TEST

24HRS_URINARY_17_KETOST

ERIOD

Text SPECIAL_TEST

24HRS_URINVARY_VMA Text SPECIAL_TEST

TOTAL_VALUE Text SPECIAL_TEST

PREGNANCY_TEST Text SPECIAL_TEST


42/82


Page 42


RBCS_HPE Text MICROSCOPIC

WBCS_HPF Text MICROSCOPIC

EPITH_CELLS_HPF Text MICROSCOPIC

CRYSTAILS_HPF Text MICROSCOPIC

CAST_HPF Text MICROSCOPIC

AMORPHOUS_SEDIMENTS Text MICROSCOPIC

SPERMATOZOA Text MICROSCOPIC

OTHERS Text MICROSCOPIC

BILE_SALT Text SPECIAL_TEST

BILE_PIGMENT Text SPECIAL_TEST

UROBILINOGEN_HPF Text SPECIAL_TEST

PORPHOBILINOGEN Text SPECIAL_TEST

ACETONE Text SPECIAL_TEST

OCCULT_BLOOD Text SPECIAL_TEST

PKU Text SPECIAL_TEST

BECE_JONES_PROTEINS Text SPECIAL_TEST

AMINO_ACID Text SPECIAL_TEST

24HRS_URINARY_PROTEIN Text SPECIAL_TEST

24HRS_URINARY_17_KETOST

ERIOD

Text SPECIAL_TEST


43/82


Page 43

14. USG Table


Registration_No Number

Test_Date Date/Time

LIV Text

LIV1 Text

LIV2 Text

GALL Text

GALL1 Text

COMM Text

COMM1 Text

PORT Text

PORT1 Text

PAN Text

PAN1 Text

SPLE Text

SPLE1 Text

KIDN Text

KIDN1 Text

KIDN2 Text

RK Text

LK Text

BOTH Text

BOTH1 Text


44/82


Page 44


URIN Text

URIN1 Text

N Text

N1 Text

UTER Text

LONG Text

ANTE Text

TRAN Text

N3 Text

ADNE Text

OTH Text

ECHO Text

15. X-Ray Table



Test_Date Date/Time

X_Ray_Name Text

Remark_1 Text

Remark_2 Text

Remark_3 Text

Remark_4 Text

Remark_5 Text


45/82


Page 45


Remark_6 Text

Remark_7 Text

Remark_8 Text

Remark_9 Text

Remark_10 Text

Remark_11 Text

Opinion Text

16. X-Ray Values Table


X_Ray_Name Text

Remark_1 Text

Remark_2 Text

Remark_3 Text

Remark_4 Text

Remark_5 Text

Remark_6 Text

Remark_7 Text

Remark_8 Text

Remark_9 Text

Remark_10 Text

Remark_11 Text

Opinion Text


46/82


Page 46


Receipt_No Text

Registartion_No Text

Receipt_Date Date/Time

F_Total_Fees Number Total Fees in Figure

W_Total_Fees Text Total Fees in Words

Receipt_Name Text SELF / Cheque

Dignosios_Fees Number

XRay_Fees Number

ECG_Fees Number

Lab_Test_Fees Number

Gastroscopy_Fees Number


47/82


54

17. Patient Fee Table


Receipt_No Text

Registartion_No Text

Receipt_Date Date/Time

F_Total_Fees Number Total Fees in Figure

W_Total_Fees Text Total Fees in Words

Receipt_Name Text SELF / Cheque

Dignosios_Fees Number

XRay_Fees Number

ECG_Fees Number

Lab_Test_Fees Number

Gastroscopy_Fees Number

USG_Fees Number

Indoor_Injection_Fees Number

Colonoscopy_Fees Number


48/82


55

INTRODUCTION TO ASP.NET

ASP.NET offers a novel programming model and infrastructure that facilitates a powerful new class of

applications. ASP.NET is a compiled. NET-based environment, so one can author applications in any

.NET compatible language, including Visual Basic, C# and Jscript.NET. Developers can effortlessly

access the advantage of these technologies, which consist of a managed Common Language Runtime

environment, type safety, inheritance, and so on. With the aid of Microsoft Visual Studio.

Web services enable the exchange of data in client-server or server-server scenarios, using standards

like HTTP, SOAP (Simple Object Access Protocol) and XML messaging to move data across firewalls.

XML provides meaning to data, and SOAP is the protocol that allows web services to communicate

easily with one another. Web services are not tied to a particular component technology or object-

calling convention. As a result, programs written in any language, using any component model, and

running on any operating system can access Web services.

Advantages of ASP.NET

ASP.NET is Part of the .NET Framework:

The .NET Framework comprises over 3,400 classes that we can employ in our ASP.NET applications.

We can use the classes in the .NET Framework to develop any type of applications. Since ASP.NET is

part of the .NET Framework, we can do all these things from within an ASP.NET page. While ASP


49/82


56

Classic pages are formed with scripting languages such as VBScript and JavaScript. ASP.NET pages

are formed with full-blown programming languages such as Visual Basic and C#. And whereas there

are five

standard objects accessible in the ASP Classic Framework (the Request, Response, Application,

Session, and Server objects), there are over 3,400 standard objects in the .NET Framework that we can

use in an ASP.NET page.

ASP.NET Pages are compiled

When an ASP.NET page is first requested, it is compiled and cached on the server. This means that an

ASP.NET page performs very rapidly. All ASP.NET code is compiled rather than interpreted, which

permits early binding, strong typing, and just-in-time (JIT) compiling to native code.

XML-Based

ASP.NET configuration settings are stored in XML-based files, which are human readable and

writable. Each one of our applications can have a different configuration file and we can extend the

configuration scheme according to our necessities.

Code-Behind logic

The main problem with ASP Classic pages is that an *.asp page does not yield modularized code. Both

HTML and Script are present in a single page. But Microsoft's ASP.NET implementation contains a

new-fangled method to break up business logic code from presentation code. Each ASPX created in

Visual Studio has an equivalent class written in a .NET compliant language such as C#. This class

consists of event handlers, initialization code and other supporting code for the user interface in the

ASPX file. The C# file that hold this class is called the code-behind file and affords the ASPX file's

programmatic implementation.


50/82


57

ASP.NET Pages are built with Server Controls

We can easily build complex Web pages by bring together the pages out of ASP.NET server controls.

For example, by adding validation controls to a page, we can easily validate form data.

Introduction of Database management System

A database is a collection of interrelated data.

The collection of data must be logically coherent with some inherent meaning. A database is designed

and built for a specific purpose, keeping in mind the needs of the applications that are going to use it

and end users of those applications. It is managed by a software package known a database

management system (DBMS).

A DBMS is a software system that enables users to record and maintain database. It provides an

environment where in data can be stored and retrieved from database easily and must efficiently. The

data can be any thing that is deemed to be of significant to the organization, the system is serving.

What is .NET?

.NET is set of common services which can be used from a number of languages and

have the following specialties:


51/82


58

i. These services are executed in the form of intermediate code that is independent of theunderlying architecture.

ii. They operate in the runtime (Common Language Runtime), which manages resources andmonitors applications execution.

The .NET frameworks are a multi-language environment for building, deploying, and running web

services and applications. The Microsoft .NET platform provides .NET infrastructure and tools to build

and operate a new generation of services.

SQL-SERVER 2005

these files is irrelevant to the function of the recent years, Database Management System (DBMS)

have established themselves as primary means of data storage for information system ranging from

large commercial transaction to PC desktop application. At the heart of todays most of the information

system is Relational Database System (RDBMS).

Have been the workhouse for data management operation for over a decade and continue to

evolve and mature, providing sophisticated storage, retrieval and distribution function to enterprise

wide data processing and management system compared to the file system, RDBMS provides

organization with capability to easily integrate and leverage the massive amount of operational data

into meaningful data.

The evolution of high-powered database engine such as SQL Server 2005 has faster the

development of advance enabling technology including client/server ,data warehousing and online


52/82


59

processing ,all of which comprise the core todays state ofart information system. A database is an

organized collection of related information. Any meaningful data is called information. A database

management system is a collection of interrelated data a set of programs to access that data.

The SQL Server architecture in this section is generic architecture that applies all platforms on

which SQL run. These may be different platform, but the fundamentals are same. Physically in its

simplest form, an SQL database is nothing more than a set of files on the disk. The physical relation o

tabase. Logically the database is divided into a set of user account, each of which is identified by

username and password unique to the database. Tables and objects are owned one by one of these. SQL

Server maintains its own list of authorized user and their associated privileged, manages memory cache

paging; control locking for concurrent resource usage; dispatch and schedules users request ; manages

space usage within its table space structure.

SQL SERVER-2005 ARCHITECTURE

SQL Files

There are major three sets of files on the disk that compose database: 1) Database

File 2) Control File 3) Redo Files

The most common is the database files where the data resides. The control and the redo logs support

the functioning of the architecture itself. All of these sets of files be present, open and available to SQL

Server for any data on database to be usable all these files are binary files.

Memory


53/82


60

SQL Server uses the memory of the system to turn the user process and to cache data

objects. There are major areas used by SQL Server : memory that is shared by all process against the

data and the database memory that is local to each individual user process.

System Memory

SQL Server database wide system memory is known as the SGA (System Global SQLShared Area). The data and control structures in SGA are sharable and all SQL Server background

process uses them.

ReportsPatient information:-

In the patient information user can enter the name of the patient,age,gender,any facilites which is given by the government like as green card, white

card,kisan card etc.when the patient admitt,discharge date&day are present and many

more facilities.

Patient diseas information:-

In the patient diseas information all the entry is feed by doctor as

diseas detail.if any other diseas is found the doctor can feed in additional information

column and he can give the detail of diseas.

Doctor informatin:-

In the doctor information admin can view the name of the

doctor,age,address,degree,contact number and e mail id.


54/82


61

Nurse information:-

In the nurse information admin can view the name of the

doctor,age,address,degree,contact number and e mail id.

Ward boy information:-

In the ward boy information admin can view the name of the

doctor,age,address,education,contact number and e mail id.

Rooms information:-

In the rooms information admin can view the total number of rooms,

occupied rooms and list of left rooms.

Ambulance information:-

In the ambulance information admin can view the total number

of ambulance,occupied amblance,left ambulance,driver name,age,address,contact number

and the licence numer of the ambulanc


55/82


62

Snapshot

User name and password:-


56/82


63

Patient information:-


57/82


64

Patient diseas information:-


58/82


65

Doctor information:-


59/82


66

Nurse information:-


60/82


67



61/82


68

Rooms infrmation:-


62/82


69

Ambulance information:-


63/82


70

About us:-


64/82


71

Contact us:-


65/82


72

Coding

User name and password:-using System;

using System.Configuration;

using System.Data;

using System.Linq;

using System.Web;

using System.Web.Security;

using System.Web.UI;

using System.Web.UI.HtmlControls;

using System.Web.UI.WebControls;

using System.Web.UI.WebControls.WebParts;using System.Xml.Linq;

using System.Data.SqlClient;

publicpartialclass_Default : System.Web.UI.Page

{

SqlConnection con = newSqlConnection();

protectedvoid Page_Load(object sender, EventArgs e)

{

con.ConnectionString = "Data Source=HCL-PC\\SQLEXPRESS;Initial Catalog=hospital_management;Integrated Security=true";

}

protectedvoid Button1_Click(object sender, EventArgs e)

{

con.Open();

SqlCommand cmd = newSqlCommand();cmd.Connection = con;

cmd.CommandText = "select username,password from unp where username='" + txtusername.Text + "',password='" + txtpassword.Text +

"'";

SqlDataReaderdr;

dr = cmd.ExecuteReader();

if(dr.Read())

{

txtusername.Text=dr[0].ToString();

txtpassword.Text=dr[1].ToString();

Response.Redirect("PATIENT_INFORMATION.aspx");

}

else

{txtusername.Text="";

txtpassword.Text="";

Label1.Text="USERNAME OR PASSWORD IS INCORRECT!";

}

cmd.ExecuteNonQuery();

con.Close();


66/82


73

}

}

Patient information:-using System;

using System.Collections;


using System.Data;

using System.Linq;

using System.Web;





using System.Web.UI.WebControls.WebParts;

using System.Xml.Linq;


publicpartialclassPATIENT_INFORMATION : System.Web.UI.Page

{



{

con.ConnectionString = "Data Source=HCL-PC\\SQLEXPRESS;Initial Catalog=hospital_management;Integrated

Security=true";

}


{

con.Open();

SqlCommand cmd = newSqlCommand();

cmd.Connection = con;

cmd.CommandText = "insert into

patient_information(name,age,gender,goverment_card,weight,type,addmitted_date,discharge_date)values('"+txtname.Te

xt+"','"+txtage.Text+"','"+RadioButtonList1.Text+"','"+DropDownList1.Text+"','"+txtweight.Text+"','"+RadioButtonLis

t2.Text+"','"+txtdatead.Text+"','"+txtdd.Text+"')";cmd.ExecuteNonQuery();

con.Close();

}

protectedvoid Calendar1_SelectionChanged(object sender, EventArgs e)

{

txtdatead.Text = Calendar1.SelectedDate.ToLongDateString();


67/82


74

}

protectedvoid Calendar2_SelectionChanged(object sender, EventArgs e)

{

txtdd.Text = Calendar2.SelectedDate.ToLongDateString();

}


{

con.Open();


SqlDataAdapteradp = newSqlDataAdapter();


cmd.CommandText = "select*from patient_information";

adp.SelectCommand = cmd;

DataSet ds = newDataSet();

adp.Fill(ds, "temp");

GridView1.DataSource = ds.Tables["temp"];

GridView1.DataBind();

con.Close();

}

protectedvoid DropDownList1_SelectedIndexChanged(object sender, EventArgs e)

{

}

}


68/82


75


69/82


76

Patient diseas information:-using System;


using System.Configuration;using System.Data;

using System.Linq;

using System.Web;








publicpartialclassPATIENT_DISEAS_INFORMATON : System.Web.UI.Page

{SqlConnection con = newSqlConnection();


{


}


{

con.Open();




patient_diseas_information(disaes_name,additional_information,diseas_detail)values('"+DropDownList1.Text+"','"+txtadditional.Text+"','"+txtd

iseasdetail.Text+"')";cmd.ExecuteNonQuery();

con.Close();

}


{

con.Open();




cmd.CommandText = "select*from patient_diseas_information";ss






con.Close();

}

}


70/82


77

Doctor information:-using System;



using System.Data;

using System.Linq;

using System.Web;








publicpartialclassDOCTOR_INFORMATION : System.Web.UI.Page

{



{


security=true";

}


{

string interests = string.Empty;foreach(ListItem item inthis.CheckBoxList1.Items)

{

if(item.Selected)

{

interests += item + ",";

}

}

con.Open();



cmd.CommandText = "insert intodoctor_information(name,age,address,degree,contact_number,e_mail_id)values('"+txtname.Text+"','"+txtage.Text+"','"+

txtaddress.Text+"','"+interests+"','"+txtcontact.Text+"','"+txtemail.Text+"')";


con.Close();

}



71/82


78

{

con.Open();




cmd.CommandText = "select*from doctor_information";






con.Close();

}

}


72/82


79

Nurse information:-using System;



using System.Data;

using System.Linq;

using System.Web;








publicpartialclassNURSE_INFORMATION : System.Web.UI.Page

{

SqlConnection con=newSqlConnection();


{

con.ConnectionString="Data Source=HCL-PC\\SQLEXPRESS;Initial Catalog=hospital_management;Integrated

Security=true";

}


{string interests = string.Empty;

foreach(ListItem item inthis.CheckBoxList1.Items)

{

if(item.Selected)

{


}

}

con.Open();

SqlCommand cmd=newSqlCommand();

cmd.Connection=con;cmd.CommandText="insert into

nurse_information(name,age,address,degree,e_mail_id,contact_number)values('"+txtname.Text+"','"+txtage.Text+"','"+t

xtaddress.Text+"','"+interests+"','"+txtemail.Text+"','"+txtcontact.Text+"')";


con.Close();

}


73/82


80


{

con.Open();




cmd.CommandText = "select*from nurse_information";






con.Close();

}

}


74/82


81


using System;using System.Collections;


using System.Data;

using System.Linq;

using System.Web;






using System.Xml.Linq;using System.Data.SqlClient;

publicpartialclassWARD_BOY_INFORMATION : System.Web.UI.Page

{



{


security=true";

}


{

string interests = string.Empty;

foreach(ListItem item inthis.CheckBoxList1.Items)

{

if(item.Selected)

{


}

}

con.Open();




ward_boy_information(name,age,address,edcation,contact_number,e_mail_id)values('" + txtname.Text + "','" +

txtage.Text + "','" + txtaddress.Text + "','" + interests + "','" + txtcontact.Text + "','" + txtemail.Text + "')";



75/82


82

con.Close();

}


{

con.Open();




cmd.CommandText = "select*from ward_boy_information";






con.Close();

}

}


76/82


83

Rooms informatin:-

using System;using System.Collections;


using System.Data;

using System.Linq;

using System.Web;








publicpartialclassRoom__Information : System.Web.UI.Page

{



{


}


{

con.Open();



cmd.CommandText = "insert into rooms_information(total_rooms,occupied_rooms,left_rooms)values('" + txttr.Text + "','" + txtor.Text +"','" + txtlr.Text + "')";


con.Close();

}


{

con.Open();




cmd.CommandText = "select*from rooms_information";


DataSet ds = newDataSet();adp.Fill(ds, "temp");



con.Close();

}

}


77/82


84

Ambulance information:-using System;


using System.Configuration;using System.Data;

using System.Linq;

using System.Web;








publicpartialclassambulance_Information : System.Web.UI.Page

{SqlConnection con = newSqlConnection();


{


}


{

con.Open();




ambulance_information(total_ambulance,occupied_ambulance,left_ambulance,driver_name,age,address,contact_number,ambulance_number)va

lues('" + txtta.Text + "','" + txtoa.Text + "','" + txtla.Text + "','" + txtname.Text + "','" + txtage.Text + "','" + txtaddress.Text +"','"+txtcontact.Text+"','"+txtaln.Text+"')";


con.Close();

}


{

con.Open();




cmd.CommandText = "select*from ambulance_information";






con.Close();

}

}


78/82


85

Sql server coding:-createdatabase hospital_management

use hospital_management

createtable unp(username varchar(45),passwordvarchar(45));

select*from unp;

insertinto unp(username,password)values('dheerendra','7398016669');

createtable patient_information(namevarchar(90),age int,gendervarchar(15),goverment_card varchar(30),weight int,

typevarchar(30),addmitted_date varchar(50),discharge_date varchar(50));

select*from patient_information;

droptable patient_information;

createtable patient_diseas_information(disaes_name varchar(90),additional_information varchar(90),diseas_detail

varchar(120));

select*from patient_diseas_information;

insertinto

patient_diseas_information(disaes_name,additional_information,diseas_detail)values('maleriya','dengu','normal');

createtable rooms_information(total_rooms int,occupied_rooms int,left_rooms int);

select*from rooms_information;

createtable ambulance_information(total_ambulance int,occupied_ambulance int,left_ambulance int,driver_name

varchar(30),age int,addressvarchar(50),contact_numberint,ambulance_numbervarchar(15));

droptable unp;

select*from ambulance_information;

createtable doctor_information(namevarchar(50),age int,addressvarchar(90),degree varchar(55),contact_number

int,e_mail_id varchar(80));

select*from doctor_information;

createtable nurse_information(namevarchar(50),age int,addressvarchar(90),degree varchar(76),e_mail_idvarchar(87),contact_numberint);

Select*from nurse_information;

insertinto nurse_information(name,age,address,degree,e_mail_id,contact_number)values('sudha',19,'lucknow','diploma

in nursing','[email protected]',9898);

select*from ward_boy_information;

createtable ward_boy_information(namevarchar(30),age int,addressvarchar(50),edcation varchar(50),contact_number

int,e_mail_id varchar(50));

insertinto ward_boy_information(name,age,address,edcation,contact_number)values('madanpal',25,'kanpur','bcom',121)


79/82


86

Future Scope

It can be used in any Hospital, Clinic, Dispensary or Pathology labs for maintaining

patient details and their test results.

Bibliography


80/82


87

BOOKS:

ASP .Net By Peter Norton

Mastering ASP.Net TECHMEDIA

Learn ASP.Net in 21 days TMH

Black book ASP.Net.


81/82


88

LIBRARY:

MSDNMSDN 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
http://www.apollohospital.com/http://www.ducatindia.com/http://www.ministryofhealth.com/http://www.ministryofhealth.com/http://www.ducatindia.com/http://www.apollohospital.com/


82/82


Conclusion

The project Hospital Management System (HMS) is for computerizing the

working in a hospital. The software takes care of all the requirements of an

average hospital and is capable to provide easy and effective storage ofinformation related to patients that come up to the hospital.

It generates test reports; provide prescription details including various tests, diet

advice, and medicines prescribed to patient and doctor. It also provides

injection details and billing facility on the basis of patients status whether it is an

indoor or outdoor patient.

The system also provides the facility of backup as per the

requirement.

hospital management system origanal

Documents