HEART Compliance Sample Clauses

The HEART Compliance clause requires parties to adhere to specific standards or regulations related to health, ethics, accountability, responsibility, and transparency (HEART). In practice, this clause obligates organizations to implement policies and procedures that ensure their operations, products, or services meet these criteria, such as maintaining data privacy, ethical conduct, and transparent reporting. Its core function is to promote responsible and ethical behavior, reducing legal and reputational risks by ensuring compliance with relevant HEART principles.
HEART Compliance. Unless a different date is specified below, the following changes for compliance with HEART were effective as of the first day of the first Plan Year beginning on or after January 1, 2009: (1) Death/Disability of Participant While Performing Qualified Military Service. The Plan was amended to provide that Participants dying and/or becoming disabled on or after January 1, 2007 while performing qualified military service as defined in Code Section 414(u)(5) (“QMS”) shall be treated under the Plan for all purposes (other than benefit accruals described in paragraph (2) below), including vesting and any exceptions to applicable last day or Hours of Service requirements, in the same way as Active Participants who die and/or become disabled while employed, as if the Participant resumed employment with the Employer and then terminated employment on account of death or disability. (A) ¨ Later Effective Date for Disabled Participants: (cannot be later than the date the Plan was restated onto the Fidelity Volume Submitter). Participants becoming disabled before this date shall not be treated as having resumed employment pursuant to Section 18.06 of the Basic Plan Document on the day prior to dying or becoming. Note: A later effective date may not be elected for Participants who die while performing QMS.
View SourceView Similar (3)
HEART Compliance i Unless a different date is specified below, the following provisions were effective as of the first day of the first Plan Year beginning on or after January 1, 2007: A. ☐ Compensation: Effective for Plan Years beginning after December 31, 2008, the definition of “Compensation” was amended to include differential pay. 1. ☐ A later effective date applies: B. 415 Compensation: Effective for limitation years beginning after December 31, 2008, the definition of “415 compensation” was amended to include differential pay.
View Source

Related to HEART Compliance

  • CEQA Compliance The District has complied with all assessment requirements imposed upon it by the California Environmental Quality Act (Public Resource Code Section 21000 et seq. (“CEQA”) in connection with the Project, and no further environmental review of the Project is necessary pursuant to CEQA before the construction of the Project may commence.

  • HIPAA Compliance If this Contract involves services, activities or products subject to the Health Insurance Portability and Accountability Act of 1996 (HIPAA), the Contractor covenants that it will appropriately safeguard Protected Health Information (defined in 45 CFR 160.103), and agrees that it is subject to, and shall comply with, the provisions of 45 CFR 164 Subpart E regarding use and disclosure of Protected Health Information.

  • OSHA Compliance To the extent applicable to the services to be performed under this Agreement, Contractor represents and warrants, that all articles and services furnished under this Agreement meet or exceed the safety standards established and promulgated under the Federal Occupational Safety and Health Law (Public Law 91-596) and its regulations in effect or proposed as of the date of this Agreement.

  • FERPA Compliance In connection with all FERPA Records that Contractor may create, receive or maintain on behalf of University pursuant to the Underlying Agreement, Contractor is designated as a University Official with a legitimate educational interest in and with respect to such FERPA Records, only to the extent to which Contractor (a) is required to create, receive or maintain FERPA Records to carry out the Underlying Agreement, and (b) understands and agrees to all of the following terms and conditions without reservation:

  • PCI Compliance Company shall not connect to or utilize any computer network or systems of the Aviation Authority, including, without limitation, for transmission of credit card payments. Company shall be solely responsible for providing and maintaining its own computer networks and systems and shall ensure its system ensure its system used to collect, process, store or transmit credit card or customer credit card and/or personal information is compliant with all applicable Payment Card Industry (“PCI”) Data Security Standard (“DSS”). 1. Company shall, within 5 days, notify the Aviation Authority of any security malfunction or breach, intrusion or unauthorized access to cardholder or other customer data, and shall comply with all then applicable PCI requirements. 2. Company, in addition to notifying the Aviation Authority and satisfying the PCI requirements, will immediately take the remedial actions available under the circumstances and provide the Aviation Authority with an explanation of the cause of the breach or intrusion and the proposed remediation plan. Company will notify the Aviation Authority promptly if it learns that it is no longer PCI DSS compliant and will immediately provide the Aviation Authority with a report on steps being taken to remediate the non-compliance status and provide evidence of compliance once PCI DSS compliance is achieved. 3. Company, its successor’s and assigns, will continue to comply with all provisions of this Agreement relating to accidents, incidents, damages and remedial requirements after the termination of this Agreement. 4. Company shall ensure strict compliance with PCI DSS for each credit card transaction and acknowledges responsibility for the security of cardholder data. Company will create and maintain reasonable detailed, complete and accurate documentation describing the systems, processes, network segments, security controls and dataflow used to receive, process transmit store and secure Customer’s cardholder data. Such documentation shall conform to the most current version of PCI DSS. 5. Company must maintain PCI Certification as a bankcard merchant at the Airport. Company is responsible, at Company’s own expense, to contract and pay for all quarterly, annual or other required assessments, remediation activities related to processes within Concessionaire’s control, analysis or certification processes necessary to maintain PCI certification as a bankcard merchant. 6. PCI DSS - Company shall make available on the Premises, within 24 hours upon request by the Aviation Authority, such documentation, policies, procedures, reports, logs, configuration standards and settings and all other documentation necessary for the Aviation Authority to validate Company’s compliance with PCI DSS as well as make available to the individuals responsible for implementing, maintaining and monitoring those system components and processes. Requested logs must be made available to the Aviation Authority in electronic format compatible with computers used by the Aviation Authority. 7. Evidence of PCI DSS Compliance – Company agrees to supply their PCI DSS compliance status and evidence of its most recent validation of compliance upon execution of the Contract. Company must supply to the Aviation Authority evidence of validation of compliance at least annually to be delivered along with the Annual Certification of Fees in accordance with Article 5.C. of this Agreement.