Spreadsheet: 3a048192-370b-460a-b3d5-5c7d18f15fad
Sheet: 5. Data & Systems Integration

 | Functional Requirements
 | All of the following functionality is in the Thinkgate base system or on their development roadmap to be completed by 7/15/2013 with the exception of items related to Learning Registry and Federated search. These items will be completed when the Learning Registry is more stable and technical requirements are well defined. |  | LEA Selected IIS
 | Requirement Description | Mandatory or Preferred | Meets Requirement (Y/N)? | Tool Name | Level of Satisfaction (1, 2 or 3) | Comments
5.0 | Data and Systems Integration
5.1  Student Demograhics and Program Participation
Thinkgate Narrative: | The system supports basic student information within the student data table. Additionally, there are an unlimited number of user defined fields that can extend the student attributes tracked. All student data table fields and user defined fields can be populated and maintained with data from the student information system. A general document template facilitity provides the capability to created and track many different documents for a student, i.e. student portfolios, awards and certificates.This facility would be used for the SLPs, as well as Special Ed Data records. However, the more involved data and processes associated with special ed are not supported directly by the Elements platform. These capabilities are available with an integrated partner product. This Special Ed product is not included with this proposal since the special ed requirements below are listed as Desirable, not Critical.
5.1.1 | Provides role based access to student demographic information, including but not limited to, name, address, home phone number, date of birth, gender, ethnicity, native language,and IEP/Section 509 status with:
 | a. capability to accommodate unique student numbers | Mandatory
 | c. capability to store student photographs or pictures | Preferred
 | d. ability to sort and/or filter by all demographic fields (especially for [NAME] searches) | Preferred
5.1.2 | Provides role based access to special program information as defined by the state and district including but not limited to:
 | a. economic status (migrant classification, homeless, other) | Mandatory
 | [NAME] education status (need to add ESOL/ELL, LEP) | Mandatory
 | c. gifted and talented status | Preferred
 | d. special programs | Preferred
 | e. post secondary enrollment, IB, virtual school information | Preferred
 | [NAME]/vocational technical education | Preferred
5.1.3 | Provides for storage and access to Student Learning Plans (SLP) | Preferred
 | a. including student’s strengths
 | b. including student’s concerns
 | [NAME] attribute category selections
 | d. including additional comments (free text)
 | e. including the ability for authorized teachers to edit the SLP
5.1.4 | Provides a method to store student learning plans for students including: | Preferred
 | [NAME] of competencies, learning style, credits, and gaps in skills
 | [NAME] styles
 | c. credits
 | d. gaps in skills
 | e. RTI (tier 1, tier 2, tier 3)
5.1.5 | Provides for storage and access to selected Special Education Data including (multiple records per student): | Preferred
 | [NAME]/handicap
 | [NAME]program
 | c.  event date
 | d.  entry date
 | e.  exit date
 | f.  next IEP date
 | g.  redetermination date
 | h.  IEP teacher
 | i.  undergoing evaluation (Y/N)
 | j. ELL
 | k. Title 1
5.1.6 | Maintains a history of the student's participation in special education | Preferred
5.1.11 | Provides role based access to enrollment and attendance history including:
 | a. school year | Mandatory
 | b. school/building | Mandatory
 | [NAME] level | Mandatory
 | d. days enrolled | Preferred
 | e. school entry/withdrawal dates | Mandatory
 | f. days absent by date | Preferred
 | g. days tardy by date | Preferred
 | h. class absence/tardy/missed instructional minutes | Preferred
 | [NAME] reasons according to a uniform definition across districts | Preferred
5.1.12 | Provides role based access to discipline information including: | Preferred
 | a. School Environmental Safety Incident Report (SESIR) code
 | [NAME] rate with ability to differential between in school and out of school
 | [NAME] (time, place, teacher) for both classroom and non-classroom situations
 | d. discipline alerts or flags for all environments including but not limited to bus, playground, and other nonstudent contact time
5.1.13 | Provides a method for the storage of Student Portfolios (examples of work) in accessible formats available directly or for assessment purposes | Preferred
5.1.14 | Stores student awards and certificates, internships, independent studies, extra curricular activities | Preferred
5.1.15 | Student work stored in the system as an examplar must be decoupled from the student identify | Preferred
5.2  Data and System Standards and Integration
Thinkgate Narrative: | The Elements Platform includes two key integration components that support consumption of data from other sources, and push of data to other systems. These components are the ETL (Extract, Transfer, Load) component and the IDE (Interface Data Engine). The ETL component provides a mechanism to manage and automate consumption of data files that are required to populate the Elements Platform data structures. Also, this component provides the ability to generate assessment related data files that can be pushed out to other systems. IDE is built to deal with the variability found in assessment result data files that are imported for reporting purposes. The ETL component includes both a SIF interface, as well as a CSV file interface. Content integrations occur using several mechanisms. Content can be imported using Elements defined XML formats, or using QTI format. Content can be stored within the Elements digital library, or can be linked using URL pointers to the content. There are interfaces for many assessment administration devices, including OCR, plain paper scanning, hand-held "clickers", and tablets (IPAD currently).
5.2.1 | Provides a data dictionary identifying all data elements including source system of record, refresh rate and other data attributes. | Preferred
5.2.2 | Interfaces with district and/or state data systems utilizing Schools Interoperability Framework (SIF). | Preferred
5.2.3 | Provides a generic non-SIF loading process for SIS and state data. | Mandatory
5.2.4 | Interfaces with the Shared Learning Infrastructure (SLI) data store. | Preferred
5.2.5 | Includes future plans to be Accessible Portable Item Protocol (APIP) compliant | Preferred
5.2.6 | Provides the ability to import and export assessment items in Question and Test Interoperability (QTI) format | Preferred
5.2.7 | Supports imaging inputs and OCR capabilities | Preferred
5.2.8 | Provides the capability to interface with commonly accepted imaging standards (for example .jpg, .epi, .eps, .tif, .gif, .png) to capture and retrieve graphics and photos for use in assessment items and resources | Mandatory
5.2.9 | Supports the Sharable Content Object Reference Model (SCORM) version 1.2 or above | Preferred
5.2.10 | Supports Simplified Object Access Protocol (SOAP) standard or other Web Services protocol for exchange of information. | Preferred
5.2.11 | Complies with Priority One of the World Wide Web Consortium’s (W3C’s) Web Content Accessibility Initiative and complies with ADA Section 508 | Preferred
5.2.13 | Supports virtualization | Preferred
5.2.14 | Provides a mapping between internal data elements and data elements defined by the Common Education Data Standards (CEDS) initiative and [NAME] extensions to this standard to facilitate data transfer between compliant systems | Preferred
5.2.18 | Performs regularly scheduled updates to the IIS metadata data store by synching with the identified Learning Registry node. (Learning Registry item) | Preferred
5.2.19 | Provides a permanent, publicly accessible URL for each resource (instructional material, assessment items) containing only alphanumeric characters, periods, and slashes (Learning Registry item) | Preferred
5.2.20 | Provides for a public access to the permanent URL and underlying content/pages associated with resources. (Learning Registry item) | Preferred
5.2.21 | Provides ability to designate some resources as public access via administrative interface. Owner of resource as well as system administrators can designate access control as public or restrict access. (Learning Registry item) | Preferred