The Identifier File does not contain any data in the SNOMED CT International Release
The file structure is documented here only as a point of reference for others who may be using the files in an extension release.
This file provides a standardized way of associating alternatefrom various schemes with.
At any point in time, an alternatewithin a particular scheme will be associated with one and only one. Amay be associated with zero or more alternatewithin a single scheme.
It is important to note that theand its alternateall identify precisely the same real-world object.
Note: The Identifier file is not currently used in theas use of the more flexiblestructure 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.
|Part of Primary Key|
of theenumeration value from the Metadatathat represents the scheme to which thevalue belongs. Set to aof 900000000000453004 |Identifier scheme| within the metadata.
String representation of the alternatein its native scheme.
Specifies the inclusive date at which the alternatewas associated with the.
Specifies whether the association wasorfrom the point in time specified by the effectiveTime .
Identifies the source module that this association was created in. Set to aof 900000000000443000 |Module| within the metadata.
Uniquely identifies thewith which the alternateis associated.
Only one record with the same identifierSchemeId and alternateIdentifier fields will be current at any point in time. The current record will be the one with the most recent effectiveTime before or equal to the point in time under consideration.
If thefield of this record is false ('0'), then the association isat that point in time. If thefield is true ('1'), then there is an identity at that point in time between the referencedComponentId (a) and the alternateIdentifier in the scheme identified by identifierSchemeId.