Business Associate Agreement
All applicable ReputationStacker Professional plan and Premium plan subscribers are considered "Covered Entities" (as defined below) under this BAA (Business Associate Agreement).
These Standard HIPAA Business Associate Agreement Terms and Conditions (“HIPAA Addendum”) shall be incorporated into the Master Service Agreement for Clients that are Covered Entities (as defined below) and that provide Protected Health Information (“PHI” as defined below) to ReputationStacker in connection with ReputationStacker services that they have purchased.
These terms supplement the purchase agreement between ReputationStacker and Clients (“Underlying Agreement”) in order to comply with the federal Standards for Privacy of Individually Identifiable Health Information, located at 45 C.F.R. Part 160 and Part 164, Subparts A through E (“Privacy Rule”) and the Health Information Technology for Economic and Clinical Health Act, Public Law 111-005 (the “HITECH Act”).
1. DEFINITIONS
Terms used, but not otherwise defined, in this HIPAA Addendum shall have the same meaning as those terms in the Privacy Rule or the HITECH Act.
a) “Breach” shall have the same meaning given to such term under 42 U.S.0 § 17921.
b) “Business Associate” shall generally have the same meaning as the term “business associate” at 45 CFR 160.103, and in reference to the Client that is party to this agreement, shall mean ReputationStacker.
c) “Covered Entity” shall generally have the same meaning as the term “covered entity” at 45 CFR 160.103, and in reference to the Client that is party to this agreement, shall mean Client.
d) “HIPAA Rules” shall mean the Privacy, Security, Breach Notification, and Enforcement Rules at 45 CFR Part 160 and Part 164.
e) “Individual” shall have the same meaning as the term “individual” in 45 C.F.R. §160.103 and shall include a person who qualifies as a personal representative in accordance with 45 C.F.R. § 164.502(g).
f) “Protected Health Information” or “PHI” shall have the same meaning as the term “protected health information” in 45 C.F.R. § 160.103, limited to the information created or received by Business Associate from or on behalf of Covered Entity.
g) “Required by Law” shall have the same meaning as the term “required by law” in 45 C.F.R. §160.103.
h) “Unsecured PHI” shall have the same meaning given to such term under the HITECH Act and any guidance issued pursuant to this act.
2. Obligations and Activities of Business Associate
2.1 Use and Disclosure of PHI. ReputationStacker shall not use or disclose PHI other than as permitted or required by this HIPAA Addendum or as Required by Law. ReputationStacker shall not use or disclose PHI for fundraising or marketing purposes. ReputationStacker shall not directly or indirectly receive remuneration in exchange for PHI, except with the prior written consent of Covered Entity and as permitted by the HITECH Act; however, this prohibition shall not affect payment by Covered Entity to ReputationStacker for services provided pursuant to the Underlying Agreement.
2.2 Safeguards. ReputationStacker shall use appropriate safeguards, and comply with Subpart C of 45 CFR Part 164 with respect to electronic PHI, to prevent use or disclosure of PHI other than as provided for by the Underlying Agreement.
2.3 Mitigation. ReputationStacker shall mitigate, to the extent practicable, any harmful effect that is known to ReputationStacker of a use or disclosure of PHI by ReputationStacker in violation of the requirements of this HIPAA Addendum.
2.4 Reporting. ReputationStacker shall notify in writing Covered Entity of any access, use or disclosure of PHI for a purpose that is not provided for in this HIPAA Addendum or the Underlying Agreement, and any Breach of Unsecured PHI, of which ReputationStacker becomes aware without unreasonable delay and in no case later than thirty (30) calendar days after discovery.
2.5 Disclosure to Agents and Subcontractors. In accordance with 45 CFR 164.502(e)(1)(ii) and 164.308(b)(2), if applicable, ReputationStacker shall ensure that any subcontractors that create, receive, maintain, or transmit PHI on behalf of ReputationStacker agree to the same restrictions, conditions, and requirements that apply to the ReputationStacker with respect to such information.
2.6 Designated Record Set. ReputationStacker shall provide access, at the request of Covered Entity, to PHI in a Designated Record Set in order to meet the requirements under 45 C.F.R. § 164.524.
2.7 Internal Practices, Policies and Procedures. ReputationStacker shall make available its internal practices, books, and records, including policies and procedures and Covered Entities’ PHI, relating to the use and disclosure of PHI received from, or created or received by ReputationStacker on behalf of, Covered Entity to the Covered Entity and to the Secretary of Health and Human Services (“Secretary”) for purposes of the Secretary determining Covered Entity’s compliance with the Privacy Rule and the HITECH Act.
2.8 Accounting for Disclosures. ReputationStacker agrees to maintain the information required to provide an accounting of disclosures of PHI in accordance with 45 C.F.R. § 164.528 and to make this information available to Covered Entity upon Covered Entity’s request in order to allow Covered Entity to respond to an Individual’s request for accounting of disclosures.
2.9 Security Obligations. ReputationStacker shall implement appropriate safeguards as are necessary to prevent the use or disclosure of PHI otherwise than as permitted by the Underlying Agreement or this HIPAA Addendum including, but not limited to, administrative, physical, and technical safeguards that reasonably and appropriately protect the confidentiality, integrity, and availability of Covered Entity’s electronic PHI as required by 45 C.F.R. Sections 164.308, 164.310, and 164.312, as amended from time to time. ReputationStacker shall ensure that any agent, including a subcontractor, to whom it provides such electronic PHI, agrees to implement reasonable and appropriate safeguards to protect it. ReputationStacker shall comply with the policies and procedures and document requirements of the Privacy Rule including, but not limited to, 45 C.F.R. Section 164.316. ReputationStacker agrees to report promptly to Covered Entity any identified security incident for which it has the responsibility to respond and/or has the potential to adversely affect the Client’s PHI.
2.10 Breach Pattern or Practice by Covered Entity. If ReputationStacker knows of a pattern of activity or practice of Covered Entity that constitutes a material breach or violation of Covered Entity’s obligations under the HIPAA Addendum, ReputationStacker must take reasonable steps to cause Covered Entity to cure the breach or end the violation. If the steps are unsuccessful, ReputationStacker must terminate the Underlying Agreement, if feasible, or if termination is not feasible, report the problem to the Secretary.
3. Permitted Uses and Disclosures by ReputationStacker
3.1 Permitted Uses and Disclosures. Except as otherwise limited in this HIPAA Addendum, ReputationStacker may use or disclose PHI to perform functions, activities, or services for, or on behalf of, Covered Entity as specified in the Underlying Agreement provided such use or disclosure would not violate the Privacy Rule including, but not limited to, each applicable requirement of 45 C.F.R. § 164.504(e) and the HITECH Act if done by the Covered Entity.
3.2 Use for Management and Administration. Except as otherwise limited in this HIPAA Addendum, ReputationStacker may use PHI for the proper management and administration of ReputationStacker or to carry out the legal responsibilities of the ReputationStacker.
3.3 Disclosure for Management and Administration. Except as otherwise limited in this HIPAA Addendum, ReputationStacker may disclose PHI for the proper management and administration of ReputationStacker, provided that disclosures are Required by Law, or that ReputationStacker obtains reasonable assurances from the person to whom the information is disclosed that it will remain confidential and used or further disclosed only as Required by Law or for the purpose for which it was disclosed to the person, and the person notifies the ReputationStacker of any instances of which it is aware in which the confidentiality of the information has been breached.
3.4 Minimum Necessary. ReputationStacker (and its agents or subcontractors) shall request, use, and disclose only the minimum amount of PHI necessary to accomplish the purpose of the request, use, or disclosure. ReputationStacker understands and agrees that the definition of “minimum necessary” is subject to change from time to time and shall keep itself informed of guidance issued by the Secretary with respect to what constitutes “minimum necessary.”
3.5 Data Aggregation. Except as otherwise limited in this HIPAA Addendum, ReputationStacker may use PHI to provide Data Aggregation services to Covered Entity as permitted by 45 C.F.R. §164.504(e)(2)(i)(B).
3.6 Report Violations of Law. ReputationStacker may use PHI to report violations of law to appropriate Federal and State authorities consistent with 45 C.F.R. §164.502(j)(1).
4. Obligations of Covered Entity
4.1 Notice of Privacy Practices. Covered Entity shall notify ReputationStacker of any limitation(s) in the notice of privacy practices of the Covered Entity under 45 C.F.R. § 164.520, to the extent that such limitations may affect ReputationStacker’s use or disclosure of PHI.
4.2 Changes in Permission. Covered Entity shall notify ReputationStacker of any changes in, or revocation of, permission by an Individual to use or disclose PHI, to the extent that such changes may affect ReputationStacker’s use or disclosure of PHI.
4.3 Notification of Restrictions. Covered Entity shall notify ReputationStacker of any restriction to the use or disclosure of PHI that Covered Entity has agreed to in accordance with 45 C.F.R. § 164.522, to the extent that such restriction may affect ReputationStacker’s use or disclosure of PHI.
4.4 Permissible Requests by Covered Entity. Covered Entity shall not request ReputationStacker to use or disclose PHI in any manner that would not be permissible under the Privacy Rule and the HITECH Act if done by Covered Entity.
5. Term and Termination
5.1 Term. The Term of this HIPAA Addendum shall be effective as of the first day that Covered Entity provides PHI to ReputationStacker and shall terminate when all of the PHI provided by Covered Entity to ReputationStacker, or created or received by ReputationStacker on behalf of Covered Entity, is destroyed or returned to Covered Entity, or, if it is infeasible to return or destroy PHI, protections are extended to such information, in accordance with the termination provisions in this Section.
5.2 Termination for Cause. Upon Covered Entity’s knowledge of a material breach by ReputationStacker, Covered Entity shall either:
(a) Provide 60 days advance written notice specifying the nature of the breach or violation to ReputationStacker. ReputationStacker shall have 60 days from the date of the notice in which to remedy the breach or violation. If such corrective action is not taken within the time specified, this HIPAA Addendum and the Underlying Agreement shall terminate at the end of the 60 day period without further notice or demand;
(b) Immediately terminate this HIPAA Addendum and the Underlying Agreement if ReputationStacker has breached a material term of this HIPAA Addendum and cure is not possible; or
(c) Report the violation to the Secretary if neither cure of the breach nor termination of this HIPAA Addendum and the Underlying Agreement are feasible.
5.3 Effect of Termination.
(a) Upon termination of this HIPAA Addendum or the Underlying Agreement, for any reason, ReputationStacker shall return or destroy all PHI received from Covered Entity, or created, maintained or received by ReputationStacker on behalf of Covered Entity. This provision shall apply to PHI that is in the possession of subcontractors or agents of ReputationStacker. ReputationStacker shall retain no copies of the PHI.
(b) In the event that ReputationStacker determines that returning or destroying PHI is not feasible, ReputationStacker shall notify Covered Entity in writing of the conditions that make return or destruction infeasible. If return or destruction of the PHI is infeasible, ReputationStacker shall extend the protections of this HIPAA Addendum to such PHI and limit further uses and disclosures of such PHI to those purposes that make the return or destruction infeasible, for so long as ReputationStacker maintains such PHI.
6. Miscellaneous In Addition to Terms and Conditions
6.1 Regulatory References. A reference in this HIPAA Addendum to a section in the Privacy Rule or the HITECH Act means the section as in effect or as amended.
6.2 No Third Party Beneficiaries. Nothing in this HIPAA Addendum shall be considered or construed as conferring any right or benefit on a person not party to this HIPAA Addendum nor imposing any obligations on either Party hereto to persons not a party to this HIPAA Addendum.
6.3 Amendments. ReputationStacker reserves the right to change the terms and conditions of this HIPAA Addendum at any time. ReputationStacker will notify Covered Entity of any material changes to this HIPAA Addendum by sending Covered Entity an email to the last e-mail address Covered Entity provided to ReputationStacker or by prominently posting notice of the changes on ReputationStacker’s website. Any material changes to this HIPAA Addendum will be effective upon the earlier of thirty (30) calendar days following ReputationStacker’s transmission of an email notice to Covered Entity or thirty (30) calendar days following ReputationStacker’s posting of notice of the changes on its website. These changes will be effective immediately for new ReputationStacker Clients. Please note that at all times Covered Entity is responsible for providing ReputationStacker with its most current email address. In the event that the last e-mail address that Covered Entity has provided ReputationStacker is not valid, or for any reason is not capable of delivering to Covered Entity the notice described above, ReputationStacker’s transmission of the e-mail containing such notice will nonetheless constitute effective notice of the changes described in the notice. If Covered Entity does not agree with the changes to this HIPAA Addendum, Covered Entity must notify ReputationStacker prior to the effective date of the changes that Covered Entity wishes to terminate its subscription to the applicable ReputationStacker services. Continued use of the ReputationStacker services, following notice of such changes, shall indicate Covered Entity’s acknowledgement of such changes and agreement to be bound by the terms and conditions of such changes.
6.4 Interpretation. The provisions of this HIPAA Addendum shall prevail over the provisions of any other agreement that exists between the Parties that may conflict with, or appear inconsistent with, any provision of this HIPAA Addendum, the Privacy Rule or the HITECH Act.
