Type: Change Request
Status: Triaged (View Workflow)
Specification:FHIR Core (FHIR)
Raised in Version:STU3
Work Group:Patient Administration
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
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 ). If provided then this overrides the value provided on the availability resource"
Wouldn't it be better to instead from Slot reference a HealthcareService? HealthcareService is in itself defined as "The details of a healthcare service available at a location." which also matches the description of the Slot's serviceType element.
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.
Initially I looked into this from a Slot<-->HealthcareService perspective, but I can see that we should do the same thing from Appointment (allow possibility to reference a HealthcareService instead). This makes a complete solution for the core parts of creating a repository of services (HealthcareService), schedule capacity to provide the services (Slot), plan appointments for a certain service (Appointment for a HealthcareService) and then finally match the appointment into a corresponding slot for the correct service.
This has alos been discussed in this Zulip chat: