Profile Comparison between http://medcomfhir.dk/ig/carecommunication/StructureDefinition/medcom-careCommunication-communication vs http://medcomfhir.dk/ig/carecommunication/StructureDefinition/medcom-careCommunication-communication

Left:MedComCareCommunication (http://medcomfhir.dk/ig/carecommunication/StructureDefinition/medcom-careCommunication-communication)
Right:MedComCareCommunication (http://medcomfhir.dk/ig/carecommunication/StructureDefinition/medcom-careCommunication-communication)

Messages

ErrorStructureDefinition.versionValues for version differ: '2.1.0' vs '3.0.0'
InformationStructureDefinition.dateValues for date differ: '2023-04-14T09:10:05+02:00' vs '2023-10-04T16:21:05+02:00'
WarningCommunication.payloadElements differ in short: 'Each payload corresponds to a message segment with a signature and a message text or attachment. At least one payload with a message text shall be included.' vs 'Each payload corresponds to a message segment with a message text or an attachment. At least one payload with a message text shall be included.'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/Communication
      .copyright
        .date2023-04-14T09:10:05+02:002023-10-04T16:21:05+02:00
        • Values Differ
        .descriptionCare related communication between two or more parties in Danish healthcare
          .experimental
            .fhirVersion4.0.1
              .jurisdiction
                ..jurisdiction[0]urn:iso:std:iso:3166#DK
                  .kindresource
                    .nameMedComCareCommunication
                      .publisherMedCom
                        .purpose
                          .statusactive
                            .title
                              .typeCommunication
                                .urlhttp://medcomfhir.dk/ig/carecommunication/StructureDefinition/medcom-careCommunication-communication
                                  .version2.1.03.0.0
                                  • Values Differ

                                  Structure

                                  NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.L TypeL Description & ConstraintsCommentsdoco
                                  .. Communication C0..*CommunicationA record of information transmitted from a sender to a receiver
                                  medcom-careCommunication-5: Priority is only allowed when Communication.category = 'regarding-referral'
                                  medcom-careCommunication-6: There shall exist a Communication.topic when Communication.category = 'other'
                                  medcom-careCommunication-7: There shall exist a practitioner role when using a PractitionerRole as author in a message segment.
                                  medcom-careCommunication-8: There shall exist a practitioner name when using a Practitioner as author in a message segment.
                                  medcom-careCommunication-10: The status shall be 'unknown' or 'entered-in-error'.
                                  C0..*CommunicationA record of information transmitted from a sender to a receiver
                                  medcom-careCommunication-5: Priority is only allowed when Communication.category = 'regarding-referral'
                                  medcom-careCommunication-6: There shall exist a Communication.topic when Communication.category = 'other'
                                  medcom-careCommunication-7: There shall exist a practitioner role when using a PractitionerRole as author in a message segment.
                                  medcom-careCommunication-8: There shall exist a practitioner name when using a Practitioner as author in a message segment.
                                  medcom-careCommunication-10: The status shall be 'unknown' or 'entered-in-error'.
                                    ... id Σ0..1idLogical 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 interpretation0..1NarrativeText summary of the resource, for human interpretation
                                              ... contained 0..*ResourceContained, inline Resources
                                              0..*ResourceContained, inline Resources
                                                ... Slices for extension 0..*ExtensionExtension
                                                Slice: Unordered, Open by value:url
                                                0..*ExtensionExtension
                                                Slice: Unordered, Open by value:url
                                                  ... 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..*Reference(Resource)Request fulfilled by this communication
                                                          Σ0..*Reference(Resource)Request fulfilled by this communication
                                                            ... partOf Σ0..*Reference(Resource)Part of this action
                                                            Σ0..*Reference(Resource)Part of this action
                                                              ... inResponseTo 0..*Reference(Communication)Reply to
                                                              0..*Reference(Communication)Reply to
                                                                ... status ?!SΣ1..1codeThe status may be 'unknown' or 'entered-in-error', dependning on the type of message. status is required because of basic FHIR profile requirement
                                                                Binding: ?? (required): The status of the communication.

                                                                ?!SΣ1..1codeThe status may be 'unknown' or 'entered-in-error', dependning on the type of message. status is required because of basic FHIR profile requirement
                                                                Binding: ?? (required): The status of the communication.

                                                                  ... 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..1CodeableConceptThe category (Danish: kategori) describes the overall content of the message.
                                                                    Binding: ?? (required)
                                                                    S1..1CodeableConceptThe category (Danish: kategori) describes the overall content of the message.
                                                                    Binding: ?? (required)
                                                                      ... priority SΣ0..1codeShall be present if the message priority is known to be ASAP, but is only allowed when the category is 'regarding referral', see medcom-careCommunication-5
                                                                      Binding: ?? (required)
                                                                      SΣ0..1codeShall be present if the message priority is known to be ASAP, but is only allowed when the category is 'regarding referral', see medcom-careCommunication-5
                                                                      Binding: ?? (required)
                                                                        ... 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(MedComCorePatient) {b}Focus of messageSΣ1..1Reference(MedComCorePatient) {b}Focus of message
                                                                            ... topic S0..1CodeableConceptThe topic (Danish: emne) may be added as a supplement to the category.
                                                                            Binding: ?? (example): Codes describing the purpose or content of the communication.

                                                                            S0..1CodeableConceptThe topic (Danish: emne) may be added as a supplement to the category.
                                                                            Binding: ?? (example): Codes describing the purpose or content of the communication.

                                                                              ... about 0..*Reference(Resource)Resources that pertain to this communication
                                                                              0..*Reference(Resource)Resources that pertain to this communication
                                                                                ... encounter SΣ0..1Reference(MedComCoreEncounter) {b}Shall contain a reference to an Encounter resource with a episodeOfCare-identifier, if the identifier is included in a previous message.SΣ0..1Reference(MedComCoreEncounter) {b}Shall contain a reference to an Encounter resource with a episodeOfCare-identifier, if the identifier is included in a previous message.
                                                                                  ... sent 0..1dateTimeWhen sent0..1dateTimeWhen sent
                                                                                    ... received 0..1dateTimeWhen received0..1dateTimeWhen received
                                                                                      ... recipient S0..*Reference(MedComCorePractitionerRole | MedComCoreCareTeam) {b}Describes a more specific receiver than the MessageHeader.destination.reciever, called a recipient. It may be a careteam a homecare group in the municipality or a named general practitioner.
                                                                                      S0..*Reference(MedComCorePractitionerRole | MedComCoreCareTeam) {b}Describes a more specific receiver than the MessageHeader.destination.reciever, called a recipient. It may be a careteam a homecare group in the municipality or a named general practitioner.
                                                                                        ... sender 0..1Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson | HealthcareService)Message sender0..1Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson | HealthcareService)Message sender
                                                                                          ... 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?
                                                                                              ... Slices for payload 1..*BackboneElementEach payload corresponds to a message segment with a signature and a message text or attachment. At least one payload with a message text shall be included.
                                                                                              Slice: Ordered, Open by type:$this.content
                                                                                              1..*BackboneElementEach payload corresponds to a message segment with a message text or an attachment. At least one payload with a message text shall be included.
                                                                                              Slice: Ordered, Open by type:$this.content
                                                                                              • Elements differ in short: 'Each payload corresponds to a message segment with a signature and a message text or attachment. At least one payload with a message text shall be included.' vs 'Each payload corresponds to a message segment with a message text or an attachment. At least one payload with a message text shall be included.'
                                                                                              .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                                                .... Slices for extension 0..*ExtensionExtension
                                                                                                Slice: Unordered, Open by value:url
                                                                                                0..*ExtensionExtension
                                                                                                Slice: Unordered, Open by value:url
                                                                                                  .... 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..*AnnotationComments made about the communication
                                                                                                      0..*AnnotationComments made about the communication

                                                                                                        doco Documentation for this format