Projects

CROSS DOMAIN DATA SHARING IN DISTRIBUTED ELECTRONIC HEALTH RECORD SYSTEM

You are not Member of this Project.
Project Owner : N.SUBATHRA
Created Date : Fri, 24/02/2012 - 20:43
Project Description :

 

TITLE:

CROSS DOMAIN DATA SHARING IN DISTRIBUTED ELECTRONIC HEALTH RECORD SYSTEM

ABSTRACT :

Cross-organization or cross-domain cooperation takes place from time to time in Electronic Health Record (EHR) system for necessary and high-quality patient treatment. Cautious design of delegation mechanism must be in place as a building block of cross-domain cooperation, since the cooperation inevitably involves exchanging and sharing relevant patient data that are considered highly private and confidential. The delegation mechanism grants permission to and restricts access rights of a cooperating partner. Patients are unwilling to accept the EHR system unless their health data are guaranteed proper use and disclosure, which cannot be easily achieved without cross-domain authentication and fine-grained access control. In addition, revocation of the delegated rights should be possible at any time during the cooperation. In this paper, we propose a secure EHR system, based on cryptographic constructions, to enable secure sharing of sensitive patient data during cooperation and preserve patient data privacy. Our HER system further incorporates advanced mechanisms for fine-grained access control, and on-demand revocation, as enhancements to the basic access control offered by the delegation mechanism, and the basic revocation mechanism, respectively. The proposed HER system is demonstrated to fulfill objectives specific to the cross-domain delegation scenario of interest.

 SYSTEM ANALYSIS:

 

System analysis refers to the process of examining the business situation with the Internet of improving it through better procedures and methods. It involves the process of gathering, interpreting and diagnosing problem and using the information to recommend improvements to the system.

 

 Existing System

 

            The Existing System is don’t have any cross-domain data sharing facility. It had only share data between specified domains only. This would take time for large amount of employee working concern.

 

 DRAWBACKS

 

The concern must track the overall process flow and measure the accuracy of workflow. All the process will consume more time.

 

Proposed System

           

Our system achieves minimal privilege delegation if the delegator is able to specify which data portions of a patient can be accessed by the delegatee, even if these data portions belong to a same document of the patient as those that cannot be accessed by the delegatee.

Our system realizes access control if no entities other than the delegated (or authorized) entities can access the patient data intended for the delegated entities only.

This system encompasses legal, regulatory, behavioral, and sociological aspects of the current system, while adding additional convenience and security to the overall process. The proposed system provides

 

·         To make the data entry and updating more flexible.

·         The system makes information retrieval easy.

·         It provide details through user friendly GUIs.

·         This system provides security.

·         Data redundancy and data inconsistency can be avoided.

 


 FEASIBILITY STUDY

 

Feasibility study was conducted on the candidate system to check whether it can proceed with the new system. This Study identifies, describes and evaluates the candidate systems and Select the best system for the job.

 

 The study of this software answer three key questions

 

v  Is there a new and better way to do the job that will benefit the user?

v  What are the costs and savings of the alternative(s)?

v  What is recommended?

 

After problem is clearly understood and solution are proposed the next step is to conduct the feasibility study, which is part of system analysis as well as design process.  

ECONOMICAL  FEASIBILITY

            Economic feasibility is the most frequently used method for evaluating the effectiveness of a new system. The procedure is to determine the benefits of savings that are expected from a candidate system and compare them with costs. If benefit outweighs costs, then the decisions are made to design and implement the system. Though initial investment is high the benefits that will be reaped in along the term is high. Since the new system is developing in client/server environment it is user-friendly to work with and since it also removes the drawback of the existing system it was considered economically feasible to proceed with the system.

 TECHNICAL FEASIBILITY

Technical feasibility centers on the system and what extent it can support the proposed addition. This involves financial consideration to accommodate technical enhancements. If the budget is the series constraint then the project is judged not feasible. The hardware requirements for the new system are the client is ready to install the necessary software like, so the system was considered technically to proceed with.

 

OPERATIONAL FEASIBILITY

 

An estimate made of how strong a reaction the user staff is likely to have toward the development of a computerized system. The operation of the system becomes easy, so it was considered operationally feasible to proceed with the system.

Proposed system: 

The Proposed system offers greater levels of user friendless combined with greater processing speed is very high compared to that of manual on the management can take timely actions depending on information obtained. Since the workload is also reduced the management convenience that the project is operationally feasible.

           

After the feasibility study, the analyst has to formulate the problem.  Whenever there is a problem defined in clear terms, then only the analyst can solve it using the necessary steps.  This will help to modularize the problem.  Hence the stage of system study and problem formulation places an important role in the system development life cycle.

 SYSTEM SPECIFICATION

HARDWARE REQUIREMENT

 

CPU Type                                           :           Pentium III

 

                        CPU Clock Speed                               :           735 MHz

 

                        Memory                                               :           128 RAM

 

                        Hard Disc Capacity                            :           20 GB

 

                        Floppy   Drive                                     :           1.44 MB

 

                        Display Type                                       :           VGA

 

                        Key Board                                          :           101-102 Enhanced

 

                        Terminal Type                                     :            Pentium – III

 

 

 

 SOFTWARE REQUIREMENT

Operating System                   :           WINDOWS 2000

 

Service Pack                            :           WINDOWS 2000 SERVICE PACK

 

 

 

Software Used

Front - End                             :           Microsoft Visual Studio .NET 2005

 

Back - End                              :           SQL SERVER 2005

 

You are not authorized to access this content.
You are not authorized to access this content.
You are not authorized to access this content.
You are not authorized to access this content.
You are not authorized to access this content.