RECORD ORIGIN EVIDENCE
Create Events
Trace creation of clinical, operational, staffing, billing, and administrative records.
Audit records may contain workforce identities, Provider identifiers, Individual references, IP addresses, device details, routes, request metadata, support-session identifiers, and before-and-after values. Screenshots in this public guide use redacted or demonstration information. Production access must remain Provider-scoped, role-based, purpose-limited, and restricted to authorized personnel.
True Care System records audit evidence to support accountability, privacy review, security investigation, operational integrity, and Provider governance. These capabilities support—but do not replace—the Provider's policies, workforce training, risk analysis, legal obligations, incident response, and retention program.
Purpose
Create events establish the origin of a new record and identify the Provider, user, entity type, entity ID, date/time, route, status, and related metadata.
Examples of Audited Creation
| Field | Function |
|---|---|
| Individual | New Individual profile or protected demographic record. |
| Employee or user | New workforce, user, or administrative account. |
| Schedule | New shift, recurring schedule, or backup plan shift. |
| Medication | New medication order or administration-related record. |
| Authorization | New payer authorization, service allocation, or effective-date record. |
| Visit | New EVV or Visit Maintenance record. |
| Billing | New batch, submission, rate, or readiness-related record. |
| Support ticket | New Provider support request with ticket number and access decision. |
Review Focus
- Was the creator authorized for the module and Provider?
- Was the record created in the correct tenant and for the correct person?
- Did validation succeed?
- Were sensitive identifiers handled appropriately?
- Was the event related to a support or impersonation session?
