Patient Request for Corrections Implementation Guide
1.0.0 - STU 1 Ballot
Patient Request for Corrections Implementation Guide
1.0.0 - STU 1 Ballot
Patient Request for Corrections Implementation Guide, published by HL7 International - Patient Empowerment Workgroup. This is not an authorized publication; it is the continuous build for version 1.0.0). This version is based on the current content of https://github.com/HL7/fhir-patient-correction/ and changes regularly. See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/patient-corrections/StructureDefinition/patient-correction-task | Version: 1.0.0 | |||
| Draft as of 2023-09-11 | Computable Name: PatientCorrectionTask | |||
Represents 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.
This is the profile for the Patient Correction Task, which is used to summarize the Fulfiller process to support either a patient’s request for correction to their medical record or their logging of a disagreement to a correction denial. A Requester can query the Patient Correction Task (or request notifications) to understand the current state and history of the process for carrying out the request on the Fulfiller side. It can determine the type of process (Request for Correction or Log Disagreement), the current state of the process, timing information about the process (when did it start, when did it move through states, when did it complete), who made the original request on behalf of the Patient, and who owns the process on the Fulfiller side. This profile sets minimum expectations for the Task resource to support this workflow. It is expected to be used in conjunction with the Patient Correction Communication profile.
The following data-elements must always be present (Mandatory) definition]) or must be supported if the data is present (Must Support) definition). They are presented below in a simple human-readable explanation. Profile specific guidance is provided as well. The Formal Profile Definition below provides the formal summary, definitions, and terminology requirements. Refer to the Examples section of the guide for example resources provided in the context of an example workflow.
Each implementation of PatientCorrectionTask must provide:
id: An idstatus: status combined with businessStatus provide the state of the processbusinessStatus: status combined with businessStatus provide the state of the processintent: fixed to “order”code: indicates whether it’s a “Request Correction” or “Log Disagreement” processfor: the patient whose record is to be correctedrequestor: the person who asked for the correction on behalf of the patient in Task.for.authoredOn: date/time when the request was received on the Fulfiller sidelastModified: date/time of last update to the process.input: points to the Communication resource containing the original patient correction or log disagreement request.output: points to the Communication resource containing the resolution of the request (for example, the completed amendment report)reasonReference: if the Task represents a disagreement, points to the Task containing the original request for correction process.Usage:
Description of Profiles, Differentials, Snapshots and how the different presentations work.
This structure is derived from Task
| Name | Flags | Card. | Type | Description & Constraints |
|---|---|---|---|---|
  Task | C | 0..* | Task | A task to be performed task-reasonreference: If this is a Disagreement Task, there SHALL be a reference to the original Request for Correction Communication. task-output2: If this is a completed Request for Correction Task, there SHALL be a formal response to the request (acceptance, denial, partial acceptance/denial). |
  identifier | S | 0..* | Identifier | A business identifier for the correction process. |
| basedOn | 0..0 | |||
| partOf | 0..0 | |||
| status | SC | 1..1 | code | Current status of a Correction Request or Log Disagreement. Binding: TaskStatus (required) task-status-allowed: The status of the Task SHALL be one of the following: ready, in-progress, cancelled, completed. |
| statusReason | 0..1 | CodeableConcept | Reason for the correction request status. | |
| businessStatus | S | 0..1 | CodeableConcept | Business status of the request for correction process or the log disagreement process. Binding: Patient Correction Business Status (required) |
| intent | 1..1 | code | Indicates the actionability associated with the Task. Fixed Value: order | |
| code | SC | 1..1 | CodeableConcept | Correction Task type. Binding: Patient Correction Task Types Values Set (required) |
 for | S | 1..1 | Reference(Patient) | Patient this correction or disagreement relates to. |
| encounter | 0..0 | |||
| executionPeriod | 0..1 | Period | When the request is completed by the Fulfiller. | |
| authoredOn | S | 1..1 | dateTime | When this Task was created. |
| lastModified | S | 0..1 | dateTime | When the correction task was last modified. |
| requester | S | 0..1 | Reference(Patient | RelatedPerson) | Entity requesting the correction or logging the disagreement. |
| owner | S | 0..1 | 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 | 0..1 | CodeableConcept | Why task is needed. E.g., need record correct prior to upcoming surgery. | |
| reasonReference | C | 0..1 | Reference(Patient Correction Task) | Log Disagreement Task to point to the original Request for Correction Task. |
| note | 0..* | Annotation | Non-actionable notes about this communication. | |
| restriction | 0..0 | |||
 input | ||||
 id | 0..0 | |||
 extension | 0..0 | |||
 modifierExtension | 0..0 | |||
| type | 1..1 | CodeableConcept | Label for input Binding: Patient Correction Communication Types Value Set (required) | |
  value[x] | 1..1 | Content to use in performing the task | ||
  valueString | string | |||
 valueAttachment | Attachment | |||
 valueReference | Reference(Patient Correction Communication) | |||
| output | C | 0..* | BackboneElement | Formal Response from Fulfiller to the Correction Request or to the Disagreement to Correction Denial. |
| id | 0..0 | |||
| extension | 0..0 | |||
| modifierExtension | 0..0 | |||
| type | 1..1 | CodeableConcept | Label for output Binding: Patient Correction Output Types Value Set (required) | |
| value[x] | 1..1 | Result of output | ||
| valueString | string | |||
| valueAttachment | Attachment | |||
| valueReference | Reference(Patient Correction Communication) | |||
| Documentation for this format | ||||
| Path | Conformance | ValueSet |
| Task.status | required | TaskStatus |
| Task.businessStatus | required | PatientCorrectionBusinessStatusVS |
| Task.code | required | PatientCorrectionTaskTypesVS |
| Task.input.type | required | PatientCorrectionCommunicationTypesVS |
| Task.output.type | required | PatientCorrectionOutputTypesVS |
| Id | Grade | Path(s) | Details | Requirements |
| task-output2 | error | Task | If this is a completed Request for Correction Task, there SHALL be a formal response to the request (acceptance, denial, partial acceptance/denial). : (Task.code.coding.exists(code = 'medRecCxReq' and system = 'http://hl7.org/fhir/uv/patient-corrections/CodeSystem/PatientCorrectionTaskTypes') and Task.status = 'completed') implies Task.output.type.coding.exists(code = 'medRecCxReqResolution' and system = 'http://hl7.org/fhir/uv/patient-corrections/CodeSystem/PatientCorrectionOutputTypes') | |
| task-reasonreference | error | Task | If this is a Disagreement Task, there SHALL be a reference to the original Request for Correction Communication. : Task.code.coding.exists(code = 'medRecCxDenialDisagree' and system = 'http://hl7.org/fhir/uv/patient-corrections/CodeSystem/PatientCorrectionTaskTypes') implies Task.reasonReference.exists() | |
| task-status-allowed | error | Task.status | The status of the Task SHALL be one of the following: ready, in-progress, cancelled, completed. : $this in ('ready' | 'in-progress' | 'cancelled' | 'completed') |
| Name | Flags | Card. | Type | Description & Constraints |
|---|---|---|---|---|
| Task | C | 0..* | Task | A task to be performed task-reasonreference: If this is a Disagreement Task, there SHALL be a reference to the original Request for Correction Communication. task-output2: If this is a completed Request for Correction Task, there SHALL be a formal response to the request (acceptance, denial, partial acceptance/denial). |
| implicitRules | ?!Σ | 0..1 | uri | A set of rules under which this content was created |
| modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored |
| identifier | S | 0..* | Identifier | A business identifier for the correction process. |
| status | ?!SΣC | 1..1 | code | Current status of a Correction Request or Log Disagreement. Binding: TaskStatus (required) task-status-allowed: The status of the Task SHALL be one of the following: ready, in-progress, cancelled, completed. |
| statusReason | Σ | 0..1 | CodeableConcept | Reason for the correction request status. Binding: (unbound) (example): Codes to identify the reason for current status. These will typically be specific to a particular workflow. |
| businessStatus | SΣ | 0..1 | CodeableConcept | Business status of the request for correction process or the log disagreement process. Binding: Patient Correction Business Status (required) |
| intent | Σ | 1..1 | code | Indicates the actionability associated with the Task. Binding: TaskIntent (required): Distinguishes whether the task is a proposal, plan or full order. Fixed Value: order |
| code | SΣC | 1..1 | CodeableConcept | Correction Task type. Binding: Patient Correction Task Types Values Set (required) |
| for | SΣ | 1..1 | Reference(Patient) | Patient this correction or disagreement relates to. |
| executionPeriod | Σ | 0..1 | Period | When the request is completed by the Fulfiller. |
| authoredOn | SC | 1..1 | dateTime | When this Task was created. |
| lastModified | SΣC | 0..1 | dateTime | When the correction task was last modified. |
| requester | SΣ | 0..1 | Reference(Patient | RelatedPerson) | Entity requesting the correction or logging the disagreement. |
| owner | SΣ | 0..1 | 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 | 0..1 | CodeableConcept | Why task is needed. E.g., need record correct prior to upcoming surgery. Binding: (unbound) (example): Indicates why the task is needed. E.g. Suspended because patient admitted to hospital. | |
| reasonReference | C | 0..1 | Reference(Patient Correction Task) | Log Disagreement Task to point to the original Request for Correction Task. |
| note | 0..* | Annotation | Non-actionable notes about this communication. | |
| output | C | 0..* | BackboneElement | Formal Response from Fulfiller to the Correction Request or to the Disagreement to Correction Denial. |
| type | 1..1 | CodeableConcept | Label for output Binding: Patient Correction Output Types Value Set (required) | |
| value[x] | 1..1 | Result of output | ||
| valueString | string | |||
| valueAttachment | Attachment | |||
| valueReference | Reference(Patient Correction Communication) | |||
| Documentation for this format | ||||
| Path | Conformance | ValueSet / Code |
| Task.status | required | TaskStatus |
| Task.statusReason | example | |
| Task.businessStatus | required | PatientCorrectionBusinessStatusVS |
| Task.intent | required | Fixed Value: order |
| Task.code | required | PatientCorrectionTaskTypesVS |
| Task.reasonCode | example | |
| Task.output.type | required | PatientCorrectionOutputTypesVS |
| Id | Grade | Path(s) | Details | Requirements |
| task-output2 | error | Task | If this is a completed Request for Correction Task, there SHALL be a formal response to the request (acceptance, denial, partial acceptance/denial). : (Task.code.coding.exists(code = 'medRecCxReq' and system = 'http://hl7.org/fhir/uv/patient-corrections/CodeSystem/PatientCorrectionTaskTypes') and Task.status = 'completed') implies Task.output.type.coding.exists(code = 'medRecCxReqResolution' and system = 'http://hl7.org/fhir/uv/patient-corrections/CodeSystem/PatientCorrectionOutputTypes') | |
| task-reasonreference | error | Task | If this is a Disagreement Task, there SHALL be a reference to the original Request for Correction Communication. : Task.code.coding.exists(code = 'medRecCxDenialDisagree' and system = 'http://hl7.org/fhir/uv/patient-corrections/CodeSystem/PatientCorrectionTaskTypes') implies Task.reasonReference.exists() | |
| task-status-allowed | error | Task.status | The status of the Task SHALL be one of the following: ready, in-progress, cancelled, completed. : $this in ('ready' | 'in-progress' | 'cancelled' | 'completed') |
| Name | Flags | Card. | Type | Description & Constraints | ||||
|---|---|---|---|---|---|---|---|---|
| Task | C | 0..* | Task | A task to be performed task-reasonreference: If this is a Disagreement Task, there SHALL be a reference to the original Request for Correction Communication. task-output2: If this is a completed Request for Correction Task, there SHALL be a formal response to the request (acceptance, denial, partial acceptance/denial). | ||||
| 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.
| |||||
| 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 | A business identifier for the correction process. | ||||
| instantiatesCanonical | Σ | 0..1 | canonical(ActivityDefinition) | Formal definition of task | ||||
| instantiatesUri | Σ | 0..1 | uri | Formal definition of task | ||||
| groupIdentifier | Σ | 0..1 | Identifier | Requisition or grouper id | ||||
| status | ?!SΣC | 1..1 | code | Current status of a Correction Request or Log Disagreement. Binding: TaskStatus (required) task-status-allowed: The status of the Task SHALL be one of the following: ready, in-progress, cancelled, completed. | ||||
| statusReason | Σ | 0..1 | CodeableConcept | Reason for the correction request status. Binding: (unbound) (example): Codes to identify the reason for current status. These will typically be specific to a particular workflow. | ||||
| businessStatus | SΣ | 0..1 | CodeableConcept | Business status of the request for correction process or the log disagreement process. Binding: Patient Correction Business Status (required) | ||||
| intent | Σ | 1..1 | code | Indicates the actionability associated with the Task. Binding: TaskIntent (required): Distinguishes whether the task is a proposal, plan or full order. Fixed Value: order | ||||
| priority | 0..1 | code | routine | urgent | asap | stat Binding: RequestPriority (required): The task's priority. | |||||
| code | SΣC | 1..1 | CodeableConcept | Correction Task type. Binding: Patient Correction Task Types Values Set (required) | ||||
| description | Σ | 0..1 | string | Human-readable explanation of task | ||||
| focus | Σ | 0..1 | Reference(Resource) | What task is acting on | ||||
| for | SΣ | 1..1 | Reference(Patient) | Patient this correction or disagreement relates to. | ||||
| executionPeriod | Σ | 0..1 | Period | When the request is completed by the Fulfiller. | ||||
| authoredOn | SC | 1..1 | dateTime | When this Task was created. | ||||
| lastModified | SΣC | 0..1 | dateTime | When the correction task was last modified. | ||||
| requester | SΣ | 0..1 | Reference(Patient | RelatedPerson) | Entity requesting the correction or logging the disagreement. | ||||
| performerType | 0..* | CodeableConcept | Requested performer Binding: ProcedurePerformerRoleCodes (preferred): The type(s) of task performers allowed. | |||||
| owner | SΣ | 0..1 | 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. | ||||
| location | Σ | 0..1 | Reference(Location) | Where task occurs | ||||
| reasonCode | 0..1 | CodeableConcept | Why task is needed. E.g., need record correct prior to upcoming surgery. Binding: (unbound) (example): Indicates why the task is needed. E.g. Suspended because patient admitted to hospital. | |||||
| reasonReference | C | 0..1 | Reference(Patient Correction Task) | Log Disagreement Task to point to the original Request for Correction Task. | ||||
| insurance | 0..* | Reference(Coverage | ClaimResponse) | Associated insurance coverage | |||||
| note | 0..* | Annotation | Non-actionable notes about this communication. | |||||
| relevantHistory | 0..* | Reference(Provenance) | Key events in history of the Task | |||||
| input | 0..* | BackboneElement | Information used to perform task | |||||
| type | 1..1 | CodeableConcept | Label for input Binding: Patient Correction Communication Types Value Set (required) | |||||
| value[x] | 1..1 | Content to use in performing the task | ||||||
| valueString | string | |||||||
| valueAttachment | Attachment | |||||||
| valueReference | Reference(Patient Correction Communication) | |||||||
| output | C | 0..* | BackboneElement | Formal Response from Fulfiller to the Correction Request or to the Disagreement to Correction Denial. | ||||
| type | 1..1 | CodeableConcept | Label for output Binding: Patient Correction Output Types Value Set (required) | |||||
| value[x] | 1..1 | Result of output | ||||||
| valueString | string | |||||||
| valueAttachment | Attachment | |||||||
| valueReference | Reference(Patient Correction Communication) | |||||||
| Documentation for this format | ||||||||
| Path | Conformance | ValueSet / Code | ||||
| Task.language | preferred | CommonLanguages
| ||||
| Task.status | required | TaskStatus | ||||
| Task.statusReason | example | |||||
| Task.businessStatus | required | PatientCorrectionBusinessStatusVS | ||||
| Task.intent | required | Fixed Value: order | ||||
| Task.priority | required | RequestPriority | ||||
| Task.code | required | PatientCorrectionTaskTypesVS | ||||
| Task.performerType | preferred | ProcedurePerformerRoleCodes | ||||
| Task.reasonCode | example | |||||
| Task.input.type | required | PatientCorrectionCommunicationTypesVS | ||||
| Task.output.type | required | PatientCorrectionOutputTypesVS |
| Id | Grade | Path(s) | Details | Requirements |
| task-output2 | error | Task | If this is a completed Request for Correction Task, there SHALL be a formal response to the request (acceptance, denial, partial acceptance/denial). : (Task.code.coding.exists(code = 'medRecCxReq' and system = 'http://hl7.org/fhir/uv/patient-corrections/CodeSystem/PatientCorrectionTaskTypes') and Task.status = 'completed') implies Task.output.type.coding.exists(code = 'medRecCxReqResolution' and system = 'http://hl7.org/fhir/uv/patient-corrections/CodeSystem/PatientCorrectionOutputTypes') | |
| task-reasonreference | error | Task | If this is a Disagreement Task, there SHALL be a reference to the original Request for Correction Communication. : Task.code.coding.exists(code = 'medRecCxDenialDisagree' and system = 'http://hl7.org/fhir/uv/patient-corrections/CodeSystem/PatientCorrectionTaskTypes') implies Task.reasonReference.exists() | |
| task-status-allowed | error | Task.status | The status of the Task SHALL be one of the following: ready, in-progress, cancelled, completed. : $this in ('ready' | 'in-progress' | 'cancelled' | 'completed') |
This structure is derived from Task
Differential View
This structure is derived from Task
| Name | Flags | Card. | Type | Description & Constraints |
|---|---|---|---|---|
| Task | C | 0..* | Task | A task to be performed task-reasonreference: If this is a Disagreement Task, there SHALL be a reference to the original Request for Correction Communication. task-output2: If this is a completed Request for Correction Task, there SHALL be a formal response to the request (acceptance, denial, partial acceptance/denial). |
| identifier | S | 0..* | Identifier | A business identifier for the correction process. |
| basedOn | 0..0 | |||
| partOf | 0..0 | |||
| status | SC | 1..1 | code | Current status of a Correction Request or Log Disagreement. Binding: TaskStatus (required) task-status-allowed: The status of the Task SHALL be one of the following: ready, in-progress, cancelled, completed. |
| statusReason | 0..1 | CodeableConcept | Reason for the correction request status. | |
| businessStatus | S | 0..1 | CodeableConcept | Business status of the request for correction process or the log disagreement process. Binding: Patient Correction Business Status (required) |
| intent | 1..1 | code | Indicates the actionability associated with the Task. Fixed Value: order | |
| code | SC | 1..1 | CodeableConcept | Correction Task type. Binding: Patient Correction Task Types Values Set (required) |
| for | S | 1..1 | Reference(Patient) | Patient this correction or disagreement relates to. |
| encounter | 0..0 | |||
| executionPeriod | 0..1 | Period | When the request is completed by the Fulfiller. | |
| authoredOn | S | 1..1 | dateTime | When this Task was created. |
| lastModified | S | 0..1 | dateTime | When the correction task was last modified. |
| requester | S | 0..1 | Reference(Patient | RelatedPerson) | Entity requesting the correction or logging the disagreement. |
| owner | S | 0..1 | 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 | 0..1 | CodeableConcept | Why task is needed. E.g., need record correct prior to upcoming surgery. | |
| reasonReference | C | 0..1 | Reference(Patient Correction Task) | Log Disagreement Task to point to the original Request for Correction Task. |
| note | 0..* | Annotation | Non-actionable notes about this communication. | |
| restriction | 0..0 | |||
| input | ||||
| id | 0..0 | |||
| extension | 0..0 | |||
| modifierExtension | 0..0 | |||
| type | 1..1 | CodeableConcept | Label for input Binding: Patient Correction Communication Types Value Set (required) | |
| value[x] | 1..1 | Content to use in performing the task | ||
| valueString | string | |||
| valueAttachment | Attachment | |||
| valueReference | Reference(Patient Correction Communication) | |||
| output | C | 0..* | BackboneElement | Formal Response from Fulfiller to the Correction Request or to the Disagreement to Correction Denial. |
| id | 0..0 | |||
| extension | 0..0 | |||
| modifierExtension | 0..0 | |||
| type | 1..1 | CodeableConcept | Label for output Binding: Patient Correction Output Types Value Set (required) | |
| value[x] | 1..1 | Result of output | ||
| valueString | string | |||
| valueAttachment | Attachment | |||
| valueReference | Reference(Patient Correction Communication) | |||
| Documentation for this format | ||||
| Path | Conformance | ValueSet |
| Task.status | required | TaskStatus |
| Task.businessStatus | required | PatientCorrectionBusinessStatusVS |
| Task.code | required | PatientCorrectionTaskTypesVS |
| Task.input.type | required | PatientCorrectionCommunicationTypesVS |
| Task.output.type | required | PatientCorrectionOutputTypesVS |
| Id | Grade | Path(s) | Details | Requirements |
| task-output2 | error | Task | If this is a completed Request for Correction Task, there SHALL be a formal response to the request (acceptance, denial, partial acceptance/denial). : (Task.code.coding.exists(code = 'medRecCxReq' and system = 'http://hl7.org/fhir/uv/patient-corrections/CodeSystem/PatientCorrectionTaskTypes') and Task.status = 'completed') implies Task.output.type.coding.exists(code = 'medRecCxReqResolution' and system = 'http://hl7.org/fhir/uv/patient-corrections/CodeSystem/PatientCorrectionOutputTypes') | |
| task-reasonreference | error | Task | If this is a Disagreement Task, there SHALL be a reference to the original Request for Correction Communication. : Task.code.coding.exists(code = 'medRecCxDenialDisagree' and system = 'http://hl7.org/fhir/uv/patient-corrections/CodeSystem/PatientCorrectionTaskTypes') implies Task.reasonReference.exists() | |
| task-status-allowed | error | Task.status | The status of the Task SHALL be one of the following: ready, in-progress, cancelled, completed. : $this in ('ready' | 'in-progress' | 'cancelled' | 'completed') |
Key Elements View
| Name | Flags | Card. | Type | Description & Constraints |
|---|---|---|---|---|
| Task | C | 0..* | Task | A task to be performed task-reasonreference: If this is a Disagreement Task, there SHALL be a reference to the original Request for Correction Communication. task-output2: If this is a completed Request for Correction Task, there SHALL be a formal response to the request (acceptance, denial, partial acceptance/denial). |
| implicitRules | ?!Σ | 0..1 | uri | A set of rules under which this content was created |
| modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored |
| identifier | S | 0..* | Identifier | A business identifier for the correction process. |
| status | ?!SΣC | 1..1 | code | Current status of a Correction Request or Log Disagreement. Binding: TaskStatus (required) task-status-allowed: The status of the Task SHALL be one of the following: ready, in-progress, cancelled, completed. |
| statusReason | Σ | 0..1 | CodeableConcept | Reason for the correction request status. Binding: (unbound) (example): Codes to identify the reason for current status. These will typically be specific to a particular workflow. |
| businessStatus | SΣ | 0..1 | CodeableConcept | Business status of the request for correction process or the log disagreement process. Binding: Patient Correction Business Status (required) |
| intent | Σ | 1..1 | code | Indicates the actionability associated with the Task. Binding: TaskIntent (required): Distinguishes whether the task is a proposal, plan or full order. Fixed Value: order |
| code | SΣC | 1..1 | CodeableConcept | Correction Task type. Binding: Patient Correction Task Types Values Set (required) |
| for | SΣ | 1..1 | Reference(Patient) | Patient this correction or disagreement relates to. |
| executionPeriod | Σ | 0..1 | Period | When the request is completed by the Fulfiller. |
| authoredOn | SC | 1..1 | dateTime | When this Task was created. |
| lastModified | SΣC | 0..1 | dateTime | When the correction task was last modified. |
| requester | SΣ | 0..1 | Reference(Patient | RelatedPerson) | Entity requesting the correction or logging the disagreement. |
| owner | SΣ | 0..1 | 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 | 0..1 | CodeableConcept | Why task is needed. E.g., need record correct prior to upcoming surgery. Binding: (unbound) (example): Indicates why the task is needed. E.g. Suspended because patient admitted to hospital. | |
| reasonReference | C | 0..1 | Reference(Patient Correction Task) | Log Disagreement Task to point to the original Request for Correction Task. |
| note | 0..* | Annotation | Non-actionable notes about this communication. | |
| output | C | 0..* | BackboneElement | Formal Response from Fulfiller to the Correction Request or to the Disagreement to Correction Denial. |
| type | 1..1 | CodeableConcept | Label for output Binding: Patient Correction Output Types Value Set (required) | |
| value[x] | 1..1 | Result of output | ||
| valueString | string | |||
| valueAttachment | Attachment | |||
| valueReference | Reference(Patient Correction Communication) | |||
| Documentation for this format | ||||
| Path | Conformance | ValueSet / Code |
| Task.status | required | TaskStatus |
| Task.statusReason | example | |
| Task.businessStatus | required | PatientCorrectionBusinessStatusVS |
| Task.intent | required | Fixed Value: order |
| Task.code | required | PatientCorrectionTaskTypesVS |
| Task.reasonCode | example | |
| Task.output.type | required | PatientCorrectionOutputTypesVS |
| Id | Grade | Path(s) | Details | Requirements |
| task-output2 | error | Task | If this is a completed Request for Correction Task, there SHALL be a formal response to the request (acceptance, denial, partial acceptance/denial). : (Task.code.coding.exists(code = 'medRecCxReq' and system = 'http://hl7.org/fhir/uv/patient-corrections/CodeSystem/PatientCorrectionTaskTypes') and Task.status = 'completed') implies Task.output.type.coding.exists(code = 'medRecCxReqResolution' and system = 'http://hl7.org/fhir/uv/patient-corrections/CodeSystem/PatientCorrectionOutputTypes') | |
| task-reasonreference | error | Task | If this is a Disagreement Task, there SHALL be a reference to the original Request for Correction Communication. : Task.code.coding.exists(code = 'medRecCxDenialDisagree' and system = 'http://hl7.org/fhir/uv/patient-corrections/CodeSystem/PatientCorrectionTaskTypes') implies Task.reasonReference.exists() | |
| task-status-allowed | error | Task.status | The status of the Task SHALL be one of the following: ready, in-progress, cancelled, completed. : $this in ('ready' | 'in-progress' | 'cancelled' | 'completed') |
Snapshot View
| Name | Flags | Card. | Type | Description & Constraints | ||||
|---|---|---|---|---|---|---|---|---|
| Task | C | 0..* | Task | A task to be performed task-reasonreference: If this is a Disagreement Task, there SHALL be a reference to the original Request for Correction Communication. task-output2: If this is a completed Request for Correction Task, there SHALL be a formal response to the request (acceptance, denial, partial acceptance/denial). | ||||
| 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.
| |||||
| 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 | A business identifier for the correction process. | ||||
| instantiatesCanonical | Σ | 0..1 | canonical(ActivityDefinition) | Formal definition of task | ||||
| instantiatesUri | Σ | 0..1 | uri | Formal definition of task | ||||
| groupIdentifier | Σ | 0..1 | Identifier | Requisition or grouper id | ||||
| status | ?!SΣC | 1..1 | code | Current status of a Correction Request or Log Disagreement. Binding: TaskStatus (required) task-status-allowed: The status of the Task SHALL be one of the following: ready, in-progress, cancelled, completed. | ||||
| statusReason | Σ | 0..1 | CodeableConcept | Reason for the correction request status. Binding: (unbound) (example): Codes to identify the reason for current status. These will typically be specific to a particular workflow. | ||||
| businessStatus | SΣ | 0..1 | CodeableConcept | Business status of the request for correction process or the log disagreement process. Binding: Patient Correction Business Status (required) | ||||
| intent | Σ | 1..1 | code | Indicates the actionability associated with the Task. Binding: TaskIntent (required): Distinguishes whether the task is a proposal, plan or full order. Fixed Value: order | ||||
| priority | 0..1 | code | routine | urgent | asap | stat Binding: RequestPriority (required): The task's priority. | |||||
| code | SΣC | 1..1 | CodeableConcept | Correction Task type. Binding: Patient Correction Task Types Values Set (required) | ||||
| description | Σ | 0..1 | string | Human-readable explanation of task | ||||
| focus | Σ | 0..1 | Reference(Resource) | What task is acting on | ||||
| for | SΣ | 1..1 | Reference(Patient) | Patient this correction or disagreement relates to. | ||||
| executionPeriod | Σ | 0..1 | Period | When the request is completed by the Fulfiller. | ||||
| authoredOn | SC | 1..1 | dateTime | When this Task was created. | ||||
| lastModified | SΣC | 0..1 | dateTime | When the correction task was last modified. | ||||
| requester | SΣ | 0..1 | Reference(Patient | RelatedPerson) | Entity requesting the correction or logging the disagreement. | ||||
| performerType | 0..* | CodeableConcept | Requested performer Binding: ProcedurePerformerRoleCodes (preferred): The type(s) of task performers allowed. | |||||
| owner | SΣ | 0..1 | 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. | ||||
| location | Σ | 0..1 | Reference(Location) | Where task occurs | ||||
| reasonCode | 0..1 | CodeableConcept | Why task is needed. E.g., need record correct prior to upcoming surgery. Binding: (unbound) (example): Indicates why the task is needed. E.g. Suspended because patient admitted to hospital. | |||||
| reasonReference | C | 0..1 | Reference(Patient Correction Task) | Log Disagreement Task to point to the original Request for Correction Task. | ||||
| insurance | 0..* | Reference(Coverage | ClaimResponse) | Associated insurance coverage | |||||
| note | 0..* | Annotation | Non-actionable notes about this communication. | |||||
| relevantHistory | 0..* | Reference(Provenance) | Key events in history of the Task | |||||
| input | 0..* | BackboneElement | Information used to perform task | |||||
| type | 1..1 | CodeableConcept | Label for input Binding: Patient Correction Communication Types Value Set (required) | |||||
| value[x] | 1..1 | Content to use in performing the task | ||||||
| valueString | string | |||||||
| valueAttachment | Attachment | |||||||
| valueReference | Reference(Patient Correction Communication) | |||||||
| output | C | 0..* | BackboneElement | Formal Response from Fulfiller to the Correction Request or to the Disagreement to Correction Denial. | ||||
| type | 1..1 | CodeableConcept | Label for output Binding: Patient Correction Output Types Value Set (required) | |||||
| value[x] | 1..1 | Result of output | ||||||
| valueString | string | |||||||
| valueAttachment | Attachment | |||||||
| valueReference | Reference(Patient Correction Communication) | |||||||
| Documentation for this format | ||||||||
| Path | Conformance | ValueSet / Code | ||||
| Task.language | preferred | CommonLanguages
| ||||
| Task.status | required | TaskStatus | ||||
| Task.statusReason | example | |||||
| Task.businessStatus | required | PatientCorrectionBusinessStatusVS | ||||
| Task.intent | required | Fixed Value: order | ||||
| Task.priority | required | RequestPriority | ||||
| Task.code | required | PatientCorrectionTaskTypesVS | ||||
| Task.performerType | preferred | ProcedurePerformerRoleCodes | ||||
| Task.reasonCode | example | |||||
| Task.input.type | required | PatientCorrectionCommunicationTypesVS | ||||
| Task.output.type | required | PatientCorrectionOutputTypesVS |
| Id | Grade | Path(s) | Details | Requirements |
| task-output2 | error | Task | If this is a completed Request for Correction Task, there SHALL be a formal response to the request (acceptance, denial, partial acceptance/denial). : (Task.code.coding.exists(code = 'medRecCxReq' and system = 'http://hl7.org/fhir/uv/patient-corrections/CodeSystem/PatientCorrectionTaskTypes') and Task.status = 'completed') implies Task.output.type.coding.exists(code = 'medRecCxReqResolution' and system = 'http://hl7.org/fhir/uv/patient-corrections/CodeSystem/PatientCorrectionOutputTypes') | |
| task-reasonreference | error | Task | If this is a Disagreement Task, there SHALL be a reference to the original Request for Correction Communication. : Task.code.coding.exists(code = 'medRecCxDenialDisagree' and system = 'http://hl7.org/fhir/uv/patient-corrections/CodeSystem/PatientCorrectionTaskTypes') implies Task.reasonReference.exists() | |
| task-status-allowed | error | Task.status | The status of the Task SHALL be one of the following: ready, in-progress, cancelled, completed. : $this in ('ready' | 'in-progress' | 'cancelled' | 'completed') |
This structure is derived from Task
Other representations of profile: CSV, Excel, Schematron
IG © 2020+ HL7 International - Patient Empowerment Workgroup. Package hl7.fhir.uv.patient-corrections#1.0.0 based on FHIR 4.0.1. Generated 2023-09-11
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change