Feature Request: Family/Private Option for Blood Pressure Records

[cmjmmrp-byte]

Hello Yuvomi team,
I would like to suggest a small change to the way blood pressure measurements are recorded in Yuvomi.
I know that the Private / Family option is already integrated and works very well. My suggestion is simply to change the default option when entering blood pressure measurements (systolic and diastolic values).
At the moment, the measurement is set to “Private” by default. I would suggest changing this so that “Family” is selected by default, while still allowing the user to manually change it to “Private” whenever they prefer.
I believe that, in a family health-management application, blood pressure readings are generally useful information for all family members to have access to. In particular, having these values readily available could be very important in an emergency, when another family member may need to know the person's usual blood pressure or recent readings.
So, rather than adding a new feature, the request would simply be:
Current behaviour:
Blood pressure measurement: Private (default)
Suggested
Blood pressure Family change to default
The existing Private / Family selector would remain available, so users who prefer their measurement to remain private could still change the option before saving it.
I think this small change would make Yuvomi even more practical as a shared family health-management tool, while preserving the existing privacy controls.
Thank you very much for considering this suggestion.
And congratulations on the excellent work you are doing with Yuvomi. The application is very well designed, organized, and thoughtfully structured. It is clear that a great deal of care and attention has gone into creating such a useful and practical tool for managing family health information.
Keep up the great work!
Best regards,
Carlos

[ulsklyc]

Thank you, Carlos, and thank you for framing it as a default rather than a feature. That distinction is what makes it answerable.

The emergency argument is a good one, and I am not going to change the shipped default because of it. Here is the reasoning, and then what I am doing instead, which I think gets you closer to what you actually want.

Why not flip the default globally. Stored readings carry their own visibility, so existing entries would stay private and nothing would leak retroactively. The risk is not in the data, it is in the habit. Somebody who learned that blood pressure is private would, after an update, record a reading and share it without doing anything. An opening that nobody triggered is the one kind of privacy change that cannot be taken back: the default can be reverted in a line, the rows written in the meantime cannot.

Why not a blood-pressure-specific rule. Vitals used to have exactly that shape. Before #609 the special case type === 'bp' sat in five places in the health page, and the metric table replaced all five with one description per metric. A default that applies to one measurement type only would put the first of those five back. And the same list holds mood on a 1-5 scale, where "family by default" is a very different proposition.

What I am doing instead. The cycle tab already has what you are asking for, in a better form: a personal default visibility in its settings, plus a bulk switch that moves existing entries. The other four health areas do not have it, and that inconsistency, not the value of the default, is the actual gap. Extending that pattern means the household decides rather than me: you set blood pressure to family once, every new reading follows, and the private/family selector stays exactly where it is on each entry. The shipped default stays private, because the safe direction for a default is the one that requires a decision to open.

One thing that already exists today and may cover the emergency case better than any default: an admin can grant a person care of another person's health data (Settings, Family, edit the member). A caregiver sees the cared-for person's readings including the private ones, which a family visibility does not do. If your goal is that one specific person can look up the usual values, that is the stronger tool and it is available now.

I will follow up here when the per-area default lands.