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

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

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'
InformationCommunication.basedOnElement maximum cardinalities differ: '0' vs '2147483647'
InformationStructureDefinition.shortValues for short differ: 'Part of this action' vs 'Initial Patient Correction Communication resource for this request.'
InformationStructureDefinition.definitionValues for definition differ: 'Part of this action.' vs 'The initial communication sent by a Requester for a record correction.'
WarningCommunication.partOfElements differ in definition for mustSupport: 'false' vs 'true'
InformationCommunication.partOfElement maximum cardinalities differ: '0' vs '1'
InformationStructureDefinition.shortValues for short differ: 'Patient Correction Request Communication that this is in response to. This will only be filled in if it represents a response to another Communication resource. It can be used to query and assemble conversation threads related to the request process.' vs 'Reply to'
ErrorCommunication.inResponseToType Mismatch: Reference([CanonicalType[http://hl7.org/fhir/uv/patient-corrections/StructureDefinition/patient-correction-communication]]) vs Reference([CanonicalType[http://hl7.org/fhir/uv/patient-corrections/StructureDefinition/patient-correction-communication]])
InformationStructureDefinition.shortValues for short differ: 'A heading/subject line for the message being sent. Could be thought of as the subject line in an email thread.' vs 'A heading/subject line for the message being sent.'
InformationStructureDefinition.commentValues for comment differ: 'Communication.topic.text can be used without any codings.' vs 'Equivalent to the subject line in an email thread.'
InformationStructureDefinition.shortValues for short differ: 'If this is the original Patient Correction Request then Communication.about will initially be empty when posted by the Requester but populated with the Request for Correction Task reference by the Fulfiller when the Fulfiller spawn a Task to represent the Request for Correction or Logging of Disagreement process. For all subsequent Communication resources that represent conversations help between Requester and Fulfiller as part of the process, Communication.about references the Communication resource that contains the original request. If this Communication represents the start of a Log Disagreement request, then when the Fulfiller spawns a Task to support the logging of the disagreement, Communication.about will also reference the spawned Task.' vs 'Resources that pertain to this communication'
WarningCommunication.aboutElements differ in definition for mustSupport: 'true' vs 'false'
InformationCommunication.aboutElement maximum cardinalities differ: '2' vs '2147483647'
InformationCommunication.encounterElement maximum cardinalities differ: '0' vs '1'
InformationStructureDefinition.shortValues for short differ: 'The date that this particular part of the conversation is sent. On the initial request from the Requestor for either correction or logging a disagreement, this date/time will be used as Task.authoredOn to signify when the process was initiated on the Fulfiller.' vs 'When this communication was sent'
InformationStructureDefinition.shortValues for short differ: 'Depending on the direction of the patient correction communication, the recipient of the communication may be the Fulfiller, or it may be the Requester.' vs 'Message recipient: either a Requestor or a Fulfiller'
InformationCommunication.recipientElement maximum cardinalities differ: '1' vs '2147483647'
InformationStructureDefinition.shortValues for short differ: 'Depending on the direction of the patient correction communication, the sender of the communication may be the Requester or it may be the Fulfiller. On the initial request for correction or logging of disagreement, the Fulfiller will use sender to represent the Task.requester.' vs 'Message sender: either a Requestor or a Fulfiller'
InformationStructureDefinition.shortValues for short differ: 'The contents of this particular conversation component. If this is the original correction request or logging of a disagreement, then the payload would contain the request. If it is the final outcome of the request, then the payload would contain the final outcome information. Otherwise it contains a single message in back and forth conversation needed to process the initial request. Since it is possible to have a Communication resource reference a conversation held outside of the FHIR Rest protocol (email, mail, portal messaging – see Communication.channel) the minimum cardinality is zero. However, it is expected in most cases payload will be valued.' vs 'Contents of this communication.'
InformationStructureDefinition.shortValues for short differ: 'Notes from those that are working on the correction about that work (this is not the correction request itself).' vs 'Non-actionable notes about this communication.'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/Communication
      .copyright
        .date2022-03-29T16:29:26+00:002025-07-10T15:54:42+00:00
        • Values Differ
        .descriptionA Communication between a patient and a fulfiller relating to a patient correction request.
          .experimental
            .fhirVersion4.0.1
              .jurisdiction
                ..jurisdiction[0]http://unstats.un.org/unsd/methods/m49/m49.htm#001
                  .kindresource
                    .namePatientCorrectionCommunication
                      .publisherHL7 International - Patient Empowerment WorkgroupHL7 International / Patient Empowerment
                      • Values Differ
                      .purpose
                        .statusactive
                          .titlePatient Correction Communication
                            .typeCommunication
                              .urlhttp://hl7.org/fhir/uv/patient-corrections/StructureDefinition/patient-correction-communication
                                .version1.0.0-ballot1.0.0
                                • Values Differ

                                Structure

                                NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.R TypeR Description & ConstraintsCommentsdoco
                                .. Communication 0..*CommunicationA record of information transmitted from a sender to a receiver
                                0..*CommunicationA record of information transmitted from a sender to a receiver
                                  ... 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 Σ0..*IdentifierUnique identifier
                                                  Σ0..*IdentifierUnique identifier
                                                    ... instantiatesCanonical Σ0..*canonical(PlanDefinition | ActivityDefinition | Measure | OperationDefinition | Questionnaire)Instantiates FHIR protocol or definition
                                                    Σ0..*canonical(PlanDefinition | ActivityDefinition | Measure | OperationDefinition | Questionnaire)Instantiates FHIR protocol or definition
                                                      ... instantiatesUri Σ0..*uriInstantiates external protocol or definition
                                                      Σ0..*uriInstantiates external protocol or definition
                                                        ... basedOn Σ0..0Σ0..*Reference(Resource)Request fulfilled by this communication
                                                        • Element maximum cardinalities differ: '0' vs '2147483647'
                                                        ... partOf Σ0..0SΣ0..1Reference(Patient Correction Communication)Initial Patient Correction Communication resource for this request.
                                                        • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                        • Element maximum cardinalities differ: '0' vs '1'
                                                        ... inResponseTo S0..1Reference(Patient Correction Communication)Patient Correction Request Communication that this is in response to. This will only be filled in if it represents a response to another Communication resource. It can be used to query and assemble conversation threads related to the request process.
                                                        S0..1Reference(Patient Correction Communication)Reply to
                                                        • Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/uv/patient-corrections/StructureDefinition/patient-correction-communication]]) vs Reference([CanonicalType[http://hl7.org/fhir/uv/patient-corrections/StructureDefinition/patient-correction-communication]])
                                                        ... status ?!Σ1..1codeFixed: completed.
                                                        Binding: ?? (required): The status of the communication.
                                                        Required Pattern: completed
                                                        ?!Σ1..1codeFixed: completed.
                                                        Binding: ?? (required): The status of the communication.
                                                        Required Pattern: completed
                                                          ... statusReason Σ0..1CodeableConceptReason for current status
                                                          Binding: ?? (example): Codes for the reason why a communication did not happen.
                                                          Σ0..1CodeableConceptReason for current status
                                                          Binding: ?? (example): Codes for the reason why a communication did not happen.
                                                            ... category S1..1CodeableConceptMessage category
                                                            Binding: ?? (required)
                                                            S1..1CodeableConceptMessage category
                                                            Binding: ?? (required)
                                                              ... priority Σ0..1coderoutine | urgent | asap | stat
                                                              Binding: ?? (required): Codes indicating the relative importance of a communication.
                                                              Σ0..1coderoutine | urgent | asap | stat
                                                              Binding: ?? (required): Codes indicating the relative importance of a communication.
                                                                ... medium 0..*CodeableConceptA channel of communication
                                                                Binding: ?? (example): Codes for communication mediums such as phone, fax, email, in person, etc.
                                                                0..*CodeableConceptA channel of communication
                                                                Binding: ?? (example): Codes for communication mediums such as phone, fax, email, in person, etc.
                                                                  ... subject SΣ1..1Reference(Patient)The Patient that the correction request or the log disagreement applies to.SΣ1..1Reference(Patient)The Patient that the correction request or the log disagreement applies to.
                                                                    ... topic S0..1CodeableConceptA heading/subject line for the message being sent. Could be thought of as the subject line in an email thread.
                                                                    Binding: ?? (example): Codes describing the purpose or content of the communication.
                                                                    S0..1CodeableConceptA heading/subject line for the message being sent.
                                                                    Binding: ?? (example): Codes describing the purpose or content of the communication.
                                                                      ... about S0..2Reference(Patient Correction Task | Patient Correction Communication)If this is the original Patient Correction Request then Communication.about will initially be empty when posted by the Requester but populated with the Request for Correction Task reference by the Fulfiller when the Fulfiller spawn a Task to represent the Request for Correction or Logging of Disagreement process. For all subsequent Communication resources that represent conversations help between Requester and Fulfiller as part of the process, Communication.about references the Communication resource that contains the original request. If this Communication represents the start of a Log Disagreement request, then when the Fulfiller spawns a Task to support the logging of the disagreement, Communication.about will also reference the spawned Task.
                                                                      0..*Reference(Resource)Resources that pertain to this communication
                                                                      Slice: Unordered, Open by type:reference
                                                                      • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                      • Element maximum cardinalities differ: '2' vs '2147483647'
                                                                      ... encounter Σ0..0Σ0..1Reference(Encounter)Encounter created as part of
                                                                      • Element maximum cardinalities differ: '0' vs '1'
                                                                      ... sent 1..1dateTimeThe date that this particular part of the conversation is sent. On the initial request from the Requestor for either correction or logging a disagreement, this date/time will be used as Task.authoredOn to signify when the process was initiated on the Fulfiller.1..1dateTimeWhen this communication was sent
                                                                        ... received 0..1dateTimeWhen received0..1dateTimeWhen received
                                                                          ... recipient S1..1Reference(Patient | RelatedPerson | Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService)Depending on the direction of the patient correction communication, the recipient of the communication may be the Fulfiller, or it may be the Requester.
                                                                          S1..*Reference(Patient | RelatedPerson | Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService)Message recipient: either a Requestor or a Fulfiller
                                                                          • Element maximum cardinalities differ: '1' vs '2147483647'
                                                                          ... sender S1..1Reference(Patient | RelatedPerson | Practitioner | PractitionerRole | Organization | HealthcareService)Depending on the direction of the patient correction communication, the sender of the communication may be the Requester or it may be the Fulfiller. On the initial request for correction or logging of disagreement, the Fulfiller will use sender to represent the Task.requester.S1..1Reference(Patient | RelatedPerson | Practitioner | PractitionerRole | Organization | HealthcareService)Message sender: either a Requestor or a Fulfiller
                                                                            ... reasonCode Σ0..*CodeableConceptIndication for message
                                                                            Binding: ?? (example): Codes for describing reasons for the occurrence of a communication.
                                                                            Σ0..*CodeableConceptIndication for message
                                                                            Binding: ?? (example): Codes for describing reasons for the occurrence of a communication.
                                                                              ... reasonReference Σ0..*Reference(Condition | Observation | DiagnosticReport | DocumentReference)Why was communication done?
                                                                              Σ0..*Reference(Condition | Observation | DiagnosticReport | DocumentReference)Why was communication done?
                                                                                ... payload S0..*BackboneElementThe contents of this particular conversation component. If this is the original correction request or logging of a disagreement, then the payload would contain the request. If it is the final outcome of the request, then the payload would contain the final outcome information. Otherwise it contains a single message in back and forth conversation needed to process the initial request. Since it is possible to have a Communication resource reference a conversation held outside of the FHIR Rest protocol (email, mail, portal messaging – see Communication.channel) the minimum cardinality is zero. However, it is expected in most cases payload will be valued.
                                                                                S0..*BackboneElementContents of this communication.
                                                                                  .... 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
                                                                                        .... content[x] 1..1string, Attachment, Reference(Resource)Message part content1..1string, Attachment, Reference(Resource)Message part content
                                                                                          ... note 0..*AnnotationNotes from those that are working on the correction about that work (this is not the correction request itself).
                                                                                          0..*AnnotationNon-actionable notes about this communication.

                                                                                            doco Documentation for this format