The control plane of the Clinical Intelligence Network.
Hub is where a clinical organization becomes a PatientTrac network: enrollment, sites, departments, teams, governed role-based access, and the provisioning of every application each location needs — administered in one place.
For owners, administrators, and implementation and security teams.
Network administration with clinical seriousness
Organization
Hub establishes the organization itself as a governed entity: who you are, where you operate, and how your clinical structure maps into the network. The identifiers created here are the same identifiers every application reads, so a site or provider defined once is defined everywhere.
- Organization enrollment and identity
- Sites, locations, and facility records
- Departments and clinical service lines
- Provider and staff rosters
- Shared identifiers used by every application
Access
Access in PatientTrac is granted, scoped, and revoked deliberately. Hub assigns roles per person, per application, and per site, with authentication controls appropriate to clinical software — so offboarding is administered centrally and takes effect across the network, not app by app.
- Role-based permission assignment
- Per-application and per-site access scoping
- TOTP-aware authentication controls
- Structured onboarding of new team members
- Centrally administered offboarding across the network
Provisioning
Hub activates the network application by application. Forge, Profiler, Mind, Revela, Continuum, ASC, and Companion are switched on per site as the organization needs them, with plan and license visibility in the same view — so growing into a new location or specialty is an administrative act, not a new implementation project.
- Activation of the seven clinical and operational applications
- Per-site application assignment
- Plan and license visibility
- Expansion to new sites and service lines
- Consistent configuration carried across locations
Governance
Multi-site organizations need one source of administrative truth. Hub centralizes configuration and ownership so that navigation, roles, and organizational boundaries behave identically at every location — and administration scales with the organization instead of fragmenting across it.
- Centralized configuration management
- Clear administrative ownership and accountability
- Consistent navigation across every application
- Cross-site administration from one console
- Organization isolation as a structural boundary
From enrollment to a working network
Enroll the organization
Establish the organization, its sites, departments, and service lines as the governed foundation of the network.
Build the team
Add providers and staff to the roster and assign each person the roles their work actually requires.
Activate applications
Switch on the applications each site needs — from Forge operations to Companion recovery — with plan visibility in the same view.
Administer continuously
Onboard, offboard, expand to new sites, and adjust access as the organization changes, from one console.
Who works in Hub
Owners & administrators
See the whole organization — sites, people, applications, and plans — and make network-level decisions from one accountable console.
Implementation teams
Stand up new sites and service lines by configuration rather than by project: enroll, roster, provision, verify.
Security & compliance leads
Review who has access to what, scope permissions per application and site, and remove access centrally across the network.
Administration that surfaces what needs attention
Hub's job is clarity: which sites have which applications, which people hold which roles, and which onboarding or provisioning steps remain open. Assistive intelligence in Hub organizes and prioritizes administrative work — it summarizes configuration state and highlights incomplete setup — while every grant of access and every activation remains a deliberate human action.
Hub supports access management and provisioning. It does not replace organizational approval processes, security policy, or local workforce administration — authorized people make and own every access decision.
The foundation the other seven stand on
Every PatientTrac application trusts what Hub establishes: the organization boundary, the sites, the rosters, and the roles. Forge schedules against Hub's facilities and providers; the clinical applications enforce Hub's access decisions; Companion connects patients to organizations Hub has defined. One administrative truth, read everywhere.
See Hub set up a working network
In a guided demonstration we will enroll an organization, build a team, and activate applications — then show the same identities working across the network.
Request a Demo