Stream: terminology
Topic: ConceptMap/$translate and the reverse flag
Michael Lawley (Sep 14 2020 at 06:01):
I've been looking at the reverse parameter to $translate again.
With the changes to the ConceptMapRelationship code system, it is less problematic, but there's still the issue that the values of match.concept when reverse=true are _source_ concepts, not _target_ concepts.
Furthermore, I believe the semantics (at least from a pragmatic perspective) around the use of reverse=true with non-trivial ConceptMaps -- those that include unmapped provisions and/or product / dependsOn clauses is quite unclear.
Indeed, the semantics around a normal (reverse=false) $translate where there are dependsOn but no (or incomplete) dependency parameters is also unspecified. This scenario might be easier to deal with if additional match.input and match.dependsOn output parameters were included.
Carol Macumber (Sep 16 2020 at 14:26):
@Carmela Couderc and @Rob Hausam , can we add this to our WGM agenda when we discuss ConceptMap?
@Michael Lawley what additional output parameters do you envision being needed?
Rob Hausam (Sep 16 2020 at 14:53):
Yes, this is very pertinent for us to discuss.
Carmela Couderc (Sep 16 2020 at 17:46):
Hi @Michael Lawley Would you please enter a JIRA ticket with ConceptMap as the artifact and Vocab as the responsible work group? This way we can evaluate this along with the other open concept map issues. Thanks.
Michael Lawley (Sep 18 2020 at 06:48):
https://jira.hl7.org/browse/FHIR-28577
Michael Lawley (Sep 18 2020 at 06:50):
Not entirely relevant to the ticket, but I've always been uncomfortable that both $lookup and $translate don't include the input concept in the output. This means that the output can only be interpreted in context of the actual request.
Last updated: Apr 12 2022 at 19:14 UTC
