VirtualServiceDetail

• Datatypes
• Definitions
• Examples
• Mappings
• Profiles

Elements

• VirtualServiceDetail.channelType [0..1]: Coding The type of virtual service to connect to (i.e. Teams, Zoom, Specific VMR technology, WhatsApp).
• VirtualServiceDetail.address[x] [0..1]: url|string|ContactPoint|ExtendedContactDetail 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)
• VirtualServiceDetail.additionalInfo [0..*]: url A web address that provides additional details on the call, such as alternative/regional call in numbers, or other associated services.
• VirtualServiceDetail.maxParticipants [0..1]: positiveInt Maximum number of participants supported by the virtual service where there are limitations imposed.
• VirtualServiceDetail.sessionKey [0..1]: string Some systems require an additional factor/value be provided to access the service.

Bindings

• VirtualServiceDetail.channelType: VirtualServiceType | strength: value set | reference: valueset-virtual-service-type

Comments

• VirtualServiceDetail.channelType: 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.
• VirtualServiceDetail.maxParticipants: 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.
• VirtualServiceDetail.sessionKey: 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.