# LyCare

> LyCare is a web app for running care organizations: senior living communities, foster group homes and in-home care agencies. Staff record and coordinate care (medications, meals, medical visits, incidents, logbooks), managers keep staff compliant and see how every facility is doing, and outside partners (lawyers, guardians ad litem) get limited, logged access to the records they're entitled to. This page explains how it works, in plain text, for people and AI assistants.

Site: https://lycare.vercel.app
Animated walkthroughs: https://lycare.vercel.app/how-to
Status: demo and development. It runs on demo data only; no real people's records.

---

## 1. Core concepts

- **Company**: one care organization (a tenant). Everything belongs to a company; companies never see each other's data.
- **Facility**: a site inside a company (a community, a group home, or a home-care branch). Each facility is in a US state, and the state decides which rules apply (incident reporting, compliance requirements).
- **Resident**: a person in care. Companies can rename this ("Clients" in home care, "Youth" in group homes). Every resident has an ID number (e.g. R-1042) shown everywhere.
- **Staff / users**: people who sign in. Each belongs to a company and is assigned to one or more facilities.
- **Groups and permissions**: each user is in groups (Company Admin, Nurse, Caregiver, Clinician…). A group grants actions (read, create, edit, delete) on modules (Residents, Medications, Incidents…). The sidebar only shows modules the user can read.
- **Facility scope**: company admins and owners see every facility. Everyone else sees only residents, records and reports from the facilities they're assigned to. This applies to lists, records, dashboards, files, reports, search, AI answers and notifications.
- **Terms**: module names can be renamed per company (e.g. "Appointments" → "Care visits").
- **System users**: platform staff (super admin, support) who pick a company to work inside. Switching into a company is recorded in that company's log.

## 2. Actors

| Actor | Typical login | What they do | Lands on |
|---|---|---|---|
| Super admin (platform) | system user | Creates companies and billing plans, writes platform templates (compliance, logbook, incident rules), can "log in as" a user | Select company |
| Company admin / owner | e.g. sunrise.admin | Sets up facilities, staff, groups, templates and rules; sees everything | Dashboard |
| Facility manager / supervisor | sunrise.manager | Runs a facility: approvals, reviews, schedules | Dashboard |
| Doctor / clinician | sunrise.doctor | Runs medical visits, writes clinical notes, can read medications | My day |
| Nurse | sunrise.nurse | Med passes, PRN follow-ups, wound checks, low-intake follow-up | My day |
| Caregiver | sunrise.caregiver | Meals, logbook entries, incident reports, own compliance | My day |
| Counselor / social worker | harbor.counselor | Youth in group homes: case plans and goals, court, caseworker contacts, restraints, allowances, family links, logbooks, incidents, partner requests | My day |
| Home caregiver | brightpath.caregiver | Home visits with check-in/out (EVV) and care-plan tasks | My day |
| Clinical supervisor (home care) | brightpath.nurse | Authorizations, EVV exceptions, home-visit oversight | Dashboard |
| Lawyer / guardian ad litem (partner) | harbor.gal | Sees only shared clients and sections in the partner portal; sends requests | Partner portal |

Demo companies: Sunrise Senior Living (assisted living, Texas), Harborview Care Group (foster group homes, Washington and Oregon), BrightPath Home Care (in-home care, Florida).

## 3. Every day: My day and the Dashboard

**My day** (`/my-day`) is each person's start page. It shows:
- Today's appointments, each with a button that reflects its state: Start medical visits, Continue medical visits, or Completed + View (home visits: Open visit / Continue visit).
- "Waiting on you": logbook entries to sign or approve, compliance submissions to review, partner requests.
- Incident reporting deadlines with a countdown.
- The current med pass per facility (given / due / late, PRN to check). Before 05:00 this is still last night's bedtime pass.
- My tasks (overdue and due this week), families who should live together, and my own compliance.

**Dashboard** (`/dashboard`) is available to everyone and shows the modules that person can read, for their facilities, over 7, 30 or 90 days (and one facility or all):
- Headline numbers: residents, occupancy, % doses given, average meal intake, incidents, staff compliance %, visits done.
- Needs attention: late doses, compliance to review, expired requirements, logbook approvals, low intake, partner requests, home visits with check-in problems, overdue tasks. Each line links to the matching list.
- Sections: medications (doses per day by outcome, today's passes, PRN effectiveness, most refused), incidents (by day and severity, by type), dining (intake by day, low intake now), medical visits (seen/refused, next 7 days, residents due again), home visits (EVV on time/late/missed, hours delivered, list of visits to check), staff compliance, logbook, lawyers & partners.
- Facilities side by side (admins): residents, occupancy, doses given, med pass today, open incidents, low intake, compliance.

Admins and managers land on the Dashboard; everyone else lands on My day.

## 4. Residents

Flow: create a resident (name, date of birth, facility, admission) → assign a room → fill the record → over time: family links, insurance, medications, meals, visits, incidents, logbook entries → discharge (and readmit if needed).

The resident record (`/residents/{id}`):
- **Alerts strip** at the top: allergies, code status (e.g. DNR), high fall risk, scheduled meds, doses late or refused today, PRN waiting a follow-up, last meal and low intake, open incidents, next appointment, family who should live together, open partner requests.
- **Tabs**: Profile, Medical, Medications, Dining, Contacts, Insurance, Service plan (home care), Visits, Incidents, Shared access, Admissions, Rooms, Notes (clinical), Activity. Admins can add custom tabs and fields and rearrange the layout.
- **Family in care**: link residents as family (parent, sibling, spouse…), mark "house together"; the left panel shows family and whether they live together or apart.
- **Insurance**: coverages ranked primary/secondary (Medicare, Medicare Advantage, Medicaid, commercial, VA, private pay…). Used for visit eligibility.
- **Activity**: the resident's logbook entries, then the full history of changes. History lines from modules a viewer can't access (medications, meals, incidents, clinical notes, visits, partner sharing) are hidden from that viewer.
- **Discharge**: ends active medication orders, removes upcoming visits from schedules, records it, and tells the facility's medication, dining and appointment staff.

## 5. Medical visits (appointments)

Used for clinician visits to many residents (foot checkups, dental, wound care) and single home visits.

1. **Set up**: New appointment → title, facility, visit type (e.g. Nail & foot care, Dental cleaning, Wound assessment), date, start time, minutes per visit, buffer between visits, place of service (CMS POS code, e.g. 13 assisted living, 12 home).
2. **Where**: "Bedside" (the clinician goes room to room) or "In a room" (e.g. the clinic room, residents come to it). Each visit can still be moved to another room.
3. **Residents**: pick from current residents; anyone not eligible is greyed out with the reason (seen too recently, payer not covered, age). "Select all eligible" books everyone at once.
4. **Times**: each resident gets a time slot automatically (start time + minutes per visit + buffer). Reordering or removing someone shifts later times.
5. **Visits** (`/appointments/{id}/visits`): a queue on the left; for each resident the clinician taps codes and writes notes:
   - Procedure codes (e.g. 11720 debride nails 1–5; D0120 periodic oral exam; 97597 wound debridement).
   - Site modifiers (TA left great toe, T1–T9 other toes; SAC sacrum, LHL left heel…).
   - Findings (Q7/Q8/Q9 class findings for Medicare routine foot care; ST1–ST4 pressure-injury stage).
   - Quick notes, free-text notes, photos (resized before upload), and "Seen in" room.
   - Coverage, allergies and the last visit are shown alongside.
6. **Complete & next** saves and opens the next resident; **Refused** and **Not available** close a visit without treatment. When everyone is done the appointment is Completed and My day shows it.

Eligibility rules (per company, visit type, state, age and payer) decide who can be booked and how often (e.g. Medicare routine foot care every 61 days, needs a class finding). Completing a visit sets the resident's next eligible date from the rule they were booked under. Each outcome is written to the resident's history; refusals and absences notify the facility's nurses.

## 6. Medications

Orders (`/residents/{id}?tab=medications`): drug, strength, dose, route, times per day or "as needed" (PRN) with an indication and a daily maximum, controlled-drug schedule, prescriber, start/end dates. Orders can be stopped with a reason.

Med pass (`/medications`): per facility and day, four passes (morning, noon, evening, bedtime), every scheduled dose by room.
- **Given**: records time and who. A dose can't be given more than an hour early. Controlled drugs need a second staff member as witness.
- **Refused / Held / Not available**: needs a reason; the facility's nurses are notified.
- **Late**: a scheduled dose more than an hour past due with nothing recorded. The same rule is used on the med pass, resident alerts, My day, the dashboard, the AI and notifications.
- **PRN** (as needed): give with a reason (and a 0–10 pain score for pain). About an hour later LyCare asks "did it work?"; the follow-up pain score decides effective / not effective. "Didn't work" notifies the facility's nurses.
- **Undo**: same day only, by the person who recorded it (or a supervisor); the resident history keeps what was undone.
- **Report a medication error**: a recorded dose links to a new incident, pre-filled as a medication error.

Every dose goes into the resident's history (the medication administration record, MAR).

**Safety checks.** LyCare compares each resident's medicines with their recorded medication allergies and with each other, using its own list of common, well-documented problems (it is not a full drug database, and the pharmacist still reviews):
- **Allergies**: the drug itself or its family (e.g. penicillin allergy → amoxicillin; sulfa → Bactrim; codeine → other opioids, noting that opioid "allergies" are often intolerance; penicillin → cephalosporins as a lower-risk cross-reaction).
- **Interactions**: e.g. opioid + benzodiazepine (slowed breathing), blood thinner + NSAID (bleeding), warfarin + drugs that raise the INR, ACE inhibitor/ARB + potassium-raising drugs, lithium + NSAIDs, simvastatin + strong CYP3A4 inhibitors, nitrates + sildenafil, levothyroxine + calcium or iron (give 4 hours apart).
- **Duplicates**: two NSAIDs, two opioids, two benzodiazepines, two medicines containing acetaminophen (keep the total under 3 g a day), and so on.
Warnings are graded Allergy, Major or Moderate. While a new order is typed, its warnings show live; it can only be saved with a note of who reviewed it (prescriber or pharmacist) and why it stands, and serious ones notify the facility's medication supervisors. Warnings on existing orders show on the resident's medication tab and as a chip on the med pass until someone records a review. The dashboard counts unreviewed Allergy and Major warnings.

**Supply and refills.** An order can track the count on hand, units per dose and a refill point (default 7 days' supply). Each dose given takes from the count (an undo puts it back). Days left = on hand ÷ daily use (PRN orders use their daily maximum). Running low shows on the order, the dose row and a "Running low" list on the med pass; "Request refill" records the request against the pharmacy, and "Delivery / count" adds a delivery or sets a recount. Once a day the sweep sends the facility's medication staff one digest of tracked medicines that are low, critical or out with no refill requested (a warning if any are critical or out).

**Barcode scanning.** On the med pass, scan the resident's wristband (their ID number, Code 128) and then each package (UPC-A or GS1 DataMatrix carrying the NDC), with a USB/Bluetooth scanner or a phone or tablet camera (Chrome or Edge). A match ("right resident, right medicine") highlights the dose and records it as scanned; a package belonging to another resident, or not on any order, shows a red STOP. Scanned doses are underlined on the MAR, and the dashboard shows the share of doses scanned. `/medications/labels` prints wristband and package barcodes. Orders store the NDC from the package.

## 7. Dining

- **Diet profile** per resident: diet (e.g. Diabetic, Low sodium, Halal), texture and liquids (IDDSI levels), food allergies, assistance needed, seating.
- **Dining screen** (`/meals`): pick facility, day and meal (breakfast, lunch, dinner, snack). Everyone eating that meal with diet, texture and allergies up front. Tap where they ate (dining room, tray, refused, out) and how much (0–100%); fluids optional.
- **Supervised by**: for residents who need help, the person recording is recorded as the one who helped or supervised.
- **Low intake**: the last three meals (within three days) average under half, or two were refused. It's flagged on the dining screen, resident alerts and dashboard, and the facility's nurses are notified once a day.
- Meal schedules (menus) live at `/meals/schedules`.

## 8. Incidents

1. **Report** from the resident ("Report incident") or Incidents → New. Optional: type or dictate the story and "Draft report" — the AI (Claude) fills the form and lists what the state report still needs. Staff check and save.
2. **Fields**: type (fall, injury, medication error, abuse/neglect allegation, missing person, behavior…), severity 1–4 (minor, moderate, serious, critical), when it happened and was discovered, where, summary, description, immediate actions, injuries and body areas, medical care, police.
3. **Rules engine**: on save, the company's rules (by state, care type, incident type and severity) work out who must be told and by when (e.g. parent/guardian immediately, licensing agency within 24 hours, caseworker within 24 hours). Each becomes a deadline with a countdown; staff mark each one notified (how, who, reference).
4. **People and statements**: add people involved, witnesses and staff on duty, with statements; photos and files.
5. **Review**: investigation, root cause, corrective actions, status (open → under review → closed).
6. **Official forms**: print the state's real PDF form, filled in (Washington DCYF 15-941, Oregon PR-0210, Virginia FRI), plus HTML report layouts per agency.

Incident handlers at the facility are notified of new incidents (urgent if serious). Deadlines due within 4 hours or overdue are urgent notifications. Incident rules are edited at `/incidents/rules`.

**How far to trust a rule.** Every state rule names its regulation, links to the official text and shows when it was last checked and by whom (e.g. "WAC 110-145-2780 · last verified Oct 19, 2026 by LyCare team · re-check by Apr 2027"). Each rule has a status: Verified, Re-check due (past its 3, 6 or 12 month interval), Not verified yet, or Problem reported. Any user can "Report a problem" on a rule; it shows as Problem reported until platform staff or a licensing consultant (given a platform account) records a check: still correct, rule updated to match, or problem looked at. Every check and report is kept as the rule's history. Each deadline on an incident shows the regulation it comes from and when that rule was verified. Current coverage: Washington group care (WAC 110-145-2780 reporting, -3200 restraint), Oregon child-caring agencies (OAR 419-400-0180 restraint and seclusion, 419-400-0230 critical events, ORS 419B.015 abuse), plus Texas, Florida and Virginia rules not yet verified.

## 9. Logbook

- **Templates** (platform level): decide which fields an entry has (comments, residents, staff, mood, behavior, goals, location…) and the rules: needs approval, author signs, staff on the entry sign, approver signs. Templates are offered to all companies or selected ones.
- **Company**: can rename a template and add its own fields (text, number, date, yes/no, list) from its Fields library, placed in form sections.
- **Facility**: switches templates on or off and decides which need approval.
- **Write**: pick facility and template, then title, date, residents, staff and the template's fields. The entry shows on each resident's Activity tab.
- **Sign**: one tap stamps the user's saved signature (My signature). Staff listed on the entry are asked to sign. Editing an entry clears its signatures, and they're asked again.
- **Approve**: once every required signature is in, the facility's approvers are notified. Approving adds a note and the approver's signature and locks the entry; it can be returned to pending.

## 10. Clinical notes

Encrypted notes (`/clinical-notes`) linked to residents, facilities, staff or tags. Visible only to users with Clinical Notes access, and only for residents and facilities in their scope. Never shared with partners.

## 11. Staff compliance

1. **Templates** (platform): what staff must provide — fields (one date field can set the expiry) and documents — plus category, the states it applies to, companies it's offered to, whether a manager reviews it, and when it shows as "expiring".
2. **Company**: sees only templates offered to it that apply in its facilities' states; assigns them to facilities (a Texas requirement can't be assigned to a Washington facility). A facility can switch one off locally.
3. **Staff**: "My compliance" shows each requirement as Compliant, Expiring soon, Pending review, Missing, Declined or Expired. Staff fill in the details, upload documents and submit; reviewers are notified.
4. **Review**: a manager (not the person themselves) approves or declines with a note; the staff member is notified. Approval sets the expiry.
5. **Expiry**: staff are notified when a requirement is about to expire; once expired, managers at every facility the person works at are notified too.
6. **Overview** (`/compliance`): % compliant and counts per status, filters by facility, state and requirement, CSV export.

When staff are added to a new facility they're told to check My compliance for new requirements.

## 12. Tasks, calendar, jobs, reports

- **Tasks** (`/tasks`): title, facility, dates, priority, progress, recurring schedule, subtasks, owner, assigned staff, members, residents, tags, comments. Notifications: assignment, comments, completion (to the owner) and overdue. A recurring copy always starts not done.
- **Calendar** (`/calendar`): my calendar by default (shifts, meetings, training, time off, appointments, tasks, compliance expiries); managers can view another person or everyone. Events can invite staff; invitees are notified, and so are people affected when an event moves, is cancelled, or someone is removed. A shift added to someone else's calendar notifies them.
- **Jobs** (`/jobs`): numbered work orders by job type with custom fields, linked to a room, clients and tasks. Assignees are notified. Jobs follow facility scope.
- **Reports** (`/pdf-reports`): activity and task PDFs, resident workbook export. Staff limited to some facilities see only reports they created; downloads are logged.

## 13. Home care (in-home agencies)

- **Service plan** on each client: authorized services (e.g. Personal care, Homemaker, Respite) with hours per week, days, payer (e.g. Florida Medicaid LTC), authorization number, dates and preferred caregiver. It shows scheduled and delivered hours this week, and flags an authorization that isn't current.
- **Home visit**: the caregiver opens today's visit from My day, **checks in** at the door (time and phone location recorded), works through the care-plan task codes (bathing, dressing, meal prep, medication reminder…), adds notes, and **checks out**. This is electronic visit verification (EVV). A check-in or check-out is recorded once, with who did it, and written to the client's history.
- **Exceptions**: no check-in, late check-in (15+ minutes), short visits (under 75% of the scheduled time) and check-ins without a location are listed on the dashboard. Supervisors are notified when a visit has no check-in 30 minutes after it should have started.

## 14. Group homes: case work

For youth in foster group homes (`/casework`, and the **Case work** tab on each youth's record). Only companies that use it (group homes) have the Case work module.

- **Case plan**: permanency goal (reunification, adoption, guardianship, relative placement, independent living) and a concurrent goal, the court case number, the placing agency's caseworker (name, agency, phone, email), the next plan review, and how often the caseworker must see the youth (default every 30 days; Washington requires monthly health and safety visits).
- **Goals**: by area (education, health, behavior, family, independent living, permanency) with how it's measured, a target date, who's responsible, status (not started, in progress, met, not met, discontinued) and progress %. Each update keeps a dated note.
- **Court**: hearings (shelter care, fact-finding, disposition, dependency review, permanency planning, termination) with date, court, judge, room, the staff member going with the youth and transport, and when the home's court report is due. Hearings show on the calendar and My day. Recording the outcome can book the next hearing. Reminders go out 3 days before; court reports due within 3 days are flagged.
- **Caseworker contacts**: every visit, call, video, email or text with the caseworker, and whether the youth was seen (privately). A visit where the youth was seen resets the clock; overdue visits are flagged on the youth's record, the Case work page and the dashboard, and the facility's managers are told once a week.
- **Restraints**: start and end time, the hold (escort, standing, seated, supine, prone; holds the facility's state prohibits are marked and flagged: prone everywhere, supine too in Oregon, where a restraint past 10 minutes also needs a supervisor's written authorization every 5 minutes), the training program, why it was needed, what was tried first, staff involved, witness, injury and the youth's account. Recording one also **files an incident** (type: physical restraint), so the state's rules set the reporting deadlines (e.g. Washington: program director review, plus DCYF Intake and licensor within 48 hours if there's an injury or improper hold; Oregon: case manager, attorney, CASA and parents by the next business day, debrief within two business days, quarterly report). The facility's managers are notified. A manager who wasn't involved reviews it (parent and caseworker told, debrief with the youth, review notes; over 15 minutes needs an explanation). Restraints not reviewed after a day are flagged again.
- **Allowance**: a ledger per youth with a spending balance and a savings balance. A weekly amount by age with a share to savings; "Pay allowances" pays everyone at a home once a week. Spending, clothing, gifts, earnings and moves to or from savings; cash handed over needs the youth's confirmation, an optional witness, and can't take a balance below zero.
- **Overview** (`/casework`): youth in care, those without a plan, caseworker visits overdue, court in the next 30 days and reports due, restraints in the last 30 days and those to review, and a table of every youth with plan, goals, last caseworker visit, next hearing and balances.
- **Partners**: a guardian ad litem or lawyer sees the case plan goals and court dates only if "Case plan & court dates" is shared with them. Restraint records, contact notes and allowances stay internal.

## 15. Partner portal (lawyers, guardians ad litem)

1. **Share access** (resident → Shared access): pick or invite the partner, choose sections (profile & case details, placement history, case plan & court dates, incident reports, visits & appointments, medications, documents), the legal basis (court order, signed authorization, power of attorney, guardianship), a reference number, an end date, and a copy of the order. Clinical notes are never shared. It's recorded in the resident history and the access log.
2. **Portal** (`/portal`): partners see only "My clients" and, for each, only the shared sections, until the end date (inclusive) or until staff end access. Incident reports show only reviewed incidents the client was part of (not draft ones, not ones where they were only a witness), and incident-type logbook entries without free-text comments.
3. **Requests**: partners ask for records, a meeting or information, with a needed-by date. The staff who manage that resident get a highlighted notification and an email.
4. **Answer**: staff reply and attach a file (only if the partner has the Documents section). The partner is emailed that there's a reply (no client details in the email).
5. **Documents**: partners can upload documents (e.g. a court order); staff are notified.
6. **Access log**: every partner view and download, and staff sharing, answering, opening partner documents and ending access, is logged per resident.
7. **End access**: staff end it any time (the partner is emailed), or it lapses after the end date.

Partner logins are separate from staff: they're never in the staff Users list and can't reach any staff screen.

## 16. AI (Claude)

- **Ask LyCare** (`/ask`): ask questions in plain English ("Who has had low intake this week?", "Any medication problems today?", "Which families aren't housed together?"). It answers only from tools that read the records the asker is allowed to see (residents, medications and late doses, meals, incidents and deadlines, appointments, families, group-home case work). Names are links to the records. It never changes anything.
- **Incident drafting**: turns typed or dictated notes into a structured incident report and lists what's missing for the state report. Staff review before saving.
- Every AI request is recorded (who, what, which tools ran, which residents came back). Uses Anthropic's API directly with the company's key.

## 17. Notifications and email

Notifications appear on the bell (red when urgent) and the Notifications page (`/notifications`), where each person chooses whether urgent items are emailed and mutes kinds they don't want. Warning and urgent items are emailed through Brevo (demo addresses at example.com are skipped). Until go-live they go out **once a day** as one digest per person (warnings and urgent items from the last day that haven't been read in the app, urgent first); setting `ALERT_EMAILS=instant` emails each one as it happens.

Who hears what:

| Event | Who | Level |
|---|---|---|
| New incident | Incident handlers at the facility | Urgent if serious, else warning |
| Reporting deadline within 4 hours or overdue | Incident handlers | Urgent |
| Dose refused, held or not available | Nurses at the facility | Warning |
| Doses an hour late, unrecorded (per pass) | Staff who give medications at the facility | Warning |
| PRN not followed up after an hour / didn't work | The giver / the facility's nurses | Warning |
| Low intake | Nurses at the facility | Warning |
| Medical visit refused or resident not available | Nurses at the facility | Info |
| Home visit with no check-in after 30 minutes | Schedulers/supervisors at the facility | Warning |
| Discharge | Medication, dining and appointment staff at the facility | Info |
| Compliance submitted / approved / declined | Reviewers / the staff member | Info / info / warning |
| Compliance expiring / expired | The staff member / plus their managers | Warning |
| Added to a facility | The staff member | Info |
| Logbook entry to sign / ready to approve / decision | Listed staff / approvers / the author | Info |
| Task assigned, commented, completed, overdue | Assignees, owner, members | Info |
| Calendar invite, move, cancellation, removal, shift added | Invitees / the person whose calendar it is | Info |
| Job assigned | Assignees | Info |
| Restraint recorded / not reviewed after a day | Case work managers at the facility | Warning (urgent if injury or prohibited hold) |
| Court hearing in 3 days / court report due | Staff going with the youth, case work managers | Info / warning |
| Caseworker visit overdue | Case work managers at the facility (weekly) | Info |
| Partner request or document | Staff who manage that resident | Warning |
| Partner request answered / access ended | The partner | Warning (email) |

Company owners and admins receive company-wide alerts, but floor-level ones (refused or late doses, low intake, PRN) go only to staff at that facility. Each event notifies a person once.

**Time-based checks** (deadlines, late doses, PRN follow-ups, overdue tasks, compliance expiries, missed check-ins) run once a day from Vercel cron (`/api/cron/sweep`, 12:00 UTC, followed by the email digest) and, for the bell, whenever people use the app (at most every 10 minutes per company). The GitHub Actions workflow can run it by hand, or every 15 minutes again after go-live.

## 18. Security, privacy and audit

- Sign-in with username and password; optional or enforced two-factor authentication per company. Sessions last 7 days.
- Every module checks permissions on the server; facility scope applies everywhere (section 1).
- Files are private and streamed only after the same checks as their record. Only images, PDFs and plain text open in the browser; everything else downloads, and files can't run script.
- Audit trail: per-record history (residents, tasks, jobs, users, groups, companies…), resident activity, medication records including undo, EVV check-ins, partner access log, report downloads, company switches by platform staff, "log in as" sessions, AI requests.
- A deleted company's staff are signed out everywhere.

## 19. Setup (admins)

- Company: details, logo, two-factor policy, module names, licensed sections.
- Facilities: address, state, rooms (types, statuses, capacity), staff, compliance requirements, logbook templates.
- Staff and users: profile, positions, groups, facilities, signature, compliance.
- Groups: permissions per module and action.
- Fields library: custom fields for resident layouts, logbooks and jobs.
- Visit types: service type › sub type › visit type, eligibility rules, codes.
- Incident rules, compliance templates, logbook templates.
- Billing (subscription, payment methods, history) and proposals (benefits proposals for clients) are separate modules.

## 20. Glossary

- **PRN**: "as needed" medication (from Latin *pro re nata*), given for a reason such as pain, with a follow-up.
- **MAR**: medication administration record, the log of every dose.
- **EVV**: electronic visit verification, the check-in/out with time and location that Medicaid requires for home care.
- **IDDSI**: international scale for food texture and drink thickness (e.g. 4 pureed, 6 soft and bite-sized).
- **POS code**: CMS place of service on a claim (12 home, 13 assisted living, 14 group home, 31 skilled nursing, 32 nursing facility).
- **Class findings (Q7/Q8/Q9)**: Medicare modifiers that justify routine foot care.
- **Site modifiers (TA, T1–T9)**: which toe a foot procedure was done on.
- **GAL**: guardian ad litem, appointed by a court to represent a child's interests.
- **DCYF / ODHS / VDH**: Washington, Oregon and Virginia agencies that receive incident reports.
- **Halal / Diabetic / Low sodium**: diet types on a diet profile.

## 21. Main URLs

`/my-day` · `/dashboard` · `/residents` · `/casework` · `/residents/{id}` · `/appointments` · `/appointments/{id}/visits` · `/medications` · `/medications/labels` · `/meals` · `/incidents` · `/incidents/rules` · `/logbook` · `/clinical-notes` · `/compliance` · `/account/compliance` · `/tasks` · `/calendar` · `/jobs` · `/pdf-reports` · `/notifications` · `/ask` · `/account/profile` · `/portal` (partners) · `/how-to` (public walkthroughs) · `/llms.txt` (this page)