Per-clinic scope
Appointments, files and invoices operate inside the clinic scope, keeping data separated between locations.
When a clinic expands to more than one location, separating data and permissions becomes essential. Nasaq Care builds operations on a per-clinic scope with roles and permissions, and branch limits depend on the plan and settings available.
Quick summary: Nasaq Care organizes each branch independently while giving the owner a combined view where the plan allows it. Appointments, queues, invoices and data context stay tied to the selected branch, and permissions define who can see each branch, reducing mixed records and supporting performance review before opening a new branch.
When one branch\u2019s appointments mix with another branch\u2019s invoices in the same reports, tracking each location\u2019s performance becomes hard and permission errors increase. Nasaq Care separates each clinic\u2019s scope so data and oversight stay tied to their location.
Appointments, files and invoices operate inside the clinic scope, keeping data separated between locations.
Roles define who works on which scope, so a supporting plan can give the owner broader visibility while staff stay in their own scope.
Branch counts and limits appear within subscription plans, so you choose the plan that matches your actual expansion size.
The table describes a general operating difference, not a promise of a specific result for every clinic. Outcomes still depend on process discipline, permissions and the data actually recorded.
| Executive summary | Fragmented operations | Nasaq Care |
|---|---|---|
| Appointments | A schedule or messages kept separately | A schedule and online booking linked to the service and doctor |
| Patient file | Paper files or scattered folders | One record linked to visits, prescriptions and documents |
| Queue | Verbal calls and undocumented status | Shared waiting states and patient calls between reception and doctors |
| Billing | Invoices separated from the visit | An invoice linked to the patient, visit, payment and balance |
| Review | Manual reports prepared late | Operational reports according to permissions and clinic context |
The table does not mean every clinic needs the same steps; review team size, plan and permissions before relying on any capability.
When a second branch is on the near-term plan and you want a system that can absorb it.
When multiple locations operate and need clear separation of data and permissions.
When the owner needs oversight visibility as the plan allows, without mixing data.
No. Branch limits differ by plan. Review the subscriptions page to see each plan\u2019s limits before choosing.
The system builds operations on a per-clinic scope, and data separation between scopes is part of the permissions design.
This page does not promise data migration or transfer tools between branches. Available operations depend on what the system actually supports.
That depends on the limits of the selected plan, and limit details appear on the subscriptions page or by contacting the team.
Review branch limits across plans or contact Nasaq Care to explain your branch scenario.