Electronic PHI Security Rule Obligations Sample Clauses

Electronic PHI Security Rule Obligations. With respect to Electronic PHI, Business Associate shall: Implement and use Administrative, Physical, and Technical Safeguards in compliance with 45 CFR sections 164.308, 164.310, and 164.312; Identify in writing upon request from Covered Entity all the safeguards that it uses to protect such Electronic PHI; Prior to any Use or Disclosure of Electronic PHI by an Agent or Subcontractor, ensure that any Agent or Subcontractor to whom it provides Electronic PHI agrees in writing to implement and use Administrative, Physical, and Technical Safeguards that reasonably and appropriately protect the Confidentiality, Integrity and Availability of Electronic PHI. The written agreement must identify Covered Entity as a direct and intended third party beneficiary with the right to enforce any breach of the agreement concerning the Use or Disclosure of Electronic PHI, and be provided to Covered Entity upon request; Report in writing to Covered Entity any Successful Security Incident or Targeted Security Incident as soon as it becomes aware of such incident and in no event later than five (5) business days after such awareness. Such report shall be timely made notwithstanding the fact that little information may be known at the time of the report and need only include such information then available; Following such report, provide Covered Entity with the information necessary for Covered Entity to investigate any such incident; and Continue to provide to Covered Entity information concerning the incident as it becomes available to it.
Sample 1

Related to Electronic PHI Security Rule Obligations

  • Payment Security Requirements A. Unless Company has maintained an agreement similar to this Agreement with Authority during the 18 months prior to the effective date of this Agreement without the occurrence of any act or omission that would have been a default under this Agreement, Company will provide Authority on or before the commencement date of this Agreement with an acceptable bond, irrevocable letter of credit or other similar security acceptable to Authority in an amount equal to the estimate of three months’ Rents, fees and charges, payable by Company under this Agreement, to guarantee the faithful performance by Company of its obligations under this Agreement and the payment of all Rents, fees, tax assessments, and charges due hereunder (hereinafter referred to as “Payment Security”). Company will be obligated to maintain such Payment Security in effect until the expiration of 18 consecutive months during which Company commits no default under this Agreement. Such Payment Security will be in a form and with a company acceptable to Authority and licensed to do business in the State of Florida. In the event that any such Payment Security is for a period less than the full period required under this Agreement or if such Payment Security is canceled, Company will provide a renewal or replacement Payment Security for the remaining required period at least 60 days prior to the date of such expiration or cancellation. Such Payment Security will require notice by the surety to Authority at least 60 days prior to any cancellation.

  • Data Security Requirements A. Data Transport. When transporting Confidential Information electronically, including via email, the data will be protected by:

  • Electronic Payments The Grantee can choose to use electronic funds transfer (EFT) to receive grant payments. All grantees wishing to receive their award through EFT must submit a Vendor Direct Deposit Authorization form (form number DFS-AI-26E, rev 6/2014), incorporated by reference, to the Florida Department of Financial Services. If EFT has already been set up for your organization, you do not need to submit another authorization form unless you have changed bank accounts. To download this form visit xxxxxxxxxxxx.xxx/Xxxxxxxx/XX/Xxxxx/XXX-X0-00X.xxx. The form also includes tools and information that allow you to check on payments.

  • Information Security Requirements In cases where the State is not permitted to manage/modify the automation equipment (server/computer/other) that controls testing or monitoring devices, the Contractor agrees to update and provide patches for the automation equipment and any installed operating systems or applications on a quarterly basis (at minimum). The Contractor will submit a report to the State of updates installed within 30 days of the installation as well as a Plan of Actions and Milestones (POA&M) to remediate any vulnerabilities ranging from Critical to Low. The contractor will provide an upgrade path or compensatory security controls for any operating systems and applications listed as beyond “end-of-life” or EOL, within 90 days of the EOL and complete the EOL system’s upgrade within 90 days of the approved plan.

  • Sub-processor Obligations MailChimp shall: (i) enter into a written agreement with the Sub-processor imposing data protection terms that require the Sub-processor to protect the Customer Data to the standard required by Data Protection Laws; and (ii) remain responsible for its compliance with the obligations of this DPA and for any acts or omissions of the Sub-processor that cause MailChimp to breach any of its obligations under this DPA.

  • Processor Obligations 4.1 The Processor may collect, process or use Personal Data only within the scope of this DPA.

  • Security Rule “Security Rule” shall mean the Standards for the Protection of Electronic Protected Health Information at 45 CFR Part 160 and Part 164, Subparts A and C.

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