mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-09 13:01:00 +00:00
Marc-André Bombeck
14f0fc4d4f
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
27 lines
968 B
TypeScript
27 lines
968 B
TypeScript
/**
|
|
* The body-site view query (v1.39.2).
|
|
*
|
|
* Without `site` the route answers with the sites the record holds, which is
|
|
* both the view's list of choices and the suggestions a body-site field offers
|
|
* while the person types. With `site` it also answers with what is filed at
|
|
* that site. `site` is compared after the decrypt, case and accents folded, to
|
|
* the whole stored site: it names a site the list offered, it is not a word
|
|
* search (the procedures tab keeps that).
|
|
*/
|
|
import { z } from "zod/v4";
|
|
|
|
import { lateralityEnum } from "@/lib/validations/encounters";
|
|
|
|
export const bodySiteQuerySchema = z
|
|
.object({
|
|
site: z.string().trim().min(1).max(200).optional(),
|
|
laterality: lateralityEnum.optional(),
|
|
})
|
|
.strict()
|
|
.refine((v) => v.laterality === undefined || v.site !== undefined, {
|
|
path: ["laterality"],
|
|
message: "laterality narrows a site and needs one",
|
|
});
|
|
|
|
export type BodySiteQuery = z.infer<typeof bodySiteQuerySchema>;
|