QUALITY ASSURANCE • TRUE CARE SYSTEM
Test Data
Create safe, repeatable, Provider-scoped datasets for reliable quality validation.
Protected-data and QA evidence notice
QA artifacts may contain workforce identity, Provider configuration, PHI, GPS, visit, payroll, billing, audit, or integration evidence. Public documentation and shared test evidence must use synthetic, demonstration, or properly redacted information. Never place production passwords, tokens, full SSNs, bank account numbers, or unnecessary PHI in screenshots, tickets, automated test output, or repositories.
Purpose
Test Data provides controlled, repeatable datasets that support reliable validation without exposing unnecessary real PHI or production secrets.
Approved Dataset Types
| Dataset | Use |
|---|---|
| Synthetic Provider | Tenant isolation, branding, configuration, branches, locations, roles, reports. |
| Synthetic Individual | Demographics, contacts, authorizations, schedules, medication, BSS, reports. |
| Synthetic Employee | Roles, employment, payroll rates, Mobile access, DSP readiness, audit events. |
| EVV Golden Set | Known Client, Employee, and Visit records used to validate payload and sequence behavior. |
| Billing Dataset | Scheduled/actual times, units, corrections, rates, payer/program, batch states. |
| Security Dataset | Multiple Providers and roles for positive and negative authorization tests. |
| Boundary Dataset | Dates, timezones, overnight shifts, rounding, missing and invalid fields. |
Protection Rules
- Prefer synthetic or de-identified data.
- Never store production passwords, tokens, bank account numbers, full SSNs, or unredacted PHI.
- Separate Providers clearly so isolation tests can detect leakage.
- Use stable identifiers for repeatable regression tests.
- Reset datasets after destructive or sequence-sensitive testing.