Profile Comparison between http://hl7.org/fhir/uv/order-catalog/StructureDefinition/CatalogMessageDefinition vs http://hl7.org/fhir/uv/order-catalog/StructureDefinition/CatalogMessageDefinition

Left:Message definition for messaging order-catalog content (http://hl7.org/fhir/uv/order-catalog/StructureDefinition/CatalogMessageDefinition)
Right:Message definition for messaging order-catalog content (http://hl7.org/fhir/uv/order-catalog/StructureDefinition/CatalogMessageDefinition)

Messages

ErrorStructureDefinition.versionValues for version differ: '0.1.0' vs 'current'
WarningStructureDefinition.fhirVersionValues for fhirVersion differ: '4.0.1' vs '5.0.0'
WarningMessageDefinition.idElements differ in comments: 'The only time that a resource does not have an id is when it is being submitted to the server using a create operation.' vs 'Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.'
WarningMessageDefinition.implicitRulesElements differ in comments: 'Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.' vs 'Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.'
WarningMessageDefinition.languageElements differ in binding.description: 'A human language.' vs 'IETF language tag for a human language'
WarningMessageDefinition.textElements differ in comments: 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a 'text blob' or where text is additionally entered raw or narrated and encoded information is added later.' vs 'Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a 'text blob' or where text is additionally entered raw or narrated and encoded information is added later.'
WarningMessageDefinition.containedElements differ in definition: 'These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.' vs 'These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.'
WarningMessageDefinition.extensionElements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.'
WarningMessageDefinition.modifierExtensionElements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).'
WarningMessageDefinition.urlElements differ in short: 'Business Identifier for a given MessageDefinition' vs 'The cannonical URL for a given MessageDefinition'
WarningMessageDefinition.identifierElements differ in short: 'Primary key for the message definition on a given server' vs 'Business Identifier for a given MessageDefinition'
WarningMessageDefinition.versionElements differ in comments: 'There may be different message definition instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the message definition with the format [url]|[version].' vs 'There may be different message definition instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the message definition with the format [url]|[version]. The version SHOULD NOT contain a '#' - see [Business Version].'
WarningMessageDefinition.statusElements differ in comments: 'Allows filtering of message definitions that are appropriate for use versus not.' vs 'Allows filtering of message definitions that are appropriate for use versus not. See guidance around (not) making local changes to elements [here].'
WarningMessageDefinition.dateElements differ in definition: 'The date (and optionally time) when the message definition was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the message definition changes.' vs 'The date (and optionally time) when the message definition was last significantly changed. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the message definition changes.'
WarningMessageDefinition.dateElements differ in comments: 'Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the message definition. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.' vs 'The date is often not tracked until the resource is published, but may be present on draft content. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the message definition. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource. See guidance around (not) making local changes to elements [here].'
WarningMessageDefinition.publisherElements differ in short: 'Name of the publisher (organization or individual)' vs 'Name of the publisher/steward (organization or individual)'
WarningMessageDefinition.publisherElements differ in definition: 'The name of the organization or individual that published the message definition.' vs 'The name of the organization or individual responsible for the release and ongoing maintenance of the message definition.'
WarningMessageDefinition.contactElements differ in comments: 'May be a web site, an email address, a telephone number, etc.' vs 'May be a web site, an email address, a telephone number, etc. See guidance around (not) making local changes to elements [here].'
WarningMessageDefinition.descriptionElements differ in comments: 'This description can be used to capture details such as why the message definition was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the message definition as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the message definition is presumed to be the predominant language in the place the message definition was created).' vs 'This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the message definition as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the message definition is presumed to be the predominant language in the place the message definition was created).'
WarningMessageDefinition.jurisdictionElements differ in comments: 'It may be possible for the message definition to be used in jurisdictions other than those for which it was originally designed or intended.' vs 'It may be possible for the message definition to be used in jurisdictions other than those for which it was originally designed or intended. DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.)'
WarningMessageDefinition.focus.extensionElements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.'
WarningMessageDefinition.focus.modifierExtensionElements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).'
WarningMessageDefinition.responseRequiredElements differ in description: 'HL7-defined table of codes which identify conditions under which acknowledgments are required to be returned in response to a message.' vs 'This enables the capability currently available through MSH-16 (Application Level acknowledgement) in HL7 Version 2 to declare at a message definition level whether a response is required or only upon error or success, or never.'
WarningMessageDefinition.responseRequiredElements differ in description: 'HL7-defined table of codes which identify conditions under which acknowledgments are required to be returned in response to a message.' vs 'This enables the capability currently available through MSH-16 (Application Level acknowledgement) in HL7 Version 2 to declare at a message definition level whether a response is required or only upon error or success, or never.'
WarningMessageDefinition.allowedResponse.extensionElements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.'
WarningMessageDefinition.allowedResponse.modifierExtensionElements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).'
WarningMessageDefinition.graphElements differ in definition: 'Canonical reference to a GraphDefinition. If a URL is provided, it is the canonical reference to a [GraphDefinition] that it controls what resources are to be added to the bundle when building the document. The GraphDefinition can also specify profiles that apply to the various resources.' vs 'Graph is Canonical reference to a GraphDefinition. If a URL is provided, it is the canonical reference to a GraphDefinition that it controls what additional resources are to be added to the Bundle when building the message. The GraphDefinition can also specify profiles that apply to the various resources.'
InformationMessageDefinition.graphElement maximum cardinalities differ: '2147483647' vs '1'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/MessageDefinition
      .copyright
        .date2020-04-02
          .descriptionThis profile constrains MessageDefinition in the context of messaging the content of catalogs, in conformance with the FHIR messaging framework
            .experimental
              .fhirVersion4.0.15.0.0
              • Values Differ
              .jurisdiction
                ..jurisdiction[0]http://unstats.un.org/unsd/methods/m49/m49.htm#001
                  .kindresource
                    .nameCatalogMessageDefinition
                      .publisherHL7 International - Orders and Observations Work Group
                        .purposeThis profile specifies the event codes that are available for messaging the content of catalogs between a system owning a catalog and a system interested in the catalog content, in whole or in part.
                          .statusdraft
                            .titleMessage definition for messaging order-catalog content
                              .typeMessageDefinition
                                .urlhttp://hl7.org/fhir/uv/order-catalog/StructureDefinition/CatalogMessageDefinition
                                  .version0.1.0current
                                  • Values Differ

                                  Structure

                                  NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.L TypeL Description & ConstraintsCommentsdoco
                                  .. MessageDefinition C0..*MessageDefinitionA resource that defines a type of message that can be exchanged between systems
                                  C0..*MessageDefinitionA resource that defines a type of message that can be exchanged between systems
                                    ... id Σ0..1stringLogical id of this artifactΣ0..1idLogical id of this artifact
                                    • Elements differ in comments: 'The only time that a resource does not have an id is when it is being submitted to the server using a create operation.' vs 'Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.'
                                    ... 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
                                      • Elements differ in comments: 'Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.' vs 'Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.'
                                      ... language 0..1codeLanguage of the resource content
                                      Binding: ?? (preferred): A human language.

                                      Additional BindingsPurpose
                                      ??Max Binding
                                      0..1codeLanguage of the resource content
                                      Binding: ?? (required): IETF language tag for a human language

                                      • Elements differ in binding.description: 'A human language.' vs 'IETF language tag for a human language'
                                      ... text 0..1NarrativeText summary of the resource, for human interpretation0..1NarrativeText summary of the resource, for human interpretation
                                      • Elements differ in comments: 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.' vs 'Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.'
                                      ... contained 0..*ResourceContained, inline Resources
                                      0..*ResourceContained, inline Resources
                                      • Elements differ in definition: 'These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.' vs 'These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.'
                                      ... extension 0..*ExtensionAdditional content defined by implementations
                                      0..*ExtensionAdditional content defined by implementations
                                      • Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.'
                                      ... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
                                      ?!Σ0..*ExtensionExtensions that cannot be ignored
                                      • Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).'
                                      ... url Σ0..1uriBusiness Identifier for a given MessageDefinitionΣC0..1uriThe cannonical URL for a given MessageDefinition
                                      • Elements differ in short: 'Business Identifier for a given MessageDefinition' vs 'The cannonical URL for a given MessageDefinition'
                                      ... identifier Σ0..*IdentifierPrimary key for the message definition on a given server
                                      Σ0..*IdentifierBusiness Identifier for a given MessageDefinition
                                      • Elements differ in short: 'Primary key for the message definition on a given server' vs 'Business Identifier for a given MessageDefinition'
                                      ... version Σ0..1stringBusiness version of the message definitionΣ0..1stringBusiness version of the message definition
                                      • Elements differ in comments: 'There may be different message definition instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the message definition with the format [url]|[version].' vs 'There may be different message definition instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the message definition with the format [url]|[version]. The version SHOULD NOT contain a '#' - see [Business Version].'
                                      ... name ΣC0..1stringName for this message definition (computer friendly)ΣC0..1stringName for this message definition (computer friendly)
                                        ... title Σ0..1stringName for this message definition (human friendly)Σ0..1stringName for this message definition (human friendly)
                                          ... replaces Σ0..*canonical(MessageDefinition)Takes the place of
                                          Σ0..*canonical(MessageDefinition)Takes the place of
                                            ... status ?!Σ1..1codedraft | active | retired | unknown
                                            Binding: ?? (required): The lifecycle status of an artifact.

                                            ?!Σ1..1codedraft | active | retired | unknown
                                            Binding: ?? (required): The lifecycle status of an artifact.

                                            • Elements differ in comments: 'Allows filtering of message definitions that are appropriate for use versus not.' vs 'Allows filtering of message definitions that are appropriate for use versus not. See guidance around (not) making local changes to elements [here].'
                                            ... experimental Σ0..1booleanFor testing purposes, not real usageΣ0..1booleanFor testing purposes, not real usage
                                              ... date Σ1..1dateTimeDate last changedΣ1..1dateTimeDate last changed
                                              • Elements differ in definition: 'The date (and optionally time) when the message definition was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the message definition changes.' vs 'The date (and optionally time) when the message definition was last significantly changed. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the message definition changes.'
                                              • Elements differ in comments: 'Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the message definition. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.' vs 'The date is often not tracked until the resource is published, but may be present on draft content. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the message definition. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource. See guidance around (not) making local changes to elements [here].'
                                              ... publisher Σ0..1stringName of the publisher (organization or individual)Σ0..1stringName of the publisher/steward (organization or individual)
                                              • Elements differ in short: 'Name of the publisher (organization or individual)' vs 'Name of the publisher/steward (organization or individual)'
                                              • Elements differ in definition: 'The name of the organization or individual that published the message definition.' vs 'The name of the organization or individual responsible for the release and ongoing maintenance of the message definition.'
                                              ... contact Σ0..*ContactDetailContact details for the publisher
                                              Σ0..*ContactDetailContact details for the publisher
                                              • Elements differ in comments: 'May be a web site, an email address, a telephone number, etc.' vs 'May be a web site, an email address, a telephone number, etc. See guidance around (not) making local changes to elements [here].'
                                              ... description Σ0..1markdownNatural language description of the message definitionΣ0..1markdownNatural language description of the message definition
                                              • Elements differ in comments: 'This description can be used to capture details such as why the message definition was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the message definition as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the message definition is presumed to be the predominant language in the place the message definition was created).' vs 'This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the message definition as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the message definition is presumed to be the predominant language in the place the message definition was created).'
                                              ... useContext Σ0..*UsageContextThe context that the content is intended to support
                                              Σ0..*UsageContextThe context that the content is intended to support
                                                ... jurisdiction Σ0..*CodeableConceptIntended jurisdiction for message definition (if applicable)
                                                Binding: ?? (extensible): Countries and regions within which this artifact is targeted for use.


                                                ΣXD0..*CodeableConceptIntended jurisdiction for message definition (if applicable)
                                                Binding: ?? (extensible): Countries and regions within which this artifact is targeted for use.


                                                • Elements differ in comments: 'It may be possible for the message definition to be used in jurisdictions other than those for which it was originally designed or intended.' vs 'It may be possible for the message definition to be used in jurisdictions other than those for which it was originally designed or intended. DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.)'
                                                ... purpose Σ0..1markdownWhy this message definition is definedΣ0..1markdownWhy this message definition is defined
                                                  ... copyright 0..1markdownUse and/or publishing restrictions0..1markdownUse and/or publishing restrictions
                                                    ... base Σ0..1canonical(MessageDefinition)Definition this one is based onΣ0..1canonical(MessageDefinition)Definition this one is based on
                                                      ... parent Σ0..*canonical(ActivityDefinition | PlanDefinition)Protocol/workflow this is part of
                                                      Σ0..*canonical(ActivityDefinition | PlanDefinition)Protocol/workflow this is part of
                                                        ... event[x] SΣ1..1CodingEvent code
                                                        Binding: ?? (extensible): message events for messages conveying order-catalog content

                                                        SΣ1..1CodingEvent code
                                                        Binding: ?? (extensible): message events for messages conveying order-catalog content

                                                          ... category Σ0..1codeconsequence | currency | notification
                                                          Binding: ?? (required): The impact of the content of a message.


                                                          Fixed Value: consequence
                                                          Σ0..1codeconsequence | currency | notification
                                                          Binding: ?? (required): The impact of the content of a message.


                                                          Fixed Value: consequence
                                                            ... focus ΣC0..*BackboneElementResource(s) that are the subject of the event
                                                            md-1: Max must be postive int or *
                                                            ΣC0..*BackboneElementResource(s) that are the subject of the event
                                                              .... 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
                                                                • Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.'
                                                                .... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                • Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).'
                                                                .... code Σ1..1codeType of resource
                                                                Binding: ?? (required): One of the resource types defined as part of this version of FHIR.

                                                                Σ1..1codeType of resource
                                                                Binding: ?? (required): One of the resource types defined as part of this version of FHIR.

                                                                  .... profile 0..1canonical(StructureDefinition)Profile that must be adhered to by focus0..1canonical(StructureDefinition)Profile that must be adhered to by focus
                                                                    .... min Σ1..1unsignedIntMinimum number of focuses of this typeΣ1..1unsignedIntMinimum number of focuses of this type
                                                                      .... max C0..1stringMaximum number of focuses of this typeC0..1stringMaximum number of focuses of this type
                                                                        ... responseRequired S1..1codealways | on-error | never | on-success
                                                                        Binding: ?? (required): HL7-defined table of codes which identify conditions under which acknowledgments are required to be returned in response to a message.


                                                                        Example General: always
                                                                        S1..1codealways | on-error | never | on-success
                                                                        Binding: ?? (required): This enables the capability currently available through MSH-16 (Application Level acknowledgement) in HL7 Version 2 to declare at a message definition level whether a response is required or only upon error or success, or never.


                                                                        Example General: always
                                                                        • Elements differ in description: 'HL7-defined table of codes which identify conditions under which acknowledgments are required to be returned in response to a message.' vs 'This enables the capability currently available through MSH-16 (Application Level acknowledgement) in HL7 Version 2 to declare at a message definition level whether a response is required or only upon error or success, or never.'
                                                                        • Elements differ in description: 'HL7-defined table of codes which identify conditions under which acknowledgments are required to be returned in response to a message.' vs 'This enables the capability currently available through MSH-16 (Application Level acknowledgement) in HL7 Version 2 to declare at a message definition level whether a response is required or only upon error or success, or never.'
                                                                        ... allowedResponse 0..*BackboneElementResponses to this message
                                                                        0..*BackboneElementResponses to this message
                                                                          .... 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
                                                                            • Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.'
                                                                            .... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                            ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                            • Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).'
                                                                            .... message 1..1canonical(MessageDefinition)Reference to allowed message definition response1..1canonical(MessageDefinition)Reference to allowed message definition response
                                                                              .... situation 0..1markdownWhen should this response be used0..1markdownWhen should this response be used
                                                                                ... graph 0..*canonical(GraphDefinition)Canonical reference to a GraphDefinition
                                                                                0..1canonical(GraphDefinition)Canonical reference to a GraphDefinition
                                                                                • Elements differ in definition: 'Canonical reference to a GraphDefinition. If a URL is provided, it is the canonical reference to a [GraphDefinition] that it controls what resources are to be added to the bundle when building the document. The GraphDefinition can also specify profiles that apply to the various resources.' vs 'Graph is Canonical reference to a GraphDefinition. If a URL is provided, it is the canonical reference to a GraphDefinition that it controls what additional resources are to be added to the Bundle when building the message. The GraphDefinition can also specify profiles that apply to the various resources.'
                                                                                • Element maximum cardinalities differ: '2147483647' vs '1'
                                                                                ... versionAlgorithm[x] Σ0..1string, CodingHow to compare versions
                                                                                Binding: ?? (extensible)
                                                                                • Added this element
                                                                                ... copyrightLabel 0..1stringCopyright holder and year(s)
                                                                                • Added this element

                                                                                doco Documentation for this format