---
title: Reminders
slug: redshift/reminders
icon: {"lucideIcon":"Bell"}
docTags: 
createdAt: 2026-10-01T12:35:24.364Z
---

:::hint{type="warning"}
`reminder_protocol_usage` and `reminder_protocol_usage_items` don't currently appear on the [All views](docId\:RWeIE3wRWbbe5hA1cUmH3) granted-access list. The columns below are documented for completeness (they exist in the underlying schema), but confirm you actually have a client-scoped view for them before building a report against these names.
:::

### `reminder_protocol_usage` — reminder protocol applied to a patient record

- `reminder_protocol_template_id` — the protocol/template being applied
- `clinic_id`, `pet_id`, `vet_id`, `file_case_id` → `new_file_cases.id`
- `due_date`, `administration_date` (plus `_utc` variants — see [Dates & Timezones](docId\:RX3HRkivNEpJwznBBy6dt))
- `is_active`, `overwritten_by` — set when a later reminder supersedes this one

### `reminder_protocol_usage_items` — product/service line attached to the reminder

- `reminder_protocol_usage_id` → `reminder_protocol_usage.id`
- `reminder_protocol_usage_itemable_type` / `_itemable_id` — polymorphic reference, meaning the linked item could be a product, a service package, or another entity depending on `_itemable_type`. Check the type value before assuming what the id points to.

### How this connects to Stock & Services

`product_reminders` (documented in [Stock & Services](docId\:up9_3heKVh32jzLj4BwZH)) is the *template-level* link between a product and a reminder cadence. `reminder_protocol_usage` is the *instance* — the reminder as actually applied to a specific patient record.