mirror of https://github.com/temetro/temetro.git synced 2026-08-28 19:37:33 +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

coss Meter

When to use

Bounded scalar measurement display (not task progress).
Quality/capacity indicators with min/max semantics.

When NOT to use

If displaying task completion or async progress -> use Progress instead.
If the indicator is indeterminate -> use Spinner or Progress instead.

Install

npx shadcn@latest add @coss/meter

Manual deps from docs:

npm install @base-ui/react

Canonical imports

import { Meter, MeterLabel, MeterValue } from "@/components/ui/meter"

Minimal pattern

<Meter value={40}>
  <MeterLabel>Progress</MeterLabel>
  <MeterValue />
</Meter>

Patterns from coss particles

Key patterns

Meter with formatted value and range:

<Meter value={75} min={0} max={100}>
  <div className="flex justify-between text-sm">
    <MeterLabel>Storage</MeterLabel>
    <MeterValue>{({ formattedValue }) => `${formattedValue} used`}</MeterValue>
  </div>
</Meter>

Minimal meter without label:

<Meter value={40} aria-label="Progress" />

More examples

See p-meter-1 through p-meter-4 for label, formatted value, and range patterns.

Common pitfalls

Using meter to represent completion tasks better suited for Progress.
Missing min/max context when values are not obvious to the user.
Treating meter as interactive control rather than read-only indicator.

Useful particle references

without label and value: p-meter-2
with formatted value: p-meter-3
with range: p-meter-4

1.5 KiB Raw Blame History