So I’ve been working a program, exact details don’t matter, which stores information in a database(either locally hosted or privately hosted by user). Basically it’s to store a history of seizures and medication, so you can give it to a doctor and see something like “well most seizures occur in morning so let’s give medication at 6am instead of 8am” or something like that. To do that requires two “accounts” one for caregiver and one for patient(idea is for parents of a child with medical issues). It requires accounts to see like “dad gave medicine at 7pm” or “mom saw child 1 have a seizure at 230pm”. These are basically just names stored in the local/private database, I will not no them or track them.
I don’t want to deal with hippa or be responsible for medical data so I specifically don’t want to host the data. Assuming you had a use for this and the ability host the database would you be turned off by the requirements of “accounts” even if you completely controlled them?
The whole idea behind having it hosted is to be able to record stuff when not at home. For example he had a seizure in the bathroom of a gas station the other day. I’d like to be able to use an app on my phone to generate a json file and send it to a server where it’s recorded in a dB.
The big thing I want is to be able to go to a doctor’s appointment and have a list of all seizures with applicable details. Like “in the last 6 months he had 84 seizures but you added medication X 4 months ago and as you can see that resulted in a 80% reduction in seizures on a weekly basis” or “he had 45 seizures in 3 months but they mostly happen just after lunch, can we adjust the medication schedule to account for lunch time?”
I don’t want it locally on my phone completely because I want his mother(my girlfriend) to also be able to record incidents if I’m not around and have everything sync to one source of truth. Yeah I guess it’s possible to record on my phone, record on her phone and then do some sort of merge to generate the full report but that seems really messy.
What I hear you say is: This would be convenient and easy for the user. Doing it differently, in a safer way that’s not problematically under scope for data protection regulations, would be more effort, not what you’re used to and “messy”. Certain useful features seem like they’d require more upfront work and the while system would be more complex and unfamiliar.
How is that relevant? None of that changes what you’re actually asking about or makes it a good approach. I don’t see how it’d make it either safer or less legally problematic?
Ok, so what other solutions are there? I want the ability to record medication doses given and seizure incidents from multiple sources into one collection and potentially pull that data to make reports?
DM me if you’d like to discuss further consulting on this project. I do think I could help you. However, reaching a proper design for this that is actually appropriate for your situation is non-trivial, goes beyond the scope of lemmy thread and would likely be paid.
I would also like these things to be easier and just be able to point you to something existing but the reality is they currently aren’t and such solution isn’t. But if you do push ahead and are open to sharing (potential security tradeoffs there too), maybe you’re in a position to be part of improving that situation.