SNOMED Documentation Search
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| , |All 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| .
Data Structure
A |MRCM attribute domain reference set| is structured as shown in the following table.
Field | Datatype | 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 |Module| 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. | Y |
grouped | Boolean | 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. | 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): 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): 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| 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:
Descriptor Template
The table below shows the reference set descriptor for a reference set that follows the |MRCM attribute domain reference set| pattern.
refsetId | referencedComponentId | attributeDescription | attributeType | attributeOrder |
|---|---|---|---|---|
0 | ||||
1 | ||||
2 | ||||
3 | ||||
4 | ||||
5 | ||||
6 |
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| .
refsetId | referencedComponentId | domainId | grouped | attributeCardinality | attributeInGroup | ruleStrengthId | contentTypeId |
|---|---|---|---|---|---|---|---|
1 | 0..* | 0..* | |||||
1 | 0..* | 0..* | |||||
1 | 0..* | 0..1 | |||||
0 | 0..1 | 0..0 |
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.
Ref |
Notes |
|---|---|
| 1 |
Please note that the
<a href="http://snomed.info/id/723574004" title="723574004 | Content type |" class="external-link conf-macro output-inline" rel="nofollow" data-hasbody="true" data-macro-name="scg-expression">
<span style="color: #00ccff;" class="sctpipe">|</span><span style="color: #000000;" class="sctid">Content type</span><span style="color: #00ccff;" class="sctpipe">|</span></a>
hierarchy is designed using 'universal restriction' logic. The hierarchy may therefore appear to be 'upside down'. However, it was designed in this way because if an MRCM rule applies to
<a href="http://snomed.info/id/723596005" title="723596005 | All SNOMED CT content |" class="external-link conf-macro output-inline" rel="nofollow" data-hasbody="true" data-macro-name="scg-expression">
<span style="color: #00ccff;" class="sctpipe">|</span><span style="color: #000000;" class="sctid">All SNOMED CT content</span><span style="color: #00ccff;" class="sctpipe">|</span></a>
then it also applies to the Content Types that are a supertype of this - including
<a href="http://snomed.info/id/723594008" title="723594008 | All precoordinated SNOMED CT content |" class="external-link conf-macro output-inline" rel="nofollow" data-hasbody="true" data-macro-name="scg-expression">
<span style="color: #00ccff;" class="sctpipe">|</span><span style="color: #000000;" class="sctid">All precoordinated SNOMED CT content</span><span style="color: #00ccff;" class="sctpipe">|</span></a>
and
<a href="http://snomed.info/id/723595009" title="723595009 | All postcoordinated SNOMED CT content |" class="external-link conf-macro output-inline" rel="nofollow" data-hasbody="true" data-macro-name="scg-expression">
<span style="color: #00ccff;" class="sctpipe">|</span><span style="color: #000000;" class="sctid">All postcoordinated SNOMED CT content</span><span style="color: #00ccff;" class="sctpipe">|</span></a>
. |
Feedback
Overview
Content Tools
Apps