Struct DeviceUsageBuilder

pub struct DeviceUsageBuilder { /* private fields */ }

Builder for DeviceUsageInner.

Implementations

impl DeviceUsageBuilder

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

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) -> DeviceUsageBuilder

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) -> DeviceUsageBuilder

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) -> DeviceUsageBuilder

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) -> DeviceUsageBuilder

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>) -> DeviceUsageBuilder

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>) -> DeviceUsageBuilder

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>) -> DeviceUsageBuilder

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>>) -> DeviceUsageBuilder

External identifier for this record

An external identifier for this statement such as an IRI.

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

Extension field.

pub fn based_on(self, value: Vec<Option<Reference>>) -> DeviceUsageBuilder

Fulfills plan, proposal or order

A plan, proposal or order that is fulfilled in whole or in part by this DeviceUsage.

pub fn based_on_ext( self, value: Vec<Option<FieldExtension>>, ) -> DeviceUsageBuilder

Extension field.

pub fn status(self, value: DeviceUsageStatus) -> DeviceUsageBuilder

DeviceUsageStatus; active | completed | not-done | entered-in-error +

A code representing the patient or other source’s judgment about the state of the device used that this statement is about. Generally this will be active or completed.

DeviceUseStatment is a statement at a point in time. The status is only representative at the point when it was asserted. The value set for contains codes that assert the status of the use by the patient (for example, stopped or on hold) as well as codes that assert the status of the resource itself (for example, entered in error).

This element is labeled as a modifier because the status contains the codes that mark the statement as not currently valid.

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

Extension field.

pub fn category(self, value: Vec<Option<CodeableConcept>>) -> DeviceUsageBuilder

The category of the statement - classifying how the statement is made

This attribute indicates a category for the statement - The device statement may be made in an inpatient or outpatient settting (inpatient | outpatient | community | patientspecified).

pub fn category_ext( self, value: Vec<Option<FieldExtension>>, ) -> DeviceUsageBuilder

Extension field.

pub fn patient(self, value: Reference) -> DeviceUsageBuilder

Patient using device

The patient who used the device.

pub fn patient_ext(self, value: FieldExtension) -> DeviceUsageBuilder

Extension field.

pub fn derived_from(self, value: Vec<Option<Reference>>) -> DeviceUsageBuilder

Supporting information

Allows linking the DeviceUsage to the underlying Request, or to other information that supports or is used to derive the DeviceUsage.

The most common use cases for deriving a DeviceUsage comes from creating it from a request or from an observation or a claim. it should be noted that the amount of information that is available varies from the type resource that you derive the DeviceUsage from.

pub fn derived_from_ext( self, value: Vec<Option<FieldExtension>>, ) -> DeviceUsageBuilder

Extension field.

pub fn context(self, value: Reference) -> DeviceUsageBuilder

The encounter or episode of care that establishes the context for this device use statement

The encounter or episode of care that establishes the context for this device use statement.

pub fn context_ext(self, value: FieldExtension) -> DeviceUsageBuilder

Extension field.

pub fn timing(self, value: DeviceUsageTiming) -> DeviceUsageBuilder

How often the device was used

How often the device was used.

pub fn timing_ext(self, value: DeviceUsageTimingExtension) -> DeviceUsageBuilder

Extension field.

pub fn date_asserted(self, value: DateTime) -> DeviceUsageBuilder

When the statement was made (and recorded)

The time at which the statement was recorded by informationSource.

pub fn date_asserted_ext(self, value: FieldExtension) -> DeviceUsageBuilder

Extension field.

pub fn usage_status(self, value: CodeableConcept) -> DeviceUsageBuilder

DeviceUsageStatus; The status of the device usage, for example always, sometimes, never. This is not the same as the status of the statement

The status of the device usage, for example always, sometimes, never. This is not the same as the status of the statement.

pub fn usage_status_ext(self, value: FieldExtension) -> DeviceUsageBuilder

Extension field.

pub fn usage_reason( self, value: Vec<Option<CodeableConcept>>, ) -> DeviceUsageBuilder

The reason for asserting the usage status - for example forgot, lost, stolen, broken

The reason for asserting the usage status - for example forgot, lost, stolen, broken.

pub fn usage_reason_ext( self, value: Vec<Option<FieldExtension>>, ) -> DeviceUsageBuilder

Extension field.

pub fn adherence(self, value: DeviceUsageAdherence) -> DeviceUsageBuilder

How device is being used

This indicates how or if the device is being used.

pub fn adherence_ext(self, value: FieldExtension) -> DeviceUsageBuilder

Extension field.

pub fn information_source(self, value: Reference) -> DeviceUsageBuilder

Who made the statement

Who reported the device was being used by the patient.

pub fn information_source_ext(self, value: FieldExtension) -> DeviceUsageBuilder

Extension field.

pub fn device(self, value: CodeableReference) -> DeviceUsageBuilder

Code or Reference to device used

Code or Reference to device used.

pub fn device_ext(self, value: FieldExtension) -> DeviceUsageBuilder

Extension field.

pub fn reason(self, value: Vec<Option<CodeableReference>>) -> DeviceUsageBuilder

Why device was used

Reason or justification for the use of the device. A coded concept, or another resource whose existence justifies this DeviceUsage.

When the status is not done, the reason code indicates why it was not done.

pub fn reason_ext( self, value: Vec<Option<FieldExtension>>, ) -> DeviceUsageBuilder

Extension field.

pub fn body_site(self, value: CodeableReference) -> DeviceUsageBuilder

BodySite; Target body site

Indicates the anotomic location on the subject’s body where the device was used ( i.e. the target).

pub fn body_site_ext(self, value: FieldExtension) -> DeviceUsageBuilder

Extension field.

pub fn note(self, value: Vec<Option<Annotation>>) -> DeviceUsageBuilder

Addition details (comments, instructions)

Details about the device statement that were not represented at all or sufficiently in one of the attributes provided in a class. These may include for example a comment, an instruction, or a note associated with the statement.

pub fn note_ext(self, value: Vec<Option<FieldExtension>>) -> DeviceUsageBuilder

Extension field.

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

Builds a new DeviceUsageInner.

Errors

If a required field has not been initialized.

impl DeviceUsageBuilder

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

Finalize building DeviceUsage.

Trait Implementations

impl Default for DeviceUsageBuilder

fn default() -> DeviceUsageBuilder

Returns the “default value” for a type.