Understanding Software with HIPAA Compliance

In the software industry, HIPAA compliance can be complicated and confusing. The data your business handles will determine if you need to be compliant or not. If you do need to be compliant, there are many questions you need to ask. One of the largest being, do you host your data internally or in the cloud? Here we aim to better help you understand HIPAA compliance and provide you with some resources to help evaluate your needs.

The Health Insurance Portability and Accountability Act of 1996 (HIPAA) required the Secretary of the U.S. Department of Health and Human Services (HHS) to develop regulations protecting the privacy and security of certain health information.1 To fulfill this requirement, HHS published what are commonly known as the HIPAA Privacy Rule and the HIPAA Security Rule. The Privacy Rule, or Standards for Privacy of Individually Identifiable Health Information, establishes national standards for the protection of certain health information. The Security Standards for the Protection of Electronic Protected Health Information (the Security Rule) establish a national set of security standards for protecting certain health information that is held or transferred in electronic form. The Security Rule operationalizes the protections contained in the Privacy Rule by addressing the technical and non-technical safeguards that organizations called “covered entities” must put in place to secure individuals’ “electronic protected health information” (e-PHI). Within HHS, the Office for Civil Rights (OCR) has responsibility for enforcing the Privacy and Security Rules with voluntary compliance activities and civil money penalties.

Today, providers are using clinical applications such as computerized physician order entry (CPOE) systems, electronic health records (EHR), and radiology, pharmacy, and laboratory systems. Health plans are providing access to claims and care management, as well as member self-service applications. While this means that the medical workforce can be more mobile and efficient (i.e., physicians can check patient records and test results from wherever they are), the rise in the adoption rate of these technologies increases the potential security risks.

A major goal of the Security Rule is to protect the privacy of individuals’ health information while allowing covered entities to adopt new technologies to improve the quality and efficiency of patient care. Given that the health care marketplace is diverse, the Security Rule is designed to be flexible and scalable so a covered entity can implement policies, procedures, and technologies that are appropriate for the entity’s particular size, organizational structure, and risks to consumers’ e-PHI.

Below is a slide show presentation from TrueVault that will shed some light on HIPAA compliance for software developers, or anyone thinking about building software with HIPAA compliant data.

Additional resources for this article came from the HHS.gov website.

Comments are closed.

Get Amazing Deals!

Get great deals on technology, delivered straight to your inbox every month. Laptops, desktops, monitors, wireless equipment, virus scan software and more. Just a click away, sign up now!
Email address
First Name
Last Name
Secure and Spam free...