-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
QI-Core 4.1.1 CommunicationNotDone Reason Code Mapping #1153
Comments
The underlying issue is that the negation pattern relies on the "what is being negated" element having a max cardinality of 1. It's not clear whether or how the negation pattern could be generalized to multi-cardinality elements. Compounding the issue in this case is that although the profiles for Communication and CommunicationNotDone in QICore do reduce the cardinality to a max of 1, because the underlying element is still multi-cardinality the mapping does not expand correctly. In addition, the primary code path for Communication and CommunicationNotDone has been changed in QICore 5 to the single-cardinality element topic. For these reasons, we recommend not addressing this issue in the translator/mapping but rather avoiding the use of the reasonCode element directly in the negation pattern for CommunicationNotDone. We have updated the pattern here to reflect this recommendation: https://github.com/cqframework/CQL-Formatting-and-Usage-Wiki/wiki/Authoring-Patterns---QICore-v4.1.1#communication-not-done |
To summarize:
|
Regarding the QICore update, QICore 5 has addressed this issue by changing CommunicationNotDone primary code path to topic. QICore 5 is published, but movement to that is subject to overall timeline. |
Closing this issue per discussion on the 6/27/23 FHIR measure collab call. Future work to be done in cqframework/cql-execution#296 |
Similar to #1136, there is an issue in how reasonCode is getting mapped to ELM for the CommunicationNotDone datatype in QI-Core 4.1.1.
Test Measure:
BM1420-v0.0.000-FHIR4.zip
Generated ELM:
elm.txt
The text was updated successfully, but these errors were encountered: