Machine Readable Concept Model

SNOMED Documentation Search

SNOMED CT Document Library

    Loading...

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Purpose

An |MRCM attribute domain reference set| allows attributes to be associated with the domains in which they may be applied. It also allows grouping and cardinality constraints to be specified for each attribute and domain combination. For each attribute-domain rule, the strength of the rule (e.g. |Mandatory concept model rule| or |Optional concept model rule|) and the content type over which this rule applies (e.g. |All SNOMED CT content|, |Precoordinated SNOMED CT content|) is also specified.
Each attribute is identified by its concept id, while each domain is identified by the same concept id used in the referencedComponentId of the |MRCM domain reference set|. To assist implementation, the domain constraint for each domain is repeated in the |MRCM attribute domain reference set|. However, as this repetition is redundant, it is recommended that the domain constraint is always edited in the |MRCM domain reference set|, and then automatically updated where it reappears in this reference set.

Data Structure

An |MRCM attribute domain 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 a subtype of |MRCM attribute domain reference set|

Y

referenced ComponentId

SCTID

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

Y

domainId

SCTID

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

 

domainConstraint

String

An expression constraint, which defines the set of concepts to which the given attribute (identified by referencedComponentId) may be applied.
The domainConstraint must be the same as the one defined for this domainId in the |MRCM domain reference set|.
This string can be parsed using the ABNF syntax defined for the Expression Constraint Language [4].

N

grouped

Boolean

Whether or not the given attribute (identified by referencedComponentId) may be used in a relationship group.
If groupable = 1 (true) then the given attribute (identified by referencedComponentId) may be grouped in a relationship group. If groupable = 0 (false) then the given attribute (identified by referencedComponentId) may not be grouped in a relationship group.

N

attributeCardinality

String

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 specification [4]):
attributeCardinality = minimum to maximum

N

attributeInGroup Cardinality

String

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 specification [4]):
attributeCardinality = minimum to maximum

N

ruleStrengthId

SCTID

A subtype of |Concept model rule strength|, which specifies whether the given rule is mandatory (resulting in an error) or optional (resulting in a warning).

N

contentTypeId

SCTID

A subtype of |Content type value|, which indicates the type of SNOMED CT content over which this rule applies. In many cases, this will be set to |All SNOMED CT content|.

N

Metadata

The following metadata hierarchy supports this reference set:

  • Foundation metadata concept
    • Reference set
      • MRCM reference set
        • MRCM attribute domain reference set
          • MRCM attribute domain (INT) reference set
    • Reference set attribute
      • Domain
      • Domain constraint
      • Grouped
      • Cardinality
        • Attribute cardinality
        • Attribute in group cardinality
      • Rule strength
        • Mandatory concept model rule
        • Optional concept model rule
      • Content type
        • New precoordinated SNOMED CT content only
          • All precoordinated SNOMED CT content
            • All SNOMED CT content
        • All postcoordinated SNOMED CT content
          • All SNOMED CT content

Descriptor Template

The table below shows the reference set descriptor for a reference set that follows the |MRCM attribute domain reference set| pattern.

* Due to space limitations the full domain templates have not been included in this table.

* Due to space limitations the full domain templates have not been included in this table.1 .

refsetId

referenced ComponentId

attribute Description

attributeType

attribute Order

900000000000456007 |Reference set descriptor|

111115 |MRCM attribute domain reference set|

449608002 |Referenced component|

900000000000461009|Concept type component|

0

900000000000456007 |Reference set descriptor|

111115 |MRCM attribute domain reference set|

111115 |Domain|

900000000000461009|Concept type component|

1

900000000000456007 |Reference set descriptor|

111115 |MRCM attribute domain reference set|

111115 |Domain constraint|

707000009 |SNOMED CT parsable string|

2

900000000000456007 |Reference set descriptor|

111115 |MRCM attribute domain reference set|

111115 |Grouped|

900000000000478000 |Unsigned integer|

3

900000000000456007 |Reference set descriptor|

111115 |MRCM attribute domain reference set|

111115 |Attribute Cardinality|

707000009 |SNOMED CT parsable string|

4

900000000000456007 |Reference set descriptor|

111115 |MRCM attribute domain reference set|

111115 |Attribute In Group Cardinality|

707000009 |SNOMED CT parsable string|

5

900000000000456007 |Reference set descriptor|

111115 |MRCM attribute domain reference set|

111115 |Rule Strength|

900000000000461009|Concept type component|

6

900000000000456007 |Reference set descriptor|

111115 |MRCM attribute domain reference set|

111115 |Content type|

900000000000461009|Concept type component|

7

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

 The table below shows some example rows from a reference set that follows the format of the |MRCM attribute domain reference set{*}|1 .

refsetId

referenced Component Id

domainId

domain
Constraint

grouped

attribute Cardinality

attribute
InGroup
Cardinality

rule Strength

contentType

111115 |MRCM attribute domain (INT) reference set|

255234002 |After|

404684003 |Clinical finding (finding)|

<< 404684003 |Clinical finding (finding)|

1

0..*

0..*

111115 |Mandatory|

130xxxxxxxxx |All SNOMED CT content|

111115 |MRCM attribute domain (INT) reference set|

255234002 |After|

272379006 |Event (event)|

<< 272379006 |Event (event)|

1

0..*

0..*

111115 |Mandatory|

130xxxxxxxxx |All SNOMED CT content|

111115 |MRCM attribute domain (INT) reference set|

408729009 |Finding context|

413350009 |Finding with explicit context (situation)|

<< 413350009 |Finding with explicit context (situation)|

1

0..*

0..1

111115 |Mandatory|

130xxxxxxxxx |All SNOMED CT content|

111115 |MRCM attribute domain (INT) reference set|

123005000 |Part of|

91723000 |Anatomical structure (body structure)|

<< 91723000 |Anatomical structure (body structure)|

0

0..*

0..0

111115 |Mandatory|

129xxxxxxxxx |Precoordinated SNOMED CT content|


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.

Footnotes
Ref
Notes
1 Concepts for which an identifier has not been assigned have been shown with an identifier of '111115' [ a b ]

Feedback