Mappings
General Comments
HL7 MIF Vocabulary to LexGrid Coding Scheme
The design and implementation of the LexEVS 6.1 HL7 MIF Vocabulary Loader assumes there is only one <vocabularyModel> XML element contained within the XML load source file being loaded. A single LexGrid Coding Scheme will get created. Refer to the mapping table labeled MIF Vocabulary - VocabularyModel Mapping to LexGrid Coding Scheme for more information on what data is used to create the LexGrid Coding Scheme.
Overview
The current implementation of the LexEVS 6.1 HL7 MIF Vocabulary Loader will load all codeSystems and concept related information contained within the XML load source. Concept related information includes the concept and the properties, relationships and codes the concept has. Concept domain and valueSet related information will NOT be loaded.
Consider the image below of a small set of HL7 MIF Vocabulary loaded data:
As depicted under A1 in the above image, the loader will create a default root node named "@". For each codeSystem XML element in the load source, the loader will create a LexGrid Entity (A3) and a "hasSubtype" association (A2) with the "@" root node. The LexGrid Entity representing a codeSystem XML element will have its entityCode value comprised of the codeSystem's name attribute value and the codeSystem's codeSystemId attribute value concatenated with the colon (":") character as depicted by the value "ConceptStatus:2.16.840.1.113883.5.1086" under A3.
For each concept XML element contained by a codeSystem XML element, the loader will create a LexGrid Entity (A5) and a "hasSubtype" association (A4) with the respective LexGrid Entity (A3) representing the codeSystem. The LexGrid Entity representing a concept XML element will have its entityCode value comprised of the code attribute value of the code XML element contained by the concept XML element and the value of the conceptProperty XML element contained by the concept XML element where the conceptProperty element has a type attribute value defined as the internal identifier type ("internalId"). These two values are concatenated with the colon (":") character to create the entityCode value of the LexGrid Entity as depicted by the value "A:19960" under A5.
Concepts having concept relationships with other concepts will be created by the loader such the association's name (or association predicate) will be the relationshipName attribute value of the conceptRelationship XML element in the load source file. NOTE: these associations between concepts are not depicted in the above image.
Text
Topic two
Add sections as needed. Delete the headings if none are needed. Delete the instructions, leaving the page-info macro and the contents if there are headings.
