Closed lmckenzi closed 5 years ago
It could be relevant for multiple types of users - admissions clerk/receptionist, nurse, physician. Each would have an interest in/influence on what tasks need to be done during the encounter and might have responsibility for following particular protocols, ensuring clinical trial requirements and/or payor requirements are met, etc. It would be up to the service to determine what sort of information to display based on user role. The timing of the hook is essentially when a user first deals with the encounter (or at least when they're in the early stages of dealing with the encounter). I'm not really sure how to nail it down much more than that with general applicability, though it's possible that EHR implementers might be able to tighten it a bit more if there's more concrete consistent implementation aspects we can tie it to.
Since we have consensus on the reviews, I'm going to merge this PR in. This is still in draft state and I expect the discussion to continue around this hook.
Thanks @lmckenzi for putting this hook together!
Hey @lmckenzi , overall, looks great!
Within the shoes of a CDS Client implementer, this description, while informative, is a bit loosey-goosey.
Do you think it's possible to more tightly specify the workflow or user type? It may be the case that we're not sure yet and more implementer feedback is needed to see if a tighter spec is possible. And that's okay.