Wiki: IHIN

TRACK SAFETY INCIDENTS
Incident Info tab
Incident
Reported
Location
Phone
Incident Factors tab
Investigation tab
People Involved tab
Vehicle Reports tab
Vehicle Passenger
Witnesses tab
Associated Costs

TRACK SAFETY INCIDENTS#

The Track Safety Incidents (IHIN) allows you to record information on safety incidents. These incidents may be recorded in detail, covering information on the time, location, factors, investigation and costs surrounding a specific incident.

The definition data for the Track Safety Incidents screen is stored in the P2K_SH_INCIDENTS table.

Entity: This field identifies the entity associated with this incident. Entity from IDEN (P2K_CM_ENTITIES) is a mandatory field you must fill through the LOV.

Incident Code: This field displays a user-defined code that uniquely identifies the incident. Incident_Code is a mandatory 16-character alphanumeric field you may fill manually.

Description: This field provides a description of the incident

Incident Info tab#

Incident#

Incident Date: This field indicates the date the incident occurred. Date_of_Incident is an optional date field you must fill either manually or using the calendar icon (F9).

Incident Time: This field will display the time the incident occurred. Time_Of_Incident is an optional field you may fill manually. Please note that unless indicated otherwise, the time will default to ‘AM’. EG 4:30 PM must be inputted as either ‘430 PM’ or ‘1630’.

Incident Status: This field displays the current status of the incident. Incident_Status is an optional field you may fill from the fixed lexicon X_Incident_Status.

Incident Type: This field displays the nature of the incident. Incident_Type is an optional field you may fill from the fixed lexicon X_Incident_Type.

Incident Category: This field allows you to further categorize the incident. Incident_Category is an optional field you may fill from the user-defined lexicon X_Incident_Category.

Incident Reason: This field allows you to identify a reason for the incident, if applicable. Incident_Reason is an optional field you may fill from the fixed lexicon X_Incident_Reason.

Reported#

Report by Employee Or by Contact: These fields will identify the individual who reported the incident. This is an optional field you may fill manually or retrieve from the LOV provided.

: You may only complete one of these fields.

: * For internal contacts, use the Employee Name field. The link to IEID (P2K_HR_IDENTITIES) is made through the foreign key EID_ID.

: * For external contacts, use the Contact Name field. The link to IECI (P2K_HR_CONTACTS) is made through the foreign key ECT_ID.

Date Reported: This field displays the date the incident was reported. Date_Reported is an optional field you may fill either manually or using the calendar icon (F9).

Time Reported: This field displays the time the incident was reported. Time_Reported is an optional field you may fill manually. Please note that unless indicated otherwise, the time will default to ‘AM’. EG 4:30 PM must be inputted as either ‘430 PM’ or ‘1630’.

How Reported: This field displays the communication method used to report the incident. How_Reported is an optional field you may fill from the fixed lexicon X_How_Reported.

Anonymous: If this toggle is ON, the incident was reported anonymously. Anonymous is an optional toggle field.

Location#

Location: This field will identify the location of the incident. For instance, if an entity has two or three plants, this field will identify which plant is incident spot. Location from IDLN (P2K_CM_LOCATIONS) is a mandatory field you must fill through the LOV

Place of Incident: This field allows you to further define the exact location of the incident, by room, station, etc. Place_of_Incident is an optional 50-character alphanumeric field you may fill manually. Once the ‘Location’ field has been selected, any information defined on the IDLN table (e.g. address, phone number, email address), will default into the fields below. These fields can, however, be edited.

Address Line 1: This field displays the exact address of the incident. Address_Line_1 is an optional 50-character alphanumeric field you may fill manually.

Address Line 2: This field displays further information for the exact address of the incident. Address_Line_2 is an optional 50-character alphanumeric field you may fill manually.

Locality: This field will display the town or city of the incident. Locality is an optional 50-character alphanumeric field you may fill manually.

State/Province: This field allows you to define the state or province of the incident. State_Province from IDSP (P2K_CM_STATE_PROVINCES) is a mandatory field you must fill through the LOV.

Zip Postal: This field will display the zip or postal code for the address of the incident location. Zip_Postal is an optional 16-character alphanumeric field you may fill manually.

Phone#

Phone #: This field will display the phone number of the incident location. Phone_Number is an optional 20-character alphanumeric field you may fill manually.

Phone Extension: If there is a phone extension for the incident location, that number will be displayed here. Phone_Extension is an optional 16-character alphanumeric field you may fill manually.

Fax #: If there is a fax number for the incident location, that number will be displayed here. Fax_Number is an optional 20-character alphanumeric field you may fill manually.

Email Address: If there is an email address for the incident location, you may input that address in this field. Email_Address is an optional 50-character alphanumeric field you may fill manually.

Notification List: This field displays all those who were notified of the incident. Notification_List is an optional 4000-character alphanumeric field you may fill manually.

Incident Factors tab#

Caused By EE: If the incident was caused by a particular individual, this field allows you to identify that employee. Caused_By from IEEI (P2K_HR_EMPLOYMENTS) is an optional field you must fill with the LOV.

On State Property: If this toggle is ON, the incident occurred on state property On_State_Property is an optional toggle field.

On Employer Site: If this toggle is ON, the incident occurred at the work site. On_Employer_Site is an optional toggle field.

Entire Dept Affected: If this toggle is ON, the entire department was affected by this incident. Entire_Dept_Affected is an optional toggle field.

Vehicle Involved: If this toggle is ON, a vehicle was involved in this incident. Vehicle_Involved is an optional toggle field.

Equipment Involved: If this toggle is ON, equipment was involved in this incident. Equipment_Involved is an optional toggle field.

Incident Description: This field allows you to record additional information about the incident. Incident_Text is an optional 4000-character alphanumeric field you may fill manually.

Environmental Factors: If the work environment (e.g. windy construction site) is a factor in the incident, you may indicate those factors here. Environmental_Factors is an optional 4000-character alphanumeric field you may fill manually.

Incident Caused By: If an individual was responsible for the incident, you may indicate that person here. Incident_Caused_By is an optional 4000-character alphanumeric field you may fill manually.

Investigation tab#

Investigated by Employee Or by Contact: These fields will display the name of the individual who investigated the incident. This is an optional field you may fill manually or retrieve from the LOV provided. You may only complete one of these fields.

: * For internal contacts, use the Employee Name field. The link to IEID (P2K_HR_IDENTITIES) is made through the foreign key EID_ID_INVESTIGATED_BY.

: * For external contacts, use the Contact Name field. The link to IECI (P2K_HR_CONTACTS) is made through the foreign key ECT_ID_INVESTIGATED_BY.

Date Investigated: This field will display the date of the investigation. Date_Investigated is a mandatory date you must fill either manually or using the calendar icon (F9).

Date Closed: This field will identify the date the investigation was closed. Date_Closed is an optional date you must fill either manually or using the calendar icon (F9).

Avoidable: If this toggle is ON, the investigation determined that the incident was avoidable. Avoidable is an optional toggle field.

Investigation Result: This field allows you to provide further information about the investigation and its results. Investigation_Result is an optional 4000-character alphanumeric field you may fill manually.

People Involved tab#

Case Number: This field displays a user-defined code that uniquely identifies the investigation case number. Case_Number is a mandatory 16-character alphanumeric field you must manually fill.

Incident Date: This field will display the date the incident took place. Date_Of_Incident is mandatory field you may fill either manually or using the calendar icon (F9).

Incident Time: This field will display the time the incident occurred. Time_of_Incident is an optional field you may fill manually. Please note that unless indicated otherwise, the time will default to ‘AM’. EG 4:30 PM must be inputted as either ‘430 PM’ or ‘1630’.

Entity: This field will display the entity that the employee works for. Entity from IDEN (P2K_CM_ENTITIES) is a mandatory field you must fill through the LOV.

Injured Employee/Or Contact: These fields will display the name of any individuals who were injured by this incident. You may only complete one of these fields. This is an optional field you may fill manually or retrieve from the LOV provided. Once the ‘Injured Employee’ field has been selected, the entity, department and job fields will automatically fill with information from the IEAS screen. These fields may, however, be edited.

: * For internal contacts, use the Employee Name field. The link to IEAS (P2K_HR_ASSIGNMENTS) is made through the foreign key EAS_ID.

: * For external contacts, use the Contact Name field. The link to IECI (P2K_HR_CONTACTS) is made through the foreign key ECT_ID_REGARDING.

Department: This field will display the department the employee is assigned to. Department from IDDP (P2K_CM_DEPARTMENTS) is a mandatory field you must fill through the LOV.

Job: This field will display the employee’s job. Job from IDJB (P2K_CM_JOBS) is a mandatory field you must fill through the LOV.

View Health Issue: This button will take you to the Track Health Issues (IHHI) form.

Vehicle Reports tab#

The definition data for the Vehicle Reports screen is stored in the P2K_SH_VEHICLE_REPORTS and P2K_SH_VEHICLE_PASSENGERS table.

Vehicle Year: This field identifies the year the vehicle was made. Vehicle_Year is a mandatory field you must fill either manually or using the calendar icon (F9).

Vehicle Type: This field identifies the type of vehicle Vehicle_Type is a mandatory 16-character alphanumeric field you must manually fill.

Vehicle Make: This field identifies the make of vehicle. Vehicle_Make is a mandatory 16-character alphanumeric field you must manually fill.

Vehicle Plates: This field identifies the vehicle’s license plates. Vehicle_Plates is a mandatory 16-character alphanumeric field you must manually fill.

Vehicle Speed: This field displays how fast the vehicle was going. Vehicle_Speed is an optional 16 character alphanumeric field you may fill manually.

Driven By EE / Or By Contact: These fields will display the name of the individual driving the vehicle at the time of the incident.

: You may only complete one of these fields.

: This is an optional field you may fill manually or retrieve from the LOV provided.

: * For internal contacts, use the Employee Name field. The link to IEID (P2K_HR_IDENTITIES) is made through the foreign key EID_ID.

: * For external contacts, use the Contact Name field. The link to IECI (P2K_HR_CONTACTS) is made through the foreign key ECT_ID.

Owned By Ee / Or By Contact: These fields will display the name of the vehicle owner.

: You may only complete one of these fields.

: This is an optional field you may fill manually or retrieve from the LOV provided.

: * For internal contacts, use the Employee Name field. The link to IEID (P2K_HR_IDENTITIES) is made through the foreign key EID_ID_OWNED_BY.

: * For external contacts, use the Contact Name field. The link to IECI (P2K_HR_CONTACTS) is made through the foreign key ECT_ID_OWNED_BY.

State/ Prov: This field identifies the state or province where the vehicle is registered. State_Province from IDSP (P2K_CM_STATE_PROVINCES) is a mandatory field you must fill through the LOV.

Insurance Company: This field identifies which company insures the vehicle. Insurance_Company is an optional 50-character alphanumeric field you may fill manually.

Insurance Policy: This field identifies the policy the vehicle is insured under. Insurance_Policy is an optional 16 character alphanumeric field you may fill manually.

Company Vehicle: This field indicates if the vehicle is owned by the entity. Company_Vehicle is an optional toggle field.

Seat Belt Worn: This field indicates if the passengers were wearing seat belts. Seat_Belt_Worn is an optional toggle field.

Photos Taken: This field indicates if photos were taken at the accident site. Photos_Taken is an optional toggle field.

Recovery Cost: This field displays recovery costs associated with the incident. Recovery_Cost is an optional 18 character alphanumeric field you may fill manually.

Repair Cost: This field displays repair costs associated with the incident. Repair_Cost is an optional 18 character alphanumeric field you may fill manually.

Road Conditions: This field displays the road conditions at the time of the incident. Road_Conditions is an optional 50-character alphanumeric field you may fill manually.

Weather Conditions: This field displays the weather conditions at the time of the incident. Weather_Conditions is an optional 50-character alphanumeric field you may fill manually.

Damage: This field provides information on the damage incurred through this incident.

Vehicle_Damage is an optional 4000-character alphanumeric field you may fill manually.

Operator Statement: This field provides the accident statement from the operator of the vehicle. Vehicle_Operator_Statement is an optional 4000-character alphanumeric field you may fill manually.

Vehicle Passenger#

Passenger Employee/Contact: These fields will display the passengers in the vehicle.

: You may only complete one of these fields.

: This is an optional field you may fill manually or retrieve from the LOV provided.

: * For internal contacts, use the Employee Name field. The link to IEID (P2K_HR_IDENTITIES) is made through the foreign key EID_ID.

: * For external contacts, use the Contact Name field. The link to IECI (P2K_HR_CONTACTS) is made through the foreign key ECT_ID.

Passenger Injuries: This field will detail any injuries incurred by the passengers. Passenger_Injuries is an optional 4000-character alphanumeric field you may fill manually.

Passenger Statement: This field displays statements from the vehicle passengers. Passenger_Statement is an optional 4000-character alphanumeric field you may fill manually.

Seat Belt Worn: This field indicates if the passenger were wearing their seat belt. Seat_Belt_Worn is an optional toggle field.

Witnesses tab#

The definition data for the Incident Witnesses screen is stored in the P2K_SH_INCIDENT_WITNESSES table.

Date Interviewed: This field displays the date of the interview. Date_Interviewed is an optional date you must fill either manually or using the calendar icon (F9).

Witnessed By Employee/Contact: These fields will display the name of any witness to the incident. You may only complete one of these fields. This is an optional field you may fill manually or retrieve from the LOV provided.

: * For internal contacts, use the Employee Name field. The link to IEID (P2K_HR_IDENTITIES) is made through the foreign key EID_ID.

: * For external contacts, use the Contact Name field. The link to IECI (P2K_HR_CONTACTS) is made through the foreign key ECT_ID.

Interviewed By Employee/Contact: These fields will display the name of any witness to the incident. You may only complete one of these fields. This is an optional field you may fill manually or retrieve from the LOV provided.

: * For internal contacts, use the Employee Name field. The link to IEID (P2K_HR_IDENTITIES) is made through the foreign key EID_ID_INTERVIEWED_BY.

: * For external contacts, use the Contact Name field. The link to IECI (P2K_HR_CONTACTS) is made through the foreign key ECT_ID_INTERVIEWED_BY.

Witness Statement: This field allows you to record the witness’s statement of the incident. Witness_Statement is an optional 4000-character alphanumeric field you may fill manually.

Associated Costs#

The definition data for the Health Access screen is stored in the P2K_SH_HEALTH_COSTS table.

Cost Date: This field will display the date the cost was incurred. Cost_Date is a mandatory date field you must fill either manually or through the calendar function (F9).

Cost Category: This field allows you to further categorize the cost. Cost_Category is a mandatory field you must fill with a selection from the user-defined lexicon X_Cost_Currency.

Cost Amount: This field displays the actual amount of this health cost. Cost_Amount is an optional 18-character numeric field you may manually fill.

Currency: This field defines the currency in which the cost amount is expressed. Currency is an optional field you may fill with a selection from the fixed lexicon X_CURRENCY.

Employer %: This field will display the percent of the cost to be paid by the employer. Employer_Percent is an optional 5-character numeric field you may fill manually.

Payment Status: This field will display the current status of the payment for this cost. Payment_Status is an optional field you may fill with a selection from the fixed lexicon X_Payment_Status.

Payment Method: This field will indicate how payment was made for this cost. Payment_Method is an optional field you may fill with a selection from the fixed lexicon X_Payment_Method.

Description: This field allows you to give a short description of the health cost being defined. Description is an optional 50-character alphanumeric field you may fill manually.

Cost Reference: This field allows you to reference the cost, for example, to an invoice number. Cost_Reference is an optional 50-character alphanumeric field you may fill manually.

Table of Contents