Security and Archival of Data Sample Clauses

Security and Archival of Data. ‌ The EDC system is hosted by Medidata; the data are stored at Medidata’s primary data center in Houston, Texas, with fail-safe data centers in New Jersey. Data are regularly backed up by Medidata. Medidata maintains 21 CFR Part 11-compliant electronic systems, with procedures in place to safeguard against unauthorized acquisition of data. Any authorized communication with the Medidata servers at the Houston Data Center is conducted via SSL (128-bit) encryption. Robust password procedures, consistent with 21 Part 11, are in place. Robust physical security procedures are in place at the Houston Data Center to prevent unauthorized personnel physical access to the server rooms. EDC account access is maintained and monitored by the Biostatistics and Clinical Data Management group of the TDNCC. Other databases will be stored on Seattle Children’s servers and are safeguarded against unauthorized access by established security procedures. Network accounts are password protected and maintained and monitored by Seattle Children’s. Data is backed up regularly according to the Information Services group’s procedures. Note that there is an intention to make biospecimens and associated data available to investigators for future exploration. The biospecimens will be collected under IRB approval, processed according to a rigorous standard operating procedure and stored at a central facility, with appropriate procedures to enable long term, stable storage. Researchers may apply, via a standardized process, for use of de-identified data and specimens for research purposes. Applications will undergo a scientific review process administered through CFFT. When applying for use of data or specimens, the applicant must agree to: (1) use the data and specimens only for research purposes and to not make any attempts to try to identify any individual subject; (2) securing the data and specimens using appropriate methods; and (3) destroy or return the data (and specimens) in accordance with the specimen/data use agreement after analyses are completed. Before data or specimens will be released to an investigator, documentation of IRB exemption or approval from their institution must be provided to the CFFT.
Sample 1
AutoNDA by SimpleDocs
Security and Archival of Data. ‌ The EDC system is hosted by Medidata; the data are stored at Medidata’s primary data center in Houston, Texas, with fail-safe data centers in New Jersey. Data are regularly backed up by Medidata and stored with Iron Mountain. Medidata maintains 21 CFR Part 11-compliant electronic systems, with procedures in place to safeguard against unauthorized acquisition of data. Any authorized communication with the Medidata servers at the Houston Data Center is conducted via SSL (128-bit) encryption. Robust password procedures, consistent with 21 Part 11, are in place. Robust physical security procedures are in place at the Houston Data Center to prevent unauthorized personnel physical access to the server rooms. EDC account access is maintained and monitored by the Biostatistics and Clinical Data Management unit at the TDNCC Other databases will be stored on Seattle Children’s servers and are safeguarded against unauthorized access by established security procedures. Network accounts are password protected and maintained and monitored by the Seattle Children’s Information Services group. Data is backed up regularly according to the Information Technology group’s procedures.
Sample 1

Related to Security and Archival of Data

  • Security and Data Privacy Each party will comply with applicable data privacy laws governing the protection of personal data in relation to their respective obligations under this Agreement. Where Siemens acts as Customer’s processor of personal data provided by Customer, the Data Privacy Terms available at xxxxx://xxx.xxxxxxx.xxx/dpt/sw, including the technical and organizational measures described therein, apply to the use of the relevant Learning Services and are incorporated herein by reference.

  • Removal of Data County PHI or PI must not be removed from the premises of the Contractor except with express written permission of County.

  • System Security and Data Safeguards When SAP is given access to Licensee’s systems and data, SAP shall comply with Licensee’s reasonable administrative, technical, and physical safeguards to protect such data and guard against unauthorized access. In connection with such access, Licensee shall be responsible for providing Consultants with user authorizations and passwords to access its systems and revoking such authorizations and terminating such access, as Licensee deems appropriate from time to time. Licensee shall not grant SAP access to Licensee systems or personal information (of Licensee or any third party) unless such access is essential for the performance of Services under the Agreement. The parties agree that no breach of this provision shall be deemed to have occurred in the event of SAP non-conformance with the aforementioned safeguard but where no personal information has been compromised.

  • Source of Data A description of (1) the process used to identify Paid Claims in the Population and (2) the specific documentation relied upon by the IRO when performing the Claims Review (e.g., medical records, physician orders, certificates of medical necessity, requisition forms, local medical review policies (including title and policy number), CMS program memoranda (including title and issuance number), Medicare carrier or intermediary manual or bulletins (including issue and date), other policies, regulations, or directives).‌‌‌

  • Security of Data a. Each of the parties shall:

  • Protection of Customer Data The Supplier shall not delete or remove any proprietary notices contained within or relating to the Customer Data. The Supplier shall not store, copy, disclose, or use the Customer Data except as necessary for the performance by the Supplier of its obligations under this Call Off Contract or as otherwise Approved by the Customer. To the extent that the Customer Data is held and/or Processed by the Supplier, the Supplier shall supply that Customer Data to the Customer as requested by the Customer and in the format (if any) specified by the Customer in the Call Off Order Form and, in any event, as specified by the Customer from time to time in writing. The Supplier shall take responsibility for preserving the integrity of Customer Data and preventing the corruption or loss of Customer Data. The Supplier shall perform secure back-ups of all Customer Data and shall ensure that up-to-date back-ups are stored off-site at an Approved location in accordance with any BCDR Plan or otherwise. The Supplier shall ensure that such back-ups are available to the Customer (or to such other person as the Customer may direct) at all times upon request and are delivered to the Customer at no less than six (6) Monthly intervals (or such other intervals as may be agreed in writing between the Parties). The Supplier shall ensure that any system on which the Supplier holds any Customer Data, including back-up data, is a secure system that complies with the Security Policy and the Security Management Plan (if any). If at any time the Supplier suspects or has reason to believe that the Customer Data is corrupted, lost or sufficiently degraded in any way for any reason, then the Supplier shall notify the Customer immediately and inform the Customer of the remedial action the Supplier proposes to take. If the Customer Data is corrupted, lost or sufficiently degraded as a result of a Default so as to be unusable, the Supplier may: require the Supplier (at the Supplier's expense) to restore or procure the restoration of Customer Data to the extent and in accordance with the requirements specified in Call Off Schedule 8 (Business Continuity and Disaster Recovery) or as otherwise required by the Customer, and the Supplier shall do so as soon as practicable but not later than five (5) Working Days from the date of receipt of the Customer’s notice; and/or itself restore or procure the restoration of Customer Data, and shall be repaid by the Supplier any reasonable expenses incurred in doing so to the extent and in accordance with the requirements specified in Call Off Schedule 8 (Business Continuity and Disaster Recovery) or as otherwise required by the Customer. Confidentiality

  • Data Security and Privacy 12.1 SERVICE PROVIDER acknowledges the importance of Data Security and agrees to adhere to the Terms and Conditions of the Data Security Policy of IIMC.

  • Protection of Data The Contractor agrees to store Data on one or more of the following media and protect the Data as described:

  • Security and Privacy 3. Security and privacy policies for the Genesys Cloud Service addressing use of Customer Data, which are incorporated by reference, are located at xxxxx://xxxx.xxxxxxxxxxx.xxx/articles/Genesys Cloud-security-compliance/.

  • Information Integrity and Security Contractor shall immediately notify County of any known or suspected breach of personal, sensitive and confidential information related to Contractor’s work under this Agreement.

Time is Money Join Law Insider Premium to draft better contracts faster.