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.
SELECTED WORK / PATIENT PORTALNeno HealthScroll into the project
Patient dashboard · Health information in one place · EXPLORE BELOWSELECTED WORK / Neno HealthHealth information.
Health information.
Connected around people.
A custom health platform connecting patient, practitioner and admin portals, with consent-based sharing, encryption, device security and audit trails. Originally developed as U-Health.
Launch project (opens in a new tab)Explore the experience ↓02 / THE BRIEFHealth records.
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
Patients needed a way to organise their health history and share selected information with practitioners. The product also needed emergency access and an administration layer to manage accounts, consent settings and audit records.
HOW WE HELPED
We delivered three connected portals: patients manage their records and sharing decisions; practitioners request access and view approved information; administrators manage practitioner accounts and platform controls.
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.
BEHIND THE EXPERIENCEThe right information.
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.
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.
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.
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.
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.
05 / DELIVERYThree portals.
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.
WHAT THE WORK MADE POSSIBLEOne product.
One product.
A place for every role.
Neno has a working foundation for connecting health information around people. Patients, practitioners and administrators each have a defined experience, with consent and access decisions built into the journeys.
Give each person a relevant experience
Separate portals organise the information and actions needed by patients, practitioners and the team administering the platform.
Make information sharing deliberate
Consent controls and emergency QR access support the intended sharing journeys, alongside records and medical-history features.
Build accountability into the platform
Encryption and device security complement consent and access controls, while reviewable audit trails give administrators greater visibility into platform activity.
DELIVERED IN NUMBERS
- Role-specific portals
- 3Patient, practitioner and administration experiences.
THE WIDER PICTUREWork. Ideas.
Work. Ideas.
Useful connections.
RELATED READING / FROM THE ARCHIVE
Make complexity
usable.
Discuss your platform ↗View all projects ↗Growth Advisory
