🛠️ These articles include high-priority cards and their logic. If you notice a card you use is missing, please be assured we are working our way through them.

📖 Learning: This card is calculated by counting all the referrals received within the applied date range, breaking them down by status category.

There is a filter applied to this card to only show referrals relevant to clients who are assigned to the organisation currently viewing the dashboard.

For example, if a referral is tagged against a particular client, but the joy organisation ID assigned to that client does not match the organisation viewing the dashboard, that referral won't be included in the figures here. You must be in the organisation the client is managed under.

Similarly, if a client has been 🗑️ deleted within the CMS, any referrals for that client will not show. Their data is deleted from the system.

📖 Learning: This is calculated by counting all the referrals received within the applied date range, matching them with the service that the referral was sent into.

This is done by linking the referral to the corresponding transaction record (the referral that was sent), looking for the listing connected to that transaction record and returning the title of the listing, for any listings created by someone within the correct organisation.

There is a filter applied to this card to only show referrals relevant to clients who are assigned to the organisation currently viewing the dashboard. For example, if a referral is tagged against a particular client, but the joy organisation ID assigned to that client does not match the organisation viewing the dashboard, that referral won't be included in the figures here

📌 Note: this card was not previously filtering out clients who had been deleted in the CMS, leading to a mismatch in the number of referrals shown on this card vs. other inbound referrals cards.
​
​An update to this has been rolled out as of 15/04/25.

📖 Learning: This is calculated by counting all the referrals received within the applied date range, finding all of the reasons included in the why_like_to field (reason for referral) and the additional_needs field (additional needs) and counting the number of times each reason appears within the list.

There is a filter applied to this card to only show referrals relevant to clients who are assigned to the organisation currently viewing the dashboard.

For example, if a referral is tagged against a particular client, but the joy organisation ID assigned to that client does not match the organisation viewing the dashboard, that referral won't be included in the figures here.

📌 Note: referrals can have more than one reason, so the number of reasons is likely to be higher than the total number of referrals.

📖 Learning: This is calculated by counting all the referrals received for the viewing organisation within the applied date range, finding the title of the 'invited by org' (the referring organisation) on the referral record and counting the number of referrals that have come from each different org. If there is no inviting org, we show this as 'Unknown/Self'.

There is a filter applied to this card to only show referrals relevant to clients who are assigned to the organisation currently viewing the dashboard.

For example, if a referral is tagged against a particular client, but the joy organisation ID assigned to that client does not match the organisation viewing the dashboard, that referral won't be included in the figures here.

📌 Note: The client created_at filter does not apply to this card, the date instead filters by when the referral was received.

📖 Learning: For this card, we find all the referral records with the same joy_organization_id as the viewing user within the applied date range.

We then remove any records where the associated client has been deleted in the CMS and count the number of referrals attributed to each GP surgery listed against any of the referrals within the filtered list.