# Family Health Record Design: Identity in Every Entry Source: https://www.jvds.cn/en/share/ui-design/family-health-identity-data-u090 Language: en Published: 2026-10-18 Author: JVDS Design Studio Vitaio uses pale backgrounds, cyan emphasis, and small object icons to make sleep, hydration, and activity records approachable. Family pages show name, age, and relationship before entries, a useful order for shared viewing. Identity, record time, and data meaning still need to remain clear. ## Key takeaways - Family records should establish identity before explaining completion and reminders. - Measurements, scores, and summaries need names, units, and time ranges. ## Establish whose record it is first Sara Bennett’s portrait and relationship appear above Health overview, followed by sleep, activity, medication, and hydration. Icons help scanning on the left, with checks or bells on the right; Not logged yet explicitly retains missing information. Checks, bells, and values mean completion, reminders, and content respectively, and should not be treated as one judgment. JVDS prefers explicit missing states and update times for each entry, preventing a tidy list from implying complete records. Adding a family member offers QR codes, scanning, and invitation links for in-person or remote connections. After connecting, visible content and [viewing, proxy-entry, and editing permissions](https://www.jvds.cn/en/share/ui-design/b2b-role-permission-design) still need choices. A relationship name does not automatically mean every record is shareable. ![Vitaio QR invitation and Sara family summary with completed or unlogged entries](https://www.jvds.cn/upload/2026/1008/d187-tp/u090-i1.webp) Family page | Identity precedes records; missing states remain explicit in words. ## Large values need readable meanings The heart-rate page has dates above a ring emphasizing 100, then 80 bpm below, with maximum, minimum, and average in the nearby overview. Dates and metrics remain together for checking one day’s records. 100 lacks a clear name; size cannot identify it as measurement, score, or target. Scores need names and explanation; measurements need units. Aggregations over different periods also need labels so averages do not become mistaken for current readings. Manual addition is visible and should retain [source and time](https://www.jvds.cn/en/share/ui-design/ai-agent-task-history-audit-log) after saving. Today’s insight needs correspondence with its underlying records, avoiding complete conclusions when data is missing or insufficient. This is information design, not a health assessment of the readings. ![Heart-rate dates, large 100, 80 bpm, maximum/minimum/average, and manual addition](https://www.jvds.cn/upload/2026/1008/d187-tp/u090-i2.webp) Record details | Name scores, measurements, and statistics separately. ## Preserve identity and time across devices Tablet navigation moves left, with records centrally and cyan current sections and add controls continuing the mobile style. Additional space stabilizes lists rather than converting everything into large charts, suiting multi-item management. Android examples continue cyan dates and key figures. Layouts can adapt, while current person, units, and sources stay consistent. Adding water needs to establish for whom, on which day, and how much, beyond identical graphics across platforms. The presentation mentions stylus and device adaptation, but actual use still needs verification around concrete input tasks. Revoked sharing or stopped updates should also have explicit states, keeping older content within a clear time context. ![Tablet My trackers cards and Android hydration pages](https://www.jvds.cn/upload/2026/1008/d187-tp/u090-i3.webp) Cross-device records | Layout changes should not change the object or time basis. ## Frequently asked questions ### Can connecting family members share every record by default? Provide explicit content and action permission choices, plus a way to stop sharing. An invitation identifies the connected person but cannot replace scope confirmation. ### Are numbers and icons sufficient for health cards? Key values also need names, units, dates, and sources. Different items update at different times; missing information should be explicit. ## Design review checklist - Make the record’s person identifiable in every detail. - Name scores and measured readings separately. - Allow sharing and proxy-entry scope to be edited and revoked. ## Organize records and sharing permissions A family record product can standardize people, dates, and sources first, then plan shared viewing, manual entry, and cross-device experiences. JVDS Design Studio provides UI/UX design, website design, and development services, helping organize page content, interface structure, and implementation needs. [Contact JVDS to discuss your project](https://www.jvds.cn/contact)