The following data types are used in the
| Gloss |
|---|
| PreSpace | false |
|---|
| t | release files |
|---|
|
:
...
Data Type
...
...
| data-types-used-in-release-files | | CapType | Table |
|---|
|
Data Types Used in Release Files |
...
...
| false | | t | SNOMED CT identifier, |
|---|
|
between 6 and 18 digits long, as described in |
|
...
...
...
- This data type is used to identify , to refer to a
|
|
...
...
...
...
...
| A Universally Unique Identifier is a 128-bit unsigned generated using a standard algorithm. - UUIDs are represented as strings of hexadecimal characters split by - characters as points specified by the UUID standard.
| |
|
...
...
...
...
...
...
...
text of a specified length. | | Specref |
|---|
| RefType | (data type) |
|---|
| t | Boolean |
|---|
|
| A Boolean value, represented as one of two possible integer values (1 = true, 0 = false). | |
|
...
| Specref |
|---|
| RefType | (data type) |
|---|
| t | Integer |
|---|
|
...
| A date and time format expressed as a text string in line the basic representation specified in the ISO 8601 standard. - Where only date is required the format is YYYYMMDD (e.g. 20180125 refers to 25th January 2018)
- Where a time is also required the YYYYMMDDThhmmssZ (e.g. 20180125T123000Z refers to 12:30 UTC on 25th January 2018)
- The time should be expressed as UTC, as indicated by the trailing "Z".
|
|
Concept Enumerations
| Glossary include |
|---|
| Gloss | Concept enumeration |
|---|
| Suffix | is the |
|---|
| Def | inline |
|---|
| Example | true |
|---|
| Note | true |
|---|
| Alt | true |
|---|
|
| Caption label |
|---|
| CapId | concept-enumeration-values-subtypes-of-900000000000442005-core-metadata-concept- |
|---|
| CapType | Table |
|---|
|
Concept enumeration values (subtypes of 900000000000442005|Core metadata concept|) |
Concept | Comment |
|---|
| Concept |
|---|
| t | 900000000000443000|Module (core metadata concept)| |
|---|
|
| Each of this represents a development module. These provide values to the field that is present in all file. The value indicates the module within which a was created and is being maintained. |
| Concept |
|---|
| t | 900000000000444006|Definition status (core metadata concept)| |
|---|
|
| Each of this represents a value that can be applied to the . | Specref |
|---|
| RefType | field |
|---|
| t | definitionStatusId |
|---|
|
field. This is used to indicate whether the current set of defining applied to a are sufficient to fully-define it relative to its supertypes. |
| Concept |
|---|
| t | 900000000000446008|Description type (core metadata concept)| |
|---|
|
| Each of this represents a value that can be applied to the . field. This is used to indicate whether the represents a , a synonymous term, a definition or some other symbolic or textual representation of the associated . |
| Concept |
|---|
| t | 900000000000447004|Case significance (core metadata concept)| |
|---|
|
| Each of this represents a value that can be applied to the . | Specref |
|---|
| RefType | field |
|---|
| t | caseSignificanceId |
|---|
|
field. This is used to indicate whether the text of the term can be modified to by switching characters from upper to lower case (or vice-versa). |
| Concept |
|---|
| t | 900000000000449001|Characteristic type (core metadata concept)| |
|---|
|
| Each of this represents a value that can be applied to the . | Specref |
|---|
| RefType | field |
|---|
| t | characteristicTypeId |
|---|
|
field. This is used to indicate whether a forms part of the definition of the source . |
| Concept |
|---|
| t | 900000000000450001|Modifier (core metadata concept)| |
|---|
|
| Each of this represents a value that can be applied to the . field. This is used to indicate the type of (DL) restriction (some, all, etc.) that applies to the . |
| Concept |
|---|
| t | 900000000000453004|Identifier scheme (core metadata concept)| |
|---|
|
| Each of this represents a value that can be applied to the . | Specref |
|---|
| RefType | field |
|---|
| t | identifierSchemeId |
|---|
|
field. This is used to indicate the scheme to which the value belongs. |
...
...
For
a time format down to day of the year is used, having an 8601 basic representation of YYYYMMDD . For development interchange formats, an ASCII text field in the
8601 basic format YYYYMMDDThhmmss Z will be used. The time zone will always be UTC, as indicated by the trailing "Z". (e.g. 20080602T223000Z represents 10:30pm June 2 2008 UTC.) Related Links
...