Appointment journey
The source prototype models request, confirmation, arrival and session completion.
FULL-STACK DESIGN / BILINGUAL EXPERIENCE
One workflow. Every care-team role.
An anonymized portfolio case study of a bilingual clinic platform prototype. It connects appointment, report-review and staff leave journeys, with a proposed production design for identity, scoped access and private document storage.
Interactive prototype; production architecture proposedReport review
Draft, submission, review and publication states illustrate a controlled release workflow.
Arabic / English
The original prototype includes bilingual presentation and right-to-left layouts.
Staff operations
A simplified leave-request and HR decision journey demonstrates cross-role coordination.
INTERACTIVE PORTFOLIO ILLUSTRATION
Explore the workflow.
DEMO CASE 001
Appointment → report publication
A reduced portfolio simulation. All state stays in this page and resets on reload.
SYSTEM DESIGN
Architecture at a glance.
01AR / EN portals
02Application API (planned)
03Scoped policy (planned)
04PostgreSQL (planned)
05Private S3 (planned)
06Audit / outbox (planned)
Prototype: React · Next.js conventions · TypeScript · Vinext / Vite. Proposed production: PostgreSQL · Prisma · Redis · private S3 · OIDC / MFA.
SOURCE EVIDENCE
What was actually built
Local delivery documentation and application source confirm an exportable prototype with simulated personas and in-memory state. The proposed schema covers appointments, report versions, role bindings, care assignments, files, audit events and leave approvals.
SCOPE & LIMITATIONS
What this demonstration means
The delivered prototype does not connect production authentication, PostgreSQL, Redis or S3. Persona selection is not authentication. This public demonstration contains only synthetic identifiers and a reduced workflow; it cannot store or process medical records.
Discuss a project with RegalFire.
Use the profile to explore more engineering work and start a discussion about scope.
Public / private boundary
Client identity, branding, commercial terms, clinical content, full schema, source application, credentials and all production integration details. These remain private.