You are accessing documentation for Bp Allied version 5. This is not the latest version of Bp Allied.
Support for this product will cease on 1 November 2020
 
 
Due to changes in security requirements for the Medicare implementation using Medicare Online Claiming in Version 5 is longer available. Please contact our support team about upgrading to the latest version of BpAllied to enable this implementation.
Version 5
×
Menu

Synchronising Bp Allied

Synchronising is used by users of either using Bp Allied Live or those who have laptops out of the office.  All other comptuers have a direct connection to the database and do not require synchronisation. The Refresh button will be displayed in it's place.

Synchronising Bp Allied
1

Sync All button

1. Sync All button
Use Sync All to update all other Bp Allied information e.g Referrals or Client Details. 
 
It will not however, synchronise Invoice templates, Letter Templates or attached Client Documents. 
2

Sync Appointments button

2. Sync Appointments button
Use Sync Appointments to update your Appointment Book with changes to appointments others have made. The words turn red when you need to sync.
 
 
Two other things to watch out for on a synchronising version of Bp Allied are on the Status bar at the bottom of the screen.
 
If your online status turns red this means that you're either not connected to your local computer network or the internet (depending on your set-up). In some cases, this is valid e.g working on a laptop out of the office or with the internet disconnected.
 
If the Last Sync status turns red it's time to synchronise. Bp Allied has detected changes that need to be sychronised.
 
So, if changes can be detected, why doesn't Bp Allied update automatically?
The short answer is Performance.
 
The long answer is: We used to automatically do it but we took it out because it takes several seconds to redraw the screen and people got annoyed that when it would refresh while they were working on something else.We then tried some quite complex ideas involving detecting when the application was in use and waiting for a defined period after the last activity before refreshing. We also allowed a custom refresh time (eg 60 second or 30 seconds) – none of those worked because users would complain that the application was refreshing just as they switched back to it and appeared ‘frozen’ when it wasn’t.
 
So now, we leave it for you to decide.