Responsibility for Reporting of Breaches when Required by State or Federal Law Sample Clauses

Responsibility for Reporting of Breaches when Required by State or Federal Law. If the cause of a breach is attributable to the County Department/Agency or its agents, subcontractors or vendors, the County Department/Agency is responsible for all required reporting of the breach. If the cause of the breach is attributable to CDSS, CDSS is responsible for all required reporting of the breach. When applicable law requires the breach be reported to a federal or state agency or that notice be given to media outlets, DHCS (if the breach involves MEDS or SSA data), CDSS, and the County Department/Agency shall coordinate to ensure such reporting is in compliance with applicable law and to prevent duplicate reporting, and to jointly determine responsibility for purposes of allocating the costs of such reports, if any.
AutoNDA by SimpleDocs
Responsibility for Reporting of Breaches when Required by State or Federal Law. If the cause of a breach of Medi-Cal PII is attributable to the County Department or its agents, subcontractors or vendors, the County Department is responsible for reporting the breach and all costs associated with the breach. If the cause of the breach is attributable to DHCS, DHCS is responsible for reporting the breach and for all costs associated with the breach. When applicable law requires the breach be reported to a federal or state agency or that notice be given to media outlets, DHCS and the County Department shall coordinate to ensure such reporting is in compliance with applicable law and to prevent duplicate reporting, and to jointly determine responsibility for purposes of allocating the costs of such reports, if any.
Responsibility for Reporting of Breaches when Required by State or Federal Law. If the cause of a breach is attributable to the Contractor or its agents, subcontractors or vendors, the Contractor is responsible for all required reporting of the breach. If the cause of the breach is attributable to the County, the County is responsible for all required reporting of the breach. When applicable law requires the breach be reported to a federal or state agency or that notice be given to media outlets, DHCS (Department of Health Care Services) and XXXX (California Department of Social Services) (if the breach involves MEDS or SSA data), then the Contractor shall coordinate with the County to ensure such reporting is in compliance with applicable law and to prevent duplicate reporting, and to jointly determine responsibility for purposes of allocating the costs of such reports, if any.
Responsibility for Reporting of Breaches when Required by State or Federal Law. If the cause of a breach is attributable to the County Department/Agency or its agents, subcontractors or vendors, the County Department/Agency is responsible for all required reporting the breach and all costs associated withof the breach. If the cause of the breach is attributable to CDSS, CDSS is responsible for all required reporting the breach and for all costs associated withof the breach. When applicable law requires the breach be reported to a federal or state agency or that notice be given to media outlets, DHCS (if the breach involves MEDS or SSA data), CDSS, and the County Department/Agency shall coordinate to ensure such reporting is in compliance with applicable law and to prevent duplicate reporting, and to jointly determine responsibility for purposes of allocating the costs of such reports, if any.
Responsibility for Reporting of Breaches when Required by State or Federal Law. If the cause of a breach is attributable to the Contractor or its agents, subcontractors or vendors, the Contractor is responsible for all required reporting of the breach. If the cause of the breach is attributable to the County, the County is responsible for all required reporting of the breach. When applicable law requires the breach be reported to a federal or state agency or that notice be given to media outlets, DHCS (Department of Health Care Services) and CDSS (California Department of Social Services) (if the breach involves MEDS or SSA data), then the Contractor shall coordinate with the County to ensure such reporting is in compliance with applicable law and to prevent duplicate reporting, and to jointly determine responsibility for purposes of allocating the costs of such reports, if any. DocuSign Envelope ID: 9AF40527-22C4-4230-B711-536D5ED76CF0
Responsibility for Reporting of Breaches when Required by State or Federal Law. If the cause of a breach of Medi-Cal PII is attributable to the CalSAWS Consortium or its agents, subcontractors or vendors, the CalSAWS Consortium is responsible for all required reporting of the breach. If the cause of the breach is attributable to DHCS, DHCS is responsible for all required reporting of the breach. When applicable law requires the breach be reported to a federal or state agency or that notice be given to media outlets, DHCS and the CalSAWS Consortium shall coordinate to ensure such reporting is in compliance with applicable law and to prevent duplicate reporting, and to jointly determine responsibility for purposes of allocating the costs of such reports, if any.
Responsibility for Reporting of Breaches when Required by State or Federal Law. If the cause of a breach of Medi-Cal PII is attributable to the County Department/Agency or its agents, subcontractors or vendors, the County Department/Agency is responsible for all required reporting the breach and all costs associated withof the breach. If the cause of the breach is attributable to DHCS, DHCS is responsible for all required reporting of the breach and for all costs associated with the
AutoNDA by SimpleDocs
Responsibility for Reporting of Breaches when Required by State or Federal Law. If the cause of a breach is attributable to the Contractor or its agents, subcontractors or vendors, the Contractor is responsible for all required reporting of the breach. If the cause of the breach is attributable to the County, the County is responsible for all required reporting of the breach. When applicable law requires the breach be reported to a federal or state agency or that notice be given to media outlets, DHCS (Department of Health Care Services) and CDSS (California DocuSign Envelope ID: C1699981-367A-4E93-B66A-CA0849068709 DocuSign Envelope ID: 81A5495A-230D-4264-8358-EB12B24A8B8D DocuSign Envelope ID: 8FC5ECED-4536-49EB-A4AB-9CA23D0B1D81 Department of Social Services) (if the breach involves MEDS or SSA data), then the Contractor shall coordinate with the County to ensure such reporting is in compliance with applicable law and to prevent duplicate reporting, and to jointly determine responsibility for purposes of allocating the costs of such reports, if any.
Responsibility for Reporting of Breaches when Required by State or Federal Law. If the cause of a breach is attributable to the Contractor or its agents, AMR0121-A1 January 12, 2024 DocuSign Envelope ID: 38FE53CB-23DB-4F33-BEA3-052481BD6AFC subcontractors or vendors, the Contractor is responsible for all required reporting of the breach. If the cause of the breach is attributable to the County, the County is responsible for all required reporting of the breach. When applicable law requires the breach be reported to a federal or state agency or that notice be given to media outlets, DHCS (Department of Health Care Services) and XXXX (California Department of Social Services) (if the breach involves MEDS or SSA data), then the Contractor shall coordinate with the County to ensure such reporting is in compliance with applicable law and to prevent duplicate reporting, and to jointly determine responsibility for purposes of allocating the costs of such reports, if any.

Related to Responsibility for Reporting of Breaches when Required by State or Federal Law

  • COMPLIANCE OF LAWS, NOTIFICATIONS ETC. BY PARTIES The Parties are entering into this Agreement for the allotment of a Apartment with the full knowledge of all laws, rules, regulations, notifications applicable to the project.

  • COMPLIANCE OF LAWS, NOTIFICATIONS ETC BY ALLOTTEE(S)

  • Liability for Failure to Stop Payment of Preauthorized Transfers If you order us to stop payment of a preauthorized transfer three (3) business days or more before the transfer is scheduled and we do not do so, we will be liable for your losses or damages.

  • Effect of Failure to File and Obtain and Maintain Effectiveness of any Registration Statement If (i) a Registration Statement covering the resale of all of the Registrable Securities required to be covered thereby (disregarding any reduction pursuant to Section 2(f)) and required to be filed by the Company pursuant to this Agreement is (A) not filed with the SEC on or before the Filing Deadline for such Registration Statement (a “Filing Failure”) (it being understood that if the Company files a Registration Statement without affording each Investor and Legal Counsel the opportunity to review and comment on the same as required by Section 3(c) hereof, the Company shall be deemed to not have satisfied this clause (i)(A) and such event shall be deemed to be a Filing Failure) or (B) not declared effective by the SEC on or before the Effectiveness Deadline for such Registration Statement (an “Effectiveness Failure”) (it being understood that if on the Business Day immediately following the Effective Date for such Registration Statement the Company shall not have filed a “final” prospectus for such Registration Statement with the SEC under Rule 424(b) in accordance with Section 3(b) (whether or not such a prospectus is technically required by such rule), the Company shall be deemed to not have satisfied this clause (i)(B) and such event shall be deemed to be an Effectiveness Failure), (ii) other than during an Allowable Grace Period (as defined below), on any day after the Effective Date of a Registration Statement sales of all of the Registrable Securities required to be included on such Registration Statement (disregarding any reduction pursuant to Section 2(f)) cannot be made pursuant to such Registration Statement (including, without limitation, because of a failure to keep such Registration Statement effective, a failure to disclose such information as is necessary for sales to be made pursuant to such Registration Statement, a suspension or delisting of (or a failure to timely list) the shares of Common Stock on the Principal Market (as defined in the Securities Purchase Agreement) or any other limitations imposed by the Principal Market, or a failure to register a sufficient number of shares of Common Stock or by reason of a stop order) or the prospectus contained therein is not available for use for any reason (a “Maintenance Failure”), or (iii) if a Registration Statement is not effective for any reason or the prospectus contained therein is not available for use for any reason, and either (x) the Company fails for any reason to satisfy the requirements of Rule 144(c)(1), including, without limitation, the failure to satisfy the current public information requirement under Rule 144(c) or (y) the Company has ever been an issuer described in Rule 144(i)(1)(i) or becomes such an issuer in the future, and the Company shall fail to satisfy any condition set forth in Rule 144(i)(2) (a “Current Public Information Failure”) as a result of which any of the Investors are unable to sell Registrable Securities without restriction under Rule 144 (including, without limitation, volume restrictions), then, as partial relief for the damages to any holder by reason of any such delay in, or reduction of, its ability to sell the underlying shares of Common Stock (which remedy shall not be exclusive of any other remedies available at law or in equity, including, without limitation, specific performance), the Company shall pay to each holder of Registrable Securities relating to such Registration Statement an amount in cash equal to two percent (2%) of such Investor’s original principal amount stated in such Investor’s Note on the Closing Date (1) on the date of such Filing Failure, Effectiveness Failure, Maintenance Failure or Current Public Information Failure, as applicable, and (2) on every thirty (30) day anniversary of (I) a Filing Failure until such Filing Failure is cured; (II) an Effectiveness Failure until such Effectiveness Failure is cured; (III) a Maintenance Failure until such Maintenance Failure is cured; and (IV) a Current Public Information Failure until the earlier of (i) the date such Current Public Information Failure is cured and (ii) such time that such public information is no longer required pursuant to Rule 144 (in each case, pro rated for periods totaling less than thirty (30) days). The payments to which a holder of Registrable Securities shall be entitled pursuant to this Section 2(e) are referred to herein as “Registration Delay Payments.” Following the initial Registration Delay Payment for any particular event or failure (which shall be paid on the date of such event or failure, as set forth above), without limiting the foregoing, if an event or failure giving rise to the Registration Delay Payments is cured prior to any thirty (30) day anniversary of such event or failure, then such Registration Delay Payment shall be made on the third (3rd) Business Day after such cure. In the event the Company fails to make Registration Delay Payments in a timely manner in accordance with the foregoing, such Registration Delay Payments shall bear interest at the rate of two percent (2%) per month (prorated for partial months) until paid in full. Notwithstanding the foregoing, no Registration Delay Payments shall be owed to an Investor (other than with respect to a Maintenance Failure resulting from a suspension or delisting of (or a failure to timely list) the shares of Common Stock on the Principal Market) with respect to any period during which all of such Investor’s Registrable Securities may be sold by such Investor without restriction under Rule 144 (including, without limitation, volume restrictions) and without the need for current public information required by Rule 144(c)(1) (or Rule 144(i)(2), if applicable).

  • Compliance with Federal and State Work Authorization and Immigration Laws The Contractor and all subcontractors, suppliers and consultants must comply with all federal and state work authorization and immigration laws, and must certify compliance using the form set forth in Section 7 (“Georgia Security and Immigration Compliance Act Affidavits”). The required certificates must be filed with the Owner and copied maintained by the Contractor as of the beginning date of this contract and each subcontract, supplier contract, or consultant contract, and upon final payment to the subcontractor or consultant. State officials, including officials of the Georgia Department of Audits and Accounts, officials of the Owner, retain the right to inspect and audit the Project Site and employment records of the Contractor, subcontractors and consultants without notice during normal working hours until Final Completion, and as otherwise specified by law and by Rules and Regulations of the Georgia Department of Audits and Accounts.

  • Compliance with Federal Law, Regulations, and Executive Orders This is an acknowledgement that FEMA financial assistance will be used to fund all or a portion of the contract. The contractor will comply with all applicable Federal law, regulations, executive orders, FEMA policies, procedures, and directives.

  • Compliance with Securities Regulations and Commission Requests; Payment of Filing Fees The Operating Partnership, subject to Section 3(e), will comply with the requirements of Rule 430B and will notify the Representatives immediately, and confirm the notice in writing, (i) when any post-effective amendment to the Registration Statement or new registration statement relating to the Notes shall become effective, or any supplement to the Prospectus or any amended Prospectus shall have been filed, (ii) of the receipt of any comments from the Commission, (iii) of any request by the Commission for any amendment to the Registration Statement or the filing of a new registration statement or any amendment or supplement to the Prospectus or any document incorporated by reference therein or otherwise deemed to be a part thereof or for additional information, (iv) of the issuance by the Commission of any stop order suspending the effectiveness of the Registration Statement or such new registration statement or of any order preventing or suspending the use of any preliminary prospectus, or of the suspension of the qualification of the Notes for offering or sale in any jurisdiction, or of the initiation or threatening of any proceedings for any of such purposes or of any examination pursuant to Section 8(e) of the 1933 Act concerning the Registration Statement and (v) if the Operating Partnership becomes the subject of a proceeding under Section 8A of the 1933 Act in connection with the offering of the Notes. The Operating Partnership will effect the filings required under Rule 424(b), in the manner and within the time period required by Rule 424(b) (without reliance on Rule 424(b)(8)), and will take such steps as it deems necessary to ascertain promptly whether the form of prospectus transmitted for filing under Rule 424(b) was received for filing by the Commission and, in the event that it was not, it will promptly file such prospectus. The Operating Partnership will make every reasonable effort to prevent the issuance of any stop order and, if any stop order is issued, to obtain the lifting thereof at the earliest possible moment. The Operating Partnership shall pay the required Commission filing fees relating to the Notes within the time required by Rule 456(b)(1) (i) of the 1933 Act Regulations without regard to the proviso therein and otherwise in accordance with Rules 456(b) and 457(r) of the 1933 Act Regulations (including, if applicable, by updating the “Calculation of Registration Fee” table in accordance with Rule 456(b)(1)(ii) either in a post-effective amendment to the Registration Statement or on the cover page of a prospectus filed pursuant to Rule 424(b)).

  • Medicaid Notification of Termination Requirements Party shall follow the Department of Vermont Health Access Managed-Care-Organization enrollee-notification requirements, to include the requirement that Party provide timely notice of any termination of its practice.

  • COMPLIANCE OF LAWS RELATING TO REMITTANCES 3.1 The Allottee, if resident outside India, shall be solely responsible for complying with the necessary formalities as laid down in Foreign Exchange Management Act, 1999, Reserve Bank of India Act, 1934 and the Rules and Regulations made thereunder or any statutory amendment(s) modification(s) made thereof and all other applicable laws including that of remittance of payment acquisition/sale/transfer of immovable properties in India etc. and provide the Promoter with such permission, approvals which would enable the Promoter to fulfil its obligations under this Agreement. Any refund, transfer of security, if provided in terms of the Agreement shall be made in accordance with the provisions of Foreign Exchange Management Act, 1999 or the statutory enactments or amendments thereof and the Rules and Regulations of the Reserve Bank of India or any other applicable law. The Allottee understands and agrees that in the event of any failure on his/her part to comply with the applicable guidelines issued by the Reserve Bank of India; he/she may be liable for any action under the Foreign Exchange Management Act, 1999 or other laws as applicable, as amended from time to time. 3.2 The Promoter accepts no responsibility in regard to matters specified in para 3.1 above. The Allottee shall keep the Promoter fully indemnified and harmless in this regard. Whenever there is any change in the residential status of the Allottee subsequent to the signing of this Agreement, it shall be the sole responsibility of the Allottee to intimate the same in writing to the Promoter immediately and comply with necessary formalities if any under the applicable laws. The Promoter shall not be responsible towards any third party making payment/remittances on behalf of any Allottee and such third party shall not have any right in the application/allotment of the said apartment applied for herein in any way and the Promoter shall be issuing the payment receipts in favour of the Allottee only.

  • Liability for Failure to Stop Payment of Preauthorized Transfer If you order us to stop one of these payments 3 business days or more before the transfer is scheduled, and we do not do so, we will be liable for your losses or damages.

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