Enhanced support for ValueSet search and import from public terminology servers

[danielhmendoza01]

It would be helpful to include default value sets that are either preloaded or can be easily added. Similar to how the FHIR uploader provides an “Add Built-in Examples” option.

[preston]

This was discussed at the US FHIR Connectathon this week. In short, the CQL with FHIR specification will change to support multiple "terminologyEndpoint" options such that we can provide a list of public terminology endpoints from which to search and pull. So basically this ticket will evolve into a refactoring of application Settings, the Terminology Browser, and way the $evaluate operation is run.

In addition, we'll add support for the value set management IG to make search and import of entire pre-expanded value set packages from VSAC and other systems trivial.

[preston]

Starting with v1.12.12, released today, special support for VSAC search and import integration has been reintroduced by proxying through a required instance of CQL Studio Server. The user needs to have a VSAC API key and provide it in application settings. They can then browse VSAC directly in CQL Studio via the Terminology -> VSAC Browser, search, $expand them (when supported), and import any desired value sets to the local terminology server without having to manually download or upload anything. The Terminology -> Terminology Browser will be changed next to support other, arbitrary external FHIR terminology servers with the same types of features.

[preston]

@danielhmendoza01 This, as well as direct VSAC support is complete. Could you help test these features? If it's possible to cut the first CQL Studio v2.0 release with the next week or so (with this and other feature announcements) I'd like to do that. The FHIR registry search and import feature isn't great yet but does work for some use cases.