pub struct DeviceRequestParameterBuilder { /* private fields */ }
Expand description
Builder for DeviceRequestParameter
.
Implementations§
Source§impl DeviceRequestParameterBuilder
impl DeviceRequestParameterBuilder
Sourcepub fn id(self, value: String) -> DeviceRequestParameterBuilder
pub fn id(self, value: String) -> DeviceRequestParameterBuilder
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>) -> DeviceRequestParameterBuilder
pub fn extension(self, value: Vec<Extension>) -> DeviceRequestParameterBuilder
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>,
) -> DeviceRequestParameterBuilder
pub fn modifier_extension( self, value: Vec<Extension>, ) -> DeviceRequestParameterBuilder
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 code(self, value: CodeableConcept) -> DeviceRequestParameterBuilder
pub fn code(self, value: CodeableConcept) -> DeviceRequestParameterBuilder
ParameterCode; Device detail
A code or string that identifies the device detail being asserted.
Sourcepub fn code_ext(self, value: FieldExtension) -> DeviceRequestParameterBuilder
pub fn code_ext(self, value: FieldExtension) -> DeviceRequestParameterBuilder
Extension field.
Sourcepub fn value(
self,
value: DeviceRequestParameterValue,
) -> DeviceRequestParameterBuilder
pub fn value( self, value: DeviceRequestParameterValue, ) -> DeviceRequestParameterBuilder
Value of detail
The value of the device detail.
Range means device should have a value that falls somewhere within the specified range.
Sourcepub fn value_ext(
self,
value: DeviceRequestParameterValueExtension,
) -> DeviceRequestParameterBuilder
pub fn value_ext( self, value: DeviceRequestParameterValueExtension, ) -> DeviceRequestParameterBuilder
Extension field.