Health Membership Platform, Tested Before Build

The Challenge

A membership card is only worth buying if enough good clinics accept it. Every hospital runs its own management system and there is no shared integration standard, so each new partner would turn into a separate IT project. The client needed 6 to 10 facilities live at launch, and that target was at risk if joining took weeks of integration work.

One Design Rule: Join Without IT

Nexora designed Phase 1 around a single constraint: a facility should be able to join in one session with no IT department. The front desk opens a web page on a phone or tablet it already owns, scans the member’s QR code, sees the tier and benefits, and records the visit. Nothing is installed and nothing touches the hospital’s own systems. Integration with those systems was moved to Phase 2, for facilities with enough members to justify it.

What the Prototype Proves

The prototype runs three roles on one live event feed. A transaction recorded at the counter shows up on the member’s phone and in the admin view within the same second, with no refresh. The trial guide walks reviewers through five properties of the design.

• Benefits that follow the member’s tier, with a per-visit discount cap shown to the front desk before it confirms
• Points kept as an append-only ledger, with expiring points spent first
• QR codes that rotate every 60 seconds and live for 90, so a forwarded screenshot is refused
• Monthly partner reconciliation whose lines always add up to the month total
• New partners added through one admin form, visible in the member app at once

Rules Built Into the Flows

The prototype carries real business rules, not mock screens. Cards show green, amber or red at the counter, and every refusal comes with a reason in plain language. An expired card gets a seven-day grace period, and family plans give each person their own QR card under one account. Front-desk staff see the discount, the amount the member pays and the points earned, but never the platform’s commission.

Phase 1 Scope

Three apps share one backend that Nexora would build and run on domestic cloud infrastructure. The member app targets iOS and Android, the counter app is a browser-based PWA, and the admin site is built in Next.js. Payments go through an external gateway instead of in-app purchase, which suits a membership that is redeemed at real facilities. Medical records are not stored.

• One city, 6 to 10 facilities, 3 member tiers
• One payment gateway, one e-invoice provider, one OTP channel
• Vietnamese only, online-only counter
• Points redemption, charts and in-app maps deferred to Phase 2

What Is Still Simulated

OTP codes, the payment screen and e-invoice numbers in the prototype are simulated, and sample data reloads every morning. The prototype is a decision tool. It shows the client what they would own, where the rules live and what was left out on purpose. The next step is a scope workshop to fix benefits, points rules and the first facility list.