Latest profile of Task: http://ehealth-documentation.s3-website-eu-west-1.amazonaws.com/latest/ig/StructureDefinition-ehealth-task.html
...
Example endpoint to the eHealth stub:
http://vendortest2.ehealth.sundhed.dk/hapi-fhir-server/fhir/$test-only-create
Points of Interest:
ehealth-task-category
The type of Task. The example shows a "MeasurementForAssessment" 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
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)
...