Computer Requirements You are responsible for obtaining, installing, maintaining and operating all software, hardware, or other equipment necessary (collectively, “Access Device Systems”) necessary for you to access and use the Service. This responsibility includes, without limitation, your utilizing up to date web-browsers and Access Devices and the best commercially available encryption, antivirus, anti-spyware, and Internet security software. You are additionally responsible for obtaining Internet service via an Internet service provider of your choice, for any and all fees imposed by such Internet service provider, and any associated communications service provider charges. You acknowledge that there are certain security, corruption, transmission error and access availability risks associated with using open networks such as the Internet and you hereby expressly assume such risk, including, but not limited to those we may disclose in our educational materials. You acknowledge that you are responsible for data security of the Systems used to access the Service, and for the transmission and receipt of information using such System. You acknowledge that you have requested the Service for your convenience, have made your own independent assessment of the adequacy of the Internet and Systems and that you are satisfied with that assessment. The Bank shall have no responsibility for failures, interruption or other defects in the Services, which arise from the malfunction or failure of the Internet or your Systems nor are we responsible for notifying you of any upgrades, fixes, or enhancements to, or for providing technical or other support for your Systems. The Bank may add to, modify, or replace software programs used in conjunction with providing the Services under this Agreement at its sole discretion and without notice, provided Services rendered to you are not substantially negatively affected or obligations altered.
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.
System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.
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:
E-Verify Requirements To the extent applicable under ARIZ. REV. STAT. § 41- 4401, the Contractor and its subcontractors warrant compliance with all federal immigration laws and regulations that relate to their employees and their compliance with the E-verify requirements under ARIZ. REV. STAT. § 23-214(A). Contractor’s or its subcontractor’s failure to comply with such warranty shall be deemed a material breach of this Agreement and may result in the termination of this Agreement by the City.
Match Requirements There is no match required on the part of the Grantee under this Agreement.
Other Requirements AVIF will require that each Participating Insurance Company and Participating Plan enter into an agreement with AVIF that contains in substance the same provisions as are set forth in Sections 4.1(b), 4.1(d), 4.3(a), 4.4(b), 4.5(a), 5, and 10 of this Agreement.
PJM Requirements The DS Supplier acknowledges and agrees that, as a member of PJM, the Company is bound by all PJM operating instructions, policies and procedures as are currently set forth in the PJM Operating Manual, which are available through the Internet on the PJM Home Page (xxxx://xxx.xxx.xxx), as may be revised from time to time, which are needed to maintain the integrity of the PJM system. The DS Supplier acknowledges and agrees that it will cooperate with the Company so that the Company will be in compliance with all PJM Emergency Operations Procedures, which include, but are not limited to, those procedures pertaining to minimum and maximum generation Emergencies, and measures requiring involuntary Customer participation, such as supply voltage reduction or full interruption of Customer load by either manual or automatic means.
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.
City Requirements Design, construction, materials, sizing, other specifications, permitting, inspections, testing, documentation and furnishing of as-built drawings, and acceptance of completed infrastructure shall be in accordance with City Requirements. Design and construction shall be by professionals licensed in the state of North Carolina to do the relevant work. City approval of the design of the Improvements shall be required prior to construction, as set forth in City Requirements. If Developer is connecting to the County sewer system, the City may require Developer to furnish the contract providing for such connection.
