We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

Central Database Sample Clauses

Central Database. Company shall maintain a central international Adverse Event database of Adverse Event and Serious Adverse Event reports associated with the Compound or a Covered Product (the “Central Database”). Not later thirty (30) days after the first clinical site initiation of a clinical study of Covered Product, Company shall provide NovaMedica with a copy of Company’s standard operating procedure (“SOP”) for safety-related reporting, including a detailed technical description of any data or information intended for inclusion and storage in, and retrieval from, the Central Database. Company shall periodically, but less than annually, review its SOP to ensure adequacy and compliance with then-applicable United States FDA and EMEA regulatory reporting requirements.
Sample 1Sample 2Sample 3
Central Database. Marinus shall maintain a central international Adverse Event database of Adverse Event and Serious Adverse Event reports associated with the Compound or a Covered Product (the “Central Database”). Not later thirty (30) days after the first clinical site initiation of a clinical study of Covered Product, Marinus shall provide NovaMedica with a copy of Marinus’s standard operating procedure (“SOP”) for safety-related reporting, including a detailed technical description of any data or information intended for inclusion and storage in, and retrieval from, the Central Database. Marinus shall periodically, but less than annually, review its SOP to ensure adequacy and compliance with then-applicable United States FDA and EMEA regulatory reporting requirements.
Sample 1Sample 2
Central Database. PharmaEngine shall be responsible for the maintenance of the central database for the Territory regarding all adverse drug reactions, suspected adverse drug reactions and other medical and technical information relevant to the safety of the Licensed Product and shall make the central database available to Xenova's Medical Affairs Liaison or such other Xenova representatives as agreed upon from time to time in writing between the Parties.
Sample 1
Central Database. Data Setup: CONTRACTOR shall utilize a detailed implementation guide that shall allow CONTRACTOR to work with COUNTY to identify system codes and parameters to setup the system to conform to COUNTY’S business requirements. The implementation project manager shall work directly with COUNTY to work through the implementation guide, and this data is subject to approval by COUNTY prior to entry into the system. Once the main implementation guide is approved, CONTRACTOR shall work with COUNTY project manager to develop a series of specific forms to be used by COUNTY staff to submit their park information. These forms shall be specific to COUNTY, and shall be based on COUNTY administrative rules, laws and business requirements as well as the main implementation guide. When these critical documents are completed by the CONTRACTOR, they will then be sent to each park for completion and each park shall submit their park/campground maps for CONTRACTOR to create and enter into the system. The CONTRACTOR’S inventory team shall enter all park data and create maps, which will be returned to each park for review, corrections and resubmission, which review shall not be unreasonably delayed and such acceptance not unreasonably withheld. This process shall continue until each park has ‘signed- off’ on their information within the system. In addition to the park data, CONTRACTOR shall work with COUNTY’S finance staff to review current financial procedures and requirements per the AGREEMENT to ensure that the system is setup accordingly. CONTRACTOR shall work with COUNTY in the initial contact meeting with COUNTYS auditor/controllers department, which shall occur during the initial planning and coordination meetings; and
Sample 1

Related to Central Database

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

  • Line Information Database LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, MyLineToo 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.

  • 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: xxxx://xxx.xxx.xxx/E-Verify.

  • Technical Data For the purpose of this Agreement, "TECHNICAL DATA" shall mean all information of the Company in written, graphic or tangible form relating to any and all products which are developed, formulated and/or manufactured by the Company, as such information exists as of the Effective Date or is developed by the Company during the term hereof.

  • Data The statistical, industry-related and market-related data included in the Registration Statement and the Prospectus are based on or derived from sources which the Company reasonably and in good faith believes are reliable and accurate, and such data agree with the sources from which they are derived. The Company has obtained the written consent to the use of such data from such sources to the extent necessary.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • The Web Services E-Verify Employer Agent agrees to, consistent with applicable laws, regulations, and policies, commit sufficient personnel and resources to meet the requirements of this MOU.

  • Personnel Data The School shall maintain accurate and complete personnel and payroll information and shall provide such information to the Commission, in the format and timeframe prescribed by the Commission, as required for the Legislature or any State agency including but not limited to the Department of Budget & Finance, Employees' Retirement System, and the Hawaii Employer-Union Health Benefits Trust Fund. The School shall ensure each employee receiving State benefits qualifies for such benefits.

  • Links If The Services are made available through the Internet, the Financial Institution’s website may provide links to other websites, including those of Third Parties who may also provide services to You. You acknowledge that all those other websites and Third Party services are independent from the Financial Institution’s and may be subject to separate agreements that govern their use. The Financial Institution and Central 1 have no liability for those other websites or their contents or the use of Third Party services. Links are provided for convenience only, and You assume all risk resulting from accessing or using such other websites or Third Party services.

  • Monthly Data Download Not later than fifteen (15) days after the end of each month, beginning with the month in which the Commencement Date occurs and ending with the Final Shared-Loss Recovery Month, Assuming Bank shall provide Receiver:

Most Referenced Clauses

Most Referenced Definitions