Software Requirements 7 Developer shall prepare the Project Schedule using Oracle’s Primavera P6.
Time Requirements The Independent Contractor will not be required to follow or establish a regular or daily work schedule, but shall devote during the term of this Agreement the time, energy and skill as necessary to perform the services of this engagement and shall, periodically or at any time upon the request of the Company, submit information as to the amount of time worked and scope of work performed.
Interface Requirements 2.4.5.1 The NID shall be equal to or better than all of the requirements for NIDs set forth in the applicable industry standard technical references.
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.
Vehicle Requirements The following shall be considered minimum Vehicle requirements. The Authorized User shall include supplemental required specifications for Vehicles specified in a Mini-Bid. Unless otherwise indicated, all items specified which are listed on the OEM Pricelist as standard or optional equipment shall be factory installed and operative. Vehicles delivered to an Authorized User in a condition considered to be below retail customer acceptance levels will not be accepted. Items which determine this acceptance level shall include, but not be limited to, the general appearance of the interior and exterior of the vehicle for completeness and quality of workmanship, lubrication and fluid levels, with any leaks corrected, mechanical operation of the vehicle and all electrical components operational. Product specified to be furnished and installed which is not available through the OEM shall conform to the standards known to that particular industry, both product and installation.
Disclosure Requirements (a) The Estate Agent or Salesperson *has / does not have(1) (11) a conflict or potential conflict of interest in acting for the Tenant. If the Estate Agent or Salesperson has a conflict or potential conflict of interest, the details are as follows: (b) If the Estate Agent or Salesperson has declared that there is no conflict or potential conflict of interest but a conflict or potential conflict of interest only arises (or he becomes aware of the conflict or potential conflict of interest) after the execution of this Agreement, the conflict or potential conflict of interest must be immediately disclosed in writing to the Tenant. Upon such disclosure, the Estate Agent and Salesperson may continue to act for the Tenant only if the Tenant, being fully informed, consents in writing to the Estate Agent and Salesperson continuing to act for him.
Diligence Requirements Company shall use diligent efforts or shall cause its Affiliates or Sublicensees to use diligent efforts to develop Licensed Products and to introduce Licensed Products into the commercial market; thereafter, Company or its Affiliates or Sublicensees shall make Licensed Products reasonably available to the public. Specifically, Company or its Affiliates or Sublicensees shall fulfill the following obligations: (a) Within ninety (90) days after the Effective Date, Company shall furnish Medical School with a written research and development plan under which Company intends to develop Licensed Products. (b) Within sixty (60) days after each anniversary of the Effective Date, Company shall furnish Medical School with a written report on the progress of its efforts during the prior year to develop and commercialize Licensed Products, including without limitation research and development efforts, efforts to obtain regulatory approval, marketing efforts, and sales figures. The report shall also contain a discussion of intended efforts and sales projections for the current year. (c) Company shall endeavor to obtain all necessary governmental approvals for the manufacture, use and sale of Combination Product and Licensed Product. Specifically, Company shall: (i) Within eight (8) years after the Effective Date, file an Investigational New Drug Application (“IND”) or its equivalent covering at least one Combination Product or Licensed Product with the U.S. Food and Drug Administration (“FDA”); (ii) Within thirteen (13) years after the Effective Date, file a New Drug Application (“NDA”) with the FDA covering at least one Combination Product or Licensed Product; (iii) Within eighteen (18) months after receiving FDA approval of the NDA for a Combination Product or Licensed Product, market at least one Combination Product or Licensed Product in the U.S.; and (iv) reasonably fill the market demand for any Combination Product or Licensed Product following commencement of marketing of such product at any time during the exclusive period of this Agreement. (d) Within eighteen (18) months after the Effective Date, Company shall successfully undertake a public or private offering of raising ten million dollars ($10,000,000). (e) In addition to the obligations set forth above, Company or its Affiliates or Sublicensees shall spend (either directly or through sponsored research by Company or its Affiliates or Sublicensees at the Medical School) an aggregate of not less than {***} per calendar year for the development of Combination Product and/or Licensed Product commencing with the year 2004. Company shall have the responsibility to finance its obligations in this Section 3.1, and the Medical School shall provide reasonable cooperation to Company in this regard. In the event that Medical School determines that Company (or an Affiliate or Sublicensee) has not fulfilled its obligations under this Section 3.1., Medical School shall furnish Company with written notice of such determination. Within sixty (60) days after receipt of such notice, Company shall either (i) fulfill the relevant obligation or (ii) negotiate with Medical School a mutually acceptable schedule of revised diligence obligations, failing which Medical School shall have the right, immediately upon written notice to Company, to terminate this Agreement.
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.
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:
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.
