Stream: implementers
Topic: Slots & Appointments
Richard Kavanagh (Jun 02 2016 at 16:37):
For a slot that is "busy" what is the best way to find the appointment that is using that slot.? Why does the slot not have a reference to appointment?
Elliot Silver (Jun 02 2016 at 18:01):
@Richard Kavanagh Generally, things that are created later have the reference back to things that are created earlier. Thus the Appointment, has a reference to the Slot(s) it occupies.
Now, why there isn't a search parameter on Appointment to find the appointments assoicated with a particular slot is a good question. Looks like a change request to me.
Richard Kavanagh (Jun 02 2016 at 19:37):
OK I see the logic there but it doesn't make life easy. I guess we'll just add an extension as in our use case the slot will only ever be associated with one appointment. Having to implement another route into finding appointments, especially a non standard one is probably harder in our case.
Brian Postlethwaite (Jun 06 2016 at 01:43):
Maybe log a change request to include the slot reference as a standard search parameter?
Brian Postlethwaite (Jun 06 2016 at 01:43):
Also, a slot may be busy for other reasons than having an appointment in it. And in the case of group sessions, the appointment might have multiple appointments associated (until the group max count is reached)
Brian Heiting (Jun 29 2016 at 21:10):
Is there a guideline for how to show appointment requests through the appointment resource? Generally, these are appointments requests that have been triggered by a future order being placed. It looks like these non-booked appointment requests could fall into the Appointment resource with a status of 'proposed', but if i also had a requested date range, would the 'start' and 'end' be appropriate places to give this information? I worry because for an appointment in any other status, the start and end represent the appointment's start and end, not a range that could cross days.
Brian Postlethwaite (Jun 29 2016 at 21:49):
The dynamic range request space used in clinical ro negotiation hasn't been explored/covered by the existing resource yet (haven't had people with experience come forward to assist and provide feedback - yet)
So as a result this would be extension space.
We would really like additional input to change this though (however is a little late for STU3 at this point)
Last updated: Apr 12 2022 at 19:14 UTC
