mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-18 08:02:12 +00:00
Carry medication dose changes through backup and restore
The titration history was classified as backed up and travelled with nothing. An account restored from a backup showed the current dose and no record of how it got there: the ramp, the reductions, the note the prescriber gave for each step. For a long-running drug that history is often the more clinically interesting half. Export writes the rows nested inside their drug, ordered by effectiveFrom, so a portable restore that mints fresh ids needs no remap. The note follows the contract the side effects already use: a portable export decrypts it for a human reader, a disaster-recovery export carries the ciphertext verbatim, and a restore never writes it into the legacy plaintext column. Order is the content here, not decoration. Two rows on the same drug in the same unit, 5 mg then 10 mg, describe a ramp; the same two rows returned in the other order describe a taper. Counting them back cannot tell those apart, so the round-trip test asserts the sequence and the values, not the count. MedicationDoseChange moves from the coverage-pending register into the two-ended list, which makes the round-trip registry incomplete until a row is seeded and counted. That is a compile error, not a review note.
This commit is contained in:
1 parent
aca5b2d30b
commit
5e0994aab9
6 files changed
+152
-2
No files matched your search
@@ -82,6 +82,7 @@ vi.mock("@/lib/cache/invalidate", () => ({
|
||||
|
||||
const OWNER_ID = "round-trip-owner";
|
||||
const AT = (iso: string) => new Date(iso);
|
||||
const DOSE_CHANGE_NOTE = "titration note, encrypted at rest";
|
||||
const SIDE_EFFECT_NOTE = "nausea for two hours after the evening dose";
|
||||
|
||||
beforeEach(async () => {
|
||||
@@ -107,6 +108,9 @@ const COUNT_BACK: Record<
|
||||
p.medicationSideEffect.count({ where: { userId } }),
|
||||
MedicationPauseEra: (p, userId) =>
|
||||
p.medicationPauseEra.count({ where: { userId } }),
|
||||
// No own `userId` column — reached through the drug, like the schedules.
|
||||
MedicationDoseChange: (p, userId) =>
|
||||
p.medicationDoseChange.count({ where: { medication: { userId } } }),
|
||||
MoodEntry: (p, userId) => p.moodEntry.count({ where: { userId } }),
|
||||
MoodContext: (p, userId) => p.moodContext.count({ where: { userId } }),
|
||||
MoodEntryTagLink: (p, userId) =>
|
||||
@@ -230,6 +234,27 @@ async function seedEveryTwoEndedModel(prisma: PrismaClient): Promise<void> {
|
||||
// drug is paused right now; a restore that closed it at restore time would
|
||||
// still count one row back here and read as recovered. The field-level
|
||||
// assertion at the end of the test is what holds the null.
|
||||
// A two-step ramp. The ORDER is the content here: same drug, same unit,
|
||||
// 5 mg then 10 mg. A restore that returned them reversed would still count
|
||||
// two rows back and would describe the opposite clinical story.
|
||||
await prisma.medicationDoseChange.createMany({
|
||||
data: [
|
||||
{
|
||||
medicationId: medication.id,
|
||||
effectiveFrom: AT("2026-04-01T08:00:00.000Z"),
|
||||
doseValue: 5,
|
||||
doseUnit: "mg",
|
||||
noteEncrypted: encryptToBytes(DOSE_CHANGE_NOTE),
|
||||
},
|
||||
{
|
||||
medicationId: medication.id,
|
||||
effectiveFrom: AT("2026-06-01T08:00:00.000Z"),
|
||||
doseValue: 10,
|
||||
doseUnit: "mg",
|
||||
noteEncrypted: null,
|
||||
},
|
||||
],
|
||||
});
|
||||
await prisma.medicationPauseEra.createMany({
|
||||
data: [
|
||||
{
|
||||
@@ -732,6 +757,39 @@ describe("every model the plan claims two-ended survives a real restore", () =>
|
||||
{ pausedAt: "2026-07-15T08:00:00.000Z", resumedAt: null },
|
||||
]);
|
||||
|
||||
// The ramp, in order, with the note back in its column. Counting says two
|
||||
// rows returned; only this says they came back as the same ramp, and that
|
||||
// the encrypted note did not land in the plaintext column on the way.
|
||||
const doses = await prisma.medicationDoseChange.findMany({
|
||||
where: { medication: { userId: OWNER_ID } },
|
||||
orderBy: { effectiveFrom: "asc" },
|
||||
});
|
||||
expect(
|
||||
doses.map((d) => ({
|
||||
effectiveFrom: d.effectiveFrom.toISOString(),
|
||||
doseValue: d.doseValue,
|
||||
doseUnit: d.doseUnit,
|
||||
note: readNote(d.noteEncrypted, d.note),
|
||||
plaintextColumn: d.note,
|
||||
})),
|
||||
"the titration must come back as the same ramp, in order",
|
||||
).toEqual([
|
||||
{
|
||||
effectiveFrom: "2026-04-01T08:00:00.000Z",
|
||||
doseValue: 5,
|
||||
doseUnit: "mg",
|
||||
note: DOSE_CHANGE_NOTE,
|
||||
plaintextColumn: null,
|
||||
},
|
||||
{
|
||||
effectiveFrom: "2026-06-01T08:00:00.000Z",
|
||||
doseValue: 10,
|
||||
doseUnit: "mg",
|
||||
note: null,
|
||||
plaintextColumn: null,
|
||||
},
|
||||
]);
|
||||
|
||||
// The dose, read back column by column. The count above says a row
|
||||
// returned; a restore that wrote one row with every optional column
|
||||
// defaulted would satisfy it and hand back an Impfpass line with no
|
||||
|
||||
Reference in new issue
Block a user