Struct LocationBuilder

Source

pub struct LocationBuilder { /* private fields */ }

Expand description

Builder for LocationInner.

Implementations§

Source §

impl LocationBuilder

Source

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

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.

Source

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

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.

Source

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

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.

Source

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

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

Source

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

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.

Source

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

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.

Source

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

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.

Source

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

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.

Source

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

Unique code or number identifying the location to its users

Unique code or number identifying the location to its users.

Source

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

Extension field.

Source

pub fn status(self, value: LocationStatus) -> LocationBuilder

LocationStatus; active | suspended | inactive

The status property covers the general availability of the resource, not the current value which may be covered by the operationStatus, or by a schedule/slots if they are configured for the location.

Source

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

Extension field.

Source

pub fn operational_status(self, value: Coding) -> LocationBuilder

OperationalStatus; The operational status of the location (typically only for a bed/room)

The operational status covers operation values most relevant to beds (but can also apply to rooms/units/chairs/etc. such as an isolation unit/dialysis chair). This typically covers concepts such as contamination, housekeeping, and other activities like maintenance.

Source

pub fn operational_status_ext(self, value: FieldExtension) -> LocationBuilder

Extension field.

Source

pub fn name(self, value: String) -> LocationBuilder

Name of the location as used by humans

Name of the location as used by humans. Does not need to be unique.

If the name of a location changes, consider putting the old name in the alias column so that it can still be located through searches.

Source

pub fn name_ext(self, value: FieldExtension) -> LocationBuilder

Extension field.

Source

pub fn alias(self, value: Vec<Option<String>>) -> LocationBuilder

A list of alternate names that the location is known as, or was known as, in the past

A list of alternate names that the location is known as, or was known as, in the past.

There are no dates associated with the alias/historic names, as this is not intended to track when names were used, but to assist in searching so that older names can still result in identifying the location.

Source

pub fn alias_ext(self, value: Vec<Option<FieldExtension>>) -> LocationBuilder

Extension field.

Source

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

Additional details about the location that could be displayed as further information to identify the location beyond its name

Description of the Location, which helps in finding or referencing the place.

Source

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

Extension field.

Source

pub fn mode(self, value: LocationMode) -> LocationBuilder

LocationMode; instance | kind

Indicates whether a resource instance represents a specific location or a class of locations.

This is labeled as a modifier because whether or not the location is a class of locations changes how it can be used and understood.

Source

pub fn mode_ext(self, value: FieldExtension) -> LocationBuilder

Extension field.

Source

pub fn type(self, value: Vec<Option<CodeableConcept>>) -> LocationBuilder

LocationType; Type of function performed

Indicates the type of function performed at the location.

Source

pub fn type_ext(self, value: Vec<Option<FieldExtension>>) -> LocationBuilder

Extension field.

Source

pub fn contact( self, value: Vec<Option<ExtendedContactDetail>>, ) -> LocationBuilder

Official contact details for the location

The contact details of communication devices available at the location. This can include addresses, phone numbers, fax numbers, mobile numbers, email addresses and web sites.

The address/telecom use code ‘home’ are not to be used. Note that these contacts are not the contact details of people who provide the service (that would be through PractitionerRole), these are official contacts for the Healthcare itself for specific purposes. E.g. Mailing Addresses, Billing Addresses, Contact numbers for Booking or Billing Enquiries, general web address, web address for online bookings etc.

If this is empty (or the type of interest is empty), refer to the organization’s contacts.

Source

pub fn contact_ext(self, value: Vec<Option<FieldExtension>>) -> LocationBuilder

Extension field.

Source

pub fn address(self, value: Address) -> LocationBuilder

Physical location

Physical location.

Additional addresses should be recorded using another instance of the Location resource, or via the Organization.

Source

pub fn address_ext(self, value: FieldExtension) -> LocationBuilder

Extension field.

Source

pub fn form(self, value: CodeableConcept) -> LocationBuilder

LocationForm; Physical form of the location

Physical form of the location, e.g. building, room, vehicle, road, virtual.

Source

pub fn form_ext(self, value: FieldExtension) -> LocationBuilder

Extension field.

Source

pub fn position(self, value: LocationPosition) -> LocationBuilder

The absolute geographic location

The absolute geographic location of the Location, expressed using the WGS84 datum (This is the same co-ordinate system used in KML).

To define a boundary shape for this location use the standard extension [http://hl7.org/fhir/StructureDefinition/location-boundary-geojson](http://hl7.org/fhir/extensions/StructureDefinition-location-boundary-geojson.html), and search using the contains special search parameter.

Source

pub fn position_ext(self, value: FieldExtension) -> LocationBuilder

Extension field.

Source

pub fn managing_organization(self, value: Reference) -> LocationBuilder

Organization responsible for provisioning and upkeep

The organization responsible for the provisioning and upkeep of the location.

This can also be used as the part of the organization hierarchy where this location provides services. These services can be defined through the HealthcareService resource.

Source

pub fn managing_organization_ext(self, value: FieldExtension) -> LocationBuilder

Extension field.

Source

pub fn part_of(self, value: Reference) -> LocationBuilder

Another Location this one is physically a part of

Another Location of which this Location is physically a part of.

Source

pub fn part_of_ext(self, value: FieldExtension) -> LocationBuilder

Extension field.

Source

pub fn characteristic( self, value: Vec<Option<CodeableConcept>>, ) -> LocationBuilder

LocationCharacteristic; Collection of characteristics (attributes)

Collection of characteristics (attributes).

These could be such things as is wheelchair accessible.

Source

pub fn characteristic_ext( self, value: Vec<Option<FieldExtension>>, ) -> LocationBuilder

Extension field.

Source

pub fn hours_of_operation( self, value: Vec<Option<Availability>>, ) -> LocationBuilder

What days/times during a week is this location usually open (including exceptions)

What days/times during a week is this location usually open, and any exceptions where the location is not available.

This type of information is commonly found published in directories and on websites informing customers when the facility is available.

Specific services within the location may have their own hours which could be shorter (or longer) than the locations hours.

Systems may choose to render availability differently than it is exchanged on the interface. For example, rather than “Mon, Tue, Wed, Thur, Fri from 9am-12am; Mon, Tue, Wed, Thur, Fri from 1pm-5pm” as would be implied by two availableTime repetitions, an application could render this information as “Mon-Fri 9-12am and 1-5pm”.

The availableStartTime is the opening time, and the availableEndTime is the closing time.

Source

pub fn hours_of_operation_ext( self, value: Vec<Option<FieldExtension>>, ) -> LocationBuilder

Extension field.

Source

pub fn virtual_service( self, value: Vec<Option<VirtualServiceDetail>>, ) -> LocationBuilder

Connection details of a virtual service (e.g. conference call)

Connection details of a virtual service (e.g. shared conference call facility with dedicated number/details).

There are two types of virtual meetings that often exist:

a persistent, virtual meeting room that can only be used for a single purpose at a time,
and a dynamic virtual meeting room that is generated on demand for a specific purpose.

Implementers may consider using Appointment.virtualService for virtual meeting rooms that are generated on-demand.

Source