Methods, systems, and media for determining application compliance with the health insurance portability and accountability act

A non-transitory computer readable medium comprising machine executable code that, upon execution by one or more computer processors of a computing device, cause the computing device to perform operations comprising:

• receiving a request to determine whether a software application is compliant with the Health Insurance Portability and Accounting Act (HIPAA), wherein the software application has access to a data object that includes at least protection health information (PHI) or personally identifiable information (PII);
• determining if the software application implements for the data object a threshold number of one or more safeguard techniques for each of a plurality of different types of safeguard techniques;
• determining that the software application is compliant with HIPAA in response to determining that the software application implements for the data object the threshold number of the one or more safeguard techniques for each of the plurality of different types of safeguard techniques;
• determining that the software application is not compliant with HIPAA in response to determining that the software application does not implement for the data object the threshold number of the one or more safeguard techniques for each of the plurality of different types of safeguard technique;
• and
• outputting, on a user interface, an indication indicating that the software application is compliant with HIPAA or not compliant with HIPAA.

A system for determining whether a software application, executing on an electronic device, is compliant with the Health Insurance Portability and Accountability Act (HIPAA), the system comprising:

• a processor coupled to a memory, the processor configured to:
• receive, over a computer network, a request to determine whether the software application is compliant with HIPPA, wherein the software application has access to a data object that includes at least protected health Information (PHI) or personally identifiable information (PII);
• determine if the software application implements for the data object a threshold number of one or more safeguard techniques for each of a plurality of different types of safeguard techniques;
• determine that the software application is compliant with HIPAA in response to determining that the software application implements for the data object the threshold number of the one or more safeguard techniques for each of the plurality of different types of safeguard techniques;
• determine that the software application is not compliant with HIPAA in response to determining that the software application does not implement for the data object the threshold number of the one or more safeguard techniques for each of the plurality of different types of safeguard technique;
• and
• output, on a user interface, an indication indicating that the software application is compliant with HIPAA or not compliant with HIPAA.