QUALITY ASSURANCE • TRUE CARE SYSTEM
Release Checklist
Complete the approved controls required before a True Care System release.
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
The Release Checklist is the final quality gate before deployment. It ensures technical, operational, privacy, security, data, documentation, and rollback requirements are addressed.
Pre-Release Checklist
| Control | Required confirmation |
|---|---|
| Scope | Approved requirements, files, modules, and known limitations are documented. |
| Build | Type checking, compilation, linting, and required automated tests pass. |
| Database | Schema reviewed; manual SQL tested; Prisma Generate completed; backup and rollback ready. |
| Functional QA | Acceptance, smoke, targeted, integration, and regression tests pass. |
| Security | Authentication, authorization, Provider isolation, session, input, and export controls pass. |
| HIPAA | PHI access, minimum necessary, audit evidence, and support-session logging pass. |
| Mobile | Approved build/version, permissions, GPS, alerts, and affected workflows pass. |
| Billing/EVV | Rates, units, readiness, sequence, payload, environment, and submission behavior pass. |
| Payroll | Hours, role separation, overtime, extras, rate source, totals, and history pass. |
| Documentation | User guide, release notes, screenshots, support instructions, and known issues are updated. |
| Rollback | Previous release, database recovery, and decision owner are documented. |