Stream: argonaut
Topic: scheduling / Issue #41 Procedure-based scheduling support
argo-scheduling-bot (Sep 12 2017 at 21:23):
cooperthompson opened Issue #41
9/22/17 - PA/SOA joint scheduling meeting comments:
Add support to the $find operation for providing the order as an input (in lieu of specialty/location/appt-type).
This would support scheduling of specific procedures (i.e. CT with contrast with specific laterality/positioning).
Michael Donnelly (Sep 12 2017 at 21:24):
What resource would the order be? ProcedureRequest?
Eric Haas (Sep 12 2017 at 22:46):
y
Jenni Syed (Sep 12 2017 at 22:56):
I hope as alternative and not as full replacement of existing params?
Cooper Thompson (Sep 12 2017 at 23:02):
Yes - as an alternative. It would probably be either this or the other (relevant) params. Dunno if we want to actually make a constraint to make it mutually exclusive, but in practice it probably would be.
Michael Donnelly (Sep 13 2017 at 15:49):
If it isn't exclusive, we'd have to handle conflicts gracefully. Best to just avoid that.
argo-scheduling-bot (Sep 27 2017 at 00:30):
Healthedata1 commented on Issue #41
Would this be for patient scheduling or provider scheduling?
argo-scheduling-bot (Sep 27 2017 at 03:31):
Healthedata1 labeled Issue #41
argo-scheduling-bot (Sep 27 2017 at 19:50):
Healthedata1 commented on Issue #41
Future Scope
argo-scheduling-bot (Nov 01 2017 at 00:20):
Healthedata1 labeled Issue #41
Last updated: Apr 12 2022 at 19:14 UTC
