Generated Narrative: StructureDefinition HealthAppPrescriptionUnit Name Flags Card. Type Description & Constraints<img src="[binary]" alt="doco" style="background-color: inherit"/> ChargeItemDefinition S 0..* ChargeItemDefinition Anwendungs- bzw. Verordnungseinheit #xD; Slices for extension Content/Rules for all slices #xD; extension:anwendungsdauer 0..1 Duration Anwendungsdauer URL: https://fhir.bfarm.de/StructureDefinition/HealthAppPrescriptionUnitAnwendungsdauer #xD; extension:ergaenzendeUnterstuetzungsleistungen 0..1 (Complex) Ergänzende Unterstützungsleistungen URL: https://fhir.bfarm.de/StructureDefinition/HealthAppPrescriptionUnitErgaenzendeUnterstuetzungsleistungen #xD; extension:indikation 0..1 (Complex) Indikationen URL: https://fhir.bfarm.de/StructureDefinition/HealthAppPrescriptionUnitIndikation #xD; extension:kontraindikation 0..1 (Complex) Kontraindikationen URL: https://fhir.bfarm.de/StructureDefinition/HealthAppPrescriptionUnitKontraindikation #xD; extension:vertragsaerztlicheLeistungen 0..1 (Complex) Ergänzende vertragsärztlicher Leistungen URL: https://fhir.bfarm.de/StructureDefinition/HealthAppPrescriptionUnitVertragsaerztlicheLeistungen #xD; url S 1..1 uri URL zum Verzeichnis #xD; Slices for identifier S 0..* Identifier IDs Slice: Unordered, Open by value:system #xD; identifier:digaVeId S 0..1 Identifier DiGA-VE-ID #xD; system S 1..1 uri The namespace for the identifier value Fixed Value: https://fhir.bfarm.de/Identifier/DigaVeId #xD; value S 1..1 string The value that is unique #xD; identifier:dipaAeId S 0..1 Identifier DiPA-AE-ID #xD; system S 1..1 uri The namespace for the identifier value Fixed Value: https://fhir.bfarm.de/Identifier/DipaAeId #xD; value S 1..1 string The value that is unique #xD; title S 0..1 string Name #xD; status S 1..1 code Status (unknown) #xD; description S 0..1 markdown Anmerkungen zum Preismodell #xD; Slices for useContext S 0..* UsageContext Patienten- und Zielgruppen Slice: Unordered, Open by value:code.code #xD; useContext:age S 0..* UsageContext Altersgruppen #xD; code S 1..1 Coding Type of context being specified #xD; system S 1..1 uri Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/usage-context-type #xD; code S 1..1 code Symbol in syntax defined by the system Fixed Value: age #xD; display S 1..1 string Representation defined by the system #xD; value[x] S 1..1 CodeableConcept Value that defines the context #xD; coding 1..1 Coding-HealthAppAge Code defined by a terminology system #xD; text S 0..1 string Kommentar #xD; useContext:focus S 0..* UsageContext Beeinträchtigungen #xD; code S 1..1 Coding Type of context being specified #xD; system S 1..1 uri Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/usage-context-type #xD; code S 1..1 code Symbol in syntax defined by the system Fixed Value: focus #xD; display S 1..1 string Representation defined by the system #xD; value[x] S 1..1 CodeableConcept Value that defines the context #xD; Slices for extension Content/Rules for all slices #xD; extension:severity 0..* Coding-HealthAppSeverity Ausprägungsgrad URL: https://fhir.bfarm.de/StructureDefinition/HealthAppPrescriptionUnitUseContextValueSeverity #xD; coding 1..1 Coding-HealthAppFocus Code defined by a terminology system #xD; useContext:gender S 0..* UsageContext Geschlechter #xD; code S 1..1 Coding Type of context being specified #xD; system S 1..1 uri Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/usage-context-type #xD; code S 1..1 code Symbol in syntax defined by the system Fixed Value: gender #xD; display S 1..1 string Representation defined by the system #xD; value[x] S 1..1 CodeableConcept Value that defines the context #xD; coding 1..1 Coding-HealthAppGender Code defined by a terminology system #xD; effectivePeriod S 0..1 Period Gültigkeitsdauer #xD; start S 0..1 dateTime Starting time with inclusive boundary #xD; end S 0..1 dateTime End time with inclusive boundary, if not ongoing #xD; code S 0..1 CodeableConcept Codierung #xD; Slices for extension Content/Rules for all slices #xD; extension:validUntil 0..1 dateTime Zur Verordnung bis URL: https://fhir.bfarm.de/StructureDefinition/HealthAppPrescriptionUnitCodeValidUntil #xD; coding S 1..1 CodingPZN Code defined by a terminology system #xD; system S 1..1 uri Canonische CodeSystem URL für PZN #xD; code S 1..1 code Der PZN-Code #xD; instance S 1..1 Reference(Medication | Substance | Device) HealthAppModule #xD; extension 1..* Extension Extension #xD; Slices for extension Content/Rules for all slices #xD; extension:deviceDefinition 1..1 Reference(HealthAppModule) Verweis URL: https://fhir.bfarm.de/StructureDefinition/HealthAppPrescriptionUnitHealthAppModuleLink #xD; propertyGroup S 0..1 BackboneElement Group of properties which are applicable under the same conditions #xD; Slices for extension Content/Rules for all slices #xD; extension:nonRefundable 0..1 (Complex) Nicht-erstattungsfähige Kosten URL: https://fhir.bfarm.de/StructureDefinition/HealthAppPrescriptionUnitPropertyGroupNonRefundable #xD; extension 1..* Extension Extension #xD; priceComponent S 0..* BackboneElement Preisangaben #xD; type S 1..1 code Preisbestandteil (Typ) #xD; <a href="StructureDefinition-HealthAppPrescriptionUnit-definitions.html#ChargeItemDefinition.propertyGroup.priceComponent.code" title="Bezeichnung des Preisbestandteils:#xD;#xA;+ additional-costs: Mehrkosten bei alleiniger Nutzung (nur DiPA)#xD;#xA;+ compensation-amount: Verhandelter Vergütungsbetrag (nur DiPA)#xD;#xA;+ maximum-amount: Vergütungs- / Höchstbetrag (nur DiGA)#xD;#xA;+ publisher-price: Herstellerpreis (nur DiGA)">code S 0..1 CodeableConcept Preisbestandteil (Bezeichnung) #xD; coding 0..1 Coding-HealthAppPriceCode Code defined by a terminology system #xD; amount S 0..1 Money Betrag #xD; value S 0..1 decimal Numerical value (with implicit precision) #xD; currency S 0..1 code ISO 4217 Currency Code #xD; <img src="[binary]" alt="doco" style="background-color: inherit"/> Documentation for this format
In diesem Profil werden Informationen zu einer Verordnungseinheit eines Moduls einer digitalen Gesundheitsanwendung (DiGA) bzw. zu einer Anwendungseinheit eines Moduls einer digitalen Pflegeanwendung (DiPA) repräsentiert.
Name should be usable as an identifier for the module by machine processing applications such as code generation
not(exists(f:name/@value)) or matches(f:name/@value, '[A-Z]([A-Za-z0-9_]){0,254}')
If the resource is contained in another resource, it SHALL NOT contain nested Resources
not(parent::f:contained and f:contained)
If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
not(exists(for $id in f:contained/*/f:id/@value return $contained[not(parent::*/descendant::f:reference/@value=concat('#', $contained/*/id/@value) or descendant::f:reference[@value='#'])]))
If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
not(exists(f:contained/*/f:meta/f:versionId)) and not(exists(f:contained/*/f:meta/f:lastUpdated))
If a resource is contained in another resource, it SHALL NOT have a security label
When a resource has no narrative, only systems that fully understand the data can display the resource to a human safely. Including a human readable representation in the resource makes for a much more robust eco-system and cheaper handling of resources by intermediary systems. Some ecosystems restrict distribution of resources to only those systems that do fully understand the resources, and as a consequence implementers may believe that the narrative is superfluous. However experience shows that such eco-systems often open up to new participants over time.
A resource should have narrative for robust management
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 might not always be associated with version changes to the resource.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
A set of rules under which this content was created
A 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.
This element is labeled 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).
Text summary of the resource, for human interpretation
A 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.
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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
Nur DiGA: Enthält Angaben zur Dauer, über welche die Verordnungseinheit der digitalen Gesundheitsanwendung (DiGA) angewendet werden soll. Sind keine Angaben enthalten, dann ist die Nutzung der Anwendung ohne zeitliche Begrenzung möglich (Einmallizenz).
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
Nur DiPA: Enthält Angaben dazu, ob ergänzende Unterstützungsleistungen zur Anwendungseinheit erforderlich sind.
Nur DiGA: Beinhaltet Informationen dazu, wann die Anwendung der Verordnungseinheit der digitalen Gesundheitsanwendung (DiGA) angezeigt ist.
Nur DiGA: Beinhaltet Informationen dazu, wann die Anwendung der Verordnungseinheit der digitalen Gesundheitsanwendung (DiGA) nicht angezeigt, also kontraindiziert ist.
Ergänzende vertragsärztlicher Leistungen
Nur DiGA: Enthält Angaben dazu, ob ergänzende vertragsärztliche Leistungen zur Anwendungseinheit bzw. Verordnungseinheit erforderlich sind.
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).
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.
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](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the resource that contains them
Enthält die URL zu einer der Anwendungs- bzw. Verordnungseinheit zugehörigen Information im Verzeichnis.
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](http://hl7.org/fhir/R4/resource.html#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](http://hl7.org/fhir/R4/resource.html#meta) element to indicate where the current master source of the resource can be found.
Allows the charge item definition to be referenced by a single globally unique identifier.
Enthält Werte zur eindeutigen Identifizierung der Anwendungs- bzw. Verordnungseinheit.
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.
Allows externally provided and/or usable business identifiers to be easily associated with the module.
DiGA-Verordnungseinheit-ID als eindeutiges Identifizierungsmerkmal der Verordnungseinheit der digitalen Gesundheitsanwendung (DiGA).
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
Additional content defined by implementations
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.
usual | official | temp | secondary | old (If known)
Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.
Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.
This is labeled as "Is Modifier" because applications should not mistake a temporary id for a permanent one.
Identifies the purpose for this identifier, if known .
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
Allows users to make use of identifiers when the identifier system is not known.
A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.
Establishes the namespace for the value - that is, a URL that describes a set values that are unique.
Identifier.system is always case sensitive.
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the [Rendered Value extension](http://hl7.org/fhir/R4/extension-rendered-value.html). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)
Time period when id is/was valid for use
Time period during which identifier is/was valid for use.
Role.effectiveTime or implied by context
Organization that issued id (may be just text)
Organization that issued/manages the identifier.
The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
DiPA-Anwendungseinheit-ID als eindeutiges Identifizierungsmerkmal der Anwendungseinheit der digitalen Pflegeanwendung (DiPA).
Business version of the charge item definition
The 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].
Die namentliche Bezeichnung der Anwendungs- bzw. Verordnungseinheit.
This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.
Underlying externally-defined charge item definition
The URL pointing to an externally-defined charge item definition that is adhered to in whole or in part by this definition.
A larger definition of which this particular definition is a component or step
A larger definition of which this particular definition is a component or step.
Completed or terminated request(s) whose function is taken by this new request
As new versions of a protocol or guideline are defined, allows identification of what versions are replaced by a new instance.
Repräsentiert den Status der Anwendungs- bzw. Verordnungseinheit. Dieser ist hier immer auf unknown gesetzt. Ob eine Anwendungs- bzw. Verordnungseinheit zum aktuellen Zeitpunkt aktiv ist, ergibt sich aus der effectivePeriod.
Allows filtering of charge item definitions that are appropriate for use versus not.
This is labeled as "Is Modifier" because applications should not use a retired {{title}} without due consideration
A 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.
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.
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.
Name of the publisher (organization or individual)
The name of the organization or individual that published the charge item definition.
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.
Helps establish the "authority/credibility" of the charge item definition. May also allow for contact.
Definition.publisher {as string instead of CodeableConcept}
Contact details to assist a user in finding and communicating with the publisher.
May be a web site, an email address, a telephone number, etc.
Enthält weitere optionale Erläuterungen zum Preismodell.
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).
Enthält Angaben zu Patienten- und Zielgruppen, für welche die Anwendungseinheit bzw. Verordnungseinheit geeignet ist.
This material includes SNOMED Clinical Terms® (SNOMED CT®) which is used by permission of the International Health Terminology Standards Development Organisation (IHTSDO). All rights reserved. SNOMED CT®, was originally created by The College of American Pathologists. SNOMED and SNOMED CT are registered trademarks of the IHTSDO.
Assist in searching for appropriate content.
Angabe der Altersgruppen (der Patienten) für welche die Anwendungs- bzw. Verordnungseinheit geeignet ist.
When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.
A code that identifies the type of context being specified by this usage context.
A code that specifies a type of context being specified by a usage context.
The identification of the code system that defines the meaning of the symbol in the code.
The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
Need to be unambiguous about the source of the definition of the symbol.
fhir:Coding.system rdfs:subPropertyOf dt:CDCoding.codeSystem
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
fhir:Coding.version rdfs:subPropertyOf dt:CDCoding.codeSystemVersion
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
Need to refer to a particular code in the system.
fhir:Coding.code rdfs:subPropertyOf dt:CDCoding.code
A representation of the meaning of the code in the system, following the rules of the system.
Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
C*E.2 - but note this is not well followed
fhir:Coding.display rdfs:subPropertyOf dt:CDCoding.displayName
If this coding was chosen directly by the user
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map; fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [ fhir:source "true"; fhir:target dt:CDCoding.codingRationale\#O ]
A value that defines the context specified in this context of use. The interpretation of the value is defined by the code.
A code that defines the specific value for the context being specified.
A reference to a code defined by a terminology system.
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
Allows for alternative encodings within a code system, and translations to other code systems.
fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
Very often the text is the same as a displayName of one of the codings.
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.
C*E.9. But note many systems use C*E.2 for this
fhir:CodeableConcept.text rdfs:subPropertyOf dt:CD.originalText
Nur DiPA: Angabe der Dimensionen der Beeinträchtigungen (der Patienten) für welche die Anwendungseinheit geeignet ist.
Nur DiPA: Optionaler Ausprägungsgrad der Dimension der Beeinträchtigung.
Plain text representation of the concept
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
Angabe der Geschlechter (der Patienten) für welche die Anwendungs- bzw. Verordnungseinheit geeignet ist.
Intended jurisdiction for charge item definition (if applicable)
A 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.
A 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.
When the charge item definition was approved by publisher
The 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.
When the charge item definition was last reviewed
The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date.
If specified, this date follows 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.
Gibt an in welchem Zeitraum die Anwendungs- bzw. Verordnungseinheit gültig ist.
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.
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 start of the period. The boundary is inclusive.
If the low element is missing, the meaning is that the low boundary is not known.
End time with inclusive boundary, if not ongoing
The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.
The high value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has an end value of 2012-02-03.
If the end of the period is missing, it means that the period is ongoing
Nur DiGA: Codiert die Verordnungseinheit einer digitalen Gesundheitsanwendung (DiGA), beispielsweise in Form der Pharmazentralnummer (PZN).
Billing Code defined by this ChargeItemDefinition.
Nur DiGA: Bis wann die Verordnung der PZN möglich ist.
Die Referenz zum übergeordneten Modul der digitalen Anwendung (HealthAppModule).
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.
Der Verweis auf das Modul der digitalen Anwendung (HealthAppModule).
Literal reference, Relative, internal or absolute URL
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
Type the reference refers to (e.g. "Patient")
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
Aa resource (or, for logical models, the URI of the logical model).
Logical reference, when literal reference is not known
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
Plain text narrative that identifies the resource in addition to the resource reference.
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
Whether or not the billing code is applicable
Expressions 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.
Extensions that cannot be ignored even if unrecognized
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).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
Natural language description of the condition
A brief, natural language description of the condition that effectively communicates the intended semantics.
The media type of the language for the expression, e.g. "text/cql" for Clinical Query Language expressions or "text/fhirpath" for FHIRPath expressions.
An 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.
Group of properties which are applicable under the same conditions
Group of properties which are applicable under the same conditions. If no applicability rules are established for the group, then all properties always apply.
Enthält Angaben zu Kosten der Anwendungs- bzw. Verordnungseinheit, die nicht (z.B. durch die Gesetzliche Krankenversicherung) erstattet werden können.
Die Beschreibung der nicht-erstattungsfähigen Kosten in Textform, falls die Anwendungseinheit bzw. Verordnungseinheit nicht-erstattungsfähige Kostenbestandteile enthält.
Source of the definition for the extension code - a logical name or a URL.
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).
Vorhandensein nicht-erstattungsfähiger Kosten (true | false)
Gibt an, ob die Kosten der Anwendungseinheit bzw. Verordnungseinheit nicht-erstattungsfähige Bestandteile enthalten: + true: nicht-erstattungsfähige Kosten enthalten + false: keine nicht-erstattungsfähigen Kosten enthalten / alle Kosten werden erstattet
Conditions under which the priceComponent is applicable
Expressions that describe applicability criteria for the priceComponent.
Enthält Angaben zum Preis der Anwendungs- bzw. Verordnungseinheit.
Typ des Preisbestandteils: + informational: Bruttopreis inkl. Mehrwertsteuer
Codes indicating the kind of the price component.
Bezeichnung des Preisbestandteils: + additional-costs: Mehrkosten bei alleiniger Nutzung (nur DiPA) + compensation-amount: Verhandelter Vergütungsbetrag (nur DiPA) + maximum-amount: Vergütungs- / Höchstbetrag (nur DiGA) + publisher-price: Herstellerpreis (nur DiGA)
Factor used for calculating this component
The factor that has been applied on the base price for calculating this component.
Enthält den Betrag des jeweiligen Preisbestandteils.
Numerical value (with implicit precision)
Numerical value (with implicit precision).
Monetary values have their own rules for handling precision (refer to standard accounting text books).
The amount of the currency. The value includes an implicit precision in the presentation of the value.
A code indicating the currency, taken from ISO 4217.