Services should have referral-stage tracking for securing benefit, item, etc.
We are not able to use services for most of our data collection needs, despite measuring a lot of securing or discussing benefits, items, identification, etc. That is because we need to measure whether a given item or benefit is just discussed as a topic, applied or attempted to acquire, secured, etc. Adding a couple optional questions that managers could configure to track the stages of a referral would meet so many more data collection needs, and allow us to actually use services.
Kat Freeman commented
There does not seem to be a cognitive link between Services and Referrals. One could think of referrals as a service, markedly changing the use of Services to document the depth of a referral and its outcome. The current Referral module seems only focused on sending an actual referral to a community queue or to another agency also using the same Clarity instance. This severely limits the usefulness of the Referral module. Additionally, there does not seem to be a cognitive link between the Referral module and Coordinated Entry, other than the referral to a community queue. This means duplicative and unaligned data entry between HUD data element 4.20 and the Referral module, again limiting its usefulness and value within the broader system. Currently, it does not appear that Clarity clients can customize either the Service or Referral module to properly document and align with HUD data elements or accurately document referrals and their outcomes. Giving system administrators the ability to customize both the Services and Referral modules would be incredibly helpful to communities whose partnerships go beyond active Clarity users.