Must support

The meaning of the presence or absence of the must support flag is described in Must support.

Extensions

No extensions have been introduced in this profile.

Usage notes

When updating an existing task resource, note can only be updated if status is being changed from 'completed' to 'failed'.

Supported interactions

Supported service interactions for this profile are defined in the following capability statements:

• For publishing systems: PCA Publisher Agent
• For subscribing systems: PCA Subscriber Agent

• 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
status	S	1..1	code	failed | completed Binding: PCA Matching Status (required)
intent	S	1..1	code	reflex-order Fixed Value: reflex-order
code	S	1..1	CodeableConcept	Task Type Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://pca.digitalhealth.gov.au/fhir/4.0/CodeSystem/pca-task-type
code		1..1	code	Symbol in syntax defined by the system Fixed Value: MATCH
focus	S	1..1	Reference(PCA Healthcare Service | PCA Practitioner Role | PCA Organization | PCA Location)	The resource that the matching status applies to
owner	S	1..1	Reference(PCA Partner Service)	The partner service reporting the matching status
note	S	0..1	Annotation	Informational message about the matching status
text	S	1..1	markdown	The annotation - text content (as markdown)
Documentation for this format

Terminology Bindings (Differential)

Path	Conformance	ValueSet	URI
Task.status	required	PcaMatchingStatus http://pca.digitalhealth.gov.au/fhir/4.0/ValueSet/pca-matching-status from this IG

Name	Flags	Card.	Type	Description & Constraints
Task	C	0..*	Task	A task to be performed inv-1: Last modified date must be greater than or equal to authored-on date.
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
status	?!SΣ	1..1	code	failed | completed Binding: PCA Matching Status (required)
intent	SΣ	1..1	code	reflex-order Binding: TaskIntent (required): Distinguishes whether the task is a proposal, plan or full order. Fixed Value: reflex-order
code	SΣ	1..1	CodeableConcept	Task Type Binding: TaskCode (example): Codes to identify what the task involves. These will typically be specific to a particular workflow. Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://pca.digitalhealth.gov.au/fhir/4.0/CodeSystem/pca-task-type
code		1..1	code	Symbol in syntax defined by the system Fixed Value: MATCH
focus	SΣ	1..1	Reference(PCA Healthcare Service | PCA Practitioner Role | PCA Organization | PCA Location)	The resource that the matching status applies to
owner	SΣ	1..1	Reference(PCA Partner Service)	The partner service reporting the matching status
note	S	0..1	Annotation	Informational message about the matching status
text	SΣ	1..1	markdown	The annotation - text content (as markdown)
Documentation for this format

Terminology Bindings

Path	Conformance	ValueSet / Code	URI
Task.status	required	PcaMatchingStatus http://pca.digitalhealth.gov.au/fhir/4.0/ValueSet/pca-matching-status from this IG
Task.intent	required	Fixed Value: reflex-order http://hl7.org/fhir/ValueSet/task-intent|4.0.1 from the FHIR Standard
Task.code	example	Pattern: MATCH http://hl7.org/fhir/ValueSet/task-code from the FHIR Standard

Name	Flags	Card.	Type	Description & Constraints
Task	C	0..*	Task	A task to be performed inv-1: Last modified date must be greater than or equal to authored-on date.
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		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
partOf	Σ	0..*	Reference(Task)	Composite task
status	?!SΣ	1..1	code	failed | completed Binding: PCA Matching Status (required)
statusReason	Σ	0..1	CodeableConcept	Reason for current status Binding Description (No ValueSet): (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 Description (No ValueSet): (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	reflex-order Binding: TaskIntent (required): Distinguishes whether the task is a proposal, plan or full order. Fixed Value: reflex-order
priority		0..1	code	routine | urgent | asap | stat Binding: RequestPriority (required): The task's priority.
code	SΣ	1..1	CodeableConcept	Task Type Binding: TaskCode (example): Codes to identify what the task involves. These will typically be specific to a particular workflow. Required Pattern: At least the following
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
system		1..1	uri	Identity of the terminology system Fixed Value: http://pca.digitalhealth.gov.au/fhir/4.0/CodeSystem/pca-task-type
version		0..1	string	Version of the system - if relevant
code		1..1	code	Symbol in syntax defined by the system Fixed Value: MATCH
display		0..1	string	Representation defined by the system
userSelected		0..1	boolean	If this coding was chosen directly by the user
text		0..1	string	Plain text representation of the concept
description	Σ	0..1	string	Human-readable explanation of task
focus	SΣ	1..1	Reference(PCA Healthcare Service | PCA Practitioner Role | PCA Organization | PCA Location)	The resource that the matching status applies to
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(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson)	Who is asking for task to be done
performerType		0..*	CodeableConcept	Requested performer Binding: ProcedurePerformerRoleCodes (preferred): The type(s) of task performers allowed.
owner	SΣ	1..1	Reference(PCA Partner Service)	The partner service reporting the matching status
location	Σ	0..1	Reference(Location)	Where task occurs
reasonCode		0..1	CodeableConcept	Why task is needed Binding Description (No ValueSet): (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	S	0..1	Annotation	Informational message about the matching status
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
author[x]	Σ	0..1		Individual responsible for the annotation
authorReference			Reference(Practitioner | Patient | RelatedPerson | Organization)
authorString			string
time	Σ	0..1	dateTime	When the annotation was made
text	SΣ	1..1	markdown	The annotation - text content (as markdown)
relevantHistory		0..*	Reference(Provenance)	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 Description (No ValueSet): (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 Description (No ValueSet): (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 / Code	URI
Task.language	preferred	CommonLanguages Additional Bindings Purpose AllLanguages Max Binding http://hl7.org/fhir/ValueSet/languages from the FHIR Standard
Task.status	required	PcaMatchingStatus http://pca.digitalhealth.gov.au/fhir/4.0/ValueSet/pca-matching-status from this IG
Task.statusReason	example
Task.businessStatus	example
Task.intent	required	Fixed Value: reflex-order http://hl7.org/fhir/ValueSet/task-intent|4.0.1 from the FHIR Standard
Task.priority	required	RequestPriority http://hl7.org/fhir/ValueSet/request-priority|4.0.1 from the FHIR Standard
Task.code	example	Pattern: MATCH http://hl7.org/fhir/ValueSet/task-code from the FHIR Standard
Task.performerType	preferred	ProcedurePerformerRoleCodes http://hl7.org/fhir/ValueSet/performer-role from the FHIR Standard
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
status	S	1..1	code	failed | completed Binding: PCA Matching Status (required)
intent	S	1..1	code	reflex-order Fixed Value: reflex-order
code	S	1..1	CodeableConcept	Task Type Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://pca.digitalhealth.gov.au/fhir/4.0/CodeSystem/pca-task-type
code		1..1	code	Symbol in syntax defined by the system Fixed Value: MATCH
focus	S	1..1	Reference(PCA Healthcare Service | PCA Practitioner Role | PCA Organization | PCA Location)	The resource that the matching status applies to
owner	S	1..1	Reference(PCA Partner Service)	The partner service reporting the matching status
note	S	0..1	Annotation	Informational message about the matching status
text	S	1..1	markdown	The annotation - text content (as markdown)
Documentation for this format

Terminology Bindings (Differential)

Path	Conformance	ValueSet	URI
Task.status	required	PcaMatchingStatus http://pca.digitalhealth.gov.au/fhir/4.0/ValueSet/pca-matching-status from this IG

Key Elements View

Name	Flags	Card.	Type	Description & Constraints
Task	C	0..*	Task	A task to be performed inv-1: Last modified date must be greater than or equal to authored-on date.
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
status	?!SΣ	1..1	code	failed | completed Binding: PCA Matching Status (required)
intent	SΣ	1..1	code	reflex-order Binding: TaskIntent (required): Distinguishes whether the task is a proposal, plan or full order. Fixed Value: reflex-order
code	SΣ	1..1	CodeableConcept	Task Type Binding: TaskCode (example): Codes to identify what the task involves. These will typically be specific to a particular workflow. Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://pca.digitalhealth.gov.au/fhir/4.0/CodeSystem/pca-task-type
code		1..1	code	Symbol in syntax defined by the system Fixed Value: MATCH
focus	SΣ	1..1	Reference(PCA Healthcare Service | PCA Practitioner Role | PCA Organization | PCA Location)	The resource that the matching status applies to
owner	SΣ	1..1	Reference(PCA Partner Service)	The partner service reporting the matching status
note	S	0..1	Annotation	Informational message about the matching status
text	SΣ	1..1	markdown	The annotation - text content (as markdown)
Documentation for this format

Terminology Bindings

Path	Conformance	ValueSet / Code	URI
Task.status	required	PcaMatchingStatus http://pca.digitalhealth.gov.au/fhir/4.0/ValueSet/pca-matching-status from this IG
Task.intent	required	Fixed Value: reflex-order http://hl7.org/fhir/ValueSet/task-intent|4.0.1 from the FHIR Standard
Task.code	example	Pattern: MATCH http://hl7.org/fhir/ValueSet/task-code from the FHIR Standard

Snapshot View

Name	Flags	Card.	Type	Description & Constraints
Task	C	0..*	Task	A task to be performed inv-1: Last modified date must be greater than or equal to authored-on date.
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		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
partOf	Σ	0..*	Reference(Task)	Composite task
status	?!SΣ	1..1	code	failed | completed Binding: PCA Matching Status (required)
statusReason	Σ	0..1	CodeableConcept	Reason for current status Binding Description (No ValueSet): (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 Description (No ValueSet): (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	reflex-order Binding: TaskIntent (required): Distinguishes whether the task is a proposal, plan or full order. Fixed Value: reflex-order
priority		0..1	code	routine | urgent | asap | stat Binding: RequestPriority (required): The task's priority.
code	SΣ	1..1	CodeableConcept	Task Type Binding: TaskCode (example): Codes to identify what the task involves. These will typically be specific to a particular workflow. Required Pattern: At least the following
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
system		1..1	uri	Identity of the terminology system Fixed Value: http://pca.digitalhealth.gov.au/fhir/4.0/CodeSystem/pca-task-type
version		0..1	string	Version of the system - if relevant
code		1..1	code	Symbol in syntax defined by the system Fixed Value: MATCH
display		0..1	string	Representation defined by the system
userSelected		0..1	boolean	If this coding was chosen directly by the user
text		0..1	string	Plain text representation of the concept
description	Σ	0..1	string	Human-readable explanation of task
focus	SΣ	1..1	Reference(PCA Healthcare Service | PCA Practitioner Role | PCA Organization | PCA Location)	The resource that the matching status applies to
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(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson)	Who is asking for task to be done
performerType		0..*	CodeableConcept	Requested performer Binding: ProcedurePerformerRoleCodes (preferred): The type(s) of task performers allowed.
owner	SΣ	1..1	Reference(PCA Partner Service)	The partner service reporting the matching status
location	Σ	0..1	Reference(Location)	Where task occurs
reasonCode		0..1	CodeableConcept	Why task is needed Binding Description (No ValueSet): (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	S	0..1	Annotation	Informational message about the matching status
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
author[x]	Σ	0..1		Individual responsible for the annotation
authorReference			Reference(Practitioner | Patient | RelatedPerson | Organization)
authorString			string
time	Σ	0..1	dateTime	When the annotation was made
text	SΣ	1..1	markdown	The annotation - text content (as markdown)
relevantHistory		0..*	Reference(Provenance)	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 Description (No ValueSet): (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 Description (No ValueSet): (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 / Code	URI
Task.language	preferred	CommonLanguages Additional Bindings Purpose AllLanguages Max Binding http://hl7.org/fhir/ValueSet/languages from the FHIR Standard
Task.status	required	PcaMatchingStatus http://pca.digitalhealth.gov.au/fhir/4.0/ValueSet/pca-matching-status from this IG
Task.statusReason	example
Task.businessStatus	example
Task.intent	required	Fixed Value: reflex-order http://hl7.org/fhir/ValueSet/task-intent|4.0.1 from the FHIR Standard
Task.priority	required	RequestPriority http://hl7.org/fhir/ValueSet/request-priority|4.0.1 from the FHIR Standard
Task.code	example	Pattern: MATCH http://hl7.org/fhir/ValueSet/task-code from the FHIR Standard
Task.performerType	preferred	ProcedurePerformerRoleCodes http://hl7.org/fhir/ValueSet/performer-role from the FHIR Standard
Task.reasonCode	example
Task.input.type	example
Task.output.type	example

This structure is derived from Task

Summary

Mandatory: 3 elements
Must-Support: 7 elements
Fixed: 1 element

Structures

This structure refers to these other structures:

• PCA Healthcare Service (http://pca.digitalhealth.gov.au/fhir/4.0/StructureDefinition/pca-healthcare-service)
• PCA Practitioner Role (http://pca.digitalhealth.gov.au/fhir/4.0/StructureDefinition/pca-practitioner-role)
• PCA Organization (http://pca.digitalhealth.gov.au/fhir/4.0/StructureDefinition/pca-organization)
• PCA Location (http://pca.digitalhealth.gov.au/fhir/4.0/StructureDefinition/pca-location)
• PCA Partner Service (http://pca.digitalhealth.gov.au/fhir/4.0/StructureDefinition/pca-partner-service)

No additional search parameters defined for this resource profile.