US20070061357A1

US20070061357A1 - Computer-implemented process of reporting injured worker information

Info

Publication number: US20070061357A1
Application number: US11/527,780
Authority: US
Inventors: Michael Jensen
Original assignee: Individual
Current assignee: Individual
Priority date: 1995-07-19
Filing date: 2006-09-25
Publication date: 2007-03-15
Also published as: US20100185636A1; US7113940B1

Abstract

Predefined lists of selected variables are created and interrelated to produce incident reports. The lists are created and modified through the use of formatted computer screens or input forms, and the reports are produced through the use of formatted computer outputs or output formats. The lists include accident-related information such as industry types, occupations, safety teams, attendance codes, types of injuries, body parts affected, types of incidents, site conditions, accident causes and safety reminders. The input forms often correspond directly to the types of lists, so that there is a form through which the list of industry types is created and/or modified, and another form through which the list of occupations is created. In addition, there are input forms that allow creation and/or modification of several lists at one time, particularly when each element in one list is directly associated with one element from another list. The output formats include agency-related formats such as an OSHA (Occupational Safety & Health Administration) No. 200 report, and statistical summaries used for managerial decision making. The statistical summaries may be textual or graphical, or a combination of textual and graphical.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 09/557,878, filed Apr. 24, 2000 and entitled “Computer-Implemented Process of Reporting Injured Worker Information”, which is a continuation of from U.S. patent application Ser. No. 08/684,217 entitled “Computer-Implemented Process Of Reporting Injured Worker Information” filed on Jul. 19, 1996, which claims priority from U.S. Provisional Patent Application Ser. No. 60/001,281 entitled “Incident Reporting System” filed on Jul. 19, 1995.

TECHNICAL FIELD

This invention relates generally to the organization, coordination and presentation of data related to workplace incidents such as accidents resulting in worker injuries. For example, the invention includes a method of prompting a user for information about the workplace such as employee identification, accident and injury classification, and educational and precautionary actions to be taken. The invention also includes a method of prompting a user for information necessary to complete accident reports of the type required by federal, state and local agencies, and reports useful for making managerial decisions about the workplace. The recording and reporting of statistics about such incidents is both necessary to comply with governmental regulations, and useful to evaluate and improve workplace safety. The present invention provides a system for the administration and support of the industry process known as light duty/restricted duty/recurrence of injury recording, analysis and reporting.

BACKGROUND ART

In the past, a myriad of paper and paperless forms have been developed and used to aid in this process. For example, OSHA (Occupational Safety & Health Administration) form No. 200 is a fill-in-the-blanks form, with blanks for specific information about a given accident, such as the name of the injured, the type of injury, the severity of the injury and the extent of any resulting absence from work. While it is relatively simple for a user to complete the form, only the most experienced user is able to complete the form with any type of standardization. Furthermore, it is difficult to coordinate such standardization among disparate users, as is desirable in a large, multi-plant workplace. Computer databases have also been used to track employee information and accident statistics. However, no method has, prior to the present invention, interrelated predefined lists of the possible variables used in accident reporting to repeatably produce consistent accident reports, nor has any previously done so using a plurality of defined lists of such variables stored on a computer.

DISCLOSURE OF THE INVENTION

The present invention includes predefined lists of selected variables, the methods of creating and interrelating such lists, and the methods of using such lists to produce incident reports. The lists are created and modified through the use of formatted computer screens, referred to herein as input forms, and the reports are produced through the use of formatted computer outputs, referred to herein as output formats. The lists include accident-related information such as industry types, occupations, safety teams, attendance codes, types of injuries, body parts affected, types of incidents, site conditions, accident causes and safety reminders. The input forms often correspond directly to the types of lists, so that there is a form through which the list of industry types is created and/or modified, and another form through which the list of occupations is created. In addition, there are input forms that allow creation and/or modification of several lists at one time, particularly when each element in one list is directly associated with one element from another list. The output formats include agency-related formats such as the OSHA 200 report discussed above, and statistical summaries used for managerial decision making. The statistical summaries may be textual or graphical, or a combination of textual and graphical.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a conventional user workstation that may act as a hardware/firmware platform for the software of the present invention, including an accident reporting system and invented method and apparatus which forms a part thereof;
FIG. 2 is a control flow diagram of the software of the present invention;
FIG. 3 is an example of a form through which information is added to a list as part of the present invention;
FIG. 4 is an example of an OSHA 200 form produced by the present invention;
FIG. 5 is an example of a graphical accident analysis by nature of injury, produced by the present invention;
FIG. 6 is an example of a graphical accident analysis by type of accident, produced by the present invention;
FIG. 7 is an example of a graphical accident analysis by day of the week, produced by the present invention;
FIG. 8 is an example of a textual/graphical accident analysis showing the status of accident investigations, produced by the present invention;
FIG. 9 is an example of a textual report showing the vital statistics for employees, produced by the present invention;
FIG. 10 is an example of a textual accident analysis listing a synopsis of each accident by period, produced by the present invention; and
FIG. 11 is a data flow diagram of the present invention.
FIGS. 12-71 are illustrations from the operating instructions of a preferred embodiment of the invention.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT
Referring first to FIG. 1, a user workstation is shown generally at 10, including a general-purpose computer typically providing a digital processor 12 containing an arithmetic logic unit (ALU) and various registers typically including register stacks, scratchpad memories and accumulators. Skilled persons also will appreciate that the workstation also typically will provide computer memory such as mass data storage 14, e.g. a hard or flex disk drive 14 a, 14 b, or both, as well as a quantity of read-and-write semiconductor memory (RAM) 16 (shown in outline as residing within workstation 10 and its housing 18) in which application programs reside for execution by processor 12. Finally, skilled persons will appreciate that the workstation also typically will provide one or more user interfaces or display mediums such as a video display terminal (VDT) 20, a keyboard 22 and an associated display cursor control system 24 including, for example, a mouse or joystick 24 a, 24 b, or both. In addition to disk drives 14 a and b, RAM 16 and VDT 20, other computer output mediums might be included such as printers, communication networks or other storage devices. All such conventional hardware, firmware and software-executing-on-a-hardware/firmware platform architectures for the accident report system of the present invention are contemplated, and all are within the spirit and scope of the present invention.
Referring now to FIG. 2, a highly simplified control flow diagram is shown of the software executed on user workstation(s) 10 of the present system. The software is preferably stored on mass data storage device 14, then loaded into RAM 16 by digital processor 12. The represented steps of displaying control panels, forms and reports are logical displays, generated by digital processor(s) 12 on one or more VDTs 20 at one or more user workstations 10. The user would then be able to review the information on VDTs 20 and modify the database(s) stored on mass storage device(s) 14. This is done through the use of input devices like keyboards 22 or display cursor control systems 24.
A step of system startup 26 includes a verification of database integrity by determining if any other users currently are attached to the database, and to verify that all required elements of the database are available. After startup 26, there is a check to determine if any recent incidents have occurred, at 28. If such an incident has occurred, then the incident form is accessed and displayed at 30. If there is no recent incident, or if review of such a recent incident is completed, control is then transferred to the main control panel 32, another logical display operated on by the user through keyboards 22 or display cursor control systems 24.
One option at control panel 32 is to check again to determine if there are any recent incidents by returning to step 28. A second option is to direct the operation of the program to selecting an input form, at 34. Once such an input form has been selected, it is displayed at 36. When the user is done reviewing the displayed form, another input form may be selected at 34. Alternatively, there is a return to the main control panel at 32.
A third option from the main control panel is to direct control to selecting a report format, at 38. A selected report format is displayed as indicated at 40, after which control is returned to selecting a report format at 38. As with selecting an input form at 34, control can now be returned to the main control panel at 32.
Cross-transfer of control is available from selecting an input format 32 directly to selecting a report format at 38, and vice versa, as shown.
A fourth transfer available from the main control panel at 32 is to import data at 42, from external databases, at 44. Similarly, control can be transferred from the main control panel at 32 to export data at 46, to external databases, at 48.
Each of the above steps usually requires access at 50 to the internal database(s) 52. This access is controlled to ensure system data integrity and confidentiality. Database 52 is preferably stored on mass storage devices 14 that are controlled and accessed through a single digital processor 12, with the step of controlling access being performed by this processor 12. Processor 12 may in turn be connected to other user work stations 10, for example through a local area network (LAN), a wide area network (WAN) or a modem.
For reference, database 52 could include a system database containing lists of entries or records that might be selected to describe any given incident, an incident database containing lists of records that describe specific incidents, or both. The system database might also be referred to as a company database, particularly when the database has been customized for a particular company. For example, database 52 might include information on the company address, parents or subsidiaries, employees or specific types of incidents expected in the company's operations.
Referring now to FIG. 3, a sample input form is shown, including a screen image 54. Within screen image 54 there are insert-from-list fields at 56, which when selected with cursor control system 24 present a defined list of selectable variables from the system database. Cursor control 24 can then be operated to select one of such variables and to enter the selected variable into field 56. Next, there are direct-entry fields 58, into which the user inserts the requested information, using, for example, keyboard 22. Fields 56 may also provide for such direct entry of information. Screen image 54 further includes one or more control buttons 60, the selection of which, using cursor control 24, transfers control from the displayed form to a different form, report or control panel. Exiting screen image 54 causes the added or modified information from fields 56 and 58 to be written to incident database 52 b.
An example of a completed OSHA 200 report is shown in FIG. 4. This report includes numerous rows 62 and columns 64 of information. The rows represent a record for a single incident, and the columns represent selected elements or entries from such records.
In FIGS. 5, 6 and 7, graphical reports are shown, with the graph being indicated generally at 66, a key being indicated at 68, and summary of the scope of the report being indicated at 70. In FIGS. 8, 9 and 10, textual reports are shown with text fields at 72 and with graphical status indicators at 74.
It will be appreciated that the overall database structure can be accomplished in many different forms. For example, each of the lists referred to in more detail below could be stored in a separate file in either mass data storage device 14 or RAM 16, or several or all of the lists could be accumulated into a single file in such devices. Furthermore, the files could be stored on a variety of different storage media, or even distributed about either a local area network or a wide area network. Thus, reference herein to a system database as opposed to an incident database could be reference to the same file/storage device 14/16, or an intertwined assemblage of files/storage devices 14/16, whether closely or loosely associated.
The use of “system” and “incident” identifiers for databases 52 a and 52 b is not as a description of a particular database structure, but as a description of the relationship of one type of list of records to another. The system database includes a plurality of defined lists of system records of selected variables and a plurality of defined report formats for producing selected incident reports. The selected variables define possible aspects of a given incident, such as the body part injured. By pre-defining the variables, completion of incident reports is standardized. For example, a human arm can also be referred to as an upper limb or an upper extremity, detailed to include the forearm, elbow and upper arm, or described using specific tissues or bones. If the list of body parts includes a record listing “ARM,” then the user need only select this record, and need not deliberate as to whether the proper description would be one of the above-discussed alternatives. The selecting of a specific record also includes the automatic step of extracting the selected record from the system database for manipulation and/or use in a different record.
The incident database includes one or more defined lists of incident records of data, each incident record describing one or more aspects of a specific incident. Using the present invention, each incident record would normally contain one or more elements that were extracted and/or manipulated from the system database, as discussed above. Thus, each incident record would be standardized, regardless of who entered the information into the incident record.
The use of the system database to complete a record in the incident database also allows for the efficient creation of a more complete record. For example, when an incident occurs, all that may be known is the name of the injured worker and a simple description of what happened. By accessing the system database using that worker's name alone, additional information can be inserted automatically into the incident record, such as the worker's address, social security number, insurer, manager or special medical issues. Furthermore, the selection of a specific type of incident from a predefined list may automatically insert into the incident record a list of suggested corrective actions, follow-up procedures or reporting requirements. In addition, such selection might automatically generate a message for communication to a predefined list of other affected workers about the accident, and about how to avoid further accidents.
A further aspect of the present invention is to provide a direct comparison of the incident for which the user is viewing or modifying the information in the incident database to previously recorded incident records. For example, when a manager is inputting the initial information about an incident caused by constricted space, if there are other incidents already recorded in which constricted space was a contributing cause, the number of these similar, earlier incidents would be displayed on the incident input form. This immediate feedback is helpful in highlighting and identifying possible corrective steps to prevent the occurrence of yet further accidents.
In the preferred embodiment, the system/incident database(s) include at least the following lists of records: LIST OF DATABASES, INPUT FORMS, INPUT FORM DESCRIPTIONS, REPORT FORMATS, REPORT FORMAT DESCRIPTIONS, PARENTS/SUBSIDIARIES, COMPANY INFORMATION, INDUSTRY TYPES, LOCATIONS, OCCUPATIONS, DEPARTMENTS, SAFETY TEAMS, HOLIDAYS, EMPLOYEES, ATTENDANCE, ABSENCE CODES, HOSPITALS, ACCIDENTS, NATURE OF INJURY, BODY PARTS, INCIDENT TYPE, CONDITIONS, CAUSES, FED/STATE AGENCIES, AGENCY RECORDINGS, AWARENESS CODES, TRAINING CLASSES, TRAINING INTERVALS, TRAINING ROSTERS, TRAINING TESTS, TEST RESULTS and SAFETY REMINDERS.

The preferred data record structure of some of the lists of the system database are demonstrated by tables 1-3.

TABLE 1


List of Fields For Import/Export Purposes-Company Setup

#	Field Name	Description	Data Type

1.	Company Name	Company Name	Text
2.	Address #1	Address 1 of Company	Text
3.	Address #2	Address 2 of Company	Text
4.	City	Company City	Text
5.	State	Company State	Text
6.	Zip	Company Zip	Text
7.	County	Company County	Text
8.	Phone	Company Phone	Text
9.	Fed ID Number	Employer's FEIN	Number
10.	Plant/Location #	Company's Plant and Location No.	Text
11.	Primary Contact	Primary Contact w/ Company	Text
12.	Secondary Contact	Second Company Contact	Text
13.	General Mgr or President	General Manager or President of Co.	Text
14.	General Nature of Business	General Nature of Business	Text
15.	Primary Hospital	Primary-Use Hospital for Co.	Text
16.	# Accidents To-Date	No. of Accidents To-Date	Number
17.	# Employees Enrolled To-Date	No. of Employees Enrolled To-Date	Number
18.	Avg Length of Employment	Average Length of Employment	Number
19.	State of Operatoin	State of Operation	Text
20.	Corp Type - Corporation	CB/Corporation Type of Corporation	Yes/No
21.	Corp Type - Partnership	CB/Partnership Type of Corporation	Yes/No
22.	Corp Type - Other	CB/Other Type of Corporation	Yes/No
23.	Ins Co	Insurance Co. Name	Text
24.	Ins Address1	Insurance Co. Address1	Text
25.	Ins Address2	Insurance Co. Address2	Text
26.	Ins City	Insurance Co. City	Text
27.	Ins State	Insurance Co. State	Text
28.	Ins Zip	Insurance Co. Zip	Text
29.	Ins Phone	Insurance Co. Phone	Text
30.	Ins Division1	Insurance Co. Division1	Text
31.	Ins Division2	Insurance Co. Division2	Text
32.	Ins Division3	Insurance Co. Division3	Text
33.	Co Logo	Company's Logo	OLE Object

Note:
The file you are importing must include all of the above listed columns in the order and data types. If your file does not originally have all of these fields (which it probably won't), you will need to make a “SPACER” column for each one that is missing and insert them in the correct position.
This “SPACER” function will be much easier if you are importing a spreadsheet file, than if you are importing an ASCII text file. Remember, even if your file is an ASCII text file, you can open that text file in Excel or Lotus and use the “Parse” function to separate the information into organized columns. Then import the completed files.

TABLE 2


List of Fields For Import/Export Purposes-Master Names

#	Field Name	Description	Data Type

1.	ID	Employee ID	Counter
2.	LAST	Employee's Last Name	Text
3.	FIRST	Employee's First Name	Text
4.	SSN	Employee's Social Security Number	Number
5.	Birthday	Employee's Date of Birth	Date/Time
6.	LOE	Employee's Length of Employment	Text
7.	ADJ	Employee's ADJ	Date/Time
8.	Address	Employee's Address	Text
9.	City	Employee's City	Text
10.	State	Employee's State	Text
11.	Zip	Employee's Zip	Number
12.	PHONE	Employee's Phone	Text
13.	DEPT	Employee's Department No.	Text
14.	Dept Name	Employee's Dept Name	Text
15.	Company	Company Name	Text
16.	Locale	Location of Company	Text
17.	HrlyRate	Employee Hourly Wage	Number
18.	Occupation	Employee's Occupation	Text
19.	TeamCode	Employee's Team Code	Text
20.	TeamName	Employee's Team Name	Text

Note:
The file you are importing must include all of the above listed columns in the order and data types. If your file does not originally have all of these fields (which it probably won't), you will need to make a “SPACER” column for each one that is missing and insert them in the correct position.
This “SPACER” function will be much easier if you are importing a spreadsheet file, than if you are importing an ASCII text file. Remember, even if your file is an ASCII text file, you can open that text file in Excel or Lotus and use the “Parse” function to separate the information into organized columns. Then import the completed files.

TABLE 3


List of Fields For Import/Export Purposes-Injury Reminder

#	Field Name	Description	Data Type

1.	Accident Type	Type of Accident	Text
2.	Reminder	Reminder of Accident	Memo

Note:
The file you are importing must include all of the above listed columns in the order and data types. If your file does not originally have all of these fields (which it probably won't), you will need to make a “SPACER” column for each one that is missing and insert them in the correct position.
This “SPACER” function will be much easier if you are importing a spreadsheet file, than if you are importing an ASCII text file. Remember, even if your file is an ASCII text file, you can open that text file in Excel or Lotus and use the “Parse” function to separate the information into organized columns. Then import the completed files.

The preferred data record structures of some of the lists of the incident database are demonstrated by tables 4-6.

TABLE 4


List of Fields For Import/Export Purposes-Accident Form

#	Field Name	Description	Data Type

1.	ID	Accident ID	Counter
2.	Last	Employee Last Name	Text
3.	First	Employee First Name	Text
4.	Company	Company Name	Text
5.	Locale	Co. Plant Location	Text
6.	Department	Department Number	Text
7.	Dept Name	Department Name	Text
8.	Phone	Employee Phone Number	Text
9.	DOB	Employee Date of Birth	Text
10.	Sex Male	Check Box/Employee's Sex-Male	Yes/No
11.	Sex Female	Check Box/Employee's Sex-Female	Yes/No
12.	SSN	Employee Social Security Number	Text
13.	Address	Employee Address	Text
14.	City	Employee City	Text
15.	State	Employee State	Text
16.	Zip	Employee Zip	Number
17.	LOE	Employee Length of Employment	Text
18.	Hired	Date Employee Hired	Text
19.	Hospitalized	Check Box/Was Employee Hospitalized	Yes/No
20.	Hospital Name	Name of Hospital Emp. was taken to	Text
21.	Date of Injury	Date Injury Occurred	Date/Time
22.	Time of Injury	Time Injury Occurred	Date/Time
23.	Time in Dept	Time Employee's been in Dept	Text
24.	Name of Physician	Emp. Treating Physician	Text
25.	Body Part	Part of Employee Body that was Injured	Text
26.	Body Part - Left	Check Box/Left side of Emp. Body	Yes/No
27.	Body Part - Right	Check Box/Right side of Emp. Body	Yes/No
28.	Injured Previously	CB/Had Emp. Injured Body Part Before	Yes/No
29.	Nature of Injury	Nature of Employee's Injury	Text
30.	Cause	Cause of Employee's Injury	Text
31.	Condition	Condition that Contributed to Injury	Text
32.	Accident Type	What Type of Accident Caused Injury	Text
33.	Accident Description	Description of the Accident	Memo
34.	Corrective Action Taken	What Corrective Action Taken	Memo
35.	Date Corrective Action Taken	Date the Corrective Action was Taken	Date/Time
36.	Witness	Witness of the Accident	Text
37.	Date Company Knew	Date that Company First Knew of Acc.	Date/Time
38.	Street Address of Accident	Address Where Accident Occurred	Text
39.	Nature of Business	Nature of Business	Text
40.	County of Injury	County where Injury Occurred	Text
41.	Emp Worker Status - Yes	Check Box -	Yes/No
42.	Emp Worker Status - No	Check Box -	Yes/No
43.	Emp Occupation	Occupation of Emplooyee	Text
44.	Length of Employment	Length of Time Emp. Worked for Co.	Date/Time
45.	Injured on Premises - Yes	CB/Was Emp Injured on Premises - Yes	Yes/No
46.	Injured on Premises - No	CB/Was Emp Injured on Premises - No	Yes/No
47.	Fatality	CB/Was Accident a Fatality	Yes/No
48.	Injured on Job - Yes	CB/Did Injury Occur on the Job - Yes	Yes/No
49.	Injured on Job - No	CB/Did Injury Occur on the Job - No	Yes/No
50.	Injured on Job - Unknown	CB/Injury Occur on the Job - Unknown	Yes/No
51.	Other Workers Injured	CB/Were Other Workers Injured	Yes/No
52.	Accident Result of Machine Failure	CB/Acc. a Result of Machine Failure	Yes/No
53.	Accident Caused by Someone Else	CB/Acc. Caused by Someone Else	Yes/No
54.	Company Accident Description	Company's Description of Accident	Memo
55.	801 OSHA To Be Filed?	CB/Is 801 OSHA to be Filed	Yes/No
56.	Previous Injury Description	Description of Previous Injury	Text
57.	Shift Start	Beginning of Employee's Shift	Date/Time
58.	Shift End	End of Employee's Shift	Date/Time
59.	Date Worker Left	Date Employee Left Work	Date/Time
60.	Time Worker Left	Time Employee Left Work	Date/Time
61.	Date Worker Returned	Date Worker Returned From Disability	Date/Time
62.	Number Hrs Per Shift	Number Hrs Employee Works Per Shift	Number
63.	Days Worked - 3 or less	CB/Emp. Reg. Works less then 3 days	Yes/No
64.	Days Worked - 4	CB/Emp. Reg. Works 4 days	Yes/No
65.	Days Worked - 5	CB/Emp. Reg. Works 5 days	Yes/No
66.	Days Worked - 6	CB/Emp. Reg. Works 6 days	Yes/No
67.	Days Worked - 7	CB/Emp. Reg. Works 7 days	Yes/No
68.	Days Off - Sat	CB/Emp. Reg. Days Off - Sat	Yes/No
69.	Days Off - Sun	CB/Emp. Reg. Days Off - Sun	Yes/No
70.	Days Off - Mon	CB/Emp. Reg. Days Off - Mon	Yes/No
71.	Days Off - Tue	CB/Emp. Reg. Days Off - Tue	Yes/No
72.	Days Off - Wed	CB/Emp. Reg. Days Off - Wed	Yes/No
73.	Days Off - Thurs	CB/Emp. Reg. Days Off - Thurs	Yes/No
74.	Days Off - Fri	CB/Emp. Reg. Days Off - Fri	Yes/No
75.	Wage	Employee's Current Wage	Number
76.	Wage - Hr	CB/Emp. Wage Per Hour	Yes/No
77.	Wage - Wk	CB/Emp. Wage Per Week	Yes/No
78.	Wage - Day	CB/Emp. Wage Per Day	Yes/No
79.	Wage - Mo	CB/Emp. Wage Per Month	Yes/No
80.	Wage - Yr	CB/Emp. Wage Per Year	Yes/No
81.	DirectMedical	Direct Medical Costs to Company	Currency
82.	AdminCosts	Administration Costs to Company	Currency
83.	EmpCompCosts	Employer Contribution	Currency
84.	TotalCompCosts	Total Compensation Costs By Company	Currency
85.	EstLongTermCosts	Estimated Long Term Costs to Company	Currency
86.	TeamCode	Team Code	Text
87.	TeamName	Team Name	Text

Note:
The file you are importing must include all of the above listed columns in the order and data types. If your file does not originally have all of these fields (which it probably won't), you will need to make a “SPACER” column for each one that is missing and insert them in the correct position.
This “SPACER” function will be much easier if you are importing a spreadsheet file, than if you are importing an ASCII text file. Remember, even if your file is an ASCII text file, you can open that text file in Excel er Lotus and use the “Parse” function to separate, the information into organized columns. Then import the cempleted files.

TABLE 5


List of Fields For Import/Export Purposes-OSHA-AccExport

#	Field Name	Description	Data Type

1.	Last	Employee Last Name	Text
2.	First	Employee First Name	Text
3.	Name	Employee Name	Text
4.	ID	Accident ID	Counter
5.	Department	Department Number	Text
6.	Dept Name	Department Name	Text
7.	Phone	Employee Phone Number	Text
8.	DOB	Employee Date of Birth	Text
9.	Sex Male	Check Box/Employees Sex-Male	Yes/No
10.	Sex Female	Check Box/Employees Sex-Female	Yes/No
11.	SSN	Employee Social Security Number	Text
12.	Address	Employee Address	Text
13.	City	Employee City	Text
14.	State	Employee State	Text
15.	Zip	Employee Zip	Number
16.	LOE	Employee Length of Employment	Text
17.	Hired	Date Employee Hired	Text
18.	Hospitalized	Check Box/Was Employee Hospitalized	Yes/No
19.	Hospital Name	Name of Hospital Emp. was taken to	Text
20.	Date of Injury	Date Injury Occurred	Date/Time
21.	Month	Month	Text
22.	Time of Injury	Time Injury Occurred	Date/Time
23.	Time in Dept	Time Employee's been in Dept	Text
24.	Name of Physician	Emp. Treating Physician	Text
25.	Body Part	Part of Employee Body that was Injured	Text
26.	Body Part - Left	Check Box/Left side of Emp. Body	Yes/No
27.	Body Part - Right	Check Box/Right side of Emp. Body	Yes/No
28.	Injured Previously	CB/Had Emp. Injured Body Part Before	Yes/No
29.	Nature of Injury	Nature of Employees Injury	Text
30.	Cause	Cause of Employees Injury	Text
31.	Condition	Condition that Contributed to Injury	Text
32.	Accident Type	What Type of Accident Caused Injury	Text
33.	Accident Description	Description of the Accident	Memo
34.	Corrective Action Taken	What Corrective Action Taken	Memo
35.	Date Corrective Action Taken	Date the Corrective Action was Taken	Date/Time
36.	Witness	Witness of the Accident	Text
37.	Date Company Knew	Date that Company First Knew of Acc.	Date/Time
38.	Street Address of Accident	Address Where Accident Occurred	Text
39.	Nature of Business	Nature of Business	Text
40.	County of Injury	County where Injury Occurred	Text
41.	Emp Worker Status - Yes	Check Box -	Yes/No
42.	Emp Worker Status - No	Check Box -	Yes/No
43.	Emp Occupation	Occupation of Emplooyee	Text
44.	Length of Employment	Length of Time Emp. Worked for Co.	Date/Time
45.	Injured on Premises - Yes	CB/Was Emp Injured on Premises - Yes	Yes/No
46.	Injured on Premises - No	CB/Was Emp Injured on Premises - No	Yes/No
47.	Fatality	CB/Was Accident a Fatality	Yes/No
48.	Injured on Job - Yes	CB/Did Injury Occur on the Job - Yes	Yes/No
49.	Injured on Job - No	CB/Did Injury Occur on the Job - No	Yes/No
50.	Injured on Job - Unknown	CB/Injury Occur on the Job - Unknown	Yes/No
51.	Other Workers Injured	CB/Were Other Workers Injured	Yes/No
52.	Accident Result of Machine Failure	CB/Acc. a Result of Machine Failure	Yes/No
53.	Accident Caused by Someone Else	CB/Acc. Caused by Someone Else	Yes/No
54.	Company Accident Description	Companys Description of Accident	Memo
55.	801 OSHA To Be Filed?	CB/Is 801 OSHA to be Filed	Yes/No
56.	Previous Injury Description	Description of Previous Injury	Text
57.	Shift Start	Beginning of Employees Shift	Date/Time
58.	Shift End	End of Employees Shift	Date/Time
59.	Date Worker Left	Date Employee Left Work	Date/Time
60.	Time Worker Left	Time Employee Left Work	Date/Time
61.	Date Worker Returned	Date Worker Returned From Disability	Date/Time
62.	Number Hrs Per Shift	Number Hrs Employee Works Per Shift	Number
63.	Days Worked - 3 or less	CB/Emp. Reg. Works less then 3 days	Yes/No
64.	Days Worked - 4	CB/Emp. Reg. Works 4 days	Yes/No
65.	Days Worked - 5	CB/Emp. Reg. Works 5 days	Yes/No
66.	Days Worked - 6	CB/Emp. Reg. Works 6 days	Yes/No
67.	Days Worked - 7	CB/Emp. Reg. Works 7 days	Yes/No
68.	Days Off - Sat	CB/Emp. Reg. Days Off - Sat	Yes/No
69.	Days Off - Sun	CB/Emp. Reg. Days Off - Sun	Yes/No
70.	Days Off - Mon	CB/Emp. Reg. Days Off - Mon	Yes/No
71.	Days Off - Tue	CB/Emp. Reg. Days Off - Tue	Yes/No
72.	Days Off - Wed	CB/Emp. Reg. Days Off - Wed	Yes/No
73.	Days Off - Thurs	CB/Emp. Reg. Days Off - Thurs	Yes/No
74.	Days Off - Fri	CB/Emp. Reg. Days Off - Fri	Yes/No
75.	Wage	Employee's Current Wage	Number
76.	Wage - Hr	CB/Emp. Wage Per Hour	Yes/No
77.	Wage - Wk	CB/Emp. Wage Per Week	Yes/No
78.	Wage - Day	CB/Emp. Wage Per Day	Yes/No
79.	Wage - Mo	CB/Emp. Wage Per Month	Yes/No
80.	Wage - Yr	CB/Emp. Wage Per Year	Yes/No
81.	DirectMedical	Direct Medical Costs to Company	Currency
82.	EmpCompCosts	Employer Contribution	Currency
83.	EstLongTermCosts	Estimated Long Term Costs to Company	Currency
84.	TotalCompCosts	Total Compensation Costs By Company	Currency
85.	AdminCosts	Administration Costs to Company	Currency
86.	Locale	Co. Plant Location	Text
87.	Company	Company Name	Text
88.	TeamCode	Team Code	Text
89.	TeamName	Team Name	Text

Note:
The file you are importing must include all of the above listed columns in the order and data types. If your file does not originally have all of these fields (which it probably won't), you will need to make a “SPACER” column for each one that is missing and insert them in the correct position.
This “SPACER” function will be much easier if you are importing a spreadsheet file, than if you are importing an ASCII text file. Remember, even if your file is an ASCII text file, you can open that text file in Excel or Lotus and use the “Parse” function to separate the information into organized columns. Then import the completed files.

List of Fields For Import/Export Purposes-SOS Form Data

#	Field Name	Description	Data Type

1.	ReportID	Report ID	Text
2.	IncidentID	Incident ID (Auto Counter)	Counter
3.	Last	Last Name	Text
4.	First	First Name	Text
5.	AffectedPerson	Affected Person	Text
6.	WeyerEmp	Is this an Employee?	Yes/No
7.	NonEmp	Is this a Non-Employee	Yes/No
8.	Company	Company Name	Text
9.	Locale	Plant/Location #	Text
10.	Department	Employee Department Code	Text
11.	Dept Name	Employee Department Name	Text
12.	MailStop	Employee Mail Stop	Text
13.	ReportType	Report Type	Text
14.	DOB	Date of Birth	Text
15.	Sex Male	Is the employee Male?	Yes/No
16.	Sex Female	Is the employee Female?	Yes/No
17.	SSN	Social Security Number	Text
18.	Address	Date Employee Hired	Text
19.	City	Check Box/Was Employee Hospitalized	Text
20.	State	Name of Hospital Emp. was taken to	Text
21.	Zip	Date Injury Occurred	Text
22.	LOE	Time Injury Occurred	Number
23.	Hired	Time Employee's been in Dept	Text
24.	DateOfIncident	Emp. Treating Physician	Date/Time
25.	Time of Incident	Part of Employee Body that was Injured	Date/Time
26.	Time in Dept	Check Box/Left side of Emp. Body	Date/Time
27.	Location	Check Box/Right side of Emp. Body	Text
28.	Nature of Injury	CB/Had Emp. Injured Body Part Before	Text
29.	IncidentType	Nature of Employee's Injury	Text
30.	IncidentCode	Cause of Employee's Injury	Text
31.	InjuryCode	Condition that Contributed to Injury	Text
32.	Cause	What Type of Accident Caused Injury	Text
33.	Condition	Description of the Accident	Text
34.	ConditionCode	What Corrective Action Taken	Text
35	Accident Type	Date the Corrective Action was Taken	Text
36.	Accident Description	Witness of the Accident	Text
37.	CorrectiveActionTaken	Date that Company First Knew of Acc.	Memo
38.	Corrective ActionDescription	Address Where Accident Occurred	Yes/No
39.	DateCorrectiveActionTaken	Nature of Business	Memo
40.	Witness	County where Injury Occurred	Date/Time
41.	DateReceived	Check Box -	Date/Time
42.	DateReplied	Check Box -	Date/Time
43.	ProjectedCompleteDate	Occupation of Emplooyee	Date/Time
44.	DateCompleted	Length of Time Emp. Worked for Co.	Text
45.	AcknowledgedBy	CB/Was Emp Injured on Premises - Yes	Memo
46.	AcknowledgeNotes	CB/Was Emp Injured on Premises - No	Yes/No
47.	Response-Yes/Completed	CB/Was Accident a Fatality	Yes/No
48.	Response-Yes/TBI	CB/Did Injury Occur on the Job - Yes	Yes/No
49.	Response-Pending	CB/Did Injury Occur on the Job - No	Yes/No
50.	Response-No	CB/Injury Occur on the Job - Unknown	Yes/No
51.	Response-Other	CB/Were Other Workers Injured	Yes/No
52.	SupervisorInvolved	CB/Acc. a Result of Machine Failure	Text
53.	SupervisorName	CB/Acc. Caused by Someone Else	Yes/No
54.	FurtherActionNeeded	Company's Description of Accident	Memo
55.	FurtherActionSugg	CB/Is 801 OSHA to be Filed	Text
56.	InvestigationAssignedTo	Description of Previous Injury	Text
57.	IncidentLocation	Beginning of Employee's Shift	Text
58.	PreventativeAction	End of Employee's Shift	Text
59.	RecommendedActionDate	Date Employee Left Work	Date/Time
60.	ActualActionApproved	Time Employee Left Work	Memo
61.	CorrectiveActionAssigned	Date Worker Returned From Disability	Text
62.	WorkOrderNo	Number Hrs Employee Works Per Shift	Number

It will be appreciated that the physical data structure in storage device 14 or RAM 16 may take any suitable form, such as inline or multidimensional arrays, indexed arrays, or indexed tables.
To better explain the system and methods of the present invention, the operating instructions of a preferred embodiment of the invention are incorporated below:

SAFESTAR

Versions 3.0-3.NET and 4.0

Operating Instructions

Chapter 1
Program Overview:
Developed by STAR SOLUTIONS™ (SSCS), SAFESTAR™ is a Windows™-based software program that allows you to:

- Track corporate safety performances
- Create State & Federally required OSHA forms in 1/30th to 1/60th the time traditionally required (both manually and electronically via Electronic Data Interchange)
- Help meet Federal OSHA time requirements for reporting fatalities or catastrophic injuries.(Avoid expensive fines & violations).
- Administer effective safety awareness incentive programs
- Track and administer training programs
- Track attendance performances
- Support internal safety reporting requirements (including graphs, issuance of safety communication pieces, and multi-type detailed analysis).
- Import and export data from/to other data sources and types.
  System Requirements:

In order for SAFESTAR™ to run optimally, it will require a minimum operating system of at least the following specifications:

- 486DX
- 33 megahertz cpu
- Minimum RAM—
- Using Windows 3.11-4 meg RAM (recommend at least 8)
- Using Windows for Workgroups or Windows NT—8 meg min. RAM
- Local Bus Recommended
- 1 meg VRAM (recommend at 2 for optimum performance)
- Novell LAN Network or Equivalent
  Using This Manual:

To help you make the best use of this manual, we have included the symbols below to set off special information or warnings to which you should pay extra attention. Although relatively easy to understand, you may still want to familiarize yourself with their meanings:
System-Related Issue
Shortcut or Tip
PREPARING YOUR COMPUTER FOR SAFESTAR™
The following items are recommended in order to make absolutely sure your system is “fine-tuned” and ready for SAFESTAR™!
VIDEO RESOLUTION: VGA vs. SVGA SAFESTAR™ has been designed to fit completely
in the VGA mode. If you have Windows 3.1 or higher and a SVGA monitor, you can select the Super VGA video driver from the Options menu in the Windows Setup file. It is important to remember that using the SVGA mode is overkill, as it will result in more blank space for most forms. The primary benefit would be found when displaying state and federal forms on-screen.
For optimum viewing and graphic resolution, we recommend that you operate in the VGA mode when using SAFESTAR™.
MEMMAKER:
If you have only 4 megs of RAM and also have DOS 6.0 or higher, you will want to run “MEMMAKER” before installing SAFESTAR™. To do this, exit Windows to the DOS prompt and make the following entries:

- cd\DOS [Enter]
- MEMMAKER [Enter]

It's that simple. Just answer the questions on the screen and DOS will do the rest. MEMMAKER is a DOS function that will optimize your memory management and make the maximum memory available for use when running Windows applications.
UTILITIES:
Although not exclusively required for SAFESTAR™, we recommend that prior to installing any Windows program, you run a disk utility program (e.g. Norton, PC Tools, Defrag in DOS, etc.) to defragment your system and correct any file allocation errors that may be present on your hard disk drive.
NEVER DO's:
Never turn off your computer without first closing SAFESTAR™ and exiting Windows. Failure to do so can result in file corruption and memory allocation errors. Although these errors can usually be corrected without any problems, there is a chance that data can be permanently lost.
Installation: (Stand-Alone)
The SAFESTAR™ software consists of four,
1.4 m floppy disks (for version 3.1) and six,
1.4 m floppy disks (for version 4.0). Before beginning the installation process you must first close all open applications. Once that is accomplished, complete the following steps:
Insert the disk labeled #1 into the floppy drive
Open the File Manager application (found in the Main Menu of the Windows Program Manager).
Open the File menu and click on Run
At the prompt, type: B:\SETUP.EXE (Note: or type the appropriate drive letter where the disk is located). Or —In File Manager, you can opt to Double-Click on the SETUP.EXE file located on disk # 1.
The Install Program will prompt you to insert the next disks until complete.
Once installed, you will find the SAFESTAR™ program group in the Program Manager. To start the program use the “switch to function” or double click on the program group.
Once the program group is opened, you will have a choice of two icons: SAFESTAR∩ & Repair/Compact.
To start the program, Double-Click on the SAFESTAR™ icon (*See the Utilities section for more information on the Repair/Compact Function)
Verify Table Attachments—Attachment Manager
The data files in SAFESTAR® are located in tables that are connected by way of a special “attachment manager”. This component helps ensure that every time you open the program, all required tables are connected properly. This feature is especially helpful when SAFESTAR™ is being used in a network environment, and the network goes down. By going into the re-attachment section, the user can follow the directions below and re-direct the program to look at a local C (or whatever drive is available) and still be able to use the program even though the main data files are located on the network server that is down. The default setting for these pre-attached tables is C:\SAFESTAR. If at the time of installation, you have installed SAFESTAR™ into any other directory than the one listed above, you will need to open the “VERIFY ATTACHMENTS” section at the MAIN SWITCHBOARD and change the path commands. To do this you need to:

- 1. Go into the “VERIFY ATTACHMENTS” section (from the Main Switchboard)
- 2. Change the “Global Path” by clicking on the appropriate icon.
- 3. Once the “Global Path” dialog box has been displayed, select the “Browse” button.
- 4. Use the mouse to go to the directory that SAFESTAR™ has been installed in. You should be able to see at least three files displayed: SAFESTAR.MDB, BASICTBL.MDB, & SAFEDATA.MDB.
- 5. Double-Click on the file named SAFEDATA.MDB.
- 6. After you have returned to the “Global Path” change dialog box, select “OK”, then “OK” once more.
- 7. At this point, you will be exited out of the attachment manager and an ATTACHMENT MANAGER dialog box will appear on-screen. This box will ask you if you want to rebuild all attachments and has two options, YES or NO. Select YES.
- 8. After SAFESTAR™ has checked all tables, it will return a message that there is an ATTACHMENT ERROR. Choose “OK” to modify the file manually.
- 9. If the ATTACHMENT MANAGER does not immediately re-appear, re-select it from the Utilities section of the MAIN SWITCHBOARD.
- 10. Repeat steps 1-4 and when you come to step 5, choose BASICTBL.MDB instead.

Continue with remaining steps.
Setting up SAFESTAR™
This manual is designed to follow along with the natural format of the SAFESTAR™ software. This will hopefully make it easier for you to understand the program and find assistance when needed. There are a few tips to help you get started:

1. Enter you company information and complete all set-up forms before attempting to begin entering accident/attendance/training/workers compensation data.
2. Decide whether or not you will be importing your company's employee files into SAFESTAR™. If so, in what format, or will you manually enter the data? Should you decide not import your employee files, you will be limited from producing any one of the reports that is based on/and includes team/department data (e.g. Accident Report by Period, Employee Master Lists by Team/Department). Also, it will take longer to complete many of the forms that already include quick-entry employee/participant lookup fields.
Sample Files:

SAFESTAR™ comes with sample files to allow you to see what the entries, final reports and graphs should look like. After you have familiarized yourself with SAFESTAR's operation, you should select the “DELETE SAMPLE INFORMATION” from the MAIN SWITCHBOARD. You are now ready to use SAFESTAR™ in a “real-world” environment. Note: Once this function has been performed, do not push the DELETE SAMPLE INFORMATION button again.
New Addotions in This Edition:
If you are an existing user of SAFESTAR™ and this is an upgrade, you will find a number of new additions and enhancements. These include:

- Enhanced Accident Report Capabilities
- Advanced Accident Investigation
- SHA 200-S Year Questionnaire Report
- Safety Observations Category
- Incentive Administration Report Category
- Expanded Accident-Related Graphs (including multiple-year comparisons and design modification capabilities. Over 240 different combinations)
- Multi-Site, Network-Capabilities (Optional)
- Sign-On Security and Password Protection
- Enhanced Screen Design, utilizing “Smart Icons”

We trust that you will enjoy using this program as much as we enjoyed creating it.
Chapter 2
Navigating Around SAFESTAR™ (Overview):
Remember, to navigate your way around SAFESTAR™ you only need to push the on-screen “button”, using your mouse A. Upon opening the program you will find yourself at the Main switchboard.
Within the program there are three primary “Switchboards” that you will encounter: “Main”, “Main Forms” and “Main Reports”. *See the flow-chart below for a complete path breakdown.

See FIG. 12

On-Line Help—
An On-Line help system has been provided to assist you in working with SAFESTAR™. To open the Help system, simply press the F1 key. Once opened, you can search for a selected subject by typing the first few letters of the topic. Once a topic is selected, you may view the available options or associated sub-topics. Any help item selected may be copied and/or printed.
Navigation/Control Buttons in SAFESTAR™
Once a form has been selected and opened, you will encounter a row of buttons that assist you in locating and changing file information.

See FIG. 13

LOOKUP—The first of these buttons is a “Lookup” window that shows the reference for the current selected data (e.g. employee name, file reference, etc.). By clicking on the small “arrow-down” button on the right side of this box, all available/pertinent records will be displayed. To go to a specific record, type in the first few characters. SAFESTAR™ will highlight the first complete match it finds (at least 3 characters/letters are required). Once a selection is made, the form will go directly to that record.
First/Last/Next/Previous—Immediately to the right of the “Lookup” box are the record navigation buttons. From Left to Right, their functions are as follows:
- Button #1=Go to the first record in the table
- Button #2=Go to the previous record in the table
- Button #3=Go to the next record in the table
- Button #4=Go to the last record in the table
Edit—This button will unlock the current record and allow changes/modifications to be made.
Delete—This button will delete the current single/or multiply selected records. You will be prompted to confirm your deletions at all levels.
Add/New—This button will allow you to add a new record to the table. Once depressed, a blank screen will appear as well as two new buttons at the top of the screen “SAVE” and “RETURN”. After you have completed the new record, select SAVE prior to depressing the “RETURN” button. Should you select the “RETURN” button without first pressing “SAVE”, the data you have just entered will be lost.
Close—This button will close the current form and return to the appropriate switchboard.
Override: This button is designed to be used in the event that the user accidentally opens a form that requires specific data, and will be prevented from exiting the form until the information is completed.
Exiting Reports and Graphs—In order to exit reports and graphs, you will need to do one of the following:

If a menu is displayed at the top of the screen (e.g. File, Edit, View, Window), then select the “FILE” category and choose the “CLOSE” option.
If no menu is displayed, you may also close by “double-clicking” on the square white box in the upper left hand corner.
Very Important, when exiting a report or graph, NEVER select the “EXIT” option. If you do, you will be exited entirely out of the system and be required to restart the program.
Main Switchboard:

See FIG. 14

This is the central nervous system of the SAFESTAR™ program. Here you will be presented with several choices:

- GO TO THE MAIN FORMS SWITCHBOARD
- GO TO THE MAIN REPORTS SWITCHBOARD

OR

Perform Any One of Several Utility Functions (ranging Importing/Exporting, Check Table Attachments, Add/Modify Permissions, Delete Sample information, etc.)
In addition, this screen contains an overview of the program (current time/date, # Accidents Entered To-Date, # of Employees enrolled in the program and Est. $'s saved by using SAFESTAR™).
Opening SAFESTAR™—Each time the MAIN SWITCHBOARD is opened in SAFESTAR™, the program will first run a check of all accident case files and determine whether or not there have been any new reports created within the last 24 hours. If there have been no accidents in this time period, SAFESTAR™ will return the following message:

“There are no new accidents to report. Have a Safe Day!”

If, however, an accident(s) have occurred within the last 24 hours, an ACCIDENT NOTICE box will be displayed at the opening screen. The box lists the number and description of any qualifying accidents and offers the administrator the opportunity to go directly into any one of the new reports, bypassing the switchboard process.

See FIG. 16

SECURITY: Passwords and Permissions
Signing-On: Before being allowed entry into SAFESTAR, each user will be prompted to enter a valid SIGN-ON CODE and PASSWORD. After installing SAFESTAR, your SSCS account executive will provide you with a valid sign-on code and password. After the sign-on code and password are validated, the software will determine which files the user is authorized to have access to. To modify the password or assign new users, select the Add/Modify Permissions button at the MAIN SWITCHBOARD.

See FIG. 16

Add/Modify Permissions:
Password Protection—
Upon pushing this button, the user will be prompted to enter a valid MASTER PASSWORD before being allowed entry into the permissions group. All incorrect attempts will result in the user being exited from the program. Your SAFESTAR account executive will provide you with the valid password, which you may change after entering the permissions form. IMPORTANT NOTE: When changing your password and pressing enter, you will be prompted to reconfirm your change. You must re-enter the password exactly as it appears above in order to have the change take effect. Once you have changed your password, you will need to re-enter it each time in order to regain access to this section. It is very important that you write down the password and store it in a secure place. Should you lose or forget the new password after it is changed, the only alternative is to contact SSCS for a re-install disk.

See FIG. 17

Security/Permissions (Cont.)
Add/Modify New Users: This section allows the program administrator to create/delete authorized users. Pay special attention to the role that the “Asterisk * “plays in this process.
Instructions—Adding/Modifying:

See FIG. 18

Step # 1. Sign-On ID=Any letter/number combination that identifies the user. (required)
Step # 2. Password=Any letter/number combination (no spaces) that acts as a secondary security level (e.g. dept name, file name, etc.)
Step # 3. Company=Select a specific company name from the list, or leave the “*” if unlimited access is desired, (note: the “*” is the default value, if you want to restrict the records for this user to a specific company you will need to replace the “*” with a company name).
Step # 4. Level=Within a given company, select a specific plant/location # from the list, or leave the “*” if unlimited access is desired. (*Same note applies as for the company—see Step #3).
Instructions—Deleting:

Position the curser on the left side of the screen and click on the row which contains the user you wish to delete. You should see the data in that row become dark (highlighted). Press the delete key and select YES when prompted to confirm your changes.
Sign-On Error Log: The system administrator can view/print a sign-on error log which contains all failed attempts to gain entry into SAFESTAR. This section is particularly helpful when contacted by an authorized user who entered and incorrect sign-on. The administrator can review the entries and determined where the error occurred.
Main Forms Switchboard:

See FIG. 19

This is the platform from which you will open any of the category switchboards that contain entry/input forms. It is divided by these categories:

- Program/Employee Related
- Setup Forms
- Accident Related
- Attendance Tracking
- Training Tracking
- Workers Compensation
- Safety Observations & Suggestions

To go to a desired category, simply press the corresponding button on the screen. You will be directed to another switchboard for that subject. In this screen, you need only select any one of the form buttons on the left, verify its description and push the “OPEN” button to go to that form.

See FIG. 20

Main Reports Switchboard:

See FIG. 21

Just as the “Master Forms Switchboard” is where you will select forms for entering data, this is where you will select the direction for viewing appropriate reports and graphs. Divided by the same categories as in the forms switchboard, the types of reports include:

- Program/Employee Related
- Setup Forms
- Accident Related
- Attendance Tracking
- Training Tracking
- Attendance Information
- Workers Compensation
- Safety Observations & Suggestions

To go to a desired category, simply press the corresponding button on the screen. You will be directed to another switchboard for that subject. In this screen, you need only select any one of the report buttons on the left, verify its description and push the “PREVIEW” or “PRINT” buttons in order to view or print that report.

See FIG. 22

Chapter 3

Forms

Quick Overview

Group:	Form Name	Description

Accident	Accident Report	Entry form for recording accident
Related	Form	details
	Advanced	Advanced Accident Investigation
	Accident	entry forms (incl. all pertinent accident
	Investigation	details as well as training & accident
		history records, preventative action,
		and investigative notes)
	Corrective -	Quick-Entry Screen for recorded
	Actions Quick-	accidents. Allows the user to enter
	Entry	corrective actions taken and dates
		implemented.
	DMV Report	Department of Motor Vehicles - Traffic
	Form	Accident and Insurance Report Entry
		area, where accident information can
		be entered in new or existing reports.
	Modify OSHA	Entry form for all OSHA recordable
	200 Log	accidents. Allows the user to input
	Information	information relative to the OSHA 200
		Log (e.g. Injury/Illness Types, Days
		Lost, Fatality, etc.)
Program/	Company	Enter official Company Holiday Dates
Employee	Holidays	(for use in calculating Days Lost)
Related	Company Setup	Contains all needed corporate
	Form	information. * Company Name/
		Address/Fed. ID/Plant Location
		* Workers Comp. Insurance Carrier
		Information * State Workers Comp.
		Department & Address
	Department	Quick-entry change form for
	Quick-Entry	modifying employee department
		information.
	Monthly Hours	Enter total staff hours worked on a
	Worked	monthly basis. Allows specification
		by year and plant location #.
	Team Quick-	Quick-entry change form for
	Entry	modifying employee team
		participation information. (For use in
		conjunction with a safety awareness
		incentive program)
Attendance	Absence Codes	Setup form for coding reasons for
Related		absences
	Attendance	Entry form for recording absenteeism
	Report Form	instances. (Includes absence type
		and corrective actions taken)
Setup Forms	Accident Cause	Setup form for Accident Cause
	Codes	descriptions. *Note: This will
		information will be later used for
		assistance in internal accident
		analysis.
	Accident	Setup form for Accident Area
	Conditions	Conditions descriptions. *Note: This
		will information will be later used for
		assistance in internal accident
		analysis.
	Body Part Codes	Setup form for Affected Body Parts.
		(e.g. eye, finger, foot, torso, etc.)
	Department	Setup form for department codes and
	Codes	descriptions.
	Employee	Comprehensive enrollment form for
	Enrollment Form	participants (Note: this data can be
		imported via the Import Utility in the
		Main Switchboard)
	Incident Type	Setup form for incident types and
	Codes	corresponding codes
	Nature of Injury	Setup form for Nature of Injury.(e.g.
	Codes	slips & falls, struck by, etc.)
	Occupation	Setup form for employee Occupation
	Codes	descriptions.
	Safety Reminder	Entry form for Accident Type &
	Codes/	corresponding Safety Reminders.
	Descriptions	The data in this form is used in the
		accident report by period - Accident
		Notice section. Provides a general
		reminder for each accident type
		listed.
	Team Codes	Setup form for team codes and
		descriptions.
Safety	S.O.S.	S.O.S. Investigation form (To be
Observations	Investigation	accessed by authorized management
	Form	personnel only). Allows review and
		response to submitted S.O.S. report
		forms.
	S.O.S. Report	Safety Observation & Suggestion
	Form	form for use in reporting non-accident
		related safety issues (unsafe
		conditions, behaviors or safety
		suggestions). To report an actual
		injury or work related illness use the
		accident form.
Training	Post-Test	Scoring entry form for class
Related	Scoring Form	participants. Allows the administrator
		to input the participants' answers to
		specific test questions. The computer
		will then evaluate the answer and
		return a valid score.
	Post-Training	Entry form for writing post-training
	Test Creation	class test masters (either 3-option
		multiple choice or true/false). No
		limit to the number of questions.
	Re-Training	Enroll persons scheduled for re-
	Enrollment Form	training in a specific class & date.
		Note: Classes may not be added at
		this level. This entry form is strictly for
		re-enrollment of a mandatory class.
		Only eligible participant names will be
		displayed.
	Test Question	Provides a visual test question &
	Summary	correct answer summary for any
		selected test.
	Training Class	Entry form for setup up training class
	Enrollment	information (code, type, description,
		dates, etc.) and enrolling participants.
		*Note: The enrollment section utilizes
		a quick-entry format.
Workers	Accident Cost	Entry Form for recording accident
ompensation	Entry	related costs: (incl. Direct Medical,
		Compensation, Administration, and
		Estimated Reserves)
	Primary Product	Entry form for defining a primary
	Definition	product/service. (incl.: est. MSRP,
		Avg. Profit Per Unit, Estimated Days
		to Build/Produce each Unit)
User	Add/Modify	Entry form for adding/modifying or
Permissions:	Permissions:	deleting authorized users in the
		SAFESTAR. Includes password
		protection and security levels for use
		in a network/multi-site environment.

The previous overview has been provided to outline/describe the available forms in SAFESTAR™. The following section covers how to access and utilize specific forms or categories of forms.
Company Setup Form
Description: One of the Primary SAFESTAR setup forms, the COMPANY SETUP FORM contains all of the corporate data required to produce complete State & Federal report forms. Additionally, the form is where key data on multiple locations is stored.
Components:

- Section #1—Company Information
- Section #2—Insurance Provider Information
- Section #3 State Worker's Compensation Division Address

See FIG. 23

How To Use: In order to complete this form you will need several pieces of information:

- Company Name & Address
- Plant/Location ID. (required)
- Federal ID#
- Industry/SIC Code Information
- Worker's Compensation Insurance Carrier (and affiliated divisions)
- Address of the State Government—Workers Compensation Division
  Set-Up Forms—
  General Overview

Without exception, those forms included in the “SETUP FORMS” category or within a specific switchboard that are labeled “SETUP” are completed in the same manner. Upon opening each of these forms, you need only to complete the listed fields (e.g. category and/or corresponding code. The majority of the setup forms come to you already pre-loaded with information. You may customize, add or delete fields from these forms (utilizing the command buttons at the top of each form). We recommend that you take time to review these pre-loaded forms and verify that they contain the information you want.

See FIG. 24

Employee Enrollment Form
Description: This form is the location for the employee/participant database for all of your participants.
Components: Included in these files are all of the vital information required for the State & Federal OSHA forms (e.g. Name, Soc. Sec. #, Length of Employment, etc.). This form, greater that all of the others, once completed will be the most valuable resource tool in SAFESTAR™.

See FIG. 26

How to Use: You have four options available to you for enrolling the participants:

- IMPORT THE INFORMATION FROM ANOTHER FILE (either ASCII or Windows-Compatible environment e.g. Excel, Word, etc.)
- ENTERING THE INFORMATION MANUALLY
- CONTRACTING SSCS to enter the data for you on a per-name transaction basis
- ELECT NOT TO PRE-ENROLL the Participants and Simply fill out the information on the Accident Form Manually
  Importing Data:

To import data, go to the Main Switchboard and select the “IMPORT DATA” button. Before beginning the import process, you are provided the opportunity to print any of the available table import templates. These templates provide important information on the name, position, size and data types of each of the table fields/categories *See example below. Although it is the easiest and most time efficient way to complete your employee files, this function can potentially provide some of the greatest errors to be encountered in the program. It is very important that the data that is being “imported” into the program be found in the exact column format as the “form” is designed in SAFESTAR™.

See FIG. 26

Failure to do so will result in merge errors that cannot be reversed. Instructions are also included on each printed template.
Once into the main IMPORT section, you will be prompted to select the data-type of your file( 25 e.g. ASCII, EXCEL, LOTUS), the location of the information to imported and the destination table in SAFESTAR™.
Importing into Table Name: MASTER NAMES

See FIG. 27

Special Note: One of the “Fringe” benefits of this particular form is that the information can be 30 exported and used for other functions outside of the SAFESTAR™ program.

See FIG. 28

Exporting Data
To export data, go to the Main Switchboard and select the “EXPORT DATA” button. Within this dialog box you will be prompted for three (3) things: one, Verify that you really do mean to 35 export a specific file (click on the button in the top right of the box); two, Specify the destination file name (full path, e.g. C:\INFO\TEST.TXT) for the exported data (any 8-digit character string, followed by “.TXT*”; three, select the table that you will be exporting (from the pull-down menu).

See FIG. 29

*EXPORT DATA TYPE NOTE: Unlike the import process where you can import any one of three different types of data files (ASCII, EXCEL, LOTUS), the export process will output the data in an ASCII “comma-delimited”, flat file. That is the reason for the .TXT file extension that you will give to the exported file name.
When the process has been completed, the dialog box will close and you will be returned to the MAIN SWITCHBOARD.
TIP: As the exact exported file size will be unknown, we recommend that you create a temporary directory on your hard drive prior to copying it to a floppy disk. Should the file be 10 larger in size the 1.44 meg, you will have the opportunity to “zip” or compress the file without receiving any errors and having to start over.
Accident Report
Description: This form is the cornerstone for the SAFESTAR™ program. It is the source for all accident related reports and graphs. The more information you include, the more complete your reports will be.
Components: There are three primary and 2 secondary sections in the ACCIDENT REPORT FORM:

- SECTION # 1—Vital Statistics
- SECTION # 2—Basic Accident Details
- SECTION # 3—State First Report of Injury and OSHA 200 Log Report Information
- SECTION # 4—Secondary Causes/Conditions/Witnesses
- SECTION # 6—State Exceptions

Special Note: There are two components to this report that are ABSOLUTELY required: Last Name, and Date of Injury. Although important, the remaining fields may be completed at a 25 later time. Upon closing the form, the program will check to determine whether data is contained in the Last Name field and the Date of Injury. If these fields are not complete, you must finish them prior to being allowed to exit the program.
How To Use: The Basic Procedure covers the following areas—
SECTION # 1—Vital Statistics

See FIG. 30

- 1. Select the Accident Report Form from the Accident Related Switchboard
- 2. Tab once, or Click on, the Social Security # box (Highlighted in Yellow) or (if you don't know the participant's Soc. Sec. #T) tab once more to go to the Name Lookup Box.
- 3. Push the button with the arrow on the right side of the box. You will see the entire list of saved social security numbers, employee ID's or names & Soc. Sec. #'s.
- 4. Enter the first 2 -or- 3 digits or letters of the last name. This will bring up the Soc. Sec. # or name that most closely matches the first three numbers you entered.
- 5. If the number or name you are looking for appears, double click on it in this field.

The program will search the employee/participant database and return answers to most of the vital information fields. Once the vital information section has been completed, select Page Down to go to the Report Specifics section.
Note: At least the last name and locale (plant / or location) are required on this first screen.
SECTION #2—Basic Accident Details
How To Use: Complete the requested information, using the “Pull-Up” boxes for any of the listed categories. Note: It is important to note if you intend to produce the Accident Report By Period report, you will need to select/include an item from the Accident Reminder category. In addition to the fields in this section, the following boxes have special significance:

See FIG. 31

Is an Investigation Required?: If the accident meets your company's requirements for an accident investigation, click on this box (an “X” will appear).

See FIG. 32

Is a First Report of Injury Required?: One of the last questions you will encounter in the Report Specifics section, answering “Yes” will make visible the FROI/OSHA control button on the screen. If the accident is recordable, continue to the next section:

See FIG. 33

Sub-Section # 1—Secondary Causes/Conditions/Witnesses
In addition to the primary causes/conditions and witnesses entered into this portion of the reporting process, the user also has the ability to add secondary causes/conditions and witnesses in a separate form. To access this screen, simply press the button located beneath the CAUSE entry box. Once in this screen,you may select as many additional items from the pull down menus. The next time you open this section, your previously selected choices will be displayed in the summary boxes below.

See FIG. 34

SECTION # 3—State First Report of Injury and OSHA 200 Log Report Information
TIP—EMPLOYEE DESCRIPTION: If there is little or no variation between the COMPANY ACCIDENT DESCRIPTION and this field, you can simplify the process by copying and pasting the company accident description from the previous section (select copy from the Edit menu on the toolbar).

See FIG. 36

Sub-Section # 2: State Exceptions—
If the state to which the employee is registered (via Plant/Location #) requires additional information above thst which has already been entered, an exceptions form will open and the user will be prompted to complete the appropriate fields.

See FIG. 36

OSHA 200 Log Information: Once this button is selected, you will be prompted to acknowledge whether or not this accident meets the criteria required for inclusion on the Federal OSHA 200 Log. If you select yes, the OSHA 200 Log section will be displayed.

See FIG. 37

The first section of the OSHA 200 Log includes a synopsis of the accident as an Accident Recap in easy to read WHAT, WHEN, HOW BAD, & HOW LONG. This is provided to assist you in entering the one-line accident description for the OSHA200 form. Remember, you have very little room in which to enter a description.

See FIG. 38

This section also contains a field for entering a unique case number as well as navigation buttons that will take you to appropriate next category (depending if this is an Injury or Illness).
Injury Section—If you have completed the DATE WORKER LEFT and DATE WORKER RETURNED as well as the SCHEDULED DAYS OFF fields in the OSHA Accident Section in the ACCIDENT FORM, SAFESTAR will calculate and complete the # of days lost categories in the injury section. The only manually entered fields in this section are the date of fatality and # of Restricted Work Days.

See FIG. 39

Illness Section—All of the required components for this section have been included in easy to enter on-screen fields. To complete, simply check the appropriate boxes / fields.

See FIG. 40

Advanced Accident Investigation
Description: Accident cases are added to this section if the “INVESTIGATION REQUIRED?“box in the ACCIDENT SPECIFICS section of the Accident Form has been selected. Designed for the accident investigator who has limited knowledge of a specific accident report, this form provides a comprehensive analysis of all components (incl. status reports, accident specifics, training and previous accident history, and corporate performance analysis).

See FIG. 41

Components: Within the Advanced Accident Investigation form there are three sections:

- Vital Information
- Accident Details
- Training/Special Information

How to Use: Upon opening the form, the investigator will see the vital information of the person having the accident as well as a visual, colored “Status” bar indicating at what stage various components of the accident are in.
The next section details the accident specifics (what, where, when, how long, how bad, etc.). It also contains a PROBABLE ROOT CAUSE field in which the investigator can add/modify the probable root cause of the accident. Additionally, the investigator will see how many other accidents in SAFESTAR match each of the criteria (eg. nature/body part/condition, etc.)

See FIG. 42

Within the Training/Special Information Section, the investigator is provided with four (4) primary components:

- A complete training history of the employee (inc. Dates of classes and scheduled re-training)
- A complete accident history (inc. All other accidents/dates/etc.).
- Investigator Notes Section
- An Accident Performance Analysis. This section calculates the avg. number of accidents per employee, the number of accidents that this employee has had and finally what “Percentage” of performance (e.g. 50% or 300% of the company average).

TIP: Upon opening the Training/Special Information section, the investigator may close the “Investigator Note” box by “double-clicking” on the white box in the upper left-hand corner. To re-open this note box, it will be necessary to go back to the Accident Specifics section and then re-open the Training/Special Information section.

See FIG. 43

Corrective Actions (Quick Entry)
Description: This form can be used a quick-reference for the program administrator to be able to review those accidents for which no corrective actions have been taken to date. It also serves as a “Quick Entry” screen for entering subsequent corrective actions once they have been completed. cl SEE FIG. 44
How to Use—records can be accessed either via use of the lookup box or by simply scrolling down the list via use of the vertical scroll bar on the right side of the screen.
TIP: *Also See Corrective Actions Not Taken Report in the Reports Section.
DMV Report Form
Description: This Department of Motor Vehicles (DMV) form allows for the reporting of vehicular accidents and all related components. Very comprehensive, the DMV form includes a majority requested accident items (incl. driver, passengers, all vehicles, accident descriptions, weather conditions, insurance information, hospitalization data, etc.)

See FIG. 46

How To Use: Upon opening the form, select the involved employee from the pull-down box on the left side of the screen. Once selected, all pertinent employee data will be downloaded into the “DRIVER 1” section. You may navigate easily between the screens by depressing the appropriate buttons.
TIP: For ease in form completion, you need only open/complete those sections that are pertinent.
Department/Team Quick Entry Forms
Description: Much like the CORRECTIVE ACTIONS QUICK ENTRY form, these two forms allow the user to quickly modify the department or team information for all enrolled employees/participants.

See FIG. 46

How To Use: If a “blanket” change is being made to an entire department number/code, select the find & replace feature under the EDIT menu at the top of the screen. Enter the number to find and then the number that will be the replacement and select REPLACE ALL in the options section. SAFESTAR™ will search and replace all department numbers and their subsequent department names simultaneously.

See FIG. 47

TIP: Prior to changing all affected records, you will be prompted to verify changes. Once changes have been made, they cannot be undone, but the process can be repeated to replace the previous number/code that was changed.
Monthly Hours Worked
Description: Found in the Company/Employee Related section, the MONTHLY HOURS WORKED entry form plays an important role in producing a dynamic “Master Accident Performance” report in the reports section. This report will calculate the incident/frequency/severity rates for a specified company or division.

See FIG. 48

Components/How to Use: Categorized first by year, then by locale, the MONTHLY HOURS WORKED form is divided into company/locale information and then the months are categorized into quarters. Each quarter may be accessed by selecting the appropriate buttons at the bottom of the screen.

See FIG. 49

TIP: In order to produce a “Master Accident Performance” report that will calculate a “best-case” analysis through the end of the year, all months must be completed (even though the exact information may not be available). Providing estimates based on past year/month performance is a good way to project these performance numbers.
Safety Observations—Report Form
Description: The SAFETY OBSERVATIONS report form is designed for reporting non-recordable accidents (e.g. unsafe acts, near misses), unsafe conditions and safety suggestions.

See FIG. 60

Components: An abbreviated and modified version of the ACCIDENT REPORT FORM, there are only two primary components:

- Vital Information
- Report Specifics

See FIG. 61

How To Use: Much like the ACCIDENT REPORT FORM, at the opening screen, the user selects an employee name from the list (or may enter a non-employee in the appropriate boxes) and completes all relevant data. In the Report Specifics section, all basic information is entered and once completed, the form is closed.
Safety Observations—Investigation Form
Description: The second phase of the SAFETY OBSERVATIONS section, the Investigation Form picks up where the initial report left off.

See FIG. 62

Components/How To Use: In this form, the investigator will first be presented with a vital statistics overview and component status review. In the subsequent screens, the incident details and opportunity to determine a probable cause are provided. The last section involves reporting of all actions taken and acknowledgments/work orders issued (where applicable).
TIP: *Also See: Safety Observations Report & Investigative Report in the reports section.
Training Class Enrollment Form
Within the TRAINING CLASS ENROLLMENT FORM, there are three sections:

- Class Code/Description (incl. re-training interval)
- Date of Class (inc. Date/Time, Instructor, Test Code, Location, & Date Navigation Buttons)
- Training Class Participants (inc. Quick Lookup)

See FIG. 63

How to Use:

New Classes—Open the form and select NEW to go to a new class creation screen. Fill in all pertinent boxes and tab to the Date of Class Section.
Existing Class—Select an existing class code from the lookup box at the top of the form. Once you have been moved to the selected record, modify the data as needed (e.g. add new dates, enroll new students
Enrolling Attendees—Select an employee name from the NAME LOOKUP box in the CLASS PARTICIPANTS section. Once selected, SAFESTAR will lookup the employee's vital information and automatically complete the remaining fields.

TIP: In order to navigate between class dates, select the Next Date or Previous Date buttons to move back and forth in the class dates section. Select CREATE NEW DATE to add a new class date.
Re-Training Class Enrollment Form
Description: Once an employee/participant has been enrolled in a class for which a RE-TRAINING interval has been listed, their name will appear on the re-training list, for the correct class/time period allotted in the future. Although RE-TRAINING CLASS ENROLLMENT FORM appears very similar to the TRAINING CLASS ENROLLMENT FORM, the difference can be found when the NAME LOOKUP box is selected for a particular class, on a particular date. If there are any persons who are scheduled for retraining on/before the date of the class, their names only will appear in the lookup box when it is opened. If this box is blank when opened, the indication is that no one is scheduled for training on/before this class' date.

See FIG. 64

Post-Training Test Creation Form
Description: The POST-TRAINING TEST CREATION FORM allows the user to create a customized post-training test within SAFESTAR.
Components: The components of this form include:

- Test Name
- Description
- Question
- Possible Answers (inc. Multiple-choice or true/false)
- Correct Answer Identification

See FIG. 56

How To: In order to successfully create a post-training test, the user may open this form and select “NEW” or work on an existing test. After the test question has been created and possible answers entered, the user need only to click on the button immediately to the left of the possible answers, where the answer is correct. You may have only one correct answer per question. For True/False, leave the third box blank and enter TRUE as the first answer and FALSE as the second answer.
Post-Training Test Scoring Form
Description/How To: Once an employee or participant has completed and submitted their individual test for scoring, this form allows the program administrator to input the tested person's answers in the “ANSWER” box. Based on the inputted answers, the form will automatically evaluate the performance and return a score at the bottom of the screen. This form may be referenced at any time in order to review an employee/participant's performance.

See FIG. 66

Test Question Summary
Description: More of a report that a form, this section will provide a summary of all created test questions for a given test. It is an excellent place to review the work to-date on a particular test in a summary view.

See FIG. 67

Accident Cost Entry Form
Description: A manual entry screen that allows the user to input costs associated with each applicable accident. This information is used in producing a MASTER COST ANALYSIS management report that calculates the amount of product/service that will be required in order to pay for the accident (inc. Short- & long-term costs).

See FIG. 68

How To Use: Within this form, you will input the identified cost items (direct medical, employee compensation, administration costs and estimated reserves). The initial costs sub-total will be calculated automatically. Because this is an automated function, it requires that all preceding boxes be completed. Even if a category's value is $0.00, please enter a $0.00 amount in that box. These figures may be updated or modified at the user's discretion.
TIP: This is a pre-requisite form for the Master Cost Analysis report.
Primary Product Definition
Description: This form is basically used as a “SETUP” form in which you enter your primary product/or service and input the indicated financial categories.

See FIG. 69

TIP: It is a pre-requisite form for the Master Cost Analysis report.
ATTENDANCE FORM
Description: Completed in much the same way as the ACCIDENT REPORT form, this one screen ATTENDANCE FORM is used to track instances of absenteeism, tardiness, medical or family emergencies.
How To Use: After opening the form, simply select the correct Soc. Sec. # or name and fill in the appropriate boxes. Push Close when through.

See FIG. 60

OSHA200 Log Entry Form
Description: This form is used for adding/modifying/deleting those accidents that were indicated in the ACCIDENT REPORT FORM as being OSHA 200 recordable.
How To Use:
Entering/Modifying Information—Section # 1:
Upon opening, the program will display the OSHA200 Information form. The only required box for you to complete in this first section is the unique “CASE NUMBER” field. The other participant vital information will have already been automatically entered from the Accident Report Form.

See FIG. 61

Accident Recap—
When selected, a synopsis of the accident will appear in the Accident Recap screen in easy to read WHAT, WHEN, HOW BAD, & HOW LONG, in order to assist you in entering the one-line accident description for the OSHA200 form.

See FIG. 62

Accident Statistics Injury/Illness—Section #2:
The section you will complete is dependent on whether the accident involved an Injury or and Illness. Select the correct category from the main OSHA 200 information screen. As with all of the forms, check the correct boxes until all necessary portions are complete. When you are through, you may close the form.

See FIG. 63

Chapter 4

Reports

Overview

Group	Report Name	Description

Accident Related	Accident - Supervisors	Produce an internal \Supervisor's
	Report	Report of Occupational Injuries and
		Illnesses\. Can also be used as an
		internal accident report.
	Accident Analysis Defined	Accident analysis based on user-
		defined parameters (e.g. dates/types/
		causes, etc.).
	Accident Report -	List of all accidents for which
	Corrective Actions Not	corrective actions have not been
	Taken	implemented.
	Accident Report By Period	Detailed listing of all reported
		accidents that occur between two
		user-specified dates. (Incl. Accident
		synopsis, persons in department,
		accident notices)
	Accident Synopsis by	Provides a synopsis of all accidents
	Period	that occur between two user-specified
		dates.
	DMV Report	Department of Motor Vehicles - Traffic
		Accident and Insurance Report. This
		report gives accident details, vehicle,
		passenger, and insurance information.
	Master Accident	Comprehensive performance report
	Performance	including: Mo Hrs Worked, Incidents,
		Frequency & Severity Rates.
	Master Accident Report	Listing of all recorded accidents
		(Chronologically by Month &
		Alphabetical Participant Listing).
	OSHA - Yr. End	Produce the OSHA Year-End
	Questionnaire	Questionnaire section entitled \Cases
		with Days Away from Work\ for each
		applicable accident. User Parameter
		Defined
	OSHA 200 Log	Annual OSHA	200 Accident Log. (Can
		be parameter defined by Company/
		Locale/Department)
	State First Report of Injury	Comprehensive, individual First Report
		of Injury (By State). User-Defined.
Accident Related	Accidents - Avg. Costs	Calculates the AVERAGE COSTS by
Graphs		Injury. (BAR GRAPH)
	Accidents - By Body Part	Overview of all accidents, sorted by
		BODY PART involved(BAR GRAPH)
	Accidents - By Day of the	Presents an accident analysis by \Day
	Week	of the Week\. (Pie-Chart)
	Accidents - By Department	This graph shows the accident totals
		by DEPARTMENT. (BAR GRAPH)
	Accidents - By Department	Calculates the percentage of
	(Percentage)	accidents incurred by department.
		(PIE CHART)
	Accidents - By Length of	Accident breakdown by Length of
	Employment	Employment. (PIE-CHART)
	Accidents - By Nature of	Breaks down accidents by NATURE of
	Injury	INJURY. (BAR GRAPH)
	Accidents - By Specific	This detailed graph shows accidents
	Safety Reminder Types	by ACCIDENT REMINDER, breaking
		them down into the month in which
		they occurred. (3-D AREA GRAPH)
	Accidents - By Time of	Presents an accident analysis by
	Day	\Time of the Day\. (3D-Column)
	Accidents - Costs - Hi/Lo	Presents all the accident claims (high-
		to-low) whose COSTS were over
		$100. (LINE GRAPH)
	Accidents - Monthly Totals	Breaks down total accident counts by
		MONTH. (LINE GRAPH)
Attendance	Attendance Report By	Detailed listing of all reported
Related	Period	absenteeism instances that occur
		between two user-specified dates,
		(incl. List of all persons in department).
Program/	Basic Employee Report	Alphabetical list of all enrolled
Employee Related		employees. Includes basic
		information: (Name, ID, Hire Date,
		Department, LOE).
	Master Employee List (By	Employee list sorted alphabetically by
	Department)	Department or Shift and last name.
		Includes the same data as the Master
		List.
	Master Employee List - By	Employee list sorted alphabetically by
	Team	Team.
	Master Employee Report	Complete Alphabetical list of
		employees. Includes all personal data
		(address, phone, etc.).
Safety	Safety Observations -	Safety Observations report analysis
Observations	Analysis	based on user-defined parameters
		(e.g. dates/types/causes, etc.).
	Safety Observations -	Details all Safety Observation
	Corrective Not Taken	Incidents for which corrective actions
		have not been taken.
	Safety Observations -	Safety Observation Report -
	Investigation	Investigation Report. (Incl.
		Recommended actions, final
		dispensation, work order no.)
	Safety Observations -	Master SAFETY OBSERVATIONS
	Master Report	Incident Report
	Safety Observations -	Master SAFETY OBSERVATIONS
	Nature of Incident	report by nature of incident (user-
		defined parameters)
	Safety Observations -	Analysis of preventative actions taken
	Preventative Actions	for all SAFETY OBSERVATIONS
		reports.
	Safety Observations -	Safety Observation Report -
	Report	Confirmation/Response form.
	Safety Observations -	Produces a Visual-Status report of all
	Status Report	Safety Observations reports/
		investigations on file. Note: It is an
		excellent report for quick review.
	Safety Observations -	SAFETY OBSERVATIONS report
	Synopsis	synopsis. (Sorted by user-defined
		dates).
Training Related	Master Employee Training	Alphabetical Listing of All Participants
	Report	who have participated in Co.
		sponsored training classes. (Incl.
		Name, Classes Attended, & Class
		Totals).
	Master Safety Reminder	Alphabetical Listing of all injury
	Report	Reminders currently on file.
	Master Training Class	Alphabetical & Chronological listing of
	Report	all Employee Training Classes. (Incl.
		Class Code, Name, Description, &
		Participants).
	Re-Training Master Report	Master Re-Training Report: Shows
		scheduled re-training records for all
		enrolled employees
	Training Class Notices	Provides notices of Scheduled
		Training Classes. Parameter Defined
		by Class Specific.
	Training Class Roster	Creates a Training Class Roster for
		use in tracking actual participants.
		Provides a space for signatures.
	Training Records - By	Training report by employee specific.
	Employee	User Defined.
	Training Test Issuance	Post-Training Class Tests by Class
		(user-defined). Issued a hard-copy
		test for each individual that attended
		the selected class (alphabetical).
Workers Comp.	Master Cost Analysis	Comprehensive cost analysis of each
		accident. Incl. Amt of Product required
		to pay for an accident claim. User- Def
Incentive Program	Length of Service - By	Master Report - Length of Service.
Administration	Year	Lists all persons whose length of
		service falls between the user-defined
		year range.
	Length of Service - By	Length of Service - Anniversary Dates.
	Month	This master report lists all anniversary
		dates categorized by month.
	Accident Free	Master Report of those persons who
	Performance	have performed “accident free” for a
		period of tim greater than indicated by
		the user.
	Birthday Analysis	Birthdate Analysis. This report
		categorizes birthdates by month for all
		employees.

The previous overview has been provided to outline/describe the available reports in SAFESTAR™. With exception of the following reports, each report may be accessed in the Preview or Print mode minimal specification or without any additional entries.
Accident Related:
Accident Report 13 by Period (Report)
Description: A completely User-Defined report, the ACCIDENT REPORT BY PERIOD is very comprehensive. The report will generate a detailed listing of any accidents that have occurred during that period (by department or team) including an

- Accident description
- Accident type
- Corrective action taken.

Immediately following the accident summary, a listing of all persons from that employee's department is provided. The final section produces an accident notice for each person in that respective department. This notice outlines:

- A general description (anonymous),
- An accident type
- Corresponding safety reminder for the specific type of injury.

See FIG. 64

How To Use: When you select this report you will be prompted to enter the Period Start and Period End Dates (Include any mo/day/yr) as well as be able to specify any one of five related categories, and specify by company/locale/department. Based on the information given in these boxes, the program will search the accident files and create a report that lists any accidents (by dept.) and all persons in the department in which the accident occurred.
TIP: In order to produce the ACCIDENT NOTICES, a safety awareness reminder must first be entered in the report specifics section of the ACCIDENT REPORT FORM. This report is also one of the PRIMARY tools for administering a successful and comprehensive SAFETY AWARENESS INCENTIVE Program. *Also See the INCENTIVE RELATED Section on the Reports Switchboard.
Accident Analysis Defined
Description: This is one of the most comprehensive accident analysis reports in the system. Designed to replace most “ad-hoc” report requests, the ACCIDENT ANALYSIS DEFINED report allows the user to define/request an accident analysis report based on one or all (in any combination) from the following criteria:

- Nature of Injury
- Accident Type
- Accident Cause
- Accident Condition
- Company
- Locale
- Department
- Reporting Start & End Dates

See FIG. 65

State First Report of Injury
Description: A complete print-out of the individual state's “FIRST REPORT OF INJURY”. Submitted to the state workers compensation division, this form eliminates the need to manually produce a carbon-form report ever again.
How To Use: You will be prompted to select a case from the pull down menu. Once selected, the name and date for the person you just entered will be displayed in the confirmation boxes. From this point, you may select either the Preview or Print options.

See FIG. 66

Note: This report may contain graphic files that will cause it to take a considerable amount of time to print (2-5 minutes). Where required, an “Employee Receipt” will be automatically be included with the master report.
Depending on your internal policies for # of copies, you will need to make multiple copies of the full State First Report of Injury report and distribute to the appropriate departments.
OSHA 200 Log REPORT:
Description: This report produces the annual OSHA 200 Log (specified by Company/Locale/Department).
How To Use: Enter the year to process at the prompt and

See FIG. 67

VERY IMPORTANT—In order to be able to even view this report, the HPIIP print driver (*See the Configure Printers Section) must be installed. After the printer driver screens have been displayed, you will be prompted to enter the year as well as company/locale/department (where applicable).
Once the printer driver is loaded, the report will be displayed in the landscape view, legal size (8½ in×14 in). Preview the information on-screen. If any changes need to be made, you can make them in the “ENTER OSHA 200” form. REMEMBER to put a legal size piece of paper in the printer prior to printing.
OSHA—Yr End Questionnaire
Description: Also known as the 200-S form, the OSHA—YR END QUESTIONNAIRE report reproduces the federally mandated form for reporting cases that involved days away from work. When researched and completed manually, this function is made doubly hard by the additional fact that the scope of the request varies from year to year and requests information only on accidents that fall within a random month and days of the month period.
How To Use: At the prompt, enter the Year to Process, Starting & Ending Months, and Starting and Ending Days.

See FIG. 68

Accident Related Graphs
Description: The ACCIDENT RELATED GRAPHS report section offers dynamic, graphical views (both by single year and multiple-year) of your company's total accident related performances. With over 240 possible, different combinations, there is little information that is not covered in this section.
How To Use:
Single Year—

- 1. Enter the year to process in the YEAR box at the top of the form
- 2. Select a graph to view/print

Select any one of the three available options: Preview, Print, Design

See FIG. 69

Multiple-Year—

- 1. Depress the MULTIPLE YEAR COMPARISON button at the top of the form.
- 2. Enter the starting year to process in the first YEAR box on the Left
- 3. Enter the ending year to process in the second YEAR box on the Right
- 4. Select a graph to view/print
- 6. Select any one of the three available options: Preview, Print, Design

See FIG. 70

Design Option: In order to successfully modify the appearance of your graph, you need to be familiar with designing graphs found in most Microsoft programs (e.g. Word or Excel). When you select this option, the graph file that is displayed is not visible, but a blue instruction box appears, follow these steps and you will be able to complete the re-design process:

1. “Double-Click” in the main area of the graph (White Screen)
2. Your view will be converted to the graph design screen (Graph is made visible).
3. You can click on any of the menu options (e.g. gallery, chart, or format) and change the appearance, style, text or graphic types.
4. When you are through making any changes, select “EXIT” from the “FILE” menu. (Note: this is the only time you will ever select the exit option from a FILE menu in SAFESTAR. In this instance, it is being used only for exiting from the Microsoft Graph manager.
5. You will be returned to the main area of the graph (White Screen).
6. If you have made any changes, upon closing the graphs, you will be prompted to save those changes. Select Yes and Close the form.
Attendance Related Reports—
Attendance Report Period Analysis—

Detailed listing of all reported absenteeism instances that occur between a user-defined time period. Includes a synopsis of the absenteeism incident and lists all of the persons who work in the department with that individual.
Support Forms Required to Be Completed:

- Attendance Report Form
- Primary Product Defined (Workers Compensation Related)
  Workers Compensation Related Reports:
  Master Cost Analysis

Description: Also parameter defined, (e.g. one or all of the following: Nature of Injury, Cause, Condition, Accident Type, Company, Locale or Department), the user can produce this comprehensive cost analysis of each accident. This is very helpful when evaluating the “bottom-line” impact of any accident and then to translate it into “how much product or service” will we need to manufacture or support in order to pay for not only the short-term “hard-costs”, but also what are the long-term ramifications if We can't return this person to his/her position rght away.

See FIG. 71

Support Forms Required to Be Completed:

- Accident Report Form (Accident Related)
- Primary Product Defined (Workers Compensation Related)
  Chapter 5
  Utilities
  Printer Configuration—

In order to be able to print the OSHA200 Annual Report, you must install, or have loaded the HPIIP laser printer driver. This driver is accessed through the Main group of the Program Manager. In MAIN, you will find the computer icon labeled “CONTROL PANEL”. Double-clicking on this icon will display the CONTROL PANEL options, one of which if the PRINTERS. Double-Click on this icon and select “Add”, following the instructions on the screen. You will need to have disk # 6 of the Windows program disks. All other reports are set to print on your default printer set through windows.
Repair & Compact
Besides running regular disk utilities on the entire system, we recommend that you run the REPAIR/COMPACT utility (found in the SAFESTAR™ Program Group).
Backup
You should back up the information in the SAFESTAR™ directory weekly (daily is preferred). There are several options available. As mentioned earlier in this manual, any of the disk utility programs, the DOS function “BACKUP” or Windows “BACKUP” (from the file manager) can be used successfully.
Troubleshooting
Message: “Not Enough System Resources to Update View”
Solution: Exit SAFESTAR™ and make sure all other Windows programs are closed, then try again. If the problem continues, restart SAFESTAR™ and go directly to the report or form and attempt to reopen.
Cause: This error message will occur most often on systems with only 4 meg of RAM. You may want to consider upgrading the system memory to 6 or 8 meg. Also, if you have had Windows open for an extended period of time and have been running any of the standard memory-intensive programs (Word, Excel, Word Perfect, Access, etc.) you may be encountering a problem with conventional resources. You can check this by exiting to PROGRAM MANAGER and viewing the ABOUT file under the HELP category. This ABOUT screen will indicate the percentage of system resources available. Optimum performance with SAFESTAR™ can be achieved when there is at least 60% available. If there is any less than this amount, exit PROGRAM MANAGER and restart Windows.
Message: “You must first enter a LOCALE # for this employee in the Accident Report form. Please enter the information before attempting to re-open this file”
Cause: This message occurs as a result of a missing locale # in the Accident Report form.
Solution: To correct this error message, re-open the accident form and enter a valid “LOCALE #” in the appropriate box.
Message: “You must have the DEVELOPERS version of Microsoft Graph!”
Cause: This message occurs when the user attempts to modify the design of a graph in the Accident Related Graphs section.
Solution: In order to complete this function, Microsoft Office Professional must be loaded and active on the users system. This design category utilizes the graph engine included with this suite of products. The ability to modify the pre-built graphs is not a requirement. It has been provided as a service to those persons who have the necessary software to accommodate this request.
Given the above description of the present invention, it can be seen that it includes a data flow as shown in FIG. 11. Specifically, a system database creator/modifier 76 operates on system database 52 a to create or modify system database 52 a. Creator/modifier 76 includes an input form selector 78 that accesses database 52 a and, through VDT 20 and keyboard 22/display cursor control system 24, allows the user to select an input form for display on VDT 20. Once such an input form is selected by selector 78, an input form formatter 80, operating in digital processor 12, formats the selected form for display on VDT 20. The selected is then displayed on VDT 20, and a system record editor 82, through keyboard 22 and display cursor control systems 24, allows a user to select specific records for viewing and editing through the selected form, and input new records using the selected form.
An incident database creator/modifier is shown at 84, again operating through digital processor 12. A system record extractor 86 extracts predefined records from system database 52 a, after which a system information extractor 88, operating through VDT 20, keyboard 22 and/or display cursor control system 24, extracts predefined information from the selected records, and allows the user to specify specific information for extraction. An incident record selector 90 operates on incident database 52 b, either before, while or after the system records and information are extracted at 86 and 88, to select a specific incident record for viewing or modification or creation. This viewing, modification or creation is performed by an incident record editor 92, operating through digital processor 12, RAM 16, VDT 20, keyboard 22 and/or display cursor control system 24. Once the selected incident records are edited, the information is rewritten to incident database 52 b.
A report generator is shown at 94, again operating through digital processor 12. Generator 94 includes a report format selector 96 that accesses system database 52 a, and through VDT 20, keyboard 22 and/or display cursor control system 24, allows a user to select a defined report format. Once the report format is selected, a report formatter 98 accesses and extracts information specified in the selected format from database 52, including system database 52 a and incident database 52 b, and manipulates the information to create a completed report. The completed report is then produced through a computer output medium at 100, such as a printer.
From the forgoing identification of the components of the present invention, the following methods and systems are included within the scope of the invention.
A computer-implemented process of reporting safety information stored in computer memory is controlled by one or more user workstations 10. The process includes the step of creating a system database 52 a stored in computer memory 14/16, database 52 a including a plurality of defined lists of entries for selected variables and a plurality of defined formats for selected reports. The defined lists include information such as a defined list of employees and a defined list of types of incidents. The defined formats include reports such as OSHA report 200 and DMV (Department of Motor Vehicles) accident reports.
The process also includes the step of creating an incident database 52 b stored in computer memory 14/16 by selecting an record from one or more of the defined lists in system database 52 a and inserting the selected entry or entries into a data record. This step can include or be concurrent with the steps of accessing previously created incident records, selecting ones of such records to match information inserted into the current incident record, and displaying on the selected form information comparing the current record to the selected ones of the previously created records.
The process further includes the step of creating an incident report by selecting one of the defined formats from system database 52 a, extracting and manipulating information from incident database 52 b as defined in the selected format from system database 52 a, and producing the report on a computer output medium such as VDT 20.
Viewed somewhat differently, the invention includes a computer-assisted process of reporting safety information stored in computer memory. This process includes the step of creating a company database stored in computer memory 14/16. The company database includes a defined list of employees and a defined list of types of incidents. The process also includes the steps of selecting an employee from the company database, selecting a type of incident from the company database, and creating an incident database stored in computer memory by inserting the selected employee and type of incident into a data record. The process next includes the steps of formatting the incident database into a report and producing the report on a computer output medium.
Viewed still differently, the invention includes a computer-aided process of producing incident reports, the process comprising the step of creating a system database 52 a stored in computer memory 14/16. System database 52 a includes a plurality of defined lists of entries for selected variables and a plurality of defined formats for selected incident reports. The process further comprises the step of creating an incident database 52 b stored in computer memory 14/16 by selecting an entry from one or more of the defined lists in system database 52 a, and inserting the selected entry or entries into a data record. The process further comprises the step of creating an incident report, by selecting one of the defined formats from system database 52 a, extracting and manipulating information from incident database 52 b as defined in the selected format, and producing the report on a computer output medium.
Described differently, the invention includes an incident reporting system 10. The reporting system comprises a system database 52 a stored in computer memory 14/16, including a plurality of defined lists of system records of selected variables, and a plurality of defined report formats for producing selected incident reports. A system record selector 86 is provided for selecting one or more of the defined system records, and an information extractor 88 is provided for extracting one or more elements from the selected system record.
The reporting system 10 further comprises an incident database 52 b stored in computer memory 14/16, including one or more defined lists of incident records of data. Each incident record describes one or more aspect of a specific incident, and may contain one or more of the extracted elements from system database 52 a. A report format selector 96 is provided for selecting one or more of the defined report formats, and a report formatter 98 is provided for extracting and manipulating information from incident database 52 b as defined in the selected report format. The reporting system 10 further comprises a computer output medium through which the extracted and manipulated information is produced in the selected report format.
Reporting system 10 further comprises an input form database 52 a 2/52 b 2 including a plurality of defined input forms for prompting a user for input to system/incident database 52. An input form selector 78 is provided for selecting one or more of the defined input forms, and an input form formatter 80 is provided for extracting and manipulating information from system database 52 a as defined in the selected input form. A user interface is provided for displaying the selected input form and allowing a user to input information into one or more records of one or more lists of system database 52 a through the selected input form.

INDUSTRIAL APPLICABILITY

The present invention is particularly applicable to the administration and support of the industry process known as light duty/restricted duty/recurrence of injury recording, analysis and reporting.

Claims

1. A computer-implemented process of reporting safety information workstation, comprising the steps of:

creating a system database stored in computer memory, the system database including a plurality of defined lists of entries for selected variables and a plurality of defined formats for selected incident reports;

creating an incident database stored in computer memory by selecting an entry from one or more of the defined lists in the system database, and inserting the selected entry or entries into a data record; and

creating an incident report by:

selecting one of the defined formats from the system database;

extracting and manipulating information from the incident database as defined in the selected format; and

producing the report on a computer output medium.

2. The computer-implemented process according to claim 1, wherein the defined lists include a defined list of employees.

3. The computer-implemented process according to claim 1, wherein the defined lists include a defined list of types of incidents.

4. The computer-implemented process according to claim 1, wherein the defined formats include an OSHA report 200.

5. The computer-implemented process according to claim 1, wherein the defined formats include a Department of Motor Vehicles accident report.

6. The computer-implemented process according to claim 1, further comprising the steps of:

accessing previously created incident records;

selecting one of the previously created incident records to match information inserted into the incident record being created; and

displaying on the selected format information comparing the current incident record to the selected previously created incident record.

7. A computer-assisted process of reporting safety information stored in computer memory, comprising the steps of:

creating a company database stored in computer memory, the company database including a defined list of employees and a defined list of types of incidents;

selecting an employee from the company database;

selecting a type of incident from the company database;

creating an incident database stored in computer memory by inserting the selected employee and type of incident into a data record;

formatting the incident database into a report; and

producing the report on a computer output medium.

8. An incident reporting system comprising:

a system database stored in a computer memory, the system database including a plurality of defined lists of system records of selected variables and a plurality of defined report formats for producing selected incident reports;

a system record selector for selecting one or more of the defined system records;

an information extractor for extracting one or more of the variables from the selected system record;

an incident database stored in a computer memory, the incident database including one or more defined lists of incident records, wherein each incident record describes one or more aspects of a specific incident;

a report format selector for selecting one or more of the defined report formats;

a report formatter for extracting and manipulating information from the incident database as defined in the selected report format; and

a computer output medium through which the extracted and manipulated information is produced.

9. The incident reporting system according to claim 9, further comprising:

a user interface;

an input form database including a plurality of defined input forms for prompting for input to the system and incident databases through the user interface;

an input form selector for selecting one or more of the defined input forms; and

an input form formatter for extracting and manipulating information from the system database as defined in the selected input form.