WHAT ARE THE RESPONSIBILITIES OF A HIPAA COMPLIANCE OFFICER? Flashcards
The Healthcare Insurance Portability and Accountability Act (HIPAA) requires covered entities and business associates to have a HIPAA compliance officer.
This position may be filled in by an existing employee or a new employee can be recruited to take on the role.
It is also permitted for the position to be outsourced temporarily or permanently.
What do HIPAA Compliance Officers do?
The volume of work of a HIPAA compliance officer depends on two things: The size of the covered entity or business associate and the number of patients/amount of protected health information (PHI) that is created, used and maintained.
The duties of a HIPAA compliance officer in large healthcare organizations are often divided between two individuals –
A HIPAA security officer and a HIPAA privacy officer.
The responsibilities of a HIPAA privacy officer include:
1) Developing and maintaining a HIPAA-compliant privacy program
2) Ensuring the enforcement of privacy policies
3) Overseeing the privacy training of employees
4) Conducting a risk analysis and creating HIPAA-compliant procedures where needed
5) Monitoring compliance with the privacy program
Investigating and reporting incidences of data breaches
6) Ensuring the protection of patients’ rights in accordance with federal and state laws
7) Keeping up-to-date with pertinent state and federal laws
The responsibilities of a HIPAA Security Officer are similar to those of a Privacy Officer. That individual is also responsible
1) for developing security policies,
2) implementing procedures,
3) conducting training, and
4) performing risk analyses and
5) monitoring compliance.
Where the role of a HIPAA security officer differs from a HIPAA privacy officer is the security officer’s focus is more
about compliance with the administrative, physical and technical safeguards of the HIPAA Security Rule and general Security Rule compliance.
Specific duties of HIPAA security officer can include
1) developing a disaster recovery plan,
2) implementing mechanisms for preventing unauthorized PHI access and
3) mechanisms for secure electronic PHI transmission and storage.
HIPAA regulations do not give an exact definition of the duties and responsibilities of a HIPAA compliance officer. It is up to the covered entity or business associate to determine what duties are required according to the organization’s specific requirements.
In order to be effective,
it is essential for HIPAA compliance officers, security officers, and privacy officers to have a thorough working knowledge of HIPAA regulations and the HITECH Act, and to be families with state laws concerning the privacy and security of personal and health information.
HIPAA PASSWORD REQUIREMENTS
Like many requirements of the Health Insurance Portability and Accountability Act (HIPAA), the HIPAA password requirements are written in a way that covers many different present and future scenarios. Consequently, the requirements can be a source of confusion for Covered Entities and Business Associates.
Employers – despite maintaining health care information about their employees – are
not generally Covered Entities unless they provide self-insured health cover or benefits such as an Employee Assistance Program (EAP).
In these cases they are considered to be “hybrid entities” and any unauthorized disclosure of PHI may still be considered a breach of HIPAA.
On January 5, 2020, President Trump signed bill HR 7898 into law, which amends the Health Information Technology for Economic and Clinical Health Act (HITECH Act) to create a safe harbor for healthcare organizations and business associates that
have implemented recognized security best practices prior to experiencing a data breach.
HR 7898
The aim of the bill is to encourage HIPAA-covered entities and their business associates to adopt a common security framework.
The update requires the HHS’ Office for Civil Rights to take security best practices, such as the adoption of a recognized cybersecurity framework, into consideration when deciding on penalties and sanctions related to data breaches.
The bill also requires the HHS to decrease the extent and length of audits when an entity has achieved industry-standard security best practices.
President Trump yesterday signed into law a bill (H.R. 7898) containing provisions that require the Secretary of Health and Human Services to consider certain recognized cybersecurity best practices when making determinations against HIPAA-covered entities and business associates victimized by a cyberattack.
For example, the bill recognizes cybersecurity practices established under the National Institute of Standards and Technology Act and approaches established under Section 405(d) of the Cybersecurity Act of 2015 by the Healthcare and Public Health Sector Coordinating Council (HSCC) Working Group, whose members include the AHA.
The HR 7898 bill defines these security practices as:
1) Standards, guidelines, best practices, methodologies, procedures, and processes developed under the National Institute of Standards and Technology Act (NIST Act).
2) The cybersecurity practices developed under section 405(d) of the Cybersecurity Act of 2015.
Programs and practices that are developed in, recognized by, or set forth in federal laws other than HIPAA.
3) This standards are already defined by other institutions like the NIST and others. Although in theory you should already be doing these things, the government has decided to incentivize good practice.
HR 7898 Not a Safe Harbor
While some have referred to HR 7898 as a HIPAA Safe Harbor, the provision does not help healthcare covered entities or business associates avoid liability for HIPAA violations. The law clearly states that “Nothing in this section shall be construed to limit the Secretary’s authority to enforce the HIPAA Security rule (part 160 of title 45 Code of Federal Regulations and subparts A and C of part 164 of such title), or to supersede or conflict with an entity or business associate’s obligations under the HIPAA Security Rule.” Instead, it requires HHS Office for Civil Rights (OCR) to consider if the covered entity or business associate adequately demonstrated that it adopted certain recognized cybersecurity practices for the year preceding an audit or investigation. If so, OCR should consider this when determining the length and outcome of the audit, fines, or resolution agreement terms.