Data Management System Clause Samples

Data Management System. The Contractor must: i. Verify the accuracy and reliability of data entry. ii. Use data for monitoring purposes on compliance and quality indicators. iii. Use data for program improvement. iv. Support provider agencies in adding new users. v. Ensure eligibility and IFSP events are entered in the DMS within ten (10) business days of the completed activity and no later than the fifth (5th) of the following month. vi. Ensure that all EIS Providers complete the COS Decision Tree Survey on a quarterly basis.

Data Management System. To ensure consistent and effective ▇▇▇ management, SADES-K will use an online data management hub to gather, process, and report on data. In coordination with key technical staff and partners, the remote ▇▇▇ team will be responsible for ensuring all indicator data is entered into a SharePoint-based online data management system that FHI 360 has effectively used for multiple civil society and media programs. The system will allow SADES-K activities to be coded against SCS Global cross-cutting themes, funding streams, and objectives; map relevant indicators and interventions; and generate automated disaggregation reports. This will contribute to the DRG Center’s information sharing and learning across programs of similar thematic focus, allowing SADES-K to pull best practices and lessons learned from other programs. Data uploaded through SharePoint is aggregated on a project dashboard which will allow SADES-K to provide real-time updates on the programs progress. Moreover, it will allow program staff to monitor key performance indicators, analyze and visualize data to make management decisions, and communicate progress to stakeholders. Partners and grantees will receive varying levels of access to the database, allowing them to submit indicator data and view data based on differing restrictions.

Data Management System. The Other Party must: 1) Enter accurate, valid, and reliable data in the DMS no later than ten (10) business days following an event and in no case later than the fifth (5th) of the following month. 2) Enter the following required data in the DMS to maintain each child’s Part C of IDEA electronic record: i. All referrals; ii. All evaluation/assessments; iii. All Eligibility criteria; iv. Identification of FRC in the DMS at least one (1) business day prior to the FRC’s first meeting with the family; v. IFSPs, including documenting programmatic reasons and exceptional family circumstances resulting in delay in holding timely IFSP meetings (e.g. Initial IFSP meeting within forty-five (45) days from referral; IFSP review at least once every six

Data Management System. 2.2.1 All licensees will be required to sign up with ICIX North America, LLC. This service is utilized for maintenance of QA documentation including but not limited to plant audits, product specifications, letters of guarantee and certificates of insurance. 2.2.2 The current annual cost of the program to the licensee is approximately $299. Program membership includes the ability to upload requested documentation to all participating ICIX customers as allowed by vendor.

Data Management System. The Contractor must ensure subcontractors: (1) Enter accurate, valid and reliable data in the DMS no later than ten (10) business days following an event and in no case later than the fifth (5th) of the following month. (2) Enter the following required data in the DMS to maintain each child’s Part C of IDEA electronic record: (a) All referrals; (b) All evaluation/assessments; (c) All Eligibility criteria; (d) Identification of FRC in the DMS at least one (1) business day prior to the FRC’s first meeting with the family; (e) IFSPs, including documenting programmatic reasons and exceptional family circumstances resulting in delay in holding timely IFSP meetings (e.g. Initial IFSP meeting within forty-five (45) days from referral; IFSP review at least once every six (6) months or more frequently as needed; annual IFSP within 365 days of initial IFSP), and IFSP amendment when adding or changing services, including frequency, intensity, or duration; Initiation of services within thirty (30) days of the parent’s signature, including documenting programmatic reasons and exceptional family circumstances resulting in reasons for delay; (f) Initiation of services within thirty (30) calendar days of the parent’s signature, or the planned start date, including documenting programmatic reasons and exceptional family circumstances resulting in reasons for delay; (g) Child Outcome Summary (COS) entry and exit data reporting; (h) Transition activities: i. Transition steps and services in the IFSP Transition plan; ii. Date transition conference was held or declined; iii. Potential eligibility for Part B services in the child’s transition tab in the DMS by the first (1st) and fifteenth (15th) of every month for children between twenty-four (24) and thirty- two (32) months of age. If the child turns 32 months old after the fifteenth (15th) of the month, potential eligibility must be indicated before the first (1st) of the following month; and (i) Verify quarterly, and update as needed, the name of the local school district(s) contact person who needs to receive the school district(s) notification. (j) Enter data in the DMS to maintain a current list of all EIS staff and subcontractors including which discipline they represent, if they have current licensure/certification, and their FTE, and submit quarterly to the CLA on the form provided by the DCYF. (k) Ensure all EIS staff and subcontractors using the DMS receive the required training before assuming these duties and that...

Data Management System. If a study consists of different parts which are in the responsibility of different partners it may be advisable to establish a data management system, this should be described here as well as the main functionalities and access rights. Timing of data transfer between the partners should also be described here.

Data Management System. The Contractor must ensure subcontractors: (1) Enter accurate, valid, and reliable data in the DMS no later than ten (10) business days following an event and in no case later than the fifth (5th) of the following month.

Data Management System