StructureDefinition-patient-correction-task

Sourcehl7.fhir.uv.patient-corrections#current:Patient Request for Corrections Implementation Guide (v4.0.1)
resourceTypeStructureDefinition
idpatient-correction-task
canonicalhttp://hl7.org/fhir/uv/patient-corrections/StructureDefinition/patient-correction-task
version1.0.0
statusdraft
publisherHL7 International - Patient Empowerment Workgroup
namePatientCorrectionTask
titlePatient Correction Task
date2023-08-15T13:13:15+00:00
descriptionRepresents the process of reviewing the patient’s request for correction or the patient’s request to log a disagreement to a prior request for correction decision. This Task is spawned by the Fulfiller as a result of a post of a Communication resource that indicates a new request for correction or a new logging of a disagreement.
jurisdictionsuv
fhirVersion4.0.1
kindresource
abstractfalse
sdTtypeTask
derivationconstraint
basehttp://hl7.org/fhir/StructureDefinition/Task
Usages
Name Flags Card. Type Description & Constraints doco
. . Task Task
. . . identifier S A business identifier for the correction process.
. . . basedOn .. 0
. . . partOf .. 0
. . . status S 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.
Binding: Task Status ( required )
. . . statusReason The reason for the correction request status. Codes to identify the reason for current status. These will typically be specific to a particular workflow.
. . . businessStatus S 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.
Binding: Patient Correction Business Status ( required )
. . . intent Fixed Value: order
. . . code S 1.. Code and code.text to represent patient correction, or Code and code.text to represent a disagreement.
Binding: Patient Correction Task Types Values Set ( required )
. . . for S 1.. Reference ( Patient ) 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.
. . . encounter .. 0
. . . executionPeriod ExecutionPeriod.end can be used by the Fulfiller to represent when the request is completed.
. . . authoredOn S 1.. 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.
. . . lastModified S 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.
. . . requester S Reference ( Patient | RelatedPerson ) The entity that is requesting the correction or logging the disagreement such as the patient themselves or their caregiver.
. . . owner S Reference ( 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.
. . . reasonCode Why task is needed. E.g. Need record correct prior to upcoming surgery.
. . . reasonReference C Reference (Patient Correction Task) Used on Log Disagreement Task to point to the original Request for Correction Task.
task-reasonreference: If Task.code indicates this is a Disagreement Task, this field SHALL reference the original Request for Correction Communication.
. . . note
. . . restriction .. 0
. . . input C task-input: Task.input SHALL only be populated or updated by the CorrectionRequestor.
. . . . id .. 0
. . . . extension .. 0
. . . . modifierExtension .. 0
. . . . type Label for input
Binding: Patient Correction Communication Types Value Set ( required )
. . . . value[x]
. . . . . valueString string
. . . . . valueAttachment Attachment
. . . . . valueReference Reference (Patient Correction Communication)
. . . output C Formal Response from Fulfiller to the Correction Request or to the Disagreement to Correction Denial.
task-output1: Task.output SHALL only be populated or updated by the CorrectionFulfiller.
task-output2: If Task.code indicates this is a Request for Correction Task, this field SHALL contain the formal response to the request (acceptance, denial, partial acceptance/denial).
task-output3: If Task.code indicates this is a Disagreement Task, this field SHALL contain the formal response to the disagreement and optionally a rebuttal.
. . . . id .. 0
. . . . extension .. 0
. . . . modifierExtension .. 0
. . . . type Binding: Patient Correction Output Types Value Set ( required )
. . . . value[x]
. . . . . valueString string
. . . . . valueAttachment Attachment
. . . . . valueReference Reference (Patient Correction Communication)

doco Documentation for this format

Produced 08 Sep 2023