Information Required The report must include, at a minimum, the name, category, description, expected outcomes, anticipated CCBF contribution, anticipated start date, and anticipated end date of each active Eligible Project.
Encryption Requirements DST will not locally store Fund Data on any laptops or mobile devices (e.g., Blackberries, PDAs) managed by DST.
Compliance Verification (a) The sub recipient shall periodically interview a sufficient number of employees entitled to DB prevailing wages (covered employees) to verify that contractors or subcontractors are paying the appropriate wage rates. As provided in 29 CFR 5.6(a)(6), all interviews must be conducted in confidence. The sub recipient must use Standard Form 1445 (SF 1445) or equivalent documentation to memorialize the interviews. Copies of the SF 1445 are available from EPA on request.
(b) The sub recipient shall establish and follow an interview schedule based on its assessment of the risks of noncompliance with DB posed by contractors or subcontractors and the duration of the contract or subcontract. Sub recipients must conduct more frequent interviews if the initial interviews or other information indicated that there is a risk that the contractor or subcontractor is not complying with DB. Sub recipients shall immediately conduct interviews in response to an alleged violation of the prevailing wage requirements. All interviews shall be conducted in confidence."
(c) The sub recipient shall periodically conduct spot checks of a representative sample of weekly payroll data to verify that contractors or subcontractors are paying the appropriate wage rates. The sub recipient shall establish and follow a spot check schedule based on its assessment of the risks of noncompliance with DB posed by contractors or subcontractors and the duration of the contract or subcontract. At a minimum, if practicable, the sub recipient should spot check payroll data within two weeks of each contractor or subcontractor’s submission of its initial payroll data and two weeks prior to the completion date the contract or subcontract. Sub recipients must conduct more frequent spot checks if the initial spot check or other information indicates that there is a risk that the contractor or subcontractor is not complying with DB. In addition, during the examinations the sub recipient shall verify evidence of fringe benefit plans and payments there under by contractors and subcontractors who claim credit for fringe benefit contributions.
(d) The sub recipient shall periodically review contractors and subcontractor’s use of apprentices and trainees to verify registration and certification with respect to apprenticeship and training programs approved by either the U.S Department of Labor or a state, as appropriate, and that contractors and subcontractors are not using disproportionate numbers of, laborers, trainees and apprentices. These reviews shall be conducted in accordance with the schedules for spot checks and interviews described in Item 5(b) and (c) above. •
(e) Sub recipients must immediately report potential violations of the DB prevailing wage requirements to the EPA DB contact listed above and to the appropriate DOL Wage and Hour District Office listed at xxxx://xxx.xxx.xxx/whd/america2.htm. “Contractor shall comply with all applicable standards, orders, or requirements issued under section 306 of the Clean Air Act (42 U.S.C. 1857(h)), section 508 of the Clean Water Act (33 • U.S.C. 1368), Executive Order 11738, and Environmental Protection Agency regulations (40 CFR part 15). (Awards to Contractors and Subcontractors in Excess of $100,000) The undersigned certifies, to the best of his or her knowledge and belief, that:
(1) No Federal appropriated funds have been paid or will be paid, by or on behalf of the undersigned, to any person for influencing or attempting to influence an officer or employee of any agency, a Member of Congress, an officer or employee of Congress, or an employee of a Member of Congress in connection with the awarding of any Federal contract, the making of any Federal grant, the making of any Federal loan, the entering into of any cooperative agreement, and the extension, continuation, renewal, amendment, or modification of any Federal contract, grant, loan or cooperative agreement.
(2) If any funds other than Federal appropriated funds have been paid or will be paid to any person for influencing or attempting to influence an officer or employee of any agency, a Member of Congress, an officer or employee of Congress, or an employee of a Member of Congress in connection with this Federal contract, grant, loan, or cooperative agreement, the undersigned shall complete and submit Standard Form-LLL, “Disclosure Form to Report Lobbying,” in accordance with its instructions.
(3) The undersigned shall require that the language of this certification be included in the award documents for all subawards at all tiers (including subcontracts, subgrants, and contracts under grants, loans, and cooperative agreements) and that all subrecipients shall certify and disclose accordingly. This certification is a material representation of fact upon which reliance was placed when this transaction was made or entered into. Submission of this certification is a prerequisite for making or entering into this transaction imposed by section 1352, title 31, U.S. Code. Any person who fails to file the required certification shall be subject to a civil penalty of not less than $10,000 and not more than $100,000 for each such failure. Title Date
Rule 144 Requirements After the earliest of (i) the closing of the sale of securities of the Company pursuant to a Registration Statement, (ii) the registration by the Company of a class of securities under Section 12 of the Exchange Act, or (iii) the issuance by the Company of an offering circular pursuant to Regulation A under the Securities Act, the Company agrees to:
(a) make and keep current public information about the Company available, as those terms are understood and defined in Rule 144;
(b) use its best efforts to file with the Commission in a timely manner all reports and other documents required of the Company under the Securities Act and the Exchange Act (at any time after it has become subject to such reporting requirements); and
(c) furnish to any holder of Registrable Shares upon request (i) a written statement by the Company as to its compliance with the reporting requirements of Rule 144 and of the Securities Act and the Exchange Act (at any time after it has become subject to such reporting requirements), (ii) a copy of the most recent annual or quarterly report of the Company, and (iii) such other reports and documents of the Company as such holder may reasonably request to avail itself of any similar rule or regulation of the Commission allowing it to sell any such securities without registration.
Information Required by Rule 144A upon the request of such Holder (and shall deliver to any qualified institutional buyer designated by such Holder), such financial and other information as such Holder may reasonably determine to be necessary in order to permit compliance with the information requirements of Rule 144A under the Securities Act in connection with the resale of Notes, except at such times as the Company is subject to the reporting requirements of section 13 or 15(d) of the Exchange Act (for the purpose of this Section 7.1(j), the term “qualified institutional buyer” shall have the meaning specified in Rule 144A under the Securities Act); and
Check if Required 🗸□ If checked, the Supplemental State Terms and attached hereto as Exhibit “G” are hereby incorporated by reference into this DPA in their entirety. If Checked, the Provider, has signed Exhibit “E” to the Standard Clauses, otherwise known as General Offer of Privacy Terms
System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.
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.
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.
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.
