Secondary Parent Accounts (Multi-Parent Enterprise Structure)
Provision a second, fully independent Parent Account when a single Parent → Sub-Organization hierarchy isn't enough, since Healthie only supports one level of Sub-Organizations. Typically used when a downstream partner or enterprise client needs its own Sub-Orgs, full operational independence, or complete data isolation from the primary Parent Account. Nothing shares automatically between separate Parent Accounts; any cross-account data flow must be built and maintained by the customer via the API.
Built by Core Engineering
The problem it solves
An organization supporting large enterprise clients or partners that each need their own internal Sub-Org structure, independent branding, or complete data isolation can't fit that need inside a single Parent Account, since Sub-Orgs are capped at one level and don't offer full independence. This solves that by giving each downstream entity its own standalone Parent Account, with clear ownership and boundaries, instead of forcing an unsupported nested hierarchy.
What's included
- Fully standalone, independently configured Parent Account per downstream entity
- Complete isolation of clients, charts, appointments, billing, providers, and reports between Parent Accounts
- Separate API credentials and integration configuration required per Parent Account
- Independent Bridge by Healthie setup per Parent Account, if used, with data unification handled outside Healthie
- Manual recreation of shared elements like charting templates, forms, and program structures across accounts
How it works
When a downstream organization or enterprise client needs its own Sub-Organizations, full operational independence, or complete data separation, Healthie provisions a second Parent Account for that entity rather than attempting to nest it as a Sub-Org. Each Parent Account is configured, onboarded, and maintained independently, with no automatic sharing of clients, charts, appointments, billing, providers, permissions, or reports between them. Any content that needs to exist in both, like a charting template or form, is manually recreated in each account, while any live data sync, such as client or appointment records, must be built and maintained by the customer using Healthie's API with separate credentials per account; if Bridge by Healthie is used, each Parent Account requires its own Bridge setup, and any data unification across accounts happens outside of Healthie.
Secondary Parent Accounts let Enterprise organizations stand up a second, fully independent top-level account when their structure outgrows a single Parent → Sub-Organization hierarchy, since Sub-Organizations don't support nesting additional Sub-Orgs beneath them. It's built for situations where a downstream organization, partner, or large enterprise client needs its own Sub-Orgs, independent branding and workflows, or complete separation of client, charting, reporting, and operational data from the primary Parent Account. Each Parent Account functions as a fully standalone instance: clients, charts, appointments, billing, providers, permissions, and reports are intentionally and completely isolated from any other Parent Account, with nothing shared or mirrored automatically. Cross-account coordination, such as syncing client or appointment data between two Parent Accounts, must be built and maintained by the customer through Healthie's API; Healthie does not duplicate or unify data across separate Parent Accounts.