Stream: implementers
Topic: Appointment.reasonReference
Jose Costa Teixeira (Dec 05 2019 at 16:43):
Appointment.reasonReference points to a Procedure as "the reason the appointment is to take place". But if the appointment is to take place, the procedure does not exist yet, right? So how can Appointment point to it?
Jose Costa Teixeira (Dec 05 2019 at 16:44):
related: Can we have reasonReference pointing to xxxRequest and Task (and others)?
This reads: "You have an appointment because you have been requested to do/take this".
Lloyd McKenzie (Dec 05 2019 at 17:19):
In theory, it could be an ongoing procedure, but agree it makes more sense to point to ServiceRequest
Jose Costa Teixeira (Dec 05 2019 at 18:37):
..and medicationRequest (e.g. drugs that must be given by a nurse or are only dispensed in a hospital).
Other requests?
Jose Costa Teixeira (Dec 05 2019 at 18:43):
we can have an appointment for "getting a holter device". This would be ServiceRequest, but couldn'd it point directly to DeviceRequest?
Jose Costa Teixeira (Dec 05 2019 at 19:01):
https://jira.hl7.org/browse/FHIR-25276
(what is the shortcut to reference Jira tickets in zulip?)
Rob Hausam (Dec 07 2019 at 02:50):
it's J#25276
Rob Hausam (Dec 07 2019 at 02:56):
but GF#25276 also works
Cooper Thompson (May 24 2021 at 13:17):
We were looking at this suggestion during May 2021 WGM. We already have a basedOn(ServiceRequest) in Appointment and Encounter. Do you both think that it makes sense to also include it in the reason/reasonReference property?
Cooper Thompson (May 24 2021 at 13:18):
(we have some outstanding/unapplied trackers that will be updating the "reasonReference->reason" properties, but those are not adding ServiceRequest).
Last updated: Apr 12 2022 at 19:14 UTC
