Struct DeviceRequestBuilder

pub struct DeviceRequestBuilder { /* private fields */ }

Builder for DeviceRequestInner.

Implementations

impl DeviceRequestBuilder

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

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

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

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

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

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

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

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

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

External Request identifier

Identifiers assigned to this order by the orderer or by the receiver.

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

Extension field.

pub fn instantiates_canonical( self, value: Vec<Option<String>>, ) -> DeviceRequestBuilder

Instantiates FHIR protocol or definition

The URL pointing to a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this DeviceRequest.

Note: This is a business identifier, not a resource identifier (see discussion). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.

pub fn instantiates_canonical_ext( self, value: Vec<Option<FieldExtension>>, ) -> DeviceRequestBuilder

Extension field.

pub fn instantiates_uri( self, value: Vec<Option<String>>, ) -> DeviceRequestBuilder

Instantiates external protocol or definition

The URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this DeviceRequest.

This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier.

pub fn instantiates_uri_ext( self, value: Vec<Option<FieldExtension>>, ) -> DeviceRequestBuilder

Extension field.

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

What request fulfills

Plan/proposal/order fulfilled by this request.

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

Extension field.

pub fn replaces(self, value: Vec<Option<Reference>>) -> DeviceRequestBuilder

What request replaces

The request takes the place of the referenced completed or terminated request(s).

pub fn replaces_ext( self, value: Vec<Option<FieldExtension>>, ) -> DeviceRequestBuilder

Extension field.

pub fn group_identifier(self, value: Identifier) -> DeviceRequestBuilder

Identifier of composite request

A shared identifier common to multiple independent Request instances that were activated/authorized more or less simultaneously by a single author. The presence of the same identifier on each request ties those requests together and may have business ramifications in terms of reporting of results, billing, etc. E.g. a requisition number shared by a set of lab tests ordered together, or a prescription number shared by all meds ordered at one time.

pub fn group_identifier_ext(self, value: FieldExtension) -> DeviceRequestBuilder

Extension field.

pub fn status(self, value: RequestStatus) -> DeviceRequestBuilder

DeviceRequestStatus; draft | active | on-hold | revoked | completed | entered-in-error | unknown

The status of the request.

This element is labeled as a modifier because the status contains the codes revoked and entered-in-error that mark the request as not currently valid.

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

Extension field.

pub fn intent(self, value: RequestIntent) -> DeviceRequestBuilder

RequestIntent; proposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option

Whether the request is a proposal, plan, an original order or a reflex order.

pub fn intent_ext(self, value: FieldExtension) -> DeviceRequestBuilder

Extension field.

pub fn priority(self, value: RequestPriority) -> DeviceRequestBuilder

RequestPriority; routine | urgent | asap | stat

Indicates how quickly the request should be addressed with respect to other requests.

pub fn priority_ext(self, value: FieldExtension) -> DeviceRequestBuilder

Extension field.

pub fn do_not_perform(self, value: bool) -> DeviceRequestBuilder

True if the request is to stop or not to start using the device

If true, indicates that the provider is asking for the patient to either stop using or to not start using the specified device or category of devices. For example, the patient has undergone surgery and the provider is indicating that the patient should not wear contact lenses.

If do not perform is not specified, the request is a positive request e.g. “do perform”. DeviceRequest.reasonCode includes the reason for marking the DeviceRequest as ‘do not perform’.

pub fn do_not_perform_ext(self, value: FieldExtension) -> DeviceRequestBuilder

Extension field.

pub fn code(self, value: CodeableReference) -> DeviceRequestBuilder

DeviceRequestCode; Device requested

The details of the device to be used.

pub fn code_ext(self, value: FieldExtension) -> DeviceRequestBuilder

Extension field.

pub fn quantity(self, value: i32) -> DeviceRequestBuilder

Quantity of devices to supply

The number of devices to be provided.

pub fn quantity_ext(self, value: FieldExtension) -> DeviceRequestBuilder

Extension field.

pub fn parameter( self, value: Vec<Option<DeviceRequestParameter>>, ) -> DeviceRequestBuilder

Device details

Specific parameters for the ordered item. For example, the prism value for lenses.

pub fn parameter_ext( self, value: Vec<Option<FieldExtension>>, ) -> DeviceRequestBuilder

Extension field.

pub fn subject(self, value: Reference) -> DeviceRequestBuilder

Focus of request

The patient who will use the device.

pub fn subject_ext(self, value: FieldExtension) -> DeviceRequestBuilder

Extension field.

pub fn encounter(self, value: Reference) -> DeviceRequestBuilder

Encounter motivating request

An encounter that provides additional context in which this request is made.

pub fn encounter_ext(self, value: FieldExtension) -> DeviceRequestBuilder

Extension field.

pub fn occurrence(self, value: DeviceRequestOccurrence) -> DeviceRequestBuilder

Desired time or schedule for use

The timing schedule for the use of the device. The Schedule data type allows many different expressions, for example. “Every 8 hours”; “Three times a day”; “1/2 an hour before breakfast for 10 days from 23-Dec 2011:”; “15 Oct 2013, 17 Oct 2013 and 1 Nov 2013”.

pub fn occurrence_ext( self, value: DeviceRequestOccurrenceExtension, ) -> DeviceRequestBuilder

Extension field.

pub fn authored_on(self, value: DateTime) -> DeviceRequestBuilder

When recorded

When the request transitioned to being actionable.

pub fn authored_on_ext(self, value: FieldExtension) -> DeviceRequestBuilder

Extension field.

pub fn requester(self, value: Reference) -> DeviceRequestBuilder

Who/what submitted the device request

The individual or entity who initiated the request and has responsibility for its activation.

pub fn requester_ext(self, value: FieldExtension) -> DeviceRequestBuilder

Extension field.

pub fn performer(self, value: CodeableReference) -> DeviceRequestBuilder

Requested Filler

The desired individual or entity to provide the device to the subject of the request (e.g., patient, location).

pub fn performer_ext(self, value: FieldExtension) -> DeviceRequestBuilder

Extension field.

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

DeviceRequestReason; Coded/Linked Reason for request

Reason or justification for the use of this device.

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

Extension field.

pub fn as_needed(self, value: bool) -> DeviceRequestBuilder

PRN status of request

This status is to indicate whether the request is a PRN or may be given as needed.

pub fn as_needed_ext(self, value: FieldExtension) -> DeviceRequestBuilder

Extension field.

pub fn as_needed_for(self, value: CodeableConcept) -> DeviceRequestBuilder

Device usage reason

The reason for using the device.

pub fn as_needed_for_ext(self, value: FieldExtension) -> DeviceRequestBuilder

Extension field.

pub fn insurance(self, value: Vec<Option<Reference>>) -> DeviceRequestBuilder

Associated insurance coverage

Insurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be required for delivering the requested service.

pub fn insurance_ext( self, value: Vec<Option<FieldExtension>>, ) -> DeviceRequestBuilder

Extension field.

pub fn supporting_info( self, value: Vec<Option<Reference>>, ) -> DeviceRequestBuilder

Additional clinical information

Additional clinical information about the patient that may influence the request fulfilment. For example, this may include where on the subject’s body the device will be used (i.e. the target site).

pub fn supporting_info_ext( self, value: Vec<Option<FieldExtension>>, ) -> DeviceRequestBuilder

Extension field.

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

Notes or comments

Details about this request 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>>, ) -> DeviceRequestBuilder

Extension field.

pub fn relevant_history( self, value: Vec<Option<Reference>>, ) -> DeviceRequestBuilder

Request provenance

Key events in the history of the request.

This might not include provenances for all versions of the request - only those deemed “relevant” or important. This SHALL NOT include the Provenance associated with this current version of the resource. (If that provenance is deemed to be a “relevant” change, it will need to be added as part of a later update. Until then, it can be queried directly as the Provenance that points to this version using _revinclude All Provenances should have some historical version of this Request as their subject.

pub fn relevant_history_ext( self, value: Vec<Option<FieldExtension>>, ) -> DeviceRequestBuilder

Extension field.

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

Builds a new DeviceRequestInner.

Errors

If a required field has not been initialized.

impl DeviceRequestBuilder

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

Finalize building DeviceRequest.

Trait Implementations

impl Default for DeviceRequestBuilder

fn default() -> DeviceRequestBuilder

Returns the “default value” for a type.