JP
JP
Hi @csandersdev . There are actually two JSON serialization formats supported by the CQL translator one for Jaxb (JSON) and one for Jackson (JXSON). The CQL Engine supports the Jackson...
We initially introduced the use of Jackson because of lack of JAXB support on Android. At the time we did the merge we thought it was likely backwards compatible though...
I've dug into this enough to confirm that the JAXB and Jackson formats can't be fully reconciled at this time. I did a fair amount of investigating on getting JAXB...
So are the next steps here to shoot an e-mail to the Bonnie team to discuss the possibility of annotations as HTML?
What are the next steps on this? Does the XML structure Bryn posted above work for your use case @mgramigna ?
So, I understand the resolution to be that we're phasing out JAXB in favor of Jackson with a transition period. Post transition period it'll all be Jackson, and it'll include...
There are some pending updates to the cql-translator that supersede some of this discussion: cqframework/clinical_quality_language/pull/752
The annotations work for JSON because of an opposite bug: https://github.com/DBCG/cql_engine/issues/453
Converted to draft PR given that we need to reconcile some fixed vs arbitrary precision issues in the CQL spec.
The fix for this is probably either adding a specific resolution for that type here: https://github.com/DBCG/cql_engine/blob/master/engine.fhir/src/main/java/org/opencds/cqf/cql/engine/fhir/model/R4FhirModelResolver.java#L129 Or generalizing the mapping logic to support inner types here: https://github.com/DBCG/cql_engine/blob/master/engine.fhir/src/main/java/org/opencds/cqf/cql/engine/fhir/model/FhirModelResolver.java#L199 I need to...