Build a useful health history.
Patients manage allergies, conditions with ICD-10 lookup, medications, immunisations, screenings and family history. Vitals include BMI calculations and historical charts.

Neno Health needed a way for people to manage their health history and share selected information with practitioners. We developed the brand and a custom platform with patient, practitioner and administration portals, building consent decisions into the experience.
Launch project (opens in a new tab)Explore the experienceBranding · Product design · Patient portal · Practitioner portal · Admin console · Consent management · Emergency QR · Encryption · Device security · Audit trails
A useful health record has to serve different people without giving everyone the same access. Patients need to organise their history, practitioners need to request relevant information and administrators need to manage accounts and review activity.
Originally developed as U-Health, the platform brings those roles into three connected portals. Patients manage their records and approve or decline requests. Practitioners specify what they need, why they need it and when access should end. Administration tools support practitioner verification, settings and audit review, alongside the delivered encryption and device-security capabilities.
Practitioners request a defined scope of information with a purpose and expiry, and patients can approve or decline access. The connected administration portal supports verification and audit review, making those consent decisions part of the working platform rather than an instruction outside it.
Practitioner requests define the scope, purpose and expiry of access. The patient decides whether to approve, and shared views follow that consent.
Practitioner accounts, configurable settings and audit-log review give administrators practical tools behind the patient and practitioner journeys.
A practitioner request defines what information is needed, why it is needed and when access should expire. The patient decides whether to approve it.
Patients manage allergies, conditions with ICD-10 lookup, medications, immunisations, screenings and family history. Vitals include BMI calculations and historical charts.
Practitioners search by email or ID and compose requests with a defined scope, purpose and expiry. A request list makes progress and status visible.
Patients approve or deny practitioner requests. Approved information is presented through read-only shared views based on that consent.
Administrators create and verify practitioner accounts, explore and export audit logs, and manage consent settings, security settings and email templates.
Product workflow overview across the patient, practitioner and administration portals.
Quick selections and structured fields help patients add medical conditions, describe their history and record diagnosis status.

The public entry screen directs patients and healthcare practitioners into their respective portals, explaining what each experience provides.

Onboarding captures consent; profiles include medical aid and emergency contacts. Six medical-history categories and vitals charts make the record useful beyond a basic profile.
A configurable public emergency card is accessed by QR code. Separate practitioner requests use scope, purpose and expiry, with patient approval and read-only shared views.
Practitioner verification, consent settings, security settings and email templates give administrators the tools to manage the platform behind the patient and practitioner experiences.
Encryption, device security, access controls and audit trails form part of the delivered platform, alongside patient-controlled sharing.
Encryption adds protection for health information handled by the platform, alongside the permissions that govern access.
Device security forms another layer of the platform’s safeguards, complementing account permissions and patient-controlled sharing.
Administrators can filter audit logs and export them as CSV files, giving the team a record to review when investigating platform activity.
Role management and row-level data policies separate access across the three portals. Practitioner requests define scope, purpose and expiry, with the patient deciding whether to approve.
Neno Health needed a way for people to manage their health history and share selected information with practitioners. We developed the brand and a custom platform with patient, practitioner and administration portals, building consent decisions into the experience.

Branding · Product design · Patient portal · Practitioner portal · Admin console · Consent management · Emergency QR · Encryption · Device security · Audit trails
A useful health record has to serve different people without giving everyone the same access. Patients need to organise their history, practitioners need to request relevant information and administrators need to manage accounts and review activity.
Originally developed as U-Health, the platform brings those roles into three connected portals. Patients manage their records and approve or decline requests. Practitioners specify what they need, why they need it and when access should end. Administration tools support practitioner verification, settings and audit review, alongside the delivered encryption and device-security capabilities.
Practitioners request a defined scope of information with a purpose and expiry, and patients can approve or decline access. The connected administration portal supports verification and audit review, making those consent decisions part of the working platform rather than an instruction outside it.