Task resource example - unexpected measurement

Latest profile of Task: http://ehealth-documentation.s3-website-eu-west-1.amazonaws.com/latest/ig/StructureDefinition-ehealth-task.html

Tasks are currently only generated by the Processing Service, but can be stubbed using the test-only-create operation:

Example endpoint to the eHealth stub:
http://vendortest2.ehealth.sundhed.dk/hapi-fhir-server/fhir/$test-only-create (POST only)

Points of Interest:

ehealth-task-category

The type of Task. The example shows a "UnexpectedMeasurementResolving" task.

See the API documentation for other Task categories.

ehealth-task-responsible

A reference to the CareTeam that has received the Task

status

When a Task is created by the Processing Service, it is in status "ready". When the Task is accepted by a Practitioner, it must be changed to status "accepted" (see owner)

intent

Is set to "order" from the Processing Service

priority

This is the triaging of the Task. Depending on the rules defined a triging code is defined for the Task. In the example below the investigation found that the Observation was within the expected referenceRange, causing the triage to be coded as priority=routine
Unexpected measurements will still be Triage'd - but the Task to look into the measurement will be of TaskCategory "UnexpectedMeasurementResolving" as described above.

description

The text description of what needs to be done.

focus

A reference to the ClinicalImpression generated as a result of the automation in the Process Service

When a Monitoring Responsible Practitioner investigates the results a new ClinicalImpression is created from the Employee's solution, pointing to the on from the Processing Service. This is done in the element "previous"

owner

The Practitioner that has accepted the Task (see status)

Task example in JSON

{
    "resourceType": "Bundle",
    "type": "transaction",
    "entry": [
        {
            "fullUrl": "Task",
            "resource": {
                "resourceType": "Task",
                "meta": {
                  
                  "profile": [
                    "http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-task"
                  ]
                },
                "extension": [
                  {
                    "url": "http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-task-category",
                    "valueCodeableConcept": {
                      "coding": [
                        {
                          "system": "http://ehealth.sundhed.dk/cs/task-category",
                          "code": "UnexpectedMeasurementResolving"
                        }
                      ]
                    }
                  },
                  {
                    "url": "http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-task-responsible",
                    "valueReference": {
                      "reference": "http://vendortest2.ehealth.sundhed.dk/organization/fhir/CareTeam/60"
                    }
                  }
                ],
                "language": "da",
                "status": "ready",
                "intent": "order",
                "priority": "routine",
                "owner": {
                    "reference": "http://vendortest2.ehealth.sundhed.dk/organization/fhir/Practitioner/59"
                },
                "description": "Vurdering af indgående telemedicinsk data. Målingen er modtaget uden for måleregime.",
                "focus": {
                    "reference": "http://vendortest2.ehealth.sundhed.dk/hapi-fhir-server/fhir/ClinicalImpression/265"
                },
                "context": {
                  "reference": "http://vendortest2.ehealth.sundhed.dk/hapi-fhir-server/fhir/EpisodeOfCare/67"
                }
              },
            "request": {
                "method": "POST",
                "url": "Task"
            }
        }
    ]
  }