VS Digital Health (VSDH) multi-location access
VS Digital Health, commonly known as VSDH, multi-location access depends on how your organization is structured as a white-label partner — each consumer brand, bricks-and-mortar location, or API integration may map to separate partner contexts in pharmacy.vsdigitalhealth.com, ConnectRxCare, or the Consult Gateway. VSDH markets modules for bricks-and-mortar booking, mobile medicine, and nationwide telehealth, but does not publish how organization hierarchy, location switching, or user scoping works across a clinic group. Multi-site operators should confirm whether one partner login spans locations or each site needs separate provisioning.
This page frames the multi-location questions to ask VSDH and how Fizy Health structures one login across organizations and clinic locations.
Proudly Partnered With
Confirm how sites, users, and orders separate on VSDH.
For a single-site white-label brand the access model barely matters. Across a group — multiple med spas, hybrid clinic plus telehealth brands, or franchise locations — it decides whether your team juggles separate partner portals or manages every site from one account.
What you need first
- A clear organization-to-location mapConfirm how VSDH represents a parent group and its sites in partner provisioning — especially if each location runs its own white-label consumer app.
- A defined user-access model per siteConfirm whether staff can be scoped to one location or many, and how an admin manages access across the group in pharmacy.vsdigitalhealth.com.
- Separation of patients and ordersConfirm that patient records, orders, and reporting stay separated per location so sites do not see each other's data.
How access works
- 01Ask how locations are structuredHave VSDH explain whether sites live under one partner agreement or separate white-label instances — and how that maps to portal access.
- 02Confirm the login modelDetermine whether your team uses one login that switches partner contexts or separate credentials per site or brand.
- 03Scope users per locationMap which staff and prescribers need which sites, and confirm an admin can grant and revoke access during onboarding.
Common access issues
Separate partner portals per brand
If each white-label consumer brand is a separate VSDH instance, staff covering multiple brands may need multiple logins. Confirm whether consolidation is available.
Blurred data between sites
Without clear separation, one location can see another's patients or orders. Confirm tenant-style isolation across the group.
Evaluating VSDH for multiple sites — or comparing multi-clinic access?
VSDH
Each location is its own white-label brand under VSDH.
- You are launching separate D2C brands per location with VSDH-managed apps and pharmacy — not one shared clinic ops dashboard.
- You will confirm directly how VSDH represents organizations and locations before standardizing across a group.
- Annual white-label subscription plus revenue share fits your business model better than clinic ops software.
Fizy Health
You want one login across every clinic and organization.
- You want a single account with org and clinic switchers for every location you manage.
- You want users scoped by role per clinic with clean separation of patients and orders.
- You want staff covering multiple sites to switch locations without signing in and out.
What true multi-clinic access unlocks.
Across a group, the access model is the workflow. These outcomes follow from one login built for multiple locations.
One login for every clinic you run
Switch between organizations and clinic locations from a single account instead of separate logins per site.
Role-scoped users per location
Invite prescribers and staff with permissions tied to the clinics they cover — not over-broad group access.
One cart still works per clinic
Each location builds its refill-day cart independently while you manage every site from one account.
Per-line tracking across the group
Fulfillment status stays visible per patient line regardless of which clinic location placed the order.
What clinics ask about VSDH multi-location access.
- Definition
How does VSDH multi-location access work?
VSDH does not publish a standard multi-location hierarchy. Each white-label brand or partner context may receive separate provisioning in pharmacy.vsdigitalhealth.com or ConnectRxCare. Confirm org structure with VSDH during onboarding.
- Login
Can one VSDH login cover multiple clinic locations?
That is not documented publicly. Ask VSDH whether partner credentials span locations or whether each site or brand needs separate portal access.
- White-label
Does each location get its own VSDH consumer app?
VSDH supports bricks-and-mortar and mobile medicine modules per brand. Multi-location groups may run separate white-label apps — confirm whether one partner account manages them all.
- Data
Are patient records separated per location on VSDH?
VSDH does not publish tenant isolation details. Confirm that patients, orders, and reporting stay scoped per location before rolling out across a group.
- API
How do API partners handle multiple locations?
The Consult Gateway API scopes requests by partner context. Confirm with VSDH how multiple physical or virtual locations map to partner IDs in your integration.
- Alternative
How does Fizy Health handle multi-location access?
Fizy Health gives one login with organization and clinic switchers, role-scoped users per site, and separate patient-linked carts per clinic — built for multi-location cash-pay operators.
Sources reviewed June 2026
- VS Digital Health public website (vsdigitalhealth.com) and Consult Gateway documentation, reviewed June 2026.
- Fizy Health platform capabilities reflect the live product.
One login across every clinic you run.
Switch organizations and locations from a single Fizy Health account with role-scoped team access. Free to start.