Author: Craig Stancl, Scott Bauer, Kevin Peterson, Sridhar Dwarkanath
Email: stancl.craig@mayo.edu, bauer.scott@mayo.edu, peterson.kevin@mayo.edu, dwarkanath.sridhar@mayo.edu
Team: LexEVS
Contract: CBITT BOA Subcontract# 29XS223
Client: NCI CBIIT
National Institutes of Heath
US Department of Health and Human Services
Revision History
Version | Date | Description of Changes | Author |
|---|---|---|---|
1.0 | 2011/02/10 | Initial Version | — |
1.0 | 2011/02/10 | — | — |
Resolved Value Domain Persistence
The Resolved Value Domain Persistence mechanism provides a means to store the results of a resolve valueset definition. In LexEVS the persistence is achieved by treating the resolved value domain as a coding scheme. The coding scheme uri of the persisted value domain is the same as the uri of the valueset definition. The version number is generated using the MD5 value of the string that makes up the value domain definition. The information of the coding schemes which were used for the resolution is stored as coding scheme properties. The
Implementation
The resolved value domain persistence is implemented by treating the valueset as a special coding scheme. The results of the resolution of a value domain definition against a set coding schemes are treated as concepts that get stored in a coding scheme. A loader has been developed that takes the valueset definition uri and the set of coding schemes to use for resolution against as input and stores the results in a persisted coding scheme. The loader can be invoked by using the admin script:
LoadResolvedValueSetDefinition.sh
The parameters of the script are:
LoadRevolvedValueSetDefinition.sh -u \"Automobiles:valuesetDefinitionURI\" -l \"Automobiles::version1, GM::version2\" -csVersionTag \"production\" ""
where the -u "the valueset definition uri"
-l "list of coding schemes to use for the resolution"
-csVersionTag "tag to use for the load"
LoadResolvedValueSetDefinition.sh
