Overview of Incident Management {HRM-4}
The Incident
Management module is designed to allow organisations to record and
manage activities and outcomes related to specific incidents involving
students, personnel members or Other Persons/Users {GOPS-4}.
At this stage, the
system is pre-configured with a number of Incident Types and the
user may create new incident types if required. Each Indicent Type has
its own menu option for the maintenance of related incidents,
allowing the system administrator to set access control to specific
Incident Types on menu option level.
Note
that if a new incident type is created, a new menu option for the
incident type should be created. We advise that ITS be contacted to
assist.
The following Incident Types are distributed with the system.
- Disciplinary Action
- Grievance Action (Disciplinary Actions and Grievance Actions are maintained in the same screen)
- Injury on Duty
- Traffic Violation
For each Type of Incident, the following may be defined
- A set of Incident Categories may be defined
- A set of Actions to be taken or Actions taken as a result of each incident may be defined
- A set of Outcomes, to be indicated for each action may be defined
As an example, consider possible set-up values for Incident Type "Disciplinary"
- Incident Categories (may be used to group types of offences, for example)
- Theft
- Fraud
- Absent without leave
- Actions
- Receive complaint (To log when the complaint was received)
- Investigate
- Prepare Disciplinary Committee Agenda or - Documents
- Arrange Disciplinary Committee Meeting
- Disciplinary Committee Meeting Held
- Record finding of the Disciplinary Committee
- Accused Sentenced
- Outcomes
- Decide not to proceed with disciplinary action (To be used with the "Investigate" action)
- Decide to proceed with disciplinary action (To be used with the "Investigate" action)
- Accused found guilty (To be used with "Finding of the Disciplinary Committee" action)
- Accused found not guilty (To be used with "Finding of the Disciplinary Committee" action)
- The different types of sentences may also be entered as outcome codes
|
As a second example, consider possible set-up values for Incident Type "Injury on Duty"
- Incident Categories (may be used to group types of injuries, for example)
- Burns
- Neck and Back Injuries
- Head Injuries
- Inhalation of poisonous gas
- Actions (may be used to record a variety of different data elements like)
- Place and date/time of injury
- Description of how the injury happened (Free text fields for descriptions are avaiable)
- Nature of the injury
- Initial treatment of the person/patient
- Medical Practitioner consulted
- Diagnosis of the Medical Practitioner
- Treatment Prescribed by the Medical Practitioner
- Days Hospitalised
- Days Absent from Work
- First follow up visit to Medical Practitioner
- Second follow up to Medical Practitioner
- Outcomes (only possible outcomes that may be used with the "Nature of the injury" above listed)
- Injury not serious
- First Aid Required
- Consultation with Medical Practitioner Required
- Person to be hospitalised
|
Linking to other ITS Systems
Implementation Sequence
- Incident Types {PIMCS-3}. As
mentioned above, the system is distributed with basic Incident Types
and the related menu option set-up. We advise that ITS is contacted
when a new Incident Type is to be created.
- Define the Incident Categories and Actions {PIMCS-1} to be used.
- Define the Outcome Codes to be used {PIMCS-2}
Available options
- Maintain Injuries on Duty {PIMOPS-1}
- Maintain Traffic Violations {PIMOPS-2}
- Maintain Grievances {PIMOPS-3}
- Maintain Disciplinaries {PIMOPS-4}
- Maintain Grievances and Disciplinaries {PIMOPS-5} (Note that this option can handle both Grievances and Diciplinary Actions)
History Of Changes
Date |
System Version |
By Whom |
Job |
Description |
08-Jan-2007
|
v02.0.0.0 |
Frans |
t154947 |
Proofread and Correction of Integrator Manuals
|