Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
if the agency has geography (latitude, longitude), order by status, distance - “Open” resources at the top of the list
if the agency has no geography (latitude, longitude), order by status, name - “Open” resources at the top of the list
Medium
Default sorting
if the agency has geography (latitude, longitude), then ascending sort by distance
if the agency has no geography (latitude, longitude), then alpha sort
Connect with Tara on the table for Agency status table to ensure verification team training
Resource Verification UI
Medium
Revisit timeline on UI updates
Resource verification grouping functionality
Referrals workflow review
High
Support for non-eReferral tracking - Database design
Review referral workflow (capturing the referral made via print, share, resources coordinated, and ad-hoc)
Dec 4, 2020
Resource Verification UI
Revisit timeline on UI updates
Resource verification grouping functionality
Resources - DB
Resources & Referrals - UI (CCC/CRX)
High
CCC
Referral submission and management not via eReferrals (resource coordination through visit and tracking, print and share, resource not tracked in our CRX, etc.
Notes from 12/4/2020:
Request from 3 separate agencies
Visiting and tracking
Within an agency - track resource(s) that was referred to
tbl_pat_ereferrals and tbl_pat_ereferrals_media would be a one-many mapping, i.e., if a referral were sent via email/print out multiple times for the same referral (one record in tbl_pat_ereferral but multiple mapping records mapping into tbl_pat_ereferrals_media)
Update to DB structure to expand the concept of a resource beyond a physical service location, account for on-line services (no physical location), community events, seasonal/disaster relief services, documents, guild lines, information sheets, etc.
High
Resources & Referrals - UI (CCC/CRX)
Refer to the agency’s program
Prerequisite is program design and open referral design
Allow user to track the status (and make comments?) for printed or emailed agencies
Need to show All referrals made in one place for easier mgmt.
HFB team use case (aligned with what we discussed last week):
how they can suggest adding agencies they could not find in CRX (Legacy asked the same thing)
how to submit data update suggestions (Legacy asked the same thing)
How to refer to a specific program for an agency (for now, focus on internal HFB programs: CSFP, kids cafe,….)
Medium
Preferred agency search
Bookmarked agency search
Improve page performance - The resource display section (list, detail, and map) is repeated 3 times in code. Can be ascx-ed or load on demand.
Mandatory selection of specialty during eReferral submission. HFB wants to make it mandatory as the receiving agency. Should this apply as a general rule?
Resources & Referrals - API
Look into including Google Places API as an alternative directory?
Low
Nov 13, 2020
Resource Verification UI
Get feedback from Tara on Phase I & II features
Revisit the work plan on UI updates:
Q: Phases VS Iteration?
Look into data gathering for program level & eligibility (DB & UI support)
High
Open state
Open
Open but not accepting new clients/referrals
Opening soon*
Recently opened
Seasonal vs. Permanent (Ex. Back to school program)
Short term -or- Disaster services (Ex. Hurricane/pandemic)
@Swetha Kiledar Siddaramappa (Deactivated) check statuses on Open Referral and AIRS platforms
Suggested update to Closed status:
Temporarily closed
Some agencies have possible opening dates/”opening soon” status
Permanently closed
Never existed
Moved to a new location
Private place or home
Duplicate of another place
Spam or fake
It could not be verified
in some cases, the referring agency could have more information regarding this agency
Do not add these items to tbl_agency
Add workflow logic to re-verify this agency. If it cannot be verified after multiple attempts, remove it from the list
Display as “tried to verify - no information found”
On merge push to a separate table
CRX to return the agency status along with verified on date
The final status after the merge to be updated on the tbl_agency
Good to get the metrics of last cycle’s resource verification: to-do
x% was unable to be verified
y% did not get an email address
Analysis -Are we closing the gap? What’s the baseline?
List of errors picked up during the verification process
Analyze and refine the process
Allow user to report an error from CCC
Service-based queueing of unverified agency’s of MOU partner, CDX partners, CRX users, etc. - group them to identify the data fields to use
Adhoc queuing of agencies
batches - adding a new item or selecting from an existing list
based on the deployment’s preferred agencies
Flag - high priority - a specific set
visual component - “!”
placement component - always on top
Due date field - to help prioritize the unverified agencies
An integer priority/weight field to allow the verification manager to change the priority
Batch edit fields
One level above queue table to batch agencies to be verified for quick verification
Update to DB structure to expand the concept of a resource beyond a physical service location, account for on-line services (no physical location), community events, seasonal/disaster relief services, documents, guild lines, information sheets, etc.
Allow user to track the status (and make comments?) for printed or emailed agencies
Need to show All referrals made in one place for easier mgmt.
HFB team use case (aligned with what we discussed last week):
how they can suggest adding agencies they could not find in CRX (Legacy asked the same thing)
how to submit data update suggestions (Legacy asked the same thing)
How to refer to a specific program for an agency (for now, focus on internal HFB programs: CSFP, kids cafe,….)
High
Preferred agency search
Bookmarked agency search
Improve page performance - The resource display section (list, detail, and map) is repeated 3 times in code. Can be ascx-ed or load on demand.
Mandatory selection of specialty during eReferral submission. HFB wants to make it mandatory as the receiving agency. Should this apply as a general rule?
Log resources printed, shared, or emailed from the queue. Set them as inactive. Do not delete this. It will be a part of the list of resources “coordinated”/”referred.”
Resources & Referrals - API
Look into including Google Places API as an alternative directory?
Low
Nov 6, 2020
Resource Verification
Check-in on Phase II items and demo for feedback
Get feedback from Tara on Phase I features
Look into data gathering for program level & eligibility (DB & UI support)
High
Phase II feature demo:
Grid to show reviewed and approved for merge
“Rebranded” agency, what will be the
“Duplicate” supporting functionality design
Added
Notes from Nov 6, 2020
Status of service
Primary status - Open, temporarily closed, permanently closed, opening soon*
Secondary status - Duplicate of
Consider: Did something change? Change - Rebranded (need additional information to be captured)
Open state
Open
Open but not accepting new clients/referrals
Opening soon*
Recently opened
Seasonal vs. Permanent (Ex. Back to school program)
Short term -or- Disaster services (Ex. Hurricane/pandemic)
Closed state
Temporarily closed
Permanently closed
Never existed
Moved to a new location
Private place or home
Duplicate of another place
Spam or fake
It could not be verified
possible solution:
a mutually exclusive state
a second “reason for the change.”
delta change from the audit will provide additional information
Types of resources (beyond agencies with physical addresses)
Business logic needed for:
Time frame based status display (Ex. an agency that was recently opened moved it to open after 6 (or x) months
Action items
Set up a design and brainstorming meeting for the state and status of an agency discussion
Feedback from iteration I and II
Deploy on CRX prod
Review Tara’s access for CRX related Jira items @Nicolle Tamparong (Deactivated)
Resources - DB
Agency program & eligibility DB structure re-visit
Design to enable/disable e-ref for a resource (agency/program) on CRX
Re-visit concept of “Private Agency” (e.g., phone provider for HFB)
Track steps to apply for a service for an agency/program
Check-in on Phase I items and re-visit timeline to make sure we are still on target
High
Notes from 10/23/2020:
Metrics for resource verification (for each batch)
The verification platform is a good testbed for help video integration, and the framework can then be brought into CCC
Possible UoH communications internship for this effort
Bryan and Tara will explore this at UoH
API endpoints for resource verification
Claim a business
CRUD on verification agency queue
Ability to capture the response (or auto-responders) for an eReferral and ability to share that with CRX verification manager
Look into Google place API & Yelp API
Screenshots for ideas from Google
The idea for You submitted referrals to this agency last …..
Resources - DB
Resources & Referrals - UI (CCC/CRX)
Resources & Referrals - API
Communication
Security (no-reply@pcic.app)
Automated reminders for provider and patient - Care plan, calendar events
Capture patient’s response
Instantaneous (based on user actions)
Care member addition
Resource sharing with patient
Referral submission to an agency
Pre-enrollment (mail from -
Grouped status emails
Comments
New client submission
mail from for referrals:
referrals@pcic.app
email from
CRX
CCC custom deployments
Ex.: legacy-referrals@pcic.app
Ex.:
CCC Community Edition
Ex. Consent - legacy-consent.pcic.app
Next steps:
Notification use cases to review separate mail from addresses
Oct 16, 2020
Resource Verification
Review updated flow with Tara for feedbacks
Phases & timeline for verification UI feature updates
High
Reviewed updated workflow with Tara
Need to think about how duplicates need to be handled:
Linking to a primary record?
Remove if not related to any downstream data?
A chain of aliases names (searchable)
Discussed priority tiers and timeline, target to start Q4 verification week of Nov 4, 2020
Tara will be joining Friday CRX Tech meeting to provide feedback (frequency TBD)
Resources - DB
Moving program preferred agencies to CRX.
Medium
Since the “preferred agencies” are only applicable for PCIC resources, we can move the CCC data to CRX and link it with the program’s subscription ID. Once the master-resource-index is in play, we can update the IDs to reflect both PCIC and External resources (Ex: Welnity, Aunt Bertha). To retrieve this “preferred agencies” data, CCC need only send the program’s subscription ID.
Resources & Referrals - UI (CCC/CRX)
CCC
Improve search speed
Improve page load speed on preferred and bookmarked agencies
High
Resources & Referrals - API
Notes till Oct 9, 2020's discussion
Workflow
The output of the verification:
It could be the agency is shut down.
Tara provide feedback (with churches did not open every day, NPI agencies do not have reliable contact info)
Status of the resource
Duplicate
Add additional data field, ex: “reason,” to identify why there is a duplicate
OpenReferral has “alternative name,” maybe allowing the verifier to mark a link to another agency on CRX? (have to be supported with Merge function)
Functionality - Send it back to the data team (Ability to tag a team
Related to the Agency’s business details
Open - In business
Add “notes.” Ex: Magnificat House is open but not accepting any referrals
Closed
Permanently Closed
Temporarily Closed (expected re-open date?)
Renamed
Rebranded
If none of the checkboxes above are checked, then it is verification incomplete.
The screenshot above: UI change to review if this needs to be switched to a button or a dropdown (if there are other values)
Need to put in some approval process if new specialty category or specialties need to be added by the verifier, training on how this data needs to be gathered can also be strengthened (visually highlight the newly added ones for Tara)
General
Bi-directional communication
Comments on the verification process
View for “Pending review” → Group functions: Send back to the reviewer, enter comments and send back
Tooltip mode for an Agency in review grids
Batch-level grouping
UI view:
Data team to see information passed on to them
review the two notes fields that are used for verification
consider renaming the label
move from the “resource information” section to the “verification info” section
Review the potential to move the two text areas to :
Agency-specific notes
Notes were added when the agency was queued for verification.
What happens when a verifier cannot complete verification even after multiple attempts, hence submits it to the reviewer?
if the website is at least up to date
There should be a constraint to avoid not saving agency mark verification as complete and submit for review, shows saved from the front end. connect with Tara to clarify SOP
Need to track the status of the work separate from the status of the resource
In Phase II, the verifier will send a list of agencies that could not be verified via email (free form) to Tara.
Suggestion from Ela: a checkbox to indicate “could not verify.”
There is a note field for each supporting table (specialty, language, population, domain) Need more discussion on purpose of notes
Identify the use of notes and re-visit proper note fields to support
KM: is there a value to allow a verifier to post notes at different sections on the verification UI or just one note?
Internal communications within verifier & reviewer (comments - Phase I; chat - long term)
Q: Why are we keeping a permanently closed agency in CRX?
notify the community (or get notified from other directories)
backward compatibility for already sent e-referral
Open questions for design decision
Should the resources that we're unable to complete the verification process be queued automatically for the next quarter’s review process?
Algorithmically queuing agency, queued with configured priority (deployment-related preferred, new agencies, newly published list by partners/government agencies, other geo-location?)
Additional data points?
High-frequency agencies (commonly shared preferred agencies across deployments, high traffic e-ref agencies)
Rapid response resources (disaster recovery, pandemic, event-driven, changes to existing resources, etc.), and what is the ACTION needs to be taken?
community events, webinars, material
Looking into a healthy balance of resources which did not complete the verification process VS newly scheduled queue
How to prioritize the resources which did not complete the verification process (see notes from the last point)
