chronic-care / mcc-project

MCC eCare Plan project planning and documentation
Apache License 2.0
0 stars 1 forks source link

Automate retrieval of value sets from VSAC or similar services #225

Open kbertodatti opened 2 years ago

kbertodatti commented 2 years ago

Currently, the provider app has hardcoded value sets embedded. For common data services, we need to externalize the use of value sets.

Tool: cqframework/cqf-tooling#298

This is an independent command-line utility written in Java to download all IG valuesets as FHIR R4 ValueSet to your computer file system.

Symptoms Value Set Library: https://build.fhir.org/ig/HL7/fhir-us-mcc/branches/master/mcc_symptom_value_sets.html Conditions Value Set Library: https://build.fhir.org/ig/HL7/fhir-us-mcc/branches/master/mcc_chronic_condition_value_sets.html

Relevant for testing HIE data.

kbertodatti commented 2 years ago

From @drdavec: * The provider app currently has limited use of value sets, only for lab observations, I believe? The patient app makes much more use of value sets for Conditions, and all of this logic is in CQL. The production pilot testing at OHSU in Jan-March will help us evaluate performance and use of CQL going forward. We need to evaluate next steps to generalize and expand use of value sets in the provider app and how this fits into its current API design that is very different from the patient app.

savanahmueller commented 1 year ago

Dave and Sean will review value set synchronization in patient app

drdavec commented 1 year ago

My understanding of this task's requirements are to download a FHIR R4 ValueSet resource for each of the eCare IG value sets hosted in VSAC that are needed for our applications, including the CQL logic.

VSAC provides a standard FHIR terminology service, as documented here: https://www.nlm.nih.gov/vsac/support/usingvsac/vsacfhirapi.html

For each of the value set OIDs defined in the eCare IG (or, only those needed by our applications), use this request to retrieve the value set: https://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113883.11.20.9.46/$expand

The Java based tool linked in this original card is one possible starting point to automate this retrieval. This tool was suggested by Bryn Rhodes during the Sept 2022 connectathon, but he acknowledged it was an incomplete work in progress. We do not necessarily need to base our implementation on this tool, but if we do, it would be nice to contribute a PR with updates.

savanahmueller commented 1 year ago

Sean to develop a turnkey script to run at connectathon. Currently we can only point testers to a repository but no way to run it.

kbertodatti commented 9 months ago

Putting in Icebox. This is only needed for developing and testing CQL logic outside of the app.