Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 17 Current »

Findings from 2024 Extension Analysis

 Executive Summary

In 2024, the Ed-Fi Alliance analyzed the usage of its Unifying Data Model (UDM) among state-wide implementations to understand its utilization and identify areas needing extensions. This analysis provided valuable insights into adoption patterns and practical challenges, informing future iterations of the Ed-Fi model. By fostering a collaborative environment and continuously improving the UDM, Ed-Fi aims to enhance educational data interoperability and outcomes.

The analysis of the usage of the Ed-Fi Unifying Data Model (UDM) across various states reveals that each state has created extensions to address specific needs not covered by the core model. These extensions span a wide range of areas, including special education, student transportation, assessment administration, and career pathways. For example, Texas has introduced a substantial number of extensions, including 20 new entities and 491 attributes, covering areas like accountability data, special education, and finance. In contrast, states like South Carolina and Wisconsin have focused on more targeted extensions, such as assessment administration and immunization records.

Common themes across states include the need for detailed tracking of special education programs, student enrollment and attendance, and specific program participation data. States like Arizona, Delaware, and Georgia have created extensions to capture data related to school and section enrollments, discipline, and student program evaluations. Similarly, Indiana and Kansas have focused on areas like alternative education programs, curricular material assistance, and CTE instruction and certification. Minnesota and Nebraska have introduced extensions to address needs in course offerings, discipline, post-graduation activities, and crisis events.

To enhance alignment and interoperability, several recommendations have been made to Ed-Fi states. These include utilizing existing core attributes where possible, migrating to the newer versions of the Ed-Fi data model, and reviewing and updating definitions. These analyses have also given the Ed-Fi an opportunity to consider consolidating multiple entity extensions and collaborating across states to identify common extension attributes for potential inclusion in the core model. As a result of it Ed-Fi has implemented some updates in the Data Standard v5.1 and v5.2 by including student health, transportation, assessment registration and Section 504 programs. One other artifact of this analysis on the Ed-Fi side is the initiation of a overhauling review of domain specific best practices and business rules guidance Ed-Fi Alliance started and will be continued in 2025 (see for examples: Enrollment domain, Alternative and supplemental services, Assessment registration, Student Attendance).

Absence of a standardization in the format of data specification documentation across the Ed-Fi states, extension of the scope of work during the process, and limited bandwidth data standard team had due to regular responsibilities were major limitations for the completion of these analyses. With the results obtained and lessons learned during this run, Ed-Fi aims to eliminate these limitations in the next run of similar work.

Introduction

In 2024, the Ed-Fi Alliance conducted a set of analyses for the usage of its Unifying Data Model (UDM) among the community members with state-wide implementation of Ed-Fi. The primary objective of these analyses was to gain a data-informed understanding of how the Ed-Fi UDM has been utilized in these states and to identify areas where community members required extensions to the Ed-Fi model. By analyzing situational and quantifiable data from state-wide implementations and providing recommendations for best usage of the model, Ed-Fi takes another step forward in fulfilling its commitment to community members. This commitment involves creating a unifying data model that not only addresses the use cases of educational agencies (SEA, ESA, LEA) but also eases the process for educational technology providers to extend their Ed-Fi implementations to new communities.

Furthermore, this work aimed to uncover patterns and trends in the adoption and adaptation of the Ed-Fi UDM, providing valuable insights into the practical challenges and successes experienced by various stakeholders. These insights are critical for informing future adaptation and implementation of the Ed-Fi model. By fostering a collaborative environment where data from state-wide implementations is systematically gathered and analyzed, Ed-Fi Alliance demonstrates its dedication to continuous improvement and innovation. This approach not only enhances the utility and relevance of the Ed-Fi UDM but also strengthens the overall ecosystem of educational data interoperability, ultimately contributing to more effective and efficient educational outcomes.

Summary of Findings

Analyses of the usage of Ed-Fi UDM and extensions created by states highlighted that there are varying degrees to which states extend the Ed-Fi core model to meet their specific needs. While some states rely heavily on extensions, others make extensive use of the core model. Understanding these metrics helps to identify areas for potential collaboration and standardization across states, ultimately enhancing data interoperability and supporting data-driven decision-making in education.

The following graph is to visualize these differences between Ed-Fi states. On the horizontal axis it shows the number of entities each state uses from the Ed-Fi UDM (Ed-Fi Core APIs) and the number of entities created as state extension are shown on the vertical axis.

Ed-Fi API Core and Extension Counts.jpg

The size of bubbles represents the API level extension dependency rate of each state. This rate is calculated by dividing the number of core entities each state uses by the total number of entities they had in their implementation of Ed-Fi model. The median number of extensions among states is calculated as 16 were median number of Ed-Fi API used was 36. As seen in the graph Michigan has the highest extension dependency rate while South Carolina has the smallest. The median extension dependency for these states has been calculated as 37%.

Ed-Fi Alliance team had the opportunity to share this visual with the community members in multiple occasions (Ed-Fi Summit 2024 was one of them) and many community members have shown interest to understand this finding better and shared with Ed-Fi their intend to reduce their extension dependencies. While this visual is a great tool to see the general picture of Ed-Fi’s finding for the usage of Ed-Fi UDM and dependency on extension among Ed-Fi states more details Ed-Fi Data Standard team has found in these analyses are in the following section.

State by State Extension Analysis Findings

Arizona

Arizona has leveraged the Ed-Fi extension mechanism to address specific state requirements in areas where the core data standard falls short. These areas include school and section enrollments, course offerings, external provider teachers, student needs for program services, student program evaluations, SPED assessment outcomes, dropout recovery programs, school and program attendance, and discipline. The extension analysis evaluated current core options, potential better alternatives for extension, and extensions that Ed-Fi should consider incorporating into the core data model.

Arizona extensions encompass the addition of seven new entities, one new association, and 124 new attributes. Specifics about the attribution extensions of current entities are as follows; two new attributes for the Calendar entity, four for CourseOffering, two for CourseTranscript, and three for DisciplineAction, the Program Evaluations domain is significantly expanded with four new entities, incorporating a total of 24 attributes. Additionally, the Section entity receives four new attributes and a new entity with seven attributes. The student dropout recovery program is bolstered by a new association and entity, adding four attributes. The StudentEducationOrganizationAssociation sees one new attribute, while a new entity for StudentNeed introduces seven attributes. Further extensions include three new attributes for StudentParentAssociation, 15 for StudentSchoolAssociation, one for StudentSchoolAttendanceEvent, five for StudentSectionAssociation, five for StudentSpecialEducationProgramAssociation, and four for StudentProgramAttendanceEvent. These updates are designed to enhance data granularity, improve interoperability, and support robust program evaluation and student tracking capabilities.

The analysis found that Arizona created a moderate number of extensions to the Ed-Fi core in areas such as school and section enrollments, course offerings, external provider teachers, student program services, program evaluations, SPED assessment outcomes, dropout recovery programs, school and program attendance, and discipline. Specific recommendations for Arizona include migrating the four entity extensions (ProgramEvaluation, ProgramEvaluationElement, EvaluationRubricDimension, and StudentProgramEvaluation) to the Ed-Fi version 5.X core, as these extensions are already well-aligned with the new core elements. Arizona's usage of the Ed-Fi core model is generally well-aligned, with only two data elements structurally misaligned. It is recommended to communicate these deviations with the Ed-Fi Alliance for stronger alignment.

Several elements require re-examination of their definitions. For instance, the definition for SchoolID is erroneous, stating “A unique alpha-numeric code assigned to a student by the state,” which needs correction in elements like ClassPeriod.SchoolID and SectionExternalProviderTeacher.SchoolID. Additionally, some descriptors have cryptic definitions, such as “A unique identifier used as Primary Key, not derived from business logic, when acting as Foreign Key, references the parent table,” which should be replaced with the Ed-Fi definitions for elements like StaffSectionAssociation.ClassroomPositionDescriptorID, StudentSchoolAssociation.EntryTypeDescriptorID, and StudentSchoolAssociation.ExitWithdrawTypeDescriptorID. The definition for StudentOtherName.OtherNameTypeDescriptorId, although aligned, is cryptic and would benefit from using the Ed-Fi definition.

The analysis also highlighted the need for Ed-Fi to review the current design of some data elements. Arizona provided alternative, equivalent, but better definitions for several Ed-Fi elements, leading to recommendations for updates to the Ed-Fi definitions. For example, the Ed-Fi definition for Section.AvailableCredits indicates that the unit of measurement is “Carnegie units,” but there is an indication that the industry may be moving away from this measure. Ed-Fi should monitor this trend and consider dropping the Carnegie unit reference in favor of specifying the units used by the state. The Ed-Fi data type for StaffSectionAssociation.PercentageContribution is DECIMAL (5,4), indicating it is a decimal between 0 and 1 (e.g., 0.3) rather than a percentage (e.g., 30%). Arizona’s definition clarified this, and the Ed-Fi definition needs to do the same. Additionally, the handling of event duration in StudentSchoolAttendanceEvent should be re-examined, considering practices in the field, and potentially simplified by collapsing the inline common StudentSchoolAttendanceEvent.AttendanceEvent structure.

Based on these findings, Ed-Fi aims to work closely with the Arizona Department of Education to sustain data standards. Opportunities for collaboration include leveraging extension entities for external provider teachers, student program services, SPED assessment outcomes, and dropout recovery programs as common needs across states become evident. Cross-state collaboration is recommended to identify specific common extension attributes for potential inclusion in the core model, enhancing data interoperability and supporting data-driven decision-making across states.

Delaware

Delaware has extensively utilized the Ed-Fi extension mechanism to address specific state requirements where the core data standard did not suffice. Our analysis indicates that approximately 40% of Delaware's data elements in their Ed-Fi model were state-created extensions. These extensions cover areas such as student enrollment data, course offerings and grades, teaching and learning, student transportation, special education and other IDEA-mandated programs, restraint and seclusion involving students and staff, discipline, CTE instruction, and student medical records.

The Delaware extensions include one new entity, two new associations, and 49 new attributes. Key updates involve attribute extensions to StudentEducationOrganizationAssociation, StudentEducationOrganizationResponsibilityAssociation, and StudentSchoolAssociation. Additionally, the Section entity has received several new attributes. The CalendarDate entity has been extended to include attributes related to learning modalities. The Course entity has new attributes for AP exam codes, core subjects, and staff credentials. Other significant extensions include new attributes for GradingPeriod, Parent (renamed as Contact), StudentParentAssociation (renamed as StudentContactAssociation), StudentLanguageInstructionAssociation, and StudentSpecialEducationProgramAssociation. Furthermore, new entities such as StudentTransportation, GradeTypeDetail, LevelDetail, PostSecondaryDetail, StudentAssessmentRegistration, RestraintSeclusion, AllegedBullyingVictim, MedicalAlert, PersonMedicalAlert, MedicationBox, MedicalScreening, PersonImmunization, MedicalOfficeVisit, and MedicalReferralFollowUp have been introduced. New associations like Student504ProgramAssociation, StudentEarlyChildhoodProgramAssociation, and PersonMedicationBoxAssociation have also been added to support specific state needs.

The analysis found that Delaware created a significant number of extensions to the Ed-Fi core, either by extending current entities and associations or adding new ones. In total, there were 231 data element (attribute) extensions observed in various areas, including student enrollment, course offerings and grades, language instruction, CTE programs, early childhood programs, transportation, and medical-related fields. Of these extensions, 95 are nested within existing entities and attributes (47 in associations and 48 in entities), while 136 attributes were added through new associations or entities (30 in associations and 106 in entities).

Delaware has the largest extension in medical-related fields among all states analyzed, with about 20% of all extensions focused on medical data tracking. Enrollment and programs are the other two areas with the most extensions, accounting for about 40% of all observed extensions in Delaware.

Since the data collection for this analysis was conducted in early 2024, some of the extensions observed in Delaware have already been incorporated into the Ed-Fi UDM by the time this report was created. These updates include extensions in assessment registration, student transportation, Section 504, and student immunization, which account for about 15% of the extensions.

Georgia

The Georgia extensions introduce two new entities, two new associations, and 110 new attributes to the Ed-Fi data model. The new entity LocalEducationAgencyStatistics provides summary counts for psychological cases and private or home-schooled students, with attributes such as LocalEducationAgencyId, and counts for private or home-schooled students and psychological services evaluations. The SchoolStatistics entity offers summary counts for behavior incidents, social work cases, interventions, and referrals, with attributes including DualEnrollmentAwarenessGrade10, DualEnrollmentAwarenessGrade11, and various descriptors for school programs and services.

Attribute extensions to the Section entity include TaughtByESOLTeacher and AlternateEducationOrganizationId. The StudentEducationOrganizationAssociation entity has been extended with attributes for biliteracy language descriptors, county of residence, non-ESOL status, and various dates and descriptors related to student eligibility and communication. The StudentSchoolAssociation entity includes new attributes for tracking entry into 9th grade, program participation, ASVAB scores, and FTE segments. The StudentSectionAssociation entity has been extended with attributes for credit recovery, FTE program codes, inclusion types, and various delivery models for educational programs.

Additional extensions include a new association StudentSection504ProgramAssociation for Section 504 disabled students, with attributes for accommodation plans and evaluation dates, and a new association StudentSpecialEducationProgramAssociationEvent to describe events associated with students in special education programs. The DisciplineIncident and DisciplineAction entities have also been extended with new descriptors for incident timing, severity levels, and discipline processes. Finally, the Staff, StaffEducationOrganizationEmploymentAssociation, and StaffEducationOrganizationAssignmentAssociation entities have been extended with attributes related to employment types, contracts, and assignment details. These extensions aim to enhance data granularity, improve interoperability, and support comprehensive program evaluation and student tracking capabilities.

The analysis found that Georgia created a moderate number of extensions to the Ed-Fi core in the areas that include school and section enrollments, discipline, section 504 program, special education events, and staff employment and assignments. Specific suggestions for the State are as follows.

  • With regard to StudentEducationOrganizationAssociation.Extension.CountyOfResidenceDescriptor, Ed-Fi has StudentEducationOrganizationAssociation.Address.NameOfCounty

  • With regard to StaffEdOrgEmploymentAssociation.Extension.AnnualSalary, Ed-Fi V5 has a new attribute AnnualWage that should be used.

Based on these findings, Ed-Fi aims to work closely with the Georgia Department of Education to sustain data standards. Opportunities for collaboration include leveraging extension entities defined for Section 504 programs and special education events as common needs across states become evident.

Indiana

Indiana has utilized the Ed-Fi extension mechanism to address specific state requirements where the core data standard did not suffice. These areas include additional programs for alternative education and curricular material assistance, noncertified and other personnel not categorized as staff, assessment accommodations, school status as a Choice or Freeway school, staff employment contracts, special education, and discipline. The extension analysis evaluated current core options, potential better alternatives for extension, and extensions that Ed-Fi should consider incorporating into the core data model.

The Indiana extensions comprise three new entities, two new associations, and 46 new attributes. Key updates include the new association StudentAlternativeEducationProgramAssociation, a specialization of the GeneralStudentProgramAssociation, with attributes for alternative education eligibility and program meeting times. Another new association, StudentCurricularMaterialProgramAssociation, addresses students enrolled in the Curricular Material Assistance Program with attributes for parental living arrangements. The new entity EducationOrganizationOtherPersonnel captures data on noncertified personnel with attributes such as category, title, count, and full-time equivalency. The AssessmentAccommodation entity records how assessments are presented or taken, while the related StudentEducationOrganizationAssessmentAccommodation entity details the accommodations used by students.

Additional attribute extensions include school status indicators for Choice or Freeway schools, calendar event durations, staff employment contracts, and various student associations. These extensions aim to enhance data granularity, improve interoperability, and support robust program evaluation and student tracking capabilities. However, extending the current model is not a desired outcome, so alternative solutions should be considered to avoid extensive modifications.

This analysis also provided Ed-Fi information on a need for the review of current design of some data elements listed below:

  • New extension entities were created for AssessmentAccommodation and StudentEducationOrganizationAssessmentAccommodation indicating that the current Ed-FI model treatment as a simple Accommodation descriptor on StudentAccommodation is too simplistic and not meeting the needs Indiana, and possibly others.

Based on these findings of the analyses, Ed-Fi would like to work closely with the IDOE as a part of its commitment to sustaining data standards. The following are opportunities for next steps for this collaboration between the State and Ed-Fi.

  • An extension multi-valued common was defined for staff employment contracts with StaffEducationOrganizationEmploymentAssociation. StaffEducationOrganizationEmploymentAssociationContract.  This should be researched to see if this is a need across the community.

Extensions of the StudentSpecialEducationProgramAssociation are typical across the states, as needs change and evolve in this domain.  Collaboration across states should be used to keep this domain up to date with community needs.

Kansas

The Kansas extensions comprise one new entity, two new associations, and 49 new attributes. Key updates include attribute extensions to the StudentEducationOrganizationAssociation entity, adding fields for district of residence, immigrant student status, military-connected student descriptor, neglected student status, and CTE-related attributes such as certification dates and earned certifications. Additionally, transportation-related attributes were added to track miles transported, non-resident transportation, and transportation FTE.

The StudentSchoolAssociation entity has been extended with attributes for attendance days, CTE contact minutes, credits earned and required to graduate, first instructional date, individual plan of study, local education agency entry date, membership days, minutes enrolled, post-graduation plans, 504 qualification, state entry date, and unweighted GPA. The StudentSectionAssociation entity includes a new attribute for course status.

A new entity, SectionEducator, has been introduced with attributes for educator email addresses, section details, and educator names. However, it is suggested to use the StaffSectionAssociation to link educators to sections. The CourseOffering entity has been extended with attributes for college career type, course credits, delivery type, program type, sequence, and total sequence. The Grade entity includes new attributes for work-based learning, college credits earned, graduation year, instructional dates, and minutes completed.

The StudentAssessment entity has been extended with attributes for proctor staff and assessment requests. The StudentLanguageInstructionProgramAssociation entity includes new attributes for funding source, initial school entry in the US, end date, program type, and service funding source. Finally, two new associations, StudentKPATProgramAssociation and StudentKPPProgramAssociation, extend the GeneralStudentProgramAssociation to support specific program tracking needs. These extensions aim to enhance data granularity, improve interoperability, and support comprehensive program evaluation and student tracking capabilities

The analysis showed that Kansas created a limited number of extensions to the Ed-Fi core in areas such as student enrollment data, course offerings and grades, language instruction, CTE instruction and certification, and transportation. Specific suggestions for Kansas include replacing the StudentEducationOrganizationAssociation.MilitaryConnectedStudent descriptor extension with the v5.0 Ed-Fi attribute StudentEducationOrganizationAssociation. SupporterMilitaryConnection and using the StaffSectionAssociation instead of the extension entity SectionEducator to link educators to sections. Additionally, the definition for the extension attribute Grade.WorkBasedLearning, which seems to indicate a characteristic of the course, should be placed as an extension to Course or CourseOffering.

Several attributes could be handled differently if other areas of the Ed-Fi data model were used. For example, if granular StudentSchoolAttendanceEvents were captured, the StudentSchoolAssociation.AttendanceDays could be computed. Similarly, using the StudentAcademicRecord and CourseTranscript entities to capture student transcript information could replace several extensions with core elements in these entities, such as replacing StudentSchoolAssociation.CreditsEarned with StudentAcademicRecord.CumulativeEarnedCredits, StudentSchoolAssociation.UnweightedGradePointAverage with StudentAcademicRecord.GradePointAverage, Grade.CollegeCreditsEarned with CourseTranscript.EarnedAdditionalCredits, and Grade.GraduationYear with StudentAcademicRecord.ProjectedGraduationDate.

The analysis also highlighted the need to revisit the definition for StudentAssessmentAccommodation.AccommodationDescriptor to clarify its use for accommodations for disabilities. Based on these findings, Ed-Fi aims to work closely with the Kansas State Department of Education (KSED) to sustain data standards. Opportunities for collaboration include advising Kansas as they expand their use of the data model, such as with StudentAcademicRecord and CourseTranscript, and leveraging extensions defined for language instruction, CTE certifications, and transportation as common needs across states become evident. Cross-state collaboration is recommended to identify specific common extension attributes for potential inclusion in the core model, enhancing data interoperability and supporting data-driven decision-making across states.

Minnesota

The Minnesota extensions introduce significant additions to the data model, encompassing 7 new entities, 12 new associations, and 241 new attributes. These extensions span various entities, including Calendar, ClassPeriod, Course, CourseOffering, DisciplineAction, DisciplineIncident, Grade, LocalEducationAgency, Parent, School, Section, Session, and Student-related associations.

Key attribute extensions include additions to the Calendar entity, such as CalendarDescription, DaysInSession, and InstructionalDays. The ClassPeriod entity sees the inclusion of classPeriodTypeDescriptor. The Course entity is notably expanded with attributes like AssessmentToolDescriptor, CareerClusterDescriptor, and CourseLevelTypeDescriptor, among others.

New associations, such as CourseCourseAssociation, facilitate connections between State, District, and College courses. The CourseOffering entity is enhanced with attributes related to instructional approaches and site-based initiatives. Discipline-related entities, including DisciplineAction and DisciplineIncident, receive new descriptors and explanations to better capture incident details.

New entities like DisciplineIncidentAnonymousNonOffender and UnenrolledOffender are introduced to track non-offender and unenrolled offender details, respectively. The student-related associations are significantly expanded, with new associations like Student21stCenturyLearningCenterGrantProgramAssociation and StudentEarlyChildhoodScreeningProgramAssociation, each with specific attributes to capture detailed program participation data.
The analysis found that Minnesota created a fairly large number of extensions to the Ed-Fi core in areas such as course and course offerings, discipline, school and section enrollments, student information, school information, programs, and student assessment administration. Specific suggestions for Minnesota include using existing Ed-Fi attributes where possible, such as computing Calendar.InstructionalDays from Session.TotalInstructionalDays, using Course.CareerPathwayDescriptor instead of Course.CareerClusterDescriptor, and capturing Grade.AcademicSubjectDescriptor through the existing Ed-Fi structure. Additionally, the extensions Grade.CollegeCreditsEarned, Grade.CollegeGradeEarned, and Grade.LocalCreditEarned should be moved to CourseTranscript.

The extension entities SchoolAttributes and SchoolDisciplineAttributes should be reviewed to consider using a multi-valued descriptor instead of many Boolean attributes, consolidating common attributes, and evaluating the rationale for separate entities versus extending the School entity. The StudentEarlyChildhoodScreeningProgramAssociation should consider moving to the new Student Program Evaluation domain in Ed-Fi 5.x. Extensions to the StudentEducationOrganizationAssociation for Birthdate, Name, and OtherName should be examined to ensure the longitudinal identity of students is uniquely tracked, and extensions for reporting language academic honors should use StudentAcademicRecord.Recognition.

Based on these findings, Ed-Fi aims to work closely with the Minnesota Department of Education (MDE) to sustain data standards. Opportunities for collaboration include investigating the inclusion of discipline extensions and student assessment and assessment administration extensions into the Ed-Fi core, considering new StudentProgramAssociation extensions for federal programs, and identifying specific common extension attributes for potential inclusion in the core model through cross-state collaboration. This collaboration aims to enhance data interoperability and support data-driven decision-making across states.

Nebraska

The Nebraska extensions introduce three new entities, one new association, and 34 new attributes to the data model. These extensions are designed to enhance the recording and analysis of student crisis information, post-graduation activities, assessment administration, and various program associations.

Key additions include the CrisisDetails entity, which captures detailed information about student crises with attributes like CrisisType and CrisisStartDate. The PostGraduateActivity entity records students' CTE post-graduation activities, while the AssessmentAdministration entity defines the organizations administering assessments.

The discipline domain sees extensions with new boolean attributes for DisciplineIncident and DisciplineAction, as well as additional attributes for StudentDisciplineIncidentBehaviorAssociation to capture specific incident behaviors. The StudentSpecialEducationProgramAssociation is expanded with attributes related to special education programs and placements. Other notable extensions include attributes for Section, StudentSchoolAssociation, StudentEducationOrganizationAssociation, and StudentLanguageInstructionProgramAssociation. The CalendarDate entity is also extended to denote instructional duration.

The analysis found that Nebraska created a limited number of extensions to the Ed-Fi core in areas such as special education eligibility, post-graduation activities, discipline incidents, and crisis events. Specific suggestions for Nebraska include folding Boolean extensions in the discipline domain into related descriptors for Behavior and Discipline, as Ed-Fi generally avoids long sets of Boolean attributes in favor of multi-valued descriptors. The extensions for the StudentSpecialEducationProgramAssociation should be aligned with DSv5 new attributes, specifically SpecialEducationProgram => IDEAPartDescriptor, and the StudentEarlyLearningProgramAssociation entity should be aligned with the new StudentEarlyLearningProgramAssociation introduced in DSv5.

The analysis also highlighted the need for Ed-Fi to review the current design of some data elements. It is recommended to investigate model changes to capture important enrollment aggregate data, such as StudentSchoolAssociation.StudentDaysEnrolled. Additionally, there are 13 core data elements where the Nebraska definition is more precise and should be considered for adoption as the Ed-Fi definition. These elements include Parent.Addresses.AddressTypeDescriptor, StudentEducationOrganizationAssociation.Addresses.AddressTypeDescriptor, StudentEducationOrganizationAssociation.Languages.LanguageDescriptor, StudentEducationOrganizationAssociation.StudentIdentificationCodes.StudentIdentificationSystemDescriptor, StudentEducationOrganizationAssociation.Telephones.TelephoneNumberTypeDescriptor, Parent.Telephones.TelephoneNumberTypeDescriptor, Course.AcademicSubjectDescriptor, Course.CourseCode, StudentSchoolAssociation.CalendarReference, StudentSchoolAssociation.ExitWithdrawTypeDescriptor, StudentSchoolAttendanceEvent.AttendanceEventCategoryDescriptor, StudentSectionAttendanceEvent.AttendanceEventCategoryDescriptor, StudentSchoolAttendanceEvent.EventDuration, and StaffEducationOrganizationContactAssociation.Telephones.TextMessageCapabilityIndicator.

South Carolina

The South Carolina extensions introduce two new entities and 18 attributes, focusing on an Assessment Roster extension developed in collaboration with Ed-Fi and other states. This extension aims to capture and communicate data regarding the expectation that a student will take an assessment.

The new AssessmentAdministration entity includes attributes such as EducationOrganizationReference, AssessmentReference, AssessmentTitle, and Period. It also features a common AdministrationContact attribute set, which includes details like ElectronicEmailAddress, FirstName, LastSurname, and IdentificationCode.

The StudentAssessmentRegistration entity is designed to link students to their assessment administrations. It includes attributes such as AssessmentAdministrationReference, StudentEducationOrganizationAssociationReference, TestingEducationOrganizationReference, and ReportingEducationOrganizationReference. Additionally, it features a PlatformTypeDescriptor and a common AssessmentCustomization attribute set, which includes IdentificationCode and CustomizationValue.
These findings reveal that South Carolina created a limited number of extensions to the Ed-Fi core for assessment administration as part of a collaboration defining assessment rosters.  South Carolina is recommended to track Ed-Fi activities if it decides to bring the extension into core.

Texas

The Texas extensions introduce numerous new entities, associations, and attributes to the Ed-Fi data model, addressing specific state needs not fully met by the core data standard. These extensions cover areas such as accountability data, summary attendance, student applications for enrollment, special education eligibility, student academic records, prior year leaver information, and finance.

Key extensions include the StudentTitleIPartAProgramAssociation, which now captures detailed student participation data, and the StudentSpecialEducationProgramAssociation, which is significantly expanded to include various aspects of special education data, such as medically fragile students, instructional settings, disability diagnoses, language services, hearing amplification, assessment results, and residential facility associations.

The RestraintEvent entity is extended with attributes for staff type and non-membership discipline restraint indicators. The StudentLanguageInstructionProgramAssociation now includes parental permissions. Assessment extensions provide alternatives for early childhood assessments and TEA collection reporting, while Discipline extensions add attributes for threat assessments, discipline lengths, and code of conduct consistency.

The LocalEducationOrganization and School entities are extended with attributes for accountability data, enrollment methods, NSLP participation, charter school waitlists, and expanded learning opportunities. The StudentSchoolAssociation is expanded with additional enrollment attributes.

New entities for Finance capture detailed financial data, including actuals, budgets, shared service arrangements, payroll, and contracted instructional staff FTE. New entities and associations for Prior Year Leaver students and their parents capture comprehensive student and parent information. The CalendarDate entity is extended with attributes for waiver event types and operational minutes.

A new ReportingPeriod entity captures attendance reporting attributes. The Staff entity is extended with new attributes and multivalued commons for staff types and paraprofessional certifications. StudentAcademicRecord extensions capture Foundation High School Program participation and industry-based certifications. CourseTranscript extensions include new attributes for college credit hours and dual credit indicators.

A new StudentApplication entity represents enrollment applications. The StudentProgramAttendanceEvent is extended with an instructional setting attribute. New entities for various program attendance capture detailed attendance data.

The Student entity is extended with new attributes and multivalued commons for census block groups and crisis events. The Parent entity is extended with a generation code attribute. The StudentEducationOrganizationAssociation is extended with multivalued commons for various student characteristics and statuses.

A new StudentSpecialEducationProgramEligibilityAssociation entity captures special education program eligibility attributes. The Section entity is extended with a multivalued common for section details. The StaffSectionAssociation is extended with attributes for class size and teaching minutes, and the StudentSectionAssociation is extended with a course completion indicator.

Texas created a large number of extensions to the Ed-Fi core in the areas that include accountability data, summary attendance in reporting periods, student applications for enrollment, special education eligibility and program data, student academic record data, prior year leaver student information, and finance.  Texas extends the operational education data elements of Ed-Fi with summary and aggregate information required for accountability.

Specific suggestions for the State are as follows.

  • The 10 new entity extensions defined for reporting period attendance could potentially be structured into a smaller set of entities.

The two new entities and association extensions for prior year leavers could potentially be better integrated into the existing student/parent structure, reducing duplication. The following are opportunities for next steps for this collaboration between the State and Ed-Fi.

  • As common a need across states becomes evident, leverage the extensions defined for special education and other programs, student academic record, and student applications.

Analysis across states may identify specific common extension attributes for consideration into core where cross-state collaboration is recommended.

Wisconsin

The Wisconsin extensions introduce two new entities, one new association, and 72 attributes, significantly enhancing the data model. The new entities and association account for roughly half of the attribute extensions.

The StudentTransportation entity captures detailed student transportation information, including attributes like SchoolYear, StudentReference, EducationOrganizationReference, TransportationTypeDescriptor, MileageCategory, and PrivateSchoolIndicator. The ImmunizationRegistry entity records a student's immunization history with attributes such as statusCode, statusMessage, ImmunizationsStudentHistory, patientIdentifier, and various details about pharmacy treatment administrations.

A new association, StudentSpecialEducationProgramEligibilityAssociation, captures key data and milestones related to a student's eligibility determination for special education services. This association includes attributes like educationOrganizationId, programName, programTypeDescriptor, studentUniqueId, and several others related to evaluation and eligibility.

The StudentSchoolAssociation is expanded with thirteen new attributes to capture enrollment details related to residency, school choice, expected future transfers, part-time enrollments, and student status and services on the official student count date. Additionally, two attributes, actualDaysAttendance and possibleDaysAttendance, are added to capture attendance aggregates.

Other notable extensions include attributes for GraduationPlan, StudentCTEProgramAssociation, CourseOffering, Student, Section, and StudentDisciplineIncidentBehaviorAssociation. These extensions enhance the ability to manage and analyze various aspects of student data, ensuring comprehensive coverage of transportation, immunization, special education eligibility, and other critical areas.

Overall, Wisconsin created a moderate number of extensions to the Ed-Fi core in the areas that include student transportation, immunization, special education program eligibility, enrollment, and career pathways.

Ed-Fi recommended the state to implement StudentSpecialEducationProgramEligibilityAssociation instead of extension by migrating to DS v5.x and was inspired by the StudentTransportation, ImmunizationRegistry and Assessment Registration related extensions the state has created while designing those updates in Data Standard v5.1 and v5.2.

👉 To see reports for each state use the links below

📄 Analysis Report for Arizona

📄 Analysis Report for Delaware

📄 Analysis Report for Georgia

📄 Analysis Report for Indiana

📄 Analysis Report for Kansas

📄 Analysis Report for Minnesota

📄 Analysis Report for Nebraska

📄 Analysis Report for South Carolina

📄 Analysis Report for Texas

📄 Analysis Report for Wisconsin

  • No labels