ChargeItemDefinition
The ChargeItemDefinition profile that SAP Patient Management supports is the following:
ChargeItemDefinition | I | ChargeItemDefinition | There are no (further) constraints on this element Element idChargeItemDefinition Definition of properties and rules about how the price and the applicability of a ChargeItem can be determined DefinitionThe ChargeItemDefinition resource provides the properties that apply to the (billing) codes necessary to calculate costs and prices. The properties may differ largely depending on type and realm, therefore this resource gives only a rough structure and requires profiling for each type of billing code system.
| |
id | Σ | 0..1 | string | There are no (further) constraints on this element Element idChargeItemDefinition.id Logical id of this artifact DefinitionThe 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. |
meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idChargeItemDefinition.meta Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
|
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idChargeItemDefinition.implicitRules A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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.
|
language | 0..1 | codeBinding | There are no (further) constraints on this element Element idChargeItemDefinition.language Language of the resource content DefinitionThe 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). A human language.
| |
text | 0..1 | Narrative | There are no (further) constraints on this element Element idChargeItemDefinition.text Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA human-readable narrative that contains a summary of the resource and can 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 information is added later.
| |
contained | 0..* | Resource | There are no (further) constraints on this element Element idChargeItemDefinition.contained Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese 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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idChargeItemDefinition.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | ?! I | 0..* | Extension | There are no (further) constraints on this element Element idChargeItemDefinition.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
url | Σ | 1..1 | uri | There are no (further) constraints on this element Element idChargeItemDefinition.url Canonical identifier for this charge item definition, represented as a URI (globally unique) DefinitionAn 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. Allows the charge item definition to be referenced by a single globally unique identifier. 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.
|
identifier | S Σ | 0..* | Identifier | There are no (further) constraints on this element Element idChargeItemDefinition.identifier Additional identifier for the charge item definition DefinitionA formal identifier that is used to identify this charge item definition when it is represented in other formats, or referenced in a specification, model, design or an instance. Allows externally provided and/or usable business identifiers to be easily associated with the module. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this charge item definition outside of FHIR, where it is not possible to use the logical URI.
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idChargeItemDefinition.version Business version of the charge item definition DefinitionThe identifier that is used to identify this version of the charge item definition when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the charge item definition author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence. To provide a version consistent with the Decision Support Service specification, use the format Major.Minor.Revision (e.g. 1.0.0). For more information on versioning knowledge assets, refer to the Decision Support Service specification. Note that a version is required for non-experimental active assets. 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].
|
title | Σ | 0..1 | string | There are no (further) constraints on this element Element idChargeItemDefinition.title Name for this charge item definition (human friendly) DefinitionA short, descriptive, user-friendly title for the charge item definition. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.
|
derivedFromUri | Σ | 0..* | uri | There are no (further) constraints on this element Element idChargeItemDefinition.derivedFromUri Underlying externally-defined charge item definition DefinitionThe URL pointing to an externally-defined charge item definition that is adhered to in whole or in part by this definition. see http://en.wikipedia.org/wiki/Uniform_resource_identifier
|
partOf | Σ | 0..* | canonical(ChargeItemDefinition) | There are no (further) constraints on this element Element idChargeItemDefinition.partOf A larger definition of which this particular definition is a component or step Alternate namescontainer DefinitionA larger definition of which this particular definition is a component or step. canonical(ChargeItemDefinition) Constraints
|
replaces | Σ | 0..* | canonical(ChargeItemDefinition) | There are no (further) constraints on this element Element idChargeItemDefinition.replaces Completed or terminated request(s) whose function is taken by this new request Alternate namessupersedes, prior, renewed order DefinitionAs new versions of a protocol or guideline are defined, allows identification of what versions are replaced by a new instance. canonical(ChargeItemDefinition) Constraints
|
status | S Σ ?! | 1..1 | codeBinding | There are no (further) constraints on this element Element idChargeItemDefinition.status draft | active | retired | unknown DefinitionThe current state of the ChargeItemDefinition. Allows filtering of charge item definitions that are appropriate for use versus not. The lifecycle status of an artifact.
|
experimental | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idChargeItemDefinition.experimental For testing purposes, not real usage DefinitionA Boolean value to indicate that this charge item definition is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. Enables experimental content to be developed following the same lifecycle that would be used for a production-level charge item definition. Allows filtering of charge item definitions that are appropriate for use versus not.
|
date | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element idChargeItemDefinition.date Date last changed Alternate namesRevision Date DefinitionThe 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. 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.
|
publisher | Σ | 0..1 | string | There are no (further) constraints on this element Element idChargeItemDefinition.publisher Name of the publisher (organization or individual) DefinitionThe name of the organization or individual that published the charge item definition. Helps establish the "authority/credibility" of the charge item definition. May also allow for contact. 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.
|
contact | Σ | 0..* | ContactDetail | There are no (further) constraints on this element Element idChargeItemDefinition.contact Contact details for the publisher DefinitionContact details to assist a user in finding and communicating with the publisher. May be a web site, an email address, a telephone number, etc.
|
description | S Σ | 0..1 | markdown | There are no (further) constraints on this element Element idChargeItemDefinition.description Natural language description of the charge item definition DefinitionA free text natural language description of the charge item definition from a consumer's perspective. 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).
|
useContext | Σ | 0..* | UsageContext | There are no (further) constraints on this element Element idChargeItemDefinition.useContext The context that the content is intended to support DefinitionThe content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate charge item definition instances. Assist in searching for appropriate content. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.
|
jurisdiction | Σ | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idChargeItemDefinition.jurisdiction Intended jurisdiction for charge item definition (if applicable) DefinitionA legal or geographic region in which the charge item definition is intended to be used. 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. Countries and regions within which this artifact is targeted for use.
|
copyright | 0..1 | markdown | There are no (further) constraints on this element Element idChargeItemDefinition.copyright Use and/or publishing restrictions Alternate namesLicense, Restrictions DefinitionA copyright statement relating to the charge item definition and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the charge item definition. Consumers must be able to determine any legal restrictions on the use of the charge item definition and/or its content. Systems are not required to have markdown support, so the text should be readable without markdown processing. The markdown syntax is GFM - see https://github.github.com/gfm/
| |
approvalDate | 0..1 | date | There are no (further) constraints on this element Element idChargeItemDefinition.approvalDate When the charge item definition was approved by publisher DefinitionThe date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage. The 'date' element may be more recent than the approval date because of minor changes or editorial corrections.
| |
lastReviewDate | 0..1 | date | There are no (further) constraints on this element Element idChargeItemDefinition.lastReviewDate When the charge item definition was last reviewed DefinitionThe date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date. Gives a sense of how "current" the content is. Resources that have not been reviewed in a long time may have a risk of being less appropriate/relevant. If specified, this date follows the original approval date.
| |
effectivePeriod | S Σ I | 0..1 | Period | There are no (further) constraints on this element Element idChargeItemDefinition.effectivePeriod When the charge item definition is expected to be used DefinitionThe period during which the charge item definition content was or is planned to be in active use. Allows establishing a transition before a resource comes into effect and also allows for a sunsetting process when new versions of the charge item definition are or are expected to be used instead. The effective period for a charge item definition determines when the content is applicable for usage and is independent of publication and review dates. For example, a measure intended to be used for the year 2016 might be published in 2015.
|
code | S Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idChargeItemDefinition.code Billing codes or product types this definition applies to DefinitionThe defined billing details in this resource pertain to the given billing code. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Billing Code defined by this ChargeItemDefinition.
|
instance | I | 0..* | Reference(Medication | Substance | Device) | There are no (further) constraints on this element Element idChargeItemDefinition.instance Instances this definition applies to DefinitionThe defined billing details in this resource pertain to the given product instance(s). 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. Reference(Medication | Substance | Device) Constraints
|
applicability | 0..* | BackboneElement | There are no (further) constraints on this element Element idChargeItemDefinition.applicability Whether or not the billing code is applicable DefinitionExpressions that describe applicability criteria for the billing code. 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.
| |
id | 0..1 | string | There are no (further) constraints on this element Element idChargeItemDefinition.applicability.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idChargeItemDefinition.applicability.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idChargeItemDefinition.applicability.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
description | 0..1 | string | There are no (further) constraints on this element Element idChargeItemDefinition.applicability.description Natural language description of the condition DefinitionA brief, natural language description of the condition that effectively communicates the intended semantics. Note that FHIR strings SHALL NOT exceed 1MB in size
| |
language | 0..1 | string | There are no (further) constraints on this element Element idChargeItemDefinition.applicability.language Language of the expression DefinitionThe media type of the language for the expression, e.g. "text/cql" for Clinical Query Language expressions or "text/fhirpath" for FHIRPath expressions. Note that FHIR strings SHALL NOT exceed 1MB in size
| |
expression | 0..1 | string | There are no (further) constraints on this element Element idChargeItemDefinition.applicability.expression Boolean-valued expression DefinitionAn expression that returns true or false, indicating whether the condition is satisfied. When using FHIRPath expressions, the %context environment variable must be replaced at runtime with the ChargeItem resource to which this definition is applied. Please note that FHIRPath Expressions can only be evaluated in the scope of the current ChargeItem resource to which this definition is being applied. FHIRPath expressions can traverse into other resources linked from the ChargeItem resource, however, testing rules such as that a billing code may be billed only once per encounter need a wider scope. In such scenarios, CQL may be the appropriate choice.
| |
propertyGroup | 0..* | BackboneElement | There are no (further) constraints on this element Element idChargeItemDefinition.propertyGroup Group of properties which are applicable under the same conditions DefinitionGroup of properties which are applicable under the same conditions. If no applicability rules are established for the group, then all properties always apply.
| |
id | 0..1 | string | There are no (further) constraints on this element Element idChargeItemDefinition.propertyGroup.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idChargeItemDefinition.propertyGroup.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idChargeItemDefinition.propertyGroup.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
applicability | 0..* | see (applicability) | There are no (further) constraints on this element Element idChargeItemDefinition.propertyGroup.applicability Conditions under which the priceComponent is applicable DefinitionExpressions that describe applicability criteria for the priceComponent. 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.
| |
priceComponent | 0..* | BackboneElement | There are no (further) constraints on this element Element idChargeItemDefinition.propertyGroup.priceComponent Components of total line item price DefinitionThe price for a ChargeItem may be calculated as a base price with surcharges/deductions that apply in certain conditions. A ChargeItemDefinition resource that defines the prices, factors and conditions that apply to a billing code is currently under development. The priceComponent element can be used to offer transparency to the recipient of the Invoice of how the prices have been calculated.
| |
id | 0..1 | string | There are no (further) constraints on this element Element idChargeItemDefinition.propertyGroup.priceComponent.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idChargeItemDefinition.propertyGroup.priceComponent.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idChargeItemDefinition.propertyGroup.priceComponent.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
type | 1..1 | codeBinding | There are no (further) constraints on this element Element idChargeItemDefinition.propertyGroup.priceComponent.type base | surcharge | deduction | discount | tax | informational DefinitionThis code identifies the type of the component. Note that FHIR strings SHALL NOT exceed 1MB in size Codes indicating the kind of the price component.
| |
code | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idChargeItemDefinition.propertyGroup.priceComponent.code Code identifying the specific component DefinitionA code that identifies the component. Codes may be used to differentiate between kinds of taxes, surcharges, discounts etc. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
| |
factor | 0..1 | decimal | There are no (further) constraints on this element Element idChargeItemDefinition.propertyGroup.priceComponent.factor Factor used for calculating this component DefinitionThe factor that has been applied on the base price for calculating this component. Do not use an IEEE type floating point type, instead use something that works like a true decimal, with inbuilt precision (e.g. Java BigInteger)
| |
amount | 0..1 | Money | There are no (further) constraints on this element Element idChargeItemDefinition.propertyGroup.priceComponent.amount Monetary amount associated with this component DefinitionThe amount calculated for this component.
|