Report and Data Requirements Sample Clauses

The "Report and Data Requirements" clause defines the obligations of a party to provide specific reports, records, or data to another party as part of their contractual relationship. Typically, this clause outlines the types of information to be delivered, the format and frequency of reporting, and any standards or protocols that must be followed. For example, a contractor may be required to submit monthly progress reports or detailed financial statements. The core function of this clause is to ensure transparency and accountability by establishing clear expectations for information sharing between the parties.
Report and Data Requirements. 1. Weekly Teleconferences and Communication Awardee shall conduct weekly teleconferences with the Government throughout the performance of the Agreement to discuss tasks accomplished and direction for the upcoming tasks. The Government anticipates reducing the teleconferences once enrollment executes and again after completion of the trial. Awardee shall provide agendas and read-ahead material as required two days prior to the meetings and shall provide minutes of each meeting to the Government. Awardee shall include key subcontractors as attendees at these teleconferences when applicable. The Awardee shall provide meeting minutes within three (3) business days after each formal scheduled meeting/teleconference conducted with JPEO EB.
View SourceView Similar (2)
Report and Data Requirements.  If a due date for a deliverable is on a weekend or holiday, then the deliverable will be due on the next business day.  Planning o The Awardee shall provide an Integrated Master Schedule (IMS) within 30 days of contract award. Any updates to the IMS shall be included in the monthly progress reports. Submission shall be thirty (30) calendar days after the end of each month of performance. The Government will have ten (10) calendar days to respond to the report with any comments and the performer will have an additional five (5) calendar days to revise the deliverable or respond to those comments. o Three-level WBS with costs and schedule (top level is program, level two (2) is phase, level three (3) are major tasks). For WBS level two (2), show breakdown for labor, material, and other indirect costs. WBS shall be updated annually or thirty (30) calendar days after a Statement of Work modification. Government review/approval is fifteen
View Source
Report and Data Requirements. 1. Weekly Teleconferences and Communication Awardee shall conduct weekly teleconferences with the Government throughout the performance of the Agreement to discuss tasks accomplished and direction for the upcoming tasks. Awardee shall provide agendas and read-ahead material as required [***] prior to the meetings and shall provide minutes of each meeting to the Government. Awardee shall include key subcontractors as attendees at these teleconferences when applicable. The Awardee shall provide meeting minutes within [***] after each formal scheduled meeting/teleconference conducted with JPEO CDP
View Source
Report and Data Requirements. A deviation from any deadline specified will be at the mutual agreement of the parties. Weekly Teleconferences and Communication Awardee shall conduct weekly teleconferences with the Government throughout the performance of the Agreement to discuss tasks accomplished and direction for the upcoming tasks. The Government anticipates reducing the teleconferences once enrollment executes and again after completion of the trial. Awardee shall provide agendas and read-ahead material as required two days prior to the meetings and shall provide minutes of each meeting to the Government. Awardee shall include key subcontractors as attendees at these teleconferences when applicable. The Awardee shall provide meeting minutes within three (3) business days after each formal scheduled meeting/teleconference conducted with MCS/JPEO.
View Source
Report and Data Requirements. A. Weekly Teleconferences and Communication Awardee shall conduct weekly teleconferences with the Government throughout the performance of the Agreement to discuss tasks accomplished and direction for the upcoming tasks. The Government anticipates reducing the teleconferences once enrollment executes and again after completion of the trial. Awardee shall provide agendas and read-ahead material as required two days prior to the meetings and shall provide minutes of each meeting to the Government. Awardee shall include key subcontractors as attendees at these teleconferences when applicable. The Awardee shall provide meeting minutes
View Source
Report and Data Requirements. A. Weekly Teleconferences and Communication Awardee shall conduct weekly teleconferences with the Government throughout the performance of the Agreement to discuss tasks accomplished and direction for the upcoming tasks. The Government anticipates reducing the teleconferences once enrollment executes and again after completion of the trial. Awardee shall provide agendas and read-ahead material as required two days prior to the meetings and shall provide minutes of each meeting to the Government. Awardee shall include key subawardees as attendees at these teleconferences when applicable. The Awardee shall provide meeting minutes within three (3) business days after each formal scheduled meeting/teleconference conducted with JPEO JPM CBRN Medical.
View Source

Related to Report and Data Requirements

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

  • System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.

  • Program Requirements The parties shall comply with the Disadvantaged Business Enterprise Program requirements established in 49 CFR Part 26.

  • Meteorological Data Reporting Requirement (Applicable to wind generation facilities only)

  • Specific Requirements compensation insurance with statutory limits required by South Dakota law. Coverage B-Employer’s Liability coverage of not less than $500,000 each accident, $500,000 disease-policy limit, and $500,000 disease-each employee.