Verification of Safeguards Sample Clauses

Verification of Safeguards. Upon District’s written request, Contractor shall provide or make available to the District for review, the following, verifying Contractor’s administrative, physical and technical safeguards are in compliance with industry standards and best practices: (1) a third-party network security audit report, or (2) certification from Contractor indicating that an independent vulnerability or risk assessment of the Contractor’s data security program has occurred.
Sample 1Sample 2Sample 3See All (47)
AutoNDA by SimpleDocs
Verification of Safeguards. Upon District’s written request, Infinite Campus shall provide or make available to the District for review, the following, verifying Infinite Campus’ administrative, physical and technical safeguards are in compliance with industry standards and best practices: (1) a third-party network security audit report, or (2) certification from Infinite Campus indicating that an independent vulnerability or risk assessment of Infinite Campus’ data security program has occurred.
Sample 1Sample 2Sample 3See All (5)
Verification of Safeguards. Upon School’s written request, Contractor shall provide or make available to School for review, the following, verifying Contractor’s administrative, physical and technical safeguards are in compliance with industry standards and best practices: (1) a third-party network security audit report, or (2) certification from Contractor indicating that an independent vulnerability or risk assessment of the Contractor’s data security program has occurred.
Sample 1Sample 2Sample 3See All (4)
Verification of Safeguards. Upon CSDB’s written request, Contractor shall provide or make available to the CSDB for review, the following, verifying Contractor’s administrative, physical and technical safeguards are in compliance with industry standards and best practices: (1) a third-party network security audit report, or (2) certification from Contractor indicating that an independent vulnerability or risk assessment of the Contractor’s data security program has occurred.
Sample 1
Verification of Safeguards. Upon District’s written request, Contractor shall provide or make available to the District a third-party network security audit report no more than once per year.
Sample 1
Verification of Safeguards. Upon District’s written request, Contractor shall provide or make available to the District for review, one or more of the following, verifying Contractor’s administrative, physical and technical safeguards are in compliance with industry standards: (1) a third-party network security audit report; (2) certification from Contractor indicating that Contractor has conducted an internal assessment of its data security program against NIST standards, conducts third-party penetration testing, and reviews audit reports and certifications from Subcontractors regarding their data security program(s); (3) District Data has been de-identified by Contractor as set forth in the definition of De-identified Data in section 1.7 of this Addendum.
Sample 1

Related to Verification of Safeguards

  • Safeguards Business Associate, its Agent(s) and Subcontractor(s) shall implement and use appropriate safeguards to prevent the use or disclosure of PHI other than as provided for by this Agreement. With respect to any PHI that is maintained in or transmitted by electronic media, Business Associate or its Subcontractor(s) shall comply with 45 CFR sections 164.308 (administrative safeguards), 164.310 (physical safeguards), 164.312 (technical safeguards) and 164.316 (policies and procedures and documentation requirements). Business Associate or its Agent(s) and Subcontractor(s) shall identify in writing upon request from Covered Entity all of the safeguards that it uses to prevent impermissible uses or disclosures of PHI.

  • Security Safeguards Each party shall maintain appropriate administrative, physical, and technical safeguards for protection of the security, confidentiality and integrity of your Customer Content and any associated personal data that is collected and/or processed through the Services. On our part, those safeguards will include commercially reasonable measures designed to prevent unauthorized access, use, modification, deletion, and disclosure of Customer Content. Customer (not us) bears sole responsibility for adequate security, protection, and backup of Customer Content when in Customer’s or its representatives’ or agents’ possession or control.

  • Electronic Visit Verification ("EVV A. To ensure: 1. the EVV system is used to verify the provision of services governed under 40 TAC, Chapter 68 or its successor; 2. only authorized people access the Contractor's EVV account; 3. all data elements required by HHSC or HHSC's designee are uploaded or entered and maintained in the EVV system completely, accurately, and prior to submitting the claim; 4. that each time services governed by 40 TAC Chapter 68 or its successor are delivered to an individual, the Contractor's staff uses an HHSC-approved EVV system; and 5. service delivery documentation is immediately available for review by HHSC when requested. B. Equipment provided to Contractor by HHSC, HHSC’s designee, or an HHSC-approved EVV vendor, must be returned in good condition when the equipment is no longer needed under this Contract. In the context of this agreement, “good condition” means Contractor must not place any marks or identifying information on the equipment and may not alter information on the equipment including logos and serial numbers. If the equipment is lost, stolen, marked, altered or damaged by Contractor, Contractor may be required to pay the replacement cost for each piece of equipment that is lost, stolen, marked or damaged. Replacement costs for lost, stolen, marked or damaged equipment may be assessed periodically. If Contractor recovers previously lost or stolen equipment for which Contractor paid the replacement cost in the prior 12 months, Contractor may return the equipment and be reimbursed for the replacement costs within 12 months of the date HHSC, HHSC’s designee or an HHSC-approved EVV vendor (as applicable) received payment in full from the Contractor. This is provided the equipment is returned in good condition as specified above. C. HHSC may perform EVV compliance oversight reviews to determine if Contractor has complied with EVV compliance requirements as outlined in 40 TAC Chapter 68 or its successor, EVV Policy posted on the HHSC EVV website or EVV Policy Handbook. D. If the Contractor determines an electronic record in the EVV system needs to be adjusted at any time, the Contractor will make the adjustment in the EVV system using the most appropriate EVV reason code number(s), EVV reason code description(s) and enter any required free text when completing visit maintenance in the EVV system, if applicable. E. Contractor must begin using an HHSC-approved EVV system prior to submitting an EVV relevant claim. F. All claims for services required to use EVV (EVV claims) must match to an accepted EVV visit transaction in the EVV Aggregator (the state’s centralized EVV database) prior to reimbursement of an EVV claim. Without a matching accepted EVV visit transaction, the claim will be denied. G. Contractor must submit all EVV related claims through the Texas Medicaid Claims Administrator, or as otherwise described in the EVV Policy posted on the HHSC EVV website or in the EVV Policy Handbook. H. Contractor must complete all required EVV training as outlined in the EVV Policy posted on the HHSC EVV website or EVV Policy Handbook: • Prior to using either an EVV vendor system or an EVV proprietary system and • Yearly thereafter. I. Contractor and, if applicable, the Contractor’s appointed EVV system administrator, must complete, sign and date the EVV Onboarding Form as outlined in 40 TAC Chapter 68 or its successor, EVV Policy posted on the HHSC website or EVV Policy Handbook.

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