Stream: cql
Topic: Java engine: "codeSystemDef" is null
Richard Stanley (Jan 27 2022 at 05:23):
I have a CQL file that has no errors from the VSCode plugin, and evaluates (Java engine) the test data properly. However, there is an error with _refresh.sh which is "ELM generation failed with the following error: Cannot invoke "org.hl7.elm.r1.CodeSystemDef.getId()" because "codeSystemDef" is null". The CQL file in question imports concepts from another CQL file. Other than that, I'm sort of lost as to what that error indicates or where to look.
Bryn Rhodes (Jan 27 2022 at 17:03):
What version of the CQFTooling are you running?
Richard Stanley (Jan 27 2022 at 20:42):
The bash script, _updateCQFTooling.sh seems to lock it to 1.3.1
Richard Stanley (Jan 27 2022 at 21:00):
Oh, I see 1.4.0 was released. I'll update the scripts and have a go.
Richard Stanley (Jan 27 2022 at 21:18):
So, updated tooling. The error persists, but is now more consistent. Anything importing from this CQL file has the error. I was copying the approach for the WHO SMART ANC for CQL file structure, e.g. separate concepts file. https://github.com/intrahealth/simple-hiv-ig/blob/master/input/cql/HIVConcepts.cql
Bryn Rhodes (Jan 28 2022 at 18:29):
Hmmm.... try 1.4.1-SNAPSHOT, I am pretty sure that issue has been addressed
Richard Stanley (Jan 28 2022 at 18:31):
Thanks will do
Richard Stanley (Jan 31 2022 at 02:43):
I built the 1.4.1-SNAPSHOT from the main branch. The tooling complains that "The package 'cqf.fhir.common' has no entry on the current build server". Is this related to the work to use CQF Common for FHIRHelpers and FHIR-ModelInfo that I may need to configure?
Richard Stanley (Feb 01 2022 at 14:17):
I triggered the fhir build server for the missing cqf packages and now 1.4.1-snapshot runs. However, the error above persists: "ELM generation failed with the following error: Cannot invoke "org.hl7.elm.r1.CodeSystemDef.getId()" because "codeSystemDef" is null"
Bryn Rhodes (Feb 02 2022 at 16:18):
Hmm.... it shouldn't be preventing the build or packaging of the Library resources, but it is still an issue. I will take a look and see what the issue is, but I'm going to have to debug.
Last updated: Apr 12 2022 at 19:14 UTC
