FHIR Orders Exchange (FOE) / Post-Acute Orders (PAO) / (DME-Orders), published by HL7. This is not an authorized publication; it is the continuous build for version 0.2.2). This version is based on the current content of https://github.com/HL7/dme-orders/ and changes regularly. See the Directory of published versions

• Content
• Detailed Descriptions
• Mappings
• XML
• JSON
• TTL

Resource Profile: PAO Task Profile

PAO Task Resource Profile

Purpose

Usage:

• Refer to this Resource Profile: PAO MessageHeader
• Examples for this Resource Profile: Task/Home-Health and Task/MedicationRequest

Formal Views of Profile Content

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

• 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
identifier	S	1..*	Identifier	Task Instance Identifier
basedOn	S	1..*	Reference(PAO Device Request | PAO ServiceRequest | PAO MedicationRequest)	Request fulfilled by this task
status	S	1..1	code	draft | requested | received | accepted | +
statusReason	S	0..1	CodeableConcept	Reason for current status
intent	S	1..1	code	unknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option
priority	S	0..1	code	routine | urgent | asap | stat
code	S	0..1	CodeableConcept	Task Type Binding: PAO Task Code Value Set (required)
description	S	0..1	string	Human-readable explanation of task
focus		0..1	Reference(PAO Device Request | PAO ServiceRequest | PAO MedicationRequest)	What task is acting on
for	S	1..1	Reference(US Core Patient Profile)	Beneficiary of the Task
encounter	S	0..1	Reference(US Core Encounter Profile)	Healthcare event during which this task originated
authoredOn	S	0..1	dateTime	Task Creation Date
lastModified	S	0..1	dateTime	Task Last Modified Date
requester	S	1..1	Reference(US Core Practitioner Profile | US Core PractitionerRole Profile | US Core Organization Profile)	Who is asking for task to be done
owner		0..1	Reference(US Core Practitioner Profile | US Core PractitionerRole Profile | US Core Organization Profile)	Responsible individual
location	S	0..1	Reference(US Core Location Profile)	Where task occurs
insurance	S	0..*	Reference(PAO Coverage)	Associated insurance coverage
relevantHistory		0..*	Reference(US Core Provenance Profile)	Key events in history of the Task
Documentation for this format

Terminology Bindings (Differential)

Path	Conformance	ValueSet
Task.code	required	PAOxTaskCode

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
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
identifier	S	1..*	Identifier	Task Instance Identifier
basedOn	SΣ	1..*	Reference(PAO Device Request | PAO ServiceRequest | PAO MedicationRequest)	Request fulfilled by this task
status	?!SΣ	1..1	code	draft | requested | received | accepted | + Binding: TaskStatus (required): The current status of the task.
statusReason	SΣ	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.
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	0..1	code	routine | urgent | asap | stat Binding: RequestPriority (required): The task's priority.
code	SΣ	0..1	CodeableConcept	Task Type Binding: PAO Task Code Value Set (required)
description	SΣ	0..1	string	Human-readable explanation of task
focus	Σ	0..1	Reference(PAO Device Request | PAO ServiceRequest | PAO MedicationRequest)	What task is acting on
for	SΣ	1..1	Reference(US Core Patient Profile)	Beneficiary of the Task
encounter	SΣ	0..1	Reference(US Core Encounter Profile)	Healthcare event during which this task originated
authoredOn	SC	0..1	dateTime	Task Creation Date
lastModified	SΣC	0..1	dateTime	Task Last Modified Date
requester	SΣ	1..1	Reference(US Core Practitioner Profile | US Core PractitionerRole Profile | US Core Organization Profile)	Who is asking for task to be done
owner	Σ	0..1	Reference(US Core Practitioner Profile | US Core PractitionerRole Profile | US Core Organization Profile)	Responsible individual
location	SΣ	0..1	Reference(US Core Location Profile)	Where task occurs
insurance	S	0..*	Reference(PAO Coverage)	Associated insurance coverage
relevantHistory		0..*	Reference(US Core Provenance Profile)	Key events in history of the Task
Documentation for this format

Terminology Bindings

Path	Conformance	ValueSet
Task.status	required	TaskStatus
Task.statusReason	example
Task.intent	required	TaskIntent
Task.priority	required	RequestPriority
Task.code	required	PAOxTaskCode

Constraints

Id	Grade	Path(s)	Details	Requirements
dom-2	error	Task	If the resource is contained in another resource, it SHALL NOT contain nested Resources : contained.contained.empty()
dom-3	error	Task	If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource : contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4	error	Task	If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated : contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-5	error	Task	If a resource is contained in another resource, it SHALL NOT have a security label : contained.meta.security.empty()
dom-6	best practice	Task	A resource should have narrative for robust management : text.`div`.exists()
ele-1	error	**ALL** elements	All FHIR elements must have a @value or children : hasValue() or (children().count() > id.count())
ext-1	error	**ALL** extensions	Must have either extensions or value[x], not both : extension.exists() != value.exists()
inv-1	error	Task	Last modified date must be greater than or equal to authored-on date. : lastModified.exists().not() or authoredOn.exists().not() or lastModified >= authoredOn

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
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
identifier	S	1..*	Identifier	Task Instance Identifier
instantiatesCanonical	Σ	0..1	canonical(ActivityDefinition)	Formal definition of task
instantiatesUri	Σ	0..1	uri	Formal definition of task
basedOn	SΣ	1..*	Reference(PAO Device Request | PAO ServiceRequest | PAO MedicationRequest)	Request fulfilled by this task
groupIdentifier	Σ	0..1	Identifier	Requisition or grouper id
partOf	Σ	0..*	Reference(Task)	Composite task
status	?!SΣ	1..1	code	draft | requested | received | accepted | + Binding: TaskStatus (required): The current status of the task.
statusReason	SΣ	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	0..1	code	routine | urgent | asap | stat Binding: RequestPriority (required): The task's priority.
code	SΣ	0..1	CodeableConcept	Task Type Binding: PAO Task Code Value Set (required)
description	SΣ	0..1	string	Human-readable explanation of task
focus	Σ	0..1	Reference(PAO Device Request | PAO ServiceRequest | PAO MedicationRequest)	What task is acting on
for	SΣ	1..1	Reference(US Core Patient Profile)	Beneficiary of the Task
encounter	SΣ	0..1	Reference(US Core Encounter Profile)	Healthcare event during which this task originated
executionPeriod	Σ	0..1	Period	Start and end time of execution
authoredOn	SC	0..1	dateTime	Task Creation Date
lastModified	SΣC	0..1	dateTime	Task Last Modified Date
requester	SΣ	1..1	Reference(US Core Practitioner Profile | US Core PractitionerRole Profile | US Core Organization Profile)	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(US Core Practitioner Profile | US Core PractitionerRole Profile | US Core Organization Profile)	Responsible individual
location	SΣ	0..1	Reference(US Core Location Profile)	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	S	0..*	Reference(PAO Coverage)	Associated insurance coverage
note		0..*	Annotation	Comments made about the task
relevantHistory		0..*	Reference(US Core Provenance Profile)	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(Patient | Practitioner | PractitionerRole | RelatedPerson | Group | Organization)	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.status	required	TaskStatus
Task.statusReason	example
Task.businessStatus	example
Task.intent	required	TaskIntent
Task.priority	required	RequestPriority
Task.code	required	PAOxTaskCode
Task.performerType	preferred	ProcedurePerformerRoleCodes
Task.reasonCode	example
Task.input.type	example
Task.output.type	example

Constraints

Id	Grade	Path(s)	Details	Requirements
ele-1	error	**ALL** elements	All FHIR elements must have a @value or children : hasValue() or (children().count() > id.count())
ext-1	error	**ALL** extensions	Must have either extensions or value[x], not both : extension.exists() != value.exists()

This structure is derived from Task

Summary

Mandatory: 6 elements
Must-Support: 15 elements

Structures

This structure refers to these other structures:

• PAO Device Request (http://hl7.org/fhir/us/dme-orders/StructureDefinition/PAOX-devicerequest)
• PAO ServiceRequest (http://hl7.org/fhir/us/dme-orders/StructureDefinition/PAOX-servicerequest)
• PAO MedicationRequest (http://hl7.org/fhir/us/dme-orders/StructureDefinition/PAOX-medication-request)
• US Core Patient Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient)
• US Core Encounter Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-encounter)
• US Core Practitioner Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner)
• US Core PractitionerRole Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitionerrole)
• US Core Organization Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-organization)
• US Core Location Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-location)
• PAO Coverage (http://hl7.org/fhir/us/dme-orders/StructureDefinition/PAOX-coverage)
• US Core Provenance Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-provenance)

Differential View

This structure is derived from Task

Name	Flags	Card.	Type	Description & Constraints
Task		0..*	Task	A task to be performed
identifier	S	1..*	Identifier	Task Instance Identifier
basedOn	S	1..*	Reference(PAO Device Request | PAO ServiceRequest | PAO MedicationRequest)	Request fulfilled by this task
status	S	1..1	code	draft | requested | received | accepted | +
statusReason	S	0..1	CodeableConcept	Reason for current status
intent	S	1..1	code	unknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option
priority	S	0..1	code	routine | urgent | asap | stat
code	S	0..1	CodeableConcept	Task Type Binding: PAO Task Code Value Set (required)
description	S	0..1	string	Human-readable explanation of task
focus		0..1	Reference(PAO Device Request | PAO ServiceRequest | PAO MedicationRequest)	What task is acting on
for	S	1..1	Reference(US Core Patient Profile)	Beneficiary of the Task
encounter	S	0..1	Reference(US Core Encounter Profile)	Healthcare event during which this task originated
authoredOn	S	0..1	dateTime	Task Creation Date
lastModified	S	0..1	dateTime	Task Last Modified Date
requester	S	1..1	Reference(US Core Practitioner Profile | US Core PractitionerRole Profile | US Core Organization Profile)	Who is asking for task to be done
owner		0..1	Reference(US Core Practitioner Profile | US Core PractitionerRole Profile | US Core Organization Profile)	Responsible individual
location	S	0..1	Reference(US Core Location Profile)	Where task occurs
insurance	S	0..*	Reference(PAO Coverage)	Associated insurance coverage
relevantHistory		0..*	Reference(US Core Provenance Profile)	Key events in history of the Task
Documentation for this format

Terminology Bindings (Differential)

Path	Conformance	ValueSet
Task.code	required	PAOxTaskCode

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
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
identifier	S	1..*	Identifier	Task Instance Identifier
basedOn	SΣ	1..*	Reference(PAO Device Request | PAO ServiceRequest | PAO MedicationRequest)	Request fulfilled by this task
status	?!SΣ	1..1	code	draft | requested | received | accepted | + Binding: TaskStatus (required): The current status of the task.
statusReason	SΣ	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.
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	0..1	code	routine | urgent | asap | stat Binding: RequestPriority (required): The task's priority.
code	SΣ	0..1	CodeableConcept	Task Type Binding: PAO Task Code Value Set (required)
description	SΣ	0..1	string	Human-readable explanation of task
focus	Σ	0..1	Reference(PAO Device Request | PAO ServiceRequest | PAO MedicationRequest)	What task is acting on
for	SΣ	1..1	Reference(US Core Patient Profile)	Beneficiary of the Task
encounter	SΣ	0..1	Reference(US Core Encounter Profile)	Healthcare event during which this task originated
authoredOn	SC	0..1	dateTime	Task Creation Date
lastModified	SΣC	0..1	dateTime	Task Last Modified Date
requester	SΣ	1..1	Reference(US Core Practitioner Profile | US Core PractitionerRole Profile | US Core Organization Profile)	Who is asking for task to be done
owner	Σ	0..1	Reference(US Core Practitioner Profile | US Core PractitionerRole Profile | US Core Organization Profile)	Responsible individual
location	SΣ	0..1	Reference(US Core Location Profile)	Where task occurs
insurance	S	0..*	Reference(PAO Coverage)	Associated insurance coverage
relevantHistory		0..*	Reference(US Core Provenance Profile)	Key events in history of the Task
Documentation for this format

Terminology Bindings

Path	Conformance	ValueSet
Task.status	required	TaskStatus
Task.statusReason	example
Task.intent	required	TaskIntent
Task.priority	required	RequestPriority
Task.code	required	PAOxTaskCode

Constraints

Id	Grade	Path(s)	Details	Requirements
dom-2	error	Task	If the resource is contained in another resource, it SHALL NOT contain nested Resources : contained.contained.empty()
dom-3	error	Task	If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource : contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4	error	Task	If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated : contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-5	error	Task	If a resource is contained in another resource, it SHALL NOT have a security label : contained.meta.security.empty()
dom-6	best practice	Task	A resource should have narrative for robust management : text.`div`.exists()
ele-1	error	**ALL** elements	All FHIR elements must have a @value or children : hasValue() or (children().count() > id.count())
ext-1	error	**ALL** extensions	Must have either extensions or value[x], not both : extension.exists() != value.exists()
inv-1	error	Task	Last modified date must be greater than or equal to authored-on date. : lastModified.exists().not() or authoredOn.exists().not() or lastModified >= authoredOn

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
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
identifier	S	1..*	Identifier	Task Instance Identifier
instantiatesCanonical	Σ	0..1	canonical(ActivityDefinition)	Formal definition of task
instantiatesUri	Σ	0..1	uri	Formal definition of task
basedOn	SΣ	1..*	Reference(PAO Device Request | PAO ServiceRequest | PAO MedicationRequest)	Request fulfilled by this task
groupIdentifier	Σ	0..1	Identifier	Requisition or grouper id
partOf	Σ	0..*	Reference(Task)	Composite task
status	?!SΣ	1..1	code	draft | requested | received | accepted | + Binding: TaskStatus (required): The current status of the task.
statusReason	SΣ	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	0..1	code	routine | urgent | asap | stat Binding: RequestPriority (required): The task's priority.
code	SΣ	0..1	CodeableConcept	Task Type Binding: PAO Task Code Value Set (required)
description	SΣ	0..1	string	Human-readable explanation of task
focus	Σ	0..1	Reference(PAO Device Request | PAO ServiceRequest | PAO MedicationRequest)	What task is acting on
for	SΣ	1..1	Reference(US Core Patient Profile)	Beneficiary of the Task
encounter	SΣ	0..1	Reference(US Core Encounter Profile)	Healthcare event during which this task originated
executionPeriod	Σ	0..1	Period	Start and end time of execution
authoredOn	SC	0..1	dateTime	Task Creation Date
lastModified	SΣC	0..1	dateTime	Task Last Modified Date
requester	SΣ	1..1	Reference(US Core Practitioner Profile | US Core PractitionerRole Profile | US Core Organization Profile)	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(US Core Practitioner Profile | US Core PractitionerRole Profile | US Core Organization Profile)	Responsible individual
location	SΣ	0..1	Reference(US Core Location Profile)	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	S	0..*	Reference(PAO Coverage)	Associated insurance coverage
note		0..*	Annotation	Comments made about the task
relevantHistory		0..*	Reference(US Core Provenance Profile)	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(Patient | Practitioner | PractitionerRole | RelatedPerson | Group | Organization)	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.status	required	TaskStatus
Task.statusReason	example
Task.businessStatus	example
Task.intent	required	TaskIntent
Task.priority	required	RequestPriority
Task.code	required	PAOxTaskCode
Task.performerType	preferred	ProcedurePerformerRoleCodes
Task.reasonCode	example
Task.input.type	example
Task.output.type	example

Constraints

Id	Grade	Path(s)	Details	Requirements
ele-1	error	**ALL** elements	All FHIR elements must have a @value or children : hasValue() or (children().count() > id.count())
ext-1	error	**ALL** extensions	Must have either extensions or value[x], not both : extension.exists() != value.exists()

This structure is derived from Task

Summary

Mandatory: 6 elements
Must-Support: 15 elements

Structures

This structure refers to these other structures:

• PAO Device Request (http://hl7.org/fhir/us/dme-orders/StructureDefinition/PAOX-devicerequest)
• PAO ServiceRequest (http://hl7.org/fhir/us/dme-orders/StructureDefinition/PAOX-servicerequest)
• PAO MedicationRequest (http://hl7.org/fhir/us/dme-orders/StructureDefinition/PAOX-medication-request)
• US Core Patient Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient)
• US Core Encounter Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-encounter)
• US Core Practitioner Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner)
• US Core PractitionerRole Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitionerrole)
• US Core Organization Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-organization)
• US Core Location Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-location)
• PAO Coverage (http://hl7.org/fhir/us/dme-orders/StructureDefinition/PAOX-coverage)
• US Core Provenance Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-provenance)

Other representations of profile: CSV, Excel, Schematron

Notes: