Basic is used for handling concepts not yet defined in FHIR, narrative-only resources that don't map to an existing resource, and custom resources not appropriate for inclusion in the FHIR specification.

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.

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.

This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.

An Extension

R5: ChargeItemDefinition.url (new:uri)

Element ChargeItemDefinition.url is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.url has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version.

The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in Technical and Business Versions.

In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the meta.source element to indicate where the current master source of the resource can be found.

R5: ChargeItemDefinition.version (new:string)

Element ChargeItemDefinition.version is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.version has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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.

R5: ChargeItemDefinition.versionAlgorithm[x] (new:Coding, string)

Element ChargeItemDefinition.versionAlgorithm[x] is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.versionAlgorithm[x] has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). If set as a string, this is a FHIRPath expression that has two additional context variables passed in - %version1 and %version2 and will return a negative number if version1 is newer, a positive number if version2 and a 0 if the version ordering can't be successfully be determined.

R5: ChargeItemDefinition.name (new:string)

Element ChargeItemDefinition.name is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.name has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.

R5: ChargeItemDefinition.title (new:string)

Element ChargeItemDefinition.title is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.title has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.

R5: ChargeItemDefinition.derivedFromUri (new:uri)

Element ChargeItemDefinition.derivedFromUri is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.derivedFromUri has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: ChargeItemDefinition.partOf (new:canonical(ChargeItemDefinition))

Element ChargeItemDefinition.partOf is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.partOf has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: ChargeItemDefinition.replaces (new:canonical(ChargeItemDefinition))

Element ChargeItemDefinition.replaces is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.replaces has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: ChargeItemDefinition.experimental (new:boolean)

Element ChargeItemDefinition.experimental is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.experimental has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Allows filtering of charge item definitions that are appropriate for use versus not.

R5: ChargeItemDefinition.date (new:dateTime)

Element ChargeItemDefinition.date is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.date has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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.

R5: ChargeItemDefinition.publisher (new:string)

Element ChargeItemDefinition.publisher is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.publisher has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Usually an organization but may be an individual. The publisher (or steward) of the charge item definition is the organization or individual primarily responsible for the maintenance and upkeep of the charge item definition. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the charge item definition. This item SHOULD be populated unless the information is available from context.

R5: ChargeItemDefinition.contact (new:ContactDetail)

Element ChargeItemDefinition.contact is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.contact has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). May be a web site, an email address, a telephone number, etc.

See guidance around (not) making local changes to elements here.

R5: ChargeItemDefinition.description (new:markdown)

Element ChargeItemDefinition.description is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.description has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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).

R5: ChargeItemDefinition.useContext (new:UsageContext)

Element ChargeItemDefinition.useContext is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.useContext has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.

R5: ChargeItemDefinition.jurisdiction (new:CodeableConcept)

Element ChargeItemDefinition.jurisdiction is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.jurisdiction has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Element ChargeItemDefinition.jurisdiction has been flagged as deprecated. 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.)

R5: ChargeItemDefinition.purpose (new:markdown)

Element ChargeItemDefinition.purpose is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.purpose has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). This element does not describe the usage of the charge item definition. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this charge item definition.

R5: ChargeItemDefinition.copyright (new:markdown)

Element ChargeItemDefinition.copyright is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.copyright has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: ChargeItemDefinition.copyrightLabel (new:string)

Element ChargeItemDefinition.copyrightLabel is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.copyrightLabel has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). The (c) symbol should NOT be included in this string. It will be added by software when rendering the notation. Full details about licensing, restrictions, warrantees, etc. goes in the more general 'copyright' element.

R5: ChargeItemDefinition.approvalDate (new:date)

Element ChargeItemDefinition.approvalDate is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.approvalDate has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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.

R5: ChargeItemDefinition.lastReviewDate (new:date)

Element ChargeItemDefinition.lastReviewDate is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.lastReviewDate has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). If specified, this date follows the original approval date.

See guidance around (not) making local changes to elements here.

R5: ChargeItemDefinition.code (new:CodeableConcept)

Element ChargeItemDefinition.code is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.code has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: ChargeItemDefinition.instance (new:Reference(Medication,Substance,Device,DeviceDefinition,ActivityDefinition,PlanDefinition,HealthcareService))

Element ChargeItemDefinition.instance is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.instance has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). In case of highly customized, individually produced or fitted devices/substances, the pricing information may be different for each instance of the product. This reference links pricing details to specific product instances.

R5: ChargeItemDefinition.applicability (new:BackboneElement)

Element ChargeItemDefinition.applicability is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.applicability has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). The applicability conditions can be used to ascertain whether a billing item is allowed in a specific context. E.g. some billing codes may only be applicable in out-patient settings, only to male/female patients or only to children.

R5: ChargeItemDefinition.propertyGroup (new:BackboneElement)

Element ChargeItemDefinition.propertyGroup is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.propertyGroup has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: ChargeItemDefinition.propertyGroup.applicability (new:ChargeItemDefinition.applicability)

Element ChargeItemDefinition.propertyGroup.applicability is part of an existing definition because parent element ChargeItemDefinition.propertyGroup requires a cross-version extension. Element ChargeItemDefinition.propertyGroup.applicability is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.propertyGroup.applicability has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). The applicability conditions can be used to ascertain whether a billing item is allowed in a specific context. E.g. some billing codes may only be applicable in out-patient settings, only to male/female patients or only to children.

An Extension

R5: ChargeItemDefinition.status (new:code)

Element ChargeItemDefinition.status is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.status has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Allows filtering of charge item definitions that are appropriate for use versus not.

See guidance around (not) making local changes to elements here.

Identifies the 'type' of resource - equivalent to the resource name for other resources.

Because resource references will only be able to indicate 'Basic', the type of reference will need to be specified in a Profile identified as part of the resource. Refer to the resource notes section for information on appropriate terminologies for this code.

This element is labeled as a modifier because the it defines the meaning of the resource and cannot be ignored.

Codes for identifying types of resources not yet defined by FHIR

Must be able to distinguish different types of Basic resources.

R5: ChargeItemDefinition.url (new:uri)

Element ChargeItemDefinition.url is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.url has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version.

The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in Technical and Business Versions.

In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the meta.source element to indicate where the current master source of the resource can be found.

R5: ChargeItemDefinition.version (new:string)

Element ChargeItemDefinition.version is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.version has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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.

R5: ChargeItemDefinition.versionAlgorithm[x] (new:Coding, string)

Element ChargeItemDefinition.versionAlgorithm[x] is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.versionAlgorithm[x] has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). If set as a string, this is a FHIRPath expression that has two additional context variables passed in - %version1 and %version2 and will return a negative number if version1 is newer, a positive number if version2 and a 0 if the version ordering can't be successfully be determined.

R5: ChargeItemDefinition.name (new:string)

Element ChargeItemDefinition.name is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.name has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.

R5: ChargeItemDefinition.title (new:string)

Element ChargeItemDefinition.title is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.title has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.

R5: ChargeItemDefinition.derivedFromUri (new:uri)

Element ChargeItemDefinition.derivedFromUri is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.derivedFromUri has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: ChargeItemDefinition.partOf (new:canonical(ChargeItemDefinition))

Element ChargeItemDefinition.partOf is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.partOf has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: ChargeItemDefinition.replaces (new:canonical(ChargeItemDefinition))

Element ChargeItemDefinition.replaces is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.replaces has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: ChargeItemDefinition.experimental (new:boolean)

Element ChargeItemDefinition.experimental is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.experimental has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Allows filtering of charge item definitions that are appropriate for use versus not.

R5: ChargeItemDefinition.date (new:dateTime)

Element ChargeItemDefinition.date is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.date has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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.

R5: ChargeItemDefinition.publisher (new:string)

Element ChargeItemDefinition.publisher is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.publisher has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Usually an organization but may be an individual. The publisher (or steward) of the charge item definition is the organization or individual primarily responsible for the maintenance and upkeep of the charge item definition. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the charge item definition. This item SHOULD be populated unless the information is available from context.

R5: ChargeItemDefinition.contact (new:ContactDetail)

Element ChargeItemDefinition.contact is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.contact has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). May be a web site, an email address, a telephone number, etc.

See guidance around (not) making local changes to elements here.

R5: ChargeItemDefinition.description (new:markdown)

Element ChargeItemDefinition.description is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.description has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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).

R5: ChargeItemDefinition.useContext (new:UsageContext)

Element ChargeItemDefinition.useContext is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.useContext has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.

R5: ChargeItemDefinition.jurisdiction (new:CodeableConcept)

Element ChargeItemDefinition.jurisdiction is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.jurisdiction has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Element ChargeItemDefinition.jurisdiction has been flagged as deprecated. 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.)

R5: ChargeItemDefinition.purpose (new:markdown)

Element ChargeItemDefinition.purpose is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.purpose has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). This element does not describe the usage of the charge item definition. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this charge item definition.

R5: ChargeItemDefinition.copyright (new:markdown)

Element ChargeItemDefinition.copyright is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.copyright has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: ChargeItemDefinition.copyrightLabel (new:string)

Element ChargeItemDefinition.copyrightLabel is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.copyrightLabel has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). The (c) symbol should NOT be included in this string. It will be added by software when rendering the notation. Full details about licensing, restrictions, warrantees, etc. goes in the more general 'copyright' element.

R5: ChargeItemDefinition.approvalDate (new:date)

Element ChargeItemDefinition.approvalDate is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.approvalDate has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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.

R5: ChargeItemDefinition.lastReviewDate (new:date)

Element ChargeItemDefinition.lastReviewDate is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.lastReviewDate has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). If specified, this date follows the original approval date.

See guidance around (not) making local changes to elements here.

R5: ChargeItemDefinition.code (new:CodeableConcept)

Element ChargeItemDefinition.code is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.code has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: ChargeItemDefinition.instance (new:Reference(Medication,Substance,Device,DeviceDefinition,ActivityDefinition,PlanDefinition,HealthcareService))

Element ChargeItemDefinition.instance is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.instance has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). In case of highly customized, individually produced or fitted devices/substances, the pricing information may be different for each instance of the product. This reference links pricing details to specific product instances.

R5: ChargeItemDefinition.applicability (new:BackboneElement)

Element ChargeItemDefinition.applicability is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.applicability has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). The applicability conditions can be used to ascertain whether a billing item is allowed in a specific context. E.g. some billing codes may only be applicable in out-patient settings, only to male/female patients or only to children.

R5: ChargeItemDefinition.propertyGroup (new:BackboneElement)

Element ChargeItemDefinition.propertyGroup is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.propertyGroup has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: ChargeItemDefinition.propertyGroup.applicability (new:ChargeItemDefinition.applicability)

Element ChargeItemDefinition.propertyGroup.applicability is part of an existing definition because parent element ChargeItemDefinition.propertyGroup requires a cross-version extension. Element ChargeItemDefinition.propertyGroup.applicability is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.propertyGroup.applicability has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). The applicability conditions can be used to ascertain whether a billing item is allowed in a specific context. E.g. some billing codes may only be applicable in out-patient settings, only to male/female patients or only to children.

R5: ChargeItemDefinition.status (new:code)

Element ChargeItemDefinition.status is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.status has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Allows filtering of charge item definitions that are appropriate for use versus not.

See guidance around (not) making local changes to elements here.

Basic is used for handling concepts not yet defined in FHIR, narrative-only resources that don't map to an existing resource, and custom resources not appropriate for inclusion in the FHIR specification.

The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

The only time that a resource does not have an id is when it is being submitted to the server using a create operation.

The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource.

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.

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.

This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.

The base language in which the resource is written.

Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).

Unless not suitable, these codes SHALL be taken from Common Languages
(extensible to http://hl7.org/fhir/ValueSet/languages|3.0.2)

A human language.

A human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.

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 in formation is added later.

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.

This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again.

An Extension

R5: ChargeItemDefinition.url (new:uri)

Element ChargeItemDefinition.url is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.url has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version.

The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in Technical and Business Versions.

In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the meta.source element to indicate where the current master source of the resource can be found.

R5: ChargeItemDefinition.version (new:string)

Element ChargeItemDefinition.version is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.version has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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.

R5: ChargeItemDefinition.versionAlgorithm[x] (new:Coding, string)

Element ChargeItemDefinition.versionAlgorithm[x] is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.versionAlgorithm[x] has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). If set as a string, this is a FHIRPath expression that has two additional context variables passed in - %version1 and %version2 and will return a negative number if version1 is newer, a positive number if version2 and a 0 if the version ordering can't be successfully be determined.

R5: ChargeItemDefinition.name (new:string)

Element ChargeItemDefinition.name is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.name has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.

R5: ChargeItemDefinition.title (new:string)

Element ChargeItemDefinition.title is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.title has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.

R5: ChargeItemDefinition.derivedFromUri (new:uri)

Element ChargeItemDefinition.derivedFromUri is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.derivedFromUri has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: ChargeItemDefinition.partOf (new:canonical(ChargeItemDefinition))

Element ChargeItemDefinition.partOf is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.partOf has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: ChargeItemDefinition.replaces (new:canonical(ChargeItemDefinition))

Element ChargeItemDefinition.replaces is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.replaces has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: ChargeItemDefinition.experimental (new:boolean)

Element ChargeItemDefinition.experimental is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.experimental has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Allows filtering of charge item definitions that are appropriate for use versus not.

R5: ChargeItemDefinition.date (new:dateTime)

Element ChargeItemDefinition.date is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.date has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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.

R5: ChargeItemDefinition.publisher (new:string)

Element ChargeItemDefinition.publisher is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.publisher has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Usually an organization but may be an individual. The publisher (or steward) of the charge item definition is the organization or individual primarily responsible for the maintenance and upkeep of the charge item definition. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the charge item definition. This item SHOULD be populated unless the information is available from context.

R5: ChargeItemDefinition.contact (new:ContactDetail)

Element ChargeItemDefinition.contact is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.contact has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). May be a web site, an email address, a telephone number, etc.

See guidance around (not) making local changes to elements here.

R5: ChargeItemDefinition.description (new:markdown)

Element ChargeItemDefinition.description is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.description has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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).

R5: ChargeItemDefinition.useContext (new:UsageContext)

Element ChargeItemDefinition.useContext is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.useContext has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.

R5: ChargeItemDefinition.jurisdiction (new:CodeableConcept)

Element ChargeItemDefinition.jurisdiction is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.jurisdiction has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Element ChargeItemDefinition.jurisdiction has been flagged as deprecated. 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.)

R5: ChargeItemDefinition.purpose (new:markdown)

Element ChargeItemDefinition.purpose is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.purpose has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). This element does not describe the usage of the charge item definition. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this charge item definition.

R5: ChargeItemDefinition.copyright (new:markdown)

Element ChargeItemDefinition.copyright is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.copyright has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: ChargeItemDefinition.copyrightLabel (new:string)

Element ChargeItemDefinition.copyrightLabel is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.copyrightLabel has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). The (c) symbol should NOT be included in this string. It will be added by software when rendering the notation. Full details about licensing, restrictions, warrantees, etc. goes in the more general 'copyright' element.

R5: ChargeItemDefinition.approvalDate (new:date)

Element ChargeItemDefinition.approvalDate is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.approvalDate has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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.

R5: ChargeItemDefinition.lastReviewDate (new:date)

Element ChargeItemDefinition.lastReviewDate is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.lastReviewDate has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). If specified, this date follows the original approval date.

See guidance around (not) making local changes to elements here.

R5: ChargeItemDefinition.code (new:CodeableConcept)

Element ChargeItemDefinition.code is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.code has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: ChargeItemDefinition.instance (new:Reference(Medication,Substance,Device,DeviceDefinition,ActivityDefinition,PlanDefinition,HealthcareService))

Element ChargeItemDefinition.instance is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.instance has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). In case of highly customized, individually produced or fitted devices/substances, the pricing information may be different for each instance of the product. This reference links pricing details to specific product instances.

R5: ChargeItemDefinition.applicability (new:BackboneElement)

Element ChargeItemDefinition.applicability is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.applicability has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). The applicability conditions can be used to ascertain whether a billing item is allowed in a specific context. E.g. some billing codes may only be applicable in out-patient settings, only to male/female patients or only to children.

R5: ChargeItemDefinition.propertyGroup (new:BackboneElement)

Element ChargeItemDefinition.propertyGroup is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.propertyGroup has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: ChargeItemDefinition.propertyGroup.applicability (new:ChargeItemDefinition.applicability)

Element ChargeItemDefinition.propertyGroup.applicability is part of an existing definition because parent element ChargeItemDefinition.propertyGroup requires a cross-version extension. Element ChargeItemDefinition.propertyGroup.applicability is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.propertyGroup.applicability has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). The applicability conditions can be used to ascertain whether a billing item is allowed in a specific context. E.g. some billing codes may only be applicable in out-patient settings, only to male/female patients or only to children.

An Extension

R5: ChargeItemDefinition.status (new:code)

Element ChargeItemDefinition.status is not mapped to FHIR STU3, since FHIR R5 ChargeItemDefinition is not mapped. Element ChargeItemDefinition.status has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Allows filtering of charge item definitions that are appropriate for use versus not.

See guidance around (not) making local changes to elements here.

Identifier assigned to the resource for business purposes, outside the context of FHIR.

Identifies the 'type' of resource - equivalent to the resource name for other resources.

Because resource references will only be able to indicate 'Basic', the type of reference will need to be specified in a Profile identified as part of the resource. Refer to the resource notes section for information on appropriate terminologies for this code.

This element is labeled as a modifier because the it defines the meaning of the resource and cannot be ignored.

Codes for identifying types of resources not yet defined by FHIR

Must be able to distinguish different types of Basic resources.

Identifies the patient, practitioner, device or any other resource that is the "focus" of this resource.

Optional as not all potential resources will have subjects. Resources associated with multiple subjects can handle this via extension.

Needed for partitioning the resource by Patient.

Identifies when the resource was first created.

Allows ordering resource instances by time.

Indicates who was responsible for creating the resource instance.

Needed for partitioning the resource.