batch-21

1

KEY ELEMENTS: 1.ABSTRACT 2.SYSTEM DESCRIPTION 2.1 SCOPE OF THE PROJECT 2.2 EXISTING SYSTEM 2.2.1 PROBLEMS IN EXISTING SYSTEM 2.3 PROPOSED SYSTEM 2.3.1 ALGORITHM 2.3.2 ADVANTAGES 2.4 SYSTEM REQUIREMENTS

2

1.This system stores and displays the Personal Health Records and providing security to them while they are stored at third party such as cloud. 2. Personal Health Record system is a web based application that allows people to access and coordinate their lifelong health information. 3. The patient have control over access to their own PHR. 4.To achieve the security in personal health records system, the advanced encryption algorithm is used. The algorithm works with date and time to encrypt the data before outsourcing it. 4.The system focus on multiple types of PHR owner scenario and division of personal health records users into multiple security domains which reduce key management complexity for owners and users. 5.A high degree of patient’s privacy is guaranteed. The system scheme gives personal health record owner full control on data. 6.using AEA DT ,Extensive security and performance is obtained on this proposed system. . 3

2. SYSTEM DESCRIPTION: As already mentioned, the introduction of human element is the most important part of our portal. The analytical ability of eminent physicians comes in handy in complicated diagnosis.  The main service offered by our site is •  Image and text uploads. • Consultancy through chatting The uploading facilities act as a useful tool for the user to upload the various diagnostic reports and image namely X-rays, MRI scan images and so on. This helps the doctor to get a better understanding of the patient’s condition. The consultancy is facilitated with the introduction of chatting. This gives our site an edge over the present system. This chatting facility provides the user with a near to real life consultancy experience.

   4

The doctor can review the various images and reports uploaded by the patients in the earlier date. This enables the doctor to keep a track of the patient’s health status.

2.1 SCOPE OF THE PROJECT •This software which is very useful in practical world. •This project will be helpful for the people in the rural and urban areas where there is scarcity of medical aid. •Time consumption for standing in a queue to meet a doctor can also be reduced. •Patient can consult more than one doctor at the same time

5

2.2 EXISTING SYSTEM: At present, the existing system is partially computerized. This system is mainly implemented in hospitals. The information necessary for the smooth operation of a hospital outpatient section is not easily available to staff in the op-section.   In the existing system, the details regarding the departments and doctors are stored and updated or deleted with much effort. A detailed study of the existing system with the constraints and structures, which gives a complete idea of the present system, is said below and we consider only single module for the system.

2.2.1 PROBLEMS IN EXISTING SYSTEM:

1. All records may not be handled or written by the same person ,so the format will be different resulting in loss. 2. The lifetime of paper record is very less that it easily get damaged , thus resulting in loss of data.

6

3.Manual system needs more manpower for its functioning than computer system. Expenditure is high in terms of salary and time. 4.The other limitation of the existing system is that there is no communication between doctor and patient when they are away from the hospital. 5.It is quite difficult for generating the reports and is time consuming for any updating.

2.2.2 PROPOSED SYSTEM: The proposed system overcomes the difficulties faced within the existing system. The new system is a user-friendly computerized system. Most of the workloads of operator and the administrator can be reduced with the new system.

7

2.2.3 ALGORITHM: • ADVANCED DATA ENCRYPTION ALGORITHM WITH DATE AND TIME

2.2.3 ADVANTAGES •Provides an easy department and doctor detail adding section. •Provides provision for updating the details regarding the doctors and department. •Make the advance registration process fast and efficient. •Provides the enquiry section fast and integrated. •Make the selection of a doctor from a department more easy. •Fast and efficient reports about the doctors. •Provide an easy way to see the details of patient everyday. •Provides an easy communication that is chatting facility between the doctor and patient when they are away from the hospital. •Provide an online messaging

8

2.2.4 SYSTEM REQUIREMENTS

Software Requirements : Operating System Windows 7 Programming Language ,JSP server side Apache tomcat client side browsers Data base :Oracle10g

: : JDK 1.6 : :web

Hardware Requirements : Memory : 250GB Ram : 2GB Processor : Intel (R) core (TM )2 Duo Cpu E4500 @2.20GHZ

9

DESIGNING PHASE: 1.MODULES USED: 2.PROPOSED SCHEME: 3.UML DIAGRAMS: 1.MODUELS USED: A. Admin Module This module is used to control all the process. Administration is a dynamic work in every field. The initial meaning of administration is the running of a business or system. In every step of your business, it needs administration. To run faster in the technological scenario a business need to administer. Admin is a super user who creates the PHR Data Owner user and maintains the cloud servers’ configurations. He has the writes to Add, Edit or Delete any number of Data owners. Once the Admin logged in he has following functions. •Login Module •PHR Owners •Key Generation •Transaction Details •Change Password 10

B. PHR Data Owners PHR Data Owner is a person who will store the files in cloud which in turn accessed by the authorized Data Users. Data Owners are like Patient who will upload all the files in the system. Whenever the file is uploaded it will be encrypted by the system using PHR Data Owners Encryption Keys. PHR Data Owner has to specify the Hierarchical Access Policy for each and every file. Access policies are set using Domain Attribute and Designation Attribute. PHR Data Owner can able to create the Data User and he has to send them . It contains the PHR Data Owners Decryption Key and Data users Attribute Set (Domain, Designation). Once the PHR Data Owner logged in he has following functions. When you submit your final version, after your paper has been accepted, prepare it in two-column format, including figures and tables. •Login Module •File Upload •Transaction Details •Change Password

11

PROPOSED SCHEME: The main goal is to provide secure patient-centric PHR access and efficient key management at the same time. The key idea is to divide the system into multiple security domains according to the different users data access requirements. The domains consist of users who make access based on their professional roles, such as doctors and medical researchers. In practice, domains can be mapped to an independent sector in the society, such as the health care, government or insurance sector. For each domain, its users are personally associated with a data owner (such as family members or close friends), and they make accesses to PHRs based on access rights assigned by the owner.

12

Architecture Diagram:--

Clien t1

Storage server

App /SW

Application server

I N T E R N E T

Clien t2

Clien t3

13

System flow diagram: Sta rt

Clou d

Sign in

vali d

Searc h Reque st

yes Home page Updat e Update informati on

No

Authenticatio n failure

Delet e Delete informatio n

Encrypt/Decry pt data Sign out

14

UML DIAGRAMS: 1.Use case diagram 2.Activity diagrams 3.Sequence diagrams 4.Collabration diagrams 5.Class diagram 6.Deployment diagram 7.Component diagram 8.State chart diagram 9.Conclusion

15

Usecase diagram :

register database

login doctor patient send request

generate appointment

view appointment

send diagnosis details

view patient health and give prescription

change prescription

fallow doctor instruction

16 signout

Activity diagram for authenticated user:patient/doctor login enter username &pwd

wrong details

no

no

validate validate

invalied system

yes check MAC

yes

no

yes authentication sucess

send requiest to server generate session key and send to the user

enter session key ,username&pwd

17

Activity diagrams for patient:

patient login

validate

no

invalid details

yes search the doctor

send a request for appointment in encrypted form

receive appointment and decrypt

send health details in encrypt form receive the prescription and decrypt the message follow doctor instruction

signout

18

Activity diagrams for doctor: doctor login

validate

no

wrong details

yes view the received messages and decrypt message

give appointment to the patient view patient health details

send prescription to the patient in encrypted form

signout

19

Sequence diagrams: Sequence diagram for authenticated patient: S:system

P:patient

D:database

1: enter username and pwd 2: pass the details with MAC addess 3: check the data base 4: return 1 5: authentication sucess 6: proceed next step

20

sequence diagram for invalid patient:

D:database

S:system

P:patient

1: enter username and pwd 2: pass the details with MAC addess 3: check the data base 4: return 0 5: authentication failure

21

sequence diagram for valid system: P:patient

D:database

S:system

1: send MAC address 2: check data base 3: return MAC statusis 1 4: valid system

22

Sequence diagram for invalid system:

P:patient

D:database

S:system

1: send MAC address 2: check data base 3: return MAC status is 1 4: valid system

23

Sequence diagram for patient and doctor: D:doctor

S1:server

P:patient

1: doctor sign in

2: patient sign in 3: send request for appointment

4: server forward the request 5: check the messages 6: generate appoinment

7: forward the message

8: view the message 9: send the diagnosis details 10: forward the message 11: check diagnosis details 12: give the prescription 13: forward the message

14: fallow doctor instruction 15: sign out 16: sign out

24

Collaboration diagrams: 1.Collaboration diagram for valid patient: 3: check the data base

1: enter user name and pwd 6: proceed next step P:patient

2: pass the details with MAC addess S:system

D:database

4: return 1

5: authentication sucess

2.Collaboration diagram for invalid patient: 3: check the data base 1: enter username and pwd P:patient 5: authentication failure

2: pass the details with MAC addess S:system D:database 4: return 0

25

3.Collabration diagram for valid system:

2: check data base

1: send MAC address P:patient

S:system

D:database

3: return MAC status is 1 4: valid system

4.Colabration diagram for invalid system: 2: check data base

1: send MAC address

P:patient

S:syste m 4: invalid system

D:databa se 3: return MAC status is 0

26

5.Collabration diagram for patient and doctor:

8: view the message 14: fallow doctor instruction

5: check the messages 11: check diagnosis details

2: patient sign in 3: send request for appointment 9: send the diagnosis details 15: sign out

4: server forward the request 10: forward the message S1:server

P:patient 7: forward the message 13: forward the message

D:doctor 1: doctor sign in 6: generate appoinment 12: give the prescription 16: sign out

27

Class diagram: Admin aid : string; pwd : string;

1

Patient p.id p.pwd s.mac sesion key

1..*

ApplicationServer sid String; sname char; name char; startup() shutdown()

login() logout() 1..*

1..* File ftype; char; fsize;int; fileupload() filemodife() filedelete()

login() processing() logout()

1..*

Doctor d .id : string; d.pwd : string; login() sendmessages() logout()

28

Component diagram:

patientdata base Application server

database sever

doctor database

29

Deployment diagram:

doctor1

patient1

application server

doctor2

patient2

database server

doctor N patientn

30

State chart diagram for patient: patient sign in

searching t he doctor

request an appiontment

recive appointment

send diagnosis details

recive prescript ion

follow doctor instructions sign out

31

State chart diagram for doctor:

doctor sign in view the messages

send an appiontment

recive patient health information view patient health give the prescription to the patient in encrypted form

sign out

32

CONCLUSION : The personal health record system needs security against attackers and hackers. Scalable and Secure sharing includes basic securities to protect the information from unauthorized access and loss. This proposed the new approach for existing PHR system for providing more security using advanced encryption algorithm with date and time which plays an important role because these are unique and not easily hackable.  We are reducing key management problem and also we enhance privacy guarantee

33