| Javascript Feeds RSS Feed Security Dashboard | SearchSecurity.com |
|
New HIPAA Rules Could Affect Your Organization's Email System On April 21, 2005 a new Health Insurance Portability and Accountability Act (HIPAA) security rule went into effect. The new rule affects many types of organizations, not just healthcare companies. Failure to adhere to the new guidelines could cost your company up to $250,000 per infraction! Make sure your email system complies with federal laws.
Paul Judge,
06/06/2005
|
|
Introduction to HIPAA This paper will outline the HIPAA security rules. The final standards were published in the February 20 Federal Register with an effective date of April 21, 2003. Most covered entities will have two full years -- until April 21, 2005 -- to comply with the standards.
Mitchell Rowton,
11/12/2004
|
|
What is HIPAA? HIPAA is an acronym for the Health Insurance Portability and Accountability Act, passed by Congress in 1996. The purpose of the Act was to increase the ease with which people could transfer their health care information from one insurer or provider to the next. As part of HIPAA, Congress required the development of privacy regulations to protect the confidentiality of individually identifiable health care information. The final Privacy Rule was issued on August 14, 2002.
By University of Arizona, 06/29/2004
|
|
Impact of HIPAA Security Rules on Healthcare Organizations The HIPAA regulations contain a section called Administrative Simplification (Title II, Subtitle F) that articulates the Security rules (along with the Transaction and Privacy rules) for healthcare organizations that transmit or posses protected health information. This paper focuses on the impact of the Security rules.
By Tim Ferrell, 05/11/2004
|
|
The HIPAA Final Security Standards and ISO/IEC 17799 Compliance with the HIPAA Final Security Standards is a regulatory requirement for healthcare organizations. ISO/IEC 17799 is an international information security standard. This paper compares these two standards to see whether if in complying with one of the standards, the other is also satisfied. The paper concludes that the HIPAA Final Security Standards has a small number of requirements not covered by ISO/IEC 17799, and that ISO/IEC 17799 has a number of controls not covered by the HIPAA Security Standards. A detailed analysis and crossreference is provided along with an approach to compliance with both standards.
By Sheldon Borkin, 05/11/2004
|
|
HIPAA Security Standards v1.2d The very nature of the Internet communication mechanisms means that security risks cannot be totally eliminated. (Rada) Couple such Internet-based security risks with the everyday risks associated with processing thousands of claims and other related medical documents, the Federal government felt a necessity to take action to protect the confidentiality of medical records.
By Daniel Fagin, 05/11/2004
|
|
Windows 2000 White Paper - Health Insurance Portability and Accountability Act (HIPAA) The Health Insurance Portability and Accountability Act (HIPAA) proposes standards regarding the security of individual health information. To understand the impact of these standards on the Information Technology (IT) environment within the healthcare organization, it is useful to examine the regulations and the applicable software tools and technologies that may be used to securely create, maintain, transmit and store health information.
04/23/2004
|
|
Securing Wireless Networks for HIPAA Compliance The intent of this paper is to discuss wireless networks and why it is useful to organizations, namely healthcare organizations. Once we have established the foundation for why we need wireless, we will cover the vulnerabilities and problems with wireless networks. We will then take a tour of recent laws that govern healthcare organizations, and how these laws affect wireless networks. After this overview a more thorough interpretation of the laws will be presented with details on what each part means in relation to wireless. Our next step, will be to take a network and work through any current problems. We will then apply different technologies and configuration changes to that network in order to provide security that will meet the requirements set forth previously. We will then examine briefly a snapshot of the network after our security implementation. Finally we will sum up the paper with a conclusion of what we have found through this case study.
By Daniel Odorisio, 04/18/2004
|
|
A Context-Based Access Control Model for HIPAA Privacy and Security Compliance It is somewhat ironic that the Administrative Simplification1 subtitle of HIPAA, the Health Insurance Portability and Accountability Act of 1996, includes several provisions that result in administrative complexity of a hitherto unknown degree. Cumbersome record keeping and reporting requirements offset the benefits brought about by claims-processing automation. This paper proposes a new approach to meeting much of the burden imposed by the HIPAA privacy and security requirements. By adopting this approach, an organization may avail itself of the significant benefits brought about by transaction standardization and, at the same time, avoid the unwanted side effects of having to adopt inconvenient manual processes.
04/15/2004
|
|
HIPAA Compliance: Cost-Effective Solutions for the Technical Security Regulations While HIPAA is comprised of many different regulations, the objective of this document is to suggest cost-effective solutions to the proposed Technical Security Mechanisms regulation. The scope includes suggestions for a combined Windows NT and UNIX environment. Please note that there are numerous variations of each operating system, and certain techniques outlined in this paper might not be available or may function differently depending on the configuration of a company’s systems.
04/15/2004
|
|
Page: 1 2 |
