Specific requirements concerning the organisation of the Services
Specific requirements concerning Sample Clauses
Related to Specific requirements concerning
REQUIREMENTS CONTRACT This is a Requirements Contract and the County’s intent is to order from the Contractor all of the goods or services specified in the contract’s price schedule that are required to be purchased by the County. If the County urgently requires delivery of goods or services before the earliest date that delivery may be required under this contract, and if the contractor will not accept an order providing for accelerated delivery, the County may acquire the goods or services from another source. The County’s requirements in this contract are estimated and there is no commitment by the County to order any specified amount. If the estimated quantities are not achieved, this shall not be the basis for an equitable adjustment.
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.
FALSE STATEMENTS CONCERNING HIGHWAY PROJECTS T h i s p r o v i s i o n i s applicable to all Federal-aid construction contracts and to all related subcontracts. In order to assure high quality and durable construction in conformity with approved plans and specifications and a high degree of reliability on statements and representations made by engineers, contractors, suppliers, and workers on Federal- aid highway projects, it is essential that all persons concerned with the project perform their functions as carefully, thoroughly, and honestly as possible. Willful falsification, distortion, or misrepresentation with respect to any facts related to the project is a violation of Federal law. To prevent any misunderstanding regarding the seriousness of these and similar acts, Form FHWA-1022 shall be posted on each Federal-aid highway project (23 CFR 635) in one or more places where it is readily available to all persons concerned with the project: 18 U.S.C. 1020 reads as follows: "Whoever, being an officer, agent, or employee of the United States, or of any State or Territory, or whoever, whether a person, association, firm, or corporation, knowingly makes any false statement, false representation, or false report as to the character, quality, quantity, or cost of the material used or to be used, or the quantity or quality of the work performed or to be performed, or the cost thereof in connection with the submission of plans, maps, specifications, contracts, or costs of construction on any highway or related project submitted for approval to the Secretary of Transportation; or Whoever knowingly makes any false statement, false representation, false report or false claim with respect to the character, quality, quantity, or cost of any work performed or to be performed, or materials furnished or to be furnished, in connection with the construction of any highway or related project approved by the Secretary of Transportation; or Whoever knowingly makes any false statement or false representation as to material fact in any statement, certificate, or report submitted pursuant to provisions of the Federal-aid Roads Act approved July 1, 1916, (39 Stat. 355), as amended and supplemented; Shall be fined under this title or imprisoned not more than 5 years or both."
Agreements, Conditions and Covenants The Purchaser shall have performed or complied with all agreements, conditions and covenants required by this Agreement to be performed or complied with by it on or before the Closing.
Federal Medicaid System Security Requirements Compliance Party shall provide a security plan, risk assessment, and security controls review document within three months of the start date of this Agreement (and update it annually thereafter) in order to support audit compliance with 45 CFR 95.621 subpart F, ADP System Security Requirements and Review Process.
Basic Requirements To be eligible for PayPal’s Seller Protection program, all of the following basic requirements must be met, as well as any applicable additional requirements: • The primary address for your PayPal account must be in the United States. • The item must be a physical, tangible good that can be shipped, except for items subject to the Intangible Goods Additional Requirements. Transactions involving items that you deliver in person in connection with payment made in your physical store, may also be eligible for PayPal’s Seller Protection program so long as the buyer paid for the transaction in person by using a PayPal goods and services QR code. • You must ship the item to the shipping address on the Transaction Details page in your PayPal account for the transaction. If you originally ship the item to the recipient’s shipping address on the Transaction Details page but the item is later redirected to a different address, you will not be eligible for PayPal’s Seller Protection program. We therefore recommend not using a shipping service that is arranged by the buyer, so that you will be able to provide valid proof of shipping and delivery. • The shipping requirement does not apply to eligible transactions involving items that you deliver in person; provided, however, that you agree to provide us with alternative evidence of delivery or such additional documentation or information relating to the transaction that we may request. • You must respond to PayPal’s requests for documentation and other information in a timely manner as requested in our email correspondence with you or in our correspondence with you through the Resolution Center. If you do not respond to PayPal’s request for documentation and other information in the time requested, you may not be eligible for PayPal’s Seller Protection program. • If the sale involves pre-ordered or made-to-order goods, you must ship within the timeframe you specified in the listing. Otherwise, it is recommended that you ship all items within 7 days after receipt of payment. • You provide us with valid proof of shipment or delivery. • The payment must be marked “eligible” or “partially eligible” in the case of Unauthorized Transaction claims, or “eligible” in the case of Item Not Received claims, for PayPal’s Seller Protection program on the Transaction Details page. • In the case of an Unauthorized Transaction claim, you must provide valid proof of shipment or proof of delivery that demonstrates that the item was shipped or provided to the buyer no later than two days after PayPal notified you of the dispute or reversal. For example, if PayPal notifies you of an Unauthorized Transaction claim on September 1, the valid proof of shipment must indicate that the item was shipped to the buyer no later than September 3 to be eligible for PayPal’s Seller Protection program. PayPal determines, in its sole discretion, whether your claim is eligible for PayPal’s Seller Protection program. PayPal will make a decision, in its sole discretion, based on the eligibility requirements, any information or documentation provided during the resolution process, or any other information PayPal deems relevant and appropriate under the circumstances. To be eligible for PayPal’s Seller Protection program for a buyer’s Item Not Received claim, you must meet both the basic requirements and the additional requirements listed below: • Where a buyer files a chargeback with the issuer for a card-funded transaction, the payment must be marked “eligible” for PayPal’s Seller Protection on the Transaction Details page. • You must provide proof of delivery as described below.
Amendments; Construction The Administrator may amend the terms of this Restricted Share Agreement prospectively or retroactively at any time, but no such amendment shall impair the rights of the Participant hereunder without his or her consent. To the extent the terms of Section 12 above conflict with any prior agreement between the parties related to such subject matter, the more restrictive provision shall be deemed to apply. Headings to Sections of this Restricted Share Agreement are intended for convenience of reference only, are not part of this Restricted Share Agreement and shall have no effect on the interpretation hereof.
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.
Design Requirements The DG Facility shall be installed in compliance with Wisconsin Administrative Code Chapter PSC 119.
Training Requirements Grantee shall: A. Authorize and require staff (including volunteers) to attend training, conferences, and meetings as directed by DSHS; B. Appropriately budget funds in order to meet training requirements in a timely manner, and ensure that staff and volunteers are trained as specified in the training requirements listed at xxxxx://xxx.xxxx.xxxxx.xxx/hivstd/training/ and as otherwise specified by DSHS. Grantee shall document that these training requirements are met; and C. Ensure that staff hired for HIV and syphilis testing are trained to perform blood draws within three (3) months of employment.
