The purpose of the |
descriptor| is to describe the format of all other basic that may be included in a release. A Descriptor held within the | Descriptor| describes the referencedComponentIdfield and the additional fields for the it describes. Each field is described using a in the metadata. The type of each field is also described in the same way. Patterns allow a number of different types of
to be defined, each of which will conform to the specified pattern, having the same format. The file format of each pattern is described by a Descriptor Template. This Descriptor Template describes the format and number of additional fields held against members of conforming to the pattern, and provides an envelope within which those additional fields may be further refined for each conforming to the pattern. The Descriptor Template for each pattern is provided in the section describing that pattern. Each defined
that conforms to a pattern will have its own Descriptor, that describes its own specific properties, and although field types must still conform to the Descriptor Template for the pattern, each field type may be further constrained using data sub-types specified in the metadata . This provides some level of to the that may be applied to a conforming to a particular pattern. ...
file structure enables representation of subsets fo SNOMED CT components. However, the reference set format is extensible, allowing it to be used for a wide range of other purposes. For more details about the requirements that reference sets can address please see the Practical Guide to Reference Sets. The basic reference set structure can be extended by adding one or more fields. Each of these fields will hold additional specific values related to each member. Three general data types are supported in the additional columns. These are
| Specref |
|---|
| RefType | (data type) |
|---|
| t | String |
|---|
|
and- (a reference to a
| Gloss |
|---|
| PreSpace | false |
|---|
| t | SNOMED CT component |
|---|
|
)
Finer grained interpretation of these data types can also be specified using a special metadata
known as the | Concept |
|---|
| t | 900000000000456007 Reference set descriptor |
|---|
|
.The
patterns that are supported as part of the are documented in 5.2 Reference Set Types. Additional patterns can also be created as part of an extension to support additional use case (see 45524353)....
The next table summarizes the use cases for
(one per row) that are described in the following sections, and shows which patterns are used in each case: ...
Patterns
...
Use cases
...
*
...
Attribute value type
...
(C)*
...
| Concept |
|---|
| t | 900000000000496009|Simple map type reference set (foundation metadata concept)| |
|---|
|
(S)...
...
*
...
Language
...
(C)*
...
*
...
Query Specification
...
(CCS)*
...
*
...
Annotation
...
(S)*
...
| Concept |
|---|
| t | 900000000000521006|Association type reference set (foundation metadata concept)| |
|---|
|
(C)...
...
...
...
*
...
...
*
...
*
...
Inactivation indicator
...
*
...
CVT3 map
...
*
...
SNOMED RT map
...
*
...
...
*
...
...
*
...
...
*
...
Image annotation (field)
...
*
...
Short annotation (field)
...
*
...
Descriptive annotation (field)
...
*
...
reason for inactivation
...
*
...
RF1 Subset representation
...
*
...
*
...
Note: The letters shown after each pattern indicate the type and number of additional fields held against each member of a
conforming to that pattern, where 'C' is short for , 'S' is short for String (data type) and 'I' is short for Integer . Example:
conforming to the | | Gloss |
|---|
| Space | true |
|---|
| t | Attribute value |
|---|
|
type| (C) pattern will have one additional field held against each member, a component reference; conforming to the |Simple type| pattern will have no additional fields held against each member.