Struct RegulatedAuthorizationBuilder

pub struct RegulatedAuthorizationBuilder { /* private fields */ }

Builder for RegulatedAuthorizationInner.

Implementations

impl RegulatedAuthorizationBuilder

pub fn id(self, value: String) -> RegulatedAuthorizationBuilder

Logical id of this artifact

The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.

pub fn meta(self, value: Meta) -> RegulatedAuthorizationBuilder

Metadata about the resource

The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.

pub fn implicit_rules(self, value: String) -> RegulatedAuthorizationBuilder

A set of rules under which this content was created

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.

Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.

pub fn language(self, value: String) -> RegulatedAuthorizationBuilder

Language; Language of the resource content

The base language in which the resource is written.

Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).

pub fn text(self, value: Narrative) -> RegulatedAuthorizationBuilder

Text summary of the resource, for human interpretation

A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it “clinically safe” for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.

Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a “text blob” or where text is additionally entered raw or narrated and encoded information is added later.

pub fn contained(self, value: Vec<Resource>) -> RegulatedAuthorizationBuilder

Contained, inline Resources

These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.

This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.

pub fn extension(self, value: Vec<Extension>) -> RegulatedAuthorizationBuilder

Additional content defined by implementations

May be used to represent additional information that is not part of the basic definition of the resource. 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.

pub fn modifier_extension( self, value: Vec<Extension>, ) -> RegulatedAuthorizationBuilder

Extensions that cannot be ignored

May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it 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 is allowed to 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.

pub fn identifier( self, value: Vec<Option<Identifier>>, ) -> RegulatedAuthorizationBuilder

Business identifier for the authorization, typically assigned by the authorizing body

Business identifier for the authorization, typically assigned by the authorizing body.

pub fn identifier_ext( self, value: Vec<Option<FieldExtension>>, ) -> RegulatedAuthorizationBuilder

Extension field.

pub fn subject( self, value: Vec<Option<Reference>>, ) -> RegulatedAuthorizationBuilder

The product type, treatment, facility or activity that is being authorized

The product type, treatment, facility or activity that is being authorized.

pub fn subject_ext( self, value: Vec<Option<FieldExtension>>, ) -> RegulatedAuthorizationBuilder

Extension field.

pub fn type(self, value: CodeableConcept) -> RegulatedAuthorizationBuilder

RegulatedAuthorizationType; Overall type of this authorization, for example drug marketing approval, orphan drug designation

Overall type of this authorization, for example drug marketing approval, orphan drug designation.

pub fn type_ext(self, value: FieldExtension) -> RegulatedAuthorizationBuilder

Extension field.

pub fn description(self, value: String) -> RegulatedAuthorizationBuilder

General textual supporting information

General textual supporting information.

pub fn description_ext( self, value: FieldExtension, ) -> RegulatedAuthorizationBuilder

Extension field.

pub fn region( self, value: Vec<Option<CodeableConcept>>, ) -> RegulatedAuthorizationBuilder

Jurisdiction; The territory in which the authorization has been granted

The territory (e.g., country, jurisdiction etc.) in which the authorization has been granted.

pub fn region_ext( self, value: Vec<Option<FieldExtension>>, ) -> RegulatedAuthorizationBuilder

Extension field.

pub fn status(self, value: CodeableConcept) -> RegulatedAuthorizationBuilder

PublicationStatus; The status that is authorised e.g. approved. Intermediate states can be tracked with cases and applications

The status that is authorised e.g. approved. Intermediate states and actions can be tracked with cases and applications.

pub fn status_ext(self, value: FieldExtension) -> RegulatedAuthorizationBuilder

Extension field.

pub fn status_date(self, value: DateTime) -> RegulatedAuthorizationBuilder

The date at which the current status was assigned

The date at which the current status was assigned.

pub fn status_date_ext( self, value: FieldExtension, ) -> RegulatedAuthorizationBuilder

Extension field.

pub fn validity_period(self, value: Period) -> RegulatedAuthorizationBuilder

The time period in which the regulatory approval etc. is in effect, e.g. a Marketing Authorization includes the date of authorization and/or expiration date

The time period in which the regulatory approval, clearance or licencing is in effect. As an example, a Marketing Authorization includes the date of authorization and/or an expiration date.

pub fn validity_period_ext( self, value: FieldExtension, ) -> RegulatedAuthorizationBuilder

Extension field.

pub fn indication( self, value: Vec<Option<CodeableReference>>, ) -> RegulatedAuthorizationBuilder

Condition for which the use of the regulated product applies

Condition for which the use of the regulated product applies.

pub fn indication_ext( self, value: Vec<Option<FieldExtension>>, ) -> RegulatedAuthorizationBuilder

Extension field.

pub fn intended_use( self, value: CodeableConcept, ) -> RegulatedAuthorizationBuilder

ProductIntendedUse; The intended use of the product, e.g. prevention, treatment

The intended use of the product, e.g. prevention, treatment, diagnosis.

pub fn intended_use_ext( self, value: FieldExtension, ) -> RegulatedAuthorizationBuilder

Extension field.

pub fn basis( self, value: Vec<Option<CodeableConcept>>, ) -> RegulatedAuthorizationBuilder

RegulatedAuthorizationBasis; The legal/regulatory framework or reasons under which this authorization is granted

The legal or regulatory framework against which this authorization is granted, or other reasons for it.

pub fn basis_ext( self, value: Vec<Option<FieldExtension>>, ) -> RegulatedAuthorizationBuilder

Extension field.

pub fn holder(self, value: Reference) -> RegulatedAuthorizationBuilder

The organization that has been granted this authorization, by the regulator

The organization that has been granted this authorization, by some authoritative body (the ‘regulator’).

pub fn holder_ext(self, value: FieldExtension) -> RegulatedAuthorizationBuilder

Extension field.

pub fn regulator(self, value: Reference) -> RegulatedAuthorizationBuilder

The regulatory authority or authorizing body granting the authorization

The regulatory authority or authorizing body granting the authorization. For example, European Medicines Agency (EMA), Food and Drug Administration (FDA), Health Canada (HC), etc.

pub fn regulator_ext( self, value: FieldExtension, ) -> RegulatedAuthorizationBuilder

Extension field.

pub fn attached_document( self, value: Vec<Option<Reference>>, ) -> RegulatedAuthorizationBuilder

Additional information or supporting documentation about the authorization

Additional information or supporting documentation about the authorization.

pub fn attached_document_ext( self, value: Vec<Option<FieldExtension>>, ) -> RegulatedAuthorizationBuilder

Extension field.

pub fn case( self, value: RegulatedAuthorizationCase, ) -> RegulatedAuthorizationBuilder

The case or regulatory procedure for granting or amending a regulated authorization. Note: This area is subject to ongoing review and the workgroup is seeking implementer feedback on its use (see link at bottom of page)

The case or regulatory procedure for granting or amending a regulated authorization. An authorization is granted in response to submissions/applications by those seeking authorization. A case is the administrative process that deals with the application(s) that relate to this and assesses them. Note: This area is subject to ongoing review and the workgroup is seeking implementer feedback on its use (see link at bottom of page).

pub fn case_ext(self, value: FieldExtension) -> RegulatedAuthorizationBuilder

Extension field.

pub fn build_inner(self) -> Result<RegulatedAuthorizationInner, BuilderError>

Builds a new RegulatedAuthorizationInner.

Errors

If a required field has not been initialized.

impl RegulatedAuthorizationBuilder

pub fn build(self) -> Result<RegulatedAuthorization, BuilderError>

Finalize building RegulatedAuthorization.

Trait Implementations

impl Default for RegulatedAuthorizationBuilder

fn default() -> RegulatedAuthorizationBuilder

Returns the “default value” for a type.