Stream: implementers
Topic: HealthcareService and Slot
Martin Grundberg (Apr 23 2019 at 12:21):
I have been looking into the overall scheduling domain (both traditional OP appointments and surgeries).
I think the core resources make up a really robust model:
*schedule
*slot
*appointment
When we look at a Slot, it is important to know what type of "service" is provided during that slot. This is supported like this:
serviceType 0.. CodeableConcept
The type of appointments that can be booked into this slot (ideally this would be an identifiable service - which is at a location, rather than the location itself). If provided then this overrides the value provided on the availability resource
Service type (Example)*
Question/Suggestion
Wouldn't it be better to instead reference aHealthcareService which is defined as a service that is provided at a certain location? This matches the description of the Slot's serviceType element as well.
This would also bring other benefits, such as specifying resource requirements for a service (this slot needs a certain staff type, equipment and/or room) which would then be attributes on the HealthcareService.
Lloyd McKenzie (Apr 23 2019 at 14:53):
@Brian Postlethwaite
Brian Postlethwaite (Apr 23 2019 at 22:11):
You are correct. The serviceType is there so that if the HealthcareService referenced has multiple types, the slot might have different availability for different types.
Brian Postlethwaite (Apr 23 2019 at 22:12):
And yes, would expect more often to find the HealthcareService reference to be used.
Can you please log a tracker and will try to make that clearer.
Brian Postlethwaite (Apr 23 2019 at 22:14):
While you're looking might also be worth noting that the slot gives the availability info without exposing appointments. So doesn't inadvertently expose info as part of normal design.
Martin Grundberg (Jun 11 2019 at 08:52):
Better late than never :)
https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=22687
And yes, the possibility of giving slot availability without the appointments is good, especially for finding available slots and similar use cases. For viewing a Schedule I think it is probably more likely that you will want to also see the Appointments as well. But there are scenarios there where you dont want to show the appointments. I know as an example that if you book and mange a clinicians schedule where the clinician works at multiple clinics you maybe want to see slots+appointments for the slots and appointments at the clinic you are booking for/at, but you are not allowed to see the appointments at the other clinic which the clinician is working at (but you of course still need to see busy slots as not available for you).
Brian Postlethwaite (Jun 10 2020 at 20:25):
When we reviewed this today, we noticed that above I didn't point out that the slot has a link to the schedule, which is for the healthcare service. And not all slots needs to exist.
The extra data on the slot was to provide capability to further restrict the applicability of the time slot.
We haven't ruled out changes, and added some notes into the tracker in Jira (sorry for being very slow on this one)
Given it's now been quite some time, how has the use of your extensions gone?
Last updated: Apr 12 2022 at 19:14 UTC
