FHIR Chat · Task resource and Codeable Concept for Input · implementers

Stream: implementers

Topic: Task resource and Codeable Concept for Input

Peter Bernhardt (Mar 30 2020 at 17:31):

I'm thinking about using a Task resource to submit transient patient data that will be used to perform the task. The data structure will be modeled Patient resource, but will NOT be stored and should not be assumed to exist as a physical resource on any FHIR server. Looking for help on how best to describe this in the Task.input.type property as CodeableConcept?

Jose Costa Teixeira (Mar 30 2020 at 17:34):

Can you give an example?

Peter Bernhardt (Mar 30 2020 at 17:36):

An example of what a Task might look like with this approach?

Lloyd McKenzie (Mar 30 2020 at 17:39):

Task with a contained Patient instance?

Jean Duteau (Mar 30 2020 at 17:39):

yeah, but Peter needs a code for the Task.input.type as it's mandatory and there is no examplar binding.

Lloyd McKenzie (Mar 30 2020 at 17:41):

At the moment, you define your own code system

Peter Bernhardt (Mar 30 2020 at 17:54):

So, something like this:

Peter Bernhardt (Mar 30 2020 at 17:54):

  "resourceType": "Task",
  "id": "taskExample",
  "intent": "myIntent",
  "status": "requested",
  "input": [
    {
      "type": {
        "coding": [
          {
            "system": "http://my.system",
            "code": "patient"
          }
        ]
      },
      "valuePatient": {
        "resourceType": "Patient",
        "id": "patient1",
        "name": [
          {
            "family": "Public",
            "given": [
              "John"
            ]
          }
        ],
        "gender": "male",
        "address": {
          "line": [
            "100 Main St"
          ],
          "city": "Metropolis",
          "state": "Il",
          "postalCode": "44130"
        },
        "birthDate": "1956-05-27"
      }
    }
  ]
}

Lloyd McKenzie (Mar 30 2020 at 17:57):

Yes, though you might make your code specific to the intended use of the patient

Jean Duteau (Mar 30 2020 at 18:00):

Close, but I'd put your Patient resource as a contained resource:

{
    "resourceType": "Task",
    "contained": [{
        "resourceType": "Patient",
        "id": "patient1",
        "name": [{
            "family": "Public",
            "given": [
                "John"
            ]
        }],
        "gender": "male",
        "address": {
            "line": [
                "100 Main St"
            ],
            "city": "Metropolis",
            "state": "Il",
            "postalCode": "44130"
        },
        "birthDate": "1956-05-27"
    }],
    "id": "taskExample",
    "intent": "myIntent",
    "status": "requested",
    "input": [{
        "type": {
            "coding": [{
                "system": "http://my.system",
                "code": "patient"
            }]
        },
        "valueReference": "#patient1"
    }]
}

Peter Bernhardt (Mar 30 2020 at 18:01):

Thanks!

Lloyd McKenzie (Mar 30 2020 at 18:20):

Sorry, missed that.

Sa (May 15 2020 at 11:24):

Hello,
Is there any url defined in fhir documnentation from where I can get recommended "value sets" for codeable concept for a particular resource?

Oliver Egger (May 15 2020 at 11:30):

(deleted)

Oliver Egger (May 15 2020 at 11:30):

(deleted)

Oliver Egger (May 15 2020 at 11:31):

(deleted)

Lloyd McKenzie (May 15 2020 at 14:18):

Most resource elements will have a 'binding' declared that points to a value set. In the core spec, most value sets are just examples though because it's hard to get international agreement. Some are tighter though. The binding strength will tell you whether there's an expectation to use that set of codes or not

Last updated: Apr 12 2022 at 19:14 UTC