Dynamic Resolution of Source Asserted Resolvable Value Sets

• Reduction of work flow tasks and load times
• Higher performance for value set resolution by end Users

Resolved Value Set API Side Effects

• No resolved value set coding schemes reduces tremendously the number of value sets available to users under this API
• Adding these value sets back in as a dynamic presence should make this API work the same as before

CTS2 Resolved Value Set API Side Effects

• CTS2  makes use of the Resolved Value Set API for one of two CTS2 exposed Resolved Value Set functions.
• We will have to update the service to point both methods to source asserted supported methods to make things work the same as they did before.

Unintended API's Used to Query Value Sets

• It is possible to use any regular api to search value sets as coding schemes.  While this wasn't intended, it may be how some users could be searching value sets.
• We don't have a good way of anticipating this use, but can offer the extension of higher performing asserted value set searches.  

Extending Asserted Value Sets to the Distributed (AKA remote) API

• Any asserted value set API's would have to be extended to the remote API for use by Kim and any other remote API user who might need them.