AUTHENTICATED MEDICAL DOCUMENTS RELEASING WITH PRIVACY PROTECTION AND RELEASE CONTROL
INTRODUCTION
There are enormous opportunities offered by digital data collected by both commercial enterprises and government agencies; a lot of these provide for product-based uses. These advantages make for a very strong demand for publication and supply of data. That is, however, extremely important personal information in the original documents would be compromised if it was released to the public without any processing. An easy method for privacy preservation is to edit documents by blurring sensitive data I’ve therefore developed a project on medical documents privacy in which I have to take four steps to inform the doctor about the patients’ personal issues. More or less, so many different requests and keys are generated during this process so that the information is observed and decrypted so that information can be input by the doctor at once.
MAIN FUNCTIONING OF PROJECT
The Above Figure (Or) Use case Diagram shows my Overall View of My project like how exact Functioning is happening inside the project.
Starting With Basically, There are 3 servers in This Project Namely Cloud Server, PHR User, PHR owner.
CLOUD SERVER- Basically This is An authorization server wherein all requests go into this server requested by the PHR User and PHR Owner.
PHR OWNER- This is a Patient Portal Where In-Patient Registers In This Portal By asking all his personal information. Basically, there is a Form wherein he/she needs to fill in the details like about the disease they are facing from and to which doctor he/she needs to consult and also they are much personal information being asked about the past history and which blood groups he belongs to and after filling all these details he will be encrypting and upload his details and after he has done this in-order to recheck again he can see all his details filled in view patient section in This Portal Itself(PHR OWNER). After Filling in all these details the request goes to PHR USER.
PHR USER: This is a Doctors' Portal where he can see all the details filled by the patients or else requests received by the patients. Whenever a patient Fills his details in the PHR OWNER Portal the request goes to PHR USER Portal i.e doctor's portal. So When a doctor gets logged into this portal he will be asking for a provider name and patient name and after filling in these two details the request will be going to the Patients Portal i.e PHR OWNER Portal and when a patient sees this request he generates One Key and Once Doctor sees this key in his portal he will again ask for the request now in which this request to Cloud Server. Now as the request forwarded by the doctor went to Cloud Server, we need to go to the cloud server and provide two permissions namely document permission and Details Permission. So After Providing These Two Permissions Doctor can see the patient's details and also the document in which it states from which disease the patient is suffering. Now after seeing all these details he can generate the clinical report by writing some suggestions or else writing some medicines for the patient in order to get cured of the disease.
So the last step is When Doctor generates the clinical report the request goes to the Cloud Server and when the request is accepted in the cloud server the patient can see the prescription written by the doctor in his portal.
TECHNOLOGIES USED:
DATABASE CONNECTIVITY: JDBC
DATABASE: My SQL
FRONTEND: HTML,JAVA,JSP
APPLICATION SERVER: Tomcat 5.0
SERVER SIDE SCRIPT: Java Server Pages
SNAPSHOTS OF THE PROJECT
Above are Some Important Snapshots to get more insight and a broader view of this Project.
I Would Like To Say Sincere Thanks to TechCiti Technologies Pvt Ltd and my mentor Gayatri Mam for helping me Throughout this project and achieving the beautiful outcome at the end of this.
Thank you!!
Keep Smiling!😀