Financial and Compliance Audit Requirements Sample Clauses

Financial and Compliance Audit Requirements. [Intentionally Left Blank – Not applicable to this D-SNP Contract]
Sample 1Sample 2Sample 3See All (4)
AutoNDA by SimpleDocs
Financial and Compliance Audit Requirements. By signing this Agreement, the Contractor/Subcontrac tor agrees to abide by all requirements specified in 2 CFR 200, et seq., 2 CFR 400, et seq., and 45 CFR, 75, et seq., as applicable, including but not limited to obtaining an annual audit, and any subsequent federal regulatory additions or revisions.
Sample 1Sample 2Sample 3
Financial and Compliance Audit Requirements a. The definitions used in this provision are contained in Section 38040 of the Health and Safety Code, which by this reference is made a part hereof.
Sample 1Sample 2
Financial and Compliance Audit Requirements. 17. Human Subjects Use Requirements CMS 02 Page 1 of 26 $1 Federal Equal Opportunity Requirements (Applicable to all federally funded agreements.) 0330
Sample 1
Financial and Compliance Audit Requirements. [Intentionally Left Blank – Not applicable to this D-SNP Contract] 17. Human Subjects Use Requirements By signing this D-SNP Contract, D-SNP Contractor agrees that if any performance under this D-SNP Contract includes any tests or examination of materials derived from the human body for the purpose of providing information, diagnosis, prevention, treatment or assessment of disease, impairment, or health of a human being, all locations at which such examinations are performed shall meet the requirements of 42 USC 263a (CLIA) and the regulations thereto.
Sample 1
Financial and Compliance Audit Requirements. 0247 Exhibit
Sample 1
Financial and Compliance Audit Requirements. A. Paragraph d of provision 16 in Exhibit D(F) is amended to read as follows: The A-133 audit report must either include the PHEP, HPP and State General Fund Pandemic Influenza programs (as applicable to the contractor) at a minimum once every three years or a separate independent audit of these programs must be conducted according to the requirements specified in OMB Circular A-133 entitled “Audits of States, Local Governments, and Non-Profit Organizations” at least once every three years. If an audit of the PHEP, HPP and State General Fund Pandemic Influenza programs has not been completed within the past two years from the date of this Agreement, an audit of the funds awarded for the period of July 1, 2012 through June 30, 2013 must be conducted and concluded no later than July 1, 2014, or according to the County schedule for the A-133 audit for this 2012-13 fiscal period (July 1, 2012 through June 30, 2013) if PHEP, HPP and State GF Pandemic Influenza funds are included in the A-133 Audit. In addition, the A-133 or other independent audit must identify the Contractor’s legal name and the number assigned to this Agreement and be sent annually to CDPH within 30 days after the completion of the audit. The LHD/HPP Entity shall keep a copy of the audit report on file and have it available for review by CDPH or auditors upon request. Page 24 of 41 Page 28 of 41 Page 34 of 41 ATTEST XXXXXX X. XXXXXX, Clerk of said Board By Deputy Page 40 of 41 County of Mendocino 2013-14 Agreement No. EPO 13-25 EXHIBIT E 2013-14 Public Health Emergency Preparedness (PHEP), General Fund Pandemic Influenza (GF Pan Flu) and Hospital Preparedness Program (HPP) Funding NON-SUPPLANTATION CERTIFICATION FORM (City/County Name of Local Health Department and/or Local HPP Entity) I hereby certify that the above-named Local Health Department (LHD) and/or Local HPP Entity shall not use funds allocated by the California Department of Public Health (CDPH) to supplant funding for existing levels of service and that funds shall only be used for the purposes specified in the Fiscal Year (FY) 2013-2014 PHEP, GF Pan Flu, and HPP Funding Agreement as approved by the CDPH. I further certify that funds received shall be deposited in an interest-bearing Local Public Health Preparedness Trust Fund as per the Health and Safety Code, Section 101317 and expended only for the purposes stated in the LHDs and/or Local HPP Entity’s Grant Application Work Plan and Budget, as approved by the CDPH. Chairperson...
Sample 1
AutoNDA by SimpleDocs

Related to Financial and Compliance Audit Requirements

  • Compliance Requirements K. If using volunteers as provided for in this Contract during FY19, which encompasses the Contract term of July 1, 2019 to June 30, 2020, then the Grantee must either:

  • Performance or Compliance Audits The Department may conduct or have conducted performance and/or compliance audits of the Contractor and subcontractors as determined by the Department. The Department may conduct an audit and review all the Contractor’s and subcontractors’ data and records that directly relate to the Contract. To the extent necessary to verify the Contractor’s fees and claims for payment under the Contract, the Contractor’s agreements or contracts with subcontractors, partners, or agents of the Contractor, pertaining to the Contract, may be inspected by the Department upon fifteen (15) calendar days’ notice, during normal working hours and in accordance with the Contractor’s facility access procedures where facility access is required. Release statements from its subcontractors, partners, or agents are not required for the Department or its designee to conduct compliance and performance audits on any of the Contractor’s contracts relating to this Contract. The Inspector General, in accordance with section 5.6, the State of Florida’s Chief Financial Officer, the Office of the Auditor General also have authority to perform audits and inspections.

  • Standards Compliance DNS. Registry Operator shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF), including all successor standards, modifications or additions thereto relating to the DNS and name server operations including without limitation RFCs 1034, 1035, 1123, 1982, 2181, 2182, 2671, 3226, 3596, 3597, 4343, and 5966. DNS labels may only include hyphens in the third and fourth position if they represent valid IDNs (as specified above) in their ASCII encoding (e.g., “xn--ndk061n”).

Time is Money Join Law Insider Premium to draft better contracts faster.