QUALITY ASSURANCE • TRUE CARE SYSTEM
QA Guide
Enterprise quality assurance standards for True Care System.
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
The QA Guide defines the approved quality assurance framework used to validate True Care System before changes reach production. It protects production stability, Provider isolation, PHI confidentiality, billing accuracy, EVV integrity, payroll calculations, auditability, and dependable daily operations.
The guide applies to Web, API, Mobile EVV, PostgreSQL/Prisma data access, background jobs, Sandata integration, exports, reports, support workflows, and future AI-enabled features.
Quality Objectives
- Prevent regressions in workflows that are already operating correctly.
- Verify strict Provider-level data isolation in every read, write, report, alert, export, and background process.
- Confirm role-based access and minimum-necessary access to Protected Health Information.
- Validate financial, payroll, billing, authorization, unit, overtime, and rate calculations.
- Verify EVV, GPS, visit, call-log, and Sandata submission data before release.
- Create repeatable evidence for release approval, incident review, and compliance audits.
QA Lifecycle
Definition of Done
- Acceptance criteria are satisfied and demonstrated.
- Type checking, builds, and required automated tests pass.
- Targeted module testing and related-module regression testing pass.
- Provider isolation, role permissions, and HIPAA logging are verified where applicable.
- Database changes follow the approved schema, manual SQL, and Prisma Generate process.
- Release notes, rollback steps, and operational impact are documented.