Important Note
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 alternative Identifiersfrom various schemes with SNOMED CT components.
At any point in time , an alternative Identifierwithin a particular scheme will be associated with one and only one SNOMED CT component. A SNOMED CT componentmay be associated with zero or more alternative Identifierswithin a single scheme.
It is important to note that the SNOMED CT componentand it's alternative Identifiersall identify precisely the same real-world object.
Note: The Identifier file is not currently used in the SNOMED CT International Releaseas use of the more flexible Simple map type references setstructure 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.
Field | Data type | Purpose | Part of Primary Key | |
Identifierof the conceptenumeration value from the Metadata hierarchythat represents the scheme to which the Identifiervalue belongs. Set to a descendantof 900000000000453004 | Identifier scheme| within the metadata hierarchy. | NO | YES (Full/Snapshot) | ||
String representation of the alternative Identifierin its native scheme. | NO | YES (Full/Snapshot) | ||
Specifies the inclusive date at which the alternative Identifierwas associated with the SNOMED CT component. | YES | YES (Full) Optional (Snapshot) | ||
Specifies whether the association was activeor inactivefrom the point in time specified by the effectiveTime . | YES | NO | ||
Identifies the source module that this association was created in. Set to a childof 900000000000443000 | Module| within the metadata hierarchy. | YES | NO | ||
Uniquely identifies the SNOMED CT componentwith which the alternative Identifieris associated. | NO | NO |
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 the activefield of this record is false ('0'), then the association is inactiveat that point in time. If the activefield is true ('1'), then there is an identity at that point in time between the referencedComponentId (a SNOMED CT component) and the alternateIdentifier in the scheme identified by identifierSchemeId.
Feedback