Generated Narrative: StructureDefinition ext-R3-ExpansionProfile.fixedVersion Name Flags Card. Type Description & Constraints Extension 0..* Extension(4.0.1) STU3: Fix use of a code system to a particular version (new) #xD; Slices for extension 3..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:system 1..1 Extension STU3: System to have its version fixed (new) #xD; url 1..1 uri "system" #xD; value[x] 1..1 uri System to have its version fixed #xD; extension:version 1..1 Extension STU3: Specific version of the code system referred to (new) #xD; url 1..1 uri "version" #xD; value[x] 1..1 string Specific version of the code system referred to #xD; extension:mode 1..1 Extension STU3: default | check | override (new) #xD; url 1..1 uri "mode" #xD; value[x] 1..1 code default | check | override Binding: R3SystemVersionProcessingModeForR4 (0.1.0) (required): How to manage the intersection between a fixed version in a value set, and a fixed version of the system in the expansion profile #xD; url 1..1 uri "http://hl7.org/fhir/3.0/StructureDefinition/extension-ExpansionProfile.fixedVersion" #xD; value[x] 0..0 Value of extension #xD; Documentation for this format
STU3: Fix use of a code system to a particular version (new)
STU3: `ExpansionProfile.fixedVersion` (new:BackboneElement)
This extension is part of the cross-version definitions generated to enable use of the element `ExpansionProfile.fixedVersion` as defined in FHIR STU3 in FHIR R4. The source element is defined as: `ExpansionProfile.fixedVersion` 0..* `BackboneElement` Following are the generation technical comments: Element `ExpansionProfile.fixedVersion` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`. Element `ExpansionProfile.fixedVersion` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `ExpansionProfile.fixedVersion` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`. Element `ExpansionProfile.fixedVersion` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
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")])
STU3: System to have its version fixed (new)
STU3: `ExpansionProfile.fixedVersion.system` (new:uri)
Element `ExpansionProfile.fixedVersion.system` is part of an existing definition because parent element `ExpansionProfile.fixedVersion` requires a cross-version extension. Element `ExpansionProfile.fixedVersion.system` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`. Element `ExpansionProfile.fixedVersion.system` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). See ''Coding.system'' for further documentation.
Element `ExpansionProfile.fixedVersion.system` is part of an existing definition because parent element `ExpansionProfile.fixedVersion` requires a cross-version extension. Element `ExpansionProfile.fixedVersion.system` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`. Element `ExpansionProfile.fixedVersion.system` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
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 specific system for which to fix the version.
See ''Coding.system'' for further documentation.
STU3: Specific version of the code system referred to (new)
STU3: `ExpansionProfile.fixedVersion.version` (new:string)
Element `ExpansionProfile.fixedVersion.version` is part of an existing definition because parent element `ExpansionProfile.fixedVersion` requires a cross-version extension. Element `ExpansionProfile.fixedVersion.version` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`. Element `ExpansionProfile.fixedVersion.version` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Specific version of the code system referred to
The version of the code system from which codes in the expansion should be included.
STU3: `ExpansionProfile.fixedVersion.mode` (new:code)
Element `ExpansionProfile.fixedVersion.mode` is part of an existing definition because parent element `ExpansionProfile.fixedVersion` requires a cross-version extension. Element `ExpansionProfile.fixedVersion.mode` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`. Element `ExpansionProfile.fixedVersion.mode` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
How to manage the intersection between a fixed version in a value set, and this fixed version of the system in the expansion profile.
How to manage the intersection between a fixed version in a value set, and a fixed version of the system in the expansion profile
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).