Profile Comparison between http://hl7.org/fhir/uv/patient-corrections/StructureDefinition/patient-correction-task vs http://hl7.org/fhir/uv/patient-corrections/StructureDefinition/patient-correction-task

Left:Patient Correction Task (http://hl7.org/fhir/uv/patient-corrections/StructureDefinition/patient-correction-task)
Right:Patient Correction Task (http://hl7.org/fhir/uv/patient-corrections/StructureDefinition/patient-correction-task)

Messages

ErrorStructureDefinition.versionValues for version differ: '1.0.0-ballot' vs '1.0.0'
InformationStructureDefinition.dateValues for date differ: '2022-03-29T16:29:26+00:00' vs '2025-07-10T15:54:42+00:00'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 International - Patient Empowerment Workgroup' vs 'HL7 International / Patient Empowerment'
InformationStructureDefinition.shortValues for short differ: '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.' vs 'Current status of a Correction Request or Log Disagreement.'
InformationStructureDefinition.shortValues for short differ: 'The reason for the correction request status. Codes to identify the reason for current status. These will typically be specific to a particular workflow.' vs 'Reason for the correction request status.'
InformationStructureDefinition.commentValues for comment differ: 'This applies to the current status. Look at the history of the task to see reasons for past statuses.' vs 'The reason for the correction request status. Codes to identify the reason for current status. These will typically be specific to a particular workflow.'
InformationStructureDefinition.shortValues for short differ: '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.' vs 'Business status of the request for correction process or the log disagreement process.'
InformationStructureDefinition.shortValues for short differ: 'unknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option' vs 'Indicates the actionability associated with the Task.'
InformationStructureDefinition.shortValues for short differ: 'Code and code.text to represent patient correction, or Code and code.text to represent a disagreement.' vs 'Correction Task type.'
InformationStructureDefinition.definitionValues for definition differ: 'A name or code (or both) briefly describing what the task involves.' vs 'Either a patient correction or a disagreement.'
InformationStructureDefinition.shortValues for short differ: '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.' vs 'Patient this correction or disagreement relates to.'
InformationStructureDefinition.shortValues for short differ: 'ExecutionPeriod.end can be used by the Fulfiller to represent when the request is completed.' vs 'When the request is completed by the Fulfiller.'
InformationStructureDefinition.shortValues for short differ: '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.' vs 'When this Task was created.'
InformationStructureDefinition.shortValues for short differ: '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.' vs 'When the correction task was last modified.'
InformationStructureDefinition.shortValues for short differ: 'The entity that is requesting the correction or logging the disagreement such as the patient themselves or their caregiver.' vs 'Entity requesting the correction or logging the disagreement.'
InformationStructureDefinition.definitionValues for definition differ: 'The creator of the task.' vs 'The entity that is requesting the correction or logging the disagreement, such as a patient or their caregiver.'
InformationStructureDefinition.shortValues for short differ: 'Why task is needed. E.g. Need record correct prior to upcoming surgery.' vs 'Why task is needed. E.g., need record correct prior to upcoming surgery.'
InformationStructureDefinition.shortValues for short differ: 'Used on Log Disagreement Task to point to the original Request for Correction Task.' vs 'Log Disagreement Task to point to the original Request for Correction Task.'
InformationStructureDefinition.commentValues for comment differ: 'Tasks might be justified based on an Observation, a Condition, a past or planned procedure, etc. This should only be included if there is no focus or if it differs from the reason indicated on the focus. Use the CodeableConcept text element in `Task.reasonCode` if the data is free (uncoded) text.' vs 'Used on Log Disagreement Task to point to the original Request for Correction Task.'
ErrorTask.reasonReferenceType Mismatch: Reference([CanonicalType[http://hl7.org/fhir/uv/patient-corrections/StructureDefinition/patient-correction-task]]) vs Reference([CanonicalType[http://hl7.org/fhir/uv/patient-corrections/StructureDefinition/patient-correction-task]])
InformationStructureDefinition.shortValues for short differ: 'Comments made about the task' vs 'Non-actionable notes about this communication.'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/Task
      .copyright
        .date2022-03-29T16:29:26+00:002025-07-10T15:54:42+00:00
        • Values Differ
        .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.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.
        • Values Differ
        .experimental
          .fhirVersion4.0.1
            .jurisdiction
              ..jurisdiction[0]http://unstats.un.org/unsd/methods/m49/m49.htm#001
                .kindresource
                  .namePatientCorrectionTask
                    .publisherHL7 International - Patient Empowerment WorkgroupHL7 International / Patient Empowerment
                    • Values Differ
                    .purpose
                      .statusactive
                        .titlePatient Correction Task
                          .typeTask
                            .urlhttp://hl7.org/fhir/uv/patient-corrections/StructureDefinition/patient-correction-task
                              .version1.0.0-ballot1.0.0
                              • Values Differ

                              Structure

                              NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.R TypeR Description & ConstraintsCommentsdoco
                              .. Task C0..*TaskA task to be performed
                              C0..*TaskA task to be performed
                              Constraints: task-reasonreference, task-output2
                                ... id Σ0..1stringLogical id of this artifactΣ0..1idLogical id of this artifact
                                  ... meta Σ0..1MetaMetadata about the resourceΣ0..1MetaMetadata about the resource
                                    ... implicitRules ?!Σ0..1uriA set of rules under which this content was created?!Σ0..1uriA set of rules under which this content was created
                                      ... language 0..1codeLanguage of the resource content
                                      Binding: ?? (preferred): A human language.
                                      Additional BindingsPurpose
                                      ??Max Binding
                                      0..1codeLanguage of the resource content
                                      Binding: ?? (preferred): A human language.
                                      Additional BindingsPurpose
                                      ??Max Binding
                                        ... 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
                                        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
                                          0..*ResourceContained, inline Resources
                                            ... extension 0..*ExtensionAdditional content defined by implementations
                                            0..*ExtensionAdditional content defined by implementations
                                              ... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
                                              ?!0..*ExtensionExtensions that cannot be ignored
                                                ... identifier S0..*IdentifierA business identifier for the correction process.
                                                S0..*IdentifierA business identifier for the correction process.
                                                  ... instantiatesCanonical Σ0..1canonical(ActivityDefinition)Formal definition of taskΣ0..1canonical(ActivityDefinition)Formal definition of task
                                                    ... instantiatesUri Σ0..1uriFormal definition of taskΣ0..1uriFormal definition of task
                                                      ... basedOn Σ0..0Σ0..0
                                                        ... groupIdentifier Σ0..1IdentifierRequisition or grouper idΣ0..1IdentifierRequisition or grouper id
                                                          ... partOf Σ0..0Σ0..0
                                                            ... status ?!SΣ1..1codeThe 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: ?? (required)
                                                            ?!SΣC1..1codeCurrent status of a Correction Request or Log Disagreement.
                                                            Binding: ?? (required)
                                                            Constraints: task-status-allowed
                                                              ... statusReason Σ0..1CodeableConceptThe reason for the correction request status. Codes to identify the reason for current status. These will typically be specific to a particular workflow.
                                                              Binding Description: (example): Codes to identify the reason for current status. These will typically be specific to a particular workflow.
                                                              Σ0..1CodeableConceptReason 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..1CodeableConceptThe 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: ?? (required)
                                                                SΣ0..1CodeableConceptBusiness status of the request for correction process or the log disagreement process.
                                                                Binding: ?? (required)
                                                                  ... intent Σ1..1codeunknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option
                                                                  Binding: ?? (required): Distinguishes whether the task is a proposal, plan or full order.
                                                                  Fixed Value: order
                                                                  Σ1..1codeIndicates the actionability associated with the Task.
                                                                  Binding: ?? (required): Distinguishes whether the task is a proposal, plan or full order.
                                                                  Fixed Value: order
                                                                    ... priority 0..1coderoutine | urgent | asap | stat
                                                                    Binding: ?? (required): The task's priority.
                                                                    0..1coderoutine | urgent | asap | stat
                                                                    Binding: ?? (required): The task's priority.
                                                                      ... code SΣ1..1CodeableConceptCode and code.text to represent patient correction, or Code and code.text to represent a disagreement.
                                                                      Binding: ?? (required)
                                                                      SΣC1..1CodeableConceptCorrection Task type.
                                                                      Binding: ?? (required)
                                                                        ... description Σ0..1stringHuman-readable explanation of taskΣ0..1stringHuman-readable explanation of task
                                                                          ... focus Σ0..1Reference(Resource)What task is acting onΣ0..1Reference(Resource)What task is acting on
                                                                            ... for SΣ1..1Reference(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.SΣ1..1Reference(Patient)Patient this correction or disagreement relates to.
                                                                              ... encounter Σ0..0Σ0..0
                                                                                ... executionPeriod Σ0..1PeriodExecutionPeriod.end can be used by the Fulfiller to represent when the request is completed.Σ0..1PeriodWhen the request is completed by the Fulfiller.
                                                                                  ... authoredOn SC1..1dateTimeThe 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.SC1..1dateTimeWhen this Task was created.
                                                                                    ... lastModified SΣC0..1dateTimeIndicates 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.SΣC0..1dateTimeWhen the correction task was last modified.
                                                                                      ... requester SΣ0..1Reference(Patient | RelatedPerson)The entity that is requesting the correction or logging the disagreement such as the patient themselves or their caregiver.SΣ0..1Reference(Patient | RelatedPerson)Entity requesting the correction or logging the disagreement.
                                                                                        ... performerType 0..*CodeableConceptRequested performer
                                                                                        Binding: ?? (preferred): The type(s) of task performers allowed.
                                                                                        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.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Σ0..1Reference(Location)Where task occurs
                                                                                              ... reasonCode 0..1CodeableConceptWhy 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.
                                                                                              0..1CodeableConceptWhy 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)Used on Log Disagreement Task to point to the original Request for Correction Task.
                                                                                                Constraints: task-reasonreference
                                                                                                C0..1Reference(Patient Correction Task)Log Disagreement Task to point to the original Request for Correction Task.
                                                                                                • Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/uv/patient-corrections/StructureDefinition/patient-correction-task]]) vs Reference([CanonicalType[http://hl7.org/fhir/uv/patient-corrections/StructureDefinition/patient-correction-task]])
                                                                                                ... insurance 0..*Reference(Coverage | ClaimResponse)Associated insurance coverage
                                                                                                0..*Reference(Coverage | ClaimResponse)Associated insurance coverage
                                                                                                  ... note 0..*AnnotationComments made about the task
                                                                                                  0..*AnnotationNon-actionable notes about this communication.
                                                                                                    ... relevantHistory 0..*Reference(Provenance)Key events in history of the Task
                                                                                                    0..*Reference(Provenance)Key events in history of the Task
                                                                                                      ... restriction 0..00..0
                                                                                                        .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                                                          .... extension 0..*ExtensionAdditional content defined by implementations
                                                                                                          0..*ExtensionAdditional content defined by implementations
                                                                                                            .... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                                                            ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                                                              .... repetitions 0..1positiveIntHow many times to repeat0..1positiveIntHow many times to repeat
                                                                                                                .... period 0..1PeriodWhen fulfillment sought0..1PeriodWhen fulfillment sought
                                                                                                                  .... recipient 0..*Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Group | Organization)For whom is fulfillment sought?
                                                                                                                  0..*Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Group | Organization)For whom is fulfillment sought?
                                                                                                                    ... input C0..*BackboneElementInformation used to perform task
                                                                                                                    Constraints: task-input
                                                                                                                    0..*BackboneElementInformation used to perform task
                                                                                                                      .... id 0..00..0
                                                                                                                        .... extension 0..00..0
                                                                                                                          .... modifierExtension ?!Σ0..0?!Σ0..0
                                                                                                                            .... type 1..1CodeableConceptLabel for input
                                                                                                                            Binding: ?? (required)
                                                                                                                            1..1CodeableConceptLabel for input
                                                                                                                            Binding: ?? (required)
                                                                                                                              .... value[x] 1..1string, Attachment, Reference(Patient Correction Communication)Content to use in performing the task1..1string, Attachment, Reference(Patient Correction Communication)Content to use in performing the task
                                                                                                                                ... output C0..*BackboneElementFormal Response from Fulfiller to the Correction Request or to the Disagreement to Correction Denial.
                                                                                                                                Constraints: task-output1, task-output2, task-output3
                                                                                                                                C0..*BackboneElementFormal Response from Fulfiller to the Correction Request or to the Disagreement to Correction Denial.
                                                                                                                                  .... id 0..00..0
                                                                                                                                    .... extension 0..00..0
                                                                                                                                      .... modifierExtension ?!Σ0..0?!Σ0..0
                                                                                                                                        .... type 1..1CodeableConceptLabel for output
                                                                                                                                        Binding: ?? (required)
                                                                                                                                        1..1CodeableConceptLabel for output
                                                                                                                                        Binding: ?? (required)
                                                                                                                                          .... value[x] 1..1string, Attachment, Reference(Patient Correction Communication)Result of output1..1string, Attachment, Reference(Patient Correction Communication)Result of output

                                                                                                                                            doco Documentation for this format