batch-21

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

ABSTRACT:

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.

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.

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

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:

,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

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.

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.

2.2.4 SYSTEM REQUIREMENTS

Software Requirements :

client side :web browsers Data base :Oracle10g

Hardware Requirements :

Processor : Intel (R) core (TM )2 Duo Cpu

DESIGNING PHASE:

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

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

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.

Storage server App /SW Application server I N T E R N E T Clien t1 Clien t2 Clien t3 Architecture

Diagram:--System flow diagram: Sta rt Clou d Sign in vali d Authenticatio n failure Home page Searc h Reque st Updat e Delet e Update informati on Delete informatio n Encrypt/Decry pt data Sign out No yes

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

Usecase diagram :

send request

view appointment

send diagnosis details

fallow doctor instruction

change prescription database

patient

view patient health and give prescription <<include>> register <<include>> login generate appointment doctor

Activity diagram for authenticated user:-patient/doctor login validate authentication sucess enter username &pwd check MAC yes invalied system send requiest to server

generate session key and send to the user

enter session key wrong details no validate yes no yes no

Activity diagrams for patient:

patient login

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

validate invalid details

yes

Activity diagrams for doctor: doctor login

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

validate

yes

wrong details no

Sequence diagrams:

Sequence diagram for authenticated patient:

P:patient

P:patient S:systemS:system

D:database 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

P:patient

P:patient S:systemS:system

D:database D:database

1: enter username and pwd

5: authentication failure

2: pass the details with MAC addess

3: check the data base

4: return 0 sequence diagram for invalid patient:

sequence diagram for valid system: P:patient

P:patient S:systemS:system D:databaseD:database

1: send MAC address

2: check data base

3: return MAC statusis 1

3: return MAC status is 1 P:patient

P:patient S:systemS:system D:databaseD:database

1: send MAC address

2: check data base

4: valid system

P:patient

P:patient S1:serverS1:server D:doctorD:doctor

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

2: patient sign in

1: doctor sign in

15: sign out

Collaboration diagrams:

1.Collaboration diagram for valid patient:

2.Collaboration diagram for invalid patient:

P:patient S:system _D:database

3: check the data base 1: enter username and pwd 2: pass the details with MAC addess

P:patient S:system D:database

3: check the data base

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

5: authentication sucess

2: pass the details with MAC addess

S:system D:database P:patient

2: check data base

1: send MAC address

3: return MAC status is 1 4: valid system

3.Collabration diagram for valid system:

P:patient _S:syste

m D:database 2: check data base

1: send MAC address

3: return MAC status is 0 4: invalid system

5.Collabration diagram for patient and doctor:

P:patient S1:server D:doctor

5: check the messages 8: view the message

11: check diagnosis details 14: fallow doctor instruction

2: patient sign in 3: send request for appointment

9: send the diagnosis details 15: sign out

7: forward the message 13: forward the message

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

16: sign out 4: server forward the request

Class diagram: Admin aid : string; pwd : string; login() processing() logout() File ftype; char; fsize;int; fileupload() filemodife() Patient p.id p.pwd s.mac sesion key login() logout() 1..* 1..* ApplicationServer sid String; sname char; name char; startup() shutdown() 1..* 1..* Doctor d .id : string; d.pwd : string; login() sendmessages() logout() 1..* 1..* 1..* 1

Component diagram:

patientdata base

Application

server database sever

doctor database

Deployment diagram: database server patient1 patient2 patientn application server doctor1 doctor2 doctor N

patient sign in searching the doctor request an appiontment recive appointment send diagnosis details recive prescription follow doctor instructions

State chart diagram for patient:

doctor sign in view the messages send an appiontment

recive patient health information

give the prescription to the patient in encrypted form

sign out view patient

health

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}