Stream: argonaut
Topic: scheduling / Issue #45 Issues with fetching slots in PreF...
argo-scheduling-bot (Nov 02 2017 at 04:33):
Healthedata1 opened Issue #45
Assuming:
1. our goal is to get all the open slots for a service for all actors needed for that service.
1. client has a set of business rules to know what actors are needed to create an Appointmenr for a particular service
1. a "service based approach" can be used ( "visit type" links all the actors, schedules and slots together )Example: - visit-type = "Physical" - Set of rules for what is needed: - a Room (Location A) - a Doctor (Practitioner A) - a Nurse (Practitioner B)Getting open slots for type "Physical" --> just a pile of slots:
- need to first figure out which schedules are applicable (i.e., a room , a practitioner or a machine)
- 'Determining which schedules should be consulted often will involve searching via the properties of the referenced actors, such as the ServiceCategory on the HealthcareService, or the Address on a Location or the specialty on a PractitionerRole.'
Options:
- include schedules ( and possible recursively Location and PractitionerRole and Practitioner) in the search bundle (reconstruct on client side)
- filter Slots by chained search on schedule.actor ( all open slots for schedules with type = X and actor = PractitionerRole )
- Alternative: is to search by schedule by type and rev_include all open slots ( can't do this by standard search - custom operation )
- Alternative is to add actor extension to slot
argo-scheduling-bot (Nov 08 2017 at 04:32):
Healthedata1 labeled Issue #45
argo-scheduling-bot (Dec 13 2017 at 20:21):
Healthedata1 commented on Issue #45
separated prefetch with realtime WF:
specific to prefecth WF and search params. ...
follow up offline--2 questions;
# What (if any) search parameters
# _includes?
argo-scheduling-bot (Dec 13 2017 at 21:29):
brandon-larue-zocdoc commented on Issue #45
Start date and end date seem like minimal requirements, as the search needs to be bounded.
As a consumer of these, we like to be able to narrow down further - practitioner (via Schedule.actor is fine) and location are the best candidates, and requiring one but not both gives a lot of flexibility.
Cerner has a good pattern here: http://fhir.cerner.com/millennium/dstu2/scheduling/slot/ although they also require Slot.type (they're using DSTU2) which is isn't ideal for a pre-fetch scenario.
argo-scheduling-bot (Jan 03 2018 at 20:58):
Healthedata1 commented on Issue #45
same approach for polling updates.
diff
argo-scheduling-bot (Jan 03 2018 at 21:10):
Healthedata1 closed Issue #45
Last updated: Apr 12 2022 at 19:14 UTC
