OPEN RECORDS REQUIREMENTS Sample Clauses

OPEN RECORDS REQUIREMENTS. (a) All project−related re- cords are subject to the state’s open records law. (b) The grantee shall keep any confidential information that is not subject to the open records law, such as social security num- bers that is required for income tax purposes for the cost−share funding, safe from unauthorized access. (1) Grantees shall report to the department an annual accounting for accomplishments regarding its activities funded under the grant. (2) The department may require more frequent reports than those required under sub. (1) from a grantee which document ac- complishments regarding activities funded under the grant. (3) The grantee shall submit a final report after project com- pletion. At a minimum, the report shall include project evaluation and monitoring information consistent with the commitments made in the project application submitted under s. NR 155.17. The department may require the grantee to submit other information in the final report. History: CR 00−025: cr. Register September 2002 No. 561, eff. 10−1−02.
Sample 1Sample 2Sample 3See All (7)
AutoNDA by SimpleDocs
OPEN RECORDS REQUIREMENTS. (a) All project−related records are subject to the state’s open records law. (b) The grantee will keep any confidential information that is not subject to the open records law, such as social security num- bers that is required for income tax purposes for the cost−share funding, safe from unauthorized access. (1) Grantees shall report to the department an annual accounting for accomplishments regarding its activities funded under the grant. (2) The department may require more frequent reports than those required under sub. (1) from a grantee which document accomplishments regarding activities funded under the grant. (3) The grantee shall submit a final report after project com- pletion. At a minimum, the report shall include project evaluation and monitoring information consistent with the commitments made in the project application submitted under s. NR 153.17. The department may require the grantee to submit other information in the final report. History: CR 00−025: cr. Register September 2002 No. 561, eff. 10−1−02. NR 153.31 Variances. The department may approve in writing a variance from a requirement of this chapter upon written request from the grantee if the department determines that a vari- ance is essential to effect necessary grant actions or water quality objectives and where special circumstances make a variance in the best interest of the program. A grantee’s written variance request shall clearly explain the circumstances justifying the variance. Before approving a variance, the department shall take into account factors such as good cause, circumstances beyond the control of the grantee and financial hardship. The department may not grant variances from statutory requirements. History: CR 00−025: cr. Register September 2002 No. 561, eff. 10−1−02. NR 153.32 Grant evaluation and enforcement. (1) On an annual basis, the department shall evaluate the progress of projects. During the evaluation, the department shall examine the progress of the project toward project goals and water quality objectives specified in the grant application, grant or grant amend- ment. Upon consulting with the project sponsor, the department may take appropriate action to improve the progress of the project. Department action may include, but is not limited to, more fre- quent project evaluation, the use of interim project goals, changes to project funding, and the adoption of sanctions in sub. (2). (2) The following sanctions may be imposed by the depart- ment for no...
Sample 1Sample 2Sample 3
OPEN RECORDS REQUIREMENTS. This Release and Settlement Agreement is not confidential. Plaintiff understands and agrees that the State of Colorado and its agencies and departments are bound by applicable public disclosure laws including, without limitation, the provisions of C.R.S. §00-00-000, et seq. (Colorado Open Records Act), as presently or subsequently amended, and that the State of Colorado may be required to disclose this Release and Settlement Agreement in its entirety if requested to do so under such statutes. Plaintiff understands that this Release and Settlement Agreement are public records and further agrees that he will not hold the State of Colorado, or its administrators, officers, agents, or employees, liable for release of information contained in public records under such statutes.
Sample 1Sample 2
OPEN RECORDS REQUIREMENTS. If the Requestor, its employees, contractors, and/or representatives are subject to the Freedom of Information Act (5 U.S.C. § 552), or other federal, state, municipal, or other open records act, or other similar legal requirement, then the Requester will so notify the SERTP Sponsors by marking the appropriate box below. If the Requestor is subject to any such requirement, the Requestor agrees to coordinate with the SERTP Sponsors regarding potential options in an effort to ensure that the confidentiality of any Requested Confidential Information that it might seek is maintained, including the potential for read only and/or on-site review of the Confidential Information (“Option”). By signing this Agreement, the Requestor represents and warrants that it has complied with this Section 2. Any failure by Requestor to implement an Option reasonably acceptable to the SERTP Sponsors may result in the denial of access to the Confidential Information, including the revocation of any such access in accordance with Section 12. Indicate by checking one of the boxes below whether the Requestor, its employees, contractors, and/or representatives are subject to the Freedom of Information Act (5 U.S.C. § 552), or other federal, state, municipal, or other open records act or similar legal requirement: YES, the Requestor, its employees, contractors, and/or representatives are subject to the Freedom of Information Act (5 U.S.C. § 552), or other federal, state, municipal, or other open records act or similar legal requirement. NO, the Requestor, its employees, contractors, and/or representatives are NOT subject to the freedom of information act (5 U.S.C. § 552), or other federal, state, municipal, or other open records act or similar legal requirement.
Sample 1Sample 2
OPEN RECORDS REQUIREMENTS. (a) All project−related re- cords are subject to the state’s open records law. (b) The grantee shall keep any confidential information that is not subject to the open records law, such as social security num- bers that is required for income tax purposes for the cost−share funding, safe from unauthorized access. History: CR 00−025: cr. Register September 2002 No. 561, eff. 10−1−02; 2015 (1) Grantees shall report to the department an annual accounting for accomplishments regarding its activities funded under the grant. (2) The department may require more frequent reports than those required under sub. (1) from a grantee which document ac- complishments regarding activities funded under the grant. (3) The grantee shall submit a final report after project com- pletion. At a minimum, the report shall include project evaluation and monitoring information consistent with the commitments made in the project application submitted under s. NR 155.17. The department may require the grantee to submit other informa- tion in the final report. History: CR 00−025: cr. Register September 2002 No. 561, eff. 10−1−02.
Sample 1Sample 2
OPEN RECORDS REQUIREMENTS. Plaintiffs understand and agree that the State of Colorado and its departments, agencies, and employees are bound by applicable public disclosure laws, including, without limitation, the provisions of the Colorado Open Records Act at C.R.S. § 00-00-000, et seq. (2018), as presently or subsequently amended, and that the State of Colorado, its departments, agencies, or employees may be required to disclose this Settlement Agreement in its entirety if requested to do so under such statutes. Plaintiffs agree that neither the State of Colorado, nor its departments, agencies, nor employees, shall be liable for the release of public records under such statutes.
Sample 1
OPEN RECORDS REQUIREMENTS. This Release and Settlement Agreement is not confidential. Plaintiff understands and agrees that the State of Colorado and its agencies and departments are bound by applicable public disclosure laws including, without limitation, the provisions of C.R.S. §00-00-000, et seq. (Colorado Open Records Act), as presently or subsequently amended, and that the State of Colorado may be required to disclose this Release and Settlement Agreement in its entirety if requested to do so under such statutes. Plaintiff understands that this Release and Settlement Agreement are public records and further agrees that he will not hold the State of Colorado, or its administrators, officers, agents, or employees, liable for release of information contained in public records under such statutes. WARRANTIES AND REPRESENTATIONS. Plaintiff represents and warrants that he has not assigned or transferred any claim arising from or related to the Incident to any third party and that no third party has been subrogated to their interest in claims purported to be released hereby, or, if any third party has been subrogated to Plaintiff’s interest, the interest of any subrogee has been settled, compromised, and extinguished. Plaintiff agrees to defend and indemnify the State, its departments, agencies, officers, and employees, and to hold them harmless against the claims of any assignee or subrogee to claims purported to be released hereby that may hereafter be asserted.
Sample 1
AutoNDA by SimpleDocs
OPEN RECORDS REQUIREMENTS. If compensation payable hereunder exceeds Ten Thousand Dollars ($10,000) per annum, Company hereby agrees to make available to the Secretary of Health and Human Services (“HHS”), the Comptroller General of the Government Accounting Office (“GAO”), Client and Intermediary and their authorized representatives, all contracts, book, documents and records that are necessary to certify to the nature and extent of the costs hereunder for a period of four (4) years after the furnishing of services hereunder. In addition, Company hereby agrees, if services are to be provided by subcontract, to make available to the HHS, GAO, Client and Intermediary or their authorized representative, all contracts, book, documents, and records that are necessary to certify the nature and extent of the costs hereunder for a period of four (4) years after the furnishing of services hereunder within fourteen (14) days of request.
Sample 1
OPEN RECORDS REQUIREMENTS. If you are subject to the Freedom of Information Act (5 U.S.C. § 552), or other federal, state, municipal, or other open records act, or other similar legal requirement, then you will so notify the SERTP Sponsors when making your request for Covered Information by marking the appropriate box below. If you are subject to any such requirement, you agree to coordinate with the SERTP Sponsors regarding potential options in an effort to ensure that the confidentiality of the Covered Information is maintained, including the potential for read only and/or on-site review of the Covered Information (“Option”). By signing this Agreement, you represent and warrant that you have complied with this Section 4(g). Any failure by you to implement an Option reasonably acceptable to the SERTP Sponsors may result in the denial of access to the Covered Information, including the revocation of access in accordance with Section 7. Indicate by checking one of the boxes below whether you are subject to the Freedom of Information Act (5 U.S.C. § 552), or other federal, state, municipal, or other open records act or similar legal requirement: YES, the signatory and/or its organization/employer is subject to the freedom of information act (5 U.S.C. § 552), or other federal, state municipal, or open records act or similar legal requirement NO, the signatory and/or its organization/employer is NOT subject to the freedom of information act (5 U.S.C.. § 552), or other federal, state municipal, or open records act or similar legal requirement
Sample 1

Related to OPEN RECORDS REQUIREMENTS

  • 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.

  • 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.

  • 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.

  • CERTIFICATION REGARDING DRUG-FREE WORKPLACE REQUIREMENTS 1. The Contractor certifies that it will provide a drug-free workplace by: a. Publishing a statement notifying employees that the unlawful manufacture, distribution, dispensing, possession or use of a controlled substance is prohibited in the Contractor’s workplace and specifying the actions that will be taken against employees for violation of such prohibition;

  • 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.

  • Expenditure on Safety Requirements All costs and expenses arising out of or relating to Safety Requirements shall be borne by the Concessionaire to the extent such costs and expenses form part of the works and services included in the Scope of the Project, and works and services, if any, not forming part of the Scope of the Project shall be undertaken and funded in accordance with the provisions of Article 16.

  • E-Verify Requirements To the extent applicable under ARIZ. REV. STAT. § 41- 4401, the Contractor and its subcontractors warrant compliance with all federal immigration laws and regulations that relate to their employees and their compliance with the E-verify requirements under ARIZ. REV. STAT. § 23-214(A). Contractor’s or its subcontractor’s failure to comply with such warranty shall be deemed a material breach of this Agreement and may result in the termination of this Agreement by the City.

  • 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.

  • Information Requirements The Company covenants that, if at any time before the end of the Effectiveness Period the Company is not subject to the reporting requirements of the Exchange Act, it will cooperate with any Holder and take such further reasonable action as any Holder may reasonably request in writing (including, without limitation, making such reasonable representations as any such Holder may reasonably request), all to the extent required from time to time to enable such Holder to sell Registrable Securities without registration under the Securities Act within the limitation of the exemptions provided by Rule 144 and Rule 144A under the Securities Act and customarily taken in connection with sales pursuant to such exemptions. Upon the written request of any Holder, the Company shall deliver to such Holder a written statement as to whether it has complied with such filing requirements, unless such a statement has been included in the Company’s most recent report filed pursuant to Section 13 or Section 15(d) of Exchange Act. Notwithstanding the foregoing, nothing in this Section 7 shall be deemed to require the Company to register any of its securities (other than the Common Stock) under any section of the Exchange Act.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!