$translate doesn't expose dependsOn fields

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • R4
    • Terminology Infrastructure
    • ConceptMap
    • Hide

      The dependsOn parameter is missing from the output parameters for the $translate operation.  Adding this, aligned with changes made in #FHIR-28284, also results in changes with match.product.

      Add the following output parameter:

      match.dependsOn  0..*  Definition = An element that this mapping depends on.

      match.dependsOn.property  1..1

      match.dependsOn.value  1..1 (choice of code | Coding | string | integer | boolean | dateTime | decimal | uri)

      Change the match.product output parameter

      Change definition to:  An element that is a product of this mapping.

      Cardinality of match.product is not changed.

      Sub-elements become:  (prior sub-elements have been replaced)

      match.product.property 1..1

      match.product.value 1..1 (choice of code | Coding | string | integer | boolean | dateTime | decimal | uri)

      Show
      The dependsOn parameter is missing from the output parameters for the $translate operation.  Adding this, aligned with changes made in # FHIR-28284 , also results in changes with match.product. Add the following output parameter: match.dependsOn  0..*  Definition = An element that this mapping depends on. match.dependsOn.property  1..1 match.dependsOn.value  1..1 (choice of code | Coding | string | integer | boolean | dateTime | decimal | uri) Change the match.product output parameter Change definition to:  An element that is a product of this mapping. Cardinality of match.product is not changed. Sub-elements become:  (prior sub-elements have been replaced) match.product.property 1..1 match.product.value 1..1 (choice of code | Coding | string | integer | boolean | dateTime | decimal | uri)
    • Carmela Couderc/Michael Lawley : 4-0-0
    • Enhancement
    • Non-compatible

      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

       

            Assignee:
            Marc Duteau
            Reporter:
            Michael Lawley
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: