True Care System is designed with security, provider isolation, role-based access, audit logging, cloud deployment and platform readiness as core principles.
JWT and token-based access control.
Role-based permissions for operational security.
Strict separation between provider organizations.
Traceable activity, approvals and changes.
This section explains the operational value behind the diagram and how the workflow supports real provider use cases, EVV readiness, billing accuracy, and long-term SaaS scalability.
Security controls are built into the platform architecture rather than added as an afterthought.
The multi-provider SaaS model separates data by authenticated provider context and limits user visibility by role.
Operational changes, visit updates, billing activity and approval history can be tracked to support compliance and review.
The system is built for growth across provider organizations, mobile teams, billing workflows and integration needs.
The diagram below can be shared with provider leadership, compliance teams, billing teams, IT reviewers, and EVV integration stakeholders.
Provider isolation, role-based access, authenticated API calls and audit-oriented workflows help protect provider-specific information.
Yes. The SaaS architecture is designed to support additional providers, modules, mobile users, reporting, billing workflows and integrations.
Download the five-page Pennsylvania Alternate EVV Technical Solution Overview PDF.