Summary of outcomes for Data Standard 3.2
- Problem Addressed: There is ambiguity in the model of when to use StudentProgramAssociation or ProgramParticipation on the StudentEducationOrganizationAssociation.
- High-level Reasoning: Ideally, with new ParticipationStatus elements, all student program data should be captured via StudentProgramAssociation. There is use case for ProgramParticipation over StudentProgramAssociation - specifically to allow external education organizations to access a different EdOrg's program participation for a student. When this was moved from Student to StudentEducationOrganizationAssociation, authorization requirements changed to include the EducationOrganization.
- Changes Made: Deprecated StudentEducationOrganizationAssociation ProgramParticipation and direct users to instead utilize StudentProgramAssociation.
Original ticket description follows:
This entity seems to create ambiguity by allowing a second place to capture program participation. Need to look at the current model and see if it is able to address all use cases (e.g. eligibility and receipt of services).
See connection to comments in DATASTD-1183