Generated Narrative: StructureDefinition MopedSupportingInfoVortageanzahlAufKostenbeitrag Name Flags Card. Type Description & Constraints Extension 0..* Extension Supporting Info Extension for ClaimResponse - Vortageanzahl auf Kostenbeitrag #xD; extension 3..* Extension Extension #xD; Slices for extension Content/Rules for all slices #xD; extension:sequence 1..1 Extension Information instance identifier #xD; extension 0..0 Extension #xD; url 1..1 uri "sequence" #xD; value[x] 1..1 positiveInt Value of extension #xD; extension:category 1..1 Extension Classification of the supplied information #xD; extension 0..0 Extension #xD; url 1..1 uri "category" #xD; value[x] 1..1 CodeableConcept Value of extension Binding: MOPED VAESupportingInformationCategory (required) #xD; coding 0..* Coding Code defined by a terminology system Required Pattern: At least the following #xD; extension:code 0..1 Extension Type of information #xD; extension 0..0 Extension #xD; url 1..1 uri "code" #xD; value[x] 1..1 CodeableConcept Value of extension Binding: Sonderklasse ValueSet (required) #xD; extension:timing 0..1 Extension When it occurred #xD; extension 0..0 Extension #xD; url 1..1 uri "timing" #xD; value[x] 1..1 Value of extension #xD; valueDate date #xD; valuePeriod Period #xD; extension:value 1..1 Extension Data to be provided #xD; extension 0..0 Extension #xD; url 1..1 uri "value" #xD; value[x] 1..1 Quantity Value of extension #xD; value 1..1 decimal Numerical value (with implicit precision) #xD; extension:reason 0..1 Extension Explanation for the information #xD; extension 0..0 Extension #xD; url 1..1 uri "reason" #xD; value[x] 1..1 CodeableConcept Value of extension #xD; url 1..1 uri "https://elga.moped.at/StructureDefinition/MopedSupportingInfoVortageanzahlAufKostenbeitrag" #xD; value[x] 0..0 Value of extension #xD; Documentation for this format
Supporting Info Extension for ClaimResponse - Vortageanzahl auf Kostenbeitrag
Additional information codes regarding exceptions, special considerations, the condition, situation, prior or concurrent issues
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Must have either extensions or value[x], not both
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
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/R5/extensibility.html) for a list).
Classification of the supplied information
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 managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
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.
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
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.
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
Numerical value (with implicit precision)
The value of the measured amount. The value includes an implicit precision in the presentation of the value.
The implicit precision in the value should always be honored. Monetary values have their own rules for handling precision (refer to standard accounting text books).
Precision is handled implicitly in almost all cases of measurement.
PQ.value, CO.value, MO.value, IVL.high or IVL.low depending on the value
< | <= | >= | > | ad - how to understand the value
How the value should be understood and represented - whether the actual value is greater or less than the stated value due to measurement issues; e.g. if the comparator is "<" , then the real value is < stated value.
Need a framework for handling measures where the value is <5ug/L or >400mg/L due to the limitations of measuring methodology.
If there is no comparator, then there is no modification of the value
This is labeled as "Is Modifier" because the comparator modifies the interpretation of the value significantly. If there is no comparator, then there is no modification of the value
How the Quantity should be understood and represented.
There are many representations for units of measure and in many contexts, particular representations are fixed and required. I.e. mcg for micrograms.
The identification of the system that provides the coded form of the unit.
Need to know the system that defines the coded form of the unit.
CO.codeSystem, PQ.translation.codeSystem
A computer processable form of the unit in some unit representation system.
The preferred system is UCUM, but SNOMED CT can also be used (for customary units) or ISO 4217 for currency. The context of use may additionally require a code from a particular system.
Need a computable form of the unit that is fixed across all forms. UCUM provides this for quantities, but SNOMED CT provides many units of interest.
PQ.code, MO.currency, PQ.translation.code