.01identifier0;1FREE TEXTBThis is the code or id associated with an instance of this concept. The identifier in conjunction with CODING SYSTEM field (#.02) indicates its use and source.
.02coding system(+)0;2FREE TEXTCIdentifies the name of the coding system which this code is derived from.
.03purpose0;3SET OF CODES1:RESULT
Classifies the code as a result or answer code. Codes from HL7 OBX segment field OBX-3 should be classified as result codes. Example is LOINC code 11475-1 MICROORGANISM IDENTIFIED: PRID:PT:XXX:NOM:CULTURE that represents the concept of organism identified. Codes from HL7 OBX segment field OBX-5 should be classified as answer codes. Example is SNOMED CT code 30334005 AEROMONAS SALMONICIDA (ORGANISM) that represent the name of organism identified.
.04override concept0;4POINTER62.47For 'answer' type codes this field indicates the related area of the Laboratory package database where answers to this code are to be stored. It is used when the 'answer' that is associated with a 'result' code cannot not be stored in the usual VistA Laboratory LAB DATA file (#63) field. Example: SNOMED CT code 23506009 is the term 'normal flora'. This term can be the 'answer' used in several places within the Lab DATA file (#63). If it is associated as the 'answer' to a microorganism identified code instead of being stored as an entry in the ETIOLOGY FIELD file (#61.2) it would be stored as a comment.
.05national standard0;5BOOLEAN0:NO
ACThis field indicates whether this entry was distributed nationwide. If not, then it was entered locally.
2.1related entry2;1VARIABLE-POINTER61.2, 62.06AELinks this code/codeset to an entry in one of the pointed-to files. This allows the system to determine how to translate a code/codeset to a file entry.
2.2message configuration2;2POINTER62.48AGWhen the related identifier (code) is from a local coding system then this field indicates for which specific interface the code is associated with. Local codes are interface specific.

Error: Invalid Global File Type: 62.4701