Purpose
An
scg-expression| ShowParts | term |
|---|
| ShowFormat | inline |
|---|
111115 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.
scg-expression| ShowParts | term |
|---|
| ShowFormat | inline |
|---|
111115 or
scg-expression| ShowParts | term |
|---|
| ShowFormat | inline |
|---|
111115 ) and the content type over which this rule applies (e.g.
scg-expression| ShowParts | term |
|---|
| ShowFormat | inline |
|---|
111115 ,
scg-expression| ShowParts | term |
|---|
| ShowFormat | inline |
|---|
111115 ) 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
scg-expression| ShowParts | term |
|---|
| ShowFormat | inline |
|---|
111115 .
Data Structure
An A
scg-expression| ShowParts | term |
|---|
| ShowFormat | inline |
|---|
111115 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
| Scg expression |
|---|
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
| Scg expression |
|---|
| ShowParts | term |
|---|
| ShowFormat | inline |
|---|
|
111115|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.
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
| Scg expression |
|---|
| ShowParts | term |
|---|
| ShowFormat | inline |
|---|
|
111115|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
| Scg expression |
|---|
| ShowParts | term |
|---|
| ShowFormat | inline |
|---|
|
111115|Content type value| |
, which indicates the type of SNOMED CT content over which this rule applies. In many cases, this will be set to| Scg expression |
|---|
| ShowParts | term |
|---|
| ShowFormat | inline |
|---|
|
111115|All SNOMED CT content| |
....
N
| Refset spec table |
|---|
| Size | fs7 |
|---|
| RefsetType | MRCM Attribute Domain Reference Set |
|---|
|
|
Metadata
The following metadata hierarchy supports this reference set:
| Concept |
|---|
| t | 900000000000454005|Foundation metadata concept| |
|---|
|
| Concept |
|---|
| t | 900000000000455006|Reference set| |
|---|
|
| Concept |
|---|
| t | 723564002|MRCM reference set| |
|---|
|
| Concept |
|---|
| t | 723604009|MRCM attribute domain reference set| |
|---|
|
| Concept |
|---|
| t | 723561005|MRCM attribute domain international reference set| |
|---|
|
| Concept |
|---|
| t | 900000000000457003|Reference set attribute| |
|---|
|
| Concept |
|---|
| t | 723602008|Attribute cardinality| |
|---|
|
| Concept |
|---|
| t | 723603003|Attribute in group cardinality| |
|---|
|
| Concept |
|---|
| t | 723574004|Content type| |
|---|
| ShowFormat | inline |
|---|
|
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
- Grouped
- Cardinality
- Attribute cardinality
- Attribute in group cardinality
- Rule strength
- Mandatory concept model rule
- Optional concept model rule
- Content type Footnote MacroPlease note that the Content type
| Footnote Macro |
|---|
Please note that the | Concept |
|---|
| t | 723574004|Content type| |
|---|
| ShowFormat | inline |
|---|
|
|
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 | Concept |
|---|
| t | 723596005|All SNOMED CT content| |
|---|
|
|
, then it also applies to the Content Types that are a supertype of this - including | Concept |
|---|
| t | 723594008|All precoordinated SNOMED CT content| |
|---|
| ShowFormat | inline |
|---|
|
and | Concept |
|---|
| t | 723595009|All postcoordinated SNOMED CT content| |
|---|
|
.
|
| t | 723593002|All new precoordinated SNOMED CT content| |
|---|
|
| Concept |
|---|
| t | 723594008|All precoordinated SNOMED CT content| |
|---|
|
| Concept |
|---|
| t | 723596005|All SNOMED CT content| |
|---|
|
| Concept |
|---|
| t | 723595009|All postcoordinated SNOMED CT content| |
|---|
|
| Concept |
|---|
| t | 723596005|All SNOMED CT content| |
|---|
|
| Concept |
|---|
| t | 723573005|Concept model rule strength| |
|---|
|
| Concept |
|---|
| t | 723597001|Mandatory concept model rule| |
|---|
|
| Concept |
|---|
| t | 723598006|Optional concept model rule| |
|---|
|
...
...
| Excerpt Include |
|---|
| REUSE:Notes on Reference Set Example Tables |
|---|
| REUSE:Notes on Reference Set Example Tables |
|---|
| nopanel | true |
|---|
|
Descriptor Template
The table below shows the reference set descriptor for a reference set that follows the
scg-expression| ShowParts | term |
|---|
| ShowFormat | inline |
|---|
111115 pattern.
Footnote MacroConcepts for which an identifier has not been assigned have been shown with an identifier of '111115'.| Table width manager |
|---|
|
refsetId | referencedComponentId | attributeDescription | attributeType |
|---|
|
...
attributeOrder
...
| 900000000000456007|Reference |
|---|
|
|
|
...
...
...
...
...
...
...
...
...
...
| t | 900000000000461009|Concept |
|---|
|
|
|
...
...
...
| t | 900000000000456007|Reference |
|---|
|
|
|
...
...
...
...
...
...
...
...
...
...
| Concept |
|---|
| t | 900000000000461009|Concept |
|---|
|
|
|
...
...
...
| t | 900000000000456007|Reference |
|---|
|
|
|
...
...
...
...
...
...
...
...
...
...
| t | 900000000000478000|Unsigned |
|---|
|
|
|
...
...
...
| t | 900000000000456007|Reference |
|---|
|
|
|
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
4
...
| 900000000000456007|Reference |
|---|
|
|
|
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
| t | 900000000000456007|Reference |
|---|
|
|
|
...
...
...
...
...
...
...
...
...
...
| 723573005|Concept model rule Strength| |
|
| |
|
...
| t | 900000000000461009|Concept |
|---|
|
|
|
...
...
...
...
| t | 900000000000456007|Reference |
|---|
|
|
|
...
...
...
...
...
...
...
...
...
...
...
| Concept |
|---|
| t | 900000000000461009|Concept |
|---|
|
|
|
...
...
...
7
| PDF: Landscape |
|---|
Example Data |
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.
...
The table below shows some example rows from a reference set that follows the format of |
...
the ... ... | ShowParts | term |
|---|
| ShowFormat | inline |
|---|
... ... ... ... ... ... Concepts for which an identifier has not been assigned have been shown with an identifier of '111115'
| Table width manager |
|---|
| Col | 1*,1*,1*,80,120,120,1*,1* |
|---|
| Wider | true |
|---|
|
|
... |
refsetId | referencedComponent Id | domainId | grouped |
|---|
|
|
... attribute Cardinality | attribute InGroup
Cardinality | ruleStrengthId | contentTypeId |
|---|
|
|
|
... ... ... ... ... ... ... ... ... ... ... ... | 723597001|Mandatory concept model rule| |
|
| |
|
|
... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... | 723597001|Mandatory concept model rule| |
|
|
|
|
... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... | Concept |
|---|
| t | 723597001|Mandatory concept model rule| |
|---|
|
|
|
|
... ... ... ... ... ... ... ... ... ... | Scg expression |
|---|
123005000|Part of| |
... ... ... ... ... ... | Concept |
|---|
| t | 723597001|Mandatory concept model rule| |
|---|
|
| |
|
|
... ... ... ... ... ... ... 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. ...
{"serverDuration": 1127, "requestCorrelationId": "53c5d8a9c778ba9e"}
|