Practice Wide Optimisations are applied to all patients, to reduce effort and workload where ever possible.
Access them via Settings -> Practice Wide Optimisations
1) Anchor Month
How:
Simply select which anchor type you wish to use. No need to do anything if you want to use the Last Medication Review (this will be used by default)
What it does:
We need an 'anchor' month to start all recall appointment patterns from. You choose if Patient Birthday or Last Medication Review is the best fit for your Practice.
This will be applied to ALL patients, for ALL recalls.
If you'd like to use the opportunity to transition from one to the other, the system will do all the heavy lifting, and we'll help highlight any long gaps between appointments are part of that transition in Set Up step 4.
Benefits:
do you want to adjust the anchor month to the Patient's birthday month?
We've seen significant improvement in Patient engagement where they have clear requirements provided
Used alongside our printable/PDF 'Personalised Annual Patient Plans' patients become much more proactive in booking appointments, saving the need for invites, and reductions in DNAs.
2) Tolerance Windows - driving auto-completions
How:
Each Test & Review frequency (1, 2, 3, 4, 6 or 12 months) will have it's own tolerance window which each Practice can customise based on days or weeks (calculated as 7 calendar days per week)
What it does:
The Tolerance Window defines how early a test or review can be completed and still count as 'up to date'.
This is to prevent a patient being invited for a test or review that has recently been completed
Tolerance Window Example:
A patient’s At Risk of Diabetes recall is due on 15 May - it's the '15th' based on Practice's selected 'anchor' Optimisation;
as either the Patient's Birthday is the 15th of the month,
OR their medication review was last undertaken on the 15th
This recall requires (among other tests) an HbA1c test every 12 months.
The tolerance window for 12 monthly frequency is set to 12 weeks (calculated as 84 days (12 weeks x 7 days))
Scenario 1 (mark as Completed)
- The patient has an HbA1c test on 1 April.
- This is within 84 days/12-weeks of the 15 May due date, so the test is valid for this recall cycle, the Recall is marked as Complete.
- The patient will not need to be invited for another blood test.Scenario 2 (not marked as Completed)
- The patient has an HbA1c test on 1 January.
- This is outside the 84 days/12-week tolerance window, so the test is not valid for this recall cycle.
- The patient will need to be invited in May for another blood test.
Benefits:
Automatically complete Tests & Reviews, and the Appointments they are within once they've happened
Patients where all required appointments are complete and filtered out of the Monthly Overview list for a clear list of pending patients needing attention.
Identify patients where only part of the appointments requirements are completed - keeping coding clean quickly, or recognising patients need another appointment
3) Merging Appointments
How:
No action needed, this is an automatic Optimisation
What it does:
Each patient may have 1 or more recalls, each with different appointment requirements at different frequencies.
Optimising appointments will seek to merge appointments of the same staff groups in the same month. e.g. 2 recalls both need blood tests - these ideally can be taken at the same time.
Benefits:
Massive reduction in required appointments just from organising them cleanly.
Next->
(1st Pilot Session) Set Up 3: Sync/Upload Clinical Data
(Between Pilot Sessions - optional) Set Up 4: EMIS Data Accuracy
(2nd Pilot Session) PRO - Deciding your workflows
(2nd Pilot Session) Day-to-Day Guide for Recall Admins
<- Previous
Set Up 1: Recall Logic (ASAP)
Set Up 2: Optimisations (1st Pilot Session)