Software & apps · Practice guide

Make shared and local clinic settings clear

Illustrative situation

One clinic changes a setting that unexpectedly alters the booking process for every location. Some choices belong to individual clinics; others affect the whole group. An unclear settings screen can turn a local adjustment into a group-wide problem. Show the coverage before saving and agree who approves wider changes.

Healthcare scheduling software, planning board and organised folders in a blue, white and orange office.
Choose software around the work your team needs to do.

What this means for your practice

Make it clear which settings affect the whole group and which affect only one clinic. Show the locations a change will affect before saving, and agree who can approve wider changes.

An example to discuss with your team

Change a local opening rule in a test system; other locations should retain their settings.

Healthcare software workflow connecting task cards, a checklist and a database.
Map the work and the information it depends on.
Healthcare software testing with normal paths and a separate exception route.
Test the exceptions as well as the normal workflow.

What to ask before you choose

Change one clinic's opening rule in a test system and check other sites retain their arrangements. Then inspect a shared setting and its approval route. Staff should recognise the difference before editing, with a history available to explain any unexpected effect later.

Show which locations a change will affect

Ask the supplier to label shared settings and local choices where staff actually edit them. A manager should not have to remember which screen changes one clinic and which changes the whole group. Before saving an important change, the affected locations should be clear.

Use a test example involving opening arrangements or a booking option. Change the local setting and check both that clinic and another location. Then demonstrate a shared change and the approval needed to make it. Include a local exception so the team can understand whether the shared update preserves it or intentionally replaces it. Keep a history that identifies the person and reason for a change. If staff discover an unexpected effect, they need someone who can investigate and an agreed route to restore the intended arrangement. Clear labels, appropriate permissions and representative checks work together; a warning message alone will not resolve uncertainty about who should be allowed to change the group's working rules.

How to check the result

Track cross-location effects discovered after a configuration change.

Turn reading into a next step

Your action checklist

Work through these checks with your team or supplier. Tick the ones you have resolved and leave unknowns open.

Checks to discuss

Record what you know, what is still missing and the answer you need from your team or supplier.

Use project decisions only, without personal, patient or confidential details. Entries stay in this page and are not submitted to Kay & Co. Copy or download before leaving; this page does not save your notes.

Further reading

These sources provide background for the topic. The practice examples and checklist are illustrative planning suggestions from Kay & Co.

Related guides

Need help with this?

Tell us what is getting in the way. Kay & Co. can help you understand the options and turn the next step into something that works for your practice.

Explore software & apps services or discuss your project.

Try the free Healthcare Digital Planner to find your starting priority.