eHealth Infrastructure
2.5.0 - release

eHealth Infrastructure - Local Development build (v2.5.0). See the Directory of published versions

Resource Profile: ehealth-task

Official URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-task Version: 2.5.0
Active as of 2023-02-09 Computable Name: ehealth-task

Introduction

A task resource describes an activity that can be performed and tracks the state of completion of that activity. It is a representation that an activity should be or has been initiated, and eventually, represents the successful or unsuccessful completion of that activity.

Scope and Usage

In scope of the eHealth Infrastructure, the Task resource is used for:

  • tracking an activity to be performed by a Practitioner, CareTeam or Organization. The entity responsible for performing the Task is identified through the extension ehealth-task-responsible.
  • coordinating which Practitioner has assigned or been assigned a Task. This is identified through owner.

Task resources are produced by the eHealth Infrastructure as reaction to measurements being submitted, measurements being submitted at odd timing or expected measurements not being submitted. Measurements in the form of Observation, QuestionnaireResponse or other resources are expected to be submitted by a Patient according to a measurement regime specified in a CarePlan and referenced CarePlan/ServiceRequest.

The context in which the Task is created is identified through context. In the eHealth Infrastructure, this is currently a reference to an EpisodeOfCare, but in future use, it could be a reference to an Encounter. The focus element describes what resource the Task responsible should be acting on and can reference any resource.

Use of Task for coordinating assessment of submitted measurement

The eHealth Infrastructure supports that automated processing rules can be defined as Library resources, attached to plans (through the complex of PlanDefinition/ActivityDefinition/Library and CarePlan/ServiceRequest) and applied to submitted measurements. This includes automated processing rules performing triaging based on comparison of submitted measurements against reference ranges specified in CarePlan/ServiceRequest.

The definition of each automated processing rule controls whether to create the following as a result of the applying the rule:

  • zero, one or more Communication resources of profile ehealth-message
  • zero, one or more Task resources of profile ehealth-task
  • zero, one or more ClinicalImpression resources of profile ehealth-clinicalimpression

A typical result of triaging, for instance, is expected to be:

  • A Communication referring to a Task - creation of this might depend on Task.priority being other than routine
  • A Task with focus set to the ClinicalImpression
  • A ClinicalImpression referring to a measurement (Observation, QuestionnaireResponse or Media)

In case no automated processing rule has been attached to the plan, the current fallback automated processing rule creates a Task that refers to a single measurement. This, however, could change.

A typical Task created by triaging is expected to have:

  • Task category is a coding that states need to assess a triaging result
  • Task ehealth-task-responsible that references the one or more CareTeam attached to the CarePlan
  • Task ehealth-restriction-category is a coding that can be used to restrict access to the task, for instance restricting a task so only CareTeam members involved in monitoring measurements can access it
  • Task priority reflecting the urgency set by the triaging rule
  • Task focus referencing the ClinicalImpression that was also created during triaging. Focus can be overridden by the automated processing rule to reference something different than the ClinicalImpression.

Use of Task for resolving missing measurement

In case the eHealth Infrastructure detects that a measurement submission is missing, it creates a Communication for the CareTeam(s) attached to the CarePlan stating that the Patient should be reminded to follow the measurement regime. It also creates a Task where:

  • Task category is a coding that states need to resolve why measurement submission is missing
  • Task ehealth-task-responsible references the one or more CareTeam attached to the CarePlan
  • Task ehealth-restriction-category is a coding that can be used to restrict access to the task, for instance restricting a task so only CareTeam members involved in monitoring measurements can access it
  • Task priority set to routine
  • Task focus references the ServiceRequest for the missing measurement

Use of Task for unexpected measurement

In case the eHealth Infrastructure detects a measurement submission at unexpected or odd time compared to the measurement regime, it creates a Task where:

  • Task category is a coding that states need to resolve unexpected measurement submission* Task ehealth-task-responsible references the one or more CareTeam attached to the CarePlan
  • Task ehealth-restriction-category is a coding that can be used to restrict access to the task, for instance restricting a task so only CareTeam members involved in monitoring measurements can access it
  • Task priority set to routine
  • Task focus references Observation, QuestionnaireResponse or Media (the measurement)

No use of Task for coordinating measuring to be performed by Patient

No Task resources are created to assist in adhering to a measurement regime.

Use of Task in coordinating activities across multiple patients

The Task extension ehealth-task-responsible enables that multiple entities (CareTeam, Practitioner, Patient, RelatedPerson) can be responsible for the Task. It is expected, for instance, that each CareTeam will provide support/monitoring of multiple patients. The Task resources for which a CareTeam is responsible can form a list sorted by priority to support triaging.

When a Task has been assigned to a particular individual (through Task owner) it is possible for the Task responsible(s) to reassign the Task. This way, CareTeam members can coordinate Task assignments (by adding Practitioner as Task owner and setting Task status) while preserving the CareTeam as fallback in case the Practitioner is unable to process the Task, for instance due to absence.

Usage:

  • Refer to this Resource Profile:

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

This structure is derived from Task

NameFlagsCard.TypeDescription & Constraintsdoco
.. Task 0..*TaskA task to be performed
... Slices for extension 4..*ExtensionExtension
Slice: Unordered, Open by value:url
... episodeOfCare 1..1Reference(ehealth-episodeofcare) {r}EpisodeOfCare
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-task-episodeOfCare
... taskCategory 1..1CodeableConceptCategory of task.
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-task-category
Binding: Task Category (required)
... restrictionCategory 1..*CodeableConceptRestriction category
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-restriction-category
Binding: Restriction Category (required)
... groupIdentifier
.... assigner 0..1Reference(ehealth-organization) {r}Organization that issued id (may be just text)
... partOf 0..*Reference(ehealth-task) {r}Composite task
... intent S1..1codeunknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option
... priority S1..1coderoutine | urgent | asap | stat
... requester 0..1Reference(ehealth-device | ehealth-organization | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r}Who is asking for task to be done
... owner 0..1Reference(ehealth-organization | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r}Responsible individual
... note
.... authorReference 0..1Reference(ehealth-practitioner | ehealth-patient | ehealth-relatedperson)Individual responsible for the annotation
.... authorString 0..1stringIndividual responsible for the annotation
... relevantHistory 0..*Reference(ehealth-provenance) {r}Key events in history of the Task
... restriction
.... recipient 0..*Reference(ehealth-patient | ehealth-practitioner | ehealth-relatedperson | Group | ehealth-organization) {r}For whom is fulfillment sought?

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraintsdoco
.. Task C0..*TaskA task to be performed
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... Slices for extension 4..*ExtensionExtension
Slice: Unordered, Open by value:url
... episodeOfCare 1..1Reference(ehealth-episodeofcare) {r}EpisodeOfCare
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-task-episodeOfCare
... taskResponsible 1..*Reference()Responsible entity
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-task-responsible
... restrictionCategory 1..*CodeableConceptRestriction category
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-restriction-category
Binding: Restriction Category (required)
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... partOf Σ0..*Reference(ehealth-task) {r}Composite task
... status ?!Σ1..1codedraft | requested | received | accepted | +
Binding: TaskStatus (required): The current status of the task.

... intent SΣ1..1codeunknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option
Binding: TaskIntent (required): Distinguishes whether the task is a proposal, plan or full order.

... priority S1..1coderoutine | urgent | asap | stat
Binding: RequestPriority (required): The task's priority.

... requester Σ0..1Reference(ehealth-device | ehealth-organization | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r}Who is asking for task to be done
... owner Σ0..1Reference(ehealth-organization | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r}Responsible individual
... relevantHistory 0..*Reference(ehealth-provenance) {r}Key events in history of the Task

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet
Task.statusrequiredTaskStatus
Task.intentrequiredTaskIntent
Task.priorityrequiredRequestPriority
NameFlagsCard.TypeDescription & Constraintsdoco
.. Task C0..*TaskA task to be performed
... id Σ0..1idLogical id of this artifact
... meta Σ0..1MetaMetadata about the resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: CommonLanguages (preferred): A human language.

Additional BindingsPurpose
AllLanguagesMax Binding
... text 0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... Slices for extension 4..*ExtensionExtension
Slice: Unordered, Open by value:url
... episodeOfCare 1..1Reference(ehealth-episodeofcare) {r}EpisodeOfCare
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-task-episodeOfCare
... taskCategory 1..1CodeableConceptCategory of task.
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-task-category
Binding: Task Category (required)
... taskResponsible 1..*Reference()Responsible entity
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-task-responsible
... restrictionCategory 1..*CodeableConceptRestriction category
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-restriction-category
Binding: Restriction Category (required)
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier 0..*IdentifierTask Instance Identifier
... instantiatesCanonical Σ0..1canonical(ActivityDefinition)Formal definition of task
... instantiatesUri Σ0..1uriFormal definition of task
... basedOn Σ0..*Reference(Resource)Request fulfilled by this task
... groupIdentifier Σ0..1IdentifierRequisition or grouper id
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... use ?!Σ0..1codeusual | official | temp | secondary | old (If known)
Binding: IdentifierUse (required): Identifies the purpose for this identifier, if known .

.... type Σ0..1CodeableConceptDescription of identifier
Binding: Identifier Type Codes (extensible): A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.

.... system Σ0..1uriThe namespace for the identifier value
Example General: http://www.acme.com/identifiers/patient
.... value Σ0..1stringThe value that is unique
Example General: 123456
.... period Σ0..1PeriodTime period when id is/was valid for use
.... assigner Σ0..1Reference(ehealth-organization) {r}Organization that issued id (may be just text)
... partOf Σ0..*Reference(ehealth-task) {r}Composite task
... status ?!Σ1..1codedraft | requested | received | accepted | +
Binding: TaskStatus (required): The current status of the task.

... statusReason Σ0..1CodeableConceptReason for current status
Binding: (unbound) (example): Codes to identify the reason for current status. These will typically be specific to a particular workflow.

... businessStatus Σ0..1CodeableConceptE.g. "Specimen collected", "IV prepped"
Binding: (unbound) (example): The domain-specific business-contextual sub-state of the task. For example: "Blood drawn", "IV inserted", "Awaiting physician signature", etc.

... intent SΣ1..1codeunknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option
Binding: TaskIntent (required): Distinguishes whether the task is a proposal, plan or full order.

... priority S1..1coderoutine | urgent | asap | stat
Binding: RequestPriority (required): The task's priority.

... code Σ0..1CodeableConceptTask Type
Binding: TaskCode (example): Codes to identify what the task involves. These will typically be specific to a particular workflow.

... description Σ0..1stringHuman-readable explanation of task
... focus Σ0..1Reference(Resource)What task is acting on
... for Σ0..1Reference(Resource)Beneficiary of the Task
... encounter Σ0..1Reference(Encounter)Healthcare event during which this task originated
... executionPeriod Σ0..1PeriodStart and end time of execution
... authoredOn C0..1dateTimeTask Creation Date
... lastModified ΣC0..1dateTimeTask Last Modified Date
... requester Σ0..1Reference(ehealth-device | ehealth-organization | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r}Who is asking for task to be done
... performerType 0..*CodeableConceptRequested performer
Binding: ProcedurePerformerRoleCodes (preferred): The type(s) of task performers allowed.


... owner Σ0..1Reference(ehealth-organization | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r}Responsible individual
... location Σ0..1Reference(Location)Where task occurs
... reasonCode 0..1CodeableConceptWhy task is needed
Binding: (unbound) (example): Indicates why the task is needed. E.g. Suspended because patient admitted to hospital.

... reasonReference 0..1Reference(Resource)Why task is needed
... insurance 0..*Reference(Coverage | ClaimResponse)Associated insurance coverage
... note 0..*AnnotationComments made about the task
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... Slices for author[x] Σ0..1Individual responsible for the annotation
Slice: Unordered, Closed by type:$this
..... authorReferenceReference(Practitioner | Patient | RelatedPerson | Organization)
..... authorStringstring
..... author[x]:authorReference Σ0..1Reference(ehealth-practitioner | ehealth-patient | ehealth-relatedperson)Individual responsible for the annotation
..... author[x]:authorString Σ0..1stringIndividual responsible for the annotation
.... time Σ0..1dateTimeWhen the annotation was made
.... text Σ1..1markdownThe annotation - text content (as markdown)
... relevantHistory 0..*Reference(ehealth-provenance) {r}Key events in history of the Task
... restriction 0..1BackboneElementConstraints on fulfillment tasks
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... repetitions 0..1positiveIntHow many times to repeat
.... period 0..1PeriodWhen fulfillment sought
.... recipient 0..*Reference(ehealth-patient | ehealth-practitioner | ehealth-relatedperson | Group | ehealth-organization) {r}For whom is fulfillment sought?
... input 0..*BackboneElementInformation used to perform task
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... type 1..1CodeableConceptLabel for the input
Binding: (unbound) (example): Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Comparison source", "Applicable consent", "Concomitent Medications", etc.

.... value[x] 1..1Content to use in performing the task
..... valueBase64Binarybase64Binary
..... valueBooleanboolean
..... valueCanonicalcanonical(Any)
..... valueCodecode
..... valueDatedate
..... valueDateTimedateTime
..... valueDecimaldecimal
..... valueIdid
..... valueInstantinstant
..... valueIntegerinteger
..... valueMarkdownmarkdown
..... valueOidoid
..... valuePositiveIntpositiveInt
..... valueStringstring
..... valueTimetime
..... valueUnsignedIntunsignedInt
..... valueUriuri
..... valueUrlurl
..... valueUuiduuid
..... valueAddressAddress
..... valueAgeAge
..... valueAnnotationAnnotation
..... valueAttachmentAttachment
..... valueCodeableConceptCodeableConcept
..... valueCodingCoding
..... valueContactPointContactPoint
..... valueCountCount
..... valueDistanceDistance
..... valueDurationDuration
..... valueHumanNameHumanName
..... valueIdentifierIdentifier
..... valueMoneyMoney
..... valuePeriodPeriod
..... valueQuantityQuantity
..... valueRangeRange
..... valueRatioRatio
..... valueReferenceReference(Any)
..... valueSampledDataSampledData
..... valueSignatureSignature
..... valueTimingTiming
..... valueContactDetailContactDetail
..... valueContributorContributor
..... valueDataRequirementDataRequirement
..... valueExpressionExpression
..... valueParameterDefinitionParameterDefinition
..... valueRelatedArtifactRelatedArtifact
..... valueTriggerDefinitionTriggerDefinition
..... valueUsageContextUsageContext
..... valueDosageDosage
..... valueMetaMeta
... output 0..*BackboneElementInformation produced as part of task
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... type 1..1CodeableConceptLabel for output
Binding: (unbound) (example): Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Identified issues", "Preliminary results", "Filler order", "Final results", etc.

.... value[x] 1..1Result of output
..... valueBase64Binarybase64Binary
..... valueBooleanboolean
..... valueCanonicalcanonical(Any)
..... valueCodecode
..... valueDatedate
..... valueDateTimedateTime
..... valueDecimaldecimal
..... valueIdid
..... valueInstantinstant
..... valueIntegerinteger
..... valueMarkdownmarkdown
..... valueOidoid
..... valuePositiveIntpositiveInt
..... valueStringstring
..... valueTimetime
..... valueUnsignedIntunsignedInt
..... valueUriuri
..... valueUrlurl
..... valueUuiduuid
..... valueAddressAddress
..... valueAgeAge
..... valueAnnotationAnnotation
..... valueAttachmentAttachment
..... valueCodeableConceptCodeableConcept
..... valueCodingCoding
..... valueContactPointContactPoint
..... valueCountCount
..... valueDistanceDistance
..... valueDurationDuration
..... valueHumanNameHumanName
..... valueIdentifierIdentifier
..... valueMoneyMoney
..... valuePeriodPeriod
..... valueQuantityQuantity
..... valueRangeRange
..... valueRatioRatio
..... valueReferenceReference(Any)
..... valueSampledDataSampledData
..... valueSignatureSignature
..... valueTimingTiming
..... valueContactDetailContactDetail
..... valueContributorContributor
..... valueDataRequirementDataRequirement
..... valueExpressionExpression
..... valueParameterDefinitionParameterDefinition
..... valueRelatedArtifactRelatedArtifact
..... valueTriggerDefinitionTriggerDefinition
..... valueUsageContextUsageContext
..... valueDosageDosage
..... valueMetaMeta

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet
Task.languagepreferredCommonLanguages
Additional Bindings Purpose
AllLanguages Max Binding
Task.groupIdentifier.userequiredIdentifierUse
Task.groupIdentifier.typeextensibleIdentifier Type Codes
Task.statusrequiredTaskStatus
Task.statusReasonexample
Task.businessStatusexample
Task.intentrequiredTaskIntent
Task.priorityrequiredRequestPriority
Task.codeexampleTaskCode
Task.performerTypepreferredProcedurePerformerRoleCodes
Task.reasonCodeexample
Task.input.typeexample
Task.output.typeexample

Differential View

This structure is derived from Task

NameFlagsCard.TypeDescription & Constraintsdoco
.. Task 0..*TaskA task to be performed
... Slices for extension 4..*ExtensionExtension
Slice: Unordered, Open by value:url
... episodeOfCare 1..1Reference(ehealth-episodeofcare) {r}EpisodeOfCare
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-task-episodeOfCare
... taskCategory 1..1CodeableConceptCategory of task.
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-task-category
Binding: Task Category (required)
... restrictionCategory 1..*CodeableConceptRestriction category
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-restriction-category
Binding: Restriction Category (required)
... groupIdentifier
.... assigner 0..1Reference(ehealth-organization) {r}Organization that issued id (may be just text)
... partOf 0..*Reference(ehealth-task) {r}Composite task
... intent S1..1codeunknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option
... priority S1..1coderoutine | urgent | asap | stat
... requester 0..1Reference(ehealth-device | ehealth-organization | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r}Who is asking for task to be done
... owner 0..1Reference(ehealth-organization | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r}Responsible individual
... note
.... authorReference 0..1Reference(ehealth-practitioner | ehealth-patient | ehealth-relatedperson)Individual responsible for the annotation
.... authorString 0..1stringIndividual responsible for the annotation
... relevantHistory 0..*Reference(ehealth-provenance) {r}Key events in history of the Task
... restriction
.... recipient 0..*Reference(ehealth-patient | ehealth-practitioner | ehealth-relatedperson | Group | ehealth-organization) {r}For whom is fulfillment sought?

doco Documentation for this format

Key Elements View

NameFlagsCard.TypeDescription & Constraintsdoco
.. Task C0..*TaskA task to be performed
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... Slices for extension 4..*ExtensionExtension
Slice: Unordered, Open by value:url
... episodeOfCare 1..1Reference(ehealth-episodeofcare) {r}EpisodeOfCare
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-task-episodeOfCare
... taskResponsible 1..*Reference()Responsible entity
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-task-responsible
... restrictionCategory 1..*CodeableConceptRestriction category
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-restriction-category
Binding: Restriction Category (required)
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... partOf Σ0..*Reference(ehealth-task) {r}Composite task
... status ?!Σ1..1codedraft | requested | received | accepted | +
Binding: TaskStatus (required): The current status of the task.

... intent SΣ1..1codeunknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option
Binding: TaskIntent (required): Distinguishes whether the task is a proposal, plan or full order.

... priority S1..1coderoutine | urgent | asap | stat
Binding: RequestPriority (required): The task's priority.

... requester Σ0..1Reference(ehealth-device | ehealth-organization | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r}Who is asking for task to be done
... owner Σ0..1Reference(ehealth-organization | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r}Responsible individual
... relevantHistory 0..*Reference(ehealth-provenance) {r}Key events in history of the Task

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet
Task.statusrequiredTaskStatus
Task.intentrequiredTaskIntent
Task.priorityrequiredRequestPriority

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. Task C0..*TaskA task to be performed
... id Σ0..1idLogical id of this artifact
... meta Σ0..1MetaMetadata about the resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: CommonLanguages (preferred): A human language.

Additional BindingsPurpose
AllLanguagesMax Binding
... text 0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... Slices for extension 4..*ExtensionExtension
Slice: Unordered, Open by value:url
... episodeOfCare 1..1Reference(ehealth-episodeofcare) {r}EpisodeOfCare
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-task-episodeOfCare
... taskCategory 1..1CodeableConceptCategory of task.
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-task-category
Binding: Task Category (required)
... taskResponsible 1..*Reference()Responsible entity
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-task-responsible
... restrictionCategory 1..*CodeableConceptRestriction category
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-restriction-category
Binding: Restriction Category (required)
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier 0..*IdentifierTask Instance Identifier
... instantiatesCanonical Σ0..1canonical(ActivityDefinition)Formal definition of task
... instantiatesUri Σ0..1uriFormal definition of task
... basedOn Σ0..*Reference(Resource)Request fulfilled by this task
... groupIdentifier Σ0..1IdentifierRequisition or grouper id
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... use ?!Σ0..1codeusual | official | temp | secondary | old (If known)
Binding: IdentifierUse (required): Identifies the purpose for this identifier, if known .

.... type Σ0..1CodeableConceptDescription of identifier
Binding: Identifier Type Codes (extensible): A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.

.... system Σ0..1uriThe namespace for the identifier value
Example General: http://www.acme.com/identifiers/patient
.... value Σ0..1stringThe value that is unique
Example General: 123456
.... period Σ0..1PeriodTime period when id is/was valid for use
.... assigner Σ0..1Reference(ehealth-organization) {r}Organization that issued id (may be just text)
... partOf Σ0..*Reference(ehealth-task) {r}Composite task
... status ?!Σ1..1codedraft | requested | received | accepted | +
Binding: TaskStatus (required): The current status of the task.

... statusReason Σ0..1CodeableConceptReason for current status
Binding: (unbound) (example): Codes to identify the reason for current status. These will typically be specific to a particular workflow.

... businessStatus Σ0..1CodeableConceptE.g. "Specimen collected", "IV prepped"
Binding: (unbound) (example): The domain-specific business-contextual sub-state of the task. For example: "Blood drawn", "IV inserted", "Awaiting physician signature", etc.

... intent SΣ1..1codeunknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option
Binding: TaskIntent (required): Distinguishes whether the task is a proposal, plan or full order.

... priority S1..1coderoutine | urgent | asap | stat
Binding: RequestPriority (required): The task's priority.

... code Σ0..1CodeableConceptTask Type
Binding: TaskCode (example): Codes to identify what the task involves. These will typically be specific to a particular workflow.

... description Σ0..1stringHuman-readable explanation of task
... focus Σ0..1Reference(Resource)What task is acting on
... for Σ0..1Reference(Resource)Beneficiary of the Task
... encounter Σ0..1Reference(Encounter)Healthcare event during which this task originated
... executionPeriod Σ0..1PeriodStart and end time of execution
... authoredOn C0..1dateTimeTask Creation Date
... lastModified ΣC0..1dateTimeTask Last Modified Date
... requester Σ0..1Reference(ehealth-device | ehealth-organization | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r}Who is asking for task to be done
... performerType 0..*CodeableConceptRequested performer
Binding: ProcedurePerformerRoleCodes (preferred): The type(s) of task performers allowed.


... owner Σ0..1Reference(ehealth-organization | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r}Responsible individual
... location Σ0..1Reference(Location)Where task occurs
... reasonCode 0..1CodeableConceptWhy task is needed
Binding: (unbound) (example): Indicates why the task is needed. E.g. Suspended because patient admitted to hospital.

... reasonReference 0..1Reference(Resource)Why task is needed
... insurance 0..*Reference(Coverage | ClaimResponse)Associated insurance coverage
... note 0..*AnnotationComments made about the task
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... Slices for author[x] Σ0..1Individual responsible for the annotation
Slice: Unordered, Closed by type:$this
..... authorReferenceReference(Practitioner | Patient | RelatedPerson | Organization)
..... authorStringstring
..... author[x]:authorReference Σ0..1Reference(ehealth-practitioner | ehealth-patient | ehealth-relatedperson)Individual responsible for the annotation
..... author[x]:authorString Σ0..1stringIndividual responsible for the annotation
.... time Σ0..1dateTimeWhen the annotation was made
.... text Σ1..1markdownThe annotation - text content (as markdown)
... relevantHistory 0..*Reference(ehealth-provenance) {r}Key events in history of the Task
... restriction 0..1BackboneElementConstraints on fulfillment tasks
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... repetitions 0..1positiveIntHow many times to repeat
.... period 0..1PeriodWhen fulfillment sought
.... recipient 0..*Reference(ehealth-patient | ehealth-practitioner | ehealth-relatedperson | Group | ehealth-organization) {r}For whom is fulfillment sought?
... input 0..*BackboneElementInformation used to perform task
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... type 1..1CodeableConceptLabel for the input
Binding: (unbound) (example): Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Comparison source", "Applicable consent", "Concomitent Medications", etc.

.... value[x] 1..1Content to use in performing the task
..... valueBase64Binarybase64Binary
..... valueBooleanboolean
..... valueCanonicalcanonical(Any)
..... valueCodecode
..... valueDatedate
..... valueDateTimedateTime
..... valueDecimaldecimal
..... valueIdid
..... valueInstantinstant
..... valueIntegerinteger
..... valueMarkdownmarkdown
..... valueOidoid
..... valuePositiveIntpositiveInt
..... valueStringstring
..... valueTimetime
..... valueUnsignedIntunsignedInt
..... valueUriuri
..... valueUrlurl
..... valueUuiduuid
..... valueAddressAddress
..... valueAgeAge
..... valueAnnotationAnnotation
..... valueAttachmentAttachment
..... valueCodeableConceptCodeableConcept
..... valueCodingCoding
..... valueContactPointContactPoint
..... valueCountCount
..... valueDistanceDistance
..... valueDurationDuration
..... valueHumanNameHumanName
..... valueIdentifierIdentifier
..... valueMoneyMoney
..... valuePeriodPeriod
..... valueQuantityQuantity
..... valueRangeRange
..... valueRatioRatio
..... valueReferenceReference(Any)
..... valueSampledDataSampledData
..... valueSignatureSignature
..... valueTimingTiming
..... valueContactDetailContactDetail
..... valueContributorContributor
..... valueDataRequirementDataRequirement
..... valueExpressionExpression
..... valueParameterDefinitionParameterDefinition
..... valueRelatedArtifactRelatedArtifact
..... valueTriggerDefinitionTriggerDefinition
..... valueUsageContextUsageContext
..... valueDosageDosage
..... valueMetaMeta
... output 0..*BackboneElementInformation produced as part of task
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... type 1..1CodeableConceptLabel for output
Binding: (unbound) (example): Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Identified issues", "Preliminary results", "Filler order", "Final results", etc.

.... value[x] 1..1Result of output
..... valueBase64Binarybase64Binary
..... valueBooleanboolean
..... valueCanonicalcanonical(Any)
..... valueCodecode
..... valueDatedate
..... valueDateTimedateTime
..... valueDecimaldecimal
..... valueIdid
..... valueInstantinstant
..... valueIntegerinteger
..... valueMarkdownmarkdown
..... valueOidoid
..... valuePositiveIntpositiveInt
..... valueStringstring
..... valueTimetime
..... valueUnsignedIntunsignedInt
..... valueUriuri
..... valueUrlurl
..... valueUuiduuid
..... valueAddressAddress
..... valueAgeAge
..... valueAnnotationAnnotation
..... valueAttachmentAttachment
..... valueCodeableConceptCodeableConcept
..... valueCodingCoding
..... valueContactPointContactPoint
..... valueCountCount
..... valueDistanceDistance
..... valueDurationDuration
..... valueHumanNameHumanName
..... valueIdentifierIdentifier
..... valueMoneyMoney
..... valuePeriodPeriod
..... valueQuantityQuantity
..... valueRangeRange
..... valueRatioRatio
..... valueReferenceReference(Any)
..... valueSampledDataSampledData
..... valueSignatureSignature
..... valueTimingTiming
..... valueContactDetailContactDetail
..... valueContributorContributor
..... valueDataRequirementDataRequirement
..... valueExpressionExpression
..... valueParameterDefinitionParameterDefinition
..... valueRelatedArtifactRelatedArtifact
..... valueTriggerDefinitionTriggerDefinition
..... valueUsageContextUsageContext
..... valueDosageDosage
..... valueMetaMeta

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet
Task.languagepreferredCommonLanguages
Additional Bindings Purpose
AllLanguages Max Binding
Task.groupIdentifier.userequiredIdentifierUse
Task.groupIdentifier.typeextensibleIdentifier Type Codes
Task.statusrequiredTaskStatus
Task.statusReasonexample
Task.businessStatusexample
Task.intentrequiredTaskIntent
Task.priorityrequiredRequestPriority
Task.codeexampleTaskCode
Task.performerTypepreferredProcedurePerformerRoleCodes
Task.reasonCodeexample
Task.input.typeexample
Task.output.typeexample

 

Other representations of profile: CSV, Excel, Schematron