Protocol Number Clause Samples

The Protocol Number clause assigns a unique identifier to a specific agreement, contract, or transaction. This number is typically referenced in all related documents, correspondence, and records to ensure consistency and traceability. By providing a standardized way to identify and track the agreement, the clause helps prevent confusion, misfiling, or disputes over which document is being referenced.
Protocol Number. IHLOSAPOC1Site: University of Western Australia_FINAL Equipment means the equipment supplied to the Institution by or on behalf of the Sponsor for the purposes of the Study, including that specified in Schedule 1.
View SourceView Similar (2)
Protocol Number. IFX-1-P2.5
View Source
Protocol Number. Lm-LLO-E7-07 (conducted in the United States) Protocol Title: A Randomized, Single Blind, Placebo Controlled Phase 2 Study to Assess the Safety and Efficacy of Lovaxin C for the Treatment of Cervical Intraepithelial Neoplasia Grade 2/3. Pursuant to the Master Agreement entered into by Advaxis, Inc. ("ADVAXIS") and Numoda Corporation ("Numoda") on June 19, 2009 ("MA"), this Project Agreement (PA) and attachments, including:
View Source
Protocol Number. 1321.7 Protocol Title: “Single dose, open label, uncontrolled, safety trial of intravenous administration of idarucizumab to paediatric patients enrolled from ongoing phase IIb/III clinical trials with dabigatran etexilate for the treatment and secondary prevention of venous thromboembolism“ as amended (hereinafter referred to as the “Trial Protocol”) both together hereinafter referred to as “Trial” The planned Trial start date is July 2017 (expected recruitment period: 12 months at least). The Trial shall be performed in different departments of University hospital Brno, ▇▇▇▇▇▇▇▇▇ ▇▇, ▇▇▇ ▇▇ ▇▇▇▇, ▇▇▇▇▇ ▇▇▇▇▇▇▇▇ (“Institution”) as the patients will be assigned to the relevant department depending on the individual diagnosis of each patient. (University hospital Brno, Department of Pediatric Hematology, Černopolní 9, 613 00 Brno) as Principal Investigator will be responsible for Trial run.
View Source

Related to Protocol Number

  • Data Universal Number System (DUNS) number Requirement Grantee will provide their valid DUNS number contemporaneous with execution of this Agreement.

  • Protocol The attached Protocol shall be an integral part of this Agreement.

  • Signaling protocol 4.1.3.1 SS7 Signaling is AT&T-21STATE’s preferred method for signaling. Where MF signaling is currently used, the Parties agree to use their best efforts to convert to SS7. If SS7 services are provided by AT&T-21STATE, they will be provided in accordance with the provisions of the applicable access tariffs. 4.1.3.2 Where MF signaling is currently used, the Parties agree to interconnect their networks using MF or dual tone MF (DTMF) signaling, subject to availability at the End Office Switch or Tandem Switch at which Interconnection occurs. The Parties acknowledge that the use of MF signaling may not be optimal. AT&T-21STATE will not be responsible for correcting any undesirable characteristics, service problems or performance problems that are associated with MF/SS7 inter-working or the signaling protocol required for Interconnection with CLEC employing MF signaling.

  • Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-▇▇▇▇▇-▇▇▇▇▇▇▇-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-▇▇▇▇▇-▇▇▇▇▇▇▇-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • Local Number Portability The Permanent Number Portability (PNP) database supplies routing numbers for calls involving numbers that have been ported from one local service provider to another. PNP is currently being worked in industry forums. The results of these forums will dictate the industry direction of PNP. BellSouth will provide access to the PNP database at rates, terms and conditions as set forth by BellSouth and in accordance with an effective FCC or Commission directive.