Skip to content Back to projects
Neno Health patient dashboard with health readings, medical records, emergency QR and sharing controls
SELECTED WORK / PATIENT PORTALNeno HealthScroll into the project
Patient dashboard · Health information in one place · EXPLORE BELOW
SELECTED WORK / Neno Health

Health information together.
Sharing on the patient’s terms.

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 experience
02 / THE BRIEF

Health records.
Patient control.

Project period
2025 · product MVPBrand and product delivery across patient, practitioner and administration journeys.

Branding · Product design · Patient portal · Practitioner portal · Admin console · Consent management · Emergency QR · Encryption · Device security · Audit trails

WHAT THE CLIENT WANTED

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.

HOW WE HELPED

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.

WHAT THE WORK MADE POSSIBLE

A connected health record.
Clear roles and decisions.

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.

Keep sharing deliberate

Practitioner requests define the scope, purpose and expiry of access. The patient decides whether to approve, and shared views follow that consent.

Support the people running the platform

Practitioner accounts, configurable settings and audit-log review give administrators practical tools behind the patient and practitioner journeys.

DELIVERED IN NUMBERS
Role-specific portals
3Patient, practitioner and administration experiences.
BEHIND THE EXPERIENCE

The right information.
Shared by permission.

A practitioner request defines what information is needed, why it is needed and when access should expire. The patient decides whether to approve it.

01 / Personal recordsOrganisePatient portal

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.

02 / Defined accessRequestPractitioner portal

Ask for specific information.

Practitioners search by email or ID and compose requests with a defined scope, purpose and expiry. A request list makes progress and status visible.

03 / Consent decisionApprovePatient controls

Keep the sharing decision with the patient.

Patients approve or deny practitioner requests. Approved information is presented through read-only shared views based on that consent.

04 / AccountabilityOverseeAdmin console

Manage the platform behind the care journey.

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.

01 / MEDICAL RECORDS

A clearer way to build a health history.

Quick selections and structured fields help patients add medical conditions, describe their history and record diagnosis status.

neno.health
Neno Health medical-record form with common-condition choices, title, details and diagnosis status
SCROLL TO REVEAL 01 / 02
02 / PLATFORM ENTRY

One platform. Two clear entrances.

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

neno.health
Actual Neno Health platform entry interface
SCROLL TO LOOK CLOSER 02 / 02
05 / DELIVERY

Three portals.
One connected foundation.

A patient-owned health record

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.

Emergency access and controlled sharing

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.

Day-to-day platform administration

Practitioner verification, consent settings, security settings and email templates give administrators the tools to manage the platform behind the patient and practitioner experiences.

TECH STACK & CONNECTIONS
Frontend
React 18 · TypeScriptApplication interface
Interface
Tailwind CSS · Radix UIShared interface components
Server
Node.js · Express 4Application backend
Data layer
Drizzle ORMTyped data-access tooling
Build
ViteFrontend build tooling

Security & accountability.

Encryption, device security, access controls and audit trails form part of the delivered platform, alongside patient-controlled sharing.

01 / ENCRYPTION

Protect sensitive information.

Encryption adds protection for health information handled by the platform, alongside the permissions that govern access.

02 / DEVICE SECURITY

Protection beyond the account.

Device security forms another layer of the platform’s safeguards, complementing account permissions and patient-controlled sharing.

03 / AUDIT TRAILS

Make activity reviewable.

Administrators can filter audit logs and export them as CSV files, giving the team a record to review when investigating platform activity.

04 / ACCESS CONTROLS

Define who can see what.

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.

EXPLORE MORE

Related services
and articles.

RELATED READING / FROM THE ARCHIVE
YOUR NEXT PROJECT

Make complexity
usable.

Discuss your platform View all projects
NEXT PROJECT

Growth Advisory

Growth Advisory homepage with the Cliffs of Moher, designed by Cloudfusion
Actual Growth Advisory responsive homepage
Explore Growth Advisory
ShipToSage
Enlarged project screen
CLOUDFUSION / GET IN TOUCH
Rather talk first?+27 (0)81 044 5554Call
  1. 01 Choose
  2. 02 Details
  3. 03 Send
What would you like help with?

Describe it in your own words, or choose a service below.

What happens next?

Answer a few questions, then check your details before sending. We’ll review what you need and get in touch to discuss the scope, budget and next step. Sending an enquiry does not commit you to a project.

Already a client?Account help, faults, access or renewals.

Nothing is sent until you submit. How we use your details (opens in a new tab) · Privacy Notice (opens in a new tab) ·

ALREADY WITH CLOUDFUSION

Client
access.

Use the right workspace for what you need to do.

Client login Invoices, renewals, hosting, domains and account details.Get support Sign in to open a support ticket for a service Cloudfusion already manages. Your ticket stays with your account history.

Trouble signing in?

For an active project, use the workspace link supplied by your Cloudfusion contact.