Slideshow 10 Myths of a Meaningful Use Security Risk Analysis

  • December 15 2013, 2:40pm EST
11 Images Total

The Centers for Medicare & Medicaid Services recently released a tip sheet for eligible professionals on 10 myths associated with conducting a HIPAA security rule risk analysis to ensure the privacy and security of their patients' protected health information, which is a requirement in the EHR meaningful use program. Here are the facts.

MYTH: The security risk analysis is optional for small providers.

FACT: All providers who are covered entities under HIPAA are required to perform a risk analysis. In addition, all providers who want to receive EHR incentive payments must conduct a risk analysis.

Content Continues Below

MYTH: Simply installing a certified EHR fulfills the security risk analysis meaningful use requirement.

FACT: Even with a certified EHR, you must perform a full security risk analysis. Security requirements address all electronic protected health information you maintain, not just what is in your EHR.

MYTH: My EHR vendor took care of everything I need to do about privacy and security.

FACT: Your EHR vendor may be able to provide information, assistance and training on the privacy and security aspects of the EHR product. However, EHR vendors are not responsible for making their products compliant with HIPAA privacy and security rules. It is solely your responsibility to have a complete risk analysis conducted.

MYTH: I have to outsource the security risk analysis.

FACT: It is possible for small practices to do risk analysis themselves using self-help tools. However, doing a thorough and professional risk analysis that will stand up to a compliance review will require expert knowledge that could be obtained through services of an experienced outside professional.

Content Continues Below

MYTH: A checklist will suffice for the risk analysis requirement.

FACT: Checklists can be useful tools, especially when starting a risk analysis, but they fall short of performing a systematic security risk analysis or documenting that one has been performed.

MYTH: There is a specific risk analysis method that I must follow.

FACT: A risk analysis can be performed in countless ways. OCR has issued Guidance on Risk Analysis Requirements of the Security Rule. This guidance assists organizations in identifying and implementing the most effective and appropriate safeguards to secure e-PHI.

MYTH: My security risk analysis only needs to look at my EHR.

FACT: Review all electronic devices that store, capture or modify electronic protected health information. Include your EHR hardware and software and devices that can access your EHR data (e.g., your tablet computer, your practice manager’s mobile phone). Remember that copiers also store data. See U.S. Department of Health and Human Services guidance on remote use.

Content Continues Below

MYTH: I only need to do a risk analysis once.

FACT: To comply with HIPAA, you must continue to review, correct or modify, and update security protections.

MYTH: Before I attest for an EHR incentive program, I must fully mitigate all risks.

FACT: The EHR incentive program requires correcting any deficiencies (identified during the risk analysis) during the reporting period, as part of its risk management process.

MYTH: Each year, I’ll have to completely redo my security risk analysis.

FACT: Perform the full security risk analysis as you adopt an EHR. Each year or when changes to your practice or electronic systems occur, review and update the prior analysis for changes in risks. Under meaningful use, reviews are required for each EHR reporting period. For EPs, the EHR reporting period will be 90 days or a full calendar year, depending on the EP’s year of participation in the program.