Stream: implementers
Topic: Appointments, eConsulting and Location
Alexander Henket (Jul 02 2019 at 10:05):
Suppose I'm booking an appointment for an eConsult: how do I convey the virtual location of that? In our use case we assume a URI to exist as starting point. This could be a webex/skype/zoom/fcc/http link.
Appointment could have a .participant.actor Location or HealthcareService that describes the virtual service. HealthcareService relies on Location for the actual 'address'.
Location is scoped to be a physical location, which seems to contradict the virtual notion of an eConsult. My initial leaning goes towards Location.telecom nonetheless.
Help appreciated. @Brian Postlethwaite?
Brian Postlethwaite (Jul 02 2019 at 10:19):
You're right there. The location has indeed been scoped to physical, the only wiggle room in the definition is jurisdiction, but that's not what you're after.
I thought it wasn't so tight, but that's what it is.
Healthcare servo e is feeling better, and would suggest an endpoint for the details of the service.
Could even schedule the HCS.
Dont need to have the location on the HCS if not needed.
Alexander Henket (Jul 02 2019 at 10:45):
Thanks. HealthcareService.endpoint is 0..*, so presumably when I want to say "please log in at this endpoint" I would have to make sure that my HealthcareService instance has a 1..1 connection to Endpoint.
Would scheduling an EndPoint actor directly from Appointment not make more sense? If you feel it deserves some discussion I could file a tracker for it?
Brian Postlethwaite (Jul 02 2019 at 11:44):
Specify which type of endpoint rather than constraing the reference.
Brian Postlethwaite (Jul 02 2019 at 11:45):
Healthcare services should have lots for various purposes.
Brian Postlethwaite (Jul 02 2019 at 11:45):
One for inbound referrals etc.
Last updated: Apr 12 2022 at 19:14 UTC
