Architecture View:
ENTERPRISE MULTI-TENANT ARCHITECTUREGroup ➔ Clinic Branches HierarchyHIPAA BAA & FHIR R4 Interoperability

Enterprise Group & Multi-Branch Architecture Hub

Interactive architecture explorer visualizing the multi-tenant Group & Clinic Branches hierarchy, database-level tenant isolation, and the technical connectivity roadmap for eClinicalWorks onboarding.

Tier 1 • Corporate Group NetworkGroup Root
Parent Healthcare Group

Governs the parent health system or medical group (`ClinicGroup`), Master HIPAA BAA vault, MAC jurisdiction, and group-wide compliance oversight.

Unified Group Governance & BAA Perimeter
GROUP ➔ BRANCHES
Tier 2 • Clinic BranchesBranch Scope
Multi-Branch Practice Hierarchy

Scales across specialty clinic branches and regional practice locations with isolated patient workspaces, NPI routing, and roving provider memberships.

Strict Per-Branch Clinical Isolation
Tier 3 • ViacoraMed.ai EngineActive Standard
Healthcare Interoperability Standard

Combines Dual-Key Semantic Identifiers, universal EF Core query filters (65+ entities), impassable DbContext write gates, and SMART on FHIR R4 pipelines.

100% Tenant-Isolated Clinical AI
Filter Scope:
1. Multi-Tenant Group & Branch HierarchyTenancy
Architectural Rationale: A clean Group ➔ Clinic Branches hierarchy enables multi-clinic healthcare organizations to scale across specialty locations with strict branch isolation.
Group Network Tier (ClinicGroup)group root
Corporate Group Network (ClinicGroup)

Governs the parent health system or medical group, Master HIPAA BAA perimeter, MAC jurisdiction, and enterprise-wide oversight.

Clinic Branch Tier (Group ➔ Branches)branch scope
Multi-Branch Practice Structure: Group ➔ Clinic Branches

Scales cleanly across multiple specialty clinic branches and regional practice locations with isolated clinical workspaces.

ViacoraMed.ai Implementationstandard
3-Tier Enterprise: Group (BAA) ➔ Branch Clinic ➔ Encounter

Maintains legal HIPAA BAA governance at the Group level while isolating operational chart processing and billing per Clinic Branch.

Enterprise Architecture Standard: A clean Group ➔ Clinic Branches hierarchy enables multi-clinic healthcare organizations to scale across specialty locations with strict branch isolation.
2. Database Query Filters (HasQueryFilter)Database
Architectural Rationale: Universal database-level query filters eliminate cross-branch clinical data leakage even if a query omits a manual clinic filter.
3. Identifier Architecture & Dual-Key PatternTenancy
Architectural Rationale: The Dual-Key pattern preserves relational database performance while enabling clear, human-readable routing across EHR integrations and clinic branches.
4. Ambient Tenant Dynamic ID ResolutionTenancy
Architectural Rationale: Dynamic ID resolution enables seamless routing across clinic branches during health system expansions and EHR onboarding.
5. DbContext Write Gate (SaveChangesAsync)Database
Architectural Rationale: Enforcing security at both the read gate (query filters) and write gate (SaveChanges) guarantees complete protection against cross-tenant data mutation.
6. Global Reference Catalog ExemptionDatabase
Architectural Rationale: Cleanly separates shared universal clinical reference knowledge from strictly isolated branch-level patient health information (PHI).
7. Anti-IDOR Security & Audit LoggingSecurity
Architectural Rationale: Immutable security audit logging ensures full compliance with HIPAA Security Rule 45 CFR § 164.312 (Audit Controls).
8. Role-Based Access Control (RBAC) & Roving ProvidersSecurity
Architectural Rationale: Enables attending physicians and coding auditors to switch seamlessly between authorized clinic branches while blocking unauthorized clinics.
9. EHR Pipeline & Interoperability PortInteroperability
Architectural Rationale: ViacoraMed's hybrid ingestion topology (SMART on FHIR R4 + Webhooks + SFTP) provides enterprise healthcare interoperability for multi-branch practices.
10. Multi-Tier Acceptance & Isolation VerificationSecurity
Architectural Rationale: Rigorous multi-tier testing guarantees that group and clinic branch isolation boundaries remain mathematically impassable.