Stream: questionnaire
Topic: answerExpression and ValueSet expansions?
Paul Lynch (Sep 18 2020 at 14:37):
J#25960 says that answerExpression "would evaluate to a collection of Coding, integer, string, or other valid answer types." Can that include ValueSet.expansion.contains (which is almost the same as a Coding, but not quite)? I know we have answerValueSet, but if one has an expansion sitting in Questionnaire.contained, one could also use answerExpression to pull it in, and possibly filter it with FHIRPath "where" statements.
Lloyd McKenzie (Sep 18 2020 at 14:39):
That certainly wouldn't be allowed right now. You could submit a change request for us to consider allowing that
Paul Lynch (Sep 18 2020 at 14:44):
Will do. Are there any concerns about that? I am writing code for answerExpression handling Coding, and as a test I am using a FHIRPath expression which actually give it the "contains" elements from a contained ValueSet expansion. The field names match (system, code, display) so my processing code doesn't know those aren't really Codings. I think it might be useful to make that support explicit rather than accidental, unless it causes a problem.
Lloyd McKenzie (Sep 18 2020 at 14:45):
It doesn't fill me with joy, but I'm not violently opposed. Would like to have a group discussion
Paul Lynch (Sep 18 2020 at 15:00):
Brian Postlethwaite (Sep 19 2020 at 03:50):
I'm curious what the c# engine would do with that.
Brian Postlethwaite (Sep 19 2020 at 03:50):
I think I'll add support for resolve and a custom expression to return that...
Last updated: Apr 12 2022 at 19:14 UTC