Page History
...
codeSystemName | Code system OID | Internal concept identifier | Concept code | Designation |
---|---|---|---|---|
HL7ConformanceInclusion | 2.16.840.1.113883.5.55 | 10011 | R | Required - V2.x |
HL7ConformanceInclusion | 2.16.840.1.113883.5.55 | 10011 | M | Mandatory |
HL7ConformanceInclusion | 2.16.840.1.113883.5.55 | 10011 | M | Required - V2.x |
HL7ConformanceInclusion | 2.16.840.1.113883.5.55 | 10011 | R | Mandatory |
...
Representing HL7 in LexGrid
...
- A single coding scheme will be created in LexGrid.
- Each VCS_concept_code_xref.internalId will be represented as a LexGrid Concept Code.
- The LexGrid Concept Code will be generated by the concatination of VCS_concept_code_xref.internalId and VCS_concept_code_xref.conceptCode2 (separated by a colon ':' ).
- Not only the duplicates that exist within coding schemes will be dealt with using the id/mnemonic concatenation but also those duplicates that exist between coding schemes.
- A LexGrid Concept Code Presentation Property will be created for each HL7 designation (VCS_concept_designation).
- The Presentation Property will include Presentation (HL7 Designation), Source (HL7 codeSystemName) and a Property Qualifier of source-code (HL7 Concept Code).
For example, the following structure represents both HL7 10011 entries in code system 2.16.840.1.113883.5.55: - Coding Scheme: HL7 - urn:oid:2.16.840.1.113883.3.26.1.2
- Concept Code: <span style="background-color: #99FFFF">10011:M</span>
- Entity Description: >The message element must appear every time the message is communicated and its value must not be null. This condition is subject to the rules of multiplicity and conditionality. If a non-null default value is defined for the element, a null value may be communicated.
- Status: Active
- Is Active: true
- Is Anonymous: false
- Presentation: <span style="background-color: #99FFFF">Mandatory</span>
- Property Name: textualPresentation
- Property Id: T-1
- Language: ENG
- Is Preferred: true
- Representational Form: PT
- Source: <span style="background-color: #99FFFF">HL7ConformanceInclusion</span> , Role: null, SubRef: null
- Property Qualifier Id: <span style="background-color: #99FFFF">source-code</span> , Property Qualifier Content: <span style="background-color: #99FFFF">M</span>
- Presentation: <span style="background-color: #99FFFF">Required - V2.x</span>
- Property Name: textualPresentation
- Property Id: T-2
- Language: ENG
- Is Preferred: false
- Representational Form: PT
- Source: <span style="background-color: #99FFFF">HL7ConformanceInclusion</span>, Role: null, SubRef: null
- Property Qualifier Id: <span style="background-color: #99FFFF">source-code</span> , Property Qualifier Content: <span style="background-color: #99FFFF">M</span>
- Coding Scheme: HL7 - urn:oid:2.16.840.1.113883.3.26.1.2
- Concept Code: <span style="background-color: #99FFFF">10011:R</span>
- Entity Description: >The message element must appear every time the message is communicated and its value must not be null. This condition is subject to the rules of multiplicity and conditionality. If a non-null default value is defined for the element, a null value may be communicated.
- Status: Active
- Is Active: true
- Is Anonymous: false
- Presentation: <span style="background-color: #99FFFF">Mandatory</span>
- Property Name: textualPresentation
- Property Id: T-1
- Language: ENG
- Is Preferred: true
- Representational Form: PT
- Source: <span style="background-color: #99FFFF">HL7ConformanceInclusion</span> , Role: null, SubRef: null
- Property Qualifier Id: <span style="background-color: #99FFFF">source-code</span> , Property Qualifier Content: <span style="background-color: #99FFFF">R</span>
- Presentation: Required - V2.x
- Property Name: textualPresentation
- Property Id: T-2
- Language: ENG
- Is Preferred: false
- Representational Form: PT
- Source: <span style="background-color: #99FFFF">HL7ConformanceInclusion</span>, Role: null, SubRef: null
- Property Qualifier Id: <span style="background-color: #99FFFF">source-code</span> , Property Qualifier Content: <span style="background-color: #99FFFF">R</span>
...
Loading the HL7 Rim as a
...
Monolithic Coding Scheme
- Load coding scheme data as HL7 Rim Metadata from the Model table (rather than the coding scheme data for each HL7 coding scheme).
- Mapping of these values will be incomplete:
- Mapping proposal:
LexGrid
HL7 RIM
<codingSchemeName>
<modelID>
<formalName>
<name>
<registeredName>
http://www.hl7.org/Library/data-model/RIM
*
<defaultLanguage>
en*
<representsVersion>
<versionNumber>
<isNative>
0*
<approximateNumberofConcepts>
Result of count on concept bearing table?
<firstRelease>
MISSING
<modifiedInRelease>
MISSING
<deprecated>
MISSING
<entityDescription>
<description>
<copyright>
MISSING
- No URN exists and we may need to consider creating one (see entry for registeredName).
- Locate and load all mappings (such as supportedAssociations and supportedProperties).
- Create a supportedHiearchy with a root node of @ on hasSubtype?
- Iterate through the code system table rows and get each coding scheme.
- Create and persist an "@" node in the database
- Prepare an artificial "top node" for each coding scheme. (Metadata persisted here as concept properties?) This will result in 250 top nodes.
- The artificial top nodes will need to have a concept code created for them.
- Attach to "@" the artificial top nodes as a hasSubtype.
- Locate the actual top nodes of each coding scheme by querying the relations table to see if they exist as a target code, if not, they are top nodes so attach them to the artificial top node via hasSubtype.
- Translate the RRF source property loads to the EMF world.
- Load the concepts ensuring that the coding scheme name is loaded as a "source" property
- Load the relations ensuring that the source and target coding scheme data is loaded with the coding scheme name.
- Concurrent to this process create an updated "HL7 RIM to LexGrid for NCI" mapping from the current Excel mapping document.
...
The leading tabs represent hierarchical "hasSubtype" relationship nesting:
- (name1 hasSubtype name2 and name2 hasSubtype name3)
- Concept Codes will be automatically generated.
- If a name is used more than once - it will be assigned the same code.
- If a description is used more than once (for a given name) only the first description will be stored.
Format B
In this format, concept codes can be provided. This is the same as "Format A" with the inclusion of concept codes as part of the input.
...