ahrq-cds / cql-testing-framework Goto Github PK

Hello again,

thanks for your previous help for the first issue about the "dosage" attribute. Another element we are trying to implement involves the "Medication" resource type. Specifically from this we would like to access items from the "ingredient" part of this where we extract the "amount" of a medication. FHIR provides an example of this for a medication statement here where we can see the "Tylenol PM" medication specified as an ingredient named "Acetaminophen 500 MG" which has an amount 500 milligrams.

We notice that the test cases support specifying the "medication[x]" portion of MedicationStatements via the CodeableConcept, but it looks like for the functionality above it would need to be done through a reference to a full medication object, which doesn't currently seem to be a supported resource type. Is this correct? If so, what steps would you suggest for implementing the use of full medication objects?

Thank you for your time!
-Eric

Hello,
I am a researcher at the University of Pittsburgh Department of Biomedical Informatics and our lab forked this repository in order to work with it for drug-drug interaction alerting. For many of our use cases, though, we would like to be able to use STU3 MedicationStatement items such as "dosage" and the amount for each ingredient(s) of the medication. We understand that currently "dosage" is not a supported attribute , but on our fork I have looked into how to implement these ourselves via the src file loadYamlTestCases.js in the function "handleMedicationStatement".

I have only gotten this to be able to partially work for implementing dosage, though, basically by adding a line for "dosage: d.dosage ? d.dosage : undefined" in the "handleMedicationStatement" return statement. Below are a couple of screenshots of how the YAML I am trying to test is outputted with this addition. It looks like only the dosage text made it through but none of the other "dosage" elements.

So overall:

• Is there a general process that you all have for implementing new attributes for these resources?
• Do you have additional pointers for which files/functions I should look into that are necessary to keep up to date for implementing additional attributes?

Thank you!
-Eric

I recently started working with CQL-Testing-Framework in my work at Optum. I tried to run the cql2elm tool that is included with this repo. I installed it in my IG by adding "cql-testing": "^2.6.1" to my package.json.

When I tried to run cql2elm, I got a NoClassDefFoundError from java. A little bit of research and hacking lead to a temporary,brittle solution of adding runtimeOnly 'xmlpull:xmlpull:1.1.3.1' to the node_modules/cql-testing/build.gradle

Once I added that dependency, the tool ran as expected and generated the ELM json files that are needed by CQL-Testing-Framework.