FHIR Chat · ConceptMap/$translate with product

Stream: terminology

Topic: ConceptMap/$translate with product

Michael Lawley (Jan 20 2021 at 04:41):

@Grahame Grieve while exploring expected behaviour for $translate with a ConceptMap including .product entries I found this:

curl 'http://tx.fhir.org/r4/ConceptMap/102/$translate?system=http://terminology.hl7.org/CodeSystem/v2-0487&code=URINN&_format=json'

which should exercise this part of the map:

{
  "code": "URINN",
  "target": [
    {
      "code": "446277003",
      "equivalence": "equivalent",
      "product": [
        {
          "property": "http://snomed.info/id/246380002",
          "system": "http://snomed.info/sct",
          "value": "225109005"
        },
        {
          "property": "http://snomed.info/id/3006873018",
          "system": "http://snomed.info/sct",
          "value": "25990002"
        }
      ]
    }
  ]
},

But it returns:

{
  "resourceType": "Parameters",
  "parameter": [
    {
      "name": "result",
      "valueBoolean": true
    },
    {
      "name": "match",
      "part": [
        {
          "name": "match",
          "valueCoding": {
            "system": "http://snomed.info/sct",
            "code": "446277003"
          }
        },
        {
          "name": "equivalence",
          "valueCode": "Equivalent"
        }
      ]
    },
    {
      "name": "result",
      "valueBoolean": false
    },
    {
      "name": "message",
      "valueString": "no match found"
    }
  ]
}

Note:

two (different) values for result
message of "no match found"
neither of the .product values returned.

Michael Lawley (Jan 20 2021 at 04:42):

The other concern is that .product.value is string-typed (to accommodate path, valueSet, text, etc) but the corresponding OUT field for $translate is Coding.

I have use-cases where I need to produce string and integer typed products.

Grahame Grieve (Jan 20 2021 at 23:08):

two (different) values for result
message of "no match found"
neither of the .product values returned.

Fixed next update - thanks

Grahame Grieve (Jan 20 2021 at 23:09):

The other concern

has to be discussion in committee. Make a task with your use cases. And use extensions for now

Michael Lawley (Jan 21 2021 at 09:36):

Will do.
There are other issues as well -- 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.
I'll create a task for this as well.

Michael Lawley (Jan 22 2021 at 04:50):

See (existing ticket) FHIR-28284 for the .product output issue (updated with additional detail and a simple use-case)

Michael Lawley (Jan 22 2021 at 05:03):

See FHIR-30515 for the issue relating to .dependsOn (and .comment)

Michael Lawley (Jan 22 2021 at 05:05):

@Grahame Grieve given that the main issue here is to do with the OUT Parameters, is it required to use an extension, or is it permissible (preferable?) to just include additional parts?

Grahame Grieve (Feb 04 2021 at 20:53):

you can just create new named parameters @Michael Lawley

Last updated: Apr 12 2022 at 19:14 UTC

Main menu

FHIR Chat · ConceptMap/$translate with product · terminology