This page (revision-39) was last changed on 26-Nov-2021 10:22 by mmcfarland

This page was created on 26-Nov-2021 10:22 by Administrator

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
39 26-Nov-2021 10:22 16 KB mmcfarland to previous
38 26-Nov-2021 10:22 15 KB mmcfarland to previous | to last
37 26-Nov-2021 10:22 15 KB mmcfarland to previous | to last
36 26-Nov-2021 10:22 14 KB mmcfarland to previous | to last
35 26-Nov-2021 10:22 14 KB mmcfarland to previous | to last
34 26-Nov-2021 10:22 13 KB rforbes to previous | to last
33 26-Nov-2021 10:22 13 KB jmyers to previous | to last
32 26-Nov-2021 10:22 13 KB jmyers to previous | to last
31 26-Nov-2021 10:22 13 KB jmyers to previous | to last EMAIL_ADDRESS ==> EMAIL_ADDRESS(Disambiguation)
30 26-Nov-2021 10:22 13 KB JMyers to previous | to last
29 26-Nov-2021 10:22 14 KB JMyers to previous | to last
28 26-Nov-2021 10:22 17 KB JMyers to previous | to last
27 26-Nov-2021 10:22 17 KB JMyers to previous | to last
26 26-Nov-2021 10:22 17 KB JMyers to previous | to last
25 26-Nov-2021 10:22 19 KB JMyers to previous | to last
24 26-Nov-2021 10:22 19 KB JMyers to previous | to last
23 26-Nov-2021 10:22 19 KB JMyers to previous | to last
22 26-Nov-2021 10:22 20 KB RForbes to previous | to last
21 26-Nov-2021 10:22 20 KB RForbes to previous | to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 1 changed one line
[{TableOfContents }] <-- only if tabbed form
[{TableOfContents }]
At line 3 removed one line
[{Image src='ILDI.JPG' width='360' align='right' link='attach/ILDI/ILDI.JPG'}]
At line 5 changed one line
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 Track Safety Incidents (IHIN) allows users to record information on safety incidents. These incidents can be recorded in detail, covering information on the time, location, factors, investigation and costs surrounding a specific incident.\\ \\
At line 6 added 2 lines
In addition, this area allows users to keep records of medical costs, exams and time lost due to illness and injury. \\ \\
At line 9 removed 3 lines
;[Entity|ENTITY_CODE]: 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|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
At line 13 changed 15 lines
!Incident
;[Incident Date|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|TIME_OF_INCIDENT]: 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|INCIDENT_STATUS]: This field displays the current status of the incident. Newly Reported Being Investigated Investigation Completed Closed Incident_Status is an optional field you may fill from the fixed lexicon X_Incident_Status.
;[Incident Type|INCIDENT_TYPE]: This field displays the nature of the incident. Safety Violation Near Miss Accident Incident_Type is an optional field you may fill from the fixed lexicon X_Incident_Type.
;[Incident Category|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|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 display the name of the individual who reported the
incident. You may only complete one of these fields. For internal contacts, use the Employee Name field and for external contacts, use the Contact Name field. Identity is derived from both the [IEID] ([P2K_HR_IDENTITIES]) and [IECT] ([P2K_HR_CONTACTS) tables. This is an optional field you may fill manually or retrieve from the LOV provided.
;Date Reported |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|TIME_REPORTS]: 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|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.
!!IHIN Field Descriptions
||Field||Description
|[Entity|ENTITY_CODE]|This field defines the entity associated with the incident.
|[Incident Code|INCIDENT_CODE]| This field displays a user-defined code that uniquely identifies the incident.
|[Description|DESCRIPTION]|This field displays a description of the incident
\\
----
!!Investigation tab
||Field||Description
|Investigated by Employee/Or By Contact|These fields define the name of the individual who investigated the incident. This is an optional field users can enter manually or retrieve from the LOV provided. \\ \\__NOTE:__ Users can select either one or the other one of these fields, but not both. \\* 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 Investigated|DATE_INVESTIGATED]|This field defines the date of the investigation.
|[Date Closed|DATE_CLOSED]|This field defines the date the investigation was closed.
|[Avoidable|AVOIDABLE]|When this toggle is set to ON, the investigation determined that the incident was avoidable.
|[Investigation Result|INVESTIGATION_RESULT]|Users can enter additional information about the investigation and the results in this field.
At line 30 changed 2 lines
[{Image src='ILDI_Tabname.JPG' width='360' align='right' link='attach/ILDI/ILDI_Tabname.JPG'}]
!!Location
!!People Involved tab
At line 33 changed 8 lines
;[Location|LOATION_CODE]: 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|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|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|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|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|STATE_PROVINCE_CODE]: 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|ZIP+POSTAL_CODE]: 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.
||Field||Description
|[Case Number|CASE_NUMBER]|This field displays the user-defined code that uniquely identifies the investigation case number.
|[Incident Date|DATE_OF_INCIDENT]|This field defines the date the incident occurred.
|[Incident Time|TIME_OF_INCIDENT]|This field defines the time the incident occurred. \\__NOTE:__ The time will default to ‘AM’, unless otherwise defined. Example: 4:30 PM must be entered as either ‘430 PM’ or ‘1630’.
|Entity|This field defines the entity the employee works for.
|Injured Employee/Or Contact|These fields define the name(s) of any individuals who were injured in the incident.
|Investigated by Employee/Or By Contact|These fields define the name of the individual who investigated the incident. This is an optional field you may fill manually or retrieve from the LOV provided.\\ \\__NOTE:__ Users can select either one or the other one of these fields, but not both. \\* 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].\\ \\Once the ‘Injured Employee’ field has been selected, the entity, department and job fields will automatically fill with information from [IEAS]. However, these fields can be edited.
|Department|This field defines the department the employee is assigned to.
|Job|This field defines the employee’s job.
|View Health Issue|This link will take users to the Track Health Issues ([IHHI]) form.
At line 42 changed 6 lines
!Phone
[Phone #|PHONE_NUMBER]: 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|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 #|FAX_NUMBER]: 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|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|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.
----
!!Vehicle Reports tab
At line 43 added one line
The definition data for the Vehicle Reports screen is stored in the [P2K_SH_VEHICLE_REPORTS] and [P2K_SH_VEHICLE_PASSENGERS] table.
At line 45 added 22 lines
||Field||Description
|[Vehicle Year|VEHICLE_YEAR]|This field defines the year the vehicle was made.
|[Vehicle Type|VEHICLE_TYPE]|This field defines the type of vehicle.
|[Vehicle Make|VEHICLE_MAKE]|This field defines the make of vehicle.
|[Vehicle Plates|VEHICLE_PLATES]|This field defines the vehicle’s license plate number.
|[Vehicle Speed|VEHICLE_SPEED]|This field defines how fast the vehicle was going.
|Driven By EE/Or By Contact|These fields define the name of the individual driving the vehicle at the time of the incident.
|Investigated by Employee/Or By Contact|These fields define the name of the individual who investigated the incident. This is an optional field users can enter manually or retrieve from the LOV provided. \\ \\__NOTE:__ Users can select either one or the other one of these fields, but not both. \\* 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 define the name of the vehicle owner.
|Investigated by Employee/Or By Contact|These fields define the name of the individual who investigated the incident. This is an optional field users can enter manually or retrieve from the LOV provided. \\ \\__NOTE:__ Users can select either one or the other one of these fields, but not both. \\* 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].\\ \\
|State/Prov|This field defines the State or Province where the vehicle is registered.
|[Insurance Company|INSURANCE_COMPANY]|This field defines the company that insures the vehicle.
|[Insurance Policy|INSURANCE_POLICY]|This field defines the policy the vehicle is insured under.
|[Company Vehicle|COMPANY_VEHICLE]|When this toggle is set to ON, the vehicle is owned by the entity.
|[Seat Belt Worn|SEAT_BELT_WORN]|When this toggle is set to ON, the operator of the vehicle was wearing a seat belt.
|[Photos Taken|PHOTOS_TAKEN]|When this toggle is set to ON, photos were taken at the accident site.
|[Recovery Cost|RECOVERY_COST]|This field defines the recovery costs associated with the incident.
|[Repair Cost|REPAIR_COST]|This field defines the repair costs associated with the incident.
|[Road Conditions|ROAD_CONDITIONS]|This field defines the road conditions at the time of the incident.
|[Weather Conditions|WEATHER_CONDITIONS]|This field defines the weather conditions at the time of the incident.
|[Damage|VEHICLE_DAMAGE]|This field defines the damage sustained during the incident.
|[Operator Statement|VEHICLE_OPERATOR_STATEMENT]|Users can enter the accident statement from the operator of the vehicle in this field.
At line 68 added 9 lines
!Vehicle Passenger
||Field||Description
|Passenger Employee/Contact|These fields define the passengers in the vehicle.
|Investigated by Employee/Or By Contact|These fields define the name of the individual who investigated the incident. This is an optional field users can enter manually or retrieve from the LOV provided. \\ \\__NOTE:__ Users can select either one or the other one of these fields, but not both. \\* 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|PASSENGER_INJURIES]|This field defines any injuries sustained by the passengers during the incident.
|[Passenger Statement|PASSENGER_STATEMENT]|Users can enter the accident statement(s) from the vehicle passenger(s).
|[Seat Belt Worn|SEAT_BELT_WORN]|When this toggle is set to ON, the passengers were wearing seat belts.
\\
At line 52 changed 2 lines
[{Image src='ILDI_Tabname.JPG' width='360' align='right' link='attach/ILDI/ILDI_Tabname.JPG'}]
!!Tab Headings
!!Witnesses tab
At line 55 changed 2 lines
!Section Headings within in each tab
;[FieldName]:Definition
The definition data for the Incident Witnesses screen is stored in the [P2K_SH_INCIDENT_WITNESSES] table.
||Field||Description
|[Date Interviewed|DATE_INTERVIEWED]|This field defines the date of the interview.
|Witnessed By Employee/Contact|These fields define the name(s) of any witness(es) of the incident.
|Investigated by Employee/Or By Contact|These fields define the name of the individual who investigated the incident. This is an optional field users can enter manually or retrieve from the LOV provided. \\ \\__NOTE:__ Users can select either one or the other one of these fields, but not both. \\* 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 define the individual who interviewed the witness(es) of the incident.
|Investigated by Employee/Or By Contact|These fields define the name of the individual who investigated the incident. This is an optional field users can enter manually or retrieve from the LOV provided. \\ \\__NOTE:__ Users can select either one or the other one of these fields, but not both. \\* 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].\\ \\
|[Witness Statement|WITNESS_STATEMENT]|Users can enter the witness’s statement of the incident in this field.
\\
----
!!Associated Costs tab
The definition data for the Health Access screen is stored in the [P2K_SH_HEALTH_COSTS] table.
||Field||Description
|[Cost Date|COST_DATE]|This field defines the date the cost was incurred.
|[Cost Category|COST_CATEGORY]|This field defines the category the cost.
|[Cost Amount|COST_AMOUNT]|This field defines the actual amount of the health cost.
|[Currency|CURRENCY]|This field defines the currency in which the cost amount is expressed in.
|[Employer %|EMPLOYER_PERCENT]|This field defines the percent of the cost to be paid by the employer.
|[Payment Status|PAYMENT_STATUS]|This field defines the current status of the payment for the cost.
|[Payment Method|PAYMENT_METHOD]|This field defines how the payment was made for the cost.
|[Description]|This field displays a short description of the health cost being defined.
|[Cost Reference|CROSS_REFERENCE]|Users can enter a reference the cost, such as an invoice number.
----
!!Incident Info tab
!Incident Area
||Field||Description
|[Incident Date|INCIDENT_DATE]|This field defines the date the incident occurred. Optional.
|[Incident Time|TIME_OF_INCIDENT]|This field defines the time the incident occurred. \\ \\__NOTE:__ The time will default to ‘AM’, unless otherwise defined. Example: 4:30 PM must be entered as either ‘430 PM’ or ‘1630’. \\Optional.
|[Incident Status|INCIDENT_STATUS]|This field defines the current status of the incident. Options are: \\* Newly Reported \\* Being Investigated \\* Investigation Completed\\* Closed. \\Optional.
|[Incident Type|INCIDENT_TYPE]|This field defines the nature of the incident. Options are: \\* Safety Violation \\* Near Miss \\* Accident.\\Optional
|[Incident Category|INCIDENT_CATEGORY]|This field further categorizes the incident. Optional
|[Incident Reason|INCIDENT_REASON]|This field defines a reason for the incident, if applicable. Options are: \\* Substance Abuse \\* Machine Failure \\* Not Use Safety Device \\* Disobeyed Rules
!Location Area
||Field||Description
|[Location|LOCATION_CODE]|Mandatory. This field defines the location of the incident. Example: If an entity has two or three plants, this field will identify which plant the incident occurred at.
|[Place of Incident|PLACE_OF_INCIDENT]|This field further defines the exact location of the incident, by room, station, etc. Optional
|[Address Line 1|ADDRESS_LINE_1]|This field defines the exact address of the incident. \\__NOTE:__ Once the ‘Location’ field (above) has been defined, any location information defined on [IDLN], such as address, phone number, email address, etc. will automatically populate the address fields below. However, these fields can be edited.
|[Address Line 2|ADDRESS_LINE_2]| Users can enter further information for the exact address of the incident. Optional.
|[Locality|LOCALITY]|This field defines the Town or City of the incident. Optional.
|[State/Province|STATE_PROVINCE_CODE]|Mandatory. This field defines the State or Province of the incident.
|[Zip Postal|ZIP_POSTAL]|This field defines the zip or postal code for the address of the incident location. Optional
!Reported Area
||Field||Description
|Reported by Employee/Or by Contact|These fields define the individual who reported the incident. This is an optional field users can enter manually or retrieve from the LOV provided. \\ \\__NOTE:__ Users can select either one or the other one of these fields, but not both. \\* 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].\\ \\
|Investigated by Employee/Or By Contact|These fields define the name of the individual who investigated the incident. This is an optional field users can enter manually or retrieve from the LOV provided. \\ \\__NOTE:__ Users can select either one or the other one of these fields, but not both. \\* 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 |DATE_REPORTED]|This field defines the date the incident was reported. \\__NOTE:__ The system allows for the Date Reported to be earlier than the Incident Date.\\Optional.
|[Time Reported|TIME_REPORTED]|This field defines the time the incident was reported. \\ \\__NOTE:__ The time will default to ‘AM’, unless otherwise defined. Example: 4:30 PM must be entered as either ‘430 PM’ or ‘1630’.
|[How Reported|HOW_REPORTED]|This field defines the communication method used to report the incident. Options are: \\* In Person \\* Email \\* Phone \\* Fax \\* Self Service \\Optional.
|[Anonymous|ANONYMOUS]|When this toggle is set to ON, the incident was reported anonymously.
|Not OSHA Reportable| |
!Phone Area
||Field||Description
|[Phone #|PHONE_NUMBER]|This field defines the phone number of the incident location.
|[Phone Extension|PHONE_EXTENSION]|This field defines the phone extension number for the incident location, if applicable.
|[Fax #|FAX_NUMBER]|This field defines the fax number for the incident location, if applicable.
|[Email Address|EMAIL_ADDRESS(Field)]|This feild defines an email address for the incident location, if applicable.
|[Notification List|NOTIFICATION_LIST]|This field defines all individuals who were notified of the incident.
\\
----
!!Incident Factors tab
||Field||Description
|Caused By EE|Defines the name of the specific employee that caused the incident.
|[On Government Property|ON_STATE_PROPERTY]|When this toggle is set to ON, the incident occurred on government property
|[On Employer Site|ON_EMPLOYER_SITE]|When this toggle is set to ON, the incident occurred at the work site.
|[Entire Dept Affected|ENTIRE_DEPT_AFFECTED]|When this toggle is set to ON, the entire department was affected by the incident.
|[Vehicle Involved|VEHICLE_INVOLVED]|When this toggle is set to ON, a vehicle was involved in the incident.
|[Equipment Involved|EQUIPMENT_INVOLVED]|When this toggle is set to ON, equipment was involved in the incident.
|[Incident Description|INCIDENT_TEXT]|Users can enter additional information about the incident in this field.
|[Environmental Factors|ENVIRONMENTAL_FACTORS]|If the work environment, such as a windy construction site, is a factor in the incident, the factors are defined in this field.
|[Incident Caused By|INCIDENT_CAUSED_BY]|Defines the name of the specific individual (not an employee) that caused the incident.
\\
----
![Notes|Edit:Internal.IHIN]
[{InsertPage page='Internal.IHIN' default='Click to create a new notes page'}]