Create an inherited codelist

From Fusion Registry Wiki
Revision as of 07:13, 15 March 2021 by Vmurrell (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Overview

This time-saving feature allows you to inherit codes from another Codelist rather than having to recreate codes that are already in the Registry.

To do this:

Step 1 - Select an existing Codelist

You can do this from either a new or an existing Codelist. In step 1 of the wizard on the right-hand side of the page, you will see the Inheritance buttons.

IH0.PNG

If the Add button is clicked, a list of Codelists will be displayed and you can select one or more to be used.

IH3.PNG

Having selected a Codelist, you will see the selection reflected in Step 1 of the Wizard.

IH1.PNG

Step 2 - Adding new codes

This can be done in the usual way either via Step 2 of the Wizard (CSV import) or via Step 3 (Manual Editing). It is important to note that in the Codelist which is inheriting codes from another Codelist, only codes added will be displayed in the Wizard as shown in the example below (Step 4 of the Wizard).

Note: If you add a code which has the name ID as one in the Inherited Codelist, the one that you add manually will be used when this codelist is referenced by a Concept Scheme or a Data Structure.

IH4.PNG

Viewing the whole codelist

From the Codelist page, if you select View you will be able to see all codes, both inherited and manually added.

IH5.PNG

Other Features

Remove Inheritance

From Step 1 of the Codelist, select the one to be removed and click Remove.

Change order of Precedence

Use the Move up and Down buttons if you have more than 1 inherited codelist and a code appears on both to set the order of precedence

Annotations

The Inheritance is recorded as an Annotation and, as such would be treated as an Internal Setting when a structure is downloaded as detailed in the Export Structures article.

The annotation type is EXTENDS as shown below.

IH6.PNG

Deleting Codelists

If the Codelist with Inheritances applied is deleted there are no other implications.

If the Codelist which has been used in an Inheritance is deleted, the codes that were in that Codelist will be copied to the Codelist which used them in an Inheritance.

Content Security

If you are using Content Security to restrict access to a Codelist and you decide to use that Codelist in a structure rule (for example to restrict access to one of more codes to specific organisations), please be aware that the restriction is not applied to any new Codelists that use the restricted Codelist using this Inherited feature. As a result you may need to add the new Codelist (or elements thereof) to the structure rule in order to achieve your desired level of Content Security.