NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Old Version 1

changes.mady.by.user Bauer, Scott (NIH/NCI) [C]

Saved on

compared with

New Version 2

changes.mady.by.user Bauer, Scott (NIH/NCI) [C]

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

LexEVS 6.1 has all the administrative capabilities of LexEVS 6.0 as well as the following loader functions:

 

LexEVS 6.1 OWL2 Loader

...

Script

 Loads a file specified in the Medical Dictionary for Regulatory Activities (MedDRA) format.
Options:
  •    -in,--input <uri> URI or path specifying location of the source file
  •    -mf,--manifest <uri> URI or path specifying location of the manifest file
  •    -v, --validate <int> Perform validation of the candidate  resource without loading data.  If specified, the '-a' and '-t' options are ignored.  Supported levels of validation include:0 = Verify document is valid
    •    -a, --activate ActivateScheme on successful load; if unspecified the vocabulary is loaded but not activated.
  •    -t, --tag <id> An optional tag ID (e.g. 'PRODUCTION' or 'TEST') to assign.
    • Load Example:

    Shell Script

    Use and Function

    LoadMedDRA

    Code Block
    LoadMedDRA -in "file:///path/to/file.asc" -a
    Validation Example:
    Code Block
     LoadMedDRA -in "file:///path/to/file.asc" -v 0

    LoadMIFVocabulary

     Loads from an the HL7 Vocabulary mif file.
     Options:
    •    -in,--input <uri> URI or path specifying location of the source file.
    •    -a, --activate ActivateScheme on successful load; if unspecified the vocabulary is loaded but not activated.
    •    -t, --tag <id> An optional tag ID (e.g. 'PRODUCTION' or 'TEST') to assign.
    Load Example:
    Code Block
    LoadMIFVocabulary -in "file:///path/to/file.xml" -a
    Info
    titleNote

    This replaces the LoadHL7RIM script and function

    LoadOWL2

     Loads an OWL file. You can provide a manifest file to configure coding scheme# meta data.

     Options:

    •    -in,--input <uri> URI or path specifying location of the source file
    •    -mf,--manifest <uri> URI or path specifying location of the manifest file
    •    -lp,--loaderPrefs<uri> URI or path specifying location of the loader preference file
    •    -v, --validate <int> Perform validation of the candidate resource without loading data.  If specified, the '-a' and '-t' options are ignored.  Supported levels of validation include:
    •          0 = Verify document is well-formed
    •          1 = Verify document is valid
    •    -a, --activate ActivateScheme on successful load; if unspecified the vocabulary is loaded but not activated.
    •    -t, --tag <id> An optional tag ID (e.g. 'PRODUCTION' or 'TEST') to assign.


     Load Example:

    Code Block
    LoadOWL2 -in "file:///path/to/somefile.owl" -a
    Code Block
    LoadOWL2 -in "file:///path/to/somefile.owl" -v 0

    LoadResolvedValueSetDefinition

    Loads Value Set Definition content, provided in LexGrid canonical xml format.

     Options:
       -u, The valueset definition URI to use
       -l, The list of coding schemes to revolve against. The format is codingschemeName::version
       -csVersionTag    The tag to use for resolving coding scheme
           
     Load Example:
    Code Block
    LoadResolvedValueSetDefinition -u \"Automobiles:valuesetDefinitionURI\" -l \"Automobiles::version1, GM::version2\" -csVersionTag \"production\" ""
    Wiki Markup
    {scrollbar:icons=false}

    ...