Phoenix Health Platform
Security architecture for protected healthcare operations.
Phoenix separates public education from authenticated operations with dedicated portal domains, scoped access, document handling controls, audit evidence, and release governance.Portal separation Governed workflow Audit evidence
Security model
Controls are aligned to how the platform actually operates.
The portfolio site explains the control model at a product level. Admin, Provider, Employer, and Member work each stay inside their own authenticated workspace with the access rules, audit trail, and operational scope expected for healthcare administration.
Host-only session boundaries so public website traffic does not share portal sessions
Role-based and scope-based authorization for protected workflows
MFA-ready identity model for admin, employer, and provider access
Audit evidence for protected operational actions
Public portfolio boundary with feature-only visuals and governed portal routing
Operational protection
Security follows the claim, coverage, document, and reporting lifecycle.
Phoenix presents intake, eligibility, clinical review, adjudication, enrollment, ID-card, reporting, and payment handoff as governed workflows with clear ownership, review points, and evidence capture.
Separate workspaces reduce access mistakes.
Public portfolio, Admin Portal, Provider Portal, Employer Portal, and Member Portal each use a dedicated hostname so users enter the correct security boundary before work begins.
Roles map to operational responsibilities.
Operations, provider office, employer benefits, and member-facing access are separated by audience and workflow, with protected routes validated by role and scope.
Auditable controls support release confidence.
Route-health checks, visual QA, asset provenance, deployment config checks, and cutover runbooks provide repeatable proof before production changes are accepted.
Privacy by design
Feature education stays separate from operational case work.
Public pages use approved product visuals, portal routing, security explanations, and process diagrams. Case handling, document review, financial processing, and member service activity remain inside secured portals.