Identification of Covered Persons Sample Clauses

Identification of Covered Persons. 11 6.7 Calculation of Capitation.................................................. 11 6.8 Payment of Capitation...................................................... 11 6.9
AutoNDA by SimpleDocs
Identification of Covered Persons. In order to identify Covered Persons and determine compensation under this Agreement, TMHC shall provide Provider with the following information regarding Covered Persons within two (2) days after receipt from the applicable Payer: (a) the names of the Covered Persons who are currently enrolled in a Payer Plan; (b) the names of Covered Persons who have terminated their enrollment in a Payer Plan and the effective date of such termination; (c) the Capitation rates payable to Provider for Covered Persons who are enrolled in a Payer Plan; (d) the names of new Covered Persons and copies of their enrollment forms; and (e) all other necessary and pertinent information regarding Covered Persons for whom Provider is responsible for providing Covered Services. For the purpose of calculating Capitation payments due under this Agreement, the number of Covered Persons will be determined when the necessary information is received from the applicable Payers.

Related to Identification of Covered Persons

  • Certification Regarding Business with Certain Countries and Organizations Pursuant to Subchapter F, Chapter 2252, Texas Government Code, PROVIDER certifies it is not engaged in business with Iran, Sudan, or a foreign terrorist organization. PROVIDER acknowledges this Purchase Order may be terminated if this certification is or becomes inaccurate.

  • Identification of Data a. All Background, Third Party Proprietary and Controlled Government Data provided by Disclosing Party shall be identified in the Annex under which it will be provided. b. NASA software and related Data provided to Partner shall be identified in the Annex under which it will be used. Notwithstanding H.4., Software and related Data will be provided to Partner under a separate Software Usage Agreement (SUA). Partner shall use and protect the related Data in accordance with this Article. Unless the SUA authorizes retention, or Partner enters into a license under 37 C.F.R. Part 404, the related Data shall be disposed of as instructed by NASA.

  • Certification Regarding Prohibition of Certain Terrorist Organizations (Tex Gov. Code 2270) Certification Regarding Prohibition of Boycotting Israel (Tex. Gov. Code 2271) 5 Certification Regarding Prohibition of Contracts with Certain Foreign-Owned Companies (Tex. Gov. 5 Code 2274) 5 Certification Regarding Prohibition of Discrimination Against Firearm and Ammunition Industries (Tex.

  • Access to Personal Information by Subcontractors Supplier agrees to require any subcontractors or agents to which it discloses Personal Information under this Agreement or under any SOW to provide reasonable assurance, evidenced by written contract, that they will comply with the same or substantially similar confidentiality, privacy and security obligations with respect to such Personal Information as apply to Supplier under this Agreement or any SOW. Supplier shall confirm in writing to DXC that such contract is in place as a condition to DXC’s approval of use of a subcontractor in connection with any SOW. Upon request of DXC, Supplier will provide to DXC a copy of the subcontract or an extract of the relevant clauses. Supplier shall ensure that any failure on the part of any subcontractor or agent to comply with the Supplier obligations under this Agreement or any SOW shall be grounds to promptly terminate such subcontractor or agent. If during the term of this Agreement or any SOW, DXC determines, in its exclusive discretion, that any Supplier subcontractor or agent cannot comply with the Supplier obligations under this Agreement or with any SOW, then DXC may terminate this Agreement in whole or in part (with respect to any SOW for which such subcontractor or agent is providing services), if not cured by Supplier within the time prescribed in the notice of such deficiency.

  • Identification Cards Identification (“ID”) cards are issued by Us for identification purposes only. Possession of any ID card confers no right to services or benefits under this Contract. To be entitled to such services or benefits, Your Premiums must be paid in full at the time that the services are sought to be received.

  • Partnership Formation and Identification 6 2.1 Formation............................................................................................ 6 2.2 Name, Office and Registered Agent.................................................................... 6 2.3 Partners............................................................................................. 6 2.4

  • Non-Identification Approved Users agree not to use the requested datasets, either alone or in concert with any other information, to identify or contact individual participants from whom data and/or samples were collected. Approved Users also agree not to generate information (e.g., facial images or comparable representations) that could allow the identities of research participants to be readily ascertained. These provisions do not apply to research investigators operating with specific IRB approval, pursuant to 45 CFR 46, to contact individuals within datasets or to obtain and use identifying information under an 2 The project anniversary date can be found in “My Projects” after logging in to the dbGaP authorized-access portal. IRB-approved research protocol. All investigators including any Approved User conducting “human subjects research” within the scope of 45 CFR 46 must comply with the requirements contained therein.

  • Identification of Goods Identification of the goods shall not be deemed to have been made until both Buyer and Seller have agreed that the goods in question are to be appropriate to the performance of this Agreement.

  • Outside Activities of Limited Partners Subject to any agreements entered into by a Limited Partner or its Affiliates with the General Partner, Partnership or a Subsidiary, any Limited Partner and any officer, director, employee, agent, trustee, Affiliate or stockholder of any Limited Partner shall be entitled to and may have business interests and engage in business activities in addition to those relating to the Partnership, including business interests and activities in direct competition with the Partnership or that are enhanced by the activities of the Partnership. Neither the Partnership nor any Partners shall have any rights by virtue of this Agreement in any business ventures of any Limited Partner or Assignee. Subject to such agreements, none of the Limited Partners nor any other Person shall have any rights by virtue of this Agreement or the partnership relationship established hereby in any business ventures of any other Person, other than the Limited Partners benefiting from the business conducted by the General Partner, and such Person shall have no obligation pursuant to this Agreement to offer any interest in any such business ventures to the Partnership, any Limited Partner or any such other Person, even if such opportunity is of a character which, if presented to the Partnership, any Limited Partner or such other Person, could be taken by such Person.

  • Technical and Organizational Measures The following sections define SAP’s current technical and organizational measures. SAP may change these at any time without notice so long as it maintains a comparable or better level of security. Individual measures may be replaced by new measures that serve the same purpose without diminishing the security level protecting Personal Data.

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