A Secure Privacy Preserving Cloud-based Framework for Sharing
Electronic Health Data
ABSTRACT
PHR System is a favorable platform for personal health information exchange. In order to
ensure that the personal information is not falsified and leaked by malicious users, we use the
attribute based signcryption technology to provide secure and reliable data protection. At the
same time, in order to prevent users from accessing the data in the system by collusion of
attributes, we proposes a revocable cloud-assisted attribute-based signcryption scheme which
using the broadcast encryption technology and key segmentation technology realize user
revocation function. Moreover, the proposed scheme is proven to be confidentiality and
unforgeability under chosen plaintext attack in the random oracle model. And the experimental
evaluation indicates that the proposed scheme is practical and feasible. With the development of
medical information technology, Personal Health Record (PHR) system is gradually developing
and improving. PHR system is a health record storage service system, which allows patients to
create, control and share their HR data with a wide range of target users, including doctors,
nurses, health insurance providers and family members. In order to improve the quality of PHR
services at a lower cost, PHR service providers want to store PHR users’ personal medical data
on cloud servers.
Software used:
FRONT END: PHP
BACK END: MYSQL
MODULES DESCRIPTION
Administrator
Administrator is the incharge of creating the doctors. The administrator can create
doctors and can remove unwanted doctor records. The doctor record includes name, gender,
address, qualification, certificate number, userid and password. The information can be viewed
in separate module and unwanted doctor records can be removed.
Doctor Login
Doctor is incharge of creating new patient records and uploading the disease records and
the presctiption records.
New Patient
In this module the doctor creates new patient information like name, blood group, gender,
address, mobile, userid and password of the patient. Then after uploading the record it is stored
in the server. When the patient accepts the upload then the records are encrypted using the
generated key for the user by the user and is uploaded to the server.
Upload Status
In this module, the doctor view the upload status of the patient records. If the user
generates the key then the record is encrypted and is uploaded to the server. Other wise it is not
encrypted. Also the doctor can view the encrypted patient records in this module. And
unwanted user records can be removed from the system.
Send Key Request
The doctor can send the key request to the patient. So if the patient accepts then the
doctor can enter the disease information, prescription information and can view the same of the
patient. If the user not accept the request the doctor cannot enter the patient health records.
Patient Login
The patient can login the system and can generate a key to encrypt the records in the
server. Then they can accept the doctor request so that the doctor can enter the health records.
Edit Profile
The patient can edit their profile in this module. The information like name, address,
city, blood group, password can be changed in this module.
Generate Key
The users can generate their key in this module. On clicking the link Generate Key the
key is generated and the user record is encrypted and is uploaded to the server.
Accept Request
The users can accept the doctor’s request in this module. Once accepted, the doctor can
enter the patient health records and prescription records to the server. The records are encrypted
by the key generated by the user and is uploaded to the server.
Revoke Doctor
In this module the accepted doctor request for the key can be revoked by the user. Once
the user revokes the doctor’s request, then the doctor cannot enter or view the users records to
the server.
EXISTING SYSTEM
In existing system there is no security key is generated by the user to upload data to the
server. In some system the key is generated in the server itself and is not secured. More over the
key cannot be revoked in the existing system. So once the permission is granted then the
permission cannot be revoked.
PROPOSED SYSTEM
In proposed system the user itself can generate the key to encrypt the data in the server.
Only after the user generates the key the data can be encrypted to the server. The user also
controls the doctors permission of enter or view the records. If the user revokes the permission
to the doctor, then the doctor cannot enter or view the patient records.
