pub struct DeviceConformsTo {
pub id: Option<String>,
pub extension: Vec<Extension>,
pub modifier_extension: Vec<Extension>,
pub category: Option<CodeableConcept>,
pub category_ext: Option<FieldExtension>,
pub specification: CodeableConcept,
pub specification_ext: Option<FieldExtension>,
pub version: Option<String>,
pub version_ext: Option<FieldExtension>,
}
Expand description
Sub-fields of the conformsTo field in Device
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.
category: Option<CodeableConcept>
DeviceSpecificationCategory; Describes the common type of the standard, specification, or formal guidance. communication | performance | measurement
Describes the type of the standard, specification, or formal guidance.
category_ext: Option<FieldExtension>
Extension field.
specification: CodeableConcept
DeviceSpecification-type; Identifies the standard, specification, or formal guidance that the device adheres to
Code that identifies the specific standard, specification, protocol, formal guidance, regulation, legislation, or certification scheme to which the device adheres.
specification_ext: Option<FieldExtension>
Extension field.
version: Option<String>
Specific form or variant of the standard
Identifies the specific form or variant of the standard, specification, or formal guidance. This may be a ‘version number’, release, document edition, publication year, or other label.
version_ext: Option<FieldExtension>
Extension field.
Implementations§
Source§impl DeviceConformsTo
impl DeviceConformsTo
Sourcepub fn builder() -> DeviceConformsToBuilder
pub fn builder() -> DeviceConformsToBuilder
Start building a new instance
Trait Implementations§
Source§impl Clone for DeviceConformsTo
impl Clone for DeviceConformsTo
Source§fn clone(&self) -> DeviceConformsTo
fn clone(&self) -> DeviceConformsTo
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read more