Reporting and Data Sharing Clause Samples

Reporting and Data Sharing. Organization shall provide [monthly, bi-monthly, quarterly] participant status reports to Payer which will contain data on beneficiaries related to enrollment, engagement, retention, and weight-loss progress. The Organization shall release to Payer, upon request, any additional information necessary for the Payer to perform any of its contractual and regulatory obligations, including, but not limited to, its records, reporting, and quality assurance duties. The Organization’s facilities and records shall be open to inspection by the Payer and Medicaid agency, and the Organization is subject to all audits and inspections to the same extent that audits and inspections may be required of the Payer under law or under its contract. Copies of Organization’s medical records pertaining to the Payer’s enrollees, if any, shall be furnished to the Payer upon request for transfer to a subsequent provider in the event of a termination of this agreement.‌
View SourceView Similar (2)
Reporting and Data Sharing a. The Contractor will submit a monthly report at the end of each month during the service span, including, at minimum: i. The peak number of vehicles operating each day in the Town; ii. The vehicle-hours and vehicle-miles operated in service (excluding deadhead travel) and total vehicle-hours and vehicle-miles (including deadhead travel), consistent with FTA National Transit Database definitions by vehicle and by day. iii. The total number of users segregated into new users and returning customers; iv. Data related to ridership connection via app, telephone, etc.; v. Ridership payment data, i.e., paid via debit card, credit card, app-based transfer, cash, etc.; vi. On-time performance; vii. In-vehicle ride time; viii. Number of missed trips; ix. Data on cancellation rates and wait time and its effect on retention; x. The ridership by hour; xi. Detailed miles traveled report of cost per mile and cost per hour, and passengers per hour and passengers per mile; xii. Average weekday boardings;
View Source
Reporting and Data Sharing. 4.3.1. Aggregate customer demographic data that does not identify individual customers, payment methods, of their individual trip history, gathered by Bird shall be provided to the Director of DPW on at least a monthly basis using anonymized keys. 4.3.2. The following information shall be required on the first of each month throughout the duration of the pilot, or as directed by the Director of DPW: 4.3.2.1. Total downloads, active customers & repeat customer information; 4.3.2.2. List of reported parking complaints including: description, location of incident, description of Bird response, and response time; 4.3.2.3. Incidents of electric scooter theft and vandalism; 4.3.2.4. Electric scooter maintenance reports; 4.3.2.5. Complaints received by Bird; 4.3.2.6. Accident/crash information; and 4.3.2.7. Payment method information. 4.3.3. Customer information shall be made available to GBPD upon warrant or subpoena or otherwise required by law.
View Source
Reporting and Data Sharing. To enable Kāinga Ora to collate and share health and safety related information, trends and statistics for the betterment of health and safety generally, upon Possession the Purchaser shall commence providing monthly reports to Kāinga Ora detailing the Purchaser’s implementation of and compliance with this clause 27 and any activity, incidents or accidents that have occurred in the prior month from the date of the last report, such monthly report to be in a form acceptable to Kāinga Ora. The Purchaser acknowledges and agrees this data shall be collated, reviewed, analysed and may then be (anonymously) shared by Kāinga Ora to builder partners and the industry generally for the betterment of health and safety.
View Source
Reporting and Data Sharing. 19.1 Provision of a report on usage statistics when requested by Licensor. The specific statistics being reported will be subject to upfront negotiation between the parties, and may include elements such as: a. number of customer queries received b. number and type of complaints
View Source

Related to Reporting and Data Sharing

  • Reporting and Monitoring Please provide a brief description of the mechanisms proposed for this project for reporting to the UNDP and partners, including a reporting schedule.

  • Information and Data ‌ Upon request of the Union, the Employer agrees to furnish the Union with the following information: budgets for the Board of Regents; budgets for each College; public information used in the preparation of budgets as provided by law such as salaries; minutes of meetings of the Board; policies of the Board of Regents which apply to faculty members. Voluminous information shall be made available for inspection or will be provided at reproduction cost.

  • Reporting and liaison 13.1 The Grantee agrees to provide the Reporting Material specified in the Grant Details to the Commonwealth. 13.2 In addition to the obligations in clause 13.1, the Grantee agrees to: (a) liaise with and provide information to the Commonwealth as reasonably required by the Commonwealth; and (b) comply with the Commonwealth’s reasonable requests, directions, or monitoring requirements, in relation to the Activity. 13.3 If the Commonwealth acting reasonably has concerns regarding the performance of the Activity or the management of the Grant, the Commonwealth may by written notice require the Grantee to provide one or more additional reports, containing the information and by the date(s) specified in the notice. 13.4 The Grantee acknowledges that the giving of false or misleading information to the Commonwealth is a serious offence under the Criminal Code Act 1995 (Cth).

  • Why We Collect Information and For How Long We are collecting your data for several reasons: · To better understand your needs and provide you with the services you have requested; · To fulfill our legitimate interest in improving our services and products; · To send you promotional emails containing information we think you may like when we have your consent to do so; · To contact you to fill out surveys or participate in other types of market research, when we have your consent to do so; · To customize our website according to your online behavior and personal preferences. The data we collect from you will be stored for no longer than necessary. The length of time we retain said information will be determined based upon the following criteria: the length of time your personal information remains relevant; the length of time it is reasonable to keep records to demonstrate that we have fulfilled our duties and obligations; any limitation periods within which claims might be made; any retention periods prescribed by law or recommended by regulators, professional bodies or associations; the type of contract we have with you, the existence of your consent, and our legitimate interest in keeping such information as stated in this Policy.

  • New Hampshire Specific Data Security Requirements The Provider agrees to the following privacy and security standards from “the Minimum Standards for Privacy and Security of Student and Employee Data” from the New Hampshire Department of Education. Specifically, the Provider agrees to: (1) Limit system access to the types of transactions and functions that authorized users, such as students, parents, and LEA are permitted to execute; (2) Limit unsuccessful logon attempts; (3) Employ cryptographic mechanisms to protect the confidentiality of remote access sessions; (4) Authorize wireless access prior to allowing such connections; (5) Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity; (6) Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions; (7) Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles; (8) Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services; (9) Enforce a minimum password complexity and change of characters when new passwords are created; (10) Perform maintenance on organizational systems; (11) Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance; (12) Ensure equipment removed for off-site maintenance is sanitized of any Student Data in accordance with NIST SP 800-88 Revision 1; (13) Protect (i.e., physically control and securely store) system media containing Student Data, both paper and digital; (14) Sanitize or destroy system media containing Student Data in accordance with NIST SP 800-88 Revision 1 before disposal or release for reuse; (15) Control access to media containing Student Data and maintain accountability for media during transport outside of controlled areas; (16) Periodically assess the security controls in organizational systems to determine if the controls are effective in their application and develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems; (17) Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems; (18) Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception); (19) Protect the confidentiality of Student Data at rest; (20) Identify, report, and correct system flaws in a timely manner; (21) Provide protection from malicious code (i.e. Antivirus and Antimalware) at designated locations within organizational systems; (22) Monitor system security alerts and advisories and take action in response; and (23) Update malicious code protection mechanisms when new releases are available.