Struct ServiceRequest 

pub struct ServiceRequest {

    pub id: Option<String>,
    pub meta: Option<Box<Meta>>,
    pub implicitRules: Option<Box<FHIRUri>>,
    pub language: Option<Box<FHIRCode>>,
    pub text: Option<Box<Narrative>>,
    pub contained: Option<Vec<Box<Resource>>>,
    pub extension: Option<Vec<Box<Extension>>>,
    pub modifierExtension: Option<Vec<Box<Extension>>>,
    pub identifier_: Option<Vec<Box<Identifier>>>,
    pub instantiatesCanonical: Option<Vec<Box<FHIRString>>>,
    pub instantiatesUri: Option<Vec<Box<FHIRUri>>>,
    pub basedOn: Option<Vec<Box<Reference>>>,
    pub replaces: Option<Vec<Box<Reference>>>,
    pub requisition: Option<Box<Identifier>>,
    pub status: Box<RequestStatus>,
    pub intent: Box<RequestIntent>,
    pub category: Option<Vec<Box<CodeableConcept>>>,
    pub priority: Option<Box<RequestPriority>>,
    pub doNotPerform: Option<Box<FHIRBoolean>>,
    pub code: Option<Box<CodeableConcept>>,
    pub orderDetail: Option<Vec<Box<CodeableConcept>>>,
    pub quantity: Option<ServiceRequestQuantityTypeChoice>,
    pub subject: Box<Reference>,
    pub encounter: Option<Box<Reference>>,
    pub occurrence: Option<ServiceRequestOccurrenceTypeChoice>,
    pub asNeeded: Option<ServiceRequestAsNeededTypeChoice>,
    pub authoredOn: Option<Box<FHIRDateTime>>,
    pub requester: Option<Box<Reference>>,
    pub performerType: Option<Box<CodeableConcept>>,
    pub performer: Option<Vec<Box<Reference>>>,
    pub locationCode: Option<Vec<Box<CodeableConcept>>>,
    pub locationReference: Option<Vec<Box<Reference>>>,
    pub reasonCode: Option<Vec<Box<CodeableConcept>>>,
    pub reasonReference: Option<Vec<Box<Reference>>>,
    pub insurance: Option<Vec<Box<Reference>>>,
    pub supportingInfo: Option<Vec<Box<Reference>>>,
    pub specimen: Option<Vec<Box<Reference>>>,
    pub bodySite: Option<Vec<Box<CodeableConcept>>>,
    pub note: Option<Vec<Box<Annotation>>>,
    pub patientInstruction: Option<Box<FHIRString>>,
    pub relevantHistory: Option<Vec<Box<Reference>>>,
}

A record of a request for service such as diagnostic investigations, treatments, or operations to be performed.

Fields

id: Option<String>

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

meta: Option<Box<Meta>>

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.

implicitRules: Option<Box<FHIRUri>>

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.

language: Option<Box<FHIRCode>>

The base language in which the resource is written.

text: Option<Box<Narrative>>

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: Option<Vec<Box<Resource>>>

These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.

extension: Option<Vec<Box<Extension>>>

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 manageable, 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.

modifierExtension: Option<Vec<Box<Extension>>>

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 manageable, 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).

identifier_: Option<Vec<Box<Identifier>>>

Identifiers assigned to this order instance by the orderer and/or the receiver and/or order fulfiller.

instantiatesCanonical: Option<Vec<Box<FHIRString>>>

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

instantiatesUri: Option<Vec<Box<FHIRUri>>>

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

basedOn: Option<Vec<Box<Reference>>>

Plan/proposal/order fulfilled by this request.

replaces: Option<Vec<Box<Reference>>>

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

requisition: Option<Box<Identifier>>

A shared identifier common to all service requests that were authorized more or less simultaneously by a single author, representing the composite or group identifier.

status: Box<RequestStatus>

The status of the order.

intent: Box<RequestIntent>

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

category: Option<Vec<Box<CodeableConcept>>>

A code that classifies the service for searching, sorting and display purposes (e.g. “Surgical Procedure”).

priority: Option<Box<RequestPriority>>

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

doNotPerform: Option<Box<FHIRBoolean>>

Set this to true if the record is saying that the service/procedure should NOT be performed.

code: Option<Box<CodeableConcept>>

A code that identifies a particular service (i.e., procedure, diagnostic investigation, or panel of investigations) that have been requested.

orderDetail: Option<Vec<Box<CodeableConcept>>>

Additional details and instructions about the how the services are to be delivered. For example, and order for a urinary catheter may have an order detail for an external or indwelling catheter, or an order for a bandage may require additional instructions specifying how the bandage should be applied.

quantity: Option<ServiceRequestQuantityTypeChoice>

An amount of service being requested which can be a quantity ( for example $1,500 home modification), a ratio ( for example, 20 half day visits per month), or a range (2.0 to 1.8 Gy per fraction).

subject: Box<Reference>

On whom or what the service is to be performed. This is usually a human patient, but can also be requested on animals, groups of humans or animals, devices such as dialysis machines, or even locations (typically for environmental scans).

encounter: Option<Box<Reference>>

An encounter that provides additional information about the healthcare context in which this request is made.

occurrence: Option<ServiceRequestOccurrenceTypeChoice>

The date/time at which the requested service should occur.

asNeeded: Option<ServiceRequestAsNeededTypeChoice>

If a CodeableConcept is present, it indicates the pre-condition for performing the service. For example “pain”, “on flare-up”, etc.

authoredOn: Option<Box<FHIRDateTime>>

When the request transitioned to being actionable.

requester: Option<Box<Reference>>

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

performerType: Option<Box<CodeableConcept>>

Desired type of performer for doing the requested service.

performer: Option<Vec<Box<Reference>>>

The desired performer for doing the requested service. For example, the surgeon, dermatopathologist, endoscopist, etc.

locationCode: Option<Vec<Box<CodeableConcept>>>

The preferred location(s) where the procedure should actually happen in coded or free text form. E.g. at home or nursing day care center.

locationReference: Option<Vec<Box<Reference>>>

A reference to the the preferred location(s) where the procedure should actually happen. E.g. at home or nursing day care center.

reasonCode: Option<Vec<Box<CodeableConcept>>>

An explanation or justification for why this service is being requested in coded or textual form. This is often for billing purposes. May relate to the resources referred to in supportingInfo.

reasonReference: Option<Vec<Box<Reference>>>

Indicates another resource that provides a justification for why this service is being requested. May relate to the resources referred to in supportingInfo.

insurance: Option<Vec<Box<Reference>>>

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

supportingInfo: Option<Vec<Box<Reference>>>

Additional clinical information about the patient or specimen that may influence the services or their interpretations. This information includes diagnosis, clinical findings and other observations. In laboratory ordering these are typically referred to as “ask at order entry questions (AOEs)”. This includes observations explicitly requested by the producer (filler) to provide context or supporting information needed to complete the order. For example, reporting the amount of inspired oxygen for blood gas measurements.

specimen: Option<Vec<Box<Reference>>>

One or more specimens that the laboratory procedure will use.

bodySite: Option<Vec<Box<CodeableConcept>>>

Anatomic location where the procedure should be performed. This is the target site.

note: Option<Vec<Box<Annotation>>>

Any other notes and comments made about the service request. For example, internal billing notes.

patientInstruction: Option<Box<FHIRString>>

Instructions in terms that are understood by the patient or consumer.

relevantHistory: Option<Vec<Box<Reference>>>

Key events in the history of the request.

Trait Implementations

impl Clone for ServiceRequest

fn clone(&self) -> ServiceRequest

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for ServiceRequest

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for ServiceRequest

fn default() -> ServiceRequest

Returns the “default value” for a type.

impl FHIRJSONDeserializer for ServiceRequest

fn from_json_str(s: &str) -> Result<Self, DeserializeError>

fn from_serde_value( obj: &Value, context: Context<'_>, ) -> Result<Self, DeserializeError>

impl FHIRJSONSerializer for ServiceRequest

fn serialize_value( &self, writer: &mut dyn Write, ) -> Result<bool, SerializeError>

fn serialize_extension( &self, writer: &mut dyn Write, ) -> Result<bool, SerializeError>

fn serialize_field( &self, field: &str, writer: &mut dyn Write, ) -> Result<bool, SerializeError>

fn is_fp_primitive(&self) -> bool

impl MetaValue for ServiceRequest

fn fields(&self) -> Vec<&'static str>

fn get_field<'a>(&'a self, field: &str) -> Option<&'a dyn MetaValue>

fn get_field_mut<'a>(&'a mut self, field: &str) -> Option<&'a mut dyn MetaValue>

fn get_index_mut<'a>( &'a mut self, index: usize, ) -> Option<&'a mut dyn MetaValue>

fn get_index<'a>(&'a self, _index: usize) -> Option<&'a dyn MetaValue>

fn typename(&self) -> &'static str

fn as_any(&self) -> &dyn Any

fn flatten(&self) -> Vec<&dyn MetaValue>