This site provides a visual tree representation of each of the OIICS hierarchical
coding subcomponents (Nature;
Part of Body Affected;
Source and Secondary Source;
and
Event or Exposure
) with code descriptions and a search function. To move between
the trees, click on the tabs in the upper right or use the right-hand menu links.
To expand or collapse the code trees, click the + or – symbols, respectively. If
you switch to a different subsection, previously expanded sections will automatically
collapse when the new section is expanded.
Each classification is assigned a 1, 2, 3, or 4-digit code number depending upon
the coding structure level (i.e., how far the tree is expanded). An asterisk following
the code number on the tree (e.g., 0*) indicates a division, major group, or minor
group title (these group titles are not assignable to an individual injury case).
To view descriptive information for specific code items, click on the information
symbol (
). Clicking on the
information symbol toggles the descriptions on and off.
To view the definition and selection rules for a structure, click on the information symbol
(
SELECTION RULES) next to the
structure title at the top of the tree.
To search for specific codes or descriptive terms within a code tree, enter text
(a partial word, whole word, phrase, or code number; do not exceed 99 characters)
into the Search Tree window.
Then click Find. Do not use quotes or wildcard characters. This function searches
the OIICS manual alphabetic indices, the descriptive information, and the code titles
for exact “numeric” or “text string” matches. Matches, if any are found, will appear
in a list below the search window. Click on an item in the search result list to
expand the code tree and to display the corresponding match in red.
Example 1: Search for Event code descriptions or words
cross-referenced in the index containing the text “slip.”
In the search results list, clicking on “0232 – Struck by
slipping handheld object” expands the Event code division
“Contact with objects or equipment” and displays the
selected item in red.

Example 2: Search for Source codes related to “cots.”
The search for “cots” will return “231-Beds, bedding, mattresses”
because “cots” are cross-referenced to this item in the OIICS
Manual Source code index.

Example 3: Search for Source codes related to “cot.”
The search for “cot” will return “231-Beds, bedding, mattresses”
as in example 2 because “cots” contains the three letters (cot)
and is cross-referenced to this code item in the OIICS Manual
Source code index. Additionally, it returns two other code items
which have the words “cotton” and “Nicotine” cross-referenced
in the index.

Example 4: Search for Source codes related to “coffee.”
The search for “coffee” will return “1 CONTAINERS” because the descriptive information for the
containers groups states that it excludes “coffee makers (3321)”. The search returned “236 – Tables,
worktables” because descriptive information lists “coffee tables” as included in this group.
Lastly, the search returned “3321 – Beverage heating and percolating equipment and appliances”
because the descriptive information included “coffee makers”. Coffee tables and coffee makers
were also included in the Source Code Index. The search does not return a source code related
to the spilling of “hot coffee” in one’s lap because of the somewhat limited vocabulary included
in the manual.

If one can not find an appropriate code, one should use a search strategy with
related terms that are more broadly encompassing (e.g., “drinks” or “beverages”). Searching for
“drinks” returns no codes, but searching for “drink” returns a number of options. However, none
of the drink options are related to “hot coffee”.


Searching for “Beverage” returns a long list
of possible items, including “522 – Beverages, n.e.c.” Even broader search terms such as “Food”
would eventually lead one to the correct code. When the search function returns no likely code
options, one must simply search the structure manually, reviewing the descriptive information,
and eventually selecting the best fitting code.
