Jlhoffman Support

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Saturday, 10 August 2013

HIPAA Omnibus Rule Compliance Deadline is Near. Are you ready?

Posted on 15:14 by Unknown
The Omnibus Final Rule (Omnibus Rule) was released on January 17, 2013.   HIPAA covered entities and business associates are required to be fully compliant with the Omnibus Rule by September 23, 2013.  Are you ready?

In order to comply with the Omnibus Rule, organizations must update their internal privacy policies to reflect the changes to the HIPAA Privacy Rule, Security Rule, and Breach Notification Rule.  Here is a quick summary of those changes:

Release of Decedents’ PHI.

Under the Omnibus Rule, the definition of “protected health information” now expressly excludes the health information of a person who has been deceased for more than 50 years. In addition, the Omnibus Rule provides that providers may disclose the PHI of a deceased person to such person’s family members, relatives or other individuals indicated by the deceased, who were involved either in the deceased’s care or the payment of care. Providers may disclose only PHI that is relevant to the family member, relative, or friend’s involvement in the deceased’s care. PHI cannot be disclosed if the deceased person expressed a prior preference for it not to be disclosed.

Patient rights to limit disclosures. Under the Omnibus Rule, your organization must comply with a patient’s request that PHI regarding a specific health care item or service not be disclosed to a health plan for purposes of payment or health care operations if the patient paid out-of-pocket, in full, for that item or service.

Providing electronic copies of medical records.  Providers must comply with a patient’s request for an electronic copy of his or her PHI if the records are maintained in an electronic format and are readily producible in the requested format.

Changes The Breach Notification Standards.   

The Omnibus Rule changed the standard for determining whether a breach of unsecured PHI has occurred, and what steps the provider must follow.  In essence, your internal policies must reflect how you will respond to a potential breach and must be spelled out more completely and the requirements are now tighter. Once the new standards are reflected into your policies, you should no longer use your previous breach standard, even for breaches that occured prior to the Omnibus Rule’s compliance deadline.

Marketing and sale of PHI.

Under the Omnibus Rule, the marketing or sale of products based upon patient PHI is generally prohibited. Generally these prohibitions don’t apply if your organization has received valid authorization from the patient.  Organizations must also ensure that any definitions of “marketing” and “sale of PHI” in their policies complies with the revised definitions and standards under the Omnibus Rule.

HHS has posted on its website the audit protocol derived from the recently completed audit pilot program. The audit protocol provides a helpful list of the items that an auditor will review when assessing whether a covered entity is in compliance with HIPAA.

After the policies are finalized, your organization should formally adopt and approve the policies in accordance with any procedural requirements in your governing documents or standard operating procedures.

Staff Training Requirements.

Any time your organization updates its privacy policies, workforce members should receive training on any new and revised policies. In particular, management and higher-level employees should be fully trained on the new breach standards.

Training is important component of compliance with HIPAA and the HITECH Act. Security training should be documented and maintained in your event training logs. Program details may be requested during an audit or investigation.

Changes to Notice of Privacy Practices.

The Omnibus Rule modifies and expands the content of the notice of privacy practices (NPP) that a provider is required to maintain and distribute to its patients.   A covered entity must:
  • Make their NPP available to patients who request a copy on or after the effective date of any revisions.
  • Must post the revised notice on its website, if applicable.
  • Must post the notice in a prominent location on its premises.
  • New patients who receive services for the first time after modification of an NPP should be provided with a copy of the revised NPP.

Also remember that covered entities should always retain copies of previous versions of their NPPs and of any written acknowledgements by patients of receipt of NPPs.

Changes to Business Associate Agreements.

There have been changes to the Business Associate Agreement (BAA) document requirements.  Omnibus has changed the definition of a “Business Associate” and now includes subcontractors of business associates that deal with PHI.  Covered entities are not required to enter into BAAs with downstream subcontractors. Rather, the business associate who contracts with the subcontractor must enter into a BAA with the subcontractor and you should require proof of compliance.

Are you unsure of your status on HIPAA Compliance?  Contact ACT for a FREE consultation and review of your readiness at (847) 639-7000 or by e-mail at support@act4networks.com
Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Posted in | No comments
Newer Post Older Post Home

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts

  • Ransomeware Now #1 MalwareThreat - Learn More Here
    I just read an outstanding white paper from a couple of researchers at Sophos Security outlining how Ransomware is passing up FakeAlert malw...
  • Computer Support Rates - When Cheap Really Isn't
    What's in a labor rate?  Why are some IT companies more expensive than others?  Our company is neither the most expensive in our market ...
  • Server Configuration - Heaven Save Us From Well-Meaning Amateurs!
    How do I tell the client what their old tech did to them?  They've got to spend a bunch of money to correct the mess he made and I'm...
  • When It's Time To Fire A Customer
    What?  Isn't that backwards?  Isn't it the customer that usually does the firing? Usually, as business people, we work so hard to fi...
  • Using Personal Computers In the Workplace
    At ACT, we support a great many organizations that allow employees to use their own computers at work.  Sadly, I've noticed that some of...
  • What to do with Windows XP
    Well, it had a good long run.  Windows XP is now 13 years old.  In less than 10 months Microsoft is pulling the plug on our old friend XP.  ...
  • Wireless Networking Is Due For A Big Jump In Performance
    Just when we were getting comfortable with the 802.11n wireless standard, here comes a newer and better wireless solution - 802.11ac.  It wi...
  • Documentation - The Key To Client Support Success
    Recently, we won the trust of a new client that was unhappy with the service provided by their previous IT company.  After the client notifi...
  • Going to the Cloud is easy, getting out is a lot tougher!
    Everyone is pushing you to take your business to the cloud, right?  It's easy, right?  The sales rep used all the right words in his pit...
  • Support for Windows XP and Office 2003 stops on April 8th.
    All Microsoft support for Windows XP and Office 2003 stops on April 8th. What are the risks to your business if you don't upgrade? Let...

Blog Archive

  • ▼  2013 (39)
    • ►  November (3)
    • ►  October (4)
    • ►  September (2)
    • ▼  August (4)
      • When It's Time To Fire A Customer
      • Using the Cloud? Have you got a backup Internet c...
      • HIPAA Omnibus Rule Compliance Deadline is Near. A...
      • Computer Support Rates - When Cheap Really Isn't
    • ►  July (3)
    • ►  June (9)
    • ►  May (3)
    • ►  April (3)
    • ►  March (6)
    • ►  January (2)
  • ►  2012 (12)
    • ►  December (2)
    • ►  November (8)
    • ►  October (2)
Powered by Blogger.

About Me

Unknown
View my complete profile