Page History
...
- 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).
- Mapping of these values will be incomplete: Mapping proposal:
- 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.
LexGrid Text
Wiki Markup |
---|
The text files that can be imported must use the following formats. Items surrounded by <> are required. Items further surrounded by \[\] are optional. \t represents a tab - the default delimiter - however other delimiters may be used. |
Lines beginning with # are comments.
...
the first "real" line of the file must be of the following format:
No Format |
---|
# |
Wiki Markup |
---|
<codingSchemeName>\t<codingSchemeId>\t<defaultLanguage>\t<formalName>\[-t_version_\]\[-t_source_\]\[-t_description_\]\[-t_copyright_\] |
colors 1.2.3 en colors coding scheme 1.0 Someone's Head a simple example coding scheme using colors This isn't worth copyrighting
No Format |
---|
# |
The rest of the file (for format A) should look like this:
...
the first "real" line of the file must be of the following format:
No Format |
---|
# |
Wiki Markup |
---|
<codingSchemeName>\t<codingSchemeId>\t<defaultLanguage>\t<formalName>\[-t_version_\]\[-t_source_\]\[-t_description_\]\[-t_copyright_\] |
colors2 1.2.4 en colors coding scheme 1.1 Someone's Head a simple example coding scheme using colors This isn't worth copyrighting
No Format |
---|
# |
The rest of the file (for format B) should look like this:
Code Block |
---|
1 Color Holder of colors 4 Red 6 Green The color Green 7 Light Green 8 Dark Green 5 Blue 8 Dark Green The color dark green 6 Green A different color of green |
Scrollbar | ||
---|---|---|
|
...