CHAPTER - 1
INTRODUCTION
The application of information technology to healthcare has become increasingly important in many countries in the recent years. As on several applications has been ruminate in electronic healthcare (e-health), e.g., electronic health records, accounting and billing, medical research, and trading intellectual property .In particular Personal Health Records(PHRs) are believed to abate costs in healthcare and to improve personal health management in general. Healthcare organizations also must comply with multiple standards and regulations regarding patient data privacy, including those issued by the Joint Commission, the Health Insurance Portability and Accountability Act (HIPAA), and individual states. Accordingly, they
…show more content…
While it is exciting to have convenient PHR services for everyone, there are many security and privacy risks.
Which could impede its wide adoption? The main concern is about whether the patients could actually control the sharing of their sensitive personal health information (PHI), especially when they are stored on a third-party server which people may not fully trust.
2.1 DISADVANTAGES OF EXISTING SYSTEM:
There have been wide privacy concerns as personal health information could be exposed to those third party servers and to unauthorized parties.
Department of Veterans Affairs database containing sensitive PHI of 26.5 million military veterans, including their social security numbers and health problems was stolen by an employee who took the data home without authorization.
They usually assume the use of a single trusted authority (TA) in the system. This not only may create a load bottleneck, but also suffers from the key escrow problem since the TA can access all the encrypted files, opening the door for potential privacy exposure. In addition, it is not practical to delegate all attribute management tasks to one TA, including certifying all users’ attributes or roles and generating secret
…show more content…
Be independent of particular programming languages and development process.
4. Provide a formal basis for understanding the modelling language.
5. Encourage the growth of OO tools market.
6. Support higher level development concepts such as collaborations, frameworks, patterns and fundamentals.
7. Integrate best practices.
5.3 CLASS DIAGRAM:
In software engineering, a class diagram in the Unified modelling Language (UML) is a type of static structure diagram that describes the structure of a system by showing the system's classes, their attributes, operations (or methods), and the relationships among the classes. It explains which class contains information.
5.4 USE CASE DIAGRAM:
A use case diagram in the Unified Modeling Language (UML) is a type of behavioral diagram defined by and created from a Use-case analysis. Its purpose is to present a graphical overview of the functionality provided by a system in terms of actors, their goals (represented as use cases), and any dependencies between those use cases. The main purpose of a use case diagram is to show what system functions are performed for which actor. Roles of the actors in the system can be depicted.
PHR USE CASE