This file provides a standardized way of associating alternate
from various schemes with
.
At any point in time, an alternate
within a particular scheme will be associated with one and only one
. A
may be associated with zero or more alternate
within a single scheme.
It is important to note that the
and its alternate
all identify precisely the same real-world object.
Note: The Identifier file is not currently used in the
as use of the more flexible
structure is preferred for links to alternative codes. The only known current use
of this file is for internal identification of components during the content development
process.
|
Table 12. Identifier file - Detailed Specification |
|
|
|
|
|---|---|---|---|---|
|
Field |
Data type |
Immutable |
Purpose |
|
|
Y |
|
|
||
|
Y |
String (data type) representation of the alternate
|
|
||
|
N |
Specifies the inclusive date at which the alternate
|
|
||
|
N |
Specifies whether the association was
|
|
||
|
N |
Identifies the source module that this association was created in. Set to a
|
|
||
|
Y |
Uniquely identifies the
|
|
Only one record with the same identifierSchemeId (field) and alternateIdentifier (field) fields will be current at any point in time. The current record will be the one with the most recent effectiveTimebefore or equal to the point in time under consideration.
If the
field of this record is false ('0'), then the association is
at that point in time. If the
field is true ('1'), then there is an identity at that point in time between the
referencedComponentId (field) (a
) and the alternateIdentifier in the scheme identified by
identifierSchemeId (field) .
Related Links
Feedback
Overview
Content Tools
Apps