Identification of Individual Sample Clauses

Identification of Individual. Data User may not use the Limited Data Set to identify or contact any individual who is the subject of the PHI from which the Limited Data Set was created.
Sample 1Sample 2Sample 3See All (14)
AutoNDA by SimpleDocs
Identification of Individual. Data User may not use the Limited Data Set to identify or contact any individual who is the subject of the PHI from which the Limited Data Set was created. Disclosures Required By Law. Data User shall not, without the prior written consent of Covered Entity, disclose the Limited Data Set on the basis that such disclosure is required by law without notifying Covered Entity so that Covered Entity shall have an opportunity to object to the disclosure and to seek appropriate relief. If Covered Entity objects to such disclosure, Data User shall refrain from disclosing the Limited Data Set until Covered Entity has exhausted all alternatives for relief.
Sample 1Sample 2Sample 3See All (4)
Identification of Individual. Recipient may not use the Data to identify or contact any individual involved in the Data. Reporting: Recipient shall report to Provider within twenty-four (24) hours of Recipient becoming aware of any use or disclosure of the Data in violation of this Agreement or applicable law.
Sample 1Sample 2Sample 3
Identification of Individual. Data user may not use the Limited Data Set to identify or contact any individual who is the subject of the PHI from which the Limited Data Set was created. Disclosures Required By Law. Data User shall not, without the prior written consent of Covered Entity, disclose the Limited Data Set on the basis that such disclosure is 2 The parties should specify the protected health information that will be included in the Limited Data Set. 3 See 45 C.F.R. § 164.514(e). Exhibit A should specify the research activities, public health activities, or health care operations for which Data User may use the Limited Data Set. Alternatively, the Agreement may reference the description of activities set forth in an underlying agreement. In either case this Agreement may not authorize Data User to use or further disclose the information in a manner that would violate the requirements of HIPAA and the HIPAA Regulations if done by Covered Entity. 45 C.F.R. § 164.514(e)(4)(ii)(A). 4 Covered Entity and Data User should specify the individuals who are permitted to use or disclose the Limited Data Set under the Agreement. 45 C.F.R. § 164.514(e)(4)(ii)(B). required by law without notifying Covered Entity o that Covered Entity shall have an opportunity to object to the disclosure and to seek appropriate relief. If Covered Entity objects to such disclosure, Data User shall refrain from disclosing the Limited Data Set until Covered Entity has exhausted all alternatives for relief.
Sample 1

Related to Identification of Individual

  • Identification When performing work on District property, Contractor shall be in appropriate work attire (or uniform, if applicable) at all times. If Contractor does not have a specific uniform, then Contractor shall provide identification tags and/or any other mechanism the District in its sole discretion determines is required to easily identify Contractor. Contractor and its employees shall (i) display on their clothes the above-mentioned identifying information and (ii) carry photo identification and present it to any District personnel upon request. If Contractor cannot produce such identification or if the identification is unacceptable to District, District may provide at its sole discretion, District-produced identification tags to Contractor, costs to be borne by Contractor.

  • 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.

  • Identification Cards Identification (“ID”) cards are issued by Us for identification purposes only. Possession of any ID card confers no right to services or benefits under this Contract. To be entitled to such services or benefits, Your Premiums must be paid in full at the time that the services are sought to be received.

  • Personal Identification Number We will issue you a Personal Identification Number (PIN) for use with your Card at VISA NET automatic teller machines (ATM’s). These numbers are issued to you for your security purposes. These numbers are confidential and should not e disclosed to third parties. You are responsible for safekeeping your PIN. You agree not to disclose or otherwise make available your PIN to anyone not authorized to sign on your Accounts. To keep your Account secure, please do not write your PIN on your Card or keep it in the same place as your Card.

  • Type and Jurisdiction of Organization, Organizational and Identification Numbers The type of entity of such Grantor, its state of organization, the organizational number issued to it by its state of organization and its federal employer identification number are set forth on Exhibit A.

  • 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.

  • Tax Identification Number All deposits to the Accounts shall be subject to the Escrow Agent's receipt of a valid tax identification number for the Company, Manager or Potential Investor, as applicable.

  • Identification of Goods Identification of the goods shall not be deemed to have been made until both Buyer and Seller have agreed that the goods in question are to be appropriate to the performance of this Agreement.

  • 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.

  • Notification of Incidents If Contractor becomes aware of or has reasonable suspicion of a privacy incident or security incident regarding any State data, Contractor must report such incident to the State and the State Chief Information Security Officer as soon as possible, but no later than twenty-four (24) hours after such incident. The decision to notify the affected data subjects and the form of such notice following report of a privacy incident or security incident are the responsibility of the State. Notwithstanding anything to the contrary in this Contract, Contractor will indemnify, hold harmless and defend the State and its officers, and employees for and against any claims, damages, costs and expenses related to any privacy incident or security incident involving any State data. For purposes of clarification, the foregoing sentence shall in no way limit or diminish Contractor’s obligation(s) to indemnify, save, hold harmless, or defend the State under any other term of this Contract. Contractor will reasonably mitigate any harmful effects resulting from any privacy incident or security incident involving any State data.

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