TRUE CARE SYSTEM • RELEASE NOTES
Database Release Notes
Documents approved schema, SQL, indexing, data-repair, and generation changes while preserving the project’s manual database-change policy.
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
Documents approved schema, SQL, indexing, data-repair, and generation changes while preserving the project’s manual database-change policy.
Release Documentation Requirements
Schema Changes
List models, fields, relations, indexes, constraints, defaults, and enums changed in schema.prisma.
Manual SQL
Record the exact approved SQL sequence used to create or alter database structures.
Prisma Generate
Confirm Prisma Generate was completed after schema and SQL updates.
Data Repair
Document any targeted correction, backfill, duplicate cleanup, or Provider-scope repair.
Rollback
Record backup, reversal SQL, compatibility risk, and data-validation steps.
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. |