Automated Data System Clause Samples

The Automated Data System clause defines the use and management of automated systems for collecting, processing, and storing data within the scope of an agreement. Typically, this clause outlines the responsibilities of each party regarding the operation, maintenance, and security of such systems, and may specify standards for data accuracy, access controls, or system updates. Its core practical function is to ensure that both parties understand their obligations and the technical requirements for handling data, thereby reducing the risk of data mishandling or breaches and promoting operational efficiency.
Automated Data System. The Sponsor will utilize its existing automated reporting system to collect data required for various reports required by the Department of Education. The Sponsor agrees to provide necessary training and the School agrees to release appropriate staff for such training at mutually convenient times. Upon request of the Sponsor, the School agrees to enter the necessary data required for such reports into the Sponsor’s automated student data system, via electronic remote access with IBM- compatible hardware. The data elements shall include but not be limited to, the following: a. Demographic information; b. ESE data; c. Grade level assignment; d. Required health information; e. Required discipline codes/incident data; f. Daily attendance; g. Transportation; h. Student schedules; i. Teacher demographics; j. Master schedule; k. ESOL/migrant codes; l. Grades/grading period/grading scale; m. ERW (entry, re-entry, withdrawal information); n. Test scores; o. Academic history and transcripts; and p. Student lunch information as required.
View SourceView Similar (3)
Automated Data System. The Sponsor will utilize its existing autom ated 12 reporting system to collect data requi red for various reports required by the 13 Florida Department of Education. Upon request of the Sponsor, the School agrees 14 to enter the necessary data required for su ch reports into the Sponsor’s automated 15 student data system, via electronic remote access. By the 12th day of each school 16 term, the School will enter all inform ation required for enrollment of its students 17 into the Sponsor’s student inform ation system. The Sponsor will analyze the 18 School’s facility and develop a hardware /software solution which provides the 19 School with limited access to the Sponsor’s data processing facility. The School 20 will provide hardware and related infrastr uctures. The Sponsor will also provide 21 training for the School’s personnel in the us e of designated district applications 22 necessary to respond to the requirem ents of 1008.345, Florida Statute, including 23 the annual report and the state/district required assessm ent program. The
View SourceView Similar (3)
Automated Data System. The Sponsor will utilize its existing automated reporting system to collect data required for various reports required by the Department of Education. Upon request of the Sponsor, the School agrees to enter the necessary data required for such reports into the Sponsor’s automated student data system, via electronic remote access with IBM-compatible hardware. By the 12th day of each school term, the School will enter all information required for enrollment of its students into the Sponsor’s mainframe. The School may amend such data prior to the first FTE count. The data elements shall include but not be limited to the following:
View SourceView Similar (2)
Automated Data System. The Sponsor shall utilizeuse its existing automated reporting system to collect data required for various reports required by the FDOEFLDOE. The School agrees to enter the necessary data required for such reports into the Sponsor’s automated student data system, via electronic remote access with a Windows-compatible system. The School shall provide appropriate equipment for data entry. The Sponsor shall provide training on the automated system and data entry screens. The School shall employ trained personnel to enter and manage data for the School.
View Source
Automated Data System. The Sponsor will utilize its existing automated reporting system to collect data required for various reports required by the Department of Education. Upon request of the Sponsor, the School agrees to enter the necessary data required for such reports into the Sponsor’s automated student data system, via electronic remote access with IBM-compatible hardware. By the 12th day of each school term, the School will enter all information required for enrollment of its students into the Sponsor’s mainframe. The School may amend such data prior to the first FTE count. The data elements shall include but not be limited to the following: a. ESE data; b. Grade level assignment; c. Required health information; d. Required discipline codes/incident data; e. Daily attendance; f. Transportation; g. Student schedules; h. Teacher demographics; i. Master schedule; j. ESOL/migrant codes; k. Grades/grading period/grading scale; l. ERW (entry, re-entry, withdrawal) information; m. Test scores; n. Demographic information; o. Academic history and transcripts; p. Student lunch information as required, including a listing of students eligible for free and reduced meals, with supporting documentation.
View Source
Automated Data System. The Sponsor will utilize its existing automated reporting sys- tem to collect data required for various reports required by the Florida Department of Education. Upon request of the Sponsor, the School agrees to enter the necessary data required for such re- ports into the Sponsor’s automated student data system, via electronic remote access. By the 12th day of each school term, the School will enter all information required for enrollment of its stu- dents into the Sponsor’s student information system. The Sponsor will analyze the School’s fa- cility and develop a hardware/software solution which provides the School with limited access to the Sponsor’s data processing facility. The School will provide hardware and related infrastruc- tures. The Sponsor will also provide training for the School’s personnel in the use of designated district applications necessary to respond to the requirements of 1008.345, Florida Statute, in- cluding the annual report and the state/district required assessment program. The Sponsor’s sup- port for this function will be provided and not exceed the administrative fee provided in the law. Access by the School to additional data processing applications not required by law but available through the Sponsor may be negotiated separately by the parties. The School may amend such data prior to the first FTE count. If the School submits data relevant to FTE funding that is later determined though the audit procedure to be inaccurate, the School shall be responsible for any reimbursement to the State for any errors or omissions for which the School is responsible. The data elements shall include but not be limited to, the following: (a) ESE data; (b) Grade level assignment; (c) Required health information; (d) Required discipline codes/incident data; (e) Daily attendance; (f) Transportation; (g) Student schedules; (h) Teacher demographics; (i) Master schedule; (j) ESOL/migrant codes; (k) Grades/grading period/grading scale; (l) ERW (entry, re-entry, withdrawal) information; (m) Test scores; (n) Demographic information (o) Academic history and transcripts; (p) 504 data; and (q) Student lunch information as required.
View Source

Related to Automated Data System

  • System Except as otherwise provided herein, the Trustee shall not be accountable for the use or application by the Company or the Master Servicer of any of the Certificates or of the proceeds of such Certificates, or for the use or application of any funds paid to the Company or the Master Servicer in respect of the Mortgage Loans or deposited in or withdrawn from the Custodial Account or the Certificate Account by the Company or the Master Servicer.

  • Data Exchange Except where prohibited by law or regulation, MCP and MHP must share the minimum necessary data and information to facilitate referrals and coordinate care under this MOU. The Parties must have policies and procedures for supporting the timely and frequent exchange of Member information and data, including behavioral health and physical health data; for ensuring the confidentiality of exchanged information and data; and, if necessary, for obtaining Member consent, when required. The minimum necessary information and data elements to be shared as agreed upon by the Parties, are set forth in Exhibit C of this MOU. To the extent permitted under applicable law, the Parties must share, at a minimum, Member demographic information, behavioral and physical health information, diagnoses, assessments, medications prescribed, laboratory results, referrals/discharges to/from inpatient or crisis services and known changes in condition that may adversely impact the Member’s health and/or welfare. The Parties must annually review and, if appropriate, update Exhibit C of this MOU to facilitate sharing of information and data. MHP and MCP must 4 CalAIM Data Sharing Authorization Guidance VERSION 2.0 June 2023 available at: ▇▇▇▇▇://▇▇▇.▇▇▇▇.▇▇.▇▇▇/Documents/MCQMD/CalAIM-Data-Sharing-Authorization- Guidance-Version-2- Draft-Public-Comment.pdf. establish policies and procedures to implement the following with regard to information sharing: i. A process for timely exchanging information about Members eligible for ECM, regardless of whether the Specialty Mental Health provider is serving as an ECM provider; ii. A process for MHP to send regular, frequent batches of referrals to ECM and Community Supports to MCP in as close to real time as possible; iii. A process for MHP to send admission, discharge, and transfer data to MCP when Members are admitted to, discharged from, or transferred from facilities contracted by MHP (e.g., psychiatric inpatient hospitals, psychiatric health facilities, residential mental health facilities), and for MCP to receive this data. This process may incorporate notification requirements as described in Section 8(a)(v)(3); iv. A process to implement mechanisms to alert the other Party of behavioral health crises (e.g., MHP alerts MCP of Members’ uses of mobile health, psych inpatient, and crisis stabilization and MCP alerts MHP of Members’ visits to emergency departments and hospitals); and v. A process for MCP to send admission, discharge, and transfer data to MHP when Members are admitted to, discharged from, or transferred from facilities contracted by MCP (e.g., emergency department, inpatient hospitals, nursing facilities), and for MHP to receive this data. This process may incorporate notification requirements as described in Section 8(a)(v)(3).