This system is engineered so that privacy, data isolation, and accessibility are in place before a single member or employee signs in. Here is exactly how your members' and workforce's data is protected — and why this can become Banner's first true healthcare white label.
Force for Health builds to the standard a Banner audit expects. The controls below are designed into the platform itself, scoped to Banner – University Family Care as a fully isolated organization. Status reflects this private-preview stage; items marked BAA-ready activate when a Business Associate Agreement is executed.
The platform is built to the HIPAA Security and Privacy Rules. During this preview, no Protected Health Information (PHI) is collected — the demo uses synthetic and de-identified content only. Before any real member PHI flows, a Business Associate Agreement is executed between Banner Health and The Force for Health, defining permitted uses, safeguards, breach notification, and return/destruction of data.
Every record in the system carries an organization_id keyed to Banner – University Family Care. Row-Level Security policies enforce that no other client, tenant, or organization can ever read or write your data — the isolation is at the database layer, not just the interface. This is the same wall that keeps each organization's members, learners, and outcomes completely separate.
The Population Health Insights Tool surfaces outcomes — screenings up, blood-pressure checks up, well-child visits up — as de-identified, aggregate signals. No individual PII or PHI leaves your organization. Banner sees its own cohort detail; the network only ever sees anonymized rollups. This is what lets Sarah's team carry numbers to AHCCCS while every member's privacy is preserved.
The workforce and career-pathway tracks touch education records and, in K-12 career programs (Camp Scrubs and similar), minors. FERPA controls protect education records; an age gate and COPPA parental-consent path govern any learner under 13. The platform is built to the strictest applicable state standard, which clears the bar everywhere Banner operates.
Every page is keyboard-navigable, uses color contrast that meets or exceeds AA, never relies on color alone to convey meaning, includes alt text, and captions instructional video. Accessible to every member and employee — and required for a system serving Medicaid and long-term-care populations.
This staging space is gated to your named team with individual access codes. Nothing is indexed, public, or shareable outside your invitation. When Banner approves go-live, access moves to authenticated member and staff sign-in tied to the isolated organization above.
Every activation is mapped to a documented Health-Related Social Needs priority — older adults, justice-involved individuals, transition-age youth, maternity care, and Native American members. The reporting layer is built so each Community Reinvestment dollar traces to a named HRSN outcome, the way AHCCCS auditors expect.
Synthetic / de-identified content only. No PHI. Invite-only access for your team to test-drive.
Business Associate Agreement + Data Sharing Agreement executed between Banner and FFH before any real data flows.
Banner – University Family Care created as an isolated organization with Row-Level Security and Banner-scoped roles.
Members and staff sign in to the Banner-branded system. PHIT rolls up de-identified outcomes only.
Audit logging, accessibility monitoring, and reporting that ties every activation to a documented HRSN priority.
Plain-language summary: during this preview there is no real member data in the system at all. When it goes live, Banner's data lives in a walled-off space only Banner can see, the network only ever receives anonymized totals, and a signed BAA governs the whole arrangement.
We'll walk your security and compliance leads through the BAA, the isolation model, and the de-identification approach in as much detail as they want.
Talk to Coach Lucy →