Project Report

HealthCare System
..

On

Submitted By

RANJANA CHANDRA 0609010082 Submitted to:

B. TECH CS DEPART ENT

!EC C"##E$E "% EN$!NEER!N$ & TECHN"#"$'

CERTIFICATE
This is certify that Ranjana Chandra has carried out the work embodies in this project in entitled HealthCare System under my guidance and super ision during the academic session !""#$!""# in fulfillment of the re%uirement for b.tech Final &ear from IEC-CET' The (ork in this project is original and I am completely satisfied with this work) and wish her all success in future life'

AC*+,(-E./E0E+T
0any persons ha e contributed to make this software on HEALTHCARE SYSTEM a reality' I would especially like to e1press my appreciation to for his unstinted support) encouragement and his painstakingly and meticulous effort towards de eloping this software' I acknowledge the help and cooperation recei ed from all the faculty members of ducat Academy +oida' 2e eral colleagues and students ha e contributed directly and indirectly to the contents this software) as they had gi en me numerous ideas' Their criticism ga e me the much$needed hints about the areas that needed elaboration and amendments and also to present them with greater clarity' I sincerely e1press my gratitude to Mr. Tushar G r ) the present hod of cs department)iec$cet for his support and help in the final preparation of this Report' Finally) I wish to e1press my sincere thanks to all my family members) especially my 3arents for their constant moral support and Encouragement' I would (elcome Constructi e 2uggestions to impro e this software) which can be implemented in my further attempts' Thanking you4 Ranjana chandra roll +o' "5"6"7""#!

C,+TE+T
S.!" 7' !' ;' <' T"#IC 3reface ,bjecti e 9 2cope of the 3roject .efinition of 3roblem 2ystem Analysis 9 .esign i= Input Re%uirements ii= ,utput Re%uirements iii= Functional Re%uirements 2ystem 0aintenance 9 E aluation -ife Cycle of the 3roject i= Entity$Relationship .iagram ii= .ata Flow .iagram iii= 2tructure Chart Input 9 ,utput 2creens 3rocess In ol ed .ata .ictionary -imitations Future Applications References i= >ibliography #AGE !". 8 : 7" 7!

8' 5'

76 !!

:' #'

6'

;" <7 <8 8; 88 8#

3REFACE
(hen A Computer 2oftware succeeds$when it meets the needs of the people who use it) when it performs flawlessly o er along period of time) when it is easy to modify and e en easier to use$it can and does change things for the better' >ut when software fails$when its users are dissatisfied) when it is error prone) when it is difficult to change and e en harder to use$bad things can and do happen' (e all want to build software that makes things better) a oiding the bad things that lurk in the shadow of failed efforts' To succeed we need discipline when software is designed and built' 0any indi iduals and companies still de elop software hapha?ardly) e en as they build systems to ser ice the most ad anced technologies of the day' As a result) the %uality of the software that we produce suffers and bad things happen' This project report is intended to ser e as a guide to the software de eloped on HEALTHCARE SYSTEM ' I ha e tried to follow the principles and rules as suggested by the software engineers as far as possible) in order to make this software a 2uccessful one' The report starts with a comprehensi e introduction to the project undertaken as its ery First 2ection' It includes objecti es and scope of the project@ about the front$end tool used i'e' A23'+et with CA and the back$end tool i'e' 2B- 2er er' The second part presents and discusses the theoretical background of the project' The third section encompasses all the problems of the software that includes what is e1pected from the software) the demands and the re%uirements of the end$users' The fourth part is the 2ystem analysis and design section' This part focuses on

re%uirements analysis and specification) analysis issues) detailed procedures and the database designs' In The fifth section) different approaches to formal e aluation and re iew techni%ues are e1plored' The si1th section highlights the methodology adopted for this project' The se enth part suggests the steps re%uired to implement the software on the user machine' The eighth part discusses the hardware and software re%uirements of the user machines' The ninth part deals with the cost benefit analysis' The tenth section contains the data flow diagrams' The ne1t section is the flowchart part' The ne1t section is for the entity relationship diagram of the project' The thirteenth part e1plains the methodology used for testing' The fourteenth section is the test report' The fifteenth part is the most important part of the project i'e' the code for the software' The si1teenth part is the user manual section' The se enteenth part is the anne1ure for the topic that includes some details about the organi?ation) the data dictionary) definitions) acronyms and abbre iations used in the report' The final section is the reference part that contains a list of the books and reports that were referred during the de elopment of the project and the report as well' The emphasis in this report is to document the important concepts and techni%ues used for the successful de elopment of this project' I do hope fer ently that) through this report) the readers will get a real picture of what the project is all about' I also wish that may this software satisfies all the needs and re%uirements of the organi?ation) for which it is meant'

,>CECTIDE2 9 2C,3E ,F TEE 3R,CECT

The objective of this software is to completely automate the following process: This software provides the health card for the patient. It will display a set of information related to a patient regarding blood, urine, others. Provides information related to health and socio-economic data associated with location wise so that these inputs can further be used to decide about the effectiveness of the recommendations given to the patient. Provides different kinds of reports and analysis for the scientists, planners, doctor so as to enable them for better decision making on different occasions. Provides e cellent and easy to access means of communication medium between doctors and its patients. To maintain and store diseases information for past few months. Provides as a comparison chart among different reports at different stages. This system is providing different types of tests reports

!lood test "rine test #ther tests

3R,>-E0 .EFI+ITI,+
#R"$LEM STATEME!TF A Health Care System is an online facility by which userGdoctor can iew the diagnose information of a person related to hisGher health for better analy?ed medicine and medical treatments.

This system helps in disease management and pre enti e ser ices' It pro ides ery ital information like patients without an e1am for certain time) patient with certain le els >3) patients who are taking a certain class of medication) patients who are suffering from a certain type of disease) screening and immuni?ation information) -ab tests Results) etc' Rules can be created for arious time frames like a certain time period) last isit to the hospital) latest .ata a ailable Disit) across all isits' The system is completely dynamic in the sense@ each user can ha e his own rule and his own conditions and can decide if he wants to be alerted for the patient meeting the rule or for not '

!EE% "& THE S"&T'AREF This software is de eloped keeping in mind the abo e$mentioned problems' The needs and re%uirements of the end users are also kept in mind while designing this software' This software will enable its users to maintain) retrie e and generate reports %uickly and re%uiring minimum effort' Thus) HEALTHCARE SYSTEM is de eloped in order to facilitate it users to keep a track of case history regarding health status of Indian citi?ens' It also helps them to sa e their time and energy when they want to retrie e some kind of information for their specific purposes and needs'

2&2TE0 A+A-&2I2
Re%uirements analysis is a software engineering task that bridges the gap between system le el re%uirements engineering and software design' Re%uirements engineering acti ities result in the specification of softwareHs operational characteristics Ifunction) data and beha ior=) indicate softwareHs interface with other system elements) and establish constraints that software must meet' The most commonly used re%uirements techni%ue is to conduct a meeting or inter iew' The first meeting between a software engineer Ithe analyst= and the customer can be likened to the awkwardness of a first date between two adolescents' +either person knows what to say or ask@ both are worried that they do say will be misinterpreted@ both are thinking about where it might lead Iboth likely ha e radically different e1pectations here=@ both want to get the thing o er with) but at the same time) both want it to be a success'

/ause and (einberg suggest that the analyst start by asking C,+TEJT$FREE BKE2TI,+2' That is) a set of %uestions that will lead to a basic understanding of the problem) the people who want a solution) the nature of the solution that is desired) and the effecti eness of the first encounter itself'

The goal of the re%uirements gathering acti ity is to collect all rele ant information from the customer regarding the product to be de eloped with a iew to clearly understanding the customer re%uirements and weeding out the incompleteness and inconsistencies in these re%uirements' The re%uirements analysis acti ity is begun by collecting all rele ant data regarding the product to be de eloped from the users of the product and from the customer through inter iews and discussions'

.ata collection is done by taking the copies of the documents in ol ed in its working from the organi?ation'

De(i)* P+tte,*:
This software based on concept of the $odel %iew &ontroller '$%&( design pattern. %iew renders the data from the $odel in response to the re)uest made to the model by controlled events made by user interaction. $odel %iew &ontroller is a design approach to separate the application object model from *"I, originally invented around +,s. Then later on it has become a widely accepted common design pattern. The main objective behind this pattern is to decouple the view of the data 'presentation layer( from the actual data processing so that the same model can be used for various views. This is achieved by using three different types of objects that interact with each other in loosely coupled manner with their discreet set of tasks. These three objects are known as $odel, %iew and &ontroller.

VIEW:

%iew is the graphical data presentation 'outputting( irrespective of the real data processing. %iew is the responsible for look and feel, some custom formatting, sorting etc. %iew is completely isolated from actual comple data operations. -or e ample, #nline product catalog view is completely separated from database connection, )uery, tables etc. It simply gets final row-data from the model and puts some cosmetics and formatting before displaying it in browser. %iew provides interface to interact with the system. The beauty of $%& approach is that it supports any kind of view, which is challenging in today.s distributed and multi-platform environment. / $%& model can have multiple views, which are controlled by controller. %iew interface can be of 01!--#2$3, 4T$5, 6$57635T, 6T$5, and 0$5 or can be 0indows forms etc. "DE#: $odel is responsible for actual data processing, like database connection, )uerying database, implementing business rules etc. It feeds data to the view without worrying about the actual formatting and look and feel. 8ata provided by $odel is display-neutral so it can be interfaced with as many views without code redundancy9 this eases your code maintenance and reduces bugs and allows code -reuse at good e tent. $odel responds to the re)uest made by controllers and notifies the registered views to update their display with new data.

C"NTR"##ER: &ontroller is responsible for :otice of action. &ontroller responds to the mouse or keyboard input to command model and view to change. &ontrollers are associated with views. "ser interaction triggers the events to change the model, which in turn calls some methods of model to update its state to notify other registered views to refresh their display.

Be*e-it(: -ollowing are the few of the benefits of $%& design pattern.

3ince $%& handles the multiple views using the same enterprise model it is easier to maintain, test and upgrade the multiple system. It will be easier to add new clients just by adding their views and controllers. 3ince the $odel is completely decoupled from view it allows lot of fle ibilities to design and implement the model considering reusability and modularity. This model also can be e tended for further distributed application. It is possible to have development process in parallel for model, view and controller.

I+3KT REBKIRE0E+T2
For 0edical TestsF -

>lood Test details such as (>C) R>C) 3latelates ) Eeomoglobin) /lucose) >loodLKrea) 2erium Creatinine) E2R) T-C) .-C) etc' - Krine Test .etails such as Color) 2endiments) 2pecific) /ra ity) 3roteins) etc' - /eneral >lood .etails such as >lood /roup) EID 2tatus) RE$Type' - ,ther Test .etails such as J$Ray) EC/) CT$2can) etc'
For

iewing the EealthCard of an indi idual hisGher re%uired as an input'

oter idno will be

A legal citi?en of India can -ogin on this site by entering hisGher name as the username and hisGher oter idno as the password' For uploading the ad ertisements) the re%uired information isF Add 3ositionIi'e' the page on which aGan companyGorgani?ation wants to place its add= ) (idth and Eeight for the Adds are reser ed in ad ance which cannot be changed by an indi idual' ,n entering the location page) the width and height will automatically gets reflected' ,ther details which are needed for uploading an ad ertisement are M Add 3icture) +a igation Krl) Alternate Te1t) and Impressions of an Add'

,KT3KT REBKIRE0E+T2
#ers(n sh(uld ha)e a *(ter d .

There must be a net c(nnect (n and br(+ser t( ) e+ the +eb ,a-es (. res,ect )e s te.

FK+CTI,+A- REBKIRE0E+T2

#ers(n sh(uld ha)e a *(ter d .

There must be a net c(nnect (n and br(+ser t( ) e+ the +eb ,a-es (. res,ect )e s te

2&2TE0

0AI+TE+A+CE

2ystem maintenance denotes any changes made to a software product after it has been deli ered to the customer' 0aintenance is ine itable for almost any

kind of product' Eowe er) most products need maintenance due to the wear and tear caused by use' ,n the other hand) software products do not need maintenance on this count) but need maintenance to correct errors) enhance features) port to new platforms) etc' 2oftware maintenance is becoming an important acti ity of large number of organi?ations' This is no surprise) gi en the rate of hardware obsolescence) the immortality of a software product per se) and the demand of the user community to see the e1isting software products run on newer platforms) run in newer en ironments) andGor with enhanced features' (hen the hardware platform changes and a software product perform some low$le el functions) maintenance is necessary' Also) whene er the support en ironment of a software changes) the software product re%uires re$work to cope with the newer interface' Thus) e ery software product continues to e ol e after its de elopment through maintenance efforts' 0aintenance co ers a wide range of acti ities including correcting) coding and designing errors) updating documentation and test data and upgrading user support' Enhancement means adding) modifying or re$de eloping the code to support changes in the specifications' It is necessary to keep up with the changing user needs and the operational en ironment' The software is designed with the iew of easy updating to the software' Future ad ancements can be done easily through the re iew of product' The software architecture is strong enough to pro ide enhancement in /ATEER functionality) performance and reliability' Functions in the CEA+/E REBKIRE0E+T2 software are designed in such away that they dynamically update on addition of new and re ised modules' To append new features in this software) the databases CEA+/E REBKIRE0E+T2 for student details)A+A-&NE e1amination details are sufficient enough for the task' Thus the software is capable enough of being enhanced easily whene er re%uires by the user'
.EDI2E C,.E CEA+/E 2TRATE/IE2

MAI!TE!A!CE A33-& C,.E CEA+/E#R"CESS 2TRATE/IE2 M"%EL

T, TEE ,-. ,+E

K3.ATE .,CK0E+T2

I+TE/RATE A+. TE2T

E+TIT& RE-ATI,+2EI3 .IA/RA0

C,+TEJT .IA/RA0
The conte1t 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 arious e1ternal entities with

which the system interacts and the data flows occurring between the system and the e1ternal entities are also represented'

FIR2T -EDE- .F.

To de elop the le el 7 .F.) e1amine the high$le el functional re%uirements' If there are between three to se en high$le el functional re%uirements) then these can be directly represented as bubbles in the le el 7 .F.'

(e can then e1amine the input data to these functions and the data output by these functions) and represent them appro1imately in the diagram'

#E.E#/1 D%D :

2TRKCTKRE CEART
MAI! ME!/ S/$ME!/

E+TR& F,R0 3ER2,+ .ETAI-2 F,R0 >-,,. TE2T .ETAI-2 KRI+E TE2T .ETAI-2 ,TEER TE2T .ETAI-2 DIE( 3ER2,+ TE2T .ETAI-2 RE3,RT2 3ER2,+ >-,,. .ETAI-2 3ER2,+ KRI+E .ETAI-2 2TATE(I2E RE3,RT 3ER2,+ /R,(TE CEART RE3,RT >-,,. /R,K3 RE3,RT EID 2TATK2 RE3,RT RE2 2TATK2 RE3,RT 3ER2,+ >-,,. /RA3E RE3,RT 3ER2,+ KRI+E /RA3E RE3,RT RE/I2TRATI, + E,23ITA- RE/I2TRATI,+ F,R0 A.DERTI2E0E +T A.. A.DERTI2E0E+T F,R0 .I23-A& A.DERTI2E0E+T

F,R0

Home.Aspx

SiteMap.Aspx

Add_Details.Aspx

Admin_Page.Aspx

Blood_ ntry.Aspx

!eneral_Details_ ntry.Aspx

Hospital_Details_ ntry.Aspx

Person_Detail_Page.Aspx

Person_ ntry.Aspx

Sta""_Page.Aspx

-,/I+ 3R,CE22 F

2TART

Input Doter I.GEospital I. +,

If I. is correct &E2 ,ption for page

/enerate ,utput

2T,3

2EARCEI+/ TE2T .ETAI-2 3R,CE22F

2TART

Enter Doter I.

+,
Error 0essage

If Doter I. Is Correct

&E2
.isplay Coresponding Test .etails

2T,3

EEA-TEC AR. 3R,CE22F

2TART

Input Doter I.

+,

If I. is correct &E2

/enerate EealthCard

2T,3

.ATA>A2E .E2I/+ %atabase0 health1 n.(

Table7$KserL-oginL.etails

& eld name userid password role

%ata Ty,e archar archar archar

S 2e !" 78 78

C(nstra nts not null primary key not null

Table!$3ersonL.etails & eld name DoterLidno Fname mname -name FatherLname 0otherLname Address7 Address! City 2tate 2e1 .ob EmailLid ContactLno Image %ata Ty,e archar archar archar archar archar archar archar archar archar archar char datetime archar archar archar S 2e 78 78 78 78 !8 !8 ;" ;" !" !8 # $ 8" 78 8" C(nstra nts primary key not null allow null not null not null not null not null allow null not null not null not null not null allow null allow null not null

Table;$3ersonL/enL>loodL.etails & eld name DoterLidno >loodLgroup RhLtype Ei Lstatus %ata Ty,e archar archar archar archar S 2e 78 7" 7" 7" C(nstra nts primary key +ot null +ot null not null

Table<$KrineL2tdLDalues & eld name Color Consistancy 2endiments 2pfLgra ity Acidic KrineLsugar Albumin 3hosphate AcetoneLbodies >ileLsalt >ileLpigment Krobilinogen -uecocytes Erthyocytes EpithelialLcells Casts ketones 3roteins ,thers %ata Ty,e archar archar archar archar archar archar archar archar archar archar archar archar archar archar archar archar archar archar archar S 2e 78 78 78 78 78 78 78 78 78 78 78 78 78 78 78 78 78 78 78 C(nstra nts not null not null not null not null not null not null not null not null not null not null not null not null not null not null not null not null not null not null not null

Table8$KrineL3ersonL.etails & eld name DoterLidno Color Consistancy 2endiments 2pfLgra ity %ata Ty,e archar archar float float float S 2e 78 78 $ $ $ C(nstra nts 3rimary key null null null null

Acidic KrineLsugar Albumin 3hosphate AcetoneLbodies >ileLsalt >ileLpigment Krobilinogen -uecocytes Erthyocytes EpithelialLcells Casts ketones 3roteins ,thers TestLdate ClinicLname ClinicLaddress

float float float float float float float float float float float archar archar archar archar datetime archar archar

$ $ $ $ $ $ $ $ $ $ $ 78 78 78 78 $ 8" 8"

null null null null null null null null null null null null null null null not null not null not null

Table5$>loodL2tdLDalues & eld name %ata Ty,e (>C archar R>C archar 3latelates archar Eemoglobin archar /lucose archar >loodLurea archar 2eriumLcreatinine archar Esr archar Tlc archar .lc archar 3olymorphs archar -ymphocyte archar Esinophills archar >asophills archar 0onocytes archar S 2e 78 78 78 78 78 78 78 78 78 78 78 78 78 78 78 C(nstra nts not null not null not null not null not null not null not null not null not null not null not null not null not null not null not null

AdnormalLcells 0alaria 3arasite ,thers

archar archar archar archar

78 78 78 78

not null not null not null not null

Table:$>loodL3ersonLTestL.etails & eld name DoterLidno (bc Rbc 3latelates Eemoglobin /lucose >loodLurea 2eriumLcreatinine Esr Tlc .lc 3olymorphs -ymphocyte Esinophills >asophills 0onocytes AdnormalLcells 0alaria 3arasite ,thers TestLdate ClinicLname ClinicLaddress %ata Ty,e archar float float float float float float float float float float float float float float float float float float float datetime archar archar S 2e 78 $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ 8" 8" C(nstra nts 3rimary key allow null allow null allow null allow null allow null allow null allow null allow null allow null allow null allow null allow null allow null allow null allow null allow null allow null allow null allow null not null not null not null

Table#$,thersLTestL.etails & eld name DoterLidno ,therLtype .escription TestLdate ClinicLname ClinicLaddress %ata Ty,e archar archar archar atetime archar archar S 2e 78 !8 8" $ 8" 8" C(nstra nts 3rimary key not null not null +ot null not null not null

Table8$EospitalL.etails & eld name %ata Ty,e EospitalLid archar EospitalLname archar EospitalLaddress archar City archar .istt archar 2tate archar EeadLofLincharge archar S 2e 78 8" 8" !8 !8 !8 !8 C(nstra nts 3rimary key not null not null not null not null not null not null

Table6$AddL.etails & eld name id ImageKrl (idth Eeight +a igateKrl AlternateTe1t %ata Ty,e int archar int int archar archar S 2e $ 8" $ $ 8" 8" C(nstra nts identity not null not null not null not null not null

keyword Impression additiondate

archar archar datetime

8" 8" $

not null not null not null

.EFI+ITI,+2) ACR,+&02 A+. A>>REDIATI,+2

The following definitions and abbre iations may be used in this documentF Analys s C(d n%ata st(reF The re%uirements gathering process is intensified and focused specifically on software' The design must be translated into machine readable form' The code generation step performs this task' A logical construct used to depict data that is being recorded during manual and automated processes' .ata stores are organi?ed by logical data groupings without regard to the

%&% %es -n

storage medium .ata Flow .iagram$A diagram that shows the inputs and outputs of a process and the data stores that store the data' The software design actually a multi$step process that focuses on four distinct attributes of a programF the data structure) software architecture) interface representations and procedural details' .ata pro ided to a process .ata produced by a process 3roject E aluation and Re iew Techni%ue' A series of steps taken to accomplish a specific action or produce a specific result based on the input to those steps and the state of the system at the time of that input' Random Access 0emory 2ystem InputG,utput 2election 2oftware Re%uirements 2pecifications It focuses on the logical internals of the software' The project is di ided into small units and then the testing is done on each unit separately' It is a test case design method that uses the control the structure of the procedural design to deri e test cases'

In,ut "ut,ut #ERT #r(cess RAM SI" SRS Test n/n t Test n'h te-$(3 Test n-

-I0ITATI,+

 Provides no facility for #nline Payment. :o #nline &hat or voice chats to doctors. The site only maintain records of people above ;+ years of age,since in 5ogin process an individual is re)uired to enter his7her name and voter id.

FKTKRE A33-ICATI,+2

 Providing the #n-5ine &hat facility to users to concern the doctor for immediate response. Providing the community for speciali<e doctors for specific dieses, and share the information in the form of !logs, Photos, %ideos, discussions in various new researches in medical science. :urturing the dream of providing 1mail account facility to users so they can feel the independence of mail account at the same site. In future it will provide information of doctors with their speciali<ation in the local area of user7patient. In future we would provide the facility for online payment and implement 3ecure 3ocket 5ayer '335(.

.E3E+.E+CIE2

It doesn.t matter how efficiently the application works, if the bandwidth is not sufficient the transaction will take more time then e pected. .:et -ramework for e ecution environment and /do.:et Provides for database connectivity. II3 server is re)uired for the application. /lthough this software is architecturally independent but following hardware resources are re)uired. -or i.e. any I!$ compatible P& or any other workstation with mouse support and relevant software.

>I>-I,/RA3E&

$""4S0 A23 '+et >y 3eter +orton 0astering A23'+et TECE0E.IA -earn A23'+et in !7 days T0E >lack book A23'+et'

LI$RARY0 02.+ $38: 5ibrary %isual 3tudio .:et release The 02.+ -ibrary is the essential reference for de elopers) with more than a gigabyte of technical programming information@ including sample code) documentation) technical articles) the 0icrosoft .e eloper *nowledge >ase) and anything else we might need to de elop solutions that implement 0icrosoft technology' 'E$SITE0 www'apollohospital'com www'ducatindia'com www'ministryofhealth'com