pub struct AccountProcedureBuilder { /* private fields */ }
Expand description
Builder for AccountProcedure
.
Implementations§
Source§impl AccountProcedureBuilder
impl AccountProcedureBuilder
Sourcepub fn id(self, value: String) -> AccountProcedureBuilder
pub fn id(self, value: String) -> AccountProcedureBuilder
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>) -> AccountProcedureBuilder
pub fn extension(self, value: Vec<Extension>) -> AccountProcedureBuilder
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>,
) -> AccountProcedureBuilder
pub fn modifier_extension( self, value: Vec<Extension>, ) -> AccountProcedureBuilder
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 sequence(self, value: NonZero<u32>) -> AccountProcedureBuilder
pub fn sequence(self, value: NonZero<u32>) -> AccountProcedureBuilder
Ranking of the procedure (for each type)
Ranking of the procedure (for each type).
Sourcepub fn sequence_ext(self, value: FieldExtension) -> AccountProcedureBuilder
pub fn sequence_ext(self, value: FieldExtension) -> AccountProcedureBuilder
Extension field.
Sourcepub fn code(self, value: CodeableReference) -> AccountProcedureBuilder
pub fn code(self, value: CodeableReference) -> AccountProcedureBuilder
Sourcepub fn code_ext(self, value: FieldExtension) -> AccountProcedureBuilder
pub fn code_ext(self, value: FieldExtension) -> AccountProcedureBuilder
Extension field.
Sourcepub fn date_of_service(self, value: DateTime) -> AccountProcedureBuilder
pub fn date_of_service(self, value: DateTime) -> AccountProcedureBuilder
Date of the procedure (when coded procedure)
Date of the procedure when using a coded procedure. If using a reference to a procedure, then the date on the procedure should be used.
Sourcepub fn date_of_service_ext(
self,
value: FieldExtension,
) -> AccountProcedureBuilder
pub fn date_of_service_ext( self, value: FieldExtension, ) -> AccountProcedureBuilder
Extension field.
Sourcepub fn type(
self,
value: Vec<Option<CodeableConcept>>,
) -> AccountProcedureBuilder
pub fn type( self, value: Vec<Option<CodeableConcept>>, ) -> AccountProcedureBuilder
procedure-type; How this procedure value should be used in charging the account
How this procedure value should be used in charging the account.
Sourcepub fn type_ext(
self,
value: Vec<Option<FieldExtension>>,
) -> AccountProcedureBuilder
pub fn type_ext( self, value: Vec<Option<FieldExtension>>, ) -> AccountProcedureBuilder
Extension field.
Sourcepub fn package_code(
self,
value: Vec<Option<CodeableConcept>>,
) -> AccountProcedureBuilder
pub fn package_code( self, value: Vec<Option<CodeableConcept>>, ) -> AccountProcedureBuilder
procedure-package-code; Package Code specific for billing
The package code can be used to group procedures that may be priced or delivered as a single product. Such as DRGs.
Sourcepub fn package_code_ext(
self,
value: Vec<Option<FieldExtension>>,
) -> AccountProcedureBuilder
pub fn package_code_ext( self, value: Vec<Option<FieldExtension>>, ) -> AccountProcedureBuilder
Extension field.
Sourcepub fn device(self, value: Vec<Option<Reference>>) -> AccountProcedureBuilder
pub fn device(self, value: Vec<Option<Reference>>) -> AccountProcedureBuilder
Any devices that were associated with the procedure
Any devices that were associated with the procedure relevant to the account.
Sourcepub fn device_ext(
self,
value: Vec<Option<FieldExtension>>,
) -> AccountProcedureBuilder
pub fn device_ext( self, value: Vec<Option<FieldExtension>>, ) -> AccountProcedureBuilder
Extension field.