Stream: implementers
Topic: Scheduling - serviceType / service definition
René Spronk (Nov 22 2016 at 09:58):
Danish use-case: when scheduling for a specific kind of procedure (e.g. Cataract surgery) [as identified in appointment.serviceType] it is well known to the scheduling system as to what that entails in terms of resources, e.g. an operating room for 20 minutes, one eye surgeon for 15 minutes, 2 nurses for 30 minutes, etc.
The Danish use case requires that one has the ability (when creating the appointment request) to modify the definition, e.g. "this will be complicated, so let's schedule for longer than normal with an additional surgeon".
Question is how one defines a serviceType using FHIR resources.
StructureDefinition propably - or does anybody see other options?
Brian Postlethwaite (Nov 23 2016 at 06:26):
The HealthcareService resource?
(that you could discover from the services directory)
René Spronk (Nov 23 2016 at 08:40):
ok, so the fact that I'd need a particular kind of surgeon and 2 nurses would be coded as part of the HealthcareService.characteristics.
(in the above use case) the client would (1) query for the 'cataract surgery' HealthcareService from some service directory, (2) clone that resource to create a new HealthCareService (to state that it needs more human resources, or a longer duration), (3) reference that cloned HealthCareService resource (probably as a contained resource, it has little value beyond the scope of this appointment request) in the appointment request.
Brian Postlethwaite (Nov 23 2016 at 09:09):
That doesn't feel right, not sure why right now.
Its sounding more like the new template style resources (which I still need to get into more closely)
This is really depending on where the complexities of the internal mesh with the external.
Is the duration the time that we are advising the client, or planning for each portion?
(I think the latter is what you're talking about)
René Spronk (Nov 23 2016 at 13:04):
As I understand the Danish use-case, (a) the client queries for the "default definition" in terms of duration and resources (small r) associated with a clinical procedure [surgical procedures in their case], (b) they are allowed to modify that set of resources, (c) schedule an appointment with that modified set.
a, b, and c are definitional/templaty in nature.
René Spronk (Nov 23 2016 at 14:33):
@Allan Bro Hansen or @Niels Christain Bach - any comments on the discussion thus far ?
Allan Bro Hansen (Nov 25 2016 at 10:50):
@René Spronk - I have been sick for some days, and still am. Will surely like to give our input next week
Allan Bro Hansen (Dec 05 2016 at 15:50):
(Apologize for the late reply)
We use a kind of template, let's call it AppointmentTemplate just to have a new name for it :-).
The AppointmentTemplate holds a lot of default information for the Appointment.
E.g.
- the estimated participation time of certain kind of participants (E.g.: first 30 min: a Nurse, After 15 minutes, for 45 minutes: a Doctor) - like the requirement described by @René Spronk
- patient arrivaltime offset in respect to appointment.starttime
- the actual service carried out (Appointment.description)
- default patient guidance
Before booking an appointment the user must always choose a appointmentTemplate - the appointment keeps the reference to appointmentTemplate but does also keep it's own list of the AppoinemtTemplate-values (which may have been changed form the default).
In FHIR we have modelled this AppointmentTemplate as a DomainRessource (we only include a limited sets of elements) and the Appointment has an extension holding a reference to the AppointmentTemplate. To perform a booking our FHIR-clients must state the AppointmentTemplate along with other mandatory elements of the Appointment.
Last updated: Apr 12 2022 at 19:14 UTC
