A clinic group needs to see across locations without giving every staff member access to everything. The buying decision starts with who needs to see a record, where they work and what they are allowed to do with it.
“Multi-branch” can describe very different arrangements: a location switcher, a central operations view, shared patient records or consolidated financial reporting. Ask the vendor to demonstrate each requirement separately. The presence of one does not establish the others.
Map the jobs before assigning access
List the responsibilities at each location and at HQ. Separate viewing information from changing it. A receptionist may need to manage arrivals at one branch; a covering doctor may need authorised clinical access at another; a group manager may need an operational overview without editing the clinical record.
- Reception: which locations, appointment and contact information, queue actions and payment tasks are required?
- Doctor: which locations and visit records are accessible, and which clinical sections can be edited?
- Dispensing team: which prescriptions, inventory and supply actions belong to the role?
- HQ operations: which locations and operational views are needed, and which changes require branch ownership?
- Temporary cover: when should access begin, change or end, and who approves it?
Turn that list into a simple role-and-location worksheet. For each action, record allowed or denied and the reason. Use it during the demonstration instead of testing every screen with an administrator login.
Distinguish group oversight from a shared clinical chart
A manager seeing appointments across branches does not necessarily have access to consultation notes. Likewise, seeing a contact in an HQ view does not prove that all of the person’s clinical history is shared between locations.
Watson’s group records view provides defined operational information for bookings, contacts, catalogue, team, inbox and scheduling. It uses limited views of those records rather than exposing raw clinical records through the HQ list. Clinical access remains subject to the relevant permissions and location assignments.
If a shared clinical-history workflow is essential to your group, demonstrate that exact scenario: a returning patient visits another branch, an authorised clinician opens the appropriate information and an unauthorised user cannot. Do not infer the answer from an operational contact search.
The Clinic groups page explains Watson’s location structure and authorised oversight. Review the Clinical records page separately for the clinician-operated workspace.
Test access with ordinary staff accounts
- A branch receptionist opens their own location and tries another location. Confirm both the intended access and the denial.
- A doctor covers a second branch. Add the approved assignment, verify the required work, then remove that assignment and check access again.
- An HQ user reviews a supported group view, filters by location and opens the appropriate operational detail.
- A staff member changes role or leaves. Remove the access and test an already signed-in session.
- A user can view a clinical section but lacks permission to edit it. Verify that changing a record is rejected.
Watson establishes current access from stored assignments and permissions. A broad login role alone does not grant every clinic action. The important acceptance result is that the permitted task works and the prohibited task is denied, including after staff responsibilities change.
Use synthetic records for access demonstrations. Capture the role, location, action and observed result so a future administrator can understand the intended setup.
Keep physical inventory tied to the location
Group oversight and shared catalogue information do not turn medicine held at one branch into stock available on another branch’s shelf. Confirm where quantities, batches, expiry and dispensing movements belong.
Watson’s pharmacy inventory is location-scoped. If your group needs inter-branch transfers or pooled purchasing, ask to see the precise supported workflow and the records at both ends. Do not assume that a shared medicine name provides a complete transfer process.
Use the Pharmacy and inventory walkthrough to review the local stock model with the dispensing team.
Compare reports using the same definition
Before comparing branches, write down the reporting period, time zone, location scope and event being counted. A booking made this week may be for a visit next week. A payment collected today may relate to a service delivered earlier. Both figures can be correct while answering different questions.
- Appointments created: when the appointment was made, which differs from the date of attendance.
- Patients or visits served: the completed operational event, using a consistent treatment of appointments and walk-ins.
- Collected payments: money recorded through the payment workflow over the selected period.
- Delivered-service revenue: the value of services recognised as delivered over the selected period.
- Waiting and service times: the relevant start and end states, period and location, including how incomplete visits are treated.
Watson’s operational reporting separates payment collection from delivered-service revenue. Its front desk and general analytics views also have their own available reporting periods. Match the filters and understand the measure before presenting a branch comparison.
The Clinic reporting page describes those views. A consolidated accounting report or a shared financial dashboard should be verified as its own requirement; group access does not establish that capability.
Decide how patient communication reaches a branch
When a group uses a shared patient channel, establish how the patient chooses a location and how the team knows which branch owns the next action. Test a new enquiry, a booking request and a reply that needs a person.
Watson supports branch selection on supported shared-channel journeys. Review the configuration and handover for the channel your group intends to connect. Confirm what information follows the conversation and what the receiving staff member is authorised to see.
The Patient communication page shows the administrative conversation and human handover. Keep clinical instructions with the qualified clinic team.
Document the boundaries before rollout
Finish the evaluation with an agreed access worksheet, demonstrated workflows and a list of unresolved requirements. Name the owner for each shared function and the person who will review access when staff or branch responsibilities change.
Review the clinical data scope and access arrangements alongside the applicable agreement. Watson’s Security and patient data page sets out the questions to confirm before onboarding.
A useful group system gives each person enough information to do their job and gives the group a consistent way to understand operations. Make those outcomes visible in the demo, then keep the tested boundaries in the rollout instructions.