 |
Page History
...
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 , value set and code system supplement related information will NOT be loaded.
Consider the following image below of a small set of HL7 MIF Vocabulary loaded data:
As depicted under A1 in the above image, the LexEVS loader will create a default root node LexGrid Entity named "@". For each codeSystem XML element in the load source, the LexEVS loader will create a LexGrid Entity (A3) and a "hasSubtype" association (A2) with the "@" root node where the the "@" root node entity is the source entity and the codeSystem entity depicted by (A3) is the target entity. 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 LexEVS loader will create a LexGrid Entity (A5) and a "hasSubtype" association (A4) with the respective LexGrid Entity (A3) representing the codeSystem where the codeSystem entity (A3) is the source entity and the concept entity (A5) is the target entity. 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 concept's 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 LexEVS 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.
...
The LexEVS loader handles the multiple code scenarios for a concept by creating a LexGrid Entity for each of the codes contained within the concept. The entityCode value for the LexGrid Entity, as described in the previous Overview section, uses the code value along with concept’s internal identifier type property to distinguish the LexGrid Entities from each other and still have a mechanism via the concept’s internal identifier value to tie them to the same load source concept. The LexEVS loader will apply any concept properties and concept relationships the concept has to each of the LexGrid Entities. For example, if a concept having internal identifier value "12345" has codes ABC and DEF defined and has one concept relationship to the target code XYZ with a relationshipName attribute value of “Specializes” defined, the LexEVS loader will create the “Specializes” LexGrid AssociationPredicate and Associations to the target entity XZY for both source entities ABC and DEF as shown belowin the following diagram.
Mapping Information
...
MIF Vocabulary - VocabularyModel Mapping to LexGrid Coding Scheme
...
