 |
Page History
...
Currently LexEVS can load a value set definition to the underlying database, but does not persist the resolution of that definition. Additional persistence functionality will be added to the LexEVSValueSetDefinition API to provide the needed loader for resolved value sets. Since value sets are comprised of LexEVS entities, the resolution of these value sets can be persisted to a coding scheme created specifically as a container for that value set. Since terminology services will want to distinguish between value set coding schemes and actual coding schemes a coding scheme property named codingschemetype with value valueset will allow internal API's for coding schemes to distinguish between the two types, preventing external users from seeing value set coding schemes in the terminology service list of terminologies. The effect will be that the coding scheme API will never "see" the coding scheme value sets and the resolved value set API will only see the value set type coding schemes.
