Details
Description
There's no way to cater for $translate calls that don't include sufficient/any dependency parameters by, for example, echoing the .depend fields in the result.
For example, consider a ConceptMap, cm, that includes two possible target codes, A and B, for a given source code, X, with dependsOn conditions where:
X -> A dependsOn adult=true
X -> B dependsOn adult=false
The a call to ConceptMap/cm/$translate?code=X will return a Parameters that includes two matches:
X -> A and X -> B
but with no way to discover the contingency specified via the .dependsOn field
Related, the .comment field is also omitted from the $translate output. This is particularly strange given the presence of the constraint cmd-1 that requires a comment is the equivalence is narrower or inexact.
See also FHIR-28284
Attachments
Issue Links
- relates to
-
FHIR-28284 Improve modelling for ConceptMap's dependsOn and product fields
- Published
-
FHIR-28577 reverse=true semantics for ConceptMap/$translate
- Published