The identity used for a personal treatment record should not automatically become the identity used in community conversation.
A private record and a social presence solve different problems. The product should treat them that way.
One account can hold different contexts
A patient record needs durable identity, careful access, and a clear connection to the person receiving care. A community conversation benefits from the freedom to ask a question or share an experience without publishing that same identity.
Combining those contexts into one visible profile may be convenient for a product, but it asks the person to carry unnecessary exposure.
Separation should be structural
Privacy cannot depend only on a person remembering which field will appear publicly. The distinction should be visible in the interface and enforced in the data model.
- A community alias should not expose the legal or patient-facing name.
- Treatment events should not become community content by default.
- Connected clinics should receive only the access granted to that care relationship.
- Export and deletion controls should use plain language.
Privacy is a product behavior
Privacy statements matter, but the daily behavior of the interface matters more. The system should make the private choice the natural choice, explain when information crosses a boundary, and avoid collecting details that the product does not need.
That is the standard Dose & Tell uses when designing personal tracking, community, and connected care as related but distinct experiences.
This article provides general product and record-keeping context. It is not medical advice and does not recommend a medication, dose, treatment change, or response to symptoms. Bring medical questions to an appropriately licensed clinician.
