2024-03-15 - CRX Bi-Weekly Meeting

Recording

Video Conferencing, Web Conferencing, Webinars, Screen Sharing

Passcode: z#=Kw6CD

Community Engagement Team

March event’s

• 3/14 - Interagency meeting focus on Mental Health

• 3/20 - HFB Summit

• 3/26 - ESPN meeting

• VP to speak at HFB conference

Resource Data Management Team

1. There are a total of 3,799 active agencies spread across 6,685 locations.

2. Out of the total, 4,019 locations and 1,766 agencies have been verified.

3. Currently, there are 483 agencies pending completions.

4. Location geocoding part accuracy is up to 6 digit after decimal after latest full batch refresh. about 5000~ agency location has been ready, the target for refreshing Refernet agency data is set to be completed by end of March 2024.

5. Updated ReferNet data has been pushed into help database now. Primary key has not been changed since Feb. 2 new agency and 3 new locations, target to be updated by March 22. This is the 1st full refresh after Feb re-initial.

Resource Verification Team

• Utilizing status to indicate if agency is print only, intake online, information only status:not accepting XXX status:Print only creating ticket

  • Current service status in DB, different from Tag, stay as is -

  • Open

    

    UI similar like this?

    Open

    

• Placement to include how to document for first time community agents - create ticket

• Currently on production

  • Service Hours

  • Link

  • Languages

  • Required Documents

  • Status

  • Application Process (Hide)

  • Eligibility Requirement (Hide)

  • Contact Information - only show if linked to service or program

• Change for production

  • Service Hours (Required)

  • Link (Required)

  • Languages (Required)

  • Required Documents (Required)

  • Status (Required)

  • Accepting New Clients

• Service updates

  • Need accepting new clients

  • Need contact information

• Program updates

  • Need Required Documents

• What is displayed for programs on production

  • Need to separate Service and Programs

• adding status notification (use “/”) for items

  • stratify which referrals would be best suited for print, ereferral, email, etc. (feedback from ASF)

  • KM: is there a data point for this already?

• phase I: conveying information (multi-tags associated with referral using key words) → check on verification side for verbiage @Tara Pitts

  • look into functionality w/ tags

  • TP: I suggest putting it on the agency tab

    • KM: test it in multiple locations → would only be visible to partners on the service/ location levels; currently agency tab is a placeholder for information (no associated data points)

    • TP: if possible to have an option for “all services/ locations” that would be helpful

    • KM: on the training side, it will need to be known not to add conflicting statuses (e.g. active and inactive simultaneously)

    • keep current service statuses (as shown in img to the left); tags will be distinct from “statuses”

    • iteration I- add as many statuses as needed in drop-down format → add data points/ functionality later

• Re: linking documents to services

  • want to avoid difficulties for partners trying to locate the appropriate document by having to know the exact location/ service

  • add an icon to indicate an attached document to a resource/ service

  • what data points are we showing vs. not showing?

  • what does the data linkage look like (behind the scenes)? (look into this during the next session)

  • need to make this visible on CCC and calltracker (bulletin board function)

Software Development Team

• Accepting Client at Service

  • API Integration

  • Expose at CCC

• Show/Hide data points at CCC when no data available.

  • Identify data points - okay to be hidden

• Include email (Service side) at CCC Resource Details

  • Question: should we add email at program as well?

• CRX - CCC eReferral status sync up

  • CCC

  • CRX

    • Web

    • API

    • Webhook

• TP: the data points at the “service” level should be reflected on the “program” level

• HD: working on standardizing statuses across CRX and CCC