Stream: cds hooks
Topic: order-dispatch
Lloyd McKenzie (Feb 03 2022 at 06:00):
As discussed on the CDS call, I've put forward the draft version of the order-dispatch hook. You can see the proposal here: https://github.com/cds-hooks/docs/pull/611
(@Isaac Vetter)
Isaac Vetter (Feb 07 2022 at 16:13):
There will be cases in which a referral is made to an organization, and then that performing organization sets a specific provider, and therefore the performing organization should also call order-dispatch. Is this an intended use-case? (that the performing org may also call this hook)
Isaac Vetter (Feb 07 2022 at 16:17):
Ongoing feedback about the name choice -- we talked about not using the more obvious term "referral" on a previous call, because of concern that "referral" is overloaded and doesn't have a clear or consistent definition in the industry; hence, a new term is useful. "dispatch" is the act of sending something, but (above question), wouldn't order-delegate or order-assigned be more accurate?
Isaac Vetter (Feb 07 2022 at 16:18):
cc/ @Kyle Johnsen
Lloyd McKenzie (Feb 07 2022 at 16:35):
That's possible. When an order gets to a 'performer', there's actually an "order encoding" step where the generic order is transformed into more detail - identifying more specific products/therapies, more specific service providers, more specific timing, etc. I've been considering this to be an appropriate use of order-select/order-sign, but it's probably best to clarify that. Certainly the cards that come back need to operate within the constraints of the parent order. E.g. might be reasonable to suggest switching to a generic rather than name-brand if that's allowed by the parent order, but probably not ok to propose a therapy not allowed by the original order.
I could accept order-assign. Not a fan of order-delegate as it's not really "delegation" because there isn't anyone responsible for the order before it's assigned.
Last updated: Apr 12 2022 at 19:14 UTC
