Generated Narrative: StructureDefinition ext-R5-Encounter.virtualService Name Flags Card. Type Description & Constraints Extension 0..* Extension(4.0.1) R5: Connection details of a virtual service (e.g. conference call) (new) #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:_datatype 1..1 Extension DataType slice for a FHIR R5 `VirtualServiceDetail` value #xD; url 1..1 uri "http://hl7.org/fhir/StructureDefinition/_datatype" #xD; value[x] 1..1 string Value of extension Fixed Value: VirtualServiceDetail #xD; extension:channelType 0..1 Extension R5: Channel Type (new) #xD; url 1..1 uri "channelType" #xD; value[x] 0..1 Coding Channel Type Binding: R5VirtualServiceTypeForR4 (0.1.0) (example): The purpose for which an extended contact detail should be used. #xD; extension:address 0..1 Extension R5: Contact address/number (new) #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:_datatype 1..1 Extension DataType slice for a FHIR R5 `ExtendedContactDetail` value #xD; url 1..1 uri "http://hl7.org/fhir/StructureDefinition/_datatype" #xD; value[x] 1..1 string Value of extension Fixed Value: ExtendedContactDetail #xD; extension:purpose 0..1 Extension R5: The type of contact (new) #xD; url 1..1 uri "purpose" #xD; value[x] 0..1 CodeableConcept The type of contact Binding: ContactEntityType (preferred): The purpose for which an extended contact detail should be used. #xD; extension:name 0..* Extension R5: Name of an individual to contact (new) #xD; url 1..1 uri "name" #xD; value[x] 0..1 HumanName Name of an individual to contact #xD; extension:telecom 0..* Extension R5: Contact details (e.g.phone/fax/url) (new) #xD; url 1..1 uri "telecom" #xD; value[x] 0..1 ContactPoint Contact details (e.g.phone/fax/url) #xD; extension:address 0..1 Extension R5: Address for the contact (new) #xD; url 1..1 uri "address" #xD; value[x] 0..1 Address Address for the contact #xD; extension:organization 0..1 Extension R5: This contact detail is handled/monitored by a specific organization (new) #xD; url 1..1 uri "organization" #xD; value[x] 0..1 Reference(Cross-version Profile for R5.Organization for use in FHIR R4(0.1.0) | Organization) This contact detail is handled/monitored by a specific organization #xD; extension:period 0..1 Extension R5: Period that this contact was valid for usage (new) #xD; url 1..1 uri "period" #xD; value[x] 0..1 Period Period that this contact was valid for usage #xD; url 1..1 uri "address" #xD; value[x] 0..1 Contact address/number #xD; valueUrl url #xD; valueString string #xD; valueContactPoint ContactPoint #xD; extension:additionalInfo 0..* Extension R5: Address to see alternative connection details (new) #xD; url 1..1 uri "additionalInfo" #xD; value[x] 0..1 url Address to see alternative connection details #xD; extension:maxParticipants 0..1 Extension R5: Maximum number of participants supported by the virtual service (new) #xD; url 1..1 uri "maxParticipants" #xD; value[x] 0..1 positiveInt Maximum number of participants supported by the virtual service #xD; extension:sessionKey 0..1 Extension R5: Session Key required by the virtual service (new) #xD; url 1..1 uri "sessionKey" #xD; value[x] 0..1 string Session Key required by the virtual service #xD; url 1..1 uri "http://hl7.org/fhir/5.0/StructureDefinition/extension-Encounter.virtualService" #xD; value[x] 0..0 Value of extension #xD; Documentation for this format
R5: Connection details of a virtual service (e.g. conference call) (new)
R5: `Encounter.virtualService` (new:VirtualServiceDetail)
This extension is part of the cross-version definitions generated to enable use of the element `Encounter.virtualService` as defined in FHIR R5 in FHIR R4. The source element is defined as: `Encounter.virtualService` 0..* `VirtualServiceDetail` Across FHIR versions, the element set has been mapped as: * R5: `Encounter.virtualService` 0..* `VirtualServiceDetail` Following are the generation technical comments: Element `Encounter.virtualService` has a context of Encounter based on following the parent source element upwards and mapping to `Encounter`. Element `Encounter.virtualService` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `Encounter.virtualService` has a context of Encounter based on following the parent source element upwards and mapping to `Encounter`. Element `Encounter.virtualService` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). 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 Encounter.participant BackboneElement.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
DataType slice for a FHIR R5 `VirtualServiceDetail` value
Slice to indicate the presence of a R5 `VirtualServiceDetail` in FHIR R4
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 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.
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 of the definition for the extension code - a logical name or a URL.
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).
R5: `VirtualServiceDetail.channelType` (new:Coding)
Element `VirtualServiceDetail.channelType` is not mapped to FHIR R4, since FHIR R5 `VirtualServiceDetail` is not mapped. Element `VirtualServiceDetail.channelType` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). 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.
Element `VirtualServiceDetail.channelType` is not mapped to FHIR R4, since FHIR R5 `VirtualServiceDetail` is not mapped. Element `VirtualServiceDetail.channelType` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
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.
The purpose for which an extended contact detail should be used.
R5: `VirtualServiceDetail.address[x]` (new:ContactPoint, ExtendedContactDetail, string, url)
Element `VirtualServiceDetail.address[x]` is not mapped to FHIR R4, since FHIR R5 `VirtualServiceDetail` is not mapped. Element `VirtualServiceDetail.address[x]` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DataType slice for a FHIR R5 `ExtendedContactDetail` value
Slice to indicate the presence of a R5 `ExtendedContactDetail` in FHIR R4
R5: `ExtendedContactDetail.purpose` (new:CodeableConcept)
Element `ExtendedContactDetail.purpose` is not mapped to FHIR R4, since FHIR R5 `ExtendedContactDetail` is not mapped. Element `ExtendedContactDetail.purpose` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). If no purpose is defined, then these contact details may be used for any purpose.
Element `ExtendedContactDetail.purpose` is not mapped to FHIR R4, since FHIR R5 `ExtendedContactDetail` is not mapped. Element `ExtendedContactDetail.purpose` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
If no purpose is defined, then these contact details may be used for any purpose.
R5: Name of an individual to contact (new)
R5: `ExtendedContactDetail.name` (new:HumanName)
Element `ExtendedContactDetail.name` is not mapped to FHIR R4, since FHIR R5 `ExtendedContactDetail` is not mapped. Element `ExtendedContactDetail.name` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). If there is no named individual, the telecom/address information is not generally monitored by a specific individual.
Element `ExtendedContactDetail.name` is not mapped to FHIR R4, since FHIR R5 `ExtendedContactDetail` is not mapped. Element `ExtendedContactDetail.name` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
The name of an individual to contact, some types of contact detail are usually blank.
If there is no named individual, the telecom/address information is not generally monitored by a specific individual.
R5: Contact details (e.g.phone/fax/url) (new)
R5: `ExtendedContactDetail.telecom` (new:ContactPoint)
Element `ExtendedContactDetail.telecom` is not mapped to FHIR R4, since FHIR R5 `ExtendedContactDetail` is not mapped. Element `ExtendedContactDetail.telecom` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
The contact details application for the purpose defined.
R5: `ExtendedContactDetail.address` (new:Address)
Element `ExtendedContactDetail.address` is not mapped to FHIR R4, since FHIR R5 `ExtendedContactDetail` is not mapped. Element `ExtendedContactDetail.address` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). More than 1 address would be for different purposes, and thus should be entered as a different entry,.
Element `ExtendedContactDetail.address` is not mapped to FHIR R4, since FHIR R5 `ExtendedContactDetail` is not mapped. Element `ExtendedContactDetail.address` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
More than 1 address would be for different purposes, and thus should be entered as a different entry,.
R5: This contact detail is handled/monitored by a specific organization (new)
R5: `ExtendedContactDetail.organization` (new:Reference(Organization))
Element `ExtendedContactDetail.organization` is not mapped to FHIR R4, since FHIR R5 `ExtendedContactDetail` is not mapped. Element `ExtendedContactDetail.organization` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Some specific types of contact information can be an handled by an organization (eg legal council is via a specific firm). Element `ExtendedContactDetail.organization` is not mapped to FHIR R4, since FHIR R5 `ExtendedContactDetail` is not mapped. Element `ExtendedContactDetail.organization` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
This contact detail is handled/monitored by a specific organization
This contact detail is handled/monitored by a specific organization. If the name is provided in the contact, then it is referring to the named individual within this organization.
R5: Period that this contact was valid for usage (new)
R5: `ExtendedContactDetail.period` (new:Period)
Element `ExtendedContactDetail.period` is not mapped to FHIR R4, since FHIR R5 `ExtendedContactDetail` is not mapped. Element `ExtendedContactDetail.period` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). If the details have multiple periods, then enter in a new ExtendedContact with the new period.
Element `ExtendedContactDetail.period` is not mapped to FHIR R4, since FHIR R5 `ExtendedContactDetail` is not mapped. Element `ExtendedContactDetail.period` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Period that this contact was valid for usage
Period that this contact was valid for usage.
If the details have multiple periods, then enter in a new ExtendedContact with the new period.
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).
R5: Address to see alternative connection details (new)
R5: `VirtualServiceDetail.additionalInfo` (new:url)
Element `VirtualServiceDetail.additionalInfo` is not mapped to FHIR R4, since FHIR R5 `VirtualServiceDetail` is not mapped. Element `VirtualServiceDetail.additionalInfo` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This web address can be used to provide additional details on the call, such as alternative/regional call in numbers, or other associated services.
Element `VirtualServiceDetail.additionalInfo` is not mapped to FHIR R4, since FHIR R5 `VirtualServiceDetail` is not mapped. Element `VirtualServiceDetail.additionalInfo` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
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.
R5: Maximum number of participants supported by the virtual service (new)
R5: `VirtualServiceDetail.maxParticipants` (new:positiveInt)
Element `VirtualServiceDetail.maxParticipants` is not mapped to FHIR R4, since FHIR R5 `VirtualServiceDetail` is not mapped. Element `VirtualServiceDetail.maxParticipants` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). 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.
Element `VirtualServiceDetail.maxParticipants` is not mapped to FHIR R4, since FHIR R5 `VirtualServiceDetail` is not mapped. Element `VirtualServiceDetail.maxParticipants` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
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.
R5: Session Key required by the virtual service (new)
R5: `VirtualServiceDetail.sessionKey` (new:string)
Element `VirtualServiceDetail.sessionKey` is not mapped to FHIR R4, since FHIR R5 `VirtualServiceDetail` is not mapped. Element `VirtualServiceDetail.sessionKey` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). 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.
Element `VirtualServiceDetail.sessionKey` is not mapped to FHIR R4, since FHIR R5 `VirtualServiceDetail` is not mapped. Element `VirtualServiceDetail.sessionKey` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
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.