Data Repository. The “Data Repository” shall mean the data repository(ies) and databases (not including the Licensed Software) that HCO will have access to as part of the Services.
Data Repository. Xx. Xxxxx/Sevitar asks for your permission to add data from your clinical record to a de-identified research database. The research database will not include your name, address, or any other information that could identify you. The database will be used for scientific research about the nature and causes of anxiety, depression, and other psychological difficulties; about the processes of change during treatment; and about the quality of our assessment tools, in order to improve our understanding of psychological difficulties and to improve our treatment of those difficulties. You do not have to give permission for your data to be used in research unless you want to. Declining to give permission will not affect your treatment with Xx. Xxxxx/Sevitar in any way. Because no identifying information will be added to the data repository, data cannot be withdrawn from the data repository once they are placed there. Your information will not be added to the data repository unless you initial this section.
Data Repository. (a) The Supplier will provide a secure web-based portal through which Hawaiian Telcom will be able to access online (i) electronic copies of all of the reports run on a periodic basis (so as to provide meaningful, actionable information), (ii) such raw data underlying such reports as to provide the auditability of the reports, and (iii) the other items described below in this Section 5.4.2 (the “Data Repository”).
(b) The Data Repository will include the following:
(i) a monthly extract or data feed of the asset inventory system the Supplier will use to manage and track the Software and Equipment that is the Supplier’s responsibility to track;
(ii) all operational documents and resources to which Hawaiian Telcom is to have access, including the Procedures Manual; and
(iii) all Work Orders, Change Orders and any other contract related documentation or correspondence between the Parties relating to the Services or the Agreement.
(c) The Data Repository will:
(i) be accessible by Hawaiian Telcom using a secure web site on a 24x365 basis (subject to reasonable amounts of planned maintenance outages Master Services Agreement 27 February 4, 2005 Hawaiian Telcom/Supplier CONFIDENTIAL within mutually agreed maintenance windows outside of Business Hours in Hawaii);
(ii) allow Hawaiian Telcom to carry out searches through the web portal across all of the Reports Data, including containing a search facility to easily locate documents by name, date, author, document number, location and other key words to be defined; and free form content searches and searching using multiple criteria;
(iii) allow Hawaiian Telcom to download any data stored within the Data Repository that would otherwise be provided to Hawaiian Telcom as part of the Supplier’s reporting obligations under this Agreement;
(iv) allow Hawaiian Telcom to generate any of the reports delivered to Hawaiian Telcom by the Supplier;
(v) allow Hawaiian Telcom to create new, ad hoc or recurring reports within the Data Repository using the web portal; and
(vi) provide versioning for documents stored in the Data Repository, including retaining all previously stored versions of the relevant document; enabling authorized Hawaiian Telcom Personnel to add new versions of particular documents; logging providing the date on which each version of the document was added, the version number and the document owner; indicating the version of the document on screen.
(d) The information, reports, and documents stored in the Data...
Data Repository. (a) manage specified projects approved by Enova to create tools and systems needed to link general ledger data with other business lines' financial systems in accordance with the architecture specification;
(b) manage specified project approved by Enova to create link between corporate and affiliate financial systems in accordance with the architecture specification;
(c) build and manage central repository of business objects for reuse and redeployment as specified in the architecture specification; and
(d) provide knowledge transfer and on-the-job training to Enova personnel through work performed jointly with Enova employees and contractors.
Data Repository. A computerized, secure electronic data and information 40 storage repository system controlled and maintained by the Régie and located within the 41 Province of Québec. Information, data and documents related to activities of the QCMEP 42 whether filed by a Registered Entity, or created or obtained by the Régie, NPCC, or NERC 43 are stored on the Data Repository. 44
Data Repository. An entity engaged in the accumulation and aggregation of clinical data for the purposes of measuring the clinical performance of health care practitioners, establishing normative standards of care, and/or demonstrating the quality of patient care.
Data Repository. Data and the associated metadata, documentation and code will be initially deposited in the repositories created by each SerIoT pilot. For example, AustriaTech will provide credentials to WP4 partners that need access to their datasets. HOPU will store data securely on a platform on the FIWARE and MongoDB architecture. Then, the dataset could be transferred to the SerIoT data repository (xxxxx://xxxxxxxx.xxx.xx/seriot), which is established by Partner CERTH (see Fig. 2).
Data Repository. If any research conducted by Novartis or any of its Affiliates, either alone or with a Novartis Collaboration Partner that has shared its Clinical Data with SomaLogic, is part of a study funded by a United States federal agency or similar government entity that has a data sharing policy to which Novartis, any of its Affiliates or any such Novartis Collaboration Partner must adhere that requires the integration into a public database of all or substantially all of the SOMAscan Data provided to Novartis under a Project Plan, Novartis or its Affiliates will not, and it will procure that any Novartis Collaboration Partner will not, to the extent permitted by the study’s data sharing policy, provide any SOMAscan Data to the data repository until the earlier to occur of [****] after completion of the applicable clinical study or other project or waive [****] after acceptance for publication of a primary manuscript describing the Novartis Results of the applicable clinical study or other project conducted by Novartis or any of its Affiliates, either alone or with any such Novartis Collaboration Partner. For the avoidance of doubt, any Novartis Collaboration Partner that has not shared its Clinical Data with SomaLogic will not be permitted to provide any SOMAscan Data to a data repository at any time unless such Novartis Collaboration Partner is subject to an obligation (naming SomaLogic as a third party beneficiary) that such Novartis Collaboration Partner will not file any Patents claiming Biomarkers discovered or created through the use of the SOMAscan Data.
Data Repository. If you agreed to participate in research, Dr. Xxxxxxx is additionally asking your permission to add data from your clinical record to the Oakland CBT Data Repository, a completely de- identified research database. This database differs from the standard research databases described above in that no participant ID code is maintained. The data repository database will not include your name, address, or any other information that could identify you. The data repository database will be used for scientific research about the nature and causes of anxiety, depression, and other psychological difficulties; about the processes of change during treatment; and about the quality of our assessment tools, in order to improve our understanding of psychological difficulties and to improve our treatment of those difficulties. More information about the data repository is provided in the attached document titled Description of the Oakland Cognitive Behavior Therapy Center Data Repository. You do not have to give permission for your data to be included in the Data Repository unless you want to. Declining to give permission will not affect your treatment with Dr. Persons in any way. If you agree to give permission to provide data for the Data Repository, you may withdraw permission by letting Dr. Persons know in writing. At that point, no further research data from your clinical record will be added to the database, but because the data are completely de-identified, it will not be possible to pull your data out of the data repository once they are placed there. Please do not initial here until after you and Dr. Persons review this section and you have had the opportunity to ask any questions you have about it. (initial) I have read and understood this agreement and the attached Patient Bill of Rights and Data Repository Description, and I have had my questions answered to my satisfaction. I accept, understand, and agree to abide by the contents and terms of this agreement and consent to participate in evaluation and/or treatment. Name of patient (please print): Signature of patient: Date: You have the right to: • Request and receive full information about the therapist’s professional capabilities, including licensure, education, training, experience, professional association membership, specialization, and limitations. • Have written information about fees, method of payment, insurance reimbursement, number of sessions, substitutions (in cases of vacation and emergencies), a...
Data Repository. The repository for archiving and retrieving Scribe project files is Xxxxxx.XXX. This repository resides within a national server maintained by ERT and is accessed directly from Scribe. For each project file, a unique ID is assigned at the time the file is first published to Xxxxxx.XXX. Access to the archived Scribe project file can be granted to other stakeholders, performing parties, and groups upon submitting a request to ERT; however, the repository files can only be updated from the computer that originated the file (unless the Scribe project file is relinquished by the originator in Scribe). Independent of the Xxxxxx.XXX repository, a site-wide repository being developed by the State of Oregon, will capture and provide access to comprehensive Portland Harbor site data.
