Related to the existing idea advocating for 4.20 Coordinated Entry Events to be Service based Events instead of Inferred Events, (https://ideas.bitfocus.com/forums/930328-clarity-human-services/suggestions/43917810-provide-access-to-data-element-4-20-response-categ), there is an additional need related to how the 'Prioritization Status' associated with 4.19 Coordinated Entry Assessments is captured within Clarity.

Currently, the only way to capture that a client has been 'Placed on prioritization list' (4.19_7.1) is if the Coordinated Entry Assessment associated with the client is placed on a Community Queue. For communities that choose to take advantage of the CQ functionality offered by Clarity, this works well, but for communities who choose not to use it (oftentimes DV comparable databases who participate in their community’s CE process but only track data in the comparable database), this creates a barrier to capturing the information needed in the Coordinated Entry APR for 'Prioritization Status' associated with 4.19.

Please consider alternative methods/functionality for capturing the 'Prioritization Status' of clients receiving Coordinated Entry Assessments. An alternative method could greatly benefit communities who choose to abstain from using the Community Queue in still being able to generate required data for their Coordinated Entry APRs for table Q9b (Households Prioritized in the Date Range).