Requirements Overview. The Operations Orders must:

Requirements Overview. 1. Proposer is responsible for understanding and complying with all requirements of the RFP. Proposer shall ensure all subcontractors understand and comply with all requirements of the RFP. 2. Proposer and all subcontractors shall agree to abide by the medical treatment pricing guidelines in the California Labor section 5307.1 and in Title 8, California Code of Regulations, Article 5.3, Official Medical Fee Schedule (OFMS), and Article 5.5, Application of the Official Medical Fee Schedule (Treatment). Increases or decreases to fees covered by the above statutes shall occur during the contract period only when the State provides an increase or decrease in fee(s) or when non-fee scheduled services are pre-negotiated and approved by the City. 3. All Proposer services shall, at a minimum, meet the requirements of the Code of Federal Regulations, Cal/OSHA, and National Institute for Occupational Safety and Health. 4. Proposer shall submit their medical records retention and confidentiality policies and procedures with proposal. All policies and procedures must conform to all applicable laws, rules, and regulations. 5. Proposer shall arrange to provide the following for industrially injured City employees. Please note: The City wishes to achieve best market value. Proposer shall provide their best pricing offer for each of the listed services, using the fees outlined in the State of California’s OFMS as a guideline:

Requirements Overview. The OneHSN Childcare™ - Integrated Childcare Application and Waitlist Manager (formerly known as ONELIST) offers the following features:

Requirements Overview. 1. LabWare will transmit messages in a human-readable format that should be ‘captured’ and translated into Clarity-specific XML via processes managed by Mirth. 2. Mirth will them submit the XML to Clarity’s REST-based API, and cause the sample to be created within Clarity 3. When an assay has been completed, Clarity will generate a message that will be sent to Mirth / LabWare to indicate that the test sequencing is complete. These ?? will contain basic information; no PHI, no diagnostic information.

Requirements Overview. This workflow step describes all aspects of data management and user management.

Requirements Overview. This workflow step describes the selection process. Everybody agreed that all of this is going to take place in the CMS, so these are not functional requirements for the XXX.

Related to Requirements Overview

E-Verify Compliance The contractor represents and covenants that the contractor and its subcontractors comply with the requirements of Article 2 of Chapter 64 of the North Carolina General Statutes (NCGS). The City is relying on this E-Verify Compliance section in entering into this contract. The parties agree to this section only to the extent authorized by law. If this section is held to be unenforceable or invalid in whole or in part, it shall be deemed amended to the extent necessary to make this contract comply with NCGS 160A-20.1(b).
Compliance Requirements A. Nondiscrimination. The Contractor agrees to comply, and to require its subcontractor(s) to comply, with the nondiscrimination provisions of MCL 37.2209. The Contractor further agrees to comply with the provisions of Section 9:158 of Chapter 112 of the Xxx Arbor City Code and to assure that applicants are employed and that employees are treated during employment in a manner which provides equal employment opportunity.
GAAP Compliance Contractor maintains an adequate system of accounting and internal controls that meets Generally Accepted Accounting Principles.
General Compliance This Agreement is intended to comply with Section 409A or an exemption thereunder and shall be construed and administered in accordance with Section 409A. Notwithstanding any other provision of this Agreement, payments provided under this Agreement may only be made upon an event and in a manner that complies with Section 409A or an applicable exemption. Any payments under this Agreement that may be excluded from Section 409A either as separation pay due to an involuntary separation from service or as a short-term deferral shall be excluded from Section 409A to the maximum extent possible. For purposes of Section 409A, each installment payment provided under this Agreement shall be treated as a separate payment. Any payments to be made under this Agreement upon a termination of employment shall only be made upon a “separation from service” under Section 409A. Notwithstanding the foregoing, the Company makes no representations that the payments and benefits provided under this Agreement comply with Section 409A, and in no event shall the Company be liable for all or any portion of any taxes, penalties, interest, or other expenses that may be incurred by the Executive on account of non-compliance with Section 409A.
Program Requirements The parties shall comply with the Disadvantaged Business Enterprise Program requirements established in 49 CFR Part 26.
CONTRACT COMPLIANCE REQUIREMENT The HUB requirement on this Contract is 0%. The student engagement requirement of this Contract is 0 hours. The Career Education requirement for this Contract is 0 hours. Failure to achieve these requirements may result in the application of some or all of the sanctions set forth in Administrative Policy 3.10, which is hereby incorporated by reference.
FERPA Compliance In connection with all FERPA Records that Contractor may create, receive or maintain on behalf of University pursuant to the Underlying Agreement, Contractor is designated as a University Official with a legitimate educational interest in and with respect to such FERPA Records, only to the extent to which Contractor (a) is required to create, receive or maintain FERPA Records to carry out the Underlying Agreement, and (b) understands and agrees to all of the following terms and conditions without reservation:
System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.
Listing and Maintenance Requirements Compliance The Company has not in the two years preceding the date hereof received written notice from any stock exchange, market or trading facility on which the Common Stock is or has been listed or quoted to the effect that the Company is not in compliance with the listing, maintenance or other requirements of such exchange, market, trading or quotation facility. The Company has no reason to believe that it does not now or will not in the future meet any such requirements.
OSHA Compliance To the extent applicable to the services to be performed under this Agreement, Contractor represents and warrants, that all articles and services furnished under this Agreement meet or exceed the safety standards established and promulgated under the Federal Occupational Safety and Health Law (Public Law 91-596) and its regulations in effect or proposed as of the date of this Agreement.

Requirements Overview Sample Clauses

Filter & Search

Related Clauses

Parent Clauses

Sub-Clauses

Related to Requirements Overview