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

Left:Laboratory Service Charge Item Definition (http://hl7.org/fhir/uv/order-catalog/StructureDefinition/LabChargeItemDefinition)
Right:Laboratory Service Charge Item Definition (http://hl7.org/fhir/uv/order-catalog/StructureDefinition/LabChargeItemDefinition)

Messages

ErrorStructureDefinition.versionValues for version differ: '0.1.0' vs 'current'
WarningStructureDefinition.fhirVersionValues for fhirVersion differ: '4.0.1' vs '5.0.0'
WarningChargeItemDefinition.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.'
WarningChargeItemDefinition.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.'
WarningChargeItemDefinition.languageElements differ in binding.description: 'A human language.' vs 'IETF language tag for a human language'
WarningChargeItemDefinition.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.'
WarningChargeItemDefinition.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.'
WarningChargeItemDefinition.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.'
WarningChargeItemDefinition.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).'
WarningChargeItemDefinition.urlElements differ in definition: 'An absolute URI that is used to identify this charge item definition when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this charge item definition is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the charge item definition is stored on different servers.' vs 'An absolute URI that is used to identify this charge item definition when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which an authoritative instance of this charge item definition is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the charge item definition is stored on different servers.'
InformationChargeItemDefinition.urlElement minimum cardinalities differ: '1' vs '0'
WarningChargeItemDefinition.versionElements differ in comments: 'There may be different charge item 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 charge item definition with the format [url]|[version].' vs 'There may be different charge item 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 charge item definition with the format [url]|[version]. The version SHOULD NOT contain a '#' - see [Business Version].'
WarningChargeItemDefinition.statusElements differ in comments: 'Allows filtering of charge item definitions that are appropriate for use versus not.' vs 'Allows filtering of charge item definitions that are appropriate for use versus not. See guidance around (not) making local changes to elements [here].'
WarningChargeItemDefinition.dateElements differ in definition: 'The date (and optionally time) when the charge item 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 charge item definition changes.' vs 'The date (and optionally time) when the charge item 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 charge item definition changes.'
WarningChargeItemDefinition.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 charge item 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 charge item 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].'
WarningChargeItemDefinition.publisherElements differ in short: 'Name of the publisher (organization or individual)' vs 'Name of the publisher/steward (organization or individual)'
WarningChargeItemDefinition.publisherElements differ in definition: 'The name of the organization or individual that published the charge item definition.' vs 'The name of the organization or individual responsible for the release and ongoing maintenance of the charge item definition.'
WarningChargeItemDefinition.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].'
WarningChargeItemDefinition.descriptionElements differ in comments: 'This description can be used to capture details such as why the charge item 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 charge item 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 charge item definition is presumed to be the predominant language in the place the charge item 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 charge item 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 charge item definition is presumed to be the predominant language in the place the charge item definition was created).'
WarningChargeItemDefinition.jurisdictionElements differ in comments: 'It may be possible for the charge item definition to be used in jurisdictions other than those for which it was originally designed or intended.' vs 'It may be possible for the charge item 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.)'
WarningChargeItemDefinition.approvalDateElements differ in comments: 'The 'date' element may be more recent than the approval date because of minor changes or editorial corrections.' vs 'The 'date' element may be more recent than the approval date because of minor changes or editorial corrections. See guidance around (not) making local changes to elements [here].'
WarningChargeItemDefinition.lastReviewDateElements differ in short: 'When the charge item definition was last reviewed' vs 'When the charge item definition was last reviewed by the publisher'
WarningChargeItemDefinition.lastReviewDateElements differ in comments: 'If specified, this date follows the original approval date.' vs 'If specified, this date follows the original approval date. See guidance around (not) making local changes to elements [here].'
WarningChargeItemDefinition.codeElements differ in short: 'Billing codes or product types this definition applies to' vs 'Billing code or product type this definition applies to'
WarningChargeItemDefinition.applicability.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.'
WarningChargeItemDefinition.applicability.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).'
WarningChargeItemDefinition.propertyGroup.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.'
WarningChargeItemDefinition.propertyGroup.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).'
WarningChargeItemDefinition.propertyGroup.priceComponent.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.'
WarningChargeItemDefinition.propertyGroup.priceComponent.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).'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/ChargeItemDefinition
      .copyright
        .date2020-02-09
          .descriptionThis profile constrains the usage of ChargeItemDefinition to represent the rules and other properties attached to a billing code used by a laboratory service
            .experimental
              .fhirVersion4.0.15.0.0
              • Values Differ
              .jurisdiction
                ..jurisdiction[0]http://unstats.un.org/unsd/methods/m49/m49.htm#001
                  .kindresource
                    .nameLabChargeItemDefinition
                      .publisherHL7 International - Orders and Observations Work Group
                        .purpose
                          .statusdraft
                            .titleLaboratory Service Charge Item Definition
                              .typeChargeItemDefinition
                                .urlhttp://hl7.org/fhir/uv/order-catalog/StructureDefinition/LabChargeItemDefinition
                                  .version0.1.0current
                                  • Values Differ

                                  Structure

                                  NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.L TypeL Description & ConstraintsCommentsdoco
                                  .. ChargeItemDefinition C0..*ChargeItemDefinitionDefinition of properties and rules about how the price and the applicability of a ChargeItem can be determined
                                  C0..*ChargeItemDefinitionDefinition of properties and rules about how the price and the applicability of a ChargeItem can be determined
                                    ... 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 Σ1..1uriCanonical identifier for this charge item definition, represented as a URI (globally unique)ΣC0..1uriCanonical identifier for this charge item definition, represented as a URI (globally unique)
                                      • Elements differ in definition: 'An absolute URI that is used to identify this charge item definition when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this charge item definition is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the charge item definition is stored on different servers.' vs 'An absolute URI that is used to identify this charge item definition when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which an authoritative instance of this charge item definition is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the charge item definition is stored on different servers.'
                                      • Element minimum cardinalities differ: '1' vs '0'
                                      ... identifier Σ0..*IdentifierAdditional identifier for the charge item definition
                                      Σ0..*IdentifierAdditional identifier for the charge item definition
                                        ... version Σ0..1stringBusiness version of the charge item definitionΣ0..1stringBusiness version of the charge item definition
                                        • Elements differ in comments: 'There may be different charge item 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 charge item definition with the format [url]|[version].' vs 'There may be different charge item 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 charge item definition with the format [url]|[version]. The version SHOULD NOT contain a '#' - see [Business Version].'
                                        ... title Σ0..1stringName for this charge item definition (human friendly)Σ0..1stringName for this charge item definition (human friendly)
                                          .... id 0..1stringxml:id (or equivalent in JSON)0..1stringxml:id (or equivalent in JSON)
                                            .... Slices for extension 0..*ExtensionExtension
                                            Slice: Unordered, Open by value:url
                                            0..*ExtensionExtension
                                            Slice: Unordered, Open by value:url
                                              .... value 0..1stringPrimitive value for string
                                              Max Length: 1048576
                                              0..1stringPrimitive value for string
                                              Max Length: 1048576
                                                ... derivedFromUri Σ0..*uriUnderlying externally-defined charge item definition
                                                Σ0..*uriUnderlying externally-defined charge item definition
                                                  ... partOf Σ0..*canonical(ChargeItemDefinition)A larger definition of which this particular definition is a component or step
                                                  Σ0..*canonical(ChargeItemDefinition)A larger definition of which this particular definition is a component or step
                                                    ... replaces Σ0..*canonical(ChargeItemDefinition)Completed or terminated request(s) whose function is taken by this new request
                                                    Σ0..*canonical(ChargeItemDefinition)Completed or terminated request(s) whose function is taken by this new request
                                                      ... 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 charge item definitions that are appropriate for use versus not.' vs 'Allows filtering of charge item 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 Σ0..1dateTimeDate last changedΣ0..1dateTimeDate last changed
                                                        • Elements differ in definition: 'The date (and optionally time) when the charge item 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 charge item definition changes.' vs 'The date (and optionally time) when the charge item 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 charge item 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 charge item 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 charge item 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 charge item definition.' vs 'The name of the organization or individual responsible for the release and ongoing maintenance of the charge item 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 charge item definitionΣ0..1markdownNatural language description of the charge item definition
                                                        • Elements differ in comments: 'This description can be used to capture details such as why the charge item 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 charge item 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 charge item definition is presumed to be the predominant language in the place the charge item 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 charge item 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 charge item definition is presumed to be the predominant language in the place the charge item definition was created).'
                                                        ... Slices for useContext SΣ0..*UsageContextThe context that the content is intended to support
                                                        Slice: Unordered, Open by value:code.system, value:code.code
                                                        SΣ0..*UsageContextThe context that the content is intended to support
                                                        Slice: Unordered, Open by value:code.system, value:code.code
                                                          ... jurisdiction Σ0..*CodeableConceptIntended jurisdiction for charge item definition (if applicable)
                                                          Binding: ?? (extensible): Countries and regions within which this artifact is targeted for use.


                                                          ΣXD0..*CodeableConceptIntended jurisdiction for charge item 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 charge item definition to be used in jurisdictions other than those for which it was originally designed or intended.' vs 'It may be possible for the charge item 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.)'
                                                          ... copyright 0..1markdownUse and/or publishing restrictions0..1markdownUse and/or publishing restrictions
                                                            ... approvalDate 0..1dateWhen the charge item definition was approved by publisher0..1dateWhen the charge item definition was approved by publisher
                                                            • Elements differ in comments: 'The 'date' element may be more recent than the approval date because of minor changes or editorial corrections.' vs 'The 'date' element may be more recent than the approval date because of minor changes or editorial corrections. See guidance around (not) making local changes to elements [here].'
                                                            ... lastReviewDate 0..1dateWhen the charge item definition was last reviewed0..1dateWhen the charge item definition was last reviewed by the publisher
                                                            • Elements differ in short: 'When the charge item definition was last reviewed' vs 'When the charge item definition was last reviewed by the publisher'
                                                            • Elements differ in comments: 'If specified, this date follows the original approval date.' vs 'If specified, this date follows the original approval date. See guidance around (not) making local changes to elements [here].'
                                                            ... effectivePeriod Σ0..1PeriodWhen the charge item definition is expected to be used
                                                            • Removed this element
                                                            ... code SΣ1..1CodeableConceptBilling codes or product types this definition applies to
                                                            Binding: ?? (example): Billing Code defined by this ChargeItemDefinition.

                                                            SΣ1..1CodeableConceptBilling code or product type this definition applies to
                                                            Binding: ?? (example): Billing Code defined by this ChargeItemDefinition.

                                                            • Elements differ in short: 'Billing codes or product types this definition applies to' vs 'Billing code or product type this definition applies to'
                                                            ... instance 0..*Reference(Medication | Substance | Device)Instances this definition applies to
                                                            0..*Reference(Medication | Substance | Device | DeviceDefinition | ActivityDefinition | PlanDefinition | HealthcareService)Instances this definition applies to
                                                              ... applicability 0..*BackboneElementWhether or not the billing code is applicable
                                                              0..*BackboneElementWhether or not the billing code is applicable
                                                                .... 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).'
                                                                  .... description 0..1stringNatural language description of the condition
                                                                  • Removed this element
                                                                  .... language 0..1stringLanguage of the expression
                                                                  • Removed this element
                                                                  .... expression 0..1stringBoolean-valued expression
                                                                  • Removed this element
                                                                  .... condition 0..1ExpressionBoolean-valued expression
                                                                  • Added this element
                                                                  .... effectivePeriod Σ0..1PeriodWhen the charge item definition is expected to be used
                                                                  • Added this element
                                                                  .... relatedArtifact 0..1RelatedArtifactReference to / quotation of the external source of the group of properties
                                                                  • Added this element
                                                                  ... propertyGroup 0..*BackboneElementGroup of properties which are applicable under the same conditions
                                                                  0..*BackboneElementGroup of properties which are applicable under the same conditions
                                                                    .... 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).'
                                                                      .... applicability 0..*See applicabilityConditions under which the priceComponent is applicable
                                                                      0..*See applicability (ChargeItemDefinition)Conditions under which the priceComponent is applicable
                                                                        .... priceComponent 0..*BackboneElementComponents of total line item price
                                                                        0..*MonetaryComponentComponents of total line item price
                                                                          ..... id 0..1stringUnique id for inter-element referencing0..1idUnique id for inter-element referencing
                                                                            ..... extension 0..*ExtensionAdditional content defined by implementations
                                                                            0..*ExtensionAdditional content defined by implementations
                                                                            Slice: Unordered, Open by value:url
                                                                            • 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).'
                                                                            ..... type 1..1codebase | surcharge | deduction | discount | tax | informational
                                                                            Binding: ?? (required): Codes indicating the kind of the price component.

                                                                            • Removed this element
                                                                            ..... code 0..1CodeableConceptCode identifying the specific component
                                                                            • Removed this element
                                                                            ..... factor 0..1decimalFactor used for calculating this component
                                                                            • Removed this element
                                                                            ..... amount 0..1MoneyMonetary amount associated with this component
                                                                            • Removed this element
                                                                            ... versionAlgorithm[x] Σ0..1string, CodingHow to compare versions
                                                                            Binding: ?? (extensible)
                                                                            • Added this element
                                                                            ... name ΣC0..1stringName for this charge item definition (computer friendly)
                                                                            • Added this element
                                                                            ... purpose 0..1markdownWhy this charge item definition is defined
                                                                            • Added this element
                                                                            ... copyrightLabel 0..1stringCopyright holder and year(s)
                                                                            • Added this element

                                                                            doco Documentation for this format