Requirements for Protection In compliance with NPCC requirements and Good Utility Practice, Developer shall provide, install, own, and maintain relays, circuit breakers and all other devices necessary to remove any fault contribution of the Large Generating Facility to any short circuit occurring on the New York State Transmission System not otherwise isolated by Connecting Transmission Owner’s equipment, such that the removal of the fault contribution shall be coordinated with the protective requirements of the New York State Transmission System. Such protective equipment shall include, without limitation, a disconnecting device or switch with load- interrupting capability located between the Large Generating Facility and the New York State Transmission System at a site selected upon mutual agreement (not to be unreasonably withheld, conditioned or delayed) of the Developer and Connecting Transmission Owner. Developer shall be responsible for protection of the Large Generating Facility and Developer’s other equipment from such conditions as negative sequence currents, over- or under-frequency, sudden load rejection, over- or under-voltage, and generator loss-of-field. Developer shall be solely responsible to disconnect the Large Generating Facility and Developer’s other equipment if conditions on the New York State Transmission System could adversely affect the Large Generating Facility.
Program Requirements The parties shall comply with the Disadvantaged Business Enterprise Program requirements established in 49 CFR Part 26.
Fraud Prevention A. To screen its employees and contractors to determine if they have been excluded from Medicare, Medicaid or any federal or state health care program. The Contractor agrees to search monthly the HHS-Office of Inspector General ("OIG") and Texas Health and Human Services Commission Office of Inspector General ("HHSC-OIG") List of Excluded Individuals/Entities ("LEIE") websites to capture exclusions and reinstatements that have occurred since the last search and to immediately report to HHSC-OIG any exclusion information the Contractor discovers. Exclusionary searches for prospective employees and contractors shall be performed prior to employment or contracting.
B. That no Medicaid payments can be made for any items or services directed or prescribed by a physician or other authorized person who is excluded from Medicare, Medicaid or any federal or state health care program when the individual or entity furnishing the items or services either knew or should have known of the exclusion. This prohibition applies even when the Medicaid payment itself is made to another contractor, practitioner or supplier who is not excluded.
C. That this contract is subject to all state and federal laws and regulations relating to fraud and abuse in health care and the Medicaid program. As required by 42 C.F.R. §431.107, the Contractor agrees to keep all records necessary to disclose the extent of services the Contractor furnishes to people in the Medicaid program and any information relating to payments claimed by the Contractor for furnishing Medicaid services. On request, the Contractor also agrees to furnish HHSC, AG-MFCU, or HHS any information maintained under 42 C.F.
Certain State Law Requirements for Contracts The contents of this Section are required by Texas Law and are included by County regardless of content. For purposes of Sections 2252.152, 2271.002, and 2274.002, Texas Government Code, as amended, C&T hereby verifies that C&T and any parent company, wholly owned subsidiary, majority-owned subsidiary, and affiliate:
a. Unless affirmatively declared by the United States government to be excluded from its federal sanctions regime relating to Sudan or Iran or any federal sanctions regime relating to a foreign terrorist organization, is not identified on a list prepared and maintained by the Texas Comptroller of Public Accounts under Sections 806.051, 807.051, or 2252.153 of the Texas Government Code.
b. If employing ten (10) or more full-time employees and this Agreement has a value of
System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.
Child Abuse Reporting Requirements A. Grantees shall comply with child abuse and neglect reporting requirements in Texas Family Code Chapter 261. This section is in addition to and does not supersede any other legal obligation of the Grantee to report child abuse.
B. Grantee shall use the Texas Abuse Hotline Website located at xxxxx://xxx.xxxxxxxxxxxxxx.xxx/Login/Default.aspx as required by the System Agency. Grantee shall retain reporting documentation on site and make it available for inspection by the System Agency.
CHILD ABUSE REPORTING CONTRACTOR hereby agrees to annually train all staff members, including volunteers, so that they are familiar with and agree to adhere to its own child and dependent adult abuse reporting obligations and procedures as specified in California Penal Code section 11164 et seq. and Education Code 44691. To protect the privacy rights of all parties involved (i.e., reporter, child and alleged abuser), reports will remain confidential as required by law and professional ethical mandates. A written statement acknowledging the legal requirements of such reporting and verification of staff adherence to such reporting shall be submitted to the LEA.
Minimum Site Requirements for TIPS Sales (when applicable to TIPS Sale). Cleanup: When performing work on site at a TIPS Member’s property, Vendor shall clean up and remove all debris and rubbish resulting from their work as required or directed by the TIPS Member or as agreed by the parties. Upon completion of work, the premises shall be left in good repair and an orderly, neat, clean and unobstructed condition. Preparation: Vendor shall not begin a project for which a TIPS Member has not prepared the site, unless Vendor does the preparation work at no cost, or until TIPS Member includes the cost of site preparation in the TIPS Sale Site preparation includes, but is not limited to: moving furniture, installing wiring for networks or power, and similar pre‐installation requirements. Registered Sex Offender Restrictions: For work to be performed at schools, Vendor agrees that no employee of Vendor or a subcontractor who has been adjudicated to be a registered sex offender will perform work at any time when students are, or reasonably expected to be, present unless otherwise agreed by the TIPS Member. Vendor agrees that a violation of this condition shall be considered a material breach and may result in the cancellation of the TIPS Sale at the TIPS Member’s discretion. Vendor must identify any additional costs associated with compliance of this term. If no costs are specified, compliance with this term will be provided at no additional charge. Safety Measures: Vendor shall take all reasonable precautions for the safety of employees on the worksite, and shall erect and properly maintain all necessary safeguards for protection of workers and the public. Vendor shall post warning signs against all hazards created by the operation and work in progress. Proper precautions shall be taken pursuant to state law and standard practices to protect workers, general public and existing structures from injury or damage. Smoking: Persons working under Agreement shall adhere to the TIPS Member’s or local smoking statutes, codes, ordinances, and policies.
NMHS Governance, Safety and Quality Requirements 2.1 Participates in the maintenance of a safe work environment.
2.2 Participates in an annual performance development review.
2.3 Supports the delivery of safe patient care and the consumers’ experience including participation in continuous quality improvement activities in accordance with the requirements of the National Safety and Quality Health Service Standards and other recognised health standards.
2.4 Completes mandatory training (including safety and quality training) as relevant to role.
2.5 Performs duties in accordance with Government, WA Health, North Metropolitan Health Service and Departmental / Program specific policies and procedures.
2.6 Abides by the WA Health Code of Conduct, Occupational Safety and Health legislation, the Disability Services Act and the Equal Opportunity Act.
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.
