The basic
data structure consists of the following fields:
| Table width manager |
|---|
|
Field | Data type | Purpose | | id | | A 128 bit unsigned | Specref |
|---|
| RefType | (data type) |
|---|
| t | Integer |
|---|
|
, uniquely identifying the member. | NO | | Specref |
|---|
| RefType | (field) |
|---|
| t | effectiveTime |
|---|
|
| | Specifies the inclusive date at which this change becomes effective. | YES | | | Specref |
|---|
| RefType | (data type) |
|---|
| t | Boolean |
|---|
|
| Specifies whether the member's state was or from the nominal release date specified by the | Specref |
|---|
| RefType | (field) |
|---|
| t | effectiveTime |
|---|
|
field. | YES | | | Identifies the member version's module. Set to a of | Concept |
|---|
| t | 900000000000443000|Module| |
|---|
|
within the metadata . | YES | | | Uniquely identifies the that this row is part of. Set to a of | Concept |
|---|
| t | 900000000000455006|Reference set| |
|---|
|
within the metadata . | NO | | Specref |
|---|
| RefType | (field) |
|---|
| t | referencedComponentId |
|---|
|
| or | Uniquely identifies the component that this row relates to, thus defining membership of this component in the . This field can be set to the of a record within the , , or member file. However, the content of this field can be further restricted for each by the descriptor (see the " | Gloss |
|---|
| t | SNOMED CT Release Format 2 |
|---|
|
- Specifications" document for more details). | NO | Zero or more other fields dependent on reference set type | , | Specref |
|---|
| RefType | (data type) |
|---|
| t | String |
|---|
|
, or Integer | Optional field(s) serving purposes specific to the reference set type. For details see | |
...
...
Each
will be defined as is identified and named by a
in the
metadata hierarchy.
There will be one row in the above table for Therefore the reference set is identified by a concept identifier (an ). Each row in a reference set file represents a each member of the
.
Individual | Gloss |
|---|
|
members will be uniquely identified using - Individual reference set members are uniquely identified by a identifier represented as a .
...
...
...
...
-
- Each reference set member belongs to a single reference set, and it is linked to that reference set by the field.
- Each reference set member is also associated with a single referenced component by its
| Specref |
|---|
| RefType | (field) |
|---|
| t | referencedComponentId |
|---|
|
field
...
...
- referenced component may be a
...
...
...
- . If the referenced component is a concept that identifies another reference set than that reference set may be considered to be the target of the reference.
- Like
...
- , reference set members can be versioned to inactivate or change the status of the member. So there may be several rows in a
...
- file and in this case the one with the most recent
...
- effectiveTime before or equal to the point in time under consideration represents state of that reference set member.
...
...
...
...
- the reference set member is at that point in time, which means that component it refers to is not a member of the reference set. If the field is true ('1'), then the component referenced by the
| Specref |
|---|
| RefType | (field) |
|---|
| t | referencedComponentId |
|---|
|
field is deemed to be a member of the
...
The
and
| Specref |
|---|
| RefType | (field) |
|---|
| t | referencedComponentId |
|---|
|
fields will not change between two rows with the same id, in other words they are immutable. Where a change is required to one of these fields, the current row will be inactivated (by appending a row with the same id and the
field set to false)
and another . Another row with a new id will be appended
to reference another component.
A component may belong to any number of
and to each more than once. In the latter case, there will be more than one row with the same refsetId and | Specref |
|---|
| RefType | (field) |
|---|
| t | referencedComponentId |
|---|
|
, each having different id fields, so co-existing at the same time.Extending The Basic Reference Set Member File Format
. A component may also be referenced by more that one member of the same
The member file structure may be extended by addition of one or more fields. Each of these fields will hold additional values specific to each member. Data types that are supported in the additional columns are:- Integer
| Specref |
|---|
| RefType | (data type) |
|---|
| t | String |
|---|
|
- (a reference to a ).
Finer grained interpretation of the values is based on the
| Concept |
|---|
| t | 900000000000456007|Reference set descriptor| |
|---|
|
. Further details can be found in the | Gloss |
|---|
| t | Reference set specifications |
|---|
|
.The
patterns that are supported as part of the are documented in 4.2. Reference Set Types. Additional patterns can also be created as part of an extension to support additional use case (see 4.1.2. Extending the Basic Reference Set Member File Format). This is not useful in the case of a simple reference set but is relevant for some reference sets. For example, a SNOMED CT concept may map to or from more than on codes in another code system.