HIPAA. To the extent (if any) that DXC discloses “Protected Health Information” or “PHI” as defined in the HIPAA Privacy and Security Rules (45 CFR, Part 160-164) issued pursuant to the Health Insurance Portability and Accountability Act of 1996 (“HIPAA”) to Supplier or Supplier accesses, maintains, uses, or discloses PHI in connection with the performance of Services or functions under this Agreement, Supplier will: (a) not use or further disclose PHI other than as permitted or required by this Agreement or as required by law; (b) use appropriate safeguards to prevent use or disclosure of PHI other than as provided for by this Agreement, including implementing requirements of the HIPAA Security Rule with regard to electronic PHI; (c) report to DXC any use or disclosure of PHI not provided for under this Agreement of which Supplier becomes aware, including breaches of unsecured protected health information as required by 45 CFR §164.410, (d) in accordance with 45 CFR §164.502(e)(1)(ii), ensure that any subcontractors or agents of Supplier that create, receive, maintain, or transmit PHI created, received, maintained or transmitted by Supplier on DXC’s behalf, agree to the same restrictions and conditions that apply to Supplier with respect of such PHI; (e) make available PHI in a Designated Record Set (if any is maintained by Supplier) in accordance with 45 CFR section 164.524;
HIPAA. “HIPAA” means the Health Insurance Portability and Accountability Act of 1996 as in effect and/or as amended.
HIPAA. The Contractor agrees to comply with all applicable requirements of the Health Insurance Portability and Accountability Act of 1996, Title II, Administrative Simplification (“HIPAA”), including amendments signed into law under the American Recovery and Reinvestment Act of 2009 (“ARRA”), in particular, applicable provisions of Title XIII known as the Health Information Technology for Economic and Clinical Health Act (“HITECH”), Subtitle D, in all activities related to this Contract, to maintain compliance during the term of this Contract and after as may be required by federal law, to operate any systems used to fulfill the requirements of this Contract in full compliance with all applicable provisions of HIPAA and to take no action which adversely affects the State’s HIPAA compliance. Terms used, but not otherwise defined, in this Contract shall have the same meaning as those found in the HIPAA Regulations under 45 CFR Parts 160, 162, and 164. To the extent required by the provisions of HIPAA and regulations promulgated thereunder, the Contractor assures that it will appropriately safeguard all forms of Health Records and/or Protected Health Information (PHI), as defined by the regulations, which is made available to or obtained by the Contractor in the course of its work under this Contract. The Contractor agrees to comply with all applicable requirements of law relating to Health Records and/or PHI with respect to any task or other activity it performs for the State including, as required by the final Privacy and Security regulations:
HIPAA. Customer agrees that: (i) Oracle is not acting on Customer’s behalf as a Business Associate or subcontractor; (ii) the Cloud Service may not be used to store, maintain, process or transmit protected health information (“PHI”) and (iii) the Cloud Service will not be used in any manner that would require Oracle or the Cloud Service to be compliant with the Health Insurance Portability and Accountability Act of 1996, as amended and supplemented (“HIPAA”). In the preceding sentence, the terms “Business Associate,” “subcontractor,” “protected health information” or “PHI” shall have the meanings described in HIPAA.
HIPAA. The Contractor and its Consultants shall comply with the Authorized User's policies regarding compliance with the Health Insurance and Portability Act of 1996 (HIPAA).
HIPAA. The parties agree that:
HIPAA. (a) MCO must comply with applicable provisions of HIPAA. This includes, but is not limited to, the requirement that the MCO’s MIS system comply with applicable certificate of coverage and data specification and reporting requirements promulgated pursuant to HIPAA. MCO must comply with HIPAA EDI requirements.
HIPAA. The parties understand and agree that this Agreement may be subject to the Health Insurance Portability and Accountability Act of 1996 (HIPAA), the administrative regulations and/or guidance which have issued or may in the future be issued pursuant to HIPAA, including, but not limited to, the Department of Health and Human Services regulations on privacy and security, and Texas state laws pertaining to medical privacy (collectively, "Privacy Laws"). Vendor agrees to comply with all Privacy Laws that are applicable to this Agreement and to negotiate in good faith to execute any amendment to this Agreement that is required for the terms of this Agreement to comply with applicable Privacy Laws. In the event the parties are unable to agree on the terms of an amendment pursuant to this paragraph within thirty (30) days of the date the amendment request is delivered by a party to the other, this Agreement may be terminated by either party upon written notice to the other party.
HIPAA. If Client is a “covered entity” or a “business associate” thereof, as each term is used under the Health Insurance Portability and Accountability Act of 1996 (as may be amended or replaced, “HIPAA”) or is otherwise subject to any HIPAA-related or similar legal requirement, Client is solely responsible to ensure full compliance therewith. Client is responsible for maintaining the privacy of any persons or their information that may be covered by HIPAA or any related or similar legislation or regulation. Marketing 360® makes no claims or warranties regarding compliance with HIPAA.
HIPAA. HMO shall comply with applicable provisions of HIPAA. This includes, but is not limited to, the requirement that the HMO’s MIS system comply with applicable certificate of coverage and data specification and reporting requirements promulgated pursuant to HIPAA. HMO must comply with HIPAA EDI requirements.
