SNOMED Documentation Search


Versions Compared

Key

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

Purpose

An 

Concept
t723563008|MRCM module scope reference set|
 specifies the set of MRCM reference sets that should be applied to the content in each module. Within a SNOMED CT Edition, the MRCM rules applied to the included modules must be consistent, to ensure data integrity within an edition is maintained.

Data Structure

An 

Concept
t723563008|MRCM module scope reference set|
 is structured as shown in the following table.

...

Field

...

Data type

...

Purpose

...

Immutable

...

id

...

UUID

...

A 128 bit unsigned integer, uniquely identifying this reference set member.
Different versions of a reference set member share the same id but have different effectiveTimes. This allows a reference set member to be modified or made inactive (i.e. removed from the active set) at a specified time.

...

Y

...

effectiveTime

...

Time

...

The inclusive date or time at which this version of the identified reference set member became the current version.
The current version of this reference set member at time T is the version with the most recent effectiveTime prior to or equal to time T.

...

N

...

active

...

Boolean

...

The state of the identified reference set member as at the specified effectiveTime.
If active= 1 (true) the reference set member is part of the current version of the set, if active=0 (false) the reference set member is not part of the current version of the set.

...

N

...

moduleId

...

SCTID

...

Identifies the SNOMED CT module that contains this reference set member as at the specified effectiveTime.
The value must be a subtype of 900000000000443000 |Module (core metadata concept)| within the metadata hierarchy.

...

N

...

refsetId

...

SCTID

...

Identifies the reference set to which this reference set member belongs.
In this case, set to |MRCM module use reference set|

...

Y

...

referencedComponentId

...

SCTID

...

Identifies the SNOMED CT module to which the given concept model refset is applied.
The value must be a subtype of 900000000000443000 |Module (core metadata concept)| within the metadata hierarchy.

...

Y

...

mrcmRuleRefsetId

...

SCTID

...

A subtype of |MRCM reference set| that defines the concept model rules that are applied to content in the module identified by referencedComponentId.

...

Y

Refset spec table
Sizefs7
RefsetTypeMRCM Module Scope Reference Set

Metadata

The following metadata hierarchy supports this reference set:

  • Concept
    t900000000000454005|Foundation metadata concept|

    • Concept
      t900000000000455006|Reference set|
       

      • Concept
        t723564002|MRCM reference set|

        • Concept
          t723563008|MRCM module scope reference set|

    • Concept
      t900000000000457003|Reference set attribute|

      • Concept
        t723577006|MRCM rule reference set|

Excerpt Include
REUSE:Notes on Reference Set Example Tables
REUSE:Notes on Reference Set Example Tables
nopaneltrue

Metadata

The following metadata hierarchy supports this reference set:

...

  • MRCM reference set
    • MRCM module scope reference set

...

Descriptor Template

The table below shows the reference set descriptor for the 

Concept
t723563008|MRCM module scope reference set|
 pattern. Footnote Macro Concepts for which an identifier has not been assigned have been shown with an identifier of '111115'.

Table width manager
Col1*,1*,1*,1*,80


refsetId

referencedComponentId

attributeDescription

attributeType

attributeOrder

Concept
t900000000000456007|Reference set descriptor|

Concept
t

...

723563008|MRCM module scope reference set|

Concept
t449608002|Referenced component|

Concept
t900000000000461009|Concept type component|

0

Concept
t900000000000456007|Reference set descriptor|

Concept
t

...

723563008|MRCM module scope reference set|

...

Concept
t723577006|MRCM rule reference set|

Concept
t900000000000461009|Concept type component|

1

Note: The table above omits the initial four columns of data present in the release file. These follow the standard format for id, effectiveTime, active and moduleId. Additionally, to aid understanding, the table above also shows the term from one of the descriptions associated with each of the identified concepts. The release file only includes the identifier of these concepts.

...


Example Data

The table below shows some example rows from the  | MRCM

Concept
t723563008|MRCM module scope reference set|
Footnote Macro
 Concepts for which an identifier has not been assigned have been shown with an identifier of '111115'
.
.

Table width manager
Col1*,1.2*,1.2*


refsetId

referencedComponentId

mrcmRuleRefsetId

...

Concept
t723563008|MRCM module scope reference set|

...

Concept
t900000000000207008 |SNOMED CT

...

core module (core metadata concept)|

Concept
t723560006

...

|MRCM domain

...

international reference set|

...

Concept
t723563008|MRCM module scope reference set|

Concept
t

...

900000000000207008 |SNOMED CT

...

core module (core metadata concept)|

Concept
t723561005 |MRCM attribute domain

...

international reference set|

Concept
t

...

723563008|MRCM module scope reference set|

...

Concept
t900000000000207008 |SNOMED CT

...

core module (core metadata concept)|

Concept
t723562003 |MRCM attribute range

...

international reference set|

...

Note: The table above omits the initial four columns of data present in the release file. These follow the standard format for id, effectiveTime, active and moduleId. Additionally, to aid understanding, the table above also shows the term from one of the descriptions associated with each of the identified concepts. The release file only includes the identifier of these concepts.  

...