Stream: implementers
Topic: Flag Resource
Nick Jones (Feb 20 2017 at 12:16):
Just starting to look at the Flag resource as it is very relevant to one of our products (CAMS). I'll add more detail later but my first comment is about the language rather than the detailed content. We have a clear distinction in CAMS between Flags and Alerts. Flags are the patient attribute - i.e. Patient has MRSA, whereas the Alert is the warning that arises when an event makes that attribute relevant. So when a patient attends ER that MRSA Flag should cause an Alert to be raised - possibly a simple icon on the ER screen and/or an email to Infection Control. That separation of terms has certainly helped the implementation at Mid-Yorks -any thoughts?
Grahame Grieve (Feb 20 2017 at 12:54):
hi Nick. (met Nick in person yesterday and asked him to join us here!)
Grahame Grieve (Feb 20 2017 at 12:55):
I'm not clear on your differentiation. is it a category of different flag, or is it that the second case is active - to actually notify someone?
Nick Jones (Feb 20 2017 at 14:39):
It is mainly that the Alert is active. It is the relationship of an event with a flag that creates an alert. So 'patient has a dog' is a fact, not something I need to worry about. If I schedule a home visit then the alert is required. Maybe sounds a subtle distinction but a patient may have a number of flags and not all are significant to care all the time.
Lloyd McKenzie (Feb 20 2017 at 15:44):
Have you looked at DetectedIssue? That's probably what you need for your notion of the Alert. It lets you say "there's a potential issue here you may need to manage/mitigate. (And it could be that the mitigation is simply letting the appropriate care provider see the issue.)
Grahame Grieve (Feb 20 2017 at 17:23):
This advice seems to suggest that the existing text about detected issue in the flag resource could be improved.
Lloyd McKenzie (Feb 20 2017 at 23:21):
@Nicholas Jones Can you submit a change proposal?
Nicholas Jones (Feb 20 2017 at 23:38):
Hi @Lloyd McKenzie your message went through to the wrong Nick Jones, so I'll ping the other :) @Nick Jones
Last updated: Apr 12 2022 at 19:14 UTC
