🏠 Overview › 🎯 Features ›🎯 Contact Detail & Edit

Contact Detail & Edit

Feature Detail

medium complexity extracted Contacts & Peer Mentor Management Confidence: 100%
3
Components
58
Shared
0
User Stories
Yes
Analyzed

Description

This feature provides a dedicated screen for viewing the full profile of a contact, including personal details, associated activities, notes, and caregiver relationships. An edit flow allows authorized users to update contact information through a validated form. The detail screen serves as the central hub for all information related to a single contact, surfacing linked activities, notes, and relationships in a structured layout. Edit access is gated by role — peer mentors can edit their own contacts while coordinators can edit any contact within their local association.

User Flow

Contact Detail & Edit user flow
Click to expand

Analysis

Business Value

Accurate and up-to-date contact information is essential for effective peer mentoring. When a peer mentor visits a contact, they need immediate access to health context, previous interaction history, and caregiver details without switching between apps. The edit capability ensures data stays current without requiring coordinator intervention for every change, distributing the administrative burden appropriately. For organizations like Blindeforbundet that require formalized home visit reporting, the contact detail screen is the launching point for structured reports, making its completeness and usability directly tied to reporting compliance and Bufdir audit readiness.

Implementation Notes

The detail screen is a Flutter screen composed of sectioned cards: personal info, recent activities, notes preview, and caregiver links. Data is fetched via the Contact Service from the REST API (`/api/v1/contacts/:id`) and cached locally. The edit flow uses a shared ContactFormWidget with field-level validation matching backend constraints. Optimistic updates are applied locally and synced via the Sync Service. Role-based field visibility is enforced client-side by the Role Guard Service, with server-side enforcement on PATCH `/api/v1/contacts/:id`. All form fields use AppTextField widgets from the design system, ensuring consistent styling and accessibility. The ContactFormWidget supports dynamic field labels via the Organization Labels system to accommodate per-org terminology.

Components (61)

User Interface (3)

ui Contact Detail Screen medium ui Contact Form Widget medium ui Edit Contact Screen medium

Shared Components

These components are reused across multiple features

Infrastructure (20)

infrastructure JWT Infrastructure medium Shared infrastructure JWT Infrastructure low Shared infrastructure Auth Middleware medium Shared infrastructure Report API Middleware low Shared infrastructure Report Access Guard low Shared infrastructure Approval Audit Logger low Shared infrastructure End-to-End Encryption Infrastructure high Shared infrastructure Email Delivery Infrastructure low Shared infrastructure Invitation Token Infrastructure medium Shared infrastructure Signed URL Provider low Shared infrastructure Multi-Tenancy Infrastructure high Shared infrastructure Calculator Export Infrastructure medium Shared infrastructure Request & Response Interceptors high Shared infrastructure Design Token System medium Shared infrastructure Semantic Labels Infrastructure medium Shared infrastructure Connectivity Infrastructure low Shared infrastructure Local Database Infrastructure high Shared infrastructure Secure Storage Infrastructure medium Shared infrastructure Connection Pool Infrastructure medium Shared infrastructure Database Migration Infrastructure medium Shared

User Stories

No user stories have been generated for this feature yet.