Unique Identifiers Clause Samples
The Unique Identifiers clause establishes a requirement for assigning distinct codes, numbers, or other markers to specific items, transactions, or parties referenced in the agreement. In practice, this means that each product, document, or participant is given a unique identifier, such as a serial number or registration code, to distinguish it from others. This clause ensures accurate tracking, reduces confusion, and helps prevent errors or disputes by making it clear exactly which items or entities are being referred to throughout the contract.
Unique Identifiers. 2.13.1 For the purposes of this Clause [2.13], Unique Identifiers comprise:
Unique Identifiers. For Contracts where trading electronically with the MOD is required, insert the following wording as a new Clause 2.13 in the Contract:
Unique Identifiers. The MPS shall include a unique identifying number for each task. This will more easily allow DigitalGlobe to combine certain tasks into a DigitalGlobe Master Schedule. Unique identifiers will not be deleted, reused, or re-assigned to other tasks.
Unique Identifiers. 4.1. The Pharmacy Council assigns pharmacists unique identifiers for the Health Provider Index (HPI), the national database administered by the Ministry of Health. The principal purpose of the HPI is to uniquely identify health practitioners and to hold that information in a central, national database. The HPI will be used under this MOU for the purpose of
Unique Identifiers. We collect and use unique identifiers, such as IP addresses, as necessary to operate our Site, or Services, including to maintain or analyze their functioning; perform network communications; authenticate users or personalize content; and protect the security or integrity of users and our Site, and Services. Aggregate or De-Identified Information. We may use aggregate or de-identified information about children for research, analysis, marketing, and similar purposes. When we do so, we strip out names, contact information, and other personal identifiers.
Unique Identifiers. Having regard to and subject to Clause 20 (Payment under CP&F), the Authority and the Contractor shall comply with the provisions of this Clause 22 (Unique Identifiers). For CP&F purchase orders, the Contract or an order issued under a framework agreement will reference UOIs or URRIs, or both. The application of UOIs and URRIs is at the line item level. The Contractor must quote the applicable Unique Identifier in any communication concerning a line item. For EBC contractor logistic support contracts, the Contractor will generate EUPIs in fulfilling demands raised under a contractor logistic support contract. An EUPI applies for each package and the Contractor must quote it in any communication concerning a package. Where a delivery includes more than one package, each package must have a separate EUPI. Confirmation of a receipt of deliveries by Unique Identifiers shall not be construed as an acceptance of the Articles for the purposes of Clause 58 (Delivery, Acceptance, Rejection and transfer of Title and Risk) or any other term of this Contract relating to acceptance by the Authority.
Unique Identifiers. If a payment transaction is executed according to the unique identifiers of the payee as specified in the “Agreement” then it is considered as executed correctly with regards to the payee. In case the Client fails to present the said unique identifiers there is a possibility the execution of the payment order not to be possible and/or further expenses may arise as per the Bank’s “Tariff for Core Banking Business”. If the unique identifiers presented by the Client are wrong or insufficient, the Bank bears no liability for the non-execution or incorrect execution of the payment transaction. The Bank, if requested by the Client, shall make immediate efforts to recover the funds related to the payment transaction. In such case the Bank may proceed with charging reasonable expenses for the recovery of the funds, as per the “Tariff for Core Banking Business” of the Bank. If the Client presents additional information in relation to the payee of a payment transaction, further to the applicable unique identifiers of the payee set out by the Bank in the Agreement, the Bank shall be liable for the execution of the payment transaction only on the basis of the unique identifiers presented by the Client.
Unique Identifiers. The Digital Content may include unique identifiers that are specific to you or your purchase
Unique Identifiers. The LINK_ID and HOUSEHOLD_ID assigned by the Linkage Agent are included with each individual record in the Query Results. The DCC uses the LINK_ID and HOUSEHOLD_IDs to merge Query Results across Data Owners. After merging Query Result, the DCC prevents disclosure of the LINK_ID or the HOUSEHOLD_ID to the Data User by replacing the LINK_ID with a project-specific PROJECT_ID and replacing the HOUSEHOLD_ID with a project-specific PROJECT_HOUSHOLD_ID. CODI facilitates the creation of individual longitudinal records for Data Users by gathering Data from multiple Data Owners. Data Users are responsible for transforming multiple records for an individual into a single unified view. The methods used to reconcile Data between records may vary based on the question being answered. CODI recognizes that as a result of Record Linkage, the same individual may have conflicting birth dates, genders, or racial/ethnic groups which are time-invariant and recommends that Data Users deconflict these attributes in their Project Dataset prior to use. For Requests where the Data User seeks to receive De-identified Data from a Request, the DCC can de-identify Individual-Level Data or create an aggregate Data Product that is de-identified. A description of desired De-identified Data or of an aggregate Data Product that is de-identified must be defined within the Request process. In the event of a Request for a Data Product, the DCC will, in consultation with applicable Data Owners, evaluate the need for a project-specific Data Use Agreement on a case-by-case basis. DCC shall Use Query Results solely for the purposes set forth in this Agreement. Data Users shall only use Project Datasets for the purposes set forth in the submitted Request, the project-specific DUA, and the IRB protocol. Retention of Query Results and Project Datasets by the DCC and Data Users shall be as set forth in Section 6f (Retention) of the Agreement to which this Exhibit D is attached. For all Queries described here, DCC shall request the Minimum Necessary Data to fulfil the purpose of the Query and provide the Minimum Necessary Data to the Data User to fulfil the Request.
Unique Identifiers. The student ID number is being utilised as a third identifier. This is vital to ensure that the correct student is being matched. The other identifiers are the name, which comprises the first initial of the first name and the first four letters of the surname, and the date of birth.