During onboarding, it is important that we set up your branch sites right for you, to make go-live as smooth as possible!
ℹ️ We classify branch sites as those which use the same clinical system instance as the main site, and often have an ODS code which is an extension of the main site E.g. E81012001, with a parent of E81012.
What are the steps for setting up a branch site?
We provide separate registration form links for each branch site. This is so that the automation can determine where to register the patient.
Here is an example of how you might wish this to look on your website.
To help set this up effectively, please get in touch with us during onboarding with the following pieces of information.
Information to provide Healthtech-1
Does your branch site have a different catchment area to the main site?
As we provide more than one registration link, we suggest that you have one primary catchment area, so that patients are not restricted to which site they can register at.
Do your branch sites operate differently to your main site?
The main difference we see usually here is if the branch site is dispensing, when the main site is non-dispensing.
There may be other things, for example you would like some questions toggled on for a branch site, but not for the main site.
Do you do anything differently when registering a patient?
Practices often distinguish patients on their clinical system between branches by:
Different Usual GPs - this can be customised per branch
Utilising the Branch drop down on your Clinical System for the specific branch site
For EMIS practices only, entering text into the 'Records At' field during the Add Patient flow
How things will look for you
Registrations
When logged into the Hub, all registrations will be shown in the same place, just like in your clinical system. However, they are clearly labelled between the different sites you have linked.
Settings
You can change settings individually for each branch by clicking on the '⚙️ Settings' tab and picking your site.
Users
You can add users to all branches in one go by adding them to the parent practice. The below information box is an example of what this will look like.
