This lesson serves as a guide to the Behavior Component of the Michigan Student Data System submission.
Discipline Component
Incident ID
The Incident ID is an automatically generated ID associated with the incident. This value is not editable.
Date of Incident
The Date of Incident is reported from the "Date" field associated with the Incident.
Incident Type
The Incident Type is reported from the "Ed Code Violations" field associated with the Incident.
Note: The Incident that gets reported is based off severity of the violation. Lower values indicate higher severity. If multiple incidents exist with the same severity then assignment for state reporting will be random.
Serious Bodily Injury
The Serious Bodily Injury flag is generated for a discipline incident that indicates serious bodily injury.
Note: Incident Type must = code "00033" for this to be pulled.
Sexual Assault
The Sexual Assault flag is generated for a discipline incident that indicates Sexual Assault.
Note: Incident Type must = "60" or "61" for this to be pulled.
Initial Consequence Type
The Initial Consequence Type is generated from the "Type" when a consequence is added to an incident.
Note: Only consequence "Type" values with a state code mapping will be included for state reporting.
Initial Start Date
The Initial Start Date is generated from the "Assigned Start" date field when adding a consequence.
Secondary Consequence Type
The Secondary Consequence Type is generated the same way as the Initial Consequence Type.
Note: The Secondary Consequence Type that is pulled in the extract is the second sequential consequence added to an incident. Only consequence "Type" values with a state code mapping will be included for state reporting.
Secondary Days
Secondary Days are generated the same way as Initial Days only they are pulled from the second sequential consequence added to an incident.
Secondary Start Date
The Secondary Start Date is generated the same way as Initial Start Date only it is pulled from the second sequential consequence added to an incident.
Other Consequence Type
The Other Consequence Type is generated the same way as the Initial Consequence Type.
Note: The Other Consequence Type that is pulled in the extract is the third sequential consequence added to an incident. Only consequence "Type" values with a state code mapping will be included for state reporting.
Other Days
Other Days are generated the same way as Initial Days only they are pulled from the third sequential consequence added to an incident.
Other Start Date
The Other Start Date is generated the same way as Initial Start Date only it is pulled from the third sequential consequence added to an incident.
Follow Up
Follow Up is generated from the Follow-Up Service associated with an Incident.
Note: Only Follow-UP Services with a state code mapping will be reported.
Next Steps
If you have specific questions about this component, the data elements, or rules please reference the MSDS Collection Details Manual.
If you have additional questions about where the extract pulls data from for state reporting you can reach us via e-mail at help@illuminateed.com or by telephone at (517) 224-4499.