Documentation of Resident Roster Changes Sample Clauses

Documentation of Resident Roster Changes a) Performing Agency shall provide HHSC State Hospital Central Administration with an updated Resident Roster within fourteen calendar days if any changes to the above-referenced contents (listed above in parts1a-1i) occur throughout the state fiscal year to accurately document resident participation.
AutoNDA by SimpleDocs

Related to Documentation of Resident Roster Changes

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • Modifications and Updates to the Wire Center List and Subsequent Transition Periods 2.1.4.12.1 In the event BellSouth identifies additional wire centers that meet the criteria set forth in Section 2.1.4.5, but that were not included in the Initial Wire Center List, BellSouth shall include such additional wire centers in a carrier notification letter (CNL). Each such list of additional wire centers shall be considered a “Subsequent Wire Center List”.

  • Implementation of Strategic Plan Goals This Agreement supports the County’s Strategic Plan, Goal 1, Operational Effectiveness/Fiscal Sustainability. This Agreement will provide revenue reimbursement to the Department for services rendered.

  • Joint Network Implementation and Grooming Process Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia:

  • Documentation and Record Keeping 1. Records to be Maintained Subrecipient shall maintain all records required by the Federal regulations specified in 24 CFR 570.506 that are pertinent to the activities to be funded under this Contract. Such records shall include, but not be limited to:

  • Local Health Integration Networks and Restructuring In the event of a health service integration with another service provider the Employer and the Union agree to meet.

  • Additional Acceptable Uses of Student Data Contractor is prohibited from using Student Data for any secondary use not described in this agreement except:

  • Implementation of Agreement Each Party must promptly execute all documents and do all such acts and things as is necessary or desirable to implement and give full effect to the provisions of this Agreement.

  • Implementation Plan The Authority shall cause to be prepared an Implementation Plan meeting the requirements of Public Utilities Code Section 366.2 and any applicable Public Utilities Commission regulations as soon after the Effective Date as reasonably practicable. The Implementation Plan shall not be filed with the Public Utilities Commission until it is approved by the Board in the manner provided by Section 4.9.

  • Documentation and compliance (a) The data importer shall promptly and adequately deal with enquiries from the data exporter that relate to the processing under these Clauses.

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