Delivery channel of an appointment/encounter (in-person | video | telephone | secure message). A distinct axis from appointmentType (booking style); R5 models this as Appointment.virtualService. Value is CodeableConcept so a source/raw code and a normalized Nexus code co-exist; the binding is extensible so a future pan-Canadian/Ontario code can be added as a parallel coding.
Elements / Details
Every element this profile touches, with its full definition. Element names in the tables link here.
The delivery channel of the appointment or encounter: how the patient and provider
meet, as distinct from what service is delivered (serviceType) or how the slot was
booked (appointmentType).
Mapping onto an Encounter. Where the encounter is recorded, in-person becomes
Encounter.classAMB; video, telephone and secure-message all become VR
(http://terminology.hl7.org/CodeSystem/v3-ActCode). Encounter.class is bound, not
fixed, precisely so this mapping can be honoured: writing AMB for a video consult
asserts the visit happened in the room.
Populate the normalized coding from NexusEmrAppointmentModalityVS. When the source EMR
carries its own raw modality code (e.g. Oscar appointment.type = 'Telephone'),
converters SHOULD ALSO carry that raw code as an additional coding on the same
CodeableConcept, using the raw-code NamingSystem fallback
../NamingSystem/<instance-id>-appointment-modality-raw-code.
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.
Comments
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.
Comments
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.