Stream: implementers
Topic: Virtual Appointment JSON
Fran del Río (Mar 04 2022 at 16:13):
Hello. How can I represent an Appointment or modality of an appointment that will be held virtually? By Skype or Google Meet for example.
I thought it would be with appointmentType but the codesystem values are CHECKUP,EMERGENCY,FOLLOWUP,ROUTINE,WALKIN.
Gino Canessa (Mar 04 2022 at 16:24):
That is odd that Appointment and Slot use the (more limited) v2 Appointment Reason Codes while Encounter uses v3 Activity Encounter Codes to cover the same concepts.
Given that Appointment and Slot only have a preferred binding on the v2 set, I would guess that using http://terminology.hl7.org/CodeSystem/v3-ActCode#VR (from the v3 set) would be the route to go.
Lloyd McKenzie (Mar 04 2022 at 16:35):
@Brian Postlethwaite
Fran del Río (Mar 22 2022 at 18:19):
Could I then use v3-ActCode as Gino suggests or would that not be correct?
Lloyd McKenzie (Mar 22 2022 at 22:07):
With a preferred binding, you're free to use any codes you like. However, it would also be good to get the preferred set updated to a more useful value set.
Lloyd McKenzie (Mar 22 2022 at 22:07):
Care to submit a change request?
Last updated: Apr 12 2022 at 19:14 UTC
