Q&A: BA contract amendments, HITECH requirements, and indemnification clauses
HIM Connection, May 31, 2011
Want to receive articles like this one in your inbox? Subscribe to HIM Connection!
Q: A covered entity encounters difficulty when executing updated business associate contracts. Business associates are requesting amendments that exclude language pertaining to some HITECH requirements. The covered entity also has included an indemnification clause that not been popular with its business associates. Is this a common occurrence?
A: It is not uncommon. Business associates must comply with HITECH requirements that pertain to them regardless of whether the business associate contract includes them. Including an indemnification clause is relatively common and considered appropriate, but neither HIPAA nor HITECH requires it. If feasible, consider seeking services elsewhere if a business associate is unwilling to sign a contract that includes HITECH requirements or an indemnification clause.
Inform business associates that they must adhere to HITECH requirements regardless of whether their contract includes this language. Refer to 45 CFR 164.314(a)(1) and 45 CFR 164.502(e)(2).
A covered entity should also include language that allows it to amend a contract if necessary without business associate consent. This type of provision allows contract changes that become effective after a set period of time following business associate notification. Executing an addendum rather than a completely new contract is advisable when an existing contract already includes this language. Business associates may object, but they would be legally bound by the amended contract nonetheless.
Editor’s note: Chris Apgar, CISSP, president of Apgar & Associates, LLC, in Portland, OR, answered this question in the May issue of Briefings on HIPAA.
Want to receive articles like this one in your inbox? Subscribe to HIM Connection!
Related Products
Most Popular
- Articles
-
- Q/A: Volume requirement for reporting hydration services
- Featured blog post: Nurses face felony charges after reporting physician to the Texas Medical Board
- Catch up on what's new with injections and infusions
- Topic: CMS, OESS post new security compliance review information, checklist
- Capturing all necessary codes for IUD insertion and removal can be challenging
- HIPAA Q&A: Level of encryption needed for email
- What does case-mix index mean to you?
- QA:Coding multiple initial infusions
- News and briefs: Oklahoma Osteopathic Association against residency bill change
- OB services: Coding inside and outside of the package
- E-mailed
-
- Q/A: Volume requirement for reporting hydration services
- Featured blog post: Nurses face felony charges after reporting physician to the Texas Medical Board
- HIPAA Q&A: Level of encryption needed for email
- CMS has reformulated payments for some bilateral procedures
- Catch up on what's new with injections and infusions
- New conflicts of interest create new challenges
- Q&A: Follow CMS' coding guidelines when using modifier -25
- Q/A. One injection code or two?
- What does case-mix index mean to you?
- ED-to-inpatient transfers are flawed with safety gaps
- Searched
