Common Database Sample Clauses

Common Database. If deemed appropriate by the JDC, the Parties will establish a common database to be controlled, maintained and administered by BMS for the receipt, investigation, recordation, communication, and exchange (as between the Parties) of data arising from clinical trials for Products. The Parties shall agree upon guidelines and procedures for such common database that shall be in accordance with, and enable the Parties and their Affiliates to fulfill their reporting obligations under applicable law. Furthermore, such guidelines and procedures shall be consistent with relevant International Council for Harmonisation (“ICH”) guidelines. The Parties’ costs incurred in connection with receiving, investigating, recording, reviewing, communicating, and exchanging such efficacy data shall be included as an element of Development Costs or as Allowable Expenses, calculated on a FTE cost and direct out-of-pocket cost basis.
View SourceView Similar (6)
Common Database. If deemed appropriate by the JDC, BMS and EXEL will establish a common database to be controlled, maintained and administered by BMS for the receipt, investigation, recordation, communication, and exchange (as between BMS and EXEL) of data arising from clinical trials for Products. BMS and EXEL shall agree upon guidelines and procedures for such common database that shall be in accordance with, and enable BMS and EXEL and their Affiliates to fulfill their reporting obligations under applicable law. Furthermore, such guidelines and procedures shall be consistent with relevant International Council for Harmonisation (“ICH”) guidelines. BMS’ and EXEL’s costs incurred in connection with receiving, investigating, recording, reviewing, communicating, and exchanging such efficacy data shall be included as an element of Development Costs or as Allowable Expenses (to the extent specifically identifiable to or reasonably allocable to the Development or Commercialization of Products for the United States), calculated on a FTE cost and direct out-of-pocket cost basis.
View SourceView Similar (2)
Common Database. If deemed appropriate by the JDC, the Parties will establish a common database to be controlled, maintained and administered by BMS for the receipt, investigation, recordation, communication, and exchange (as between the Parties) of data arising from clinical trials for Products. The Parties shall agree upon guidelines and procedures for such common database that shall be in accordance with, and enable the Parties and their Affiliates to fulfill their reporting obligations under applicable law. Furthermore, such guidelines and procedures shall be consistent with relevant International Council for Harmonisation (“ICH”) guidelines. The Parties’ costs incurred in connection with receiving, investigating, recording, reviewing, communicating, and exchanging such efficacy data shall be included as an element of Development Costs or as Allowable Expenses (to the extent specifically identifiable to or reasonably allocable to the Development or Commercialization of Products for the United States), calculated on a FTE cost and direct out-of-pocket cost basis.
View Source
Common Database. If deemed appropriate by the JDC, the Parties will establish a common database to be controlled, maintained and administered by the Party designated by the JDC for the receipt, investigation, recordation, communication, and exchange (as between the [ * ] = Certain confidential information contained in this document, marked by brackets, has been omitted and filed separately with the Securities and Exchange Commission pursuant to Rule 24b-2 of the Securities Exchange Act of 1934, as amended. Parties) of data arising from Clinical Trials for Collaboration Products. The Parties shall agree upon guidelines and procedures for such common database that shall be in accordance with, and enable the Parties to fulfill their reporting obligations under applicable Law. Furthermore, such guidelines and procedures shall be consistent with relevant International Council for Harmonisation (“ICH”) guidelines. The Parties’ costs incurred in connection with receiving, investigating, recording, reviewing, communicating, and exchanging such data shall be included as an element of Development Costs or as Commercialization Costs, as applicable, calculated on a FTE cost (calculated at the FTE Rate) and direct out-of-pocket cost basis.
View Source
Common Database. If deemed appropriate by the JDC, the Parties will establish a common database to be controlled, maintained and administered by BMS for the receipt, investigation, recordation, communication, and exchange (as between the Parties) of data arising from clinical trials for Co-Developed Products. The Parties shall agree upon guidelines and procedures for such common database that shall be in accordance with, and enable the Parties and their Affiliates to fulfill their reporting obligations under applicable law. Furthermore, such guidelines and procedures shall be consistent with relevant International Council for Harmonisation (“ICH”) guidelines. The Parties’ costs incurred in connection with receiving, investigating, recording, reviewing, communicating, and exchanging such efficacy data shall be included as an element of Development Costs or Allowable Expenses (to the extent specifically identifiable to or reasonably allocable to the Development or Commercialization of Products for the United States), calculated on a FTE cost and direct out-of-pocket cost basis.
View Source

Related to Common Database

  • Database The LERG is available through Telcordia. ICONN is available through the Qwest web site.

  • Line Information Database 9.1 LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, e-Tel must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.

  • Password To enable you, and only you, to use the Service, you will be asked to choose a password when you register and are accepted as a customer of the Service. This password is stored in encrypted form by us. You are responsible for maintaining the confidentiality of your Funds Transfer customer number and password. No one at OneUnited Bank has access to your Accounts passwords or user ID's. You are responsible for uses of the Service whether or not actually or expressly authorized by you. Therefore, it is important that you DO NOT SHARE YOUR ACCOUNT NUMBER OR PASSWORD WITH ANYONE FOR ANY REASON. No one at OneUnited Bank will know or need to know your password, and OneUnited Bank employees will never ask for your password. If you believe your password has been lost or stolen, or that someone has transferred or may transfer money from your Account without your permission, call: (877) ONE-UNITED or fax: (▇▇▇) ▇▇▇-▇▇▇▇, or e-mail: ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇@▇▇▇▇▇▇▇▇▇.▇▇▇, or write: Funds Transfer Administrator, OneUnited Bank ▇▇▇▇ ▇▇▇▇▇▇▇▇ ▇▇▇▇, Los Angeles, CA, 90016. You agree to notify us AT ONCE if you believe your password has been lost or stolen. Telephoning us promptly is the best way to protect yourself from possible losses. If you never tell us, you could lose all of the money in your account (plus your maximum overdraft line of credit). However, if you tell us within 2 business days, you can lose no more than $50 if someone used your password without your permission. If you do NOT tell us within 2 business days after you learn of the loss or theft of your password, and we can prove we could have stopped someone from using your password without your permission if you had told us, you could lose as much as $500. You can see a complete statement of all your funds transfers effected or pending at any time by clicking on the History tab. If your statement shows transfers that you did not make, notify us AT ONCE. If you do not tell us within 60 days after the transfer was posted to your statement, you may not get back any money you lost after the 60 days, if we can prove that we could have stopped someone from taking the money if you had told us in time. If a good reason (such as a long trip or a hospital stay) kept you from telling us, we will extend the time periods.

  • Web Site Information on registration for and use of the E-Verify program can be obtained via the Internet at the Department of Homeland Security Web site: ▇▇▇▇://▇▇▇.▇▇▇.▇▇▇/E-Verify.

  • Passwords Passwords are an important aspect of computer security. A poorly chosen password may result in unauthorized access and/or exploitation of Placer County’s resources. All users, including contractors and vendors with access to the County’s systems, are responsible for the creation and protection of passwords and additionally any updates to County Password policies must be followed. Users must not use the same password for Placer County accounts and personal accounts. The reliability of passwords for maintaining confidentiality cannot be guaranteed. Always assume that someone, in addition to the intended or designated recipient, may read any and all messages and files. Any user suspecting that his/her password may have been compromised must, without delay, report the incident to Placer County IT. 10.2.4.1 Passwords must never be shared or disclosed. If a password is accidentally exposed or suspected of exposure, the password should be changed immediately. 10.2.4.2 All passwords must be changed on a specified, periodic basis. 10.2.4.3 Default passwords provided by the vendor for access to applications/systems on the network must be changed to unique and secret passwords. 10.2.4.4 Immediately inform the Information Technology Service Desk when user accounts are no longer required or will not be used for a period of 30 days or more. 10.2.4.5 All accounts not used for 90 days will be automatically disabled.