mirror of https://github.com/temetro/temetro.git synced 2026-08-19 06:36:21 +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.5 KiB

Raw Blame History

Composition Rules (coss)

Use this when composing complex UI from coss primitives and particles.

Core Rules

Prefer composing existing primitives over custom wrappers with duplicated behavior.
For trigger-based primitives (Dialog, Menu, Select, Popover, Tooltip), follow each primitive's documented trigger/content hierarchy and composition API; do not mix patterns across components.
Use coss/Base UI trigger APIs consistently (typically render-based composition).
Use complete sub-structures where required (for example title/description regions in dialogs where relevant).

Patterns

<Dialog>
  <DialogTrigger render={<Button variant="outline" />}>Open</DialogTrigger>
  <DialogPopup>
    <DialogHeader>
      <DialogTitle>Title</DialogTitle>
    </DialogHeader>
    <DialogPanel>Body</DialogPanel>
  </DialogPopup>
</Dialog>

Portal forwarding (`portalProps`)

Only specific composed wrappers (and ToastProvider / AnchoredToastProvider for toasts) accept optional portalProps (spread onto Base UI Portal). See ../portal-props.md for the allowlist.

Grouped Controls

<Group>
  <Button variant="outline">A</Button>
  <GroupSeparator />
  <Button variant="outline">B</Button>
</Group>

Anti-patterns

Building bespoke dropdown/dialog behavior instead of using primitives.
Mixing APIs from other ecosystems (asChild-only mental model) without checking coss equivalents.
Omitting key subcomponents that preserve accessibility and layout conventions.

1.5 KiB Raw Blame History