TRUE CARE SYSTEM • COMPANY PLAYBOOK
Release Process
Defines the controlled process for preparing, approving, deploying, and monitoring True Care System releases.
Company Playbook guidance supports controlled healthcare-software operations. It does not replace applicable law, Provider policy, contractual requirements, professional judgment, or formal legal and compliance review.
Purpose
Defines the controlled process for preparing, approving, deploying, and monitoring True Care System releases.
Core Requirements
Release Readiness
Confirm requirements, code review, QA results, deployment plan, rollback plan, database steps, and documentation updates.
Database Changes
Update schema.prisma, execute approved manual SQL, then run Prisma Generate. Do not use Prisma migrations for this project.
Controlled Deployment
Deploy only approved code and configuration to the intended environment.
Post-Deployment Validation
Verify authentication, Provider isolation, core workflows, API health, audit logs, background jobs, and integrations.
Release Communication
Document release scope, impact, known limitations, and any required Provider action.
Required Documentation
| Record | Expectation |
|---|---|
| Owner | Identify the accountable role or team. |
| Scope | Document affected systems, Providers, users, workflows, and data. |
| Evidence | Retain timestamps, identifiers, approvals, screenshots, logs, or test results as applicable. |
| Decision | Record the approved action, reason, risk, and validation result. |
| Follow-up | Track corrective actions, training, documentation, and future prevention. |