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.
Monthly Data Download Not later than fifteen (15) days after the end of each month, beginning with the month in which the Commencement Date occurs and ending with the Final Shared-Loss Recovery Month, Assuming Bank shall provide Receiver:
Data Collection, Processing and Usage The Company collects, processes and uses the International Participant’s personal data, including the International Participant’s name, home address, email address, and 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 Equity Awards or any other equity compensation awards granted, canceled, exercised, vested, or outstanding in the International Participant’s favor, which the Company receives from the International Participant or the Employer. In granting the Equity Award under the Plan, the Company will collect the International Participant’s personal data for purposes of allocating shares of Common Stock and implementing, administering and managing the Plan. The Company’s legal basis for the collection, processing and usage of the International Participant’s personal data is the International Participant’s consent.
Data Collection and Usage The Company and the Employer collect, process and use certain personal information about the Participant, including, but not limited to, the Participant’s name, home address and telephone number, email address, date of birth, social insurance, passport or other identification number, salary, nationality, job title, any Shares or directorships held in the Company, details of all restricted stock units or any other entitlement to Shares or equivalent benefits awarded, canceled, exercised, vested, unvested or outstanding in the Participant’s favor (“Data”), for the legitimate purpose of implementing, administering and managing the Plan. The legal basis, where required, for the processing of Data is the Participant’s consent.
Billing and Collection Customers BellSouth currently has in effect numerous billing and collection agreements with various interexchange carriers and billing clearing houses and as such these billing and collection customers (“B&C Customers”) query BellSouth’s LIDB to determine whether to accept various billing options from End Users. Until such time as BellSouth implements in its LIDB and its supporting systems the means to differentiate Lightyear’s data from BellSouth’s data, the following shall apply: (1) Lightyear will accept responsibility for telecommunications services billed by BellSouth for its B&C Customers for Lightyear’s End User accounts which are resident in LIDB pursuant to this Agreement. Lightyear authorizes BellSouth to place such charges on Lightyear’s xxxx from BellSouth and shall pay all such charges, including, but are not limited to, collect and third number calls. (2) Charges for such services shall appear on a separate BellSouth xxxx xxxx identified with the name of the B&C Customers for which BellSouth is billing the charge. (3) Lightyear shall have the responsibility to render a billing statement to its End Users for these charges, but Lightyear shall pay BellSouth for the charges billed regardless of whether Lightyear collects from Lightyear’s End Users. (4) BellSouth shall have no obligation to become involved in any disputes between Lightyear and B&C Customers. BellSouth will not issue adjustments for charges billed on behalf of any B&C Customer to Lightyear. It shall be the responsibility of Lightyear and the B&C Customers to negotiate and arrange for any appropriate adjustments.
RECOVERY PROCEDURES The nature and severity of any disaster will influence the recovery procedures. One crucial factor in determining how BellSouth will proceed with restoration is whether or not BellSouth's equipment is incapacitated. Regardless of who's equipment is out of service, BellSouth will move as quickly as possible to aid with service recovery; however, the approach that will be taken may differ depending upon the location of the problem.
Grievance Processing Union stewards or Union officials shall be permitted to have time off without loss of pay for the investigation and processing of grievances and arbitrations. Requests for such time off shall be made in advance and shall not be unreasonably denied. The Union will furnish the Employer with a list of Union stewards and their jurisdictions. The Union shall delineate the jurisdiction of Union stewards so that no xxxxxxx need travel between work locations or sub-divisions thereof while investigating grievances. Grievants shall be permitted to have time off without loss of pay for processing their grievances through the contractual grievance procedure, except that for class action grievances no more than three (3) grievants shall be granted such leave.
Data Collection and Reporting 1. Grantee shall develop and use a local reporting unit that will provide an assigned 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: xxxxx://xxx.xxx.xxxxx.xxx/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 Xxxx/Dorm (Add/Change/Delete), Action Code 615; and h. Screen: MH Bed Allocation Exception (Add/Change/Delete), Action Code 345. 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: xxxxx://xxxxxxxxx.xxx.xxxxx.xx.xx/helpGuide/Content/16_CARE/CAREWebCARE%20Refere nce%20Manual.htm
FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-‐xxxxxx-‐icann-‐registry-‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).
Encounter Data Party shall provide encounter data to the Agency of Human Services and/or its departments and ensure further that the data and services provided can be linked to and supported by enrollee eligibility files maintained by the State.
