True Care System True Care SystemDocumentation
Return to Website

TRUE CARE SYSTEM • TROUBLESHOOTING

Scheduling Issues

Resolve missing shifts, conflicts, assignments, backup shifts, recurrence, and notification issues.

Privacy, HIPAA, and production safety notice

Troubleshooting may expose workforce information, Provider configuration, PHI, audit data, billing records, payroll information, or technical identifiers. Use minimum-necessary access, redact public evidence, and perform changes only through approved roles and workflows.

Purpose

Resolve missing shifts, conflicts, assignments, backup shifts, recurrence, and notification issues.

Diagnostic Checklist

Date and timezone

Confirm shift dates, local timezone, overnight boundaries, and recurrence.

DSP assignment

Verify planned and actual DSP, active status, availability, and conflicts.

Backup shift

Confirm the backup flag, unassigned status, alert distribution, and claim status.

Service and authorization

Verify active service, authorization dates, units, and Individual.

Conflict validation

Review overlapping shifts, travel time, house coverage, and staffing requirements.

Notifications

Confirm changed, cancelled, reassigned, and backup notifications were sent.

Recommended Resolution Sequence

  1. Reproduce the issue using the same Provider, user role, record, date range, and device context.
  2. Confirm filters, status, account access, Provider scope, effective dates, and related records.
  3. Capture evidence before changing configuration, data, or code.
  4. Apply the smallest authorized correction and avoid unrelated changes.
  5. Retest the original workflow and one related regression workflow.
  6. Document the cause, correction, validation, and any required follow-up.

When to Escalate

Escalate immediately

Contact authorized Provider leadership or Platform Support when the issue involves possible cross-provider data, unauthorized PHI access, suspicious login activity, data loss, billing submission risk, payroll impact, medication safety, or a critical production outage.