Work Locations Tab

Work Locations Tab

The Work Locations tab is found in the Control Panel sidemenu tab.

When you click Work Locations from the Control Panel sidemenu tab, the search screen displays. If you click the Search button, all active Work Locations will be displayed. To add a new Work Location, click on the Add New Work Location hyperlink.

An Employer Organization can also be a Work Location. To create a Work Location from an Employer Organization, click on the Employer Organization tab from the Control Panel. Search for the Employer Organization and click on it. Click on the gray bar for the Chart Types section of the Summary tab. Select Work Location from the dropdown of Chart Types and Save. This will create the Work Location.

Locations Hierarchy

The Location Hierarchy is located under the System Editor within the Control Panel. The Locations Hierarchy datavis list displays (by default) active onsite location choices but also includes Checkin Stations (in the list) that are used in the Checkin module. This datavis list is a cross-reference table in the system. Do not alter any known Checkin stations for your system here. You would use the Station Manager instead. Any line item listed here that has Type of 0, indicates it is a Checkin module location, not an injury onsite location for the system. You can also create a perspective to weed out locations with Type 0 in the list. Note: To view inactive locations in the hierarchy screen, choose the perspective available, or clear the datavis filter.

Locations used in this hierarchy give your system superusers the ability to add or update locations that indicate where an injury/incident is reported as having occurred for system wide use and reporting. This onsite location hierarchy is used on OSHA reportable cases & reporting.

Specific work locations are part of an overall Group or Main Work Location. Meaning, specific work locations are part of location groups. Locations are part of location groups (for instance one Hospital ie: Indiana Hospital with 5 separate areas for work/business establishments would be one group with 5 locations).

The Locations Hierarchy provides a way to configure onsite injury locations (used in Injury cases/incidents and reporting) as well as be able to indicate a hierarchy of the onside injury location choices.

Name: This is a required field and would need to be an overall Group Name/Work Location (example: Indiana Hospital) and/or can be a specific location/establishment where employees perform work and/or could be injured at (ex: Emergency Room or Ambulatory Surgery Center). Make sure you enter the name correctly, as you cannot edit this NAME after you save. You would have to delete the entry and rekey in.

Entries into the Locations Hierarchy (name field) depend on how granular the client wants to get for onsite injury reporting. Names (from this location hierarchy) are reflected then in the case/incident onsite location ‘please select location’ auto-complete as choices (and the auto-complete reflects the hierarchy noted in this editor separated by a comma).

Site ID: This is a required field and would need to be a unique Site ID code to give to this Group Name/Work Location and/or specific location/establishment.

Parent ID: This is an optional field. If you indicate a Parent ID here in this field, it will indicate that the specific location/establishment/location group etc is a child (sub)-injury location or child (sub)-site (where an injury could occur) of the Parent site indicated. In order to set a Parent ID to a specific location, the Parent must exist in the Locations Hierarchy list (the Parent is also a site in the list with its own specific Site ID).

If a Parent ID code is set here for a specific group name/work location and/or specific location/establishment, it signifies that the specific listed group/work location and/or specific location/establishment is a sub (child)-location of the parent indicated.

To set a Parent ID code here, the Parent location (group name/work location, etc) itself must exist in this Locations Hierarchy with its own unique Site ID code. The Parent field is an auto-complete field to indicate which other Location (from this editor) is its parent. You would begin typing in the exact location name (not site code abbreviation) and then select its Parent using the auto-complete.

Once a Parent is selected (for the specific location) and the work is saved, the Parent is set and the Site ID code for that parent is what is visible in the datavis list view. The Parent ID (shown on the Location Hierarchy list view of any sub/child locations) is the unique site ID code of the parent this sub-location is tied to.

Using the above example, Indiana Hospital (site code IHL) has 5 sub (child)-locations where injuries (at Indiana Hospital) could occur. The configuration of the Location Hierarchy (with sites & parents) signifies that this system offers 5 sub (child)-location levels as onsite injury locations for OSHA reporting wrapped up to the parent of Indiana Hospital.

Parent/child location hierarchy is reflected then as such in the case/incident onsite location choices (sub (child)-locations followed by , comma and its indicated Parent) as well as in reporting to be able to filter a report based on injury happening at a sub(child)-location and/or its Parent:

Chart ID: This is an optional field. If you indicate an EO (Employer Org) type Chart or a Work Location type Chart here in this Chart ID field, it signifies the EO or Work Location chart that this location (usually a parent location) would have reporting reflected for OSHA. You can also set this for any sub (child)-locations if needed.

The Chart ID is an auto-complete giving you selections of charts (configured in the system) that have a chart type of EO/Employer Organization on them or have a chart type of Work Location on them.

Type: When adding a location to this hierarchy editor, it will automatically assign a Type of 1. This datavis list is a cross-reference table in the system. Any line item listed here that has Type of 0, indicates it is a Checkin module location, not an injury onsite location for the system and you would use the Station Manager editor for those instead. You can also create a perspective to weed out locations with Type 0 in the list.

Active: If the location listed in the hierarchy is active, the Active column will indicate a 1. Inactive locations would be signified with a 0 in this column. When adding or editing locations in the hierarchy, the Active status can be set using the appropriate radio button indications.

Add

To add a new location to the Location Hierarchy editor, simply click the Add Location Hierarchy hyperlink found at the top right corner of the Location Hierarchy editor.

An Add screen will appear as a pop-up, where you key in the required fields and any optional fields as needed. For detailed information on each field, please see above in prior pages of this document that give explanation of each field. Save your entry to the hierarchy editor by clicking the Save button.

Edit

To edit an existing location in the Location Hierarchy editor, simply checkmark which location you need to edit, and then click the Edit button at the bottom of the datavis. Only certain fields can be edited.

Delete

Deleting a location entry from the hierarchy should be done cautiously. If you just entered a new location into the hierarchy and need to delete it (perhaps you spelled it wrong etc), that’s understandable. But if you delete an existing entry that may have already been used as an onsite location for cases/incidents of charts, you should take warning that it will remove that data from any cases/incidents also. If it’s a location (in the hierarchy) that is no longer a location where injuries would occur (but has been in the past with existing cases/incidents on charts), then you would want to instead EDIT it and mark it as inactive, instead of deleting it entirely (historical and future use) from the system.

Will ask you to confirm the deletion through a pop-up. Click Yes if you wish to permanently delete the location entry from the hierarchy.

It will tell you it has successfully processed the deletion. The location is permanently deleted from the locations hierarchy and cannot be brought back.


Enterprise Health Documentation

Last Updated:

Last Build: Thu, 09 Oct 2025 18:13:28 UTC
WikiGDrive Version: 9a3c47814c851f1e3ce25659ea66b7640ddaf209