Lessee's Compliance with Applicable Requirements Except as otherwise provided in this Lease, Lessee shall, at Lessee's sole expense, fully, diligently and in a timely manner, materially comply with all Applicable Requirements, the requirements of any applicable fire insurance underwriter or rating bureau, and the recommendations of Lessor's engineers and/or consultants which relate in any manner to the Premises, without regard to whether said requirements are now in effect or become effective after the Start Date. Lessee shall, within ten (10) days after receipt of Lessor's written request, provide Lessor with copies of all permits and other documents, and other information evidencing Lessee's compliance with any Applicable Requirements specified by Lessor, and shall immediately upon receipt, notify Lessor in writing (with copies of any documents involved) of any threatened or actual claim, notice, citation, warning, complaint or report pertaining to or involving the failure of Lessee or the Premises to comply with any Applicable Requirements.
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.
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.
Response/Compliance with Audit or Inspection Findings A. Grantee must act to ensure its and its Subcontractors’ compliance with all corrections necessary to address any finding of noncompliance with any law, regulation, audit requirement, or generally accepted accounting principle, or any other deficiency identified in any audit, review, inspection or investigation of the Grant Agreement and the services and Deliverables provided. Any such correction will be at Grantee’s or its Subcontractor's sole expense. Whether Xxxxxxx's action corrects the noncompliance shall be solely the decision of the System Agency.
B. As part of the services, Grantee must provide to HHS upon request a copy of those portions of Grantee's and its Subcontractors' internal audit reports relating to the services and Deliverables provided to the State under the Grant Agreement.
C. Grantee shall include the requirement to provide to System Agency (and any of its duly authorized federal, state, or local authorities) internal audit reports related to this Grant Agreement in any Subcontract it awards. Upon request by System Agency, Grantee shall enforce this requirement against its Subcontractor. Further, Grantee shall include in any Subcontract it awards a requirement that all Subcontractor Subcontracts must also include these provisions.
Compliance with Applicable Requirements In carrying out its obligations under this Agreement, the Sub-Adviser shall at all times comply with:
(a) all applicable provisions of the 1940 Act, and any rules and regulations adopted thereunder;
(b) the provisions of the registration statement of the Trust, as it may be amended or supplemented from time to time, under the Securities Act and the 1940 Act;
(c) the provisions of the Declaration of Trust of the Trust, as it may be amended or supplemented from time to time;
(d) the provisions of any By-laws of the Trust, if adopted and as it may be amended from time to time, or resolutions of the Board as may be adopted from time to time;
(e) the provisions of the Internal Revenue Code of 1986, as amended, applicable to the Trust or the Funds;
(f) any other applicable provisions of state or federal law; and In addition, any code of ethics adopted by the Sub-Adviser must comply with Rule 17j-1 under the 1940 Act, as it may be amended from time to time, and any broadly accepted industry practices, if requested by the Trust or the Adviser.
System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.
Access Requirements You will be responsible for providing the System to enable you to use an Electronic Service.
Maintenance Requirements The Contractor shall ensure and procure that at all times during the Maintenance Period, the Project Highway conforms to the maintenance requirements set forth in Schedule-E (the “Maintenance Requirements”).
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.
