The purpose of the |
descriptor| is to describe the format of all
otherthat other that may be included in a release. A Descriptor held within the |
Descriptor| describes the referencedComponentIdfield and the additional fields for
theit the it describes. Each field is described using
ain a in the metadata. The type of each field is also described in the same way.
Patterns allow a number of different types ofto of
to be defined, each of which will conform to the specified pattern, having the
sameformatsame format. The file format of
eachpattern each pattern is described by a Descriptor Template. This Descriptor Template describes the format and number of additional fields held against members
ofconforming of conforming to the pattern, and provides an envelope within which those additional fields may be further refined for
eachconforming each conforming to the pattern. The Descriptor Template for each pattern is provided in the section describing that pattern.
Each definedthat defined
that conforms to a pattern will have its own Descriptor, that describes its own specific properties, and
althoughfield 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
ofto thethat of to the that may be applied to
aconforming a conforming to a particular pattern.
Anchor |
---|
| _68b93eb5-3fed-4f72-b3fa-b4488278db43__f |
---|
| _68b93eb5-3fed-4f72-b3fa-b4488278db43__f |
---|
|
Anchor |
---|
| _68b93eb5-3fed-4f72-b3fa-b4488278db43__1 |
---|
| _68b93eb5-3fed-4f72-b3fa-b4488278db43__1 |
---|
|
Figure 3. Graphical view of Relationships between patterns, reference sets, Descriptor Templates and Descriptors
Anchor |
---|
| _5fd40e3d-bba3-4660-9353-a9d331fe373f |
---|
| _5fd40e3d-bba3-4660-9353-a9d331fe373f |
---|
|
Patterns and Use Cases
The next table summarizes the use cases for
(one per row) that are described in the following sections, and shows
whichpatterns which patterns are used in each case:
...
| Patterns | | | | | | | | | |
---|
Use cases | * | Attribute value type | (C)* | Scg expression |
---|
ShowParts | id Concept |
---|
t | 900000000000496009|Simple |
---|
| (S) | Scg expression |
---|
ShowParts | id(IISSSC) | * | Language | (C)* | * | Query Specification | (CCS)* | * | Annotation | (S)* | Scg expression |
---|
ShowParts | id Concept |
---|
t | 900000000000521006|Association |
---|
| (C) | Scg expression |
---|
ShowParts | id(IC) | scg-expressionShowPartsid | |
---|
| * | | | | | | | | |
| * | | * | | | | | | |
Inactivation indicator | * | | | | | | | | |
CVT3 map | | * | | | | | | | |
SNOMED RT map | | * | | | | | | | |
| | | | * | | | | | |
| | | | * | | | | | |
Intension specification Intensionspecification | | | | | * | | | | |
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 aconforming 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.