7.2 KiB
-
F_ORAL: i would say for now we add all the values we have, and that are not e.g. natural physical constants that noone would ever want to change (vs. everything that could deviate from person to person and that can make a visible / measurable difference), to the (in doubt "advanced" section of the) ui for transperency and flexibility reasons. with reasonable (not to restrictive but in the realm of possibility) min/max values. in this case one could argue that everyone should take those meds oraly, but if we make it transparent everyone can see that this might e.g. be the reason that our simulation slightly deviates from some statistics or other simulations (they may not be aware of this parameter and they might want to know more about it). also, in some rare cases people may take meds via other routes (e.g. in hospital settings), so having this parameter editable could be useful in some edge cases.
-
an additional topic that came to mind (unless already mentioned earlier): we always simulate a fixed number of days to get a "stable" simulation. the user should be allowed to set this number of days as a parameter. this way one can e.g. simulate their first day starting from scratch without assuming any prior history.
-
an additional topic that came to mind (unless already mentioned earlier): we always simulate a fixed number of days to get a "stable" simulation. the user should be allowed to set this number of days as a parameter. this way one can e.g. simulate their first day starting from scratch without assuming any prior history.
-
regarding half-life vs. factor at first glance i would assume that users may be more familiar with the prinzipal of the half-life, so we make the half-life(s) editable in the ui and use the factors in our formular (if needed). i doubt it wouldn't hurt if we calculate and show the factors (where applicable) in the ui, either next to the half-life (h) input field(s) or, in case it generally makes sense to show a small (see "summary" below).
-
therapeutic range and some other defaults: this is currently my own range (most likely a bit lower and a bit wider but not by much), which may apply for other values as well (e.g. the absorption hal-life of 1.5 vs. 0.9 you mentioned, it may be that the ai suggested this initially, or i found this value somewhere, or in doubt is imply changed to what "looked how i feel" when i follow the simulated plan. so in doubt, always choose the more "general" and appropriate values as defaults and i can later change them to my own liking/needs in my personal profile
- reason: this is my own project/prototype and i am still tweaking. at least for now it dint's share it widely, just with 1-2 friends and family but if it seems helpful i might post it in a forum with my experiences (why hide it if it could potentially help others to understand the basic mechanisms).
- age selection?: it seems that this (and maybe other values as well) not only varies between persons, it also seems to be quite different between adults (lower) and children (higher), or in general depending on age. at first glance a more fine grained age range seems overkill, but we could provide a selection for Adult vs. Child (6-12) or similar at least if we can make this work in a reasonably valid way. otherwise we can stick with adults in general users could still manually change some settings to make it more/less work for children too (e.g. reduce the volume of distribution Vd value or the values that influence Vd). if this does not seem viable or too complex, then for simplicity reasons we could just start with allowing the "full range" (applicable for adults and children) and the users can make some research on their own and tweak the relevant values to their needs in an attempt e.g. to simulate for children. according to the ai research, for children taking 70mg LDX the Men C max might be around 134.0 ng/mL (vs. 69 to 80.3 ng/mL for adults taking 70mg LDX), where supra-therapeutic / alert levels might start above 100 ng/mL for adults (unknown for children from the data i have, but presumably above the 134.0 ng/mL).
-
Advanced (collapsed):
- body weight based scaling: on/off toggle (default off) with a kg input field (enabled and used only if toggle=on).
- "Taken with Food (High-Fat Meal)?": on/off toggle (default off) with a tmax input field (enabled and used only if toggle=on, default value: +1h). either a regular +/- button decimal input field (one decimal digit should suffice i guess?). min max could be 0 to 2h maybe? (where 0 is the same as disabling the feature).
- consider urin ph tendency?: on/off toggle (default off), again with a decimal input field
-
regarding disclaimer etc.: when it hink about it, since i'm based in DE (i.e. EU) we should focus on that and not US (unless necessary). i don't have abusiness and i am not selling anything, the app is hosted open source, so i am not even sure if we need anything / much. i just want to make make sure that this is just a hobbyist project without any guaranties or liabilities.
-
i would not start to use sliders for now. the +/- input fields should provide sufficient control on mobile (+/- buttons) and desktop (input field). if need be i can change this later.
-
summary: to make things more transparent we could e.g. show a table with the individual values, or a step by step description of the individual variables used in the simulation formula(s) with interim caclualations and the final formal (surely at least the dosage and time will always stay variables). something like this might not be overly complicated (e.g. simple table for the former, or in text form maybe similar to the step by step description in the AppPharmacokineticsImprovementPlan.md "5. Computational Modeling and Simulation Parameters" (formula, individual parameters with short description and actual values based on the user input). this could be a foldable box on the left side under the plan section or if need be a full width (two columns) box above the final desclaimer/footer box. if this sounds to complex or needs more discussion / input (to make at least a prototype that i can evaluate), we can leave this for now and maybe add it later.
make it so that the "Medication History" simulation setting uses a toggle so that the user can quickly toggle between no medication history (starting with the first day) and if on, the medication history days field shows (we can still allow min = 0 even if it's simulation wise the same as deactivating the feature, but we have a similar behavior in other placeses e.g. Taken With Meal / Absorptoin Dealy).
let's allow a simulation duration of 1 and call it something like "Minimum simulation duration" so users can set it to 1 to see only the chart with a single day without scrollbars. i already tried to set min=1 but there are some problems (we set it to 3 for a reason at the time). there are at least some placeses where this value is used, e.g. the calculate/generate the x-axis ticks (at least if i set it to 1 but have two alternate plans added, meaning there are 3 days in the simulation which i see in the curve but day 2 and 3 have x-axis ticks. please ensure that everywher where te value is used as is, it takes this values e.g. as max(minSimulationDays, ) (where minSimulationDays means the current field's alue).