TRUE CARE SYSTEM • COMPANY PLAYBOOK
Security Workflow
Defines how security concerns are identified, contained, investigated, remediated, and reviewed.
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 how security concerns are identified, contained, investigated, remediated, and reviewed.
Core Requirements
Identify
Capture the suspected event, affected accounts, Provider scope, systems, timestamps, IP addresses, devices, and evidence.
Contain
Disable unsafe access, rotate credentials, stop compromised sessions, or isolate affected services as appropriate.
Investigate
Review authentication history, audit logs, PHI access, support sessions, application logs, and infrastructure events.
Remediate
Apply the smallest safe fix and verify it does not weaken Provider isolation, auditability, or production stability.
Review
Complete post-event analysis, corrective actions, documentation, and required notifications.
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. |