We'll update the scope and usage and resource description of Location to make it clear that Location can be used for virtual locations, such as virtual conference calls.   A new datatype will be created to represent virtual conference call details: VirtualServiceContactDetail 0..*      * channelType (Coding) i.e. Teams, Zoom, Specific VMR technology, WhatsApp      * address [x] 0..1 url | string | ContactPoint | ExtendedContactDetail // contact address/number       * additionalInfoURL 0..1 address to see alternative connection details         *maxParticipants 0..1      * sessionKey Code 0..1 string // session key (Should the shared values be cloned into the appt values?)   Appointment and Location will be updated to add a new virtualService property: Appointment.virtualService 0..* VirtualServiceContactDetail   Notes :  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 Location.virtualService for persistent meeting rooms. If each participant would have a different meeting link, an extension using the VirtualServiceContactDetail  can be applied to the Appointment.participant BackboneElement.   Location.virtualService 0..* VirtualServiceContactDetail   Notes :  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.