System Testing and Transfer of Data Sample Clauses

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.
AutoNDA by SimpleDocs

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.

  • Certification Regarding Prohibition of Certain Terrorist Organizations (Tex Gov. Code 2270) Certification Regarding Prohibition of Boycotting Israel (Tex. Gov. Code 2271) 5 Certification Regarding Prohibition of Contracts with Certain Foreign-Owned Companies (Tex. Gov. 5 Code 2274) 5 Certification Regarding Prohibition of Discrimination Against Firearm and Ammunition Industries (Tex.

  • Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-­‐to-­‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.

  • Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.

  • Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx Xxxxxxx Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

  • Form and Transfer of Receipts Definitive Receipts shall be engraved or printed or lithographed on steel-engraved borders, with appropriate insertions, modifications and omissions, as hereinafter provided, if and to the extent required by any securities exchange on which the Receipts are listed. Pending the preparation of definitive Receipts or if definitive Receipts are not required by any securities exchange on which the Receipts are listed, the Depositary, upon the written order of the Company or any holder of Stock, as the case may be, delivered in compliance with Section 2.2, shall execute and deliver temporary Receipts which are printed, lithographed, typewritten, mimeographed or otherwise substantially of the tenor of the definitive Receipts in lieu of which they are issued and with such appropriate insertions, omissions, substitutions and other variations as the persons executing such Receipts may determine, as evidenced by their execution of such Receipts. If temporary Receipts are issued, the Company and the Depositary will cause definitive Receipts to be prepared without unreasonable delay. After the preparation of definitive Receipts, the temporary Receipts shall be exchangeable for definitive Receipts upon surrender of the temporary Receipts at the Depositary’s Office or at such other place or places as the Depositary shall determine, without charge to the holder. Upon surrender for cancellation of any one or more temporary Receipts, the Depositary shall execute and deliver in exchange therefor definitive Receipts representing the same number of Depositary Shares as represented by the surrendered temporary Receipt or Receipts. Such exchange shall be made at the Company’s expense and without any charge to the holder therefor. Until so exchanged, the temporary Receipts shall in all respects be entitled to the same benefits under this Agreement, and with respect to the Stock, as definitive Receipts. Receipts shall be executed by the Depositary by the manual and/or facsimile signature of a duly authorized officer of the Depositary. No Receipt shall be entitled to any benefits under this Deposit Agreement or be valid or obligatory for any purpose unless it shall have been executed in accordance with the foregoing sentence. The Depositary shall record on its books each Receipt so signed and delivered as hereinafter provided. Receipts shall be in denominations of any number of whole Depositary Shares. The Company shall deliver to the Depositary from time to time such quantities of Receipts as the Depositary may request to enable the Depositary to perform its obligations under this Deposit Agreement. Receipts may be endorsed with or have incorporated in the text thereof such legends or recitals or changes not inconsistent with the provisions of this Deposit Agreement as may be required by the Depositary or required to comply with any applicable law or any regulation thereunder or with the rules and regulations of any securities exchange upon which the Stock, the Depositary Shares or the Receipts may be listed or to conform with any usage with respect thereto, or to indicate any special limitations or restrictions to which any particular Receipts are subject. Title to Depositary Shares evidenced by a Receipt, which is properly endorsed or accompanied by a properly executed instrument of transfer, shall be transferable by delivery with the same effect as in the case of a negotiable instrument; provided, however, that until transfer of a Receipt shall be registered on the books of the Depositary as provided in Section 2.3, the Depositary may, notwithstanding any notice to the contrary, treat the record holder thereof at such time as the absolute owner thereof for the purpose of determining the person entitled to distributions of dividends or other distributions or to any notice provided for in this Deposit Agreement and for all other purposes.

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