Patient Request for Corrections Implementation Guide
1.0.0 - STU 1 Ballot International flag

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

Resource Profile: Patient Correction Task

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.

Mandatory and Must Support data elements

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:

  1. id: An id
  2. status: status combined with businessStatus provide the state of the process
  3. businessStatus: status combined with businessStatus provide the state of the process
  4. intent: fixed to “order”
  5. code: indicates whether it’s a “Request Correction” or “Log Disagreement” process
  6. for: the patient whose record is to be corrected
  7. requestor: the person who asked for the correction on behalf of the patient in Task.for.
  8. authoredOn: date/time when the request was received on the Fulfiller side
  9. lastModified: date/time of last update to the process.
  10. input: points to the Communication resource containing the original patient correction or log disagreement request.
  11. output: points to the Communication resource containing the resolution of the request (for example, the completed amendment report)
  12. reasonReference: if the Task represents a disagreement, points to the Task containing the original request for correction process.

Profile-specific implementation guidance

  • The Task is spawned by the Fulfiller as a result of receipt of a Request for a Correction or a Request to Log a Disagreement. It is expected that in most cases, these requests will be coming through a Communication resource. However, this specification does not preclude the use of Task when requests are received via alternative means such as paper forms in the mail.
  • When a request for correction or logging of a disagreement is received via a Request for Correction or Log Disagreement Communication resource posting, a Task is spawned and then several fields in the Task must be populated by copying from the Communication resource that contains the original request. In specific, code, for, requester, input, and authoredOn must be pulled from fields in the original Communication resource (see details on these fields below).
  • When the Task is posted on the Fulfiller as a result of an originating Communication resource, the Fulfiller must update the Communication resource to reference the Task in the Communication.about field.

Usage:

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

This structure is derived from Task

NameFlagsCard.TypeDescription & Constraintsdoco
.. Task C0..*TaskA 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 S0..*IdentifierA business identifier for the correction process.
... basedOn 0..0
... partOf 0..0
... statusReason 0..1CodeableConceptReason for the correction request status.
... businessStatus S0..1CodeableConceptBusiness status of the request for correction process or the log disagreement process.
Binding: Patient Correction Business Status (required)
... intent 1..1codeIndicates the actionability associated with the Task.
Fixed Value: order
... code SC1..1CodeableConceptCorrection Task type.
Binding: Patient Correction Task Types Values Set (required)
... for S1..1Reference(Patient)Patient this correction or disagreement relates to.
... encounter 0..0
... executionPeriod 0..1PeriodWhen the request is completed by the Fulfiller.
... authoredOn S1..1dateTimeWhen this Task was created.
... lastModified S0..1dateTimeWhen the correction task was last modified.
... requester S0..1Reference(Patient | RelatedPerson)Entity requesting the correction or logging the disagreement.
... owner S0..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.
... reasonCode 0..1CodeableConceptWhy task is needed. E.g., need record correct prior to upcoming surgery.
... reasonReference C0..1Reference(Patient Correction Task)Log Disagreement Task to point to the original Request for Correction Task.
... note 0..*AnnotationNon-actionable notes about this communication.
... restriction 0..0
... input
.... id 0..0
.... extension 0..0
.... modifierExtension 0..0
.... type 1..1CodeableConceptLabel for input
Binding: Patient Correction Communication Types Value Set (required)
.... value[x] 1..1Content to use in performing the task
..... valueStringstring
..... valueAttachmentAttachment
..... valueReferenceReference(Patient Correction Communication)
... output C0..*BackboneElementFormal 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..1CodeableConceptLabel for output
Binding: Patient Correction Output Types Value Set (required)
.... value[x] 1..1Result of output
..... valueStringstring
..... valueAttachmentAttachment
..... valueReferenceReference(Patient Correction Communication)

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSet
Task.statusrequiredTaskStatus
Task.businessStatusrequiredPatientCorrectionBusinessStatusVS
Task.coderequiredPatientCorrectionTaskTypesVS
Task.input.typerequiredPatientCorrectionCommunicationTypesVS
Task.output.typerequiredPatientCorrectionOutputTypesVS

Constraints

IdGradePath(s)DetailsRequirements
task-output2errorTaskIf 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-reasonreferenceerrorTaskIf 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-allowederrorTask.statusThe status of the Task SHALL be one of the following: ready, in-progress, cancelled, completed.
: $this in ('ready' | 'in-progress' | 'cancelled' | 'completed')
NameFlagsCard.TypeDescription & Constraintsdoco
.. Task C0..*TaskA 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..1uriA set of rules under which this content was created
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier S0..*IdentifierA business identifier for the correction process.
... statusReason Σ0..1CodeableConceptReason 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..1CodeableConceptBusiness status of the request for correction process or the log disagreement process.
Binding: Patient Correction Business Status (required)
... intent Σ1..1codeIndicates 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ΣC1..1CodeableConceptCorrection Task type.
Binding: Patient Correction Task Types Values Set (required)
... for SΣ1..1Reference(Patient)Patient this correction or disagreement relates to.
... executionPeriod Σ0..1PeriodWhen the request is completed by the Fulfiller.
... authoredOn SC1..1dateTimeWhen this Task was created.
... lastModified SΣC0..1dateTimeWhen the correction task was last modified.
... requester SΣ0..1Reference(Patient | RelatedPerson)Entity requesting the correction or logging the disagreement.
... 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.
... reasonCode 0..1CodeableConceptWhy 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 C0..1Reference(Patient Correction Task)Log Disagreement Task to point to the original Request for Correction Task.
... note 0..*AnnotationNon-actionable notes about this communication.
... output C0..*BackboneElementFormal Response from Fulfiller to the Correction Request or to the Disagreement to Correction Denial.
.... type 1..1CodeableConceptLabel for output
Binding: Patient Correction Output Types Value Set (required)
.... value[x] 1..1Result of output
..... valueStringstring
..... valueAttachmentAttachment
..... valueReferenceReference(Patient Correction Communication)

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet / Code
Task.statusrequiredTaskStatus
Task.statusReasonexample
Task.businessStatusrequiredPatientCorrectionBusinessStatusVS
Task.intentrequiredFixed Value: order
Task.coderequiredPatientCorrectionTaskTypesVS
Task.reasonCodeexample
Task.output.typerequiredPatientCorrectionOutputTypesVS

Constraints

IdGradePath(s)DetailsRequirements
task-output2errorTaskIf 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-reasonreferenceerrorTaskIf 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-allowederrorTask.statusThe status of the Task SHALL be one of the following: ready, in-progress, cancelled, completed.
: $this in ('ready' | 'in-progress' | 'cancelled' | 'completed')
NameFlagsCard.TypeDescription & Constraintsdoco
.. Task C0..*TaskA 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..1idLogical id of this artifact
... 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: CommonLanguages (preferred): A human language.

Additional BindingsPurpose
AllLanguagesMax Binding
... text 0..1NarrativeText summary of the resource, for human interpretation
... 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ΣC1..1codeCurrent 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..1CodeableConceptReason 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..1CodeableConceptBusiness status of the request for correction process or the log disagreement process.
Binding: Patient Correction Business Status (required)
... intent Σ1..1codeIndicates 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..1coderoutine | urgent | asap | stat
Binding: RequestPriority (required): The task's priority.

... code SΣC1..1CodeableConceptCorrection Task type.
Binding: Patient Correction Task Types Values Set (required)
... description Σ0..1stringHuman-readable explanation of task
... focus Σ0..1Reference(Resource)What task is acting on
... for SΣ1..1Reference(Patient)Patient this correction or disagreement relates to.
... executionPeriod Σ0..1PeriodWhen the request is completed by the Fulfiller.
... authoredOn SC1..1dateTimeWhen this Task was created.
... lastModified SΣC0..1dateTimeWhen the correction task was last modified.
... requester SΣ0..1Reference(Patient | RelatedPerson)Entity requesting the correction or logging the disagreement.
... performerType 0..*CodeableConceptRequested performer
Binding: ProcedurePerformerRoleCodes (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..1CodeableConceptWhy 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 C0..1Reference(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..*AnnotationNon-actionable notes about this communication.
... relevantHistory 0..*Reference(Provenance)Key events in history of the Task
... input 0..*BackboneElementInformation used to perform task
.... type 1..1CodeableConceptLabel for input
Binding: Patient Correction Communication Types Value Set (required)
.... value[x] 1..1Content to use in performing the task
..... valueStringstring
..... valueAttachmentAttachment
..... valueReferenceReference(Patient Correction Communication)
... output C0..*BackboneElementFormal Response from Fulfiller to the Correction Request or to the Disagreement to Correction Denial.
.... type 1..1CodeableConceptLabel for output
Binding: Patient Correction Output Types Value Set (required)
.... value[x] 1..1Result of output
..... valueStringstring
..... valueAttachmentAttachment
..... valueReferenceReference(Patient Correction Communication)

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet / Code
Task.languagepreferredCommonLanguages
Additional Bindings Purpose
AllLanguages Max Binding
Task.statusrequiredTaskStatus
Task.statusReasonexample
Task.businessStatusrequiredPatientCorrectionBusinessStatusVS
Task.intentrequiredFixed Value: order
Task.priorityrequiredRequestPriority
Task.coderequiredPatientCorrectionTaskTypesVS
Task.performerTypepreferredProcedurePerformerRoleCodes
Task.reasonCodeexample
Task.input.typerequiredPatientCorrectionCommunicationTypesVS
Task.output.typerequiredPatientCorrectionOutputTypesVS

Constraints

IdGradePath(s)DetailsRequirements
task-output2errorTaskIf 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-reasonreferenceerrorTaskIf 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-allowederrorTask.statusThe 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

NameFlagsCard.TypeDescription & Constraintsdoco
.. Task C0..*TaskA 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 S0..*IdentifierA business identifier for the correction process.
... basedOn 0..0
... partOf 0..0
... statusReason 0..1CodeableConceptReason for the correction request status.
... businessStatus S0..1CodeableConceptBusiness status of the request for correction process or the log disagreement process.
Binding: Patient Correction Business Status (required)
... intent 1..1codeIndicates the actionability associated with the Task.
Fixed Value: order
... code SC1..1CodeableConceptCorrection Task type.
Binding: Patient Correction Task Types Values Set (required)
... for S1..1Reference(Patient)Patient this correction or disagreement relates to.
... encounter 0..0
... executionPeriod 0..1PeriodWhen the request is completed by the Fulfiller.
... authoredOn S1..1dateTimeWhen this Task was created.
... lastModified S0..1dateTimeWhen the correction task was last modified.
... requester S0..1Reference(Patient | RelatedPerson)Entity requesting the correction or logging the disagreement.
... owner S0..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.
... reasonCode 0..1CodeableConceptWhy task is needed. E.g., need record correct prior to upcoming surgery.
... reasonReference C0..1Reference(Patient Correction Task)Log Disagreement Task to point to the original Request for Correction Task.
... note 0..*AnnotationNon-actionable notes about this communication.
... restriction 0..0
... input
.... id 0..0
.... extension 0..0
.... modifierExtension 0..0
.... type 1..1CodeableConceptLabel for input
Binding: Patient Correction Communication Types Value Set (required)
.... value[x] 1..1Content to use in performing the task
..... valueStringstring
..... valueAttachmentAttachment
..... valueReferenceReference(Patient Correction Communication)
... output C0..*BackboneElementFormal 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..1CodeableConceptLabel for output
Binding: Patient Correction Output Types Value Set (required)
.... value[x] 1..1Result of output
..... valueStringstring
..... valueAttachmentAttachment
..... valueReferenceReference(Patient Correction Communication)

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSet
Task.statusrequiredTaskStatus
Task.businessStatusrequiredPatientCorrectionBusinessStatusVS
Task.coderequiredPatientCorrectionTaskTypesVS
Task.input.typerequiredPatientCorrectionCommunicationTypesVS
Task.output.typerequiredPatientCorrectionOutputTypesVS

Constraints

IdGradePath(s)DetailsRequirements
task-output2errorTaskIf 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-reasonreferenceerrorTaskIf 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-allowederrorTask.statusThe 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

NameFlagsCard.TypeDescription & Constraintsdoco
.. Task C0..*TaskA 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..1uriA set of rules under which this content was created
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier S0..*IdentifierA business identifier for the correction process.
... statusReason Σ0..1CodeableConceptReason 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..1CodeableConceptBusiness status of the request for correction process or the log disagreement process.
Binding: Patient Correction Business Status (required)
... intent Σ1..1codeIndicates 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ΣC1..1CodeableConceptCorrection Task type.
Binding: Patient Correction Task Types Values Set (required)
... for SΣ1..1Reference(Patient)Patient this correction or disagreement relates to.
... executionPeriod Σ0..1PeriodWhen the request is completed by the Fulfiller.
... authoredOn SC1..1dateTimeWhen this Task was created.
... lastModified SΣC0..1dateTimeWhen the correction task was last modified.
... requester SΣ0..1Reference(Patient | RelatedPerson)Entity requesting the correction or logging the disagreement.
... 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.
... reasonCode 0..1CodeableConceptWhy 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 C0..1Reference(Patient Correction Task)Log Disagreement Task to point to the original Request for Correction Task.
... note 0..*AnnotationNon-actionable notes about this communication.
... output C0..*BackboneElementFormal Response from Fulfiller to the Correction Request or to the Disagreement to Correction Denial.
.... type 1..1CodeableConceptLabel for output
Binding: Patient Correction Output Types Value Set (required)
.... value[x] 1..1Result of output
..... valueStringstring
..... valueAttachmentAttachment
..... valueReferenceReference(Patient Correction Communication)

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet / Code
Task.statusrequiredTaskStatus
Task.statusReasonexample
Task.businessStatusrequiredPatientCorrectionBusinessStatusVS
Task.intentrequiredFixed Value: order
Task.coderequiredPatientCorrectionTaskTypesVS
Task.reasonCodeexample
Task.output.typerequiredPatientCorrectionOutputTypesVS

Constraints

IdGradePath(s)DetailsRequirements
task-output2errorTaskIf 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-reasonreferenceerrorTaskIf 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-allowederrorTask.statusThe status of the Task SHALL be one of the following: ready, in-progress, cancelled, completed.
: $this in ('ready' | 'in-progress' | 'cancelled' | 'completed')

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. Task C0..*TaskA 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..1idLogical id of this artifact
... 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: CommonLanguages (preferred): A human language.

Additional BindingsPurpose
AllLanguagesMax Binding
... text 0..1NarrativeText summary of the resource, for human interpretation
... 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ΣC1..1codeCurrent 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..1CodeableConceptReason 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..1CodeableConceptBusiness status of the request for correction process or the log disagreement process.
Binding: Patient Correction Business Status (required)
... intent Σ1..1codeIndicates 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..1coderoutine | urgent | asap | stat
Binding: RequestPriority (required): The task's priority.

... code SΣC1..1CodeableConceptCorrection Task type.
Binding: Patient Correction Task Types Values Set (required)
... description Σ0..1stringHuman-readable explanation of task
... focus Σ0..1Reference(Resource)What task is acting on
... for SΣ1..1Reference(Patient)Patient this correction or disagreement relates to.
... executionPeriod Σ0..1PeriodWhen the request is completed by the Fulfiller.
... authoredOn SC1..1dateTimeWhen this Task was created.
... lastModified SΣC0..1dateTimeWhen the correction task was last modified.
... requester SΣ0..1Reference(Patient | RelatedPerson)Entity requesting the correction or logging the disagreement.
... performerType 0..*CodeableConceptRequested performer
Binding: ProcedurePerformerRoleCodes (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..1CodeableConceptWhy 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 C0..1Reference(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..*AnnotationNon-actionable notes about this communication.
... relevantHistory 0..*Reference(Provenance)Key events in history of the Task
... input 0..*BackboneElementInformation used to perform task
.... type 1..1CodeableConceptLabel for input
Binding: Patient Correction Communication Types Value Set (required)
.... value[x] 1..1Content to use in performing the task
..... valueStringstring
..... valueAttachmentAttachment
..... valueReferenceReference(Patient Correction Communication)
... output C0..*BackboneElementFormal Response from Fulfiller to the Correction Request or to the Disagreement to Correction Denial.
.... type 1..1CodeableConceptLabel for output
Binding: Patient Correction Output Types Value Set (required)
.... value[x] 1..1Result of output
..... valueStringstring
..... valueAttachmentAttachment
..... valueReferenceReference(Patient Correction Communication)

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet / Code
Task.languagepreferredCommonLanguages
Additional Bindings Purpose
AllLanguages Max Binding
Task.statusrequiredTaskStatus
Task.statusReasonexample
Task.businessStatusrequiredPatientCorrectionBusinessStatusVS
Task.intentrequiredFixed Value: order
Task.priorityrequiredRequestPriority
Task.coderequiredPatientCorrectionTaskTypesVS
Task.performerTypepreferredProcedurePerformerRoleCodes
Task.reasonCodeexample
Task.input.typerequiredPatientCorrectionCommunicationTypesVS
Task.output.typerequiredPatientCorrectionOutputTypesVS

Constraints

IdGradePath(s)DetailsRequirements
task-output2errorTaskIf 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-reasonreferenceerrorTaskIf 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-allowederrorTask.statusThe 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

Summary

Mandatory: 3 elements
Must-Support: 9 elements
Fixed Value: 1 element
Prohibited: 10 elements

Structures

This structure refers to these other structures:

 

Other representations of profile: CSV, Excel, Schematron