Branches, access and data

One account, multiple branches, every piece of data in its place.

Each branch has its own lots, balances and sanitary dossier. The catalog is maintained once for the chosen branches, and each person sees only the areas and branches they have been granted.

Facade of a neighbourhood compounding pharmacy.
Example · userAssignments
BranchesCentro (default) · Jardins
AreasPharmacy · Inventory
On sign-inopens at the default branch
Seeslots, balances and alerts for their branches
Does not seethe inventory of other branches

Illustrative values.

The branches agent

Caio shows who sees what. The pharmacy owner decides.

Caio sets up the branches, records the sanitary dossier for each one and explains why a menu or a branch does not appear for someone. Access is granted or revoked by the pharmacy owner.

Caio
CaioBranches and access · AI agent

Sets up the branches and shows which branches each person is linked to

Explains why a menu or a branch does not appear for someone

Records each branch’s sanitary dossier, without submitting anything to the health surveillance authority

Example · conversation with CaioAssignments
You

Why can’t Ana see the inventory at the Moema branch?

Caio
CaioAI agent

Ana is linked to the Centro branch (her default) and the Jardins branch, with the Pharmacy and Inventory areas. For her to see Moema, the pharmacy owner needs to link her to that branch as well.

Owner’s decision

Illustrative example.

By branch

What belongs to the branch stays in the branch.

Separate inventory

Lots, stock ledger, balances, receiving records, adjustments, movements, assays and expiration alerts belong to one branch and are only visible to the people who belong to it.

No orphan records

An operation without a branch is rejected before saving.

Sanitary dossier

Each branch has a dossier with the operating license and the person responsible for SNGPC (ANVISA’s controlled-substance reporting system). That person’s document is stored encrypted, and the SNGPC credential is kept separately, outside the regular fields. The dossier stores this data and does not transmit anything to SNGPC.

Shared

The catalog, maintained once.

Master data that applies to more than one store is linked to the branches you choose. Regulatory vocabularies apply to the entire account.

Products, categories, dosage forms, capsule types, shelf lives, synonyms and capsule and packaging rules, for the chosen branches

Suppliers, for the chosen branches

Portaria 344/98 lists, dynamization methods and assay types, for the entire account

Access

Each person sees what is theirs.

Access areas

Screens are grouped into Pharmacy, Inventory and Administration. Users who have not been granted an area do not see its menu or open its screens.

Link to branches

Each user is linked to the branches where they work, with a default branch. The same user can serve more than one branch.

The same rules at every entry point

The saving rules apply equally to the screen, the import and the system’s automated routines.

Data

In the cloud, with history.

VUpharma runs on cloud servers and is used in the browser, with no server or database installed at the pharmacy.

01

Separation in the database

The data of each account and each branch is kept separate in the database itself, and a save without an account is rejected.

02

Previous version kept

Changes to factors, regulatory flags, shelf life, labels, lots and assays keep the previous version.

03

Updates with a procedure

Before each system update, we back up the database and check that backup. The update is only released with explicit approval. Service commitments are set out in the contract.

Tell us how many branches you have.