BILLING • CONFIGURATION
Provider Setup
Configure Provider-specific Sandata environments, identifiers, endpoints, credentials, payer/program, and activation.
Billing and EVV pages may contain PHI, Medicaid identifiers, employee identifiers, service information, visit dates, GPS evidence, claim-supporting data, and submission credentials. Screenshots in this public guide use redacted or demonstration information. Production access must be role-based, Provider-scoped, logged, and limited to the minimum information necessary.
True Care System has implemented the Sandata Alternate EVV workflow for Client, Employee, Visit, Call, correction, batching, transaction tracking, rejection review, and resubmission. The platform has completed the applicable Sandata testing and production-onboarding work for its certified payer program. Sandata certification is program-specific; availability in another state or payer program requires that program's registration, testing, approval, credentials, and current technical specifications.
True Care System sends required EVV data to the Sandata Aggregator. After accepted EVV submission, the Provider completes the Medicaid billing or claim workflow through the applicable state claims system, such as Pennsylvania PROMISe, unless the payer program specifies a different process.
Purpose
Provider Setup stores the Provider-specific Sandata configuration used for EVV validation and submission. The backend must derive the configuration from the authenticated Provider and must never rely on a hard-coded agency.
Provider Configuration Fields
| Field | Function |
|---|---|
| Environment | Selects UAT or Production configuration. |
| Primary Identifier Type | Selects the identifier qualifier required by the payer program, such as Medicaid ID or another approved qualifier. |
| Provider MPI / Provider NPI | Stores the program-required Provider identifiers. |
| Agency Code | Stores the Sandata agency code associated with the Provider. |
| Vendor Prefix | Supports unique SaaS identifiers for Client, Employee, and Visit records. |
| Payer ID / Payer Program | Stores the payer and program values required in outgoing records. |
| Timezone | Controls the visit timezone used for submission and date-time interpretation. |
API Endpoints
| Field | Function |
|---|---|
| API Base URL | Base endpoint for the selected Sandata environment. |
| Client Endpoint | Destination for Client records. |
| Employee Endpoint | Destination for Employee records. |
| Visit Endpoint | Destination for Visit and Call records. |
Production Account and Credentials
Production Account identifies the Provider's Sandata account. Username stores the approved integration user. Password must be encrypted before storage, masked in the interface, and never returned by the API. Leaving a password blank during update should retain the existing encrypted value rather than erase or expose it.
Activation and Update
The Active checkbox determines whether the configuration can be used for EVV validation and submission. Update Config saves authorized changes. Refresh reloads the current Provider configuration. Every change should be audit logged with actor, Provider, environment, changed fields, time, IP, and device context without logging the password value.