This is the set of resources that conform to either of the profiles AU eRequesting Task Group (http://hl7.org.au/fhir/ereq/StructureDefinition/au-erequesting-task-group) and AU eRequesting Task Group (http://hl7.org.au/fhir/ereq/StructureDefinition/au-erequesting-task-group). E.g. what you have to deal with if you get resources conforming to one of them
Name Flags Card. Type Description & Constraints Filter: Bindings
Task C 0..* A task to be performedConstraints: inv-1 meta S Σ 0..1 Meta Metadata about the resource extension 0..* Extension Additional content defined by implementations versionId Σ 0..1 id Version specific identifier lastUpdated Σ 0..1 instant When the resource version last changed source Σ 0..1 uri Identifies where the resource comes from profile Σ 0..* canonical (StructureDefinition )Profiles this resource claims to conform to security Σ 0..* Coding Security Labels applied to this resourceBinding: ?? ( extensible ) : Security Labels from the Healthcare Privacy and Security Classification System. tag Σ 1..* Coding Tags applied to this resourceBinding: ?? ( example ) : Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones". implicitRules ?! Σ 0..1 uri A set of rules under which this content was created language 0..1 code Language of the resource contentBinding: ?? ( preferred ) : A human language. 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 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 S Σ 1..1 ?? Requisition or grouper id extension 0..* Extension Additional content defined by implementations use ?! Σ 0..1 code usual | official | temp | secondary | old (If known)Binding: ?? ( required ) : Identifies the purpose for this identifier, if known . type Σ 1..1 CodeableConcept Coded identifier type for local order identifierBinding: ?? ( required ) extension 0..* Extension Additional content defined by implementations coding Σ 1..1 Coding Code defined by a terminology system text Σ 0..1 string Plain text representation of the concept system Σ 1..1 uri System identifier namespace for the organisation that assigned the order identifierExample General: http://www.acme.com/identifiers/patient value Σ 1..1 string Order identifierExample General: 123456 period Σ 0..1 Period Time period when id is/was valid for use assigner Σ 0..1 Reference (Organization )Organisation that assigned the order identifier extension 0..* Extension Additional content defined by implementations reference Σ 0..1 string Literal reference, Relative, internal or absolute URL type Σ 0..1 uri Type the reference refers to (e.g. "Patient")Binding: ?? ( extensible ) : Aa resource (or, for logical models, the URI of the logical model). identifier Σ 0..1 Identifier Logical reference, when literal reference is not known display Σ 1..1 string Name of the assigning organisation partOf Σ 0..* Reference (Task )Composite task status ?! S Σ 1..1 code draft | requested | received | accepted | +Binding: ?? ( required ) statusReason S Σ 0..1 CodeableConcept Reason for current statusBinding Description: ( example ) : Codes to identify the reason for current status. These will typically be specific to a particular workflow. businessStatus S Σ 0..1 CodeableConcept left: E.g. "Specimen collected", "IV prepped"; right: Business status of the Task e.g. BookedBinding: ?? ( extensible ) : 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 | optionBinding: ?? ( required ) : Distinguishes whether the task is a proposal, plan or full order. priority S 0..1 code routine | urgent | asap | statBinding: ?? ( required ) : The task's priority. code Σ 0..1 CodeableConcept Task TypeBinding: ?? ( 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 for S Σ 1..1 Reference (AU Core Patient | #sd-au-core-patient-au-core-patient )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 S 1..1 dateTime Task Creation Date lastModified S Σ 0..1 dateTime Task Last Modified Date requester S Σ 1..1 Reference (AU Core PractitionerRole | #sd-au-core-practitionerrole-au-core-practitionerrole )Who is asking for task to be done performerType 0..* CodeableConcept Requested performerBinding: ?? ( preferred ) : The type(s) of task performers allowed. owner S Σ 0..1 Reference (AU Core Organization | #sd-au-core-organization-au-core-organization )Responsible individual location Σ 0..1 Reference (Location )Where task occurs reasonCode 0..1 CodeableConcept Why task is neededBinding Description: ( 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 relevantHistory 0..* Reference (Provenance )Key events in history of the Task restriction 0..1 BackboneElement Constraints on fulfillment tasks 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 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 inputBinding Description: ( 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 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 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 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 outputBinding Description: ( 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 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 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
Task 
meta 
extension 
versionId 
contained 
modifierExtension 
basedOn 
value[x]