We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

Participant’s Users and System Access Policies Sample Clauses

Participant’s Users and System Access Policies. Each Participant shall have written policies and procedures in place that govern its Participant Users’ ability to access information on or through the Participant’s System and through the Network (“Participant Access Policies”). Each Participant acknowledges that Participant Access Policies will differ among them as a result of differing Applicable Law and business practices. At a minimum, each Participant shall ensure that it has a valid and enforceable written agreement with each of its Participant Users, and/or policies and procedures that Participant Users are required to comply with, that ensure that any Health Data accessed by its Participant Users is: (i) for a Permitted Purpose; (ii) supported by appropriate legal authority for obtaining the Health Data; (iii) requested and viewed by a Participant User with the legal authority to have such access, and (iv) as soon as reasonably practicable after determining that a Breach occurred, report such Breach to the Participant. Further, each Participant shall employ a process for identity proofing that meets or exceeds National Institutes of Standards and Technology (NIST) Level 3 requirements in effect as of the date of execution of this Agreement by which the Participant, or its designee, validates sufficient information to uniquely identify each person seeking to become a Participant User prior to issuing credentials that would grant the person access to the Participant’s System. Participant is solely responsible for authenticating Participant’s own Participant Users for that access. Each Participant represents that it shall have the ability to monitor and audit all access to and use of its System related to this Agreement, for system administration, security, and other legitimate purposes. Each Participant agrees to enforce the provisions of this Agreement including but not limited to any provisions regarding limitations on Permitted Purposes for access to the Health Data and any confidentiality provisions of this Agreement by appropriately training all Participant Users, and disciplining individuals within each Participant’s organization who violate such provisions pursuant to each Participant’s respective Participant Access Policies. Participant shall also require that its Participant Users keep on file any signed patient authorization or consent forms that may be required for documentation regarding access to Health Data from the Network, as well as any documentation of emergency accesses of Health ...
Sample 1Sample 2Sample 3See All (4)

Related to Participant’s Users and System Access Policies

  • System Access CUSTOMER agrees to provide to PROVIDER, at CUSTOMER’S expense, necessary access to the mainframe computer and related information technology systems (the “System”) on which CUSTOMER data is processed during the times (the “Service Hours”) specified in the PSAs, subject to reasonable downtime for utility outages, maintenance, performance difficulties and the like. In the event of a change in the Service Hours, CUSTOMER will provide PROVIDER with at least fifteen (15) calendar days written notice of such change.

  • System Upgrade Facilities and System Deliverability Upgrades Connecting Transmission Owner shall design, procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Appendix A hereto. The responsibility of the Developer for costs related to System Upgrade Facilities and System Deliverability Upgrades shall be determined in accordance with the provisions of Attachment S to the ISO OATT.

  • System Access Control Data processing systems used to provide the Cloud Service must be prevented from being used without authorization.

  • Agreements with Employees and Subcontractors Grantee shall have written, binding agreements with its employees and subcontractors that include provisions sufficient to give effect to and enable Grantee’s compliance with Grantee’s obligations under this Article VI, Intellectual Property.

  • Switching System Hierarchy and Trunking Requirements For purposes of routing PNG traffic to Verizon, the subtending arrangements between Verizon Tandem Switches and Verizon End Office Switches shall be the same as the Tandem/End Office subtending arrangements Verizon maintains for the routing of its own or other carriers’ traffic (i.e., traffic will be routed to the appropriate Verizon Tandem subtended by the terminating End Office serving the Verizon Customer). For purposes of routing Verizon traffic to PNG, the subtending arrangements between PNG Tandem Switches and PNG End Office Switches shall be the same as the Tandem/End Office subtending arrangements that PNG maintains for the routing of its own or other carriers’ traffic.

  • Service Level Agreements If a Service or a Plan includes a Service Level Agreement (‘SLA’): (a) we are liable for any remedy or rebate allowed to you under the SLA; and (b) subject to clauses 34 to 38, and to the express terms of the SLA, our liability for breach of the SLA is limited to such remedy or rebate.

  • Benchmarks for Measuring Accessibility For the purposes of this Agreement, the accessibility of online content and functionality will be measured according to the W3C’s Web Content Accessibility Guidelines (WCAG) 2.0 Level AA and the Web Accessibility Initiative Accessible Rich Internet Applications Suite (WAI-ARIA) 1.0 for web content, which are incorporated by reference.

  • Service Level Agreement 6.1 NCR Voyix will use commercially reasonable efforts to make the Service available to you at or above the Availability Rate set forth at xxxxx://xxx.xxx.xxx/support/aloha-sla. If NCR Voyix does not meet the Availability Rate, you are entitled to request a service-level credit subject to the terms of this Agreement. This credit is calculated as a percentage of the monthly recurring bill (or monthly pro rata share of billing, if billing does not occur monthly) for the Service for the month in which the Availability Rate was not met. The Availability Rate is determined by: (a) dividing the total number of valid outage minutes in a calendar month by the total number of minutes in that month; (b) subtracting that quotient from 1.00; (c) multiplying that difference by 100; and (d) rounding that result to two decimal places in accordance with standard rounding conventions. The number of outage minutes per day for a given service is determined by the lesser of the number of outage minutes. 6.2 Unavailability due to other conditions or caused by factors outside of NCR Voyix’s reasonable control will not be included in the calculation of the Availability Rate. Further, the following are expressly excluded from the calculation of the Availability Rate: (a) service unavailability affecting services or application program interfaces that are not used by you; (b) cases where fail-over to another data center is available but not utilized; (c) transient time-outs, required re-tries, or slower-than-normal response caused by factors outside of NCR Voyix’s reasonable control; (d) Scheduled Downtime, including maintenance and upgrades; (e) force majeure; (f) transmission or communications outages outside the NCR Voyix- controlled environment; (g) store-level down-time caused by factors outside of NCR Voyix’s reasonable control; (h) outages attributable to services, hardware, or software not provided by NCR Voyix, including, but not limited to, issues resulting from inadequate bandwidth or related to third-party software or services; (i) use of the Service in a manner inconsistent with the documentation for the application program interface or the NCR Voyix Product; (j) your Point of Sale (“POS”) failure or the failure to properly maintain the POS environment, including updating the POS firmware or version of the software running on the POS as recommended by either NCR Voyix, a third-party POS reseller or servicer; and (k) issues related to third party domain name system (“DNS”) errors or failures. 6.3 To obtain a service-level credit, you must submit a claim by contacting NCR Voyix through the website at xxxxx://xxx.xxx.xxx/support/aloha-sla Your failure to provide the claim and other information will disqualify you from receiving a credit. NCR Voyix must receive claims within 60 days from the last day of the impacted month. After that date, claims are considered waived and will be refused. You must be in compliance with the Agreement in order to be eligible for a service-level credit. You may not unilaterally offset for any performance or availability issues any amount owed to NCR Voyix. If multiple Services experience an outage in a given month, the total credit for that month will be the highest credit allowed for any single Service which failed; there is no stacking of credits. 6.4 The remedies set forth in the Section are your sole and exclusive remedies for performance or availability issues affecting the Services, including any failure by NCR Voyix to achieve the Availability Rate.

  • Use of Basement and Service Areas The basement(s) and service areas, if any, as located within the

  • Contractor’s Employees and Subcontractors (a) Contractor shall only disclose PII to Contractor’s employees and subcontractors who need to know the PII in order to provide the Services and the disclosure of PII shall be limited to the extent necessary to provide such Services. Contractor shall ensure that all such employees and subcontractors comply with the terms of this DPA. (b) Contractor must ensure that each subcontractor performing functions pursuant to the Service Agreement where the subcontractor will receive or have access to PII is contractually bound by a written agreement that includes confidentiality and data security obligations equivalent to, consistent with, and no less protective than, those found in this DPA. (c) Contractor shall examine the data security and privacy measures of its subcontractors prior to utilizing the subcontractor. If at any point a subcontractor fails to materially comply with the requirements of this DPA, Contractor shall: notify the EA and remove such subcontractor’s access to PII; and, as applicable, retrieve all PII received or stored by such subcontractor and/or ensure that PII has been securely deleted and destroyed in accordance with this DPA. In the event there is an incident in which the subcontractor compromises PII, Contractor shall follow the Data Breach reporting requirements set forth herein. (d) Contractor shall take full responsibility for the acts and omissions of its employees and subcontractors. (e) Contractor must not disclose PII to any other party unless such disclosure is required by statute, court order or subpoena, and the Contractor makes a reasonable effort to notify the EA of the court order or subpoena in advance of compliance but in any case, provides notice to the EA no later than the time the PII is disclosed, unless such disclosure to the EA is expressly prohibited by the statute, court order or subpoena.

Most Referenced Clauses

Most Referenced Definitions