Project Requirements Failure to comply with the following requirements will result in a suspension of all other operations:
Equipment Requirements No Equipment is provided to Customer as part of this Service.
System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.
Procurement Requirements The below listed provisions of State Procurement requirements shall be complied with throughout the contract period:
Network Requirements (A) The Contractor shall maintain and monitor a network of appropriate Network Providers that is supported by written agreements and is sufficient to provide adequate access to all Covered Services for all Enrollees, including those with limited English proficiency or physical or mental disabilities. In establishing and maintaining the network of Network Providers the Contractor shall consider:
Subcontract Requirements As required by Section 6.22(e)(5) of the Administrative Code, Contractor shall insert in every subcontract or other arrangement, which it may make for the performance of Covered Services under this Agreement, a provision that said subcontractor shall pay to all persons performing labor in connection with Covered Services under said subcontract or other arrangement not less than the highest general prevailing rate of wages as fixed and determined by the Board of Supervisors for such labor or services.
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.
CONTRACT REQUIREMENTS a. NSF will exercise its responsibility for oversight and monitoring of procurements, contracts or other contractual arrangements for the purchase of materials and supplies, equipment or general support services under the award. The procedures set forth below must be followed to ensure that performance, materials and services are obtained in an effective manner and in compliance with the provisions of applicable Federal statutes and executive orders. The awardee must obtain written approval from the cognizant NSF Grants and Agreements Officer prior to entering into a contract if the amount exceeds $250,000 or other amount specifically identified in the agreement. Contracts clearly identified in the NSF award budget are considered approved at the time of award unless approval is withheld by the Grants and Agreements Officer. Contracts must be clearly identified in the NSF award budget on Line G6. Other. The threshold noted above also applies to cumulative increases in the value of the contractual arrangement after initial NSF approval. The awardee must not artificially segregate its procurements to lesser dollar amounts for the purpose of circumventing this requirement. A request to enter into a contract must include, at a minimum:
Customer Requirements ▪ Seller shall comply with the applicable terms and conditions of any agreements between Buyer and Xxxxx’s Customer (the “Customer Purchase Orders”) pursuant to which Buyer agreed to sell to Buyer’s Customer products or assemblies which incorporate the goods provided by Seller hereunder. This provision specifically includes costs and obligations imposed by warranty programs instituted by the original equipment manufacturer that ultimately purchases Buyer’s products that incorporate the goods sold by Seller if applicable to Buyer under the terms of the Customer Purchase Order. ▪ If Buyer is not acting as a Tier One supplier, the defined term “Customer Purchase Order” shall also include the terms and conditions of the original equipment manufacturer that ultimately purchases Buyer’s product that incorporates the goods or services sold by Seller. ▪ Seller will be responsible to ascertain how the disclosed terms affect Seller’s performance under the Purchase Order. ▪ By written notice to Seller, Buyer may elect to disclose and have the provisions of the Customer’s Purchase Orders prevail over any term of the Purchase Order at any time.
Minimum System Requirements The following summarizes the minimum office system requirements for all Contractors and Architect/Engineer to possess in order to participate. It is the responsibility of all Contractors and Architect/Engineer to possess these minimum requirements at no additional cost to Princeton University.
