Person/Case Entity Relationship Model Sample Clauses

Person/Case Entity Relationship Model. Unlike a specific disease surveillance system, where a case-type is defined by the presence or absence of a specific condition, the original CHAMPS surveillance scope and planned duration allowed for the possibility that a person (or case) could be engaged in CHAMPS surveillance in a number of contexts over time. Figure 15 Person/Case Entity Relationship Model for CHAMPS Morality Surveillance
AutoNDA by SimpleDocs

Related to Person/Case Entity Relationship Model

  • Scope of Relationship The parties agree that the relationship established by this Agreement is non-exclusive. Without limiting the foregoing and subject to the provisions of Sections 14 and 20 of this Agreement, each party hereto is expressly permitted, without the need for obtaining any further consent or approval from the other party hereto, to market, offer, sell, broker, underwrite and/or provide other products and services, including, without limitation, any other loan products and services and specifically including, without limitation, any loan products and services similar in scope and nature to the Loans and the related services contemplated by the Program Guidelines, through any of their respective distribution channels and the distribution channels of their respective Third Party Service Providers, including, without limitation, any of such distribution channels through which Loans are offered pursuant to this Agreement.

  • Relationship Manager Inquiry for Actual Knowledge In addition to the electronic and paper record searches described above, the Reporting Financial Institution must treat as Reportable Accounts any High Value Accounts assigned to a relationship manager (including any accounts aggregated with such account) if the relationship manager, has actual knowledge that the Account Holder is a Specified Person.

  • Relationship to Parent Award This Agreement incorporates all the terms and conditions of the Award (AW825280CAV) as at 10 April 2006 with the exception of clauses 13, 16.2.1, 22.3.4, 22.3.5, 37.6 and 40.3. Where there is inconsistency between the Award and this Agreement, the latter will prevail but only to the extent of the inconsistency.

  • INDEPENDENT RELATIONSHIP This Agreement is not intended to constitute, create, give effect to or otherwise recognize a joint venture, partnership, or formal business organization, or agency agreement of any kind, and the rights and obligations of the Parties shall be only those expressly set forth herein.

  • AGENCY RELATIONSHIP Nothing herein shall be construed as constituting the Sub-Advisor as an agent of the Trust or the Fund, except as otherwise contemplated herein.

  • Red Hat Enterprise Linux Developer Suite Red Hat Enterprise Linux Developer Suite provides an open source development environment that consists of Red Hat Enterprise Linux with built-in development tools, certain Red Hat Enterprise Linux Add-Ons, Red Hat Enterprise Linux for Real Time, Smart Management and access to Software Maintenance, but no Development or Production Support. If you use any of the Subscription Services or Software associated with Red Hat Enterprise Linux Developer Suite for Production Purposes, or use the Red Hat Enterprise Linux Software Subscription entitlement independently, you agree to purchase the applicable number of Units of the applicable Software Subscription. Red Hat does not provide Production Support or Development Support for Red Hat Enterprise Developer Suite.

  • Relationship Management LAUSD expects Contractors and their Representatives to ensure that their business dealings with and/or on behalf of LAUSD are conducted in a manner that is above reproach.

  • Relationship between the Parties A Party is not by virtue of this Agreement the employee, agent or partner of the other Party and is not authorised to bind or represent the other Party.

  • Special Aggregation Rule Applicable to Relationship Managers For purposes of determining the aggregate balance or value of accounts held by a person to determine whether an account is a High Value Account, a Reporting Financial Institution shall also be required, in the case of any accounts that a relationship manager knows or has reason to know are directly or indirectly owned, controlled, or established (other than in a fiduciary capacity) by the same person, to aggregate all such accounts.

  • Special Rules Regarding Related Entities and Branches That Are Nonparticipating Financial Institutions If a Finnish Financial Institution, that otherwise meets the requirements described in paragraph 1 of this Article or is described in paragraph 3 or 4 of this Article, has a Related Entity or branch that operates in a jurisdiction that prevents such Related Entity or branch from fulfilling the requirements of a participating FFI or deemed-compliant FFI for purposes of section 1471 of the U.S. Internal Revenue Code or has a Related Entity or branch that is treated as a Nonparticipating Financial Institution solely due to the expiration of the transitional rule for limited FFIs and limited branches under relevant U.S. Treasury Regulations, such Finnish Financial Institution shall continue to be in compliance with the terms of this Agreement and shall continue to be treated as a deemed- compliant FFI or exempt beneficial owner, as appropriate, for purposes of section 1471 of the U.S. Internal Revenue Code, provided that:

Time is Money Join Law Insider Premium to draft better contracts faster.