For multi-location groups · Shared patient · local operating control
Connect your clinics. Keep access clear.
Link patient identity across clinics while keeping local schedules, contact cards, proposal reporting, case numbers and staff permissions clear.
PATIENT THREADPatient 024Crown delivery · action needed
01Teams need organisation-wide consistency without erasing local clinic context
02Staff should only access the locations and modules relevant to their role
03Patient and financial reporting needs a clear clinic scope
What changes during your clinic day
ONE CLINIC DAY
Connect patient history without opening every clinic to everyone.
Patient 024 is registered at one branch and attends another. Staff need the patient history, while the local contact card, proposal reporting, schedule, finance scope and activity review still belong to authorised clinic context.
×Teams need organisation-wide consistency without erasing local clinic context
×Staff should only access the locations and modules relevant to their role
×Patient and financial reporting needs a clear clinic scope
✓One selected clinic context
✓One connected patient journey
✓Explicit ownership for the next action
ONE PATIENT · FOUR HANDOFFS
See who does what during the clinic day.
Follow the booking, care and payment decisions through the people who handle them.
Select authorised clinic
A staff member selects the clinic they are authorised to work in. The local schedule, settings and records follow that selection.
PATIENT THREADPatient 024Crown delivery · action needed
Open its clinic contact card
Each clinic can publish its own contact card with the details it chooses to make public. The card does not capture enquiries or create patients.
PATIENT THREADPatient 024Crown delivery · action needed
Review location-scoped proposal
Authorised users review the proposal pipeline in the relevant clinic context instead of flattening every location into one list.
PATIENT THREADPatient 024Crown delivery · action needed
Inspect permitted activity
Operations review Clinic Audit activity only for the locations and actions their permissions allow. A source record remains protected by its own access.
PATIENT THREADPatient 024Crown delivery · action needed
AI WITH EXPLICIT REVIEW
A clearer picture without assuming access.
Ask within the signed-in workspace, inspect the selected reporting context and keep responsibility visible.
Explore AI Command“Show revenue by clinic for 1–21 September 2026.”
THIRTY2OS PREPARES
A clinic-level comparison linked to the underlying report available in the workspace.
Clinic scope
Make the active location explicit
Users select the clinic context in which they are working. Patient, appointment, financial and configuration workflows use organisation and clinic identifiers rather than relying on a location typed into free text.
Access
Assign staff to the clinics and roles they need
Staff profiles can be linked to one or more clinics and an access role. Permission checks and clinic access helpers remain part of the application workflow for protected records.
Multi-location operation still requires disciplined role design, joiner-leaver processes and periodic access review by the organisation.
Connected, not flattened
Link the patient while retaining local identifiers
A patient can be linked to multiple clinics and can carry per-clinic case numbers. Proposal and financial reporting can then be reviewed at the appropriate clinic scope using the records entered in Thirty2OS.
Each clinic can publish its own contact card. Permission-controlled Clinic Audit review helps authorised users investigate cross-clinic activity without assuming every staff member can see every location.
Local detail · shared routine
Keep templates, messages and follow-up in the right clinic context
Review the selected clinic before choosing a consent template, sharing an invoice or sending post-op instructions. Each location remains responsible for its approved content, provider setup and recipient eligibility.
Authorised teams can work from the relevant lab case, consent, invoice or proposal action without treating a network view as permission to open every record. Rehearse the workflow with restricted staff roles before rollout.
Rollout, responsibilities and clinic fit
ROLLOUT
Set up one branch, then test the handoff to another.
Link patient identity across clinics while keeping local schedules, contact cards, proposal reporting, case numbers and staff permissions clear.
- 01
Map access
Clinics, roles, staff assignments and joiner-leaver ownership.
- 02
Link local context
Patient identity, contact cards, local references and proposal records.
- 03
Review each location
Check location-aware proposal reporting and permission-controlled Clinic Audit activity before adding broader workflows.
PEOPLE · CHAIRS · LOCATIONS
Give each role the context it needs—and no assumed access beyond it.
Use this matrix as a discussion starter. The exact permission design must be reviewed against the clinic’s own responsibilities.
Cross-location governance
Role and clinic oversight
Review exceptions
Assigned locations
Contact-card and proposal consistency
Permission-controlled audit review
Selected clinic
Local schedule and patient work
No assumed other-branch access
Assigned clinic and patient
Authorised clinical context
Location-aware handoff
Configured scope
Invoice and payment review
Reconciliation ownership
FIT BOUNDARY
Know what still belongs to the clinic.
Software does not replace access reviews, joiner-leaver procedures or written responsibility for cross-location data decisions.
IMPLEMENTATION CHECK
Make one patient journey reliable before adding more automation.
Thirty2OS connects recorded work and applies configured access. It cannot make incomplete source data, unclear ownership or off-system decisions automatically reliable.
MAP THE REAL CLINIC
Start with the clinic day you already run.
Create a workspace free for 14 days, or book a demo when you want help mapping people, chairs and locations.