Files
HealthLog/prisma
Marc-André Bombeck 5994762c74 feat(labs): map FHIR lab observations into lab readings
A shared mapper and writer for lab results arriving as FHIR resources
(DSTU2 and R4 Observations): final results only, laboratory category,
quantity / string / coded values, comparator results kept as printed
text, the report's own reference range in the reading's unit, panel
headers naming their members, notes sealed at rest. UCUM units map onto
the spellings the labs feature uses, and a LOINC code hints the catalog
analyte when the account's markers are matched.

Readings carry an identity (lab_results.external_id, a digest of the
issuer and the record identifier) so the same result is recognised
whether it arrives again from an export or from a phone, and a deleted
result stays deleted. A reading the record already holds by value is
skipped as well.
2026-11-17 18:37:56 +01:00
..

prisma/

The database layer. HealthLog runs on PostgreSQL 18 (the compose default) or 16 via Prisma 7. This directory holds the single schema file and the forward-only migration history; the generated client is emitted elsewhere.

Contents

  • schema.prisma — 61 models, one file. cuid() primary keys, snake_case columns via @map(...), encrypted columns mostly suffixed *Encrypted (search the file; there are 24 encrypted column references). The generator client block emits to ../src/generated/prisma (imported as @/generated/prisma).
  • migrations/ — numbered, forward-only SQL migrations (0001_… upward). migration_lock.toml pins the provider to postgresql.

Migration workflow

# author a migration from a schema edit
pnpm dlx prisma migrate dev --name <short_snake_case_name>

# regenerate the client after any schema change
pnpm dlx prisma generate

Number a new migration with the next free prefix. The production entrypoint runs prisma migrate deploy on boot, so every migration must apply cleanly forward — there is no down-migration path. Always include the migration file in the same change as the schema edit.

Conventions

  • Encryption is fail-closed: *Encrypted columns are written through @/lib/crypto (AES-256-GCM, versioned key ids); never store plaintext in an encrypted column. Key rotation is scripts/rotate-encryption-key.ts + docs/ops/encryption-key-rotation.md.
  • The generated client under src/generated/prisma is build output — do not edit it.
  • Schema-touching changes that affect the API surface must regenerate docs/api/openapi.yaml (pnpm openapi:generate; CI fails on drift).

Related: ../src/lib/README.md (db.ts, rollups/), ../docs/ops/ (migrations + backup runbooks).