Auditable Events Sample Clauses

The Auditable Events clause establishes the requirement for parties to maintain records of specific actions or transactions that may be subject to review or inspection. In practice, this clause typically obligates one or both parties to document activities such as financial transactions, data access, or system changes, and to make these records available for audit by the other party or a designated third party upon request. Its core function is to ensure transparency and accountability, enabling verification of compliance with contractual obligations and helping to detect or prevent errors, fraud, or misuse.
Auditable Events. Each Participant shall utilize the security policy established by the QHIN with whom the Participant has a signed a Participant-QHIN Agreement to identify a set of auditable events. Said security policy shall be consistent with the QHIN’s security policy but with appropriate modifications based on the transactions being performed. Each Participant’s security policy shall include the following auditing requirements for each Exchange Purpose that it performs: (i) A list of auditable events described in said security policy; (ii) An audit log including records for all auditable events identified by said security policy. A Participant shall retain all audit logs (both electronic and non-electronic) in accordance with Applicable Law and make such audit logs available during any audit; and (iii) A record of an auditable event which at a minimum should include the following information: • The description of the event; • The date and time the event occurred; • A success or failure indicator; and • Where appropriate, the identity of the entity and/or operator that was responsible for the event.
View SourceView Similar (4)
Auditable Events. Each QHIN shall abide by the auditable events requirements described in the QHIN Technical Framework. Additionally, each QHIN’s security policy shall include the following auditing requirements for each Exchange Purpose that it performs: (i) Auditable events as required by the QHIN Technical Framework; (ii) An audit log including records for all auditable events required by the QHIN Technical Framework. A QHIN shall retain all audit logs (both electronic and non-electronic) in accordance with Applicable Law and make such audit logs available during any audit; and (iii) A record of an auditable event which at a minimum should include the following information: • The description of the event; • The date and time the event occurred; • A success or failure indicator; and (where appropriate) • The identity of the entity and/or operator that was responsible for the event.
View SourceView Similar (2)

Related to Auditable Events

  • Reportable Events No such Employee Benefit Plan which is an Employee Pension Benefit Plan has been completely or partially terminated or been the subject of a Reportable Event as to which notices would be required to be filed with the PBGC. No proceeding by the PBGC to terminate any such Employee Pension Benefit Plan has been instituted or threatened; and

  • Reporting of Reportable Events If ▇▇▇▇▇ determines (after a reasonable opportunity to conduct an appropriate review or investigation of the allegations) through any means that there is a Reportable Event, ▇▇▇▇▇ shall notify OIG, in writing, within 30 days after making the determination that the Reportable Event exists.

  • ERISA Reportable Event A reportable event with respect to a Guaranteed Pension Plan within the meaning of §4043 of ERISA and the regulations promulgated thereunder as to which the requirement of notice has not been waived.

  • Reportable Events Involving the ▇▇▇▇▇ Law Notwithstanding the reporting requirements outlined above, any Reportable Event that involves solely a probable violation of section 1877 of the Social Security Act, 42 U.S.C. §1395nn (the ▇▇▇▇▇ Law) should be submitted by Practitioner to CMS through the self-referral disclosure protocol (SRDP), with a copy to the OIG. If Practitioner identifies a probable violation of the ▇▇▇▇▇ Law and repays the applicable Overpayment directly to the CMS contractor, then Practitioner is not required by this Section III.G to submit the Reportable Event to CMS through the SRDP.

  • Uncontrollable Events BISYS assumes no responsibility hereunder, and shall not be liable for any damage, loss of data, delay or any other loss whatsoever caused by events beyond its reasonable control.