Component Requirements and Verification. The following tools and features are used to capture component level require- ments and perform verification.
Component Requirements and Verification Sample Clauses
Related to Component Requirements and Verification
Project Requirements 1. Project must conform to regulations under 24 CFR Part 92, commonly known as the HOME Regulations.
Agreement Requirements This agreement will be issued to cover the Janitorial Service requirements for all State Agencies and shall be accessible to any School District, Political Subdivision, or Volunteer Fire Company.
Equipment Requirements No Equipment is provided to Customer as part of this Service.
Testing Requirements 12.1. Workplaces - 12.2. On workplaces where the value of the Commonwealth’s contribution to the project that includes the building work is at least $5,000,000, and represents at least 50% of the total construction project value or the Commonwealth’s contribution to the project that includes the building work is at least $10,000,000 (irrespective of its proportion of the total construction project value) the following minimum testing requirements must be adhered to.
Payment Requirements A. Contract Amount: It is expressly agreed and understood that the total amount to be paid by County under this Contract shall not exceed the total County funding as set forth in Attachment B-Payment/Compensation to Subrecipient attached hereto and incorporated herein by reference. B. County will reclaim any unused balance of funds for reallocation to other County approved projects.
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.
Support Requirements If there is a dispute between the awarded vendor and TIPS Member, TIPS or its representatives may assist, at TIPS sole discretion, in conflict resolution or third party (mandatory mediation), if requested by either party. TIPS, or its representatives, reserves the right to inspect any project and audit the awarded vendors TIPS project files, documentation and correspondence. TIPS Members stand in the place of TIPS as related to this agreement and have the same access to the proposal information and all related documents. TIPS Members have all the same rights under the awarded Agreement as TIPS.
Amendment Requirements (a) Notwithstanding the provisions of Sections 13.1 and 13.2, no provision of this Agreement that establishes a percentage of Outstanding Units (including Units deemed owned by the General Partner) required to take any action shall be amended, altered, changed, repealed or rescinded in any respect that would have the effect of reducing such voting percentage unless such amendment is approved by the written consent or the affirmative vote of holders of Outstanding Units whose aggregate Outstanding Units constitute not less than the voting requirement sought to be reduced. (b) Notwithstanding the provisions of Sections 13.1 and 13.2, no amendment to this Agreement may (i) enlarge the obligations of any Limited Partner without its consent, unless such shall be deemed to have occurred as a result of an amendment approved pursuant to Section 13.3(c), (ii) enlarge the obligations of, restrict in any way any action by or rights of, or reduce in any way the amounts distributable, reimbursable or otherwise payable to, the General Partner or any of its Affiliates without its consent, which consent may be given or withheld in its sole discretion, (iii) change Section 12.1(b), or (iv) change the term of the Partnership or, except as set forth in Section 12.1(b), give any Person the right to dissolve the Partnership. (c) Except as provided in Section 14.3, and without limitation of the General Partner’s authority to adopt amendments to this Agreement without the approval of any Partners or Assignees as contemplated in Section 13.1, any amendment that would have a material adverse effect on the rights or preferences of any class of Partnership Interests in relation to other classes of Partnership Interests must be approved by the holders of not less than a majority of the Outstanding Partnership Interests of the class affected. (d) Notwithstanding any other provision of this Agreement, except for amendments pursuant to Section 13.1 and except as otherwise provided by Section 14.3(b), no amendments shall become effective without the approval of the holders of at least 90% of the Outstanding Units voting as a single class unless the Partnership obtains an Opinion of Counsel to the effect that such amendment will not affect the limited liability of any Limited Partner under applicable law. (e) Except as provided in Section 13.1, this Section 13.3 shall only be amended with the approval of the holders of at least 90% of the Outstanding Units.
System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.
Invoice Requirements Contractor hereby waives the right to enforce any term which contradicts or modifies any term of the solicitation or any Contract that may result, including subsequent amendments to the Contract, or would result in an unencumbered expense if enforced against the state. Contract quote and invoice must contain, at a minimum:
