feat(body-sites): record a body site on conditions and add a body-site view

A condition (illness episode) can carry where on the body it sits, in the
person's own words and encrypted at rest, plus an optional side (LEFT,
RIGHT, BOTH). Same enum, codec and reasoning as the procedure's site.

- migration 0354: two nullable columns on illness_episodes, reusing the
  laterality type from 0349
- create and edit accept bodySite and laterality; on PATCH an absent key
  keeps the stored value, so an edit from the shipped iPhone app, which
  never sends either field, leaves them untouched
- GET /api/body-sites: the sites the record holds across visits and
  conditions, folded after the decrypt and bounded per kind; with site
  (and laterality) the visits and conditions there, one hop to their
  documents, lab results and visits. Read in the profile section;
  conditions only under an illness grant with the module on, and links
  into ungranted sections come back as unlabelled placeholders
- the link service reads document and visit links from the condition's
  end of the two existing tables
- /checkups gains a Body sites tab; the visit and condition forms share
  one body-site field pair that suggests sites already used; a
  condition's page links its site into the view
- the doctor report, the clinician page and the MCP doctor-visit summary
  name the site on conditions; the Coach illness block carries it
  sanitised, and MCP get_illness_recovery returns it fenced
- backup and restore carry both fields in both file kinds; the site is
  registered as ciphertext and rotates with the key
- i18n in all seven locales, OpenAPI regenerated

Refs #1025
This commit is contained in:
Marc-André Bombeck committed 2026-09-25 21:55:14 +02:00
1 parent af65f01fec
commit 14f0fc4d4f
57 files changed
+3501 -133

No files matched your search

+11
View File
@@ -54,6 +54,17 @@ export const encounterKeys = {
*/
encounterProcedures: (q: string, laterality: string | null) =>
["encounters", "procedures", q, laterality] as const,
/**
* v1.39.2 — the body-site view and the body-site suggestions. Under the
* `["encounters"]` root, so a visit write evicts it with the list; a
* condition write reaches it through `bodySitesAll` in
* `illnessDependentKeys`, because conditions are the other half of it. The
* picked site and side are part of the key: the selection is resolved on the
* server after the decrypt. The suggestions read is the no-site slot.
*/
bodySitesAll: () => ["encounters", "body-sites"] as const,
bodySites: (site: string | null, laterality: string | null) =>
["encounters", "body-sites", site, laterality] as const,
/**
* The "which visit does this belong to" verdict for one anchor date. The
* anchor is part of the key because it IS the question: a document dated the
+3
View File
@@ -256,6 +256,9 @@ export const illnessDependentKeys = [
queryKeys.illness(),
queryKeys.dashboardSnapshot(),
queryKeys.dailyDigest(),
// v1.39.2 — a condition's body site is half of the body-site view and of
// the suggestions a body-site field offers.
queryKeys.bodySitesAll(),
];
/**