SNOMED Documentation Search
An
Concept | ||
---|---|---|
|
Concept | ||
---|---|---|
|
Concept | ||
---|---|---|
|
Concept | ||
---|---|---|
|
Concept | ||
---|---|---|
|
Each attribute is identified by its concept id, while each domain is identified by the same concept id used in the referencedComponentId of the
Concept | ||
---|---|---|
|
An
Concept | ||
---|---|---|
|
...
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 900000000000443000 |Module (core metadata concept)| within the metadata hierarchy.
...
N
Refset spec table | ||||
---|---|---|---|---|
| ||||
The following metadata hierarchy supports this reference set:
Concept | ||
---|---|---|
|
Concept | ||
---|---|---|
|
Concept | ||
---|---|---|
|
Concept | ||
---|---|---|
|
...
refsetId
...
SCTID
Identifies the reference set to which this reference set member belongs.
...
|
...
Y
...
...
SCTID
Concept |
---|
...
Y
...
domainId
...
SCTID
...
A reference to the SNOMED CT concept that identifies the relevant concept domain.
...
Y
...
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.
...
N
...
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 |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
|
Concept | ||
---|---|---|
|
Concept | ||
---|---|---|
|
Concept | ||
---|---|---|
|
Concept | ||
---|---|---|
|
Concept | ||||
---|---|---|---|---|
|
The following metadata hierarchy supports this reference set:
Footnote Macro | ||||||
---|---|---|---|---|---|---|
Please note that the
|
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 |
---|
|
Concept | ||
---|---|---|
|
Concept | ||
---|---|---|
|
Concept | ||
---|---|---|
|
Concept | ||
---|---|---|
|
Concept | ||
---|---|---|
|
Concept | ||
---|---|---|
|
Concept | ||
---|---|---|
|
Concept | ||
---|---|---|
|
Concept | ||
---|---|---|
|
...
Display Footnotes Macro |
---|
...
Excerpt Include | ||||||
---|---|---|---|---|---|---|
|
The table below shows the reference set descriptor for a reference set that follows the
Concept | ||
---|---|---|
|
Table width manager | ||||
---|---|---|---|---|
| ||||
|
...
|
...
|
...
|
...
|
...
|
...
111115 |Domain constraint|
...
707000009 |SNOMED CT parsable string|
...
2
|
...
900000000000456007 |Reference set descriptor|
...
111115 |MRCM attribute domain reference set|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
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
|
Footnote Macro |
---|
Concepts for which an identifier has not been assigned have been shown with an identifier of '111115' |
...
|
...
domainConstraint
|
...
|
...
|
...
|
...
|
...
|
...
404684003 |Clinical finding (finding)|
...
|
...
|
...
|
...
|
...
|
...
272379006 |Event (event)|
|
|
...
|
...
|
...
|
...
|
...
413350009 |Finding with explicit context (situation)|
...
|
...
|
...
|
...
|
...
|
...
123005000 |Part of|
...
91723000 |Anatomical structure (body structure)|
...
|
...
|
...
|
...
|
...
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.
...