pub struct DeviceDefinitionConformsToBuilder { /* private fields */ }
Expand description
Builder for DeviceDefinitionConformsTo
.
Implementations§
Source§impl DeviceDefinitionConformsToBuilder
impl DeviceDefinitionConformsToBuilder
Sourcepub fn id(self, value: String) -> DeviceDefinitionConformsToBuilder
pub fn id(self, value: String) -> DeviceDefinitionConformsToBuilder
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.
Sourcepub fn extension(
self,
value: Vec<Extension>,
) -> DeviceDefinitionConformsToBuilder
pub fn extension( self, value: Vec<Extension>, ) -> DeviceDefinitionConformsToBuilder
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.
Sourcepub fn modifier_extension(
self,
value: Vec<Extension>,
) -> DeviceDefinitionConformsToBuilder
pub fn modifier_extension( self, value: Vec<Extension>, ) -> DeviceDefinitionConformsToBuilder
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.
Sourcepub fn category(
self,
value: CodeableConcept,
) -> DeviceDefinitionConformsToBuilder
pub fn category( self, value: CodeableConcept, ) -> DeviceDefinitionConformsToBuilder
DeviceSpecificationCategory; Describes the common type of the standard, specification, or formal guidance
Describes the type of the standard, specification, or formal guidance.
Sourcepub fn category_ext(
self,
value: FieldExtension,
) -> DeviceDefinitionConformsToBuilder
pub fn category_ext( self, value: FieldExtension, ) -> DeviceDefinitionConformsToBuilder
Extension field.
Sourcepub fn specification(
self,
value: CodeableConcept,
) -> DeviceDefinitionConformsToBuilder
pub fn specification( self, value: CodeableConcept, ) -> DeviceDefinitionConformsToBuilder
DeviceSpecificationType; Identifies the standard, specification, or formal guidance that the device adheres to the Device Specification type
Code that identifies the specific standard, specification, protocol, formal guidance, regulation, legislation, or certification scheme to which the device adheres.
Sourcepub fn specification_ext(
self,
value: FieldExtension,
) -> DeviceDefinitionConformsToBuilder
pub fn specification_ext( self, value: FieldExtension, ) -> DeviceDefinitionConformsToBuilder
Extension field.
Sourcepub fn version(
self,
value: Vec<Option<String>>,
) -> DeviceDefinitionConformsToBuilder
pub fn version( self, value: Vec<Option<String>>, ) -> DeviceDefinitionConformsToBuilder
The specific form or variant of the standard, specification or formal guidance
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.
Sourcepub fn version_ext(
self,
value: Vec<Option<FieldExtension>>,
) -> DeviceDefinitionConformsToBuilder
pub fn version_ext( self, value: Vec<Option<FieldExtension>>, ) -> DeviceDefinitionConformsToBuilder
Extension field.
Sourcepub fn source(
self,
value: Vec<Option<RelatedArtifact>>,
) -> DeviceDefinitionConformsToBuilder
pub fn source( self, value: Vec<Option<RelatedArtifact>>, ) -> DeviceDefinitionConformsToBuilder
Standard, regulation, certification, or guidance website, document, or other publication, or similar, supporting the conformance
Standard, regulation, certification, or guidance website, document, or other publication, or similar, supporting the conformance.
Sourcepub fn source_ext(
self,
value: Vec<Option<FieldExtension>>,
) -> DeviceDefinitionConformsToBuilder
pub fn source_ext( self, value: Vec<Option<FieldExtension>>, ) -> DeviceDefinitionConformsToBuilder
Extension field.