Generated Narrative: StructureDefinition ext-R5-ElementDefinition.bi.additional Name Flags Card. Type Description & Constraints Extension 0..* Extension(4.0.1) Additional Bindings - more rules about the binding #xD; Slices for extension 2..* Extension Extension Slice: Unordered, Closed by value:url #xD; extension:purpose 1..1 Extension maximum | minimum | required | extensible | candidate | current | preferred | ui | starter | component #xD; url 1..1 uri "purpose" #xD; value[x] 0..1 code maximum | minimum | required | extensible | candidate | current | preferred | ui | starter | component Binding: R5_additional_binding_purpose_for_R4 (0.0.1-snapshot-2) (required): The use of an additional binding. #xD; extension:valueSet 1..1 Extension The value set for the additional binding #xD; url 1..1 uri "valueSet" #xD; value[x] 0..1 canonical() The value set for the additional binding #xD; extension:documentation 0..1 Extension Documentation of the purpose of use of the binding #xD; url 1..1 uri "documentation" #xD; value[x] 0..1 markdown Documentation of the purpose of use of the binding #xD; extension:shortDoco 0..1 Extension Concise documentation - for summary tables #xD; url 1..1 uri "shortDoco" #xD; value[x] 0..1 string Concise documentation - for summary tables #xD; <a href="StructureDefinition-ext-R5-ElementDefinition.bi.additional-definitions.html#Extension.extension:usage" title="Slice usage: Qualifies the usage of the binding. Typically bindings are qualified by jurisdiction, but they may also be qualified by gender, workflow status, clinical domain etc. The information to decide whether a usege context applies is usually outside the resource, determined by context, and this might present challenges for validation tooling.">extension:usage 0..* Extension Qualifies the usage - jurisdiction, gender, workflow status etc. #xD; url 1..1 uri "usage" #xD; <a href="StructureDefinition-ext-R5-ElementDefinition.bi.additional-definitions.html#Extension.extension:usage.value[x]" title="Qualifies the usage of the binding. Typically bindings are qualified by jurisdiction, but they may also be qualified by gender, workflow status, clinical domain etc. The information to decide whether a usege context applies is usually outside the resource, determined by context, and this might present challenges for validation tooling.">value[x] 0..1 UsageContext Qualifies the usage - jurisdiction, gender, workflow status etc. #xD; extension:any 0..1 Extension Whether binding can applies to all repeats, or just one #xD; url 1..1 uri "any" #xD; value[x] 0..1 boolean Whether binding can applies to all repeats, or just one #xD; url 1..1 uri "http://hl7.org/fhir/5.0/StructureDefinition/extension-ElementDefinition.binding.additional" #xD; Documentation for this format
Cross-version Extension for R5.ElementDefinition.binding.additional for use in FHIR R4
This cross-version extension represents ElementDefinition.binding.additional from http://hl7.org/fhir/StructureDefinition/ElementDefinition|5.0.0 for use in FHIR R4.
Additional Bindings - more rules about the binding
Additional bindings that help applications implementing this element. Additional bindings do not replace the main binding but provide more information and/or context.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
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
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
maximum | minimum | required | extensible | candidate | current | preferred | ui | starter | component
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.
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.
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.
The value set for the additional binding
The valueSet that is being bound for the purpose.
Documentation of the purpose of use of the binding
Documentation of the purpose of use of the bindingproviding additional information about how it is intended to be used.
Concise documentation - for summary tables
This cross-version extension represents ElementDefinition.binding.additional.shortDoco from http://hl7.org/fhir/StructureDefinition/ElementDefinition|5.0.0 for use in FHIR R4.
Qualifies the usage - jurisdiction, gender, workflow status etc.
Qualifies the usage of the binding. Typically bindings are qualified by jurisdiction, but they may also be qualified by gender, workflow status, clinical domain etc. The information to decide whether a usege context applies is usually outside the resource, determined by context, and this might present challenges for validation tooling.
Whether binding can applies to all repeats, or just one
Whether the binding applies to all repeats, or just to any one of them. This is only relevant for elements that can repeat.
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).