Data Collection and Management. 3.1. To optimise the experience for users of our website and ARE members, we use the following sections and third-party services to collect data from our visitors and members.
4.2. By agreeing to this privacy policy, you guarantee that the personal data you have provided, are complete and correct.
4.3. By agreeing to this privacy policy, partners that provide personal data of third parties (e.g. their employees, members, board members, staff, subcontractors, and contracting parties) to ARE guarantee that (i) these personal data are lawfully obtained and (ii) that the partner is authorised to transfer these personal data to ARE. These partners will comply with the Privacy Legislation. These partners will indemnify ARE against, hold ARE harmless against and shall compensate ARE for all claims that would result from non-compliance with the abovementioned guarantees and Privacy Legislation.
Data Collection and Management. A. Program Participant Data Collection
1. Grantee must collect unduplicated participant demographic information (age, sex, ethnicity, and race) for each onsite, in-classroom direct education series included in the Grantee approved State Plan regardless of number of sessions in the series to provide actual counts in the Annual Education and Administration Reporting System (EARS)
Data Collection and Management. Participating States and Purchasing Entities will have the ability to capture and display transaction data as made available from the merchant; as well as overall Purchase Card program information. Below are the transaction data and card acceptance requirements.
3.1 System will capture and display transaction data at the following minimum levels: ▪ Cardholder ▪ Approving official ▪ Entity office or unit ▪ Account/billing (available at different levels) ▪ Entity Program Administrator or alternates (available at different levels) ▪ Participating State (all state entity transactional data, statewide administrative level and compliance review group)
3.2 System will have the ability to view transaction authorization/declines in real time.
3.3 System will post transactions within twenty-four (24) to forty-eight (48) hours of receipt from merchant.
3.4 System will have the ability to capture and display Level 1, Level 2, and Level 3 transaction data as made available from the merchant.
3.5 System will allow for Users to add notes, comments, and additional descriptions to a transaction in a separate field. This field must: ▪ Allow for alpha, numeric, and special characters. ▪ Be searchable ▪ Be reportable ▪ Be accessible to all hierarchies within the system
3.6 System will be able to capture and display merchant Tax Identification Number (TIN).
3.7 System will allow for user to input a minimum of 150 character of Entity defined accounting code structure/segments at the transaction level.
3.8 System will allow for the Purchasing Entity to set requirements for accounting code segments (i.e. mandatory, non-mandatory, etc.)
3.9 System will allow for Purchasing Entity to define, edit, maintain, and upload valid value tables for each accounting code segment.
3.10 System will actively validate accounting segment data against valid value table data as determined by the Purchasing Entity.
3.11 System will allow for Program Administrator to assign, edit, and delete "default" accounting codes for all program hierarchies within the Purchasing Entity.
3.12 System will allow for User to save and edit frequently used accounting codes.
3.13 System will allow for a minimum of 99 accounting code splits per transaction.
3.14 System will allow for User to manually enter tax detail at the transaction level.
3.15 System will allow Program Administrator to download the entire Purchase Card number for use in other systems.
3.16 Participating States and Purchasing Entities have a need to ...
Data Collection and Management. 12.1. In connection with providing the Service, OmboriGrid, its Affiliates, and/or Approved Partners will collect, store, and process Customer Data, where such collection, storage and processing is necessary to provide, develop or improve the Service, or to allow OmboriGrid and/or its Affiliates to fulfil its obligations under this Agreement. The Customer shall have sole responsibility for the legality, reliability, integrity, accuracy and quality of the Customer Data, as well as its compliance with this Agreement and the Acceptable Use Policy and warrants that it has all rights, consents and approvals necessary to submit any Customer Data for the aforementioned purposes. Any and all Customer Data, which, in OmboriGrid’s sole discretion, infringes applicable laws, this Agreement, or the Applicable Use Policy, may be deleted by OmboriGrid without prior notice.
12.2. The Customer shall indemnify and hold OmboriGrid harmless from and against any damages, claims, losses and costs resulting from offensive, unlawful or objectionable Customer Data and shall indemnify and hold OmboriGrid harmless and defend or settle any claim suit or proceeding brought against OmboriGrid that is based upon a claim that any part of the Customer Data infringes any third-party intellectual property rights.
12.3. The Customer agrees and acknowledges that OmboriGrid, its Affiliates and Approved Partners have the right to create, obtain, collect, store, process and use Derived Data. All rights, title and interest in relation to Derived Data will be exclusively retained by OmboriGrid. OmboriGrid, its Affiliates and Approved Partners may freely use, amend or share any Derived Data for their business purposes as they deem fit, including, but not limited to, for the purpose of developing and improving the Service. Derived Data will not contain any Personal Data and OmboriGrid will not use the Derived Data in a way, which identifies the Customer or any User. The Customer acknowledges and agrees that OmboriGrid will not provide any copies of or information about Derived Data to the Customer, and that OmboriGrid may retain Derived Data upon termination of an Account, the Service, this Agreement, or otherwise.
Data Collection and Management. 3.1. To optimise the experience for users of our website and ARE members, we use the following sections and third-party services to collect data from our visitors and members.
Data Collection and Management. In order to build the strong technical foundation necessary to achieve the Guiding Principles, several technical teams were formed. Among those technical teams is the Data, Monitoring and Investigations Team (“DMIT”). The primary goal of the DMIT is to ensure that available hydrologic, environmental, and other pertinent data collected throughout the region is of a quality that can be used for the CFWI and is identified, inventoried, and accessible to support the CFWI technical initiatives and CFWI regulatory activities. As part of the Districts’ continuing coordination within the CFWI, the Districts commit to continuing their participation on the DMIT through appropriate technical staff. In order to further the goal of the DMIT, the Districts also agree to cooperate as follows:
Data Collection and Management. In order to track record for both outputs and outcomes indicators, a numbers of M&E tools will be used. These tools and techniques include; surveys, questionnaires, meeting records, most significant success stories, observations and so forth. The DFs and local coordinator will be provided with a template to provide their regular reports on dialogue activities, visitors to the Peace Libraries and mediation activities. The detailed process of data collection and management is as follows. Use Information for modifying the project activities if necessary Source (16 communities in 12 districts) Collection (DFs, Local Coordinators Reporting (This information will be reported to USAID team in bi-yearly basis)
Data Collection and Management. Reviewing IRB is not responsible for compliance with the requirements of any applicable federal, state, and local laws, rules, and regulations regarding electronic data management, including but not limited to: (1) the Privacy Rules at 45 CFR Part 146; and (2) rules governing electronic records at 21 CFR Part 11. Reviewing IRB is responsible only for providing the IRB Services and other obligations specified in Section I and accepts no additional responsibilities not herein described. Reviewing IRB certifies that they are an Association for the Accreditation of Human Research Protection Programs, Inc. (AAHRPP)-accredited IRB and will maintain an accreditation status of “Full Accreditation” throughout the term of this Agreement. Obligations of Relying Institution. For each research project, Relying Institution agrees to: Relying Institution agrees to submit an application to Reviewing IRB. Ensure investigators are appropriately qualified and meet Relying Institution’s standards for eligibility to conduct research including, but not limited to, completion of human subjects protection training, and collection and maintenance of conflicts of interest disclosure forms; Communicate to Reviewing IRB, on the IRB application for each research project, local context information, including requirements of any applicable state or local laws, regulations, institutional policies, standards, or other local factors relevant to each research project; Ensure compliance with Reviewing IRB’s determinations, provided there are no legal or policy concerns that would arise with compliance. In the event Relying Institution identifies legal or policy concerns that would arise with compliance, Relying Institution and Reviewing IRB shall address those concerns and make a good faith effort to resolve them. If Relying Institution’s concerns cannot be resolved in a mutually acceptable way, Relying Institution will withdraw its IRB application for that research project. Relying institution will also comply with all applicable federal, state, and local laws, rules, and regulations, including but not limited to: (1) 45 CFR Part 46, Subpart A (the Common Rule) governing protections for human research subjects; (2) the safety procedures specified in the Federal Food, Drug and Cosmetic Act at 21 U.S.C. § 301 et seq.; and (3) 21 CFR Parts 50, 56, 312, and 812 governing the review of research involving human subjects; Ensure appropriate monitoring of research and conduct internal checklists up...
Data Collection and Management. A representative from the GA DPH sent out emails with the survey link to labor and delivery nurse managers. Hospitals were reminded three times to complete the survey via email. Reminder emails were delivered once a week for the first three weeks of data collection. If completion had not occurred after the third reminder, a representative from DPH called the nurse manager to determine if the hospital preferred to complete the survey via telephone. During the phone conversations, a member of the research team concurrently entered survey responses into the spreadsheet as they were answered. The survey addressed general hospital demographic information, such as number of delivery beds and type of newborn care unit, as well as the provider’s perceptions on newborn screening and the utility of the NBS Card (see Appendix D). In regards to the hospitals’ perceptions on the implementation of the Uniform Newborn Screening Specimen card, hospitals were asked a series of questions such as “do you feel the newborn screening improves the time to intervention for CCHD and hearing problems?” To address the hospital process of completing the NBS Card, hospitals were asked a series of questions, including “how would you describe the process for screening newborns in your hospital?” After completion of all online surveys and phone interviews, responses were verified for completion and the second entry of any duplicates were deleted. Data was stored using Microsoft Excel on a password protected computer. Responses were then analyzed using SAS 9.3 software. Overall univariate statistics were used to describe the distribution of each question across responding hospitals. Survey completion by hospital was noted for birth data to determine how representative the hospitals that completed the survey are compared to those that did not complete the survey.
Data Collection and Management. All interviews were digitally recorded with the consent of the participant. Two recording devices were used to ensure no data was lost to a poor recording or human error. When the interview was completed, the interviewer checked the quality of the recordings. After every interview, each tape was transcribed for data analyses. Interviews that were conducted in Spanish were transcribed into English by RSS. Transcripts excluded personal identifying information (PII) including names, locations, and other characteristics that could reveal the identity of interviewees, their partners, their providers, and clinics and care locations. All materials, including recording devices, consent forms, and interview guides, were then transferred to locked cabinets in secure locations. All PII from the screening process was maintained on paper and kept in separate locked cabinets from other data. All transcripts, without PII, were kept on encrypted key drives. Codes were initially developed from their corresponding questions on the interview guide. Team members reviewed transcripts to further develop codes and categories and to identify emerging themes. In order to examine the coping strategies employed by the study participants for the secondary data analysis, the transcripts were also coded with Nvivo 11.0 with a new codebook.
