mirror of https://github.com/temetro/temetro.git synced 2026-09-04 06:45:26 +00:00

Files

T

Khalid Abdi 929bec8f31 feat: AI-added records save with placeholders + "Added by AI" provenance

Stop blocking AI imports/proposals on missing non-critical fields. Records
the chat agent drafts now save with safe placeholders, auto-generated file
numbers, and a source="ai" marker that surfaces an "Added by AI" badge so a
clinician can review/edit them later.

Backend:
- add `source` (manual|ai) column to patients/appointments/prescriptions
  (migration 0014) + canonical types, services, validation schemas
- relax patient/appointment validation: empty file number allowed, demographic
  + type/provider/initials fall back to placeholders (initials derived from name)
- patients.generateFileNumber() auto-assigns an MRN when one is missing
- proposeAppointment accepts a name when no file number resolves; AI commits +
  /api/ai/import stamp source="ai"

Frontend:
- `source` on Appointment/Patient/Prescription types; AI commits send source="ai"
- reusable <AiBadge> shown on the Patients table/detail and prescriptions list

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-14 19:27:17 +03:00

1.7 KiB

Raw Blame History

coss Frame

When to use

Bordered app surfaces around content blocks.
Container wrapper for data components like table, cards, and panes.

Install

npx shadcn@latest add @coss/frame

Manual deps from docs:

# No extra runtime dependency required for this primitive.

Canonical imports

import {
  Frame,
  FrameDescription,
  FrameFooter,
  FrameHeader,
  FramePanel,
  FrameTitle,
} from "@/components/ui/frame"

Minimal pattern

<Frame>
  <FrameHeader>
    <FrameTitle>Title</FrameTitle>
    <FrameDescription>Description</FrameDescription>
  </FrameHeader>
  <FramePanel>Content</FramePanel>
  <FrameFooter>Footer</FrameFooter>
</Frame>

Patterns from coss particles

Key patterns

Frame with header actions:

<Frame>
  <FrameHeader className="flex items-center justify-between">
    <div>
      <FrameTitle>Users</FrameTitle>
      <FrameDescription>Manage team members.</FrameDescription>
    </div>
    <Button size="sm">Add User</Button>
  </FrameHeader>
  <FramePanel>{/* Table or list content */}</FramePanel>
  <FrameFooter>
    <p className="text-muted-foreground text-sm">Showing 1-10 of 100</p>
  </FrameFooter>
</Frame>

Use Frame to normalize border/radius around heterogeneous inner content (tables, lists, cards).

More examples

See p-frame-1 through p-frame-3 for basic and separated panel patterns.

Common pitfalls

Using nested frames excessively, causing dense double borders.
Applying frame as layout grid replacement instead of content surface wrapper.
Forgetting to align inner component width expectations (table/list full width).

Useful particle references

separated panels: p-frame-3

1.7 KiB Raw Blame History