Data Collection The grant recipient will be required to provide performance data reports on a schedule delineated within Section A of this contract, Specific Terms and Conditions.
Data Collection and Reporting 1. Grantee shall develop and use a local reporting unit that will provide an assigned Hospital location for all clients served within the Hospital. This information shall also be entered into Client Assignment and Registration (CARE) when reporting on beds utilized at the Hospital.
2. Grantee shall budget and report expenditure data on the CARE Report III, incorporated by reference and posted at: ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇▇▇▇.▇▇▇/doing-business-hhs/provider- portals/behavioral-health-services-providers/behavioral-health-provider- resources/community-mental-health-contracts, within the Community Hospital strategy C.2.1.1 using line 764 - Project Private Beds.
3. Grantee shall ensure that patient registration, diagnostics, admission and discharge data is reported by using the CARE screens and action codes listed below:
a. Screen: Campus-Based Assignments (Add/Change/Delete), Action Code: 305;
b. Screen: Campus-Based Discharge/Community Placement (Add/Change/Delete), Action Code: 310;
c. Screen: Joint Community Support Plan (Add/Change/Delete), Action Code: 312;
d. Screen: Register Client, Action Code: 325;
e. Screen: Diagnostics (Add/Change/Delete), Action Code: 330;
f. Screen: Voluntary Admission and Commitment (Add/Change/Delete), Action Code 332;
g. Screen: Campus-Based Residential ▇▇▇▇/Dorm (Add/Change/Delete), Action Code 615; and
h. Screen: MH Bed Allocation Exception (Add/Change/Delete), Action Code 345.
4. For details related to the use of these screens and action codes, Grantee can refer to the CARE Reference Manual which can be found under the CARE (WebCARE) section on the portal at: ▇▇▇▇▇://▇▇▇▇▇▇▇▇▇.▇▇▇.▇▇▇▇▇.▇▇.▇▇/helpGuide/Content/16_CARE/CAREWebCARE%20Refere nce%20Manual.htm
Data Collection and Usage The Company and the Service Recipient collect, process and use certain personal information about Participant, including, but not limited to, Participant’s name, home address, telephone number, email address, date of birth, social insurance number, passport or other identification number, salary, nationality, job title, any shares or directorships held in the Company, details of all awards granted under the Plan or any other entitlement to shares awarded, canceled, exercised, vested, unvested or outstanding in Participant’s favor (“Data”), for purposes of implementing, administering and managing the Plan. The legal basis, where required, for the processing of Data is Participant’s consent.
Data Collection, Processing and Usage Personal data collected, processed and used by the Company in connection with Awards granted under the Plan includes the Grantee’s name, home address, email address, telephone number, date of birth, social insurance number or other identification number, salary, citizenship, job title, any shares of Common Stock or directorships held in the Company, and details of all Awards granted, cancelled, exercised, vested, or outstanding. In granting Awards under the Plan, the Company will collect the Grantee’s personal data for purposes of allocating shares of Common Stock in settlement of the Awards and implementing, administering and managing the Plan. The Company collects, processes and uses the Grantee’s personal data in compliance with Company’s Employment Data Protection Standards and the Uses of Employment Data for the Company’s Entities. The Grantee may exercise rights to access, correction, or restriction or deletion where applicable, by contacting the Grantee’s local HR manager or initiating a request through ▇▇▇.▇▇▇▇.gehealthcare.com.
Termination by ICANN (a) ICANN may, upon notice to Registry Operator, terminate this Agreement if: (i) Registry Operator fails to cure (A) any fundamental and material breach of Registry Operator’s representations and warranties set forth in Article 1 or covenants set forth in Article 2, or (B) any breach of Registry Operator’s payment obligations set forth in Article 6 of this Agreement, each within thirty (30) calendar days after ICANN gives Registry Operator notice of such breach, which notice will include with specificity the details of the alleged breach, (ii) an arbitrator or court of competent jurisdiction has finally determined that Registry Operator is in fundamental and material breach of such covenant(s) or in breach of its payment obligations, and (iii) Registry Operator fails to comply with such determination and cure such breach within ten (10) calendar days or such other time period as may be determined by the arbitrator or court of competent jurisdiction.
(b) ICANN may, upon notice to Registry Operator, terminate this Agreement if Registry Operator fails to complete all testing and procedures (identified by ICANN in writing to Registry Operator prior to the date hereof) for delegation of the TLD into the root zone within twelve (12) months of the Effective Date. Registry Operator may request an extension for up to additional twelve (12) months for delegation if it can demonstrate, to ICANN’s reasonable satisfaction, that Registry Operator is working diligently and in good faith toward successfully completing the steps necessary for delegation of the TLD. Any fees paid by Registry Operator to ICANN prior to such termination date shall be retained by ICANN in full.
(c) ICANN may, upon notice to Registry Operator, terminate this Agreement if (i) Registry Operator fails to cure a material breach of Registry Operator’s obligations set forth in Section 2.12 of this Agreement within thirty (30) calendar days of delivery of notice of such breach by ICANN, or if the Continued Operations Instrument is not in effect for greater than sixty (60) consecutive calendar days at any time following the Effective Date, (ii) an arbitrator or court of competent jurisdiction has finally determined that Registry Operator is in material breach of such covenant, and (iii) Registry Operator fails to cure such breach within ten (10) calendar days or such other time period as may be determined by the arbitrator or court of competent jurisdiction.
(d) ICANN may, upon notice to Registry Operator, terminate this Agreement if (i) Registry Operator makes an assignment for the benefit of creditors or similar act, (ii) attachment, garnishment or similar proceedings are commenced against Registry Operator, which proceedings are a material threat to Registry Operator’s ability to operate the registry for the TLD, and are not dismissed within sixty (60) calendar days of their commencement, (iii) a trustee, receiver, liquidator or equivalent is appointed in place of Registry Operator or maintains control over any of Registry Operator’s property, (iv) execution is levied upon any material property of Registry Operator, (v) proceedings are instituted by or against Registry Operator under any bankruptcy, insolvency, reorganization or other laws relating to the relief of debtors and such proceedings are not dismissed within sixty (60) calendar days of their commencement, or (vi) Registry Operator files for protection under the United States Bankruptcy Code, 11 U.S.C. Section 101, et seq., or a foreign equivalent or liquidates, dissolves or otherwise discontinues its operations or the operation of the TLD.
(e) ICANN may, upon thirty (30) calendar days’ notice to Registry Operator, terminate this Agreement pursuant to Section 2 of Specification 7 or Sections 2 and 3 of Specification 11, subject to Registry Operator’s right to challenge such termination as set forth in the applicable procedure described therein.
(f) ICANN may, upon notice to Registry Operator, terminate this Agreement if (i) Registry Operator knowingly employs any officer who is convicted of a misdemeanor related to financial activities or of any felony, or is judged by a court of competent jurisdiction to have committed fraud or breach of fiduciary duty, or is the subject of a judicial determination that ICANN reasonably deems as the substantive equivalent of any of the foregoing and such officer is not terminated within thirty (30) calendar days of Registry Operator’s knowledge of the foregoing, or (ii) any member of Registry Operator’s board of directors or similar governing body is convicted of a misdemeanor related to financial activities or of any felony, or is judged by a court of competent jurisdiction to have committed fraud or breach of fiduciary duty, or is the subject of a judicial determination that ICANN reasonably deems as the substantive equivalent of any of the foregoing and such member is not removed from Registry Operator’s board of directors or similar governing body within thirty (30) calendar days of Registry Operator’s knowledge of the foregoing.
(g) ICANN may, upon thirty (30) calendar days’ notice to Registry Operator, terminate this Agreement as specified in Section 7.5.
(h) [Applicable to intergovernmental organizations or governmental entities only.] ICANN may terminate this Agreement pursuant to Section 7.16.