There are two approaches to documenting virtual appointments: Having an Appointment, where a participating location is virtual. Having an Appointment that is itself virtual. These approaches align with how we resolved FHIR-33341 . In both cases, you may want to know an Appointment or Location is virtual prior to know the details of the web conference technology, so we need a flag.   For Location: Now that Location allows for virtual locations, we'll update Location.physicalType  to:   Location.form   0..1 CodeableConcept (Example) virtual, room, bed, unit, building For consistency, we'll also update Encounter.location.physicalType to Encounter.location.form .  We will update the location-physical-type value set to: rename it to location-form Add a code for "virtual"   For Appointment: In FHIR-32341 , we are updating the Encounter.class value set to include "virtual".  Encounter.class also includes inpatient and outpatient classes, which may be valuable on Appointment.  We will add a new property, Appointment.class, that is identical to the Encounter.class as proposed in FHIR-32341 .