pub struct DeviceDefinitionVersion {
pub id: Option<String>,
pub extension: Vec<Extension>,
pub modifier_extension: Vec<Extension>,
pub type: Option<CodeableConcept>,
pub type_ext: Option<FieldExtension>,
pub component: Option<Identifier>,
pub component_ext: Option<FieldExtension>,
pub value: String,
pub value_ext: Option<FieldExtension>,
}
Expand description
Sub-fields of the version field in DeviceDefinition
Fields§
§id: Option<String>
Unique id for inter-element referencing
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
extension: Vec<Extension>
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.
modifier_extension: Vec<Extension>
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 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. 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.
type: Option<CodeableConcept>
The type of the device version, e.g. manufacturer, approved, internal
The type of the device version, e.g. manufacturer, approved, internal.
type_ext: Option<FieldExtension>
Extension field.
component: Option<Identifier>
The hardware or software module of the device to which the version applies
The hardware or software module of the device to which the version applies.
Note that the module of the device would not need to be tracked as a separate device, e.g., using different UDI, thus would typically involve one or more software modules. For example, a device may involve two software modules each on a different version.
component_ext: Option<FieldExtension>
Extension field.
value: String
The version text
The version text.
value_ext: Option<FieldExtension>
Extension field.
Implementations§
Source§impl DeviceDefinitionVersion
impl DeviceDefinitionVersion
Sourcepub fn builder() -> DeviceDefinitionVersionBuilder
pub fn builder() -> DeviceDefinitionVersionBuilder
Start building a new instance
Trait Implementations§
Source§impl Clone for DeviceDefinitionVersion
impl Clone for DeviceDefinitionVersion
Source§fn clone(&self) -> DeviceDefinitionVersion
fn clone(&self) -> DeviceDefinitionVersion
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read more