Data Retention The Company will hold and use the Data only as long as is necessary to implement, administer and manage the Grantee’s participation in the Plan, or as required to comply with legal or regulatory obligations, including under tax and security laws.
DATA REPORTING a) CONTRACTOR shall agree to provide all data related to student information and billing information with XXX. CONTRACTOR shall agree to provide all data related to any and all sections of this contract and requested by and in the format require by the LEA. CONTRACTOR shall provide the LEA with invoices, attendance reports and progress reports for LEA students enrolled in CONTRACTOR’s NPS/A.
b) Using forms developed by the CDE or as otherwise mutually agreed upon by CONTRACTOR and XXX, CONTRACTOR shall provide LEA, on a monthly basis, a written report of all incidents in which a statutory offense is committed by any LEA student, regardless if it results in a disciplinary action of suspension or expulsion. This includes all statutory offenses as described in Education Code sections 48900 and 48915. CONTRACTOR shall also include, in this monthly report, incidents resulting in the use of a behavioral restraint and/or seclusion even if they were not a result of a violation of Education Code sections 48900 and 48915.
c) The LEA shall provide the CONTRACTORS with approved forms and/or format for such data including but not limited to invoicing, attendance reports and progress reports. The LEA may approve use of CONTRACTORS-provided forms at their discretion.
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.
Project Monitoring Reporting and Evaluation The Recipient shall furnish to the Association each Project Report not later than forty-five (45) days after the end of each calendar semester, covering the calendar semester.
Program Monitoring and Evaluation The Recipient shall prepare, or cause to be prepared, and furnish to the Association not later than six months after the Closing Date, a report of such scope and in such detail as the Association shall reasonably request, on the execution of the Program, the performance by the Recipient and the Association of their respective obligations under the Legal Agreements and the accomplishment of the purposes of the Financing.”
Reporting and Record Keeping CONTRACTOR shall comply with all program and fiscal reporting requirements set forth by appropriate Federal, State and local agencies, and as required by the COUNTY. (c) CONTRACTOR agrees to provide to COUNTY, to any Federal or State department having monitoring or review authority, to COUNTY's authorized representatives, and/or their appropriate audit agencies upon reasonable notice, access to and the right to examine all records and documents necessary to determine compliance with relevant Federal, State, and local statutes, rules and regulations, and this Agreement, and to evaluate the quality, appropriateness and timeliness of services performed.
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).
Monitoring and Evaluation a. The AGENCY shall expeditiously provide to the COUNTY upon request, all data needed for the purpose of monitoring, evaluating and/or auditing the program(s). This data shall include, but not be limited to, clients served, services provided, outcomes achieved, information on materials and services delivered, and any other data required, in the sole discretion of the COUNTY, that may be required to adequately monitor and evaluate the services provided under this Contract. Monitoring shall be performed in accordance with COUNTY’S established Noncompliance Standards, a copy of which is attached hereto and incorporated by reference as Attachment “C”.
b. The AGENCY agrees to permit persons duly authorized by the COUNTY to interview any clients and all current and/or former employees of the AGENCY to be assured of the AGENCY’S satisfactory performance of the terms of this Contract.
c. Following such evaluation, monitoring, and/or audit, the COUNTY will deliver a report of its findings and recommendations with regard to the AGENCY’S conformance with this Contract’s terms and conditions to the AGENCY and/or Board of Directors’ President, and members, whenever applicable. If deficiencies are noted, a written notice of corrective action will be issued to the AGENCY which will specify deficiencies and provide a timeline for correction of those deficiencies. Within the designated timeframe in the written notice of corrective action, the AGENCY shall submit to the COUNTY’S CCC manager (“Manager”), or their designee, a corrective action plan to rectify all deficiencies identified by the COUNTY.
d. Failure by the AGENCY to correct noted deficiencies, as outlined in the written notice of corrective action, may result in the AGENCY being deemed in breach of the Contract terms.
e. The AGENCY shall cooperate with the COUNTY on all reviews to ensure compliance with all applicable COUNTY guidelines and requirements for general fund recipients.
Data Requirements • The data referred to in this document are encounter data – a record of health care services, health conditions and products delivered for Massachusetts Medicaid managed care beneficiaries. An encounter is defined as a visit with a unique set of services/procedures performed for an eligible recipient. Each service should be documented on a separate encounter claim detail line completed with all the data elements including date of service, revenue and/or procedure code and/or NDC number, units, and MCE payments/cost of care for a service or product. • All encounter claim information must be for the member identified on the claim by Medicaid ID. Claims must not be submitted with another member’s identification (e.g., xxxxxxx claims must not be submitted under the Mom’s ID). • All claims should reflect the final status of the claim on the date it is pulled from the MCE’s Data Warehouse. • For MassHealth, only the latest version of the claim line submitted to MassHealth is “active”. Previously submitted versions of claim lines get offset (no longer “active” with MassHealth) and payments are not netted. • An encounter is a fully adjudicated service (with all associated claim lines) where the MCE incurred the cost either through direct payment or sub-contracted payment. Generally, at least one line would be adjudicated as “paid”. All adjudicated claims must have a complete set of billing codes. There may also be fully adjudicated claims where the MCE did not incur a cost but would otherwise like to inform MassHealth of covered services provided to Enrollees/Members, such as for quality measure reporting (e.g., CPT category 2 codes for A1c lab tests and care/patient management). • All claim lines should be submitted for each Paid claim, including zero paid claim lines (e.g., bundled services paid at an encounter level and patient copays that exceeded the fee schedule). Denied lines should not be included in the Paid submission. Submit one encounter record/claim line for each service performed (i.e., if a claim consisted of five services or products, each service should have a separate encounter record). Pursuant to contract, an encounter record must be submitted for all covered services provided to all enrollees. Payment amounts must be greater than or equal to zero. There should not be negative payments, including on voided claim lines. • Records/services of the same encounter claim must be submitted with same claim number. There should not be more than one active claim number for the same encounter. All paid claim lines within an encounter must share the same active claim number. If there is a replacement claim with a new version of the claim number, all former claim lines must be replaced by the new claim number or be voided. The claim number, which creates the encounter, and all replacement encounters must retain the same billing provider ID or be completely voided. • Plans are expected to use current MassHealth MCE enrollment assignments to attribute Members to the MassHealth assigned MCE. The integrity of the family of claims should be maintained when submitting claims for multiple MCEs (ACOs/MCO). Entity PIDSL, New Member ID, and the claim number should be consistent across all lines of the same claim. • Data should conform to the Record Layout specified in Section 3.0 of this document. Any deviations from this format will result in claim line or file rejections. Each row in a submitted file should have a unique Claim Number + Suffix combination. • A feed should consist of new (Original) claims, Amendments, Replacements (a.k.a. Adjustments) and/or Voids. The replacements and voids should have a former claim number and former suffix to associate them with the claim + suffix they are voiding or replacing. See Section 2.0, Data Element Clarifications, for more information. • While processing a submission, MassHealth scans the files for the errors. Rejected records are sent back to the MCEs in error reports in a format of the input files with two additional columns to indicate an error code and the field with the error. • Unless otherwise directed or allowed by XxxxXxxxxx, all routine monthly encounter submissions must be successfully loaded to the MH DW on or before the last day of each month with corrected rejections successfully loaded within 5 business days of the subsequent month for that routine monthly encounter submission to be considered timely and included in downstream MassHealth processes. Routine monthly encounter submissions should contain claims with paid/transaction dates through the end of the previous month.
Meteorological Data Reporting Requirement (Applicable to wind generation facilities only)
