Maintain Injuries on Duty {PIMOPS-1}

This option allows a user to record and maintain incidents, in this case injury on Duty - incidents

Fields in this option:

Block 1: Incidents

Processing Rules for this Block (delete if not applicable).

Field	Type & Length	Description
Reference Code	A10	A reference code is automatically assigend by the system,
Incident Type	A1	The incident type related to the menu option will default into this field. For more detail refer to Incident Types {PIMCS-3}.
Incident Category	A7	Enter an Incident Category {PIMCS-1} that is valid for the Incident Type.
Date	DD-MON-YYYY	Enter the date on which the Incident took place.
Person Handling Incident	N9	The person who will be handling this incident.
Involved Person	A1	Select what type of person will be involved, is it (P)ersonnel, (S)tudent, (O)ther of (A)lumni.
Number	N9	The number of the person involved in the incident.
Department	Display	The department of the person involved will display here.
Representative Type	A1	What type of personal representation is there.(P)ersonnel, (S)tudent, (O)ther of (A)lumni.
Number	N9	Enter a valid number for the representative.
Union Code	A4	Supply a union code, if the person belongs to one.
Committee	A4	Enter the committee code.

Example:

Block 1: Page 2 of Incidents

Processing Rules for this Block (delete if not applicable).

Field	Type & Length	Description
Meeting Date	DD-MON-YYYY	If the incident resulted in a meeting to take place, the date of the meeting.may be entered here.
Action	A4	An action code may be entered here.
Start Date	DD-MON-YYYY	Enter the start date of this meeting.
End Date	DD-MON-YYYY	Enter the date ended of this meeting.
Remarks	A2000	Free textual remarks about the incidents may be entered here.
Stop Payment	A1	For personnel members, a (Y)es will result in the salary for this person not being calculated between the cycles entered below.
Start Cycle	YYYYMM	For the start cycle, once the stop payment has been set to Yes, the start cycle will populate a cycle date. Which can be changed.
End Cycle	YYYYMM	For the start cycle, once the stop payment has been set to Yes, the end cycle will populate a cycle date. Which can be changed.

Example:

Block 2: Progress / Actions

Processing Rules for this Block (delete if not applicable).

Field	Type & Length	Description
Reference Code	A10	The reference code of the Incident in the previous tab will default here.
Appeal Successful	A1	In the case of a disciplinary/grievance incident, if an appeal was logged, was the appeal successful?.
Committee	A6	If a committee is handling the actions, the committee code may be entered here.
Action Date	DD-MON-YYYY	Date and Time of the action.
Action	A4	Supply the Action Code.
Outcome Code	A4	Enter an outcome for this action.
Start Date	DD-MMM-YYYY	Supply start date of action.
End Date	DD-MMM-YYYY	Supply the end date for action.
Remarks	A65	Supply remarks in this case.

Example:

Processing Rules
	No special processing rules.