Common use of Storage, Transfer, and Maintenance of Information Clause in Contracts

Storage, Transfer, and Maintenance of Information. (a) The Information included in the Research Repository by each Participant, including Information from a Participant’s Data Contributor, will be stored locally by each Participant in its locally approved formats. (b) Assisted by software methods developed and shared by the GPC members, each Participant’s informatics team will create a Research Repository. (c) For each Patient Count Query, and each Approved Feasibility Query or Approved Research Project which Participant has Accepted, Participant will ETL those requested items of its Information into its Research Repository. (d) The GPC Infrastructure and Software Development Core will provide technical assistance to the Participant regarding ETL and data standardization processes required by this Agreement. (e) The Participant will refresh the Information within its Research Repository in a manner responsive to the needs of both (i) the Data Requestor and (ii) PCORNet as determined by the GPC Governing Council. During network development, the refresh frequency may vary, but by completion of phase 1 of the PCORI Subcontract, each Participant will refresh its Research Repository at least quarterly. The Participant, in accordance with Section 4.06(b), will also update the software versions used for its Research Repository to be complaint with GPC and PCORNet requirements as determined by the GPC Governing Council.

Storage, Transfer, and Maintenance of Information. (a) The Information included in the Research Repository by each Participant, including Information from a Participant’s Data Contributor, will be stored locally by each Participant in its locally approved formats. (b) Assisted by software methods developed and shared by the GPC members, each Participant’s informatics team will create a Research Repository. (c) For each Patient Count Query, and each Approved Feasibility Query or Approved Research Project which Participant has Accepted, Participant will ETL those requested items of its Information into its Research Repository. (d) The GPC Infrastructure and Software Development Core will provide technical assistance to the Participant regarding ETL and data standardization processes required by this Agreement. (e) The Participant will refresh the Information within its Research Repository in a manner responsive to the needs of both (i) the Data Requestor and (ii) PCORNet PCORnet as determined by the GPC Governing Council. During network development, the refresh frequency may vary, but by completion of phase 1 of the PCORI Subcontract, each Each Participant will refresh its Research Repository at least quarterly. The Participant, in accordance with Section 4.06(b), will also update the software versions used for its Research Repository to be complaint compliant with GPC and PCORNet PCORnet requirements as determined by the GPC Governing Council.