Data Dictionary Sample Clauses

Data Dictionary. EPA, SCDHEC, and SRS recognize that each regulatory report is unique and may require the collection of data that is unique to an individual RCRA/CERCLA Unit or Operable Unit. SRS will define the unique fields and their use upon delivery of the data. DOE will provide a functional data dictionary with the transmission of electronic data for each individual report submitted.
Sample 1Sample 2
AutoNDA by SimpleDocs
Data Dictionary. Me software for the Information Desktop tools will reside on equipment located at Customer's facility and operated by Customer's employees.
Sample 1
Data Dictionary. The Contractor shall work with HCD, GMS system, and any other related system to develop a consolidated data dictionary, data mapping, and governance structure. This data dictionary shall be consistently updated for the duration of the contract.
Sample 1
Data Dictionary. Contractor shall provide a human-understandable data dictionary for the Database Software such that County staff may understand what, where and how data is stored in the Database and how the data elements relate to one another.
Sample 1
Data Dictionary. A group of domain experts and IT experts created the data dictionary which defines the data elements to be used for the CCDC. The goal was to create a comprehensive data dictionary for annotating the available biomaterial, such that the resulting data collection can be used for answering a wide range of research questions. The data dictionary not only serves as a specification for the data entry interface, but also provides a solid basis for developing a colon cancer ontology and providing a terminology service for semantic ontology mapping. A data dictionary is defined as a set of defined common data elements (CDE) for data entry and retrieval by search criteria. Its data elements are systematically ordered in a hierarchical structure similar to a taxonomy and identified by a unique global key common to all participating institutions. The key and its designation constitute a defined data element, which is an IT representation of a medical attribute. To create the CCDC data dictionary, the expert group started by identifying a list of medically relevant attributes. Unlike a collection developed to answer a specific research question, the CCDC is a general-purpose collection whose prospective users display a wide variety of information needs. The data dictionary reflects this by defining a basic set of data elements which cover the information typically recorded about a colon cancer case, thus enabling flexibility in servicing diverse queries. The medical experts ensured that the list of items to be included in the dictionary contains items with high clinical and scientific relevance. The IT experts created an entity relationship model based on the medical experts’ list, using input from the medical experts to determine the relationship between the entities and their attributes. They ensured that all data elements are disjoint, unambiguous, and that for each data element, there is a well-defined range of values. The data elements were based on typical data gathered during the course of a colon cancer case, describing both diagnostic and therapeutic measures. Where possible, the items were based on existing classification systems, such as the ICD-10 for diagnosis and the UICC scale for tumor grading. For the remaining answers, the vocabulary was chosen such that it reflects typical clinical use and minimizes potential ambiguity. The data dictionary can be extended, if user feedback determines that this is necessary.
Sample 1
Data Dictionary. The data dictionary can be seen as a first step towards developing a full-fledged ontology for colon cancer. It provides a basic set of entities and attributes to be included in the ontology and takes into account the actual level of information available in clinical and biobank information systems. The data dictionary is also suitable for semantically mapping the data from the source biobanks to a standard data model used for the CCDC. The interface described in this report allows this to happen in a manual data entry process, while the future ETL adapters will use the data model to provide semi- automatic mapping. This leads to harmonization of the diverse source data, and allows users to discover comparable data with a single search. The data dictionary is therefore an important intermediate result for creating semantic interoperability of biobank data in ADOPT. Figure 2 Patient form for the CCDC Figure 3 Sample form for CCDC
Sample 1
Data Dictionary. The aim of this section is to present the data dictionary, giving further detail on the entity previously described. Each UML model class equates to a data dictionary entity. Each UML model class attribute equates to a data dictionary element. The shaded rows define entities. The entities and elements within the data dictionary are defined by six attributes (those attributes are listed below and are based on those specified in ISO/IEC 11179-3 for the description of data element concepts, i.e. data elements without representation). The term “dataset” when used as part of a definition is synonymous with all types of geographic data resources (aggregations of datasets, individual features and the various classes that compose a feature).
Sample 1
AutoNDA by SimpleDocs
Data Dictionary. Prior to go-live, the Service Provider shall provide a data dictionary in accordance with the State of Delaware Data Modeling Standard.
Sample 1

Related to Data Dictionary

  • Contract Database Metadata Elements Title: Great Neck Union Free School District and Great Neck Paraprofessionals Association (2011) Employer Name: Great Neck Union Free School District Union: Great Neck Paraprofessionals Association Local: Effective Date: 07/01/2011 Expiration Date: 06/30/2015 PERB ID Number: 5132 Unit Size: Number of Pages: 28 For additional research information and assistance, please visit the Research page of the Catherwood website - xxxx://xxx.xxx.xxxxxxx.xxx/library/research/ For additional information on the ILR School - xxxx://xxx.xxx.xxxxxxx.xxx/ ARTICLE# TITLE PAGE# Preamble 2 Article 1 Association Rights 2 Article 2 Board-Administration-Association Relationship and Procedures 4 Article 3 Exchange of Proposals 6 Article 4 Professionals Duties and Responsibilities of Paraprofessionals 7 Article 5 Work Assignments 8 Article 6 Annual Appointment 10 Article 7 Selection and Promotion 10 Article 8 Evaluations and Standards 11 Article 9 Procedures for Termination of Employment 11 Article 10 Conferences 12 Article 11 Human Resource File 12 Article 12 Professional Growth 13 Article 13 Sick Leave 14 Article 14 Personal Leave 16 Article 15 Other Leaves 17 Article 16 Grievance Procedures 18 Article 17 Legal Assistance 19 Article 18 Conformity to Law 19 Article 19 Health Insurance 20 Article 20 Retirement Plan 20 Article 21 Salary Schedule 21 Article 22 Seniority Policy 23 Article 23 Compensation for Financial Loss 24 Article 24 Duration of Agreement 25 Appendix A Determination of Negotiating Unit 25 Appendix B Payroll Deduction Authorization 26 Appendix C Bus Aides 26 Appendix D Salary Schedules 27

  • Provider Network The Panel of health service Providers with which the Contractor contracts for the provision of covered services to Members and Out-of-network Providers administering services to Members.

  • CERTIFICATION REGARDING CERTAIN FOREIGN-OWNED COMPANIES IN CONNECTION WITH CRITICAL INFRASTRUCTURE (Texas law as of September 1, 2021) By submitting a proposal to this Solicitation, you certify that you agree to the following required by Texas law as of September 1, 2021: Proposing Company is prohibited from entering into a contract or other agreement relating to critical infrastructure that would grant to the company direct or remote access to or control of critical infrastructure in this state, excluding access specifically allowed by the Proposing Company for product warranty and support purposes. Company, certifies that neither it nor its parent company nor any affiliate of company or its parent company, is (1) owned by or the majority of stock or other ownership interest of the company is held or controlled by individuals who are citizens of China, Iran, North Korea, Russia, or a designated country; (2) a company or other entity, including governmental entity, that is owned or controlled by citizens of or is directly controlled by the government of China, Iran, North Korea, Russia, or a designated country; or (3) headquartered in China, Iran, North Korea, Russia, or a designated country. For purposes of this contract, “critical infrastructure” means “a communication infrastructure system, cybersecurity system, electric grid, hazardous waste treatment system, or water treatment facility.” See Tex. Gov’t Code § 2274.0101(2) of SB 1226 (87th leg.). The company verifies and certifies that company will not grant direct or remote access to or control of critical infrastructure, except for product warranty and support purposes, to prohibited individuals, companies, or entities, including governmental entities, owned, controlled, or headquartered in China, Iran, North Korea, Russia, or a designated country, as determined by the Governor.

  • Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.

  • Service Area (a) SORACOM shall provide the SORACOM Air Global Service within the area designated on the web site of SORACOM (the “Service Area”), provided, that, the Service Area may be different if stated otherwise as specified by SORACOM separately. However, within the Service Area, you may not use the SORACOM Air Global Service in places where transmissions are difficult to send or receive. (b) The parties of this Agreement acknowledge that there may be countries or locations within which SORACOM may be restricted from providing the SORACOM Air Global Service due to applicable laws, regulations, decisions, rules or orders (“Restrictions”). During the Term, SORACOM will use reasonable efforts to monitor whether there are any such Restrictions. SORACOM may in its sole discretion and at any time, suspend, discontinue, limit, or modify the SORACOM Air Global Service or impose additional requirements on the provision of the SORACOM Air Global Service, as may be reasonably required to comply with any such Restrictions. (c) In no event will SORACOM be required to provide the SORACOM Air Global Service in countries or locations, or in a manner that would be in violation of the Restrictions and its failure to provide the SORACOM Air Global Service due to the Restrictions will not be deemed to be a breach of its obligations under this Agreement. (d) In the event that any Restriction, or any change in applicable law, regulation, decision, rule or order materially or adversely affects the delivery of the SORACOM Air Global Service (including the economic viability thereof), SORACOM will notify Subscribers in writing and the parties will negotiate in good faith regarding changes to this Agreement. If the parties cannot reach agreement within 30 days after notification from SORACOM requesting renegotiation, SORACOM may terminate the Agreement upon 30 days’ written notice to the Subscriber.

  • Population The Population shall be defined as all Paid Claims during the 12-month period covered by the Claims Review.

  • GENERAL SERVICE DESCRIPTION Service Provider currently provides active medical, pharmacy(Rx) and dental administration for coverages provided through Empire and Anthem (medical), Medco(Rx), MetLife(dental) and SHPS (FSA) (Empire, Anthem, Medco, MetLife and SHPS collectively, the “Vendors”) for its U.S. Active, Salaried, Eligible Employees (“Covered Employees”). Service Provider shall keep the current contracts with the Vendors and the ITT CORPORATION SALARIED MEDICAL AND DENTAL PLAN (PLAN NUMBER 502 EIN 00-0000000) and the ITT Salaried Medical Plan and Salaried Dental Plan General Plan Terms (collectively, the “Plans”) and all coverage thereunder in full force through December 31, 2011 for Service Recipient’s Covered Employees. All claims of Service Recipient’s Covered Employees made under the Plans and incurred on or prior to December 31, 2011 the (“2011 Plan Year”) will be adjudicated in accordance with the current contract and Service Provider will continue to take such actions on behalf of Service Recipient’s Covered Employees as if such employees are employees of Service Provider. All medical, dental, pharmacy and FSA claims of Service Recipient’s Covered Employees made under the Plans (the “Claims”) will be paid by the Vendors on behalf of the Service Provider. Service Recipient will pay Service Provider for coverage based on 2011 budget premium rates previously set for the calendar year 2011 and described in the “Pricing” section below. Service Recipient will pay Service Provider monthly premium payments for this service, for any full or partial months, based on actual enrollment for the months covered post-spin using enrollments as of the first (1st) calendar day of the month, commencing on the day after the Distribution Date. Service Recipient will prepare and deliver to Service Provider a monthly self xxxx containing cost breakdown by business unit and plan tier as set forth on Attachment A, within five (5) Business Days after the beginning of each calendar month. The Service Recipient will be required to pay the Service Provider the monthly premium payments within ten (10) Business Days after the beginning of each calendar month. A detailed listing of Service Recipient’s employees covered, including the Plans and enrollment tier in which they are enrolled, will be made available to Service Provider upon its reasonable request. Service Provider will retain responsibility for executing funding of Claim payments and eligibility management with Vendors through December 31, 2013. Service Provider will conduct a Headcount True-Up (as defined below) of the monthly premiums and establish an Incurred But Not Reported (“IBNR”) claims reserve for Claims incurred prior to December 31, 2011 date, but paid after that date, and conduct a reconciliation of such reserve. See “Headcount True-Up” and “IBNR Reconciliation” sections under Additional Pricing for details.

  • Foreign-Owned Companies in Connection with Critical Infrastructure If Texas Government Code, Section 2274.0102(a)(1) (relating to prohibition on contracts with certain foreign-owned companies in connection with critical infrastructure) is applicable to this Contract, pursuant to Government Code Section 2274.0102, Contractor certifies that neither it nor its parent company, nor any affiliate of Contractor or its parent company, is: (1) majority owned or controlled by citizens or governmental entities of China, Iran, North Korea, Russia, or any other country designated by the Governor under Government Code Section 2274.0103, or (2) headquartered in any of those countries.

  • PROHIBITION ON CERTAIN TELECOMMUNICATIONS AND VIDEO SURVEILLANCE SERVICES OR EQUIPMENT To the extent applicable, Supplier certifies that during the term of this Contract it will comply with applicable requirements of 2 C.F.R. § 200.216.

  • Video Display Terminals ‌ The Employer shall ensure that any new office equipment or facility required for use in conjunction with VDTs shall meet the standards recommended by the Workers' Compensation Board.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!