| INFORMATION |
| Published : |
Aug 21, 2009 |
| Length : |
12 |
| Type : |
White Paper |
|
| |
|
|
|
| Overview : |
|
When the U.S. Congress passed the Health Insurance Portability and Accountability Act (HIPAA) of 1996, among the law's many provisions was the establishment of formal regulations designed to protect the confidentiality and security of patient information. In addition to mandating new policies and procedures, the HIPAA security regulations require mechanisms for controlling access to patient data on healthcare providers' information technology (IT) systems. |
|
 |
 |
|
|
| View All Items By This Company |
| Browse Related Categories : |
|
Access Control
,
Application Security
,
Authentication
,
HIPAA Compliance
,
Network Security
,
Single Sign On
|
|
|
|
|
|
|
|
When the U.S. Congress passed the Health Insurance Portability and Accountability Act (HIPAA) of 1996, among the law's many provisions was the establishment of formal regulations designed to protect the confidentiality and security of patient information. In addition to mandating new policies and procedures, the HIPAA security regulations require mechanisms for controlling access to patient data on healthcare providers' information technology (IT) systems. In response to these challenges, a growing number of healthcare institutions are turning to Enterprise Single Sign On (ESSO) solutions to help them comply with HIPAA's security requirements. ESSO solutions require a user to remember and provide just one set of credentials 'user name and password' to access the full portfolio of applications, data, and services for which that user is authorized.
|
|
|
|
 |
|
