Permitted Uses and Disclosures of PHI 2.1 Unless otherwise limited herein, Business Associate may:
Permitted Uses and Disclosures of Phi by Business Associate Except as otherwise indicated in this Agreement, Business Associate may use or disclose PHI, inclusive of de-identified data derived from such PHI, only to perform functions, activities or services specified in this Agreement on behalf of DHCS, provided that such use or disclosure would not violate HIPAA or other applicable laws if done by DHCS.
Permitted Uses and Disclosures of Protected Health Information Business Associate:
Use and Disclosure Restrictions Neither party shall, without the written consent of the other, communicate confidential information of the other, designated in writing or identified in this Agreement as such, to any third party and shall protect such information from inadvertent disclosure to any third party in the same manner that the receiving party would protect its own confidential information. The foregoing obligations will not restrict either party from disclosing confidential information of the other party: (a) pursuant to applicable law; (b) pursuant to the order or requirement of a court, administrative agency, or other governmental body, on condition that the party required to make such a disclosure gives reasonable written notice to the other party to contest such order or requirement; and (c) on a confidential basis to its legal or financial advisors.
Permitted Uses and Disclosures i. Business Associate shall use and disclose PHI only to accomplish Business Associate’s obligations under the Contract.
Two-‐character labels All two-‐character ASCII labels shall be withheld from registration or allocated to Registry Operator at the second level within the TLD. Such labels may not be activated in the DNS, and may not be released for registration to any person or entity other than Registry Operator, provided that such two-‐character label strings may be released to the extent that Registry Operator reaches agreement with the related government and country-‐code manager of the string as specified in the ISO 3166-‐1 alpha-‐2 standard. The Registry Operator may also propose the release of these reservations based on its implementation of measures to avoid confusion with the corresponding country codes, subject to approval by ICANN. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD, all such labels that remain withheld from registration or allocated to Registry Operator shall be transferred as specified by ICANN. Registry Operator may self-‐allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement.
Uses and Disclosures Pursuant to the terms of this Agreement, Contractor may receive from the Exchange Protected Health Information and/or Personally Identifiable Information in connection with Contractor Exchange Functions that is protected under applicable Federal and State laws and regulations. Contractor shall not use or disclose such Protected Health Information or Personally Identifiable Information obtained in connection with Contractor Exchange Functions other than as is expressly permitted under the Exchange Requirements and only to the extent necessary to perform the functions called for within this Agreement.
Permitted Uses and Disclosures by Business Associate 1. Business Associate may only use or disclose protected health information as necessary to perform the services as outlined in the underlying agreement.
Archival Back-Up and Disaster Recovery Licensee may use and copy the Product and related Documentation in connection with: i) reproducing a reasonable number of copies of the Product for archival backup and disaster recovery procedures in the event of destruction or corruption of the Product or disasters or emergencies which require Licensee to restore backup(s) or to initiate disaster recovery procedures for its platform or operating systems; ii) reproducing a reasonable number of copies of the Product and related Documentation for cold site storage. “Cold Site” storage shall be defined as a restorable back-up copy of the Product not to be installed until and after the declaration by the Licensee of a disaster; iii) reproducing a back-up copy of the Product to run for a reasonable period of time in conjunction with a documented consolidation or transfer otherwise allowed herein. “Disaster Recovery” shall be defined as the installation and storage of Product in ready-to-execute, back-up computer systems prior to disaster or breakdown which is not used for active production or development.
Prohibited Uses and Disclosures BA shall not use or disclose PHI other than as permitted or required by the Contract and Addendum, or as required by law. BA shall not use or disclose Protected Information for fundraising or marketing purposes. BA shall not disclose Protected Information to a health plan for payment or health care operation purposes if the patient has requested this special restriction, and has paid out of pocket in full for the health care item or service to which the PHI solely relates [42 U.S.C. Section 17935(a) and 45 C.F.R. Section 164.522(a)(vi)]. BA shall not directly or indirectly receive remuneration in exchange for Protected Information, except with the prior written consent of CE and as permitted by the HITECH Act, 42 U.S.C. Section 17935(d)(2), and the HIPAA regulations, 45 C.F.R. Section 164.502(a)(5)(ii); however, this prohibition shall not affect payment by CE to BA for services provided pursuant to the Contract.
