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 episodeOfCare. The focus element describes what resource the Task responsible should be acting on and can reference any resource. The for element can contain a reference to a Patient and shall be specified if the Task pertains to a Patient as subject. In case episodeOfCare references an EpisodeOfCare, it is enforced that for references the same Patient as is referenced in the EpisodeOfCare.”

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.

• Differential Table
• Key Elements Table
• Snapshot Table
• Statistics/References
• All

This structure is derived from Task

Name	Flags	Card.	Type	Description & Constraints
Task		0..*	Task	A task to be performed
Slices for extension		4..*	Extension	Extension Slice: Unordered, Open by value:url
episodeOfCare		1..1	Reference(ehealth-episodeofcare) {r}	EpisodeOfCare URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-task-episodeOfCare
taskCategory		1..1	CodeableConcept	Category 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..*	CodeableConcept	Restriction category URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-restriction-category Binding: Restriction Category (required)
groupIdentifier
assigner		0..1	Reference(ehealth-organization) {r}	Organization that issued id (may be just text)
partOf		0..*	Reference(ehealth-task) {r}	Composite task
intent	S	1..1	code	unknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option
priority	S	1..1	code	routine | urgent | asap | stat
requester		0..1	Reference(ehealth-device | ehealth-organization | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r}	Who is asking for task to be done
owner		0..1	Reference(ehealth-organization | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r}	Responsible individual
note
authorReference		0..1	Reference(ehealth-practitioner | ehealth-patient | ehealth-relatedperson)	Individual responsible for the annotation
authorString		0..1	string	Individual 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?
Documentation for this format

Name	Flags	Card.	Type	Description & Constraints
Task	C	0..*	Task	A task to be performed
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
Slices for extension		4..*	Extension	Extension Slice: Unordered, Open by value:url
episodeOfCare		1..1	Reference(ehealth-episodeofcare) {r}	EpisodeOfCare URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-task-episodeOfCare
taskCategory		1..1	CodeableConcept	Category 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..*	CodeableConcept	Restriction category URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-restriction-category Binding: Restriction Category (required)
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
partOf	Σ	0..*	Reference(ehealth-task) {r}	Composite task
status	?!Σ	1..1	code	draft | requested | received | accepted | + Binding: TaskStatus (required): The current status of the task.
intent	SΣ	1..1	code	unknown | 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	S	1..1	code	routine | urgent | asap | stat Binding: RequestPriority (required): The task's priority.
requester	Σ	0..1	Reference(ehealth-device | ehealth-organization | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r}	Who is asking for task to be done
owner	Σ	0..1	Reference(ehealth-organization | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r}	Responsible individual
relevantHistory		0..*	Reference(ehealth-provenance) {r}	Key events in history of the Task
Documentation for this format

Terminology Bindings

Path	Conformance	ValueSet
Task.status	required	TaskStatus
Task.intent	required	TaskIntent
Task.priority	required	RequestPriority

Name	Flags	Card.	Type	Description & Constraints
Task	C	0..*	Task	A task to be performed
id	Σ	0..1	id	Logical id of this artifact
meta	Σ	0..1	Meta	Metadata about the resource
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
language		0..1	code	Language of the resource content Binding: CommonLanguages (preferred): A human language. Additional Bindings Purpose AllLanguages Max Binding
text		0..1	Narrative	Text summary of the resource, for human interpretation
contained		0..*	Resource	Contained, inline Resources
Slices for extension		4..*	Extension	Extension Slice: Unordered, Open by value:url
episodeOfCare		1..1	Reference(ehealth-episodeofcare) {r}	EpisodeOfCare URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-task-episodeOfCare
taskCategory		1..1	CodeableConcept	Category 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..*	CodeableConcept	Restriction category URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-restriction-category Binding: Restriction Category (required)
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
identifier		0..*	Identifier	Task Instance Identifier
instantiatesCanonical	Σ	0..1	canonical(ActivityDefinition)	Formal definition of task
instantiatesUri	Σ	0..1	uri	Formal definition of task
basedOn	Σ	0..*	Reference(Resource)	Request fulfilled by this task
groupIdentifier	Σ	0..1	Identifier	Requisition or grouper id
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
use	?!Σ	0..1	code	usual | official | temp | secondary | old (If known) Binding: IdentifierUse (required): Identifies the purpose for this identifier, if known .
type	Σ	0..1	CodeableConcept	Description 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..1	uri	The namespace for the identifier value Example General: http://www.acme.com/identifiers/patient
value	Σ	0..1	string	The value that is unique Example General: 123456
period	Σ	0..1	Period	Time period when id is/was valid for use
assigner	Σ	0..1	Reference(ehealth-organization) {r}	Organization that issued id (may be just text)
partOf	Σ	0..*	Reference(ehealth-task) {r}	Composite task
status	?!Σ	1..1	code	draft | requested | received | accepted | + Binding: TaskStatus (required): The current status of the task.
statusReason	Σ	0..1	CodeableConcept	Reason 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..1	CodeableConcept	E.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..1	code	unknown | 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	S	1..1	code	routine | urgent | asap | stat Binding: RequestPriority (required): The task's priority.
code	Σ	0..1	CodeableConcept	Task Type Binding: TaskCode (example): Codes to identify what the task involves. These will typically be specific to a particular workflow.
description	Σ	0..1	string	Human-readable explanation of task
focus	Σ	0..1	Reference(Resource)	What task is acting on
for	Σ	0..1	Reference(Resource)	Beneficiary of the Task
encounter	Σ	0..1	Reference(Encounter)	Healthcare event during which this task originated
executionPeriod	Σ	0..1	Period	Start and end time of execution
authoredOn	C	0..1	dateTime	Task Creation Date
lastModified	ΣC	0..1	dateTime	Task Last Modified Date
requester	Σ	0..1	Reference(ehealth-device | ehealth-organization | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r}	Who is asking for task to be done
performerType		0..*	CodeableConcept	Requested performer Binding: ProcedurePerformerRoleCodes (preferred): The type(s) of task performers allowed.
owner	Σ	0..1	Reference(ehealth-organization | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r}	Responsible individual
location	Σ	0..1	Reference(Location)	Where task occurs
reasonCode		0..1	CodeableConcept	Why task is needed Binding: (unbound) (example): Indicates why the task is needed. E.g. Suspended because patient admitted to hospital.
reasonReference		0..1	Reference(Resource)	Why task is needed
insurance		0..*	Reference(Coverage | ClaimResponse)	Associated insurance coverage
note		0..*	Annotation	Comments made about the task
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
Slices for author[x]	Σ	0..1		Individual responsible for the annotation Slice: Unordered, Closed by type:$this
authorReference			Reference(Practitioner | Patient | RelatedPerson | Organization)
authorString			string
author[x]:authorReference	Σ	0..1	Reference(ehealth-practitioner | ehealth-patient | ehealth-relatedperson)	Individual responsible for the annotation
author[x]:authorString	Σ	0..1	string	Individual responsible for the annotation
time	Σ	0..1	dateTime	When the annotation was made
text	Σ	1..1	markdown	The annotation - text content (as markdown)
relevantHistory		0..*	Reference(ehealth-provenance) {r}	Key events in history of the Task
restriction		0..1	BackboneElement	Constraints on fulfillment tasks
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
repetitions		0..1	positiveInt	How many times to repeat
period		0..1	Period	When fulfillment sought
recipient		0..*	Reference(ehealth-patient | ehealth-practitioner | ehealth-relatedperson | Group | ehealth-organization) {r}	For whom is fulfillment sought?
input		0..*	BackboneElement	Information used to perform task
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type		1..1	CodeableConcept	Label 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..1		Content to use in performing the task
valueBase64Binary			base64Binary
valueBoolean			boolean
valueCanonical			canonical(Any)
valueCode			code
valueDate			date
valueDateTime			dateTime
valueDecimal			decimal
valueId			id
valueInstant			instant
valueInteger			integer
valueMarkdown			markdown
valueOid			oid
valuePositiveInt			positiveInt
valueString			string
valueTime			time
valueUnsignedInt			unsignedInt
valueUri			uri
valueUrl			url
valueUuid			uuid
valueAddress			Address
valueAge			Age
valueAnnotation			Annotation
valueAttachment			Attachment
valueCodeableConcept			CodeableConcept
valueCoding			Coding
valueContactPoint			ContactPoint
valueCount			Count
valueDistance			Distance
valueDuration			Duration
valueHumanName			HumanName
valueIdentifier			Identifier
valueMoney			Money
valuePeriod			Period
valueQuantity			Quantity
valueRange			Range
valueRatio			Ratio
valueReference			Reference(Any)
valueSampledData			SampledData
valueSignature			Signature
valueTiming			Timing
valueContactDetail			ContactDetail
valueContributor			Contributor
valueDataRequirement			DataRequirement
valueExpression			Expression
valueParameterDefinition			ParameterDefinition
valueRelatedArtifact			RelatedArtifact
valueTriggerDefinition			TriggerDefinition
valueUsageContext			UsageContext
valueDosage			Dosage
valueMeta			Meta
output		0..*	BackboneElement	Information produced as part of task
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type		1..1	CodeableConcept	Label 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..1		Result of output
valueBase64Binary			base64Binary
valueBoolean			boolean
valueCanonical			canonical(Any)
valueCode			code
valueDate			date
valueDateTime			dateTime
valueDecimal			decimal
valueId			id
valueInstant			instant
valueInteger			integer
valueMarkdown			markdown
valueOid			oid
valuePositiveInt			positiveInt
valueString			string
valueTime			time
valueUnsignedInt			unsignedInt
valueUri			uri
valueUrl			url
valueUuid			uuid
valueAddress			Address
valueAge			Age
valueAnnotation			Annotation
valueAttachment			Attachment
valueCodeableConcept			CodeableConcept
valueCoding			Coding
valueContactPoint			ContactPoint
valueCount			Count
valueDistance			Distance
valueDuration			Duration
valueHumanName			HumanName
valueIdentifier			Identifier
valueMoney			Money
valuePeriod			Period
valueQuantity			Quantity
valueRange			Range
valueRatio			Ratio
valueReference			Reference(Any)
valueSampledData			SampledData
valueSignature			Signature
valueTiming			Timing
valueContactDetail			ContactDetail
valueContributor			Contributor
valueDataRequirement			DataRequirement
valueExpression			Expression
valueParameterDefinition			ParameterDefinition
valueRelatedArtifact			RelatedArtifact
valueTriggerDefinition			TriggerDefinition
valueUsageContext			UsageContext
valueDosage			Dosage
valueMeta			Meta
Documentation for this format

Terminology Bindings

Path	Conformance	ValueSet
Task.language	preferred	CommonLanguages Additional Bindings Purpose AllLanguages Max Binding
Task.groupIdentifier.use	required	IdentifierUse
Task.groupIdentifier.type	extensible	Identifier Type Codes
Task.status	required	TaskStatus
Task.statusReason	example
Task.businessStatus	example
Task.intent	required	TaskIntent
Task.priority	required	RequestPriority
Task.code	example	TaskCode
Task.performerType	preferred	ProcedurePerformerRoleCodes
Task.reasonCode	example
Task.input.type	example
Task.output.type	example

Differential View

This structure is derived from Task

Name	Flags	Card.	Type	Description & Constraints
Task		0..*	Task	A task to be performed
Slices for extension		4..*	Extension	Extension Slice: Unordered, Open by value:url
episodeOfCare		1..1	Reference(ehealth-episodeofcare) {r}	EpisodeOfCare URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-task-episodeOfCare
taskCategory		1..1	CodeableConcept	Category 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..*	CodeableConcept	Restriction category URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-restriction-category Binding: Restriction Category (required)
groupIdentifier
assigner		0..1	Reference(ehealth-organization) {r}	Organization that issued id (may be just text)
partOf		0..*	Reference(ehealth-task) {r}	Composite task
intent	S	1..1	code	unknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option
priority	S	1..1	code	routine | urgent | asap | stat
requester		0..1	Reference(ehealth-device | ehealth-organization | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r}	Who is asking for task to be done
owner		0..1	Reference(ehealth-organization | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r}	Responsible individual
note
authorReference		0..1	Reference(ehealth-practitioner | ehealth-patient | ehealth-relatedperson)	Individual responsible for the annotation
authorString		0..1	string	Individual 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?
Documentation for this format

Key Elements View

Name	Flags	Card.	Type	Description & Constraints
Task	C	0..*	Task	A task to be performed
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
Slices for extension		4..*	Extension	Extension Slice: Unordered, Open by value:url
episodeOfCare		1..1	Reference(ehealth-episodeofcare) {r}	EpisodeOfCare URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-task-episodeOfCare
taskCategory		1..1	CodeableConcept	Category 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..*	CodeableConcept	Restriction category URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-restriction-category Binding: Restriction Category (required)
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
partOf	Σ	0..*	Reference(ehealth-task) {r}	Composite task
status	?!Σ	1..1	code	draft | requested | received | accepted | + Binding: TaskStatus (required): The current status of the task.
intent	SΣ	1..1	code	unknown | 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	S	1..1	code	routine | urgent | asap | stat Binding: RequestPriority (required): The task's priority.
requester	Σ	0..1	Reference(ehealth-device | ehealth-organization | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r}	Who is asking for task to be done
owner	Σ	0..1	Reference(ehealth-organization | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r}	Responsible individual
relevantHistory		0..*	Reference(ehealth-provenance) {r}	Key events in history of the Task
Documentation for this format

Terminology Bindings

Path	Conformance	ValueSet
Task.status	required	TaskStatus
Task.intent	required	TaskIntent
Task.priority	required	RequestPriority

Snapshot View

Name	Flags	Card.	Type	Description & Constraints
Task	C	0..*	Task	A task to be performed
id	Σ	0..1	id	Logical id of this artifact
meta	Σ	0..1	Meta	Metadata about the resource
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
language		0..1	code	Language of the resource content Binding: CommonLanguages (preferred): A human language. Additional Bindings Purpose AllLanguages Max Binding
text		0..1	Narrative	Text summary of the resource, for human interpretation
contained		0..*	Resource	Contained, inline Resources
Slices for extension		4..*	Extension	Extension Slice: Unordered, Open by value:url
episodeOfCare		1..1	Reference(ehealth-episodeofcare) {r}	EpisodeOfCare URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-task-episodeOfCare
taskCategory		1..1	CodeableConcept	Category 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..*	CodeableConcept	Restriction category URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-restriction-category Binding: Restriction Category (required)
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
identifier		0..*	Identifier	Task Instance Identifier
instantiatesCanonical	Σ	0..1	canonical(ActivityDefinition)	Formal definition of task
instantiatesUri	Σ	0..1	uri	Formal definition of task
basedOn	Σ	0..*	Reference(Resource)	Request fulfilled by this task
groupIdentifier	Σ	0..1	Identifier	Requisition or grouper id
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
use	?!Σ	0..1	code	usual | official | temp | secondary | old (If known) Binding: IdentifierUse (required): Identifies the purpose for this identifier, if known .
type	Σ	0..1	CodeableConcept	Description 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..1	uri	The namespace for the identifier value Example General: http://www.acme.com/identifiers/patient
value	Σ	0..1	string	The value that is unique Example General: 123456
period	Σ	0..1	Period	Time period when id is/was valid for use
assigner	Σ	0..1	Reference(ehealth-organization) {r}	Organization that issued id (may be just text)
partOf	Σ	0..*	Reference(ehealth-task) {r}	Composite task
status	?!Σ	1..1	code	draft | requested | received | accepted | + Binding: TaskStatus (required): The current status of the task.
statusReason	Σ	0..1	CodeableConcept	Reason 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..1	CodeableConcept	E.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..1	code	unknown | 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	S	1..1	code	routine | urgent | asap | stat Binding: RequestPriority (required): The task's priority.
code	Σ	0..1	CodeableConcept	Task Type Binding: TaskCode (example): Codes to identify what the task involves. These will typically be specific to a particular workflow.
description	Σ	0..1	string	Human-readable explanation of task
focus	Σ	0..1	Reference(Resource)	What task is acting on
for	Σ	0..1	Reference(Resource)	Beneficiary of the Task
encounter	Σ	0..1	Reference(Encounter)	Healthcare event during which this task originated
executionPeriod	Σ	0..1	Period	Start and end time of execution
authoredOn	C	0..1	dateTime	Task Creation Date
lastModified	ΣC	0..1	dateTime	Task Last Modified Date
requester	Σ	0..1	Reference(ehealth-device | ehealth-organization | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r}	Who is asking for task to be done
performerType		0..*	CodeableConcept	Requested performer Binding: ProcedurePerformerRoleCodes (preferred): The type(s) of task performers allowed.
owner	Σ	0..1	Reference(ehealth-organization | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r}	Responsible individual
location	Σ	0..1	Reference(Location)	Where task occurs
reasonCode		0..1	CodeableConcept	Why task is needed Binding: (unbound) (example): Indicates why the task is needed. E.g. Suspended because patient admitted to hospital.
reasonReference		0..1	Reference(Resource)	Why task is needed
insurance		0..*	Reference(Coverage | ClaimResponse)	Associated insurance coverage
note		0..*	Annotation	Comments made about the task
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
Slices for author[x]	Σ	0..1		Individual responsible for the annotation Slice: Unordered, Closed by type:$this
authorReference			Reference(Practitioner | Patient | RelatedPerson | Organization)
authorString			string
author[x]:authorReference	Σ	0..1	Reference(ehealth-practitioner | ehealth-patient | ehealth-relatedperson)	Individual responsible for the annotation
author[x]:authorString	Σ	0..1	string	Individual responsible for the annotation
time	Σ	0..1	dateTime	When the annotation was made
text	Σ	1..1	markdown	The annotation - text content (as markdown)
relevantHistory		0..*	Reference(ehealth-provenance) {r}	Key events in history of the Task
restriction		0..1	BackboneElement	Constraints on fulfillment tasks
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
repetitions		0..1	positiveInt	How many times to repeat
period		0..1	Period	When fulfillment sought
recipient		0..*	Reference(ehealth-patient | ehealth-practitioner | ehealth-relatedperson | Group | ehealth-organization) {r}	For whom is fulfillment sought?
input		0..*	BackboneElement	Information used to perform task
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type		1..1	CodeableConcept	Label 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..1		Content to use in performing the task
valueBase64Binary			base64Binary
valueBoolean			boolean
valueCanonical			canonical(Any)
valueCode			code
valueDate			date
valueDateTime			dateTime
valueDecimal			decimal
valueId			id
valueInstant			instant
valueInteger			integer
valueMarkdown			markdown
valueOid			oid
valuePositiveInt			positiveInt
valueString			string
valueTime			time
valueUnsignedInt			unsignedInt
valueUri			uri
valueUrl			url
valueUuid			uuid
valueAddress			Address
valueAge			Age
valueAnnotation			Annotation
valueAttachment			Attachment
valueCodeableConcept			CodeableConcept
valueCoding			Coding
valueContactPoint			ContactPoint
valueCount			Count
valueDistance			Distance
valueDuration			Duration
valueHumanName			HumanName
valueIdentifier			Identifier
valueMoney			Money
valuePeriod			Period
valueQuantity			Quantity
valueRange			Range
valueRatio			Ratio
valueReference			Reference(Any)
valueSampledData			SampledData
valueSignature			Signature
valueTiming			Timing
valueContactDetail			ContactDetail
valueContributor			Contributor
valueDataRequirement			DataRequirement
valueExpression			Expression
valueParameterDefinition			ParameterDefinition
valueRelatedArtifact			RelatedArtifact
valueTriggerDefinition			TriggerDefinition
valueUsageContext			UsageContext
valueDosage			Dosage
valueMeta			Meta
output		0..*	BackboneElement	Information produced as part of task
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type		1..1	CodeableConcept	Label 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..1		Result of output
valueBase64Binary			base64Binary
valueBoolean			boolean
valueCanonical			canonical(Any)
valueCode			code
valueDate			date
valueDateTime			dateTime
valueDecimal			decimal
valueId			id
valueInstant			instant
valueInteger			integer
valueMarkdown			markdown
valueOid			oid
valuePositiveInt			positiveInt
valueString			string
valueTime			time
valueUnsignedInt			unsignedInt
valueUri			uri
valueUrl			url
valueUuid			uuid
valueAddress			Address
valueAge			Age
valueAnnotation			Annotation
valueAttachment			Attachment
valueCodeableConcept			CodeableConcept
valueCoding			Coding
valueContactPoint			ContactPoint
valueCount			Count
valueDistance			Distance
valueDuration			Duration
valueHumanName			HumanName
valueIdentifier			Identifier
valueMoney			Money
valuePeriod			Period
valueQuantity			Quantity
valueRange			Range
valueRatio			Ratio
valueReference			Reference(Any)
valueSampledData			SampledData
valueSignature			Signature
valueTiming			Timing
valueContactDetail			ContactDetail
valueContributor			Contributor
valueDataRequirement			DataRequirement
valueExpression			Expression
valueParameterDefinition			ParameterDefinition
valueRelatedArtifact			RelatedArtifact
valueTriggerDefinition			TriggerDefinition
valueUsageContext			UsageContext
valueDosage			Dosage
valueMeta			Meta
Documentation for this format

Terminology Bindings

Path	Conformance	ValueSet
Task.language	preferred	CommonLanguages Additional Bindings Purpose AllLanguages Max Binding
Task.groupIdentifier.use	required	IdentifierUse
Task.groupIdentifier.type	extensible	Identifier Type Codes
Task.status	required	TaskStatus
Task.statusReason	example
Task.businessStatus	example
Task.intent	required	TaskIntent
Task.priority	required	RequestPriority
Task.code	example	TaskCode
Task.performerType	preferred	ProcedurePerformerRoleCodes
Task.reasonCode	example
Task.input.type	example
Task.output.type	example

This structure is derived from Task

Summary

Mandatory: 5 elements
Must-Support: 2 elements

Structures

This structure refers to these other structures:

• ehealth-organization (http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-organization)
• ehealth-task (http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-task)
• ehealth-device (http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-device)
• ehealth-patient (http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-patient)
• ehealth-practitioner (http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-practitioner)
• ehealth-relatedperson (http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-relatedperson)
• ehealth-provenance (http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-provenance)

Extensions

This structure refers to these extensions:

• http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-task-episodeOfCare
• http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-task-category
• http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-task-responsible
• http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-restriction-category