Stream: implementers
Topic: Flag
David Reeves (May 15 2020 at 18:56):
Our source system has two types of "Alerts", administrative (verify birthdate) and safety (patient is potentially dangerous). We would like to put the safety alerts into the Flag resource, but where should we put the administrative alerts?
Lloyd McKenzie (May 15 2020 at 19:23):
"verify birthdate" sounds like a "to do", in which case I'd look at Task. That said, it's possible to put administrative type stuff in Flag too - it has categories so different types of users can see only certain things
David Reeves (Dec 02 2020 at 23:39):
I am now looking at the Flag Category ValueSet and it is quite different from our list of categories, which is:
- Advance Directive
- Administrative
- Allergy
- Check File
- Client Safety
- Duplicate Record
- Immunization
- Impairment
- Known Aliases
- Language
- Lives with Alternate Caregiver
- Mental Health
- MRSA+
- Phone
- Practitioner Safety
- Suicide Risk
- Temporary Address
- VRE+
Can we use all of these as Flag Categories, or should we be thinking differently here?...
Lloyd McKenzie (Dec 03 2020 at 00:02):
Some of those look more like specific Flag values rather than categories. "Lives with Alternate Caregiver" seems pretty specific. Category is more about who needs to see them - e.g. are these relevant to pharmacists, nurses, admin staff, etc. The Flag.code would convey the details of exactly what is being conveyed. That said, you can categorize multiple ways, so also having a category that says that this is "Allergy-related" or "Communication-related" or "Patient-safety" related is also reasonable.
Last updated: Apr 12 2022 at 19:14 UTC
