Union of http://hl7.org/fhir/uv/patient-corrections/StructureDefinition/patient-correction-task and http://hl7.org/fhir/uv/patient-corrections/StructureDefinition/patient-correction-task

This is the set of resources that conform to either of the profiles Patient Correction Task (http://hl7.org/fhir/uv/patient-corrections/StructureDefinition/patient-correction-task) and Patient Correction Task (http://hl7.org/fhir/uv/patient-corrections/StructureDefinition/patient-correction-task). E.g. what you have to deal with if you get resources conforming to one of them

Structure

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Task C0..*A task to be performed
Constraints: inv-1
... meta Σ0..1MetaMetadata about the resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: ?? (preferred): A human language.
... text 0..1NarrativeText summary of the resource, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier S0..*IdentifierA business identifier for the correction process.
... instantiatesCanonical Σ0..1canonical(ActivityDefinition)Formal definition of task
... instantiatesUri Σ0..1uriFormal definition of task
... groupIdentifier Σ0..1IdentifierRequisition or grouper id
... status ?!SΣ1..1codeleft: The current status of the Correction Request or Log Disagreement process. The status, in conjunction with the business status, can be used to determine the state of the process.; right: Current status of a Correction Request or Log Disagreement.
Binding: ?? (required)
... statusReason Σ0..1CodeableConceptleft: The reason for the correction request status. Codes to identify the reason for current status. These will typically be specific to a particular workflow.; right: Reason for the correction request status.
Binding Description: (example): Codes to identify the reason for current status. These will typically be specific to a particular workflow.
... businessStatus SΣ0..1CodeableConceptleft: The business status of the request for correction process or the log disagreement process. The domain-specific business-contextual sub-state of the task. For example: Waiting on additional information from requester, waiting on additional information from fulfiller (could be a specific party on the fulfiller side), more time needed to review request, an amendment will be made to the record, an amendment has been made to the record, current record determined accurate and will not be amended, a partial amendment will be made to the record, a partial amendment has been made to the record, disagreement has been reviewed and attached to the record, disagreement has been rebutted.; right: Business status of the request for correction process or the log disagreement process.
Binding: ?? (required)
... intent Σ1..1codeleft: unknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option; right: Indicates the actionability associated with the Task.
Binding: ?? (required): Distinguishes whether the task is a proposal, plan or full order.
... priority 0..1coderoutine | urgent | asap | stat
Binding: ?? (required): The task's priority.
... code SΣ1..1CodeableConceptleft: Code and code.text to represent patient correction, or Code and code.text to represent a disagreement.; right: Correction Task type.
Binding: ?? (required)
... description Σ0..1stringHuman-readable explanation of task
... focus Σ0..1Reference(Resource)What task is acting on
... for SΣ1..1Reference(Patient)left: The patient whose record this correction references. If request received through Communication resource, must be populated with the value of Communication.subject from the original request for correction Communication resource or log disagreement Communication resource.; right: Patient this correction or disagreement relates to.
... executionPeriod Σ0..1Periodleft: ExecutionPeriod.end can be used by the Fulfiller to represent when the request is completed.; right: When the request is completed by the Fulfiller.
... authoredOn S1..1dateTimeleft: The date/time that the original request was received by the Fulfiller, kicking off the request for correction or log disagreement process. If the request was received within the payload of a Communication resource, it should match Communication.sent from the original request Communication resource.; right: When this Task was created.
... lastModified SΣ0..1dateTimeleft: Indicates the most recent modification date/time on the correction process – usually would change in conjunction with a status or businessStatus change. Useful when doing historical version searches as well. lastModified when status = completed gives the process completion date/time.; right: When the correction task was last modified.
... requester SΣ0..1Reference(Patient | RelatedPerson)left: The entity that is requesting the correction or logging the disagreement such as the patient themselves or their caregiver.; right: Entity requesting the correction or logging the disagreement.
... performerType 0..*CodeableConceptRequested performer
Binding: ?? (preferred): The type(s) of task performers allowed.
... owner SΣ0..1Reference(Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService)The entity that is responsibility for fulfilling the request. Initially, this could be populated from Communication.recipient on the Communication resource of the initial request. TheFulfiller can then refine to a specific individual, group, role, or department. For example, a medical records staff person.
... location Σ0..1Reference(Location)Where task occurs
... reasonCode 0..1CodeableConceptleft: Why task is needed. E.g. Need record correct prior to upcoming surgery.; right: Why task is needed. E.g., need record correct prior to upcoming surgery.
Binding Description: (example): Indicates why the task is needed. E.g. Suspended because patient admitted to hospital.
... reasonReference C0..1Reference(Patient Correction Task), Reference(Patient Correction Task)left: Used on Log Disagreement Task to point to the original Request for Correction Task.; right: Log Disagreement Task to point to the original Request for Correction Task.
Constraints: task-reasonreference
... insurance 0..*Reference(Coverage | ClaimResponse)Associated insurance coverage
... note 0..*Annotationleft: Comments made about the task; right: Non-actionable notes about this communication.
... relevantHistory 0..*Reference(Provenance)Key events in history of the Task
... input C0..*BackboneElementInformation used to perform task
Constraints: task-input
.... type 1..1CodeableConceptLabel for input
Binding: ?? (required)
.... value[x] 1..1Content to use in performing the task
..... valueStringstring
..... valueAttachmentAttachment
..... valueReferenceReference(Patient Correction Communication | #sd-patient-correction-communication-patient-correction-communication)
... output C0..*BackboneElementFormal Response from Fulfiller to the Correction Request or to the Disagreement to Correction Denial.
Constraints: task-output1, task-output2, task-output3
.... type 1..1CodeableConceptLabel for output
Binding: ?? (required)
.... value[x] 1..1Result of output
..... valueStringstring
..... valueAttachmentAttachment
..... valueReferenceReference(Patient Correction Communication | #sd-patient-correction-communication-patient-correction-communication)

doco Documentation for this format