Methods and systems for health insurance portability and accountability act application compliance

Inventors

Longmire, Michelle Rae • Smith, Timothy Robert • Sas, James Marcel

Assignees

Medable Inc • Medable Inc

Interested in licensing this patent?

MTEC can help explore whether this patent might be available for licensing for your application.

Publication Number

US-11450415-B1

Patent

Publication Date

2022-09-20

Expiration Date


Abstract

Methods and systems for determining whether a software application that is executable by an electronic device is compliant under the Health Insurance Portability and Accountability Act (HIPAA) are provided. A software application is accessed over a network. A programmed computer processor is used to determine whether said software application, upon execution, is at or above an (i) access control threshold, (ii) audit control threshold, (iii) data integrity threshold, (iv) authentication threshold, and (v) transmission security threshold, which thresholds are minimum thresholds for HIPAA compliance. Additionally, a determination that said software application is HIPAA compliant is made if said software application, upon execution, is at or above (i) said access control threshold, (ii) audit control threshold, (iii) data integrity threshold, (iv) authentication threshold, and (v) transmission security threshold. Further, a determination as to whether said software application is HIPAA compliant is output.

Core Innovation

A HIPAA compliance platform determines whether a software application, executing on an electronic device, is compliant with the Health Insurance Portability and Accountability Act (HIPAA). The method receives, over a computer network, a request to determine compliance for a software application that has access to a data object including at least protected health information (PHI) or personally identifiable information (PII). The platform determines whether a threshold number of one or more safeguard technique categories is implemented for the data object by the software application.

The safeguard technique categories include access control, audit control, data integrity, authentication, and transmission security. HIPAA compliance is determined in response to determining that the software application implements each required threshold number across the five safeguard technique categories. The method then outputs an indication on a user interface indicating that the software application is compliant with HIPAA or not compliant with HIPAA.

A system and a non-transitory computer readable medium perform the same determination and output. The system includes a processor configured to receive the request, determine the threshold numbers of access control, audit control, data integrity, authentication, and transmission security safeguard techniques implemented for the data object, and output the user-interface indication of HIPAA compliant versus not compliant.

Claims Coverage

The independent claims are directed to determining HIPAA compliance for a software application by checking threshold numbers of safeguard technique categories implemented for a data object containing PHI and/or PII, and outputting a compliant vs. not compliant indication on a user interface.

Threshold-based safeguard category compliance determination

Determining that the software application is compliant with HIPAA in response to determining that the software application implements the threshold number of the one or more access control, audit control, data integrity, authentication, and transmission security safeguard techniques.

HIPAA compliance request receiving for PHI/PII-accessing software applications

Receiving, over a computer network and at a computing system including a processor, a request to determine whether the software application is compliant with HIPAA, wherein the software application has access to a data object that includes at least protected health information (PHI) or personally identifiable information (PII).

User interface output of HIPAA compliance indication

Outputting, on a user interface, an indication indicating that the software application is compliant with HIPAA or not compliant with HIPAA.

Non-transitory medium performing threshold safeguard compliance operations

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 receive a request to determine whether a software application is compliant with HIPAA, determine whether threshold number safeguard techniques are implemented for the data object, determine that the software application is compliant with HIPAA in response to implementing the threshold numbers across access control, audit control, data integrity, authentication, and transmission security, and output an indication indicating that the software application is compliant with HIPAA or not compliant with HIPAA.

System for threshold-based HIPAA compliance determination

A system for determining whether a software application, executing on an electronic device, is compliant with HIPAA, the system comprising a processor configured to receive a request, determine whether threshold numbers of access control, audit control, data integrity, authentication, and transmission security safeguard techniques are implemented for the data object, determine that the software application is compliant with HIPAA in response to implementing the threshold numbers across the categories, and output an indication on a user interface indicating that the software application is compliant with HIPAA or not compliant with HIPAA.

Across the independent claims, compliance is determined only after threshold numbers of safeguard techniques are verified for each of the five safeguard categories—access control, audit control, data integrity, authentication, and transmission security—for a data object containing PHI and/or PII, and a user-interface indication is output accordingly.

Stated Advantages

Outputs an indication that the software application is compliant with HIPAA or not compliant with HIPAA.

Determines HIPAA compliance by verifying threshold numbers of safeguard technique categories implemented for a data object containing PHI or PII.

Documented Applications

Assessing whether a software application accessing protected health information (PHI) or personally identifiable information (PII) is compliant with HIPAA, including outputting a compliant vs. not compliant indication on a user interface.

JOIN OUR MAILING LIST

Stay Connected with MTEC

Keep up with active and upcoming solicitations, MTEC news and other valuable information.