De-Identification of Information/Creation of Limited Data Set Sample Clauses

De-Identification of Information/Creation of Limited Data Set. Broker shall not De-Identify Health Information it creates or receives for or from the Company, and shall not use or disclose such de-identified information, unless such de-identification is expressly permitted under the terms and conditions of this Agreement for services to be provided by Broker to the Company related to the Company’s activities for purposes of “treatment,” “payment” or “health care operations,” as those terms are defined under the HIPAA Privacy Regulations. Broker further agrees that it will not create a Limited Data Set using Health Information it creates or receives for or from the Company, nor use or disclose such Limited Data Set unless: (i) such creation, use or disclosure is expressly permitted under the terms and conditions of this Agreement; and (ii) such creation, use or disclosure is for services provided by Broker that relate to the Company’s activities for purposes of “payment” or “health care operations”, as those terms are defined under the HIPAA Privacy Regulations.
AutoNDA by SimpleDocs
De-Identification of Information/Creation of Limited Data Set. Broker shall not De-Identify Health Information it creates or receives for or from the Company, and shall not use or disclose such de-identified information, unless such de- identification is expressly permitted under the terms and conditions of this Agreement for services to be provided by Broker to the Company related to the Company’s activities for purposes of “treatment,” “payment” or “health care operations,” as those terms are defined under the HIPAA Privacy Regulations. Xxxxxx further agrees that it will not create a Limited Data Set using Health Information it creates or receives for or from the Company, nor use or disclose such Limited Data Set unless: (i) such creation, use or disclosure is expressly permitted under the terms and conditions of this Agreement; and
De-Identification of Information/Creation of Limited Data Set. Business Associate agrees neither to de-identify PHI it creates or receives for or from Company or from another business associate of Company, nor use or disclose such de-identified PHI, unless such de-identification is expressly permitted under the terms and conditions of the Agreement for services to be provided by Business Associate to Company related to Company’s activities for purposes of “treatment”, “payment” or “health care operations”, as those terms are defined under the HIPAA Privacy Rule. De-identification of PHI, other than as expressly permitted under the terms and conditions of the Agreement for Business Associate to perform services for Company, is not a permitted use of PHI under this Addendum. Business Associate further agrees that it will not create a “limited data set” as defined by the HIPAA Privacy Rule using PHI it creates or receives, or receives from another business associate of Company, nor use or disclose such limited data set unless: (i) such creation, use or disclosure is expressly permitted under the terms and conditions of the Agreement; and (ii) such creation, use or disclosure is for services provided by Business Associate that relate to Company’s activities for purposes of “payment” or “health care operations,” as those terms are defined under the HIPAA Privacy Rule.

Related to De-Identification of Information/Creation of Limited Data Set

  • Designation of Information Xxxxx shall clearly identify any portions of its submissions that it believes are trade secrets, or information that is commercial or financial and privileged or confidential, and therefore potentially exempt from disclosure under the Freedom of Information Act (FOIA), 5 U.S.C. § 552. Xxxxx shall refrain from identifying any information as exempt from disclosure if that information does not meet the criteria for exemption from disclosure under FOIA.

  • Identification of Data a. All Background, Third Party Proprietary and Controlled Government Data provided by Disclosing Party shall be identified in the Annex under which it will be provided. b. NASA software and related Data provided to Partner shall be identified in the Annex under which it will be used. Notwithstanding H.4., Software and related Data will be provided to Partner under a separate Software Usage Agreement (SUA). Partner shall use and protect the related Data in accordance with this Article. Unless the SUA authorizes retention, or Partner enters into a license under 37 C.F.R. Part 404, the related Data shall be disposed of as instructed by NASA.

  • Identification and Disclosure of Privacy and Security Offices Business Associate and Subcontractors shall provide, within ten (10) days of the execution of this agreement, written notice to the Covered Entity’s contract/grant manager the names and contact information of both the HIPAA Privacy Officer and HIPAA Security Officer. This information must be updated any time either of these contacts changes.

  • Non-Identification Approved Users agree not to use the requested datasets, either alone or in concert with any other information, to identify or contact individual participants from whom data and/or samples were collected. Approved Users also agree not to generate information (e.g., facial images or comparable representations) that could allow the identities of research participants to be readily ascertained. These provisions do not apply to research investigators operating with specific IRB approval, pursuant to 45 CFR 46, to contact individuals within datasets or to obtain and use identifying information under an 2 The project anniversary date can be found in “My Projects” after logging in to the dbGaP authorized-access portal. IRB-approved research protocol. All investigators including any Approved User conducting “human subjects research” within the scope of 45 CFR 46 must comply with the requirements contained therein.

  • Preservation of Information; Communications to Holders The Trustee shall preserve, in as current a form as is reasonably practicable, the names and addresses of Holders contained in the most recent list furnished to the Trustee as provided in Section 701 and the names and addresses of Holders received by the Trustee in its capacity as Security Registrar. The Trustee may destroy any list furnished to it as provided in Section 701 upon receipt of a new list so furnished. The rights of Holders to communicate with other Holders with respect to their rights under this Indenture or under the Securities, and the corresponding rights and privileges of the Trustee, shall be as provided by the Trust Indenture Act. Every Holder of Securities, by receiving and holding the same, agrees with the Company and the Trustee that neither the Company nor the Trustee nor any agent of either of them shall be held accountable by reason of any disclosure of information as to names and addresses of Holders made pursuant to the Trust Indenture Act.

  • Accessibility of Information Technology Contractor represents and warrants that any software/ hardware/ communications system/ equipment (collectively “technology”), if any, provided under this Agreement adheres to the standards and/or specifications as may be set forth in the Section 508 of the Rehabilitation Act of 1973 standards guide and is fully compliant with WCAG 2.0 AA standards for accessibility and compliant with any applicable FCC regulations. Technology that will be used on a mobile device must also be navigable with Voiceover on iOS devices in addition to meeting WCAG 2.0 level AA. If portions of the technology or user experience are alleged to be non-compliant or non- accessible at any point, District will provide Contractor with notice of such allegation and Contractor shall use its best efforts to make the technology compliant and accessible. If a state or federal department, office or regulatory agency, or if any other third party administrative agency or organization (“Claimants”), make a claim, allegation, initiates legal or regulatory process, or if a court finds or otherwise determines that technology is non-compliant or non-accessible, Contractor shall indemnify, defend and hold harmless the District from and against any and all such claims, allegations, liabilities, damages, penalties, fees, costs (including but not limited to reasonable attorneys’ fees), arising out of or related to Xxxxxxxxx’ claims. Contractor shall also fully indemnify District for the full cost of any user accommodation that is found to be necessary due to an identifiable lack of accessibility in the Contractor’s technology. If necessary, an independent 3rd party accessibility firm using POUR standards (Perceivable, Operable, Understandable and Robust) may be used to validate the accessibility of the technology.

  • Additional Submissions – Information Access The claimant shall then have the opportunity to submit written comments, documents, records and other information relating to the claim. The Plan Administrator shall also provide the claimant, upon request and free of charge, reasonable access to, and copies of, all documents, records and other information relevant (as defined in applicable ERISA regulations) to the claimant’s claim for benefits.

  • Partnership Formation and Identification 6 2.1 Formation............................................................................................ 6 2.2 Name, Office and Registered Agent.................................................................... 6 2.3 Partners............................................................................................. 6 2.4

  • Freedom of Information and Protection of Privacy Act Any information provided on this contract may be subject to release under the Freedom of Information and Protection of Privacy Act. The Contractor may be consulted prior to release of any information.

  • Sharing of Information Seller shall allow Buyer to exchange information related to Seller and the Transactions hereunder with third party lenders and Seller shall permit each third party lender to share such information with Buyer.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!