Data, Reports and Statistics Sample Clauses

Data, Reports and Statistics. Each party agrees to make available to the other, upon its written request, information and statistics compiled and records it customarily maintains when such material is readily available and is reasonably relevant to negotiations or necessary for the proper enforcement of the terms of this Agreement. This pro­ vision shall not be construed to require either party to produce to the other surveys or other documents created to inform policy deliberations.
AutoNDA by SimpleDocs

Related to Data, Reports and Statistics

  • Data Reporting 1. Maintain and adhere to data system software and encrypted portable computer device updates, and interface capability requirements for each computer located within the facility, and as specified in the Contract and required by County.

  • Meteorological Data Reporting Requirement (Applicable to wind generation facilities only) The wind generation facility shall, at a minimum, be required to provide the Transmission Provider with site-specific meteorological data including: • Temperature (degrees Fahrenheit) • Wind speed (meters/second) • Wind direction (degrees from True North) • Atmosphere pressure (hectopascals) • Forced outage data (wind turbine and MW unavailability)

  • COPIES OF REGULATORY REPORTS AND FILINGS Upon reasonable request, Competitive Supplier shall provide to the Town a copy of each public periodic or incident-related report or record relating to this ESA which it files with any Massachusetts or federal agency regulating rates, service, compliance with environmental laws, or compliance with affirmative action and equal opportunity requirements, unless the Competitive Supplier is required by law or regulation to keep such reports confidential. The Town shall treat any reports and/or filings received from Competitive Supplier as confidential information subject to the terms of Article 16. Competitive Supplier shall be reimbursed its reasonable costs of providing such copies.

  • Evaluation Reports Where a formal evaluation of an employee's performance is carried out, the employee shall be provided with a copy to read and review. Provision shall be made on the evaluation form for an employee to sign it. The form shall provide for the employee's signature in two (2) places, one indicating that the employee has read and accepts the evaluation, and the other indicating that the employee disagrees with the evaluation. The employee shall sign in one of the places provided within seven (7) calendar days. No employee may initiate a grievance regarding the contents of an evaluation report unless the signature indicates disagreement with the evaluation. The employee shall receive a copy of the evaluation report at the time of signing. An evaluation report shall not be changed after an employee has signed it, without the knowledge of the employee, and any such changes shall be subject to the grievance procedure.

  • Daily Job Reports 6.7.2.1 Developer shall maintain, at a minimum, at least one (1) set of Daily Job Reports on the Project. These must be prepared by Xxxxxxxxx's employee(s) who are present on Site, and must include, at a minimum, the following information:

  • Root-­‐zone Information Publication ICANN’s publication of root-­‐zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.

  • FINANCIAL STATUS REPORTS (FSRS Except as otherwise provided, for contracts with categorical budgets, Grantee shall submit quarterly FSRs to System Agency by the last business day of the month following the end of each quarter for System Agency review and financial assessment. Grantee shall submit the final FSR no later than forty-five (45) calendar days following the end of the applicable term.

  • 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.

  • Utilization Reports Both the Contractor and Subcontractor shall complete Quarterly Utilization Reports (or similar type documents containing the same information) and submit them to the Contracting Officer and to the Bureau within ten (10) business days at the end of each quarter. This information will be used to determine the actual dollar amount paid to Subcontractor and will also serve as a record of fulfillment of Contractor’s Small Diverse Business and Small Business Commitments. If there was no activity during the quarter, then the form must be completed by stating “No activity in this quarter.” A late fee of $100.00 per day may be assessed against the Contractor if its Utilization Report is not submitted in accordance with the schedule above.

  • Reports and Records The Custodian shall:

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