SNOMED Documentation Search


Versions Compared

Key

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

...

Concept
t723604009|MRCM attribute domain reference set|
 is structured as shown in the following table.

FieldDatatype

Data type

Purpose

Mutable

Part of Primary Key

id

Specref
RefType(data type)
tUUID

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.

NO

YES (Full/Snapshot) 

effectiveTime

Specref
RefType(data type)
tTime

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.

YES

YES (Full)

Optional (Snapshot) 

active

Specref
RefType(data type)
tBoolean

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.

YES

NO

moduleId

Specref
RefType(data type)
tSCTID

Identifies the SNOMED CT module that contains this reference set member as at the specified effectiveTime.

The value must be a subtype of

Concept
t900000000000443000|Module|
ShowFormatinline
within the metadata hierarchy.

YES

NO

refsetId

Specref
RefType(data type)
tSCTID

Identifies the reference set to which this reference set member belongs.

In this case, set to a subtype of

Concept
t723604009|MRCM attribute domain reference set|

NO

NO

referenced ComponentId

Specref
RefType(data type)
tSCTID

A reference to the SNOMED CT attribute concept to which the attribute-domain rule defined by this member applies.

NO

NO

domainId

Specref
RefType(data type)
tSCTID

A reference to the SNOMED CT concept that identifies the relevant concept domain.

NO

NO

grouped

Specref
RefType(data type)
tBoolean

Whether or not the given attribute (identified by referencedComponentId) is treated by a Description Logic reasoner as belonging to a relationship group, when applied to a concept in the given domain.

If grouped = 1 (true) then the given attribute (identified by referencedComponentId) is treated by a Description Logic reasoner as belonging to a relationship group.

If grouped = 0 (false) then the given attribute (identified by referencedComponentId) is treated by a Description Logic reasoner as not belonging to a relationship group.

YES

NO

attributeCardinalityString

Specref
RefTypedata type
tstring

The number of times the given attribute can be assigned a distinct (non-redundant) value within the definition of each concept or expression.

This string can be parsed using the following ABNF rule (together with the subrules defined in the Expression Constraint Language):

attributeCardinality = minimum to maximum

YES

NO

attributeInGroup CardinalityString

Specref
RefTypedata type
tstring

The number of times the given attribute can be assigned a distinct (non-redundant) value within a single relationship group as part of the definition of a concept or expression.

This string can be parsed using the following ABNF rule (together with the subrules defined in the Expression Constraint Language):

attributeCardinality = minimum to maximum

YES

NO

ruleStrengthId

Specref
RefType(data type)
tSCTID

A subtype of

Concept
t723573005|Concept model rule strength|
ShowFormatinline
which specifies whether the given rule is mandatory (resulting in an error) or optional (resulting in a warning).

YES

NO

contentTypeId

Specref
RefType(data type)
tSCTID

A subtype of

Concept
t723574004|Content type|
ShowFormatinline
which indicates the type of SNOMED CT content over which this rule applies. In many cases, this will be set to
Concept
t723596005|All SNOMED CT content|
.

YES

NO

...