39
Data Governance and HIPAA Risk Assessments www.hipaatrek.com [email protected] 314-272-2600 Presented by Sarah Badahman CEO/Founder, HIPAAtrek

Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

  • Upload
    others

  • View
    3

  • Download
    0

Embed Size (px)

Citation preview

Page 1: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

Data Governance and HIPAA Risk Assessments

[email protected]

Presented by Sarah BadahmanCEO/Founder, HIPAAtrek

Page 2: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

What is data governance?

Information Governance (IG): is organization-wide framework for managing information throughout its lifecycle and supporting the organization’s strategy, operations, regulatory, legal, risk, and environmental requirements.

Data Governance (DG): is the responsibility of the business unit. It is the policies, processes, and practices that address the accuracy, validity, completeness, timeliness and integrity of data (data quality)

(AHIMA via http://www.ahima.org/topics/infogovernance/ig-glossary )

Page 3: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

What is data governance?

Information Governance

Creation &

ContentPrivacy

Security

Retention

Retrieval

Disposition

Page 4: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

What is data governance?

Written Policies and Procedures: These policies should be accessible to providers and staff so that questions about business processes can be easily answered. Those policies might include:

§ Registration and Front Desk Processes§ Content of the Medical Record§ Privacy and Security § Employee Training, Training Records, and Acknowledgments§ Release of Information Procedures§ Internal Audit Processes§ External Audit Processes§ Storage, Retention and Disposition of Health Information (PHI)§ Storage, Retention and Disposition of Business Records

Provider and Staff Education: An organization should train providers and staff on policies and procedures at hire and at least annually thereafter. Inter-periodic training may be needed to reteach whenever questions, incidents or weaknesses are detected.

Page 5: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

Policies and Procedures

Page 6: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

Policies and Procedure (Safeguards)

n Policies: Define an organization’s approach

n Procedures: Describe how the organization carries out that approach.

n Both should reflect the mission and culture of the organization

Page 7: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

Privacy Rule

Page 8: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

Security Rule

Page 9: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

Breach Notification Rule

Page 10: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

n Legalese: “Retain the documentation required by paragraph (b)(1) of this section for 6 years from the date of its creation or the date when it last was in effect, whichever is later.”

n Version control managementn Be sure to notate when the policy was first created

n Be sure to notate when the policy is updated

n Maintain each new version for the time limit required by law

Time LimitTime Limit

Page 11: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

Availability

n Legalese: “Make documentation available to those persons responsible for implementing the procedures to which the documentation pertains.”

n Considerations:n Having printed manuals for your management and staff

n Posting your policies and procedures on your intranet

n Using a software management system to manage and share your policies and procedures

Page 12: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

Updates

n Legalese: “Review documentation periodically, and update as needed, in response to environmental or operational changes affecting the security of the electronic protected health information.”

n Considerations:n Frequency of reviews

n Operational Changes

n Move to EMR

n Change EMR

n Physical location

n Identified threats in risk analysis

n Major staffing changes

Page 13: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

Implementing HIPAA

Page 14: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

Define Measure Analyze Improve Control

Process Approach

Page 15: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

Project Management Approach to HIPAA Compliance: Define for each process or policy

Page 16: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

Each process defined should be evaluated and broken down into the smallest process possible

Page 17: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

Project Management Approach to HIPAA Compliance: Measure current progress or performance for each defined goal or process

Page 18: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

Project Management Approach to HIPAA Compliance: Analyze to determine if the process is meeting the objectives. Discover root cause if not meeting goals.

Page 19: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

Analyze: Threat Analysis

Goal Root Cause

Unable to quantitativelyasses threats to third party applications –i.e. EMR

We do not have control over business associate environments

Successful Not Meeting Goals

n Determined Threat Model: STRIDE and DREAD

n Determined Methodology

Page 20: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

Project Management Approach to HIPAA Compliance: Improve the problem by selecting a solution

Page 21: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

Improve: Threat Analysis

n Survey business associates for their compliance/security controls

n Conduct a qualitative analysis based off variables we have control over

Brainstorm and select solution

Goal Root Cause

Unable to quantitatively asses threats to third party applications –ie EMR

We do not have control over business associate environments

Not Meeting Goals

Page 22: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

Project Management Approach to HIPAA Compliance: Control the improved process to ensure goals are met

Page 23: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

RACI Approach to HIPAA

n What is RACI?n Responsible: responsible for doing the actual work

n Accountable: ultimately accountable for the completion of the work

n Consulted: provide input/output as needed

n Informed: want/need to be kept up-to-date

n Rolesn Champion

n Business Owner

n Process Owner

n Subject Matter Expert

Page 24: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

Example: Threat AnalysisDefine Measure Analyze Improve Control

Privacy Officer

C I I C C

Security Officer

R R R R R

IT Department

A A A A A

Management C C C C C

Employees n/a n/a n/a n/a n/a

Champion: Privacy OfficerBusiness Owner: Security Officer

Process Owner: ManagementSME: IT Department

Roles:

Page 25: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

Create An Auditable Trail of Compliance

Document every compliance activity

Who, when, where, why, and how of every activity

Page 26: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

OCR HIPAA Enforcement

• 2016 Phase 2 Audits

• 2017 Business Associate Audits

• Stage 3 of Phase 2 Audits will include on-site audits

• Information Gathering vs Punitive

• Prepare now! Only 10 days to respond when chosen for an audit

• Only submit requested information

Page 27: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

Risk Analysis

Page 28: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

Preparing for the Risk Analysis

n Scope the Assessmentn Which systems and/or processes

will be included in the assessment?

n What is the purpose of the assessment? Routine, response to a breach or client request, or adopting new technology or moving/adding a new physical location?

n Gather Informationn Where is PHI created, received,

maintained, processed or transmitted? n This should correlate with your

inventoryn What controls (policies or

procedures) are in place to protect the security and privacy of your PHI and how effective are they?

Page 29: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

Assessing Treats and Vulnerabilities

n Identifying Threats

n Choose a threat modeln STRIDE

n DREADn Assess known potential threats

n Technical

n Environmentaln People

n Identifying Vulnerabilities

n Run a Vulnerability Scann Rapid Fire, Provensec, or other

similar tooln Use the National Database of

Vulnerabilities

n Enlist the assistance of your IT Department or IT vendor to assess your technical vulnerabilities

n Conduct a site survey to identify non-technical vulnerabilities

Page 30: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

Threat Likelihood

n Using the threats and vulnerabilities identified in the previous step

n Determine the likelihood of a threat exposing a vulnerability

n Assess by threat, using the model determined in the previous step

n Prioritize threat likelihood using a quantitative, qualitative or hybrid model

Page 31: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken
Page 32: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

Assessing Policy Effectiveness

n Conduct a Policy Gap Analysisn Assess whether or not all required implementation specifications have policies

createdn Assess how well they are implemented

n Survey workforce members on HIPAA policy adherence

Page 33: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

Assessing Treats and Vulnerabilities

n Determine the Level of Riskn Using the previous steps,

assess the overall risk to your PHI security and privacy

n Risk = (Threats x Vulnerabilities x Impact) -Controls

n Recommend Security Controls

n Based on the findings from all the previous steps, create a risk management plan to address identified threats and vulnerabilities designed to reduce the impact to your organization

Page 34: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

Creating a Culture of Security

Page 35: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

Avoid Treating Your Work Environment Like Your Home Environment

n Computing habitsn Browsingn Emailn Social Media

n Physical Securityn Leaving unlocked and unattendedn Leaving mobile devices in vulnerable areas

n Security Practicesn Passwordsn Firewallsn Audit Procedures

Page 36: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

Avoid Outdated Technologyn Outdated technology costs the health industry $8.3B annually

n Reliance on legacy systems

n Older technology more prone to crashes

n Incapability with newer softwares

n Higher prevalence of cyber attacks and malware

n Less likely to be supported by the manufacturer

n Lost productivity and revenue

n Use of home or non-commercial technology

Page 37: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

Bolster BYOD Policy

n Devices included:n Laptops, tablets, mobile phones, company owned, employee

owned, non-employee owned

n Rules regarding:n What is allowed based on operating systems

n What devices, data types or applications are restricted

n Monitoring of devices

n Basic controls required for each device

n Enhanced controls required for certain devices

Page 38: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

Encryption Practicesn Encrypt data at rest

n Full Disk encryption

n Only effective on an unbooted computer

n Files are not protected when moved

n File Encryption

n Stay encrypted regardless of where they are stored

n As long as the file is ‘at rest’ it is encrypted

n Most thefts involving portable devices and laptops involved unencrypted devices

n Encrypt smart phones and tablets that store, transmit, access ePHI

n Many cost affective solutions

n AES-256 is industry standard in the healthcare industry

Page 39: Data Governance and HIPAA Risk Assessments… · Project Management Approach to HIPAA Compliance: Define for each process or policy. Each process defined should be evaluated and broken

Questions?

?? ? ? ?? ?

[email protected]