QUALITY ASSURANCE • TRUE CARE SYSTEM
Integration Testing
Validate data and workflow continuity across connected True Care System modules.
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
Integration testing validates that data remains accurate as it moves through connected True Care System modules and approved external systems.
Primary Operational Chain
Service→Authorization→Schedule→Mobile EVV→Visit Maintenance→Billing→Sandata
Integration Test Matrix
| Integration | Key validations |
|---|---|
| Web ↔ API | Token handling, Provider context, validation, error messages, refresh behavior. |
| API ↔ Database | Transactions, constraints, relationships, timestamps, and no cross-tenant leakage. |
| Schedule ↔ Mobile | Assigned and backup shifts, timezone, status, alerts, and claim behavior. |
| Mobile ↔ Visit | Check-in/out, GPS, call source, Individual, DSP, service, and duplicate prevention. |
| Visit ↔ Payroll | Approved time, DSP time, role separation, overtime, rate source, duplicate-hour prevention. |
| Visit ↔ Billing | Readiness, scheduled/actual decision, units, corrections, authorization, payer/program. |
| Billing ↔ Sandata | Environment, provider ID, payloads, sequence IDs, UUID, response status, resubmission. |
| Application ↔ HIPAA | Actor, Provider, Individual, action, purpose, decision, minimum necessary, IP and device. |