→ the link goes from this record; ← it comes from the other one. These are the edges the build gives the app. A name in the text is only a match on the words and is never treated as a link.

Comments

Comments are added in the local viewer; this copy is read-only.

Why it exists

expiring_soon Everything of Lorraine's that needs renewing in the next two or three months, all on dates relative to the build day: license (7 weeks), Buick registration (19 days), house policy (5 weeks), Buick policy (9 weeks), debit card (6 weeks), long-term-care premium (24 days), hearing aid warranty (6 weeks). Prescriptions have no date field, so the ones that need action are reminders: Eliquis and levothyroxine have no refills left, the Prolia shot is due, the disabled placard runs out. Walt's and Camille's documents are not close, except Camille's license on 2027-03-08, which is a plain date.

Questions that use it

q019 What's coming up for renewal for Mom in the next couple of months?

In the app

missing

From the app's own code (viewer/app_export.sh): Not made yet: run viewer/app_export.sh caregiver.

One step out

As the app receives it

The graph nodes the build makes for it: the record, and its phones, emails, addresses, pictures and files.

{
 "$type": "n_type_reminder",
 "id": "n_reminder_levothyroxine_refill",
 "createdAt": "1789939320000",
 "title": "Check that Abernathy's office renewed Mom's levothyroxine",
 "details": "0 refills on the bottle. Dwayne sent the request.",
 "date": "2026-10-10T00:00:00.000Z",
 "dismissed": false
}

Source

personas/caregiver/records/reminders.yaml:232

- id: reminder-levothyroxine-refill
  kind: reminder
  about: rx-lorraine-levothyroxine
  title: Check that Abernathy's office renewed Mom's levothyroxine
  details: 0 refills on the bottle. Dwayne sent the request.
  date: today+5d
  dismissed: false