Chief Sponsor: Jacob L. Anderegg

House Sponsor: Karianne Lisonbee


9     General Description:
10          This bill amends certain deadlines for the operation of a school information
11     management system.
12     Highlighted Provisions:
13          This bill:
14          ▸     amends certain deadlines for the operation of a school information management
15     system.
16     Money Appropriated in this Bill:
17          None
18     Other Special Clauses:
19          None
20     Utah Code Sections Affected:
21     AMENDS:
22          53E-3-518, as last amended by Laws of Utah 2020, Chapter 163

24     Be it enacted by the Legislature of the state of Utah:
25          Section 1. Section 53E-3-518 is amended to read:
26          53E-3-518. Utah school information management system -- Local education
27     agency requirements.
28          (1) As used in this section:
29          (a) "LEA data system" or "LEA's data system" means a data system that:

30          (i) is developed, selected, or relied upon by an LEA; and
31          (ii) the LEA uses to collect data or submit data to the state board related to:
32          (A) student information;
33          (B) educator information;
34          (C) financial information; or
35          (D) other information requested by the state board.
36          (b) "LEA financial information system" or "LEA's financial information system" means
37     an LEA data system used for financial information.
38          (c) "Utah school information management system" or "information management
39     system" means the state board's data collection and reporting system described in this section.
40          (d) "User" means an individual who has authorized access to the information
41     management system.
42          (2) On or before July 1, [2023] 2024, the state board shall have in place an information
43     management system that meets the requirements described in this section.
44          (3) The state board shall ensure that the information management system:
45          (a) interfaces with an LEA's data systems that meet the requirements described in
46     Subsection (6);
47          (b) serves as the mechanism for the state board to collect and report on all data that
48     LEAs submit to the state board related to:
49          (i) student information;
50          (ii) educator information;
51          (iii) financial information; and
52          (iv) other information requested by the state board;
53          (c) includes a web-based user interface through which a user may:
54          (i) enter data;
55          (ii) view data; and
56          (iii) generate customizable reports;
57          (d) includes a data warehouse and other hardware or software necessary to store or

58     process data submitted by an LEA;
59          (e) provides for data privacy, including by complying with Title 53E, Chapter 9,
60     Student Privacy and Data Protection;
61          (f) restricts user access based on each user's role; and
62          (g) meets requirements related to a student achievement backpack described in Section
63     53E-3-511.
64          (4) The state board shall establish the restrictions on user access described in
65     Subsection (3)(f).
66          (5) (a) The state board shall make rules that establish the required capabilities for an
67     LEA financial information system.
68          (b) In establishing the required capabilities for an LEA financial information system,
69     the state board shall consider metrics and capabilities requested by the state treasurer or state
70     auditor.
71          (6) (a) On or before July 1, [2023] 2024, an LEA shall ensure that:
72          (i) all of the LEA's data systems:
73          (A) meet the data standards established by the state board in accordance with Section
74     53E-3-501;
75          (B) are fully compatible with the state board's information management system; and
76          (C) meet specification standards determined by the state board; and
77          (ii) the LEA's financial information system meets the requirements described in
78     Subsection (5).
79          (b) An LEA shall ensure that an LEA data system purchased or developed on or after
80     May 14, 2019, will be compatible with the information management system when the
81     information management system is fully operational.
82          (7) (a) Subject to appropriations and Subsection (7)(b), the state board may use an
83     appropriation under this section to help an LEA meet the requirements in the rules described in
84     Subsection (5) by:
85          (i) providing to the LEA funding for implementation and sustainment of the LEA

86     financial information system, either through:
87          (A) awarding a grant to the LEA; or
88          (B) providing a reimbursement to the LEA; or
89          (ii) in accordance with Title 63G, Chapter 6a, Utah Procurement Code, procuring a
90     financial information system on behalf of an LEA for the LEA to use as the LEA's financial
91     information system.
92          (b) In accordance with Title 63G, Chapter 3, Utah Administrative Rulemaking Act, the
93     state board shall make rules describing:
94          (i) how an LEA may apply to the state board for the assistance described in Subsection
95     (7)(a); and
96          (ii) criteria for the state board to provide the assistance to an LEA.
97          (8) (a) Beginning July 1, [2023] 2024, the state board may take action against an LEA
98     that is out of compliance with a requirement described in Subsection (6) until the LEA
99     complies with the requirement.
100          (b) An action described in Subsection (8)(a) may include the state board withholding
101     funds from the LEA.