Hierarchies

From FMR Knowledge Base
Revision as of 03:41, 22 August 2022 by Vmurrell (talk | contribs) (Step 4 - Levels)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Overview

Hierarchies provides a hierarchical view over one or more ‘standard’ Codelists. A Hierarchy can be thought of in the same way as a database view: it does not define any new codes; it is used to group any number of existing Codes from any number of existing Codelists. See this article for more information on authoring and maintaining structures.

Wizard

From the Items menu, select the Hierarchies Page and use the maintenance button to create a Hierarchal Codelist. Cogs.PNG

Step 1 - High Level Details

The steps in a Hierarchical Codelist Wizard includes step 1 which provides the generic, high level details about the Hierarchal Codelist. See this article for more information on authoring and maintaining structures.

Step 2 - Codelists and Hierarchy

The second step requires information on the Codelists that will be required when building the Hierarchies.

In the first part of the screen, click Add and select the Codelists that you intend to use (Referenced Codelists).


Step 2 - Codelists

Step 3 - Build Hierarchy

Step 3 enables you to add Root Codes (the Parent) and Child Codes for each of the hierarchies created in Step 2.

The Hierarchy selection box will display the IDs entered in Step 2. Select the appropriate Reference Codelist (as added in Step 2) and then the individual code.

The example below shown that a root code has been added for LEVEL2.


Step 3 - Build Hierarchy

The next step is to add the Child codes.

First, highlight the Root Code and then click Add Child Codes. Next select the Referenced Codelist, and then the individual codes.

Once you have added the codes, you will be returned to Step 3 as shown in the example above.

To change the order of the codes, you can use drag and drop to reposition.

Step 3 - Re-order

Step 4 - Levels

Step 4 of the wizard allows the user to provide a formal definition for each level of the hierarchy as shown in the example below.

Step 4 - Levels