Release File Specification

Search

SNOMED CT Document Library

    Loading...

Versions Compared

Old Version 1

changes.mady.by.user David Markwell

Saved on

compared with

New Version 2

changes.mady.by.user David Markwell

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Each component in RF2 has an associated active fieldEachinhas an associatedfield, which can take values of true ('1') or false ('0'). The meaning of this flag is described by component type bytype in the following table:

Anchor
_2ba901ae-1ad1-4ea5-ac2c-9e5d5f67a50f__a
_2ba901ae-1ad1-4ea5-ac2c-9e5d5f67a50f__a
Table 3. Behavior of Active and Inactive Components

 

 

Component

 Type

active

 value

Description

 of behavior when most recent row representing a

component

has the specified

active

value

Concept

True

  • The Concept is intended for active use.
    • All active Descriptions for

    • Theis intended foruse.

    • Allfor which the conceptId refers to

    this Concept are

    • thisare valid. Visibility of

    these active Descriptions depends

    • thesedepends on information contained in applicable RefsetMembers (for example, whether

    the Description is in a language dialect reference set that

    • theis in athat is currently enabled in the vendor's system).

    All active Relationships of
    Concept

    False

    The Concept is

    • Theis not intended

    for active use

    • foruse. However, it remains a

    valid concept for

    • validfor historical purposes as part of

    the SNOMED CT commitment

    • thecommitment to the principle of '

    concept

    • permanence'.

    Valid Descriptions of the Concept remain active allowing

    • Validof theremainallowing it to be appropriately viewed in human-readable form.

    An inactive Concept cannot
    active Relationship

    • .

    Description

    True

    The Description contains a Term
    valid description of the Concept referred

    • validof thereferred to by the conceptId.

    An active Description may

    • Anmay refer to an

    inactive Concept

    • , in which case the

    Term
    valid description of

    • validof that

    inactive Concept

    • . Text based searches should (by default) include

    only active Descriptions that

    • onlythat refer to

    active Concepts

    • .

    Description

    False

    The Description is

    • Theis not a valid and the associated

    Term

    • term (field) should no longer be regarded as being associated with

    the Concept referred

    • thereferred to by conceptId.

    Relationship

    True

    The Relationship represents

    • Therepresents a valid association of the type specified by the typeId (field), between

    two Concepts referred
    An inactive Concept cannot
    active Relationship

    • .

    Relationship

    False

    The Relationship is

    • Theis not valid.

    An inactive Relationship should

    • Anshould be ignored as it does not apply.

    • This does not necessarily mean that the association indicated by

    the Relationship does

    • thedoes not apply.

    The Relationship may be inactive because

    • Themay bebecause it is redundant and inferable based on other

    active Relationships

    • .

    An inactive Relationship may

    • Anmay refer to

    either active or inactive components

    • eitheror.

    RefsetMember

    True

    • The RefsetMember contains valid information applicable to

    the component referred
    The component referred
    may be active or inactive. An active RefsetMember cannot make an inactive component active but

    • (field) may beor. AnRefsetMember cannot make anbut may provide related information that continues to be relevant (e.g. the reason for inactivation).

    RefsetMember

    False

    • The RefsetMember is not valid.

    An inactive RefsetMember

    • AnRefsetMember should be ignored. The information it contains is not applicable to

    the component referred