Back to work

Live

NRCMS - National Rehabilitation Centre Management System

A live full-stack rehabilitation-centre operations system for role-aware administration, patient records, recovery tracking, support, orders, and approvals.

Live NRCMS deployment screenshot
Status
Live
Maturity
Built and deployed
Role
Full-stack developer
Users
Rehabilitation administrators, staff members, and operational coordinators.

Problem

Rehabilitation-centre operations need role-aware tools for patient records, recovery tracking, orders, support queries, centre workflows, and administrative approvals.

Scope

Rehabilitation administrators, staff members, and operational coordinators.

My contribution

Built a role-aware rehabilitation operations platform covering administrative approval flows, patient records, recovery progress, order handling, support queries, centre operations, and deployment.

  • Implemented role-aware access patterns and protected operational dashboards for different rehabilitation workflows.
  • Built patient, recovery, order, support, centre, and administrative approval surfaces around practical operations.
  • Structured the Next.js, MongoDB, and Vercel deployment path for a live portfolio-grade product.

Technical decision

Presented NRCMS as a live working system without implying official nationwide production adoption or clinical validation.

Architecture and data flow

01Interface

Built a role-aware rehabilitation operations platform covering administrative approval flows, patient records, recovery progress, order handling, support queries, centre operations, and deployment.

02Architecture

Next.js and React interface, MongoDB-backed operational data, custom authentication, RBAC-style access, Radix UI components, and Vercel deployment.

03Data flow

Role-specific users move through patient, recovery, order, support, centre, and approval workflows with operational state persisted in the application backend.

04Security

Role-aware authentication is part of the system; clinical compliance, production healthcare deployment, and official adoption are not claimed.

Technical challenges

  • Representing sensitive healthcare-adjacent workflows without exposing personal data or making medical claims.
  • Designing several operational modules without losing role clarity.
  • Balancing live deployment visibility with careful limitations around adoption and validation.

Outcome

A live deployed management system is available for portfolio review, framed as a working software product rather than an official healthcare deployment.

Limitations

No official adoption, clinical validation, production patient data, or healthcare compliance certification is claimed.

Future improvements

Add audit trails, stronger permissions testing, reporting, and stakeholder validation for real operational deployment.

Verified technology stack

Next.jsReactTypeScriptMongoDBRadix UICustom authenticationRBACVercel