Coding vulnerable people

David Wanless
David Wanless
Tenth Anniversary Kudos 1 Name Dropper Participant
in Blackbaud CRM™ General Discussions
Hi all,

We've been asked by our Supporter Care team to work out a coding system for vulnerable people so that they know to be especially careful in dealing with them. Obviously, coding such is highly sensitive. Does anyone out there do so? What do you call the code? How do you decide when to apply it? Do you use a Constituency?

Thanks,

David.

Comments

  • Steven Finnell
    Steven Finnell
    Seventh Anniversary Kudos 1 Name Dropper Facilitator 1
    Hello Mr. Wanless,


    The organization I work for does not currently have any form of vulnerability coding but I believe the best way to approach this would be for it to be a constituent attribute. The reason it would be useful to be a constituent attribute is because you could have different categories that they fall into with different values associated with those categories (such as yes/no or a list of values from a code table). Attributes also have a related start and end date as well as a comment field that you can use to further flesh out any pertinent details.
  • Clint Grossnickle
    Clint Grossnickle Blackbaud Employee
    Eighth Anniversary Kudos 1 Name Dropper Participant
    Hi David, I agree with Steven in that a constituent attribute is probably the best solution for this type of coding. The constituent attribute can be added/removed in bulk by global change and permissioned by system security role. I have seen this type of coding achieved by using a constituent note type. The constituent note type can be permissioned by security role to limit access to a subset of the application users. This solution does not allow for bulk updates, nor does it contain an end date field. However, it does capture the author of the note as a first class field, note date, title and rich text for the content of the note. The constituent note type solution does not require creating another constituent attribute, in case limiting the number of attributes in the system is a concern. If this coding is only sparingly applied to records and there is no need to have a code table of values to further define the type of vulnerability, then this option might be viable.
  • David Wanless
    David Wanless
    Tenth Anniversary Kudos 1 Name Dropper Participant
    Thanks, Steven and Clint. I suspect we'll go with a Constituent Attribute and a Notification based on it, but that's not settled yet.

    Kind regards,

    David.

Categories