pub struct ValueSetExpansionBuilder { /* private fields */ }Expand description
Builder for ValueSetExpansion.
Implementations§
Source§impl ValueSetExpansionBuilder
impl ValueSetExpansionBuilder
Sourcepub fn id(self, value: String) -> ValueSetExpansionBuilder
pub fn id(self, value: String) -> ValueSetExpansionBuilder
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>) -> ValueSetExpansionBuilder
pub fn extension(self, value: Vec<Extension>) -> ValueSetExpansionBuilder
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>,
) -> ValueSetExpansionBuilder
pub fn modifier_extension( self, value: Vec<Extension>, ) -> ValueSetExpansionBuilder
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 identifier(self, value: String) -> ValueSetExpansionBuilder
pub fn identifier(self, value: String) -> ValueSetExpansionBuilder
Identifies the value set expansion (business identifier)
An identifier that uniquely identifies this expansion of the valueset, based on a unique combination of the provided parameters, the system default parameters, and the underlying system code system versions etc. Systems may re-use the same identifier as long as those factors remain the same, and the expansion is the same, but are not required to do so. This is a business identifier.
Typically, this uri is a UUID (e.g. urn:uuid:8230ff20-c97a-4167-a59d-dc2cb9df16dd).
Sourcepub fn identifier_ext(self, value: FieldExtension) -> ValueSetExpansionBuilder
pub fn identifier_ext(self, value: FieldExtension) -> ValueSetExpansionBuilder
Extension field.
Sourcepub fn next(self, value: String) -> ValueSetExpansionBuilder
pub fn next(self, value: String) -> ValueSetExpansionBuilder
Opaque urls for paging through expansion results
As per paging Search results, the next URLs are opaque to the client, have no dictated structure, and only the server understands them.
Clients SHOULD use the next link, if present, to page through expansion results in preference to using the offset and count parameters. Due to the optional nature of the next link, its absence does not necessarily indicate that it is the last page of results. Instead, as the offset and count parameters SHALL be populated when paging, clients can reliably use the count/offset parameters to determine whether the whole expansion is returned.
Sourcepub fn next_ext(self, value: FieldExtension) -> ValueSetExpansionBuilder
pub fn next_ext(self, value: FieldExtension) -> ValueSetExpansionBuilder
Extension field.
Sourcepub fn timestamp(self, value: DateTime) -> ValueSetExpansionBuilder
pub fn timestamp(self, value: DateTime) -> ValueSetExpansionBuilder
Time ValueSet expansion happened
The time at which the expansion was produced by the expanding system.
This SHOULD be a fully populated instant, but in some circumstances, value sets are expanded by hand, and the expansion is published without that precision.
Sourcepub fn timestamp_ext(self, value: FieldExtension) -> ValueSetExpansionBuilder
pub fn timestamp_ext(self, value: FieldExtension) -> ValueSetExpansionBuilder
Extension field.
Sourcepub fn total(self, value: i32) -> ValueSetExpansionBuilder
pub fn total(self, value: i32) -> ValueSetExpansionBuilder
Total number of codes in the expansion
The total number of concepts in the expansion. If the number of concept nodes in this resource is less than the stated number, then the server can return more using the offset parameter.
Paging only applies to flat expansions.
Sourcepub fn total_ext(self, value: FieldExtension) -> ValueSetExpansionBuilder
pub fn total_ext(self, value: FieldExtension) -> ValueSetExpansionBuilder
Extension field.
Sourcepub fn offset(self, value: i32) -> ValueSetExpansionBuilder
pub fn offset(self, value: i32) -> ValueSetExpansionBuilder
Offset at which this resource starts
If paging is being used, the offset at which this resource starts. I.e. this resource is a partial view into the expansion. If paging is not being used, this element SHALL NOT be present.
Paging only applies to flat expansions. If a filter is applied, the count is the number of concepts that matched the filter, not the number of concepts in an unfiltered view of the expansion.
Sourcepub fn offset_ext(self, value: FieldExtension) -> ValueSetExpansionBuilder
pub fn offset_ext(self, value: FieldExtension) -> ValueSetExpansionBuilder
Extension field.
Sourcepub fn parameter(
self,
value: Vec<Option<ValueSetExpansionParameter>>,
) -> ValueSetExpansionBuilder
pub fn parameter( self, value: Vec<Option<ValueSetExpansionParameter>>, ) -> ValueSetExpansionBuilder
Parameter that controlled the expansion process
A parameter that controlled the expansion process. These parameters may be used by users of expanded value sets to check whether the expansion is suitable for a particular purpose, or to pick the correct expansion.
The server decides which parameters to include here, but at a minimum, the list SHOULD include all of the parameters that affect the $expand operation. If the expansion will be persisted all of these parameters SHALL be included. If the codeSystem on the server has a specified version then this version SHALL be provided as a parameter in the expansion (note that not all code systems have a version).
Sourcepub fn parameter_ext(
self,
value: Vec<Option<FieldExtension>>,
) -> ValueSetExpansionBuilder
pub fn parameter_ext( self, value: Vec<Option<FieldExtension>>, ) -> ValueSetExpansionBuilder
Extension field.
Sourcepub fn property(
self,
value: Vec<Option<ValueSetExpansionProperty>>,
) -> ValueSetExpansionBuilder
pub fn property( self, value: Vec<Option<ValueSetExpansionProperty>>, ) -> ValueSetExpansionBuilder
Additional information supplied about each concept
A property defines an additional slot through which additional information can be provided about a concept.
Sourcepub fn property_ext(
self,
value: Vec<Option<FieldExtension>>,
) -> ValueSetExpansionBuilder
pub fn property_ext( self, value: Vec<Option<FieldExtension>>, ) -> ValueSetExpansionBuilder
Extension field.
Sourcepub fn contains(
self,
value: Vec<Option<ValueSetExpansionContains>>,
) -> ValueSetExpansionBuilder
pub fn contains( self, value: Vec<Option<ValueSetExpansionContains>>, ) -> ValueSetExpansionBuilder
Codes in the value set
The codes that are contained in the value set expansion.
Sourcepub fn contains_ext(
self,
value: Vec<Option<FieldExtension>>,
) -> ValueSetExpansionBuilder
pub fn contains_ext( self, value: Vec<Option<FieldExtension>>, ) -> ValueSetExpansionBuilder
Extension field.