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.
Regulatory Requirements Each Party’s obligations under this Agreement shall be subject to its receipt of any required approval or certificate from one or more Governmental Authorities in the form and substance satisfactory to the applying Party, or the Party making any required filings with, or providing notice to, such Governmental Authorities, and the expiration of any time period associated therewith. Each Party shall in good faith seek and use its Reasonable Efforts to obtain such other approvals. Nothing in this Agreement shall require Developer to take any action that could result in its inability to obtain, or its loss of, status or exemption under the Federal Power Act or the Public Utility Holding Company Act of 2005 or the Public Utility Regulatory Policies Act of 1978, as amended.
Compliance with Regulatory Requirements Upon demand by Lender, Borrower shall reimburse Lender for Lender’s additional costs and/or reductions in the amount of principal or interest received or receivable by Lender if at any time after the date of this Agreement any law, treaty or regulation or any change in any law, treaty or regulation or the interpretation thereof by any Governmental Authority charged with the administration thereof or any other authority having jurisdiction over Lender or the Loans, whether or not having the force of law, shall impose, modify or deem applicable any reserve and/or special deposit requirement against or in respect of assets held by or deposits in or for the account of the Loans by Lender or impose on Lender any other condition with respect to this Agreement or the Loans, the result of which is to either increase the cost to Lender of making or maintaining the Loans or to reduce the amount of principal or interest received or receivable by Lender with respect to such Loans. Said additional costs and/or reductions will be those which directly result from the imposition of such requirement or condition on the making or maintaining of such Loans.
Tax Requirements The Participant is hereby advised to consult immediately with his or her own tax advisor regarding the tax consequences of this Agreement. The Company or, if applicable, any Subsidiary (for purposes of this Section 28, the term “Company” shall be deemed to include any applicable Subsidiary), shall have the right to deduct from all amounts hereunder paid in cash or other form, any Federal, state, local, or other taxes required by law to be withheld in connection with this Award. The Company may, in its sole discretion, also require the Participant receiving shares of Common Stock issued under the Plan to pay the Company the amount of any taxes that the Company is required to withhold in connection with the Participant’s income arising with respect to this Award. Such payments shall be required to be made when requested by the Company and may be required to be made prior to the delivery of any certificate representing shares of Common Stock. Such payment may be made (i) by the delivery of cash to the Company in an amount that equals or exceeds (to avoid the issuance of fractional shares under (iii) below) the required tax withholding obligations of the Company; (ii) if the Company, in its sole discretion, so consents in writing, the actual delivery by the exercising Participant to the Company of shares of Common Stock other than (A) Restricted Stock, or (B) Common Stock that the Participant has not acquired from the Company within six (6) months prior to the date of exercise, which shares so delivered have an aggregate Fair Market Value that equals or exceeds (to avoid the issuance of fractional shares under (iii) below) the required tax withholding payment; (iii) if the Company, in its sole discretion, so consents in writing, the Company’s withholding of a number of shares to be delivered upon the exercise of the Stock Option other than shares that will constitute Restricted Stock, which shares so withheld have an aggregate fair market value that equals (but does not exceed) the required tax withholding payment; or (iv) any combination of (i), (ii), or (iii). The Company may, in its sole discretion, withhold any such taxes from any other cash remuneration otherwise paid by the Company to the Participant.
Regulatory Requirements and Governing Law 43 14.1 Regulatory Requirements. 43 14.2 Governing Law 44 ARTICLE 15. NOTICES 44 15.1 General. 44 15.2 Xxxxxxxx and Payments. 44 15.3 Alternative Forms of Notice 44 15.4 Operations and Maintenance Notice 44 ARTICLE 16. FORCE MAJEURE 45 16.1 Force Majeure 45 ARTICLE 17. DEFAULT 45 17.1 Default. 45 ARTICLE 18. INDEMNITY, CONSEQUENTIAL DAMAGES AND INSURANCE 46 18.1 Indemnity. 46 18.2 No Consequential Damages. 47 18.3 Insurance 47 ARTICLE 19. ASSIGNMENT 49 19.1 Assignment. 49 ARTICLE 20. SEVERABILITY 49 20.1 Severability. 49 ARTICLE 21. COMPARABILITY 50 21.1 Comparability. 50 ARTICLE 22. CONFIDENTIALITY 50 22.1 Confidentiality. 50 ARTICLE 23. ENVIRONMENTAL RELEASES 53 23.1 Developer and Connecting Transmission Owner Notice 53 ARTICLE 24. INFORMATION REQUIREMENT 53 24.1 Information Acquisition. 53 24.2 Information Submission by Connecting Transmission Owner 54 24.3 Updated Information Submission by Developer 54 24.4 Information Supplementation 54 ARTICLE 25. INFORMATION ACCESS AND AUDIT RIGHTS 55 25.1 Information Access. 55 25.2 Reporting of Non-Force Majeure Events. 55 25.3 Audit Rights. 56 25.4 Audit Rights Periods. 56 25.5 Audit Results. 56 ARTICLE 26. SUBCONTRACTORS 56 26.1 General. 56 26.2 Responsibility of Principal. 57 26.3 No Limitation by Insurance 57 ARTICLE 27. DISPUTES 57 27.1 Submission 57 27.2 External Arbitration Procedures. 57 27.3 Arbitration Decisions. 58 27.4 Costs. 58 27.5 Termination 58 ARTICLE 28. REPRESENTATIONS, WARRANTIES AND COVENANTS 58 28.1 General. 58 ARTICLE 29. MISCELLANEOUS 59 29.1 Binding Effect. 59 29.2 Conflicts. 59 29.3 Rules of Interpretation 59 29.4 Compliance 60 29.5 Joint and Several Obligations. 60 29.6 Entire Agreement. 60 29.7 No Third Party Beneficiaries. 60 29.8 Waiver 60 29.9 Headings. 61 29.10 Multiple Counterparts. 61 29.11 Amendment. 61 29.12 Modification by the Parties. 61 29.13 Reservation of Rights. 61 29.14 No Partnership 62 29.15 Other Transmission Rights. 62 Appendices STANDARD LARGE GENERATOR INTERCONNECTION AGREEMENT THIS STANDARD LARGE GENERATOR INTERCONNECTION AGREEMENT
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.
W-9 Requirement Alongside a signed copy of this Agreement, Grantee will provide Florida Housing with a properly completed Internal Revenue Service (“IRS”) Form W-9. The purpose of the W-9 form is to document the SS# or FEIN# per the IRS. Note: W-9s submitted for any other entity name other than the Grantee’s will not be accepted.
Procedural and Operational Requirements By accepting and using the Financial Assistance awarded under this Agreement and for this Program Element, LPHA agrees to conduct the following activities in accordance with the indicated procedural and operational requirements: a. LPHA must operate its Communicable Disease program in accordance with the Requirements and Standards for the Control of Communicable Disease set forth in ORS Chapters 431, 432, 433 and 437 and OAR Chapter 333, Divisions 12, 17, 18, 19 and 24, as such statutes and rules may be amended from time to time. b. LPHA must use all reasonable means to investigate in a timely manner all reports of Reportable Diseases, infections, or conditions. To identify possible sources of infection and to carry out appropriate control measures, the LPHA Administrator shall investigate each report following procedures outlined in OHA’s Investigative Guidelines or other procedures approved by OHA. OHA may provide assistance in these investigations, in accordance with OAR 333-019-0000. Investigative guidelines are available at: xxxx://xxx.xxxxxx.xxx/oha/PH/DiseasesConditions/CommunicableDisease/ReportingCommuni cableDisease/ReportingGuidelines/Pages/index.aspx c. As part of its Communicable Disease control program, LPHA must, within its service area, investigate the Outbreaks of Communicable Diseases, institute appropriate Communicable Disease control measures, and submit required information in a timely manner regarding the Outbreak to OHA in Orpheus (or Opera for COVID-19 Cases and XXXXX for COVID-19 contacts) as prescribed in OHA CD Investigative Guidelines available at: d. LPHA must establish and maintain a single telephone number whereby physicians, hospitals, other health care providers, OHA and the public can report Communicable Diseases and Outbreaks to LPHA 24 hours a day, 365 days a year. LPHA may employ an answering service or 911 system, but the ten-digit number must be available to callers from outside the local emergency dispatch area, and LPHA must respond to and investigate reported Communicable Diseases and Outbreaks. e. LPHA must attend Communicable Disease 101 and Communicable Disease 303 training. f. LPHA must attend monthly Orpheus user group meetings or monthly Orpheus training webinars.
Requirements At its own expense, Supplier must maintain insurance policy(ies) in effect at all times during the performance of this Contract with insurance company(ies) licensed or authorized to do business in the State of Minnesota having an “AM BEST” rating of A- or better, with coverage and limits of insurance not less than the following:
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.
