This is the set of resources that conform to both QICore Task Rejected (http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-taskrejected) and QICore Task Rejected (http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-taskrejected).
Name Flags Card. Type Description & Constraints Filter: Bindings
Task C 0..* A task to be performedConstraints: inv-1 , tnd-1 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 contentBinding: ?? ( preferred ) : A human language. text 0..1 Narrative Text summary of the resource, for human interpretationThis profile does not constrain the narrative in regard to content, language, or traceability to data elements 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 ?! Σ 1..1 code (QI) The potential performer who claimed ownership of the task has decided not to execute it prior to performing any actionBinding: ?? ( required ) : The current status of the task. statusReason Σ 1..1 CodeableConcept left: Reason for current status; right: (QI) Reason for current statusBinding: ?? ( extensible ) businessStatus Σ 0..1 CodeableConcept E.g. "Specimen collected", "IV prepped"Binding Description: ( example ) : The domain-specific business-contextual sub-state of the task. For example: "Blood drawn", "IV inserted", "Awaiting physician signature", etc. intent Σ 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 0..1 code routine | urgent | asap | statBinding: ?? ( required ) : The task's priority. code Σ 1..1 CodeableConcept left: (QI) Task Type; right: Task TypeBinding: ?? ( preferred ) : 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 Σ 1..1 Reference (Resource )left: What task is acting on; right: (QI) What task is acting on for Σ 0..1 Reference (QICore Patient | #sd-qicore-patient-qicore-patient )left: Beneficiary of the Task; right: (QI) Beneficiary of the Task encounter Σ 0..1 Reference (QICore Encounter )Healthcare event during which this task originated executionPeriod Σ 1..1 Period left: (QI) The timing the task was rejected and the reason.; right: (QI) The time action first taken meets expectation of the rejected use case. authoredOn 0..1 dateTime Task Creation Date lastModified Σ 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 performerBinding: ?? ( preferred ) : The type(s) of task performers allowed. owner Σ 0..1 Reference (Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson )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 
implicitRules 
contained 
extension 
modifierExtension 
basedOn 
value[x] 