pub struct VirtualServiceDetailInner {
pub id: Option<String>,
pub extension: Vec<Extension>,
pub channel_type: Option<Coding>,
pub channel_type_ext: Option<FieldExtension>,
pub address: Option<VirtualServiceDetailAddress>,
pub address_ext: Option<VirtualServiceDetailAddressExtension>,
pub additional_info: Vec<Option<String>>,
pub additional_info_ext: Vec<Option<FieldExtension>>,
pub max_participants: Option<NonZero<u32>>,
pub max_participants_ext: Option<FieldExtension>,
pub session_key: Option<String>,
pub session_key_ext: Option<FieldExtension>,
}Expand description
VirtualServiceDetail Type: Virtual Service Contact Details.
VirtualServiceDetail v5.0.0
Virtual Service Contact Details
Virtual Service Contact Details.
Fields§
§id: Option<String>Unique id for inter-element referencing
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
extension: Vec<Extension>Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the element. 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.
channel_type: Option<Coding>VirtualServiceType; Channel Type
The type of virtual service to connect to (i.e. Teams, Zoom, Specific VMR technology, WhatsApp).
As this type defines what the virtual service is, it then defines what address and additional information might be relevant.
Some profiles could be used for specific types to define what the other values could/should be.
channel_type_ext: Option<FieldExtension>Extension field.
address: Option<VirtualServiceDetailAddress>Contact address/number
What address or number needs to be used for a user to connect to the virtual service to join. The channelType informs as to which datatype is appropriate to use (requires knowledge of the specific type).
address_ext: Option<VirtualServiceDetailAddressExtension>Extension field.
additional_info: Vec<Option<String>>Address to see alternative connection details
Address to see alternative connection details.
This web address can be used to provide additional details on the call, such as alternative/regional call in numbers, or other associated services.
additional_info_ext: Vec<Option<FieldExtension>>Extension field.
max_participants: Option<NonZero<u32>>Maximum number of participants supported by the virtual service
Maximum number of participants supported by the virtual service.
Some services have only a limitted number of participants permitted to connect at a time, this is typically used in “shared” virtual services that you might find on location resources.
Typically on-demand services might not have these restrictions.
max_participants_ext: Option<FieldExtension>Extension field.
session_key: Option<String>Session Key required by the virtual service
Session Key required by the virtual service.
Some services require a session key to be able to access the service once connected.
This could be in cases where a shared number is used, and a session key is added to put into a private line, or to identify the participant in a call.
session_key_ext: Option<FieldExtension>Extension field.
Trait Implementations§
Source§impl Clone for VirtualServiceDetailInner
impl Clone for VirtualServiceDetailInner
Source§fn clone(&self) -> VirtualServiceDetailInner
fn clone(&self) -> VirtualServiceDetailInner
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more