Open calejvaldez opened 2 months ago
PROs should cover...
It should be understood that no medical intervention can be done to make someone the most comfortable, but it could keep families more at ease.
Another note: Often people will say that they're fine when they're not. Questionnaire won't really get it out of them, so we just have to take their word for it at the end of the day.
I think our PRO responses will not be text responses, but rather responses with numbers. (e.g.: From a scale of 1-10....) It'll be easier to chart, but it leaves it to the hospice workers to double-check with the patients about their responses.
In the backend, add hardcoded set of questions to pose to the patient. And also give these to the frontend with a tauri command I assume.
A few comments for Tuesday:
Maybe we should remove recorded_date
and generate it in the backend so that the frontend doesn't have to return too many arguments.
This is kind of how I imagine PROs to work:
---
title: PRO Flow
---
flowchart LR
A["Frontend gets questions from backend"]
B["Frontend displays questions with textbox answers"]
C["Send questions with answers to backend*"]
A --> B --> C
*Whether the backend receives individual PROs (add_pro()
) or a bunch of PROs (add_pros()
) depends on how the design looks. We should talk about this before programming, or just have options for both.
to do: add backend function to return only pro questions
edit by @calejvaldez: added in c99cca6348cdf522c56192d57fab8ce86a1eca54
ID: FUNC12 TITLE: Patient Reported Outcomes DESCRIPTION: The system shall include daily(?) surveys asking patients how their treatment has been working for them. PRIORITY: Medium
FRONTEND TODO:
BACKEND TODO: