Creating a Secondary Parent Account with Sub-Organizations

As organizations grow, their structure often becomes more complex than a single hierarchy can support. While Healthie provides a powerful Parent → Sub-Organization model, some Enterprise customers eventually reach a point where they need multiple top-level (Parent) accounts, each with their own Sub-Organizations.

Overview of Parent Accounts & Sub-Organizations

Parent Account (Main Organization)

A Parent Account is the top-level organization in Healthie. It owns:

• Global administrative control
• Core configuration and content
• Reporting and oversight

Sub-Organizations (Sub-Orgs)

Sub-Organizations are an additional administrative layer available on Enterprise plans (with semi or full web white-label). Sub-Orgs allow you to:

• Group providers, clinics, regions, or partners
• Share centralized content and workflows
• Delegate day-to-day control to sub-teams

/callout Healthie supports one level of Sub-Organizations only. Sub-Orgs cannot contain additional Sub-Orgs.

Learn more about Administrative Layers for your Organization

Why a Secondary Parent Account May Be Recommended

A secondary Parent Account is typically recommended when an organization needs more than two functional layers.

Common scenarios include:

1. Downstream Organizations Need Their Own Hierarchy

Your organization may support large enterprise clients or partners who:

• Need their own Sub‑Organizations
• Require internal data sharing across locations or teams
• Cannot operate effectively as a single Sub‑Org

Because nested Sub‑Orgs are not supported, these downstream entities should be provisioned as their own Parent Account.

2. Operational Independence Is Required

A second Parent Account is appropriate when a downstream organization needs:

• Independent branding and configuration
• Distinct appointment logic or workflows
• Separate provider and client management
• Clear administrative ownership

Trying to support this level of independence under one Parent Account often introduces operational constraints.

3. Data Separation is Intentional

While Sub-Organizations provide structured separation within a single Parent Account, some organizations require complete isolation across business entities. This may include separation of client and charting data, reporting and analytics, and operational workflows. In these cases, creating a second Parent Account establishes clear, intentional boundaries between environments.

• Client and charting data
• Reporting and analytics
• Operational workflows

In these cases, a second Parent Account provides clean, intentional boundaries.

Secondary Parent Account Structure 

Rather than attempting to model this:

Healthie recommends:

Each Parent Account functions as a standalone instance, while still allowing your organization to support multiple enterprise‑level customers or business lines.

Data & Configuration Expectations

What Does Not Happen Automatically

Between Parent Accounts, there is no automatic sharing of:

• Clients or charts
• Appointments or billing data
• Providers or permissions
• Reports or analytics

Each Parent Account is intentionally and fully isolated.

What Can Be Recreated or Shared

Some elements may be recreated or coordinated :

Manual / UI‑Based:

• Charting templates
• Forms and questionnaires
• Program structures

API‑Based (Customer‑Owned):

• Client records
• Appointment data
• Ongoing data synchronization

/callout Healthie does not duplicate or mirror full accounts. Any cross‑account data flow must be owned and maintained by the customer using the API.

API & Integration Considerations

When using multiple Parent Accounts:

• Each Parent Account have its own API credentials (if API is desired for both)
• Integrations must be configured separately per account
• Cross‑account workflows require custom API logic

If using Bridge by Healthie:

• Each Parent Account requires its own Bridge setup
• Both accounts may connect to the same external data destination, if desired
• Data unification occurs outside of Healthie

Best Practices for Secondary Parent Accounts

1. Treat Each Parent Account as Independent

Plan onboarding, configuration, and success metrics separately for each Parent Account.

/callout Secondary Parent Accounts are most effective when organizations are prepared to accept the operational tradeoffs that come with increased independence, including separate configuration, setup effort, and ongoing maintenance.

2. Clarify Data Ownership Early

Before provisioning a second Parent Account, confirm:

• Whether data must flow between accounts
• Who owns the API logic and maintenance
• How errors or mismatches will be handled

3. Use Sub‑Organizations Intentionally

Within each Parent Account:

• Use Sub‑Orgs for operational peers (locations, regions, clinics)
• Avoid using Sub‑Orgs to simulate deeper hierarchy

4. Plan for Ongoing Scale

A secondary Parent Account works best when:

• The downstream organization is large or strategic
• The model is repeatable across customers
• Clear boundaries improve performance and governance

Please reach out to us at hello@gethealthie.com if you have any additional questions about Sub-Orgs.