Generated Narrative: StructureDefinition ext-R3-DeviceComponent.productionSpecification Name Flags Card. Type Description & Constraints Extension 0..* Extension(4.0.1) STU3: Specification details such as Component Revisions, or Serial Numbers (new) #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:specType 0..1 Extension STU3: Type or kind of production specification, for example serial number or software revision (new) #xD; url 1..1 uri "specType" #xD; value[x] 0..1 CodeableConcept Type or kind of production specification, for example serial number or software revision Binding: R3SpecificationTypeForR4 (0.1.0) (extensible): Codes for device specification types such as serial number, part number, hardware revision, software revision, etc. #xD; extension:componentId 0..1 Extension STU3: Internal component unique identification (new) #xD; url 1..1 uri "componentId" #xD; value[x] 0..1 Identifier Internal component unique identification #xD; extension:productionSpec 0..1 Extension STU3: A printable string defining the component (new) #xD; url 1..1 uri "productionSpec" #xD; value[x] 0..1 string A printable string defining the component #xD; url 1..1 uri "http://hl7.org/fhir/3.0/StructureDefinition/extension-DeviceComponent.productionSpecification" #xD; value[x] 0..0 Value of extension #xD; Documentation for this format
STU3: Specification details such as Component Revisions, or Serial Numbers (new)
STU3: `DeviceComponent.productionSpecification` (new:BackboneElement)
This extension is part of the cross-version definitions generated to enable use of the element `DeviceComponent.productionSpecification` as defined in FHIR STU3 in FHIR R4. The source element is defined as: `DeviceComponent.productionSpecification` 0..* `BackboneElement` Following are the generation technical comments: Element `DeviceComponent.productionSpecification` is not mapped to FHIR R4, since FHIR STU3 `DeviceComponent` is not mapped. Element `DeviceComponent.productionSpecification` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `DeviceComponent.productionSpecification` is not mapped to FHIR R4, since FHIR STU3 `DeviceComponent` is not mapped. Element `DeviceComponent.productionSpecification` 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: Type or kind of production specification, for example serial number or software revision (new)
STU3: `DeviceComponent.productionSpecification.specType` (new:CodeableConcept)
Element `DeviceComponent.productionSpecification.specType` is part of an existing definition because parent element `DeviceComponent.productionSpecification` requires a cross-version extension. Element `DeviceComponent.productionSpecification.specType` is not mapped to FHIR R4, since FHIR STU3 `DeviceComponent` is not mapped. Element `DeviceComponent.productionSpecification.specType` 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.
Type or kind of production specification, for example serial number or software revision
The specification type, such as, serial number, part number, hardware revision, software revision, etc.
Codes for device specification types such as serial number, part number, hardware revision, software revision, etc.
STU3: Internal component unique identification (new)
STU3: `DeviceComponent.productionSpecification.componentId` (new:Identifier)
Element `DeviceComponent.productionSpecification.componentId` is part of an existing definition because parent element `DeviceComponent.productionSpecification` requires a cross-version extension. Element `DeviceComponent.productionSpecification.componentId` is not mapped to FHIR R4, since FHIR STU3 `DeviceComponent` is not mapped. Element `DeviceComponent.productionSpecification.componentId` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Internal component unique identification
The internal component unique identification. This is a provision for manufacture specific standard components using a private OID. 11073-10101 has a partition for private OID semantic that the manufacturer can make use of.
STU3: A printable string defining the component (new)
STU3: `DeviceComponent.productionSpecification.productionSpec` (new:string)
Element `DeviceComponent.productionSpecification.productionSpec` is part of an existing definition because parent element `DeviceComponent.productionSpecification` requires a cross-version extension. Element `DeviceComponent.productionSpecification.productionSpec` is not mapped to FHIR R4, since FHIR STU3 `DeviceComponent` is not mapped. Element `DeviceComponent.productionSpecification.productionSpec` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
A printable string defining the component
The printable string defining the component.
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).