System Testing and Transfer of Data Sample Clauses

The "System Testing and Transfer of Data" clause defines the requirements and procedures for verifying that a system functions correctly and for securely transferring data between parties. Typically, this clause outlines the types of tests to be performed, the responsibilities of each party during testing, and the criteria for successful completion. It may also specify protocols for data migration, including timing, formats, and security measures. The core purpose of this clause is to ensure that the system meets agreed-upon standards before it goes live and that any data transfer is handled safely and efficiently, thereby minimizing operational risks and ensuring a smooth transition.
System Testing and Transfer of Data. The HMO must have hardware, software, network and communications systems with the capability and capacity to handle and operate all MIS systems and subsystems identified in Attachment B-1, Section 8.1.18. For example, the HMO’s MIS system must comply with the Health Insurance Portability and Accountability Act of 1996 (HIPAA) as indicated in Section 8.1.18.
View SourceView Similar (16)

Related to System Testing and Transfer of Data

  • Transfer of Data The Participant consents to the Company or any Affiliate thereof processing data relating to the Participant for legal, personnel, administrative and management purposes and in particular to the processing of any sensitive personal data relating to the Participant. The Company may make such information available to any Affiliate thereof, those who provide products or services to the Company or any Affiliate thereof (such as advisers and payroll administrators), regulatory authorities, potential purchasers of the Company or the business in which the Participant works, and as may be required by law.

  • Transfer or Deletion of Student Data The Provider shall review, on an annual basis, whether the Student Data it has received pursuant to the DPA continues to be needed for the purpose(s) of the Service Agreement and this DPA. If any of the Student Data is no longer needed for purposes of the Service Agreement and this DPA, the Provider will provide written notice to the LEA as to what Student Data is no longer needed. The Provider will delete or transfer Student Data in readable form to the LEA, as directed by the LEA (which may be effectuated through Exhibit D of the DPA), within 30 calendar days if the LEA requests deletion or transfer of the Student Data and shall provide written confirmation to the LEA of such deletion or transfer. Upon termination of the Service Agreement between the Provider and LEA, Provider shall conduct a final review of Student Data within 60 calendar days. If the LEA receives a request from a parent, as that term is defined in 105 ILCS 10/2(g), that Student Data being held by the Provider be deleted, the LEA shall determine whether the requested deletion would violate State and/or federal records laws. In the event such deletion would not violate State or federal records laws, the LEA shall forward the request for deletion to the Provider. The Provider shall comply with the request and delete the Student Data within a reasonable time period after receiving the request. Any provision of Student Data to the LEA from the Provider shall be transmitted in a format readable by the LEA.

  • Additional Acceptable Uses of Student Data Contractor is prohibited from using Student Data for any secondary use not described in this agreement except: a. for adaptive learning or customized student learning purposes; b. to market an educational application or product to a parent or legal guardian of a student if Contractor did not use Data, shared by or collected per this Contract, to market the educational application or product; c. to use a recommendation engine to recommend to a student i. content that relates to learning or employment, within the third-party contractor's internal application, if the recommendation is not motivated by payment or other consideration from another party; or

  • Procedures for Providing NP Through Full NXX Code Migration Where a Party has activated an entire NXX for a single Customer, or activated at least eighty percent (80%) of an NXX for a single Customer, with the remaining numbers in that NXX either reserved for future use by that Customer or otherwise unused, if such Customer chooses to receive Telephone Exchange Service from the other Party, the first Party shall cooperate with the second Party to have the entire NXX reassigned in the LERG (and associated industry databases, routing tables, etc.) to an End Office operated by the second Party. Such transfer will be accomplished with appropriate coordination between the Parties and subject to appropriate industry lead times for movements of NXXs from one switch to another. Neither Party shall charge the other in connection with this coordinated transfer.

  • Secure Information Handling and Transfers 7.1 Physical and electronic handling, processing and transferring of DWP Data, including secure access to systems and the use of encryption where appropriate.