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

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

Messages

ErrorStructureDefinition.versionValues for version differ: '3.0.0' vs '4.0.0'
InformationStructureDefinition.dateValues for date differ: '2023-10-04T16:21:05+02:00' vs '2024-06-28T11:24:18+02:00'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://medcomfhir.dk/ig/messaging/StructureDefinition/medcom-messaging-message
      .copyright
        .date2023-10-04T16:21:05+02:002024-06-28T11:24:18+02:00
        • Values Differ
        .descriptionThe CareCommunication is used to ensure secure electronic communication of personally identifiable information and is most often used for ad hoc communication between parties in Danish Healthcare. However, the CareCommunication shall only be used in areas where no other MedCom standard is available, and it must not be used for cases with an acute nature.
          .experimental
            .fhirVersion4.0.1
              .jurisdiction
                ..jurisdiction[0]urn:iso:std:iso:3166#DK
                  .kindresource
                    .nameMedComCareCommunicationMessage
                      .publisherMedCom
                        .purpose
                          .statusactive
                            .title
                              .typeBundle
                                .urlhttp://medcomfhir.dk/ig/carecommunication/StructureDefinition/medcom-careCommunication-message
                                  .version3.0.04.0.0
                                  • Values Differ

                                  Structure

                                  NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.R TypeR Description & ConstraintsCommentsdoco
                                  .. Bundle C0..*MedComMessagingMessageContains a collection of resources
                                  bdl-1: total only when a search or history
                                  bdl-2: entry.search only when a search
                                  bdl-3: entry.request mandatory for batch/transaction/history, otherwise prohibited
                                  bdl-4: entry.response mandatory for batch-response/transaction-response/history, otherwise prohibited
                                  bdl-7: FullUrl must be unique in a bundle, or else entries with the same fullUrl must have different meta.versionId (except in history bundles)
                                  bdl-9: A document must have an identifier with a system and a value
                                  bdl-10: A document must have a date
                                  bdl-11: A document must have a Composition as the first resource
                                  bdl-12: A message must have a MessageHeader as the first resource
                                  medcom-messaging-1: The MessageHeader resource shall conform to medcom-messaging-messageHeader profile
                                  medcom-messaging-2: There shall be at least one Provenance resource in a MedCom message
                                  medcom-messaging-3: All Provenance resources shall conform to medcom-core-provenance profile
                                  medcom-careCommunication-1: The MessageHeader shall conform to medcom-careCommunication-messageHeader profile
                                  medcom-careCommunication-2: Entry shall contain exactly one Patient resource
                                  medcom-careCommunication-3: All Provenance resources shall contain activities from medcom-careCommunication-messagingActivities valueset
                                  medcom-careCommunication-4: There shall exist a practitioner given and family name when using a PractitionerRole.
                                  medcom-careCommunication-12: If a specific recipient exists, the organisation which the CareTeam or Practitioner is a part of shall be the same as the receiver organisation in the MessageHeader resource.
                                  medcom-careCommunication-11: If a specific sender exists, the organisation which the CareTeam or Practitioner is a part of shall be the same as the sender organisation in the MessageHeader resource.
                                  medcom-careCommunication-13: All PractitionerRole resources shall have a reference to an instance of a Practitioner resource.
                                  C0..*MedComMessagingMessageContains a collection of resources
                                  bdl-1: total only when a search or history
                                  bdl-2: entry.search only when a search
                                  bdl-3: entry.request mandatory for batch/transaction/history, otherwise prohibited
                                  bdl-4: entry.response mandatory for batch-response/transaction-response/history, otherwise prohibited
                                  bdl-7: FullUrl must be unique in a bundle, or else entries with the same fullUrl must have different meta.versionId (except in history bundles)
                                  bdl-9: A document must have an identifier with a system and a value
                                  bdl-10: A document must have a date
                                  bdl-11: A document must have a Composition as the first resource
                                  bdl-12: A message must have a MessageHeader as the first resource
                                  medcom-messaging-1: The MessageHeader resource shall conform to medcom-messaging-messageHeader profile
                                  medcom-messaging-2: There shall be at least one Provenance resource in a MedCom message
                                  medcom-messaging-3: All Provenance resources shall conform to the medcom-messaging-provenance profile
                                  medcom-careCommunication-1: The MessageHeader shall conform to medcom-careCommunication-messageHeader profile
                                  medcom-careCommunication-2: Entry shall contain exactly one Patient resource
                                  medcom-careCommunication-4: There shall exist a practitioner given and family name when using a PractitionerRole.
                                  medcom-careCommunication-3: All Provenance resources shall be of the type medcom-careCommunication-provenance profile
                                  medcom-careCommunication-12: If a specific recipient exists, the organisation which the CareTeam or Practitioner is a part of shall be the same as the receiver organisation in the MessageHeader resource.
                                  medcom-careCommunication-11: If a specific sender exists, the organisation which the CareTeam or Practitioner is a part of shall be the same as the sender organisation in the MessageHeader resource.
                                  medcom-careCommunication-13: All PractitionerRole resources shall have a reference to an instance of a Practitioner resource.
                                    ... id SΣ1..1idLogical id of this artifactSΣ1..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
                                          ... identifier Σ0..1IdentifierPersistent identifier for the bundleΣ0..1IdentifierPersistent identifier for the bundle
                                            ... type SΣ1..1codeAlways message
                                            Binding: ?? (required): Indicates the purpose of a bundle - how it is intended to be used.


                                            Required Pattern: message
                                            SΣ1..1codeAlways message
                                            Binding: ?? (required): Indicates the purpose of a bundle - how it is intended to be used.


                                            Required Pattern: message
                                              ... timestamp SΣ1..1instantWhen the bundle was assembledSΣ1..1instantWhen the bundle was assembled
                                                ... total ΣC0..1unsignedIntIf search, the total number of matchesΣC0..1unsignedIntIf search, the total number of matches
                                                  ... link Σ0..*BackboneElementLinks related to this Bundle
                                                  Σ0..*BackboneElementLinks related to this Bundle
                                                    .... 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
                                                          .... relation Σ1..1stringSee http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1Σ1..1stringSee http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1
                                                            .... url Σ1..1uriReference details for the linkΣ1..1uriReference details for the link
                                                              ... entry SΣC0..*BackboneElementMessage content (MedComCareCommunicationMessageHeader, MedComMessagingOrganization, MedComMessagingProvenance, MedComCareCommunication, MedComCorePatient, MedComCoreEncounter, MedComCorePractitioner, MedComCorePractitionerRole, MedComCoreCareTeam) - Open
                                                              bdl-5: must be a resource unless there's a request or response
                                                              bdl-8: fullUrl cannot be a version specific reference
                                                              This repeating element order: For bundles of type 'document' and 'message', the first resource is special (must be Composition or MessageHeader respectively). For all bundles, the meaning of the order of entries depends on the bundle type
                                                              SΣC0..*BackboneElementMessage content (MedComCareCommunicationMessageHeader, MedComMessagingOrganization, MedComMessagingProvenance, MedComCareCommunication, MedComCorePatient, MedComCoreEncounter, MedComCorePractitioner, MedComCorePractitionerRole, MedComCoreCareTeam) - Open
                                                              bdl-5: must be a resource unless there's a request or response
                                                              bdl-8: fullUrl cannot be a version specific reference
                                                              This repeating element order: For bundles of type 'document' and 'message', the first resource is special (must be Composition or MessageHeader respectively). For all bundles, the meaning of the order of entries depends on the bundle type
                                                                .... 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
                                                                      .... link Σ0..*See link (Bundle)Links related to this entry
                                                                      Σ0..*See link (Bundle)Links related to this entry
                                                                        .... fullUrl Σ0..1uriURI for resource (Absolute URL server address or URI for UUID/OID)Σ0..1uriURI for resource (Absolute URL server address or URI for UUID/OID)
                                                                          .... resource SΣ0..1ResourceEach MedCom message shall contain a MedComMessagingMessageHeader and MedComMessagingProvenance. Please refer to invariant medcom-messaging-1, medcom-messaging-2, and medcom-messaging-3.SΣ0..1ResourceEach MedCom message shall contain a MedComMessagingMessageHeader and MedComMessagingProvenance. Please refer to invariant medcom-messaging-1, medcom-messaging-2, and medcom-messaging-3.
                                                                            .... search ΣC0..1BackboneElementSearch related informationΣC0..1BackboneElementSearch related information
                                                                              ..... 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
                                                                                    ..... mode Σ0..1codematch | include | outcome - why this is in the result set
                                                                                    Binding: ?? (required): Why an entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process.

                                                                                    Σ0..1codematch | include | outcome - why this is in the result set
                                                                                    Binding: ?? (required): Why an entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process.

                                                                                      ..... score Σ0..1decimalSearch ranking (between 0 and 1)Σ0..1decimalSearch ranking (between 0 and 1)
                                                                                        .... request ΣC0..1BackboneElementAdditional execution information (transaction/batch/history)ΣC0..1BackboneElementAdditional execution information (transaction/batch/history)
                                                                                          ..... 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
                                                                                                ..... method Σ1..1codeGET | HEAD | POST | PUT | DELETE | PATCH
                                                                                                Binding: ?? (required): HTTP verbs (in the HTTP command line). See HTTP rfc for details.

                                                                                                Σ1..1codeGET | HEAD | POST | PUT | DELETE | PATCH
                                                                                                Binding: ?? (required): HTTP verbs (in the HTTP command line). See HTTP rfc for details.

                                                                                                  ..... url Σ1..1uriURL for HTTP equivalent of this entryΣ1..1uriURL for HTTP equivalent of this entry
                                                                                                    ..... ifNoneMatch Σ0..1stringFor managing cache currencyΣ0..1stringFor managing cache currency
                                                                                                      ..... ifModifiedSince Σ0..1instantFor managing cache currencyΣ0..1instantFor managing cache currency
                                                                                                        ..... ifMatch Σ0..1stringFor managing update contentionΣ0..1stringFor managing update contention
                                                                                                          ..... ifNoneExist Σ0..1stringFor conditional createsΣ0..1stringFor conditional creates
                                                                                                            .... response ΣC0..1BackboneElementResults of execution (transaction/batch/history)ΣC0..1BackboneElementResults of execution (transaction/batch/history)
                                                                                                              ..... 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
                                                                                                                    ..... status Σ1..1stringStatus response code (text optional)Σ1..1stringStatus response code (text optional)
                                                                                                                      ..... location Σ0..1uriThe location (if the operation returns a location)Σ0..1uriThe location (if the operation returns a location)
                                                                                                                        ..... etag Σ0..1stringThe Etag for the resource (if relevant)Σ0..1stringThe Etag for the resource (if relevant)
                                                                                                                          ..... lastModified Σ0..1instantServer's date time modifiedΣ0..1instantServer's date time modified
                                                                                                                            ..... outcome Σ0..1ResourceOperationOutcome with hints and warnings (for batch/transaction)Σ0..1ResourceOperationOutcome with hints and warnings (for batch/transaction)
                                                                                                                              ... signature ΣTU0..1SignatureDigital SignatureΣ0..1SignatureDigital Signature

                                                                                                                                doco Documentation for this format