TRUE CARE SYSTEM • RELEASE NOTES
Upgrade Guide
Defines the actions required before, during, and after a True Care System release.
Release notes may reference Provider operations, PHI-related workflows, security controls, billing, payroll, EVV, integrations, or proprietary implementation details. Public documentation must avoid credentials, private endpoints, source code, customer data, and sensitive internal security information.
Purpose
Defines the actions required before, during, and after a True Care System release.
Release Documentation Requirements
Before Upgrade
Review release scope, backups, dependencies, database steps, mobile-store status, Provider communication, and rollback plan.
During Upgrade
Deploy in the approved sequence and prevent duplicate jobs, submissions, or conflicting writes.
After Upgrade
Run smoke tests, Provider-isolation checks, audit validation, integration checks, and business-workflow verification.
Provider Actions
Identify browser refresh, app update, settings review, training, or data-readiness tasks.
Rollback
Define conditions that require stopping deployment and restoring the prior stable state.
Required Release Record
| Field | Required Information |
|---|---|
| Version | Product version, build, release identifier, or deployment reference. |
| Date | Release, deployment, publication, or approval date. |
| Environment | Development, QA, staging, production, TestFlight, Google Play, or Apple App Store. |
| Scope | Affected product, module, Provider workflow, integration, or documentation area. |
| Validation | QA result, regression evidence, smoke tests, security review, and production confirmation. |
| Provider Action | App update, browser refresh, training, configuration review, data correction, or no action. |
| Rollback | Rollback trigger, prior stable version, reversal steps, and data-reconciliation requirements. |