mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-16 07:13:29 +00:00
A lab panel files itself against the visit it came from, and never has to. The OCR review and the manual form both offer the suggestion through the one shared field, anchored on the draw date rather than on now, so backdating a reading moves the offer with it. The commit writes one link PER RESULT ROW, which is why the join is m:n: a marker re-run on a different day belongs to its own visit. Best-effort by design — the readings are the write that matters and must not be lost to a link that could not be made. The condition side gets a Visits about this card with an action that pre-links the episode. From the episode side only, and that is a decision: an episode spans weeks and a visit is a point, so matching the other way would be wrong often enough to teach a person to ignore every suggestion in the product. A due checkup gains a second action beside erledigt. Filing the visit as done satisfies the checkup through the same forward-only, idempotent primitive the checkbox uses, so doing both is one satisfaction and no error. The two actions answer different questions — one says it happened, the other says where. An appointment now appears where a person looks, and NEITHER surface relaxes the reminder-table exclusion that keeps it out of the preventive-care lists. Both read the visit table: a quiet line under the dashboard checkup block for anything inside two weeks, and one rail item for today or tomorrow. A diff in either that touches origin is the wrong fix. A visit write now also refreshes the reminder reads. Closing a checkup moves its next-due date on three surfaces that would otherwise keep showing it due until their own poll. OpenAPI regenerated in the same commit.
44 lines
1.3 KiB
TypeScript
44 lines
1.3 KiB
TypeScript
"use client";
|
|
|
|
/**
|
|
* The document moment of the visit suggestion.
|
|
*
|
|
* The rule and the rendering both live elsewhere — `suggest-window.ts` on the
|
|
* server and `EncounterSuggestionField` in the browser — so this file is only
|
|
* the wiring: which date to anchor on, and where the chosen id goes.
|
|
*
|
|
* The anchor is `reportDate ?? documentDate`. `reportDate` is what the model
|
|
* transcribed off the letter itself and is never inferred, so it is the truer
|
|
* of the two; `documentDate` is the person's own filing date and is the
|
|
* fallback.
|
|
*
|
|
* It renders nothing once the document already names a visit that this session
|
|
* did not choose: an offer to file something already filed is noise.
|
|
*/
|
|
import { EncounterSuggestionField } from "@/components/encounters/encounter-suggestion-field";
|
|
|
|
export function DocumentEncounterSuggestion({
|
|
anchor,
|
|
alreadyLinked,
|
|
disabled,
|
|
value,
|
|
onChange,
|
|
}: {
|
|
anchor: string | null;
|
|
alreadyLinked: boolean;
|
|
disabled?: boolean;
|
|
value: string | null;
|
|
onChange: (encounterId: string | null) => void;
|
|
}) {
|
|
if (alreadyLinked) return null;
|
|
return (
|
|
<EncounterSuggestionField
|
|
anchor={anchor}
|
|
value={value}
|
|
onChange={onChange}
|
|
disabled={disabled}
|
|
slot="document-encounter-suggestion"
|
|
/>
|
|
);
|
|
}
|