Branching Minds can accept data from any source system where we do not have an established direct integration using our generic file specifications. This option is also ideal for district IT teams who would like to control the data supplied to the platform. Data must be transformed to fit the following specifications.
Behavior Incidents & Details
Behavior Incidents and Incident Details files should be sent as two separate Comma-Separated Values files (CSV), to the appropriate remote paths. File names are not important, but files must be sent to the correct remote paths.
Behavior Incidents: /incoming_files/brm/behavior_incident/
Behavior Incident Details: /incoming_files/brm/behavior_incident_detail/
The Behavior Incident csv should include the column headers below:
Column header | Required? | Expected Format | Definition |
incident_id | Y | String | Unique identifier associated with the Behavior Incident |
school_id | N | String | Unique identifier for the school where the Behavior Incident occurred |
staff_id | N | String | Unique identifier for the staff member who documented the Behavior Incident |
staff_email | N | String | Email address for the staff member who documented the Behavior Incident |
description | N | String | Description of the Behavior Incident |
type | Y | String | Type of Behavior Incident |
location | N | String | The location where the Behavior Incident occurred |
date | Y* | Date | Date of Behavior Incident |
time | N | Time | Time of Behavior Incident (Local Time) |
datetime | N* | Datetime | Combined date and timestamp of Behavior Incident (Local Time) |
report_date | N | Date | Date on which the Behavior Incident was documented |
*Notes:
One of the following is required: 'date' or 'datetime'
The Behavior Incident Detail csv should include the column headers below:
Column Header | Required? | Expected Format | Definition |
incident_detail_id | Y | String | Unique identifier for the detail of the Behavior Incident |
incident_id | Y | String | Unique identifier for the Behavior Incident the detail is mapped to |
student_id | Y | String | Unique internal identifier for a student who was involved in the Behavior Incident |
student_role | N | Enumerated (Student Participant, Student Victim) | Role of the student in the behavior incident detail |
description | N | String | Description of the Behavior Incident detail involving a student |
antecedent_description | N | String | What was happening before the Behavior Incident occurred and which might trigger or prompt the behavior. |
consequence_description | N | String | What happened after the behavior, which can either reinforce or discourage the behavior from occurring again. |
restraint_used | N | Boolean | Indicates if restraint was used by staff in response to the Behavior Incident detail |
seclusion_used | N | Boolean | Indicates if seclusion was used by staff in response to the Behavior Incident detail |
deescalation_strategy_student | N | String | Strategy employed by the student to calm down or manage their behavior |
deescalation_strategy_staff | N | String | Strategy or technique staff employed to deescalate or redirect the student's behavior |
family_notification | N | Boolean | Indicates if the student's family was notified about the Behavior Incident |
police_notification | N | Boolean | Indicates if the police were notified about the behavior incident |
student_account | N | String | Student's account of the Behavior Incident |
action_taken | N | String | The action taken by staff in response to the Behavior Incident detail |
action_taken_days | N | String | The number of days of instructional time applied to the action; represents instructional time lost related to actions taken like ISS or OSS |