De-Identified PHI Sample Clauses

De-Identified PHI. Upon the prior written approval of Participant, Business Associate may use Protected Health Information that has been de-identified in accordance with 45 CFR § 164.514 for its normal business operations.
AutoNDA by SimpleDocs
De-Identified PHI. PHI that has been de-identified within the meaning of 45 CFR § 164.514(b) is no longer PHI and may be used or disclosed by Business Associate for any lawful purpose.
De-Identified PHI. BENECARD PBF shall not sell, give or otherwise commercialize the use of any de-identified PHI. CLIENT grants BENECARD PBF permission, during and after the expiration or term of this Agreement, to use and/or transfer to third parties de-identified Protected Health Information collected, created or received by BENECARD PBF for research, profiling, and other business purposes required for the performance of its Services hereunder. BENECARD PBF shall retain full ownership rights over all resultant data.
De-Identified PHI. Business Associate agrees not to use data that identifies Xxxxxx or PHI for its own purposes or for the benefit of its other customers, including de-identified PHI, except as permitted by the Underlying Agreement, or otherwise as permitted by Xxxxxx’x prior written consent.
De-Identified PHI. Business Associate may de-identify any and all PHI created or received by Business Associate under this Agreement. PHI that has been de-identified within the meaning of 45 CFR § 164.514(b) is no longer PHI and may be used or disclosed by Business Associate for any lawful purpose.

Related to De-Identified PHI

  • If Identified If the HSP is Identified it will:

  • De-Identified Data Provider agrees not to attempt to re-identify de-identified Student Data. De-Identified Data may be used by the Provider for those purposes allowed under FERPA and the following purposes:

  • Customer Identification Program Notice To help the U.S. government fight the funding of terrorism and money laundering activities, U.S. Federal law requires each financial institution to obtain, verify, and record certain information that identifies each person who initially opens an account with that financial institution on or after October 1, 2003. Certain of PNC’s affiliates are financial institutions, and PNC may, as a matter of policy, request (or may have already requested) the Fund’s name, address and taxpayer identification number or other government-issued identification number, and, if such party is a natural person, that party’s date of birth. PNC may also ask (and may have already asked) for additional identifying information, and PNC may take steps (and may have already taken steps) to verify the authenticity and accuracy of these data elements.

  • Separate Identity The Seller shall, to the extent applicable to it, act in a manner that is consistent with the statements set forth in Exhibit 4.2(f).

  • Customer Identification Program (A) To assist the Fund in complying with requirements regarding a customer identification program in accordance with applicable regulations promulgated by U.S. Department of Treasury under Section 326 of the USA PATRIOT Act (“CIP Regulations”), BNYM will do the following:

  • Customer Identification Unless Elastic has first obtained Customer's prior written consent, Elastic shall not identify Customer as a user of the Products, on its website, through a press release issued by Elastic and in other promotional materials.

  • Customer Identification - USA Patriot Act Notice The Lender hereby notifies the Borrower that pursuant to the requirements of the USA Patriot Act (Title III of Pub. L. 107-56, signed into law October 26, 2001) (the “Act”), and the Lender’s policies and practices, the Lender is required to obtain, verify and record certain information and documentation that identifies the Borrower, which information includes the name and address of the Borrower and such other information that will allow the Lender to identify the Borrower in accordance with the Act.

  • De-identified Information De-identified Information may be used by the Operator only for the purposes of development, product improvement, to demonstrate or market product effectiveness, or research as any other member of the public or party would be able to use de-identified data pursuant to 34 CFR 99.31(b). Operator agrees not to attempt to re-identify De-identified Information and not to transfer De-identified Information to any party unless (a) that party agrees in writing not to attempt re- identification, and (b) prior written notice has been given to LEA who has provided prior written consent for such transfer. Operator shall not copy, reproduce or transmit any De-identified Information or other Data obtained under the Service Agreement except as necessary to fulfill the Service Agreement.

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

  • Vendor Identity and Contact Information It is Vendor’s sole responsibility to ensure that all identifying vendor information (name, EIN, d/b/a’s, etc.) and contact information is updated and current at all times within the TIPS eBid System and the TIPS Vendor Portal. It is Vendor’s sole responsibility to confirm that all e-correspondence issued from xxxx-xxx.xxx, xxxxxxx.xxx, and xxxxxxxxxxxxxxxx.xxx to Vendor’s contacts are received and are not blocked by firewall or other technology security. Failure to permit receipt of correspondence from these domains and failure to keep vendor identity and contact information current at all times during the life of the contract may cause loss of TIPS Sales, accumulating TIPS fees, missed rebid opportunities, lapse of TIPS Contract(s), and unnecessary collection or legal actions against Vendor. It is no defense to any of the foregoing or any breach of this Agreement that Vendor was not receiving TIPS’ electronic communications issued by TIPS to Vendor’s listed contacts.

Time is Money Join Law Insider Premium to draft better contracts faster.