NIH | National Cancer Institute | NCI Wiki  

WIKI MAINTENANCE NOTICE

Please be advised that NCI Wiki will be undergoing maintenance Monday, July 22nd between 1700 ET and 1800 ET and will be unavailable during this period.
Please ensure all work is saved before said time.

If you have any questions or concerns, please contact the CBIIT Atlassian Management Team.

Error rendering macro 'rw-search'

null

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

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

 

LexEVS 6.1 Loader Scripts

Shell Script

Use and Function

LoadMedDRA

 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:

LoadMedDRA -in "file:///path/to/file.asc" -a


Validation Example:

 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:

LoadMIFVocabulary -in "file:///path/to/file.xml" -a

Note

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:

LoadOWL2 -in "file:///path/to/somefile.owl" -a
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:

LoadResolvedValueSetDefinition -u \"Automobiles:valuesetDefinitionURI\" -l \"Automobiles::version1, GM::version2\" -csVersionTag \"production\" ""

:

  • No labels