(1) (a) The general assembly finds that there is a need for consistency in electronic data submission protocols and requirements to allow school districts and public schools to submit data for multiple reports in one transaction. Under the existing data submission system, school districts and public schools are often forced to report data that is known to be incorrect because of an existing inability to correct or resubmit data through the current data technology system. The general assembly finds that the priority in data collection and submission must be the efficient collection and use of accurate, relevant data.

(b) The general assembly finds therefore that, with the creation and implementation of a data dictionary, the department may bring consistency and greater accuracy to the data elements collected from school districts and public schools and increase the efficiency of education data submission and collection by not collecting the same data elements more often than necessary.

(2) (a) The department shall develop and distribute to the school districts and public schools a data dictionary to define the data the department will collect and the methods and protocols by which school districts and public schools will submit the data. At a minimum, the data dictionary shall include the following items:

(I) A map of the current data collection requirements, including the definition of each data element, when each data element is collected, identification of the external reports for which each data element is used, and identification of the method by which each data element is collected;

(II) A description of the format for data submission, acceptable values in data submission, the available options for dealing with data fields for which the submitting school district or public school does not have information, and logical comparisons to prior reports;

(III) Identification of data relationships;

(IV) Data element tables; and

(V) Identification of data element locations within data access tools.

(b) In developing the data dictionary, the department shall seek and apply input from school districts, public schools, and the EDAC. In addition, the department shall ensure that the data elements included in the data dictionary are aligned with the descriptions and definitions of data elements that are used by national education organizations such as the federal department of education and other organizations that set national education standards and ratings.

(3) On or before August 1, 2007, the department shall report the status of the data dictionary to the state board, the education committees of the senate and house of representatives, or any successor committees, the governor, school districts, and the EDAC. At a minimum, the report shall include:

(a) A description of how many school districts and public schools were involved in the process of creating the data dictionary, the extent to which the EDAC was involved in the process, and the manner of the school districts', public schools', and the EDAC's involvement;

(b) An explanation of the department's methods and considerations in creating the data dictionary, including the extent to which the department considered models from other states;

(c) An explanation of the manner in which school districts and public schools will access the data dictionary; and

(d) The method by and frequency with which the department plans to review and update the data dictionary.

(4) The department shall ensure that the data dictionary is fully operational and available for use on or before October 1, 2007.

(5) The general assembly finds and declares that, for purposes of section 17 of article IX of the state constitution, the creation and implementation of the data dictionary pursuant to this section is an important element of accountability reporting and may therefore receive funding from the state education fund created in section 17 (4) of article IX of the state constitution.