A Personalised Plan will be created as the result of a Core Characteristic, Legal order, Pastoral Care info, ability or Student Behaviour. Will be a document, and the community feel that SIF would most usefully capture metadata around the document. Plans can be specific to a domain, but are still expected to aggregate information gathered about student in disparate locations. This is an extensive area and it SIF needs to provide that information which needs to be transferred between systems or agencies. Broad categories of Learning Plans that have been identified so far are; Medical Plan, Learning Plan, Attendance Plan and Behavioural Plan.

The ID (GUID) assigned to uniquely identify this PersonalisedPlan.

The ID (GUID) of the student to whom this PersonalisedPlan belongs.

The ID (GUID) of the school for which this PersonalisedPlan is being reported.

Category of PersonalisedPlan.

The date the PersonalisedPlan period commenced.

The date the PersonalisedPlan is due to finish.

The date the PersonalisedPlan is due to be reviewed.

Text relating to the particular PersonalisedPlan.

Describes the Location of any associated documents kept in relation to this Response.

Link to any attachment.

Alert indicating further intervention or knowledge required with regard to a student, which could be Medical, Legal or other. Can reflect both long-term attributes of a student (Characteristics) and short-term attributes (e.g. resulting from Events). They fulfil the need for something that can be sent, associated with the student to transfer information that carries basic, important information. Lightweight, it needs to alert teachers and systems that this student has a 'concern' that needs to be known for 'duty of care'. Currently in the SIF Model there exists the concept of 'medical alerts' and 'alerts', but these are lists of events that are carried with StudentPersonal: if anything is changed then for it to be recognised by consuming systems, they would need to re-consume StudentPersonal and ALL of the lists of alerts. It was noted that this information needs to travel as the result of an event or a concern, not necessarily as a by-product of a change in StudentPersonal.

The ID (GUID) assigned to uniquely identify this WellbeingAlert.

The ID (GUID) of the student to whom this WellbeingAlert belongs.

The ID (GUID) of the school for which this WellbeingAlert is being reported.

The calendar date on which this wellbeing alert was published.

The date the wellbeing alert period commenced.

The date the wellbeing alert is due to finish.

Category of WellbeingAlert.

Description of this particular wellbeing alert.

Is this Alert Restricted to a particular enrolment at a school?

Audience for this particular wellbeing alert.

Severity of this wellbeing alert.

Key Contact to get information about this wellbeing alert from.

A WellbeingAppeal is information about an “appeal” or a “request” in regard to a (negative/punitive) WellbeingResponse to a student event.

The ID (GUID) assigned to uniquely identify this WellbeingAppeal.

The ID (GUID) of the student to whom this WellbeingAppeal belongs.

The ID (GUID) of the school for which this WellbeingAppeal is being reported.

The ID (GUID) of the WellbeingResponse for which this WellbeingAppeal is in response to.

Local system Id of the Appeal.

Status of WellbeingAppeal.

The calendar date on which this WellbeingAppeal was registered.

Text relating to the particular WellbeingAppeal.

Outcome of the particular WellbeingAppeal if known.

Describes the Location of any associated documents kept in relation to this Appeal.

Core Wellbeing Characteristic that is integral to the Student. This may be a Medical condition, special needs or a characteristic such as a known disability or any other characteristic or condition that is student specific and impacts their learning. Some characteristics are already captured in the Demographics container of StudentPersonal however this object allows for more complex and targeted information.

The ID (GUID) assigned to uniquely identify this WellbeingCharacteristic.

The ID (GUID) of the student to whom this WellbeingCharacteristic belongs.

The ID (GUID) of the school for which this WellbeingCharacteristic is being reported.

Category of WellbeingCharacteristic.

Starting Date for this Characteristic to be noted.

End date for this Characteristic to be noted, if there is one.

Date at which this information should be reviewed.

Text relating to the particular WellbeingCharacteristic.

Category of WellbeingCharacteristic.

Sub category of the WellbeingCharacteristic.

Local Code if required for Clarity.

Flag indicating if the characteristic is confidential or not. If 'Y' should not be shared with any other system/school.

Create an Alert for this Characteristic?

Describes the Location of any associated documents kept in relation to this Characteristic.

Event that impacts on a student's duty of care. This has been modelled by Sentral as an Incident, by CEOM as a behaviour support incident and by WA previously as an "Incident Report" but looking to move to terminology such as a “Wellbeing Event”. There is an emphasis that this 'event' was needed to track both 'positive' and 'negative' behaviours and it not just the recording of a discipline incident or an accident. This event is specific to a student, and is not global (e.g. a pandemic). Where an event involves more than one student, they can be listed in the person's involved. Where the event has an impact on a student's wellbeing an individual record for each student should be generated. E.g. where a student is reporting that another student fell off his bike, then the reporting student is listed as a person involved.

The ID (GUID) assigned to uniquely identify this WellbeingEvent.

The ID (GUID) of the student to whom this WellbeingEvent belongs.

The ID (GUID) of the school for which this WellbeingEvent is being reported.

A Local Identifier for the Event. It is expected to be unique to the reporting site.

Text relating to the particular WellbeingEvent.

Category of WellbeingEvent.

List of Categories of WellbeingEvent.

The ID (GUID) of the staff member who logged the Wellbeing Event record.

Details of Event Location.

Date and time of the WellbeingEvent record creation.

The calendar date on which this WellbeingEvent occurred.

The time when WellbeingEvent occurred.

A description of the WellbeingEvent.

Time period of when the event occurred.

Flag indicating if the incident is confidential or not. If 'Y' should not be shared with any other system/school.

List of People involved in the Wellbeing event. Mandatory if more people than the student to which this event occurs is involved.

List of Actions where an action resulted and is known - maybe just a link to a WellbeingResponse Object

Current Status.

Describes the Location of any associated documents kept in relation to this Response.

An outcome of a Student Wellbeing Event - or more often referred to in discussions as an 'Incident' usually will have a WellbeingResponse, action or an outcome. Many events may have WellbeingResponses that need to be reported to other systems or agencies. This may be a Suspension, an Expulsion/Exclusion, or an experience which requires reward or recognition. WA has specific language around categories of suspension—e.g. they are legally constrained not to refer to expulsion of students.

The ID (GUID) assigned to uniquely identify this WellbeingResponse.

The ID (GUID) of the student to whom this WellbeingResponse belongs.

The ID (GUID) of the school for which this WellbeingResponse is being reported.

The calendar date on which this WellbeingResponse was published.

The date the WellbeingResponse period commenced.

The date the WellbeingResponse is due to finish.

Category of WellbeingResponse.

Text relating to the particular WellbeingResponse.

>A person (additional to the student) involved in a Wellbeing event/response where required to be known.

Container for details of a Suspension or Expulsion.

Container for details of a Detention.

Container for Information to define the need for a Plan.

Container for details of an Award.

Container for details of another type of Response.

Describes the Location of any associated documents kept in relation to this Response.